Bug Fixes v4.4.0	Fixed: (FasTrak only) PDIfastrak::Get/SetSyncMode() not implemented. Fixed: (FasTrak only) PDIfastrak::SetPresetFilters() always returns FALSE even if success. Fixed: (FasTrak only) PDIdev::GetSetBufEnabled() returns HOST_FRAME_ERROR.  Should return PI_API_UNSUPPORTED. Fixed: PDI is installed in Windows Program Files (x86) area, which is usually write-protected without Admin rights.  This prevents sample projects from being built and modified by the developer-user.
Bug Fixes v4.3.0	Fixed: (G4 only) G4Track.dll crashes when started and stopped without G4 hub activation.  Fixed by G4Track.dll v1.0.5. Fixed: Errors and omissions in online help coverage of programming for G4 with the PDI.
Bug Fixes v4.2.0	Fixed: FasTrak Set Output Data List: Command returns failure even when successful. Fixed: FasTrak Set Output Data List while in stylus point-track mode results in comm frame error. Fixed: PDIfastrak::SetBinary() not implemented. Fixed: PDIfastrak::TxtCmd() not implemented Fixed: Using the PDI_ALL_STATIONS -1 wildcard with LATUS commands may produce a crash if markers are launched.
Bug Fixes v4.0.4	Fixed G4 Filter Get/Reset: Filters read incorrectly. Fixed: Unable to start G4 using Unicode PDI build.  Extended PDIg4 to correctly support legacy PDIdev functions GetDetectedSensors() and MaxSensors()
Bug Fixes v4.0.3	Fixed legacy-mode G4 P&O data reporting: Unable to configure legacy mode outputs. Fixed DiscoverCnx() error when connecting to G4.
Bug Fixes v4.0.2	Fixed LATUS & Patriot WIRELESS DiscoverCnx bug: Read Installed Markers operation fails when it should not.
Bug Fixes v2.4.0	Fixed PDIconsole bug: FC not displayed, DisplayCont re-displays old frames.
Bug Fixes v2.2.6	Explicit calls to CPDIdev::ConnectSer() always fail, but DiscoverCnx does not. When you put the tracker into continuous mode and then destroy the connection in a disorganized fashion, perhaps by crashing the host application abnormally or ending a debugging session while the connection is live and in continuous mode.  The next time you try to create a USB connection to the tracker, you will not be able to, and the tracker will have to be restarted in order to re-connect.
Bug Fixes v2.2.5	When using station wildcard to set MinuteMan™ sensor-level configurations, memory violation occurs after operation is complete. When connected to any any tracker other than MinuteMan™ via RS-232, getting out of sync with tracker output may result in a crash of the PDI data collection thread.  The RS-232 connection can get out of sync by either forcing too much data onto the 115,200 bps link, or by overloading the host pc such that it cannot service the COM port interface in a timely manner.
Bug Fixes v2.2.4	CPDIdev::StartStylusPno() causes garbage frame to be sent to tracker.  This bug was introduced in v2.2.3. MinuteMan™ sensor-level configuration operations on sensor 2 can cause memory violations due to an indexing error. Minor PDI.chm online help edits. Modified PDImulti sample project to support all tracker types.
Bug Fixes v2.2.2	Frames lost over USB in continuous mode under CPU load. Multiple frames may be received with single event, but only one frame is propagated to client.
Bug Fixes v2.2.0	Floating-point comparison fixed so that floating point tracker settings are not erroneously reported as errors when negative numbers are involved. PDI does not return "FALSE" value when PI_HOST_CONT_CMD_SENT error code occurs.  This occurs when commands are sent while in continuous mode.  Commands do get to the tracker but settings are not read back by the PDI for verification. This does not indicate an error condition. PDI handles "empty" P&O frames received from Liberty LATUS when no markers are launched.
Bug Fixes v2.1.3	Error messages from "Set" commands are now received over RS-232 connection to trackers. Floating-point comparison relaxed so that floating point tracker settings are not erroneously reported as errors. CPDIdev::ConnectUSB() finds and establishes USB connection properly now.
Bug Fixes v2.1.2	CPDIdev::WhoAmISensor() has been modified to take sensor number '0' (zero) as a parameter to retrieve the WhoAmI information from the source.