History v4.4.0 |
- Bugs fixed: See
Bug Fixes 4.4.0
below.
- UDP/IP socket P&O output feature added to PDI.
- UnityExport sample program added for exporting P&O data to UDP for Unity3D
- FTmfc sample SetPresetFilters demonstration added.
- Updated G4Track DLL to v1.0.6
- Unmanaged VC++ v13.0 (VS 2015) build added.
- Unmanaged VC++ v12.0 (VS 2013) build added.
- Unmanaged VC++ v11.0 (VS 2012) build is no longer available.
- Unmanaged VC++ v10.0 (VS 2010) build is no longer available.
|
History v4.3.0 |
- Bugs fixed: See
Bug Fixes 4.3.0
below.
- Updated G4Track.dll to v1.0.5
- G4console sample project added.
- Unmanaged VC++ v11.0 (VS 2012) build added.
- Unmanaged VC++ v10.0 (VS 2010) build is still available.
- Unmanaged VC++ v9.0 (VS 2008) build is no longer available.
- Unsupported MinuteMan™ functions and classes removed from all builds.
- The PDI is no longer tested or guaranteed on Windows XP platforms.
- Known Anomalies in this release:
- The VC 11 build does not include the Winforms sample program.
- For FasTrak projects only: Unicode builds (ReleaseUnicode, DebugUnicode) should not be used.
Instead use multi-byte Debug and Release versions of the DLLs. This only affects PDIfastrak methods
that deal with character strings: Get/SetCfgLabel(), TxtCmdW(), WhoAmI(), GetLastResultStr(), ResultStr()
and StartSocketExport(). This limitation will be resolved in the next release of the PDI.
|
History v4.2.0 |
- Bugs fixed: See
Bug Fixes 4.2.0
below.
- Unmanaged VC++ v10.0 (VS 2010) build added.
- Unmanaged VC++ v9.0 (VS 2008) still available.
- All DLLs available in Win32 or x64 platform builds.
- FasTrak console (FTconsole) sample program added.
- TCP/IP socket P&O output feature added to PDI.
- PDIsock sample program added to demonstrate client-side of socket.
- PDImfc sample extended to work with all trackers without modification including
FasTrak and G4.
- PDIg4 and PDIfastrak dlls now delay-loaded: If they are not needed by the
end-user application, they do not need to be distributed.
- Known Anomalies in this release:
- For FasTrak projects only: Unicode builds (ReleaseUnicode, DebugUnicode) should not be used.
Instead use multi-byte Debug and Release versions of the DLLs. This only affects PDIfastrak methods
that deal with character strings: Get/SetCfgLabel(), TxtCmdW(), WhoAmI(), GetLastResultStr(), ResultStr()
and StartSocketExport(). This limitation will be resolved in the next release of the PDI.
- On Windows XP only: Launching the G4mfc sample program from the Start Menu causes an error. To work
around this problem, move the G4mfc.exe executable into the Lib\Win32 or Lib\x64 PDI folder and launch
from there.
|
History v4.1.0 |
- Support for FasTrak added in class PDIfastrak.
- Unmanaged VC++ v9.0 (VS 2008) build.
- VS 2005 (VC8.0) version deprecated.
- VC6.0 version deprecated.
- Caveat: DLLs available in Win32 platform builds only.
|
History v4.0.4 |
- Bugs fixed: See
Bug Fixes 4.0.4
below.
- Unmanaged VC++ v9.0 (VS 2008) build.
- VS 2005 (VC8.0) version deprecated.
- VC6.0 version deprecated.
- Caveat: DLLs available in Win32 platform builds only.
|
History v4.0.3 |
- Bugs fixed: See
Bug Fixes 4.0.3
below.
- Updated PDImfc sample program to demonstrate interchangeability between CPDIdev
and CPDIg4.
- Updated PDIconsole sample to demontrate event-driven processing based on Windows
messages in a non-windowing application.
- Unmanaged VC++ v9.0 (VS 2008) build.
- VS 2005 (VC8.0) version deprecated.
- VC6.0 version deprecated.
- Caveat: DLLs available in Win32 platform builds only.
|
History v4.0.0-2 |
- Support for G4 tracker added in class PDIg4.
- Unmanaged VC++ v9.0 (VS 2008) build.
- VS 2005 (VC8.0) version deprecated.
- VC6.0 version deprecated.
- Caveat: DLLs available in Win32 platform builds only.
- Bugs fixed: See
Bug Fixes 4.0.2
below.
|
History v3.0.0 |
- Unmanaged VC++ v9.0 (VS 2008) version added.
- VS 2005 (VC8.0) version still available.
- VC6.0 version deprecated.
- All DLLs available in Win32 or x64 platform builds.
|
History v2.4.1 |
|
History v2.4.0 |
- Support for Patriot Wireless™
added.
- Unmanaged C++ VS 2005 (VC8.0) version added; VS.NET (VC7.1)
deprecated.
- Bugs fixed; See Bug Fixes 2.4.0
below.
|
History v2.3.0 |
- Unmanaged C++ (VC7.1) VS.NET version of PDI added.
- PDIpipe sample program added to demonstrate creation of
named-pipe client for collection of tracker data by external processes.
- CPDImdat::FrameSize() method added to calculate size in bytes of
configured tracker data.
- CPDIdev::StationCount() method added to query number of active
stations (e.g. For framesize calculation).
|
History v2.2.6 |
- UNICODE versions of Debug and Release PDI libraries added.
- Bugs fixed; See
Bug Fixes 2.2.6 below.
|
History v2.2.5 |
- Bugs fixed; See
Bug Fixes 2.2.5 below. Fixes do not affect use with
Liberty™, Patriot™, or Liberty LATUS™ connected
via USB.
|
History v2.2.4 |
|
History v2.2.3 |
- New features do not affect use with Liberty™ or Patriot™:
- Extended PDI support for Liberty LATUS™ Boresight 'B' command.
- Extended PDI support for Liberty LATUS™
Trigger Pack output data.
- Extended to support MinuteMan™. Changes do not affect use with
Liberty™, Patriot™ or Liberty LATUS™.
|
History v2.2.2 |
- Support added for tracker USB Buffering Mode.
- Performance enhancements for continuous USB data collection:
- Internal circular buffer is larger to reduce HOST_OVERFLOW_ERROR
occurrence.
- Data collection threads operate at a higher thread priority.
- Added safety net for RS-232 frame overrun. If I/O gets out of
sync over RS-232, collection thread searches input stream for motion data frame
header to re-sync.
- Make default Debug Level 0 silent so that NO trace messages are
displayed by default. This causes significant performance problems when
debugging with Visual Studio 7.0.
- Bugs fixed. See Bug Fixes v2.2.2
below.
|
History v2.2.1 |
- New features do not affect use with Liberty™ or Patriot™:
- Improved PDI online help for programming for Liberty LATUS™.
- Extended PDI support for Liberty LATUS™ 'N' command.
|
History v2.2.0 |
- Bugs fixed; see Bug Fixes v2.2.0
below.
- Other new features do not affect use with Liberty™ or Patriot™:
- Extended to support Liberty LATUS™.
|
History v2.1.3 |
|
History v2.1.2 |
- Important: If managing a LIBERTY
with more than 8 sensors, it is recommended that you use PDI version 2.1.2 or
higher, as it has been designed to work properly with recent upgrades in USB 1.1
drivers.
- Fully supports Liberty™ trackers with 4 to 16 sensors.
- Added an internal running "HostFrameCount" that is reset each
time continuous mode is started. Value of the HostFrameCount can be queried or
manually reset through CPDIdev methods.
- Error code "level" field has been added to ePIErrorCode values.
A level of zero (0) is the highest level, indicating a failure of some sort. A
level of one (1) indicates a non-fatal condition.
- WM_PI_RAWDATA_WARNING Windows message added to report non-fatal
runtime conditions, such as sensor out of mapped area.
- Bugs fixed; see Bug Fixes v2.1.2
below.
|