Bug Fixes v3.0.0 |
- FIXED: (LATUS only) Display of installed markers produces strange message box and all installed markers not displayed if LATUS is in Throughput Mode. (In Throughput mode, LATUS only support marker frequences 1-8.) Now all installed markers are displayed, even if they are not M1-M8.
|
Bug Fixes v2.7.6 |
- FIXED: (FasTrak only) PiMgr sometimes crashes when starting Continuous Mode
after having previously STOPPED Continuous Mode by using the 'p' keyboard
shortcut or Single Frame toolbar button.
|
Bug Fixes v2.7.5 |
- FIXED: (FasTrak only) Avatars representing sensors "blink" when in
continuous mode
- FIXED: PiMgr installs in Windows Program Files (x86) area and is therefore
unable to create and write to LOG file unless run with Admin rights.
|
Bug Fixes v2.7.4 |
- FIXED: (G4 only) Avatars representing sensors on different hubs "blink" when in
continuous mode
- FIXED: (LATUS/Patriot Wireless) When 2nd marker is launched it does not always
appear as a new avatar in the graphics pane.
- FIXED: (G4 only) Motion recordings exported as TXT files have column data
delimited by null character instead of blank space.
|
Bug Fixes v2.7.3 |
- FIXED: (G4 only) G4Track.dll crashes when started and stopped without G4 hub
activation. Fixed by G4Track.dll v1.0.5.
|
Bug Fixes v2.7.2 |
- FIXED: Recording digitizer points saves buffer twice. Recording playback and export also have twice as many points as were recoreded.
- FIXED: PiMgr v2.7.1 does not parse Patriot WIRELESS P&O or configuration data.
- FIXED: In exported recording .csv files, Direction Cosine data missing some commas.
- FIXED: Changing output data list between recordings makes subsequent recording .tmots, .csv files unusable.
- FIXED: G4 Recordings with Quaternion do not playback or save quaternion data.
- FIXED: G4 Recording with multiple hubs duplicates frames between hubs and sensors.
- FIXED: Recording data displayed in Status Pane is garbled when station display above it changes. Can be corrected manually by resizing the Status pane or the PiMgr window.
- FIXED: G4 Recording: When recording stopped and played back, recorded frame
count displayed is more than actual frames recorded.
|
Bug Fixes v2.7.1 |
- FIXED: About.. dialog: installed drivers not listed on x64 systems.
- FIXED: G4 Sources are not displayed in graphics pane.
- FIXED: LATUS receptors numbered 10 or greater are not imported correctly.
- FIXED: LATUS/PatW Marker Boresight dialog unusable
- FIXED: FasTrak Automatic add of stylus flag when changing stylus mode adds
Liberty Stylus flag.
- FIXED: FasTrak sensor increment not applied to tracker
- FIXED: Filters OK/Apply creates error message even when successful.
|
Bug Fixes v2.6.4 |
- FIXED: Station Config dialog selection don't work correctly for wireless
trackers (LATUS/Patriot Wireless).
- FIXED: Tabs in Station- and Tracker Config dialogs don't update properly for
non-G4 trackers.
- FIXED: G4 Hub Filter settings not applied correctly.
- FIXED: G4 Sensor Increment settings not initialized correctly.
- FIXED: G4 Station- and Tracker Config dialogs do not use Apply-Dismiss paradigm
like other G4 dialogs do.
- FIXED: Text Command window will not open for legacy trackers; displays
"Collecting Data" dialog.
- FIXED: Units-sensitive configuration data in memory is not automatically
refreshed in new units of measure when units of measure are changed using the
Tracker Configuration dialog. Solution: Direct user to perform Sync-From-Device
after units have been changed. (Liberty/Patriot/LATUS/Patriot Wireless)
|
Bug Fixes v2.6.3 |
- FIXED: Changes to G4 output data not reflected in PiMgr data display.
|
Bug Fixes v2.6.2 |
- FIXED: Unable to connect to Liberty LATUS and/or Patriot Wireless.
|
Bug Fixes v2.5.0 |
- Erroneous “Collecting Data” dialog appears when
receptor is selected in Receptor Alignment dialog.
- Marker increment settings tab allows user to select
illegal values for position and attitude increment.
- Various settings fields require user to tab off or move
focus in order for value to be saved.
Values are now saved with each key press.
- Config file load and save functions fixed.
|
Bug Fixes v2.4.1 |
- Fixed Liberty LATUS™ Manual Launch functionality.
- Fixed PiMgr recording/playback functionality. PiMgr retains
entire recording session, not only the last minute's worth of data.
|
Bug Fixes v2.4.0 |
- Added xpthemes to installer to allow PiMgr to run on Win 2K.
|
Bug Fixes v2.3.0 |
- Liberty LATUS™ Receptor Alignment functionality repaired.
- Toolbar tooltips restored.
|
Bug Fixes v2.2.7 |
- When setting MinuteMan™
sensor-level configuration settings with the Station Configuration dialog,
memory violation occurs if All Sensors are selected.
|
Bug Fixes v2.2.6 |
- Liberty LATUS™ Receptor Alignment dialog malfunction.
|
Bug Fixes v2.2.5 |
- Sign error in Graphics source offset setting causes sensor
display error.
- When using airplane graphics image, image flashes during
continuous data collection.
|
Bug Fixes v2.2.3 |
- Corrected Context Sensitive Help linkage in Liberty LATUS™
Receptor Alignment sub-dialogs.
|
Bug Fixes v2.2.2 |
- Setting boresight for stylus in Point/Track mode sometimes leaves
PiMgr unable to collect single frame generated by stylus button. Then after
putting stylus back into marker mode, PiMgr can't get single frame or continuous
frames, but text command window does get P response.
- Boresight configuration: No way to apply boresight without
changing numbers.
- Set alignment: Modified flag gets stuck so next time station
configuration dialog is opened, alignment command gets sent again. Also, there
is no way to reset alignment.
- Export Motion Recording to .csv file is broken.
|
Bug Fixes v2.2.1 |
- Corrected potential for auto- or manually launched Liberty LATUS™
marker to be displayed as "Not Installed" even when it is installed.
|
Bug Fixes v2.1.1 |
- Improved real-time and recorded motion data display performance.
Uses system idle time to display data; doesn't hog Windows resources.
- Device->Device Configuration setting errors corrected.
- Device->Select Startup Configuration error corrected.
- Device->Device Configuration Source Mounting Frame type-in errors
corrected.
- Device->Device Configuration Filters doesn't lose previous
settings when filters disabled.
- Sensor out-of-map condition not treated like a runtime error:
does not stop continuous capture.
|