|
Version 19.40 - September 2019 |
|
New Features |
|
|
Enhancements |
|
| Recovery |
If networking was active the Recovery process File/Recover Staging or
File/Recover Registrations should not be executed due to the amount of
work these operation perform. Prior to this version, we had not
de-activated the recover processes when Networking was active. In this
version, we require Networking to be OFF. Once the recover is complete, save the
event and then re-connect any clients.
Note: this should not be a likely process however, since recovery should be a rare issue (battery dies on laptop, power glitch etc). |
| Live Timing w/Heats |
|
|
Bug Fixes |
|
| AXWareDM & Live Timing | When penalties were added via the AXWareDM Penalty manager, after a run was completed the Live Timing push would not occur with the new penalty. |
|
Version 19.30 - May 2019 |
|
New Features |
|
|
Enhancements |
|
| AC4, 5432EW | Buffer manager has been improved to strip 'junk' from RS232 communications to improve transmissions. It was possible v19.1-19.20 to ignore data due to garbage introduced into the data stream. v19.30+ strips garbage in transmissions and provides enhanced data reliability. |
| Reclassing Registrations |
When reclassing entries the focus is now set to the updated entry.
Note: If networking is in affect the Disable Auto Sort will dictate if the entry list is resorted on the active sort field (active column). |
| T-LINK |
Note: Timing Simulation Mode is strictly for training purposes....and must be off during the event. |
| Status Logging | Minor changes to logging manager to help reduce size of logs and remove extraneous newlines and carriage returns (data dependent). |
|
Bug Fixes |
|
|
JAC Chronotimer mode |
JAC Chronotimer mode was deactivated back in v18 at some point but is now back in action. |
|
Version 19.20 - April 2019 |
|
New Features |
|
| General Release | General maintenance release. |
|
Enhancements |
|
|
Bug Fixes |
|
| JA Circuits | Minor Data protocol handling changes. Mid 2018, comm management was modified and as a consequence data management for JAC could ignore 1st trip and record the 2nd. |
| Timing Triggers |
For timers with individual Start and Finish triggers, the 1st time
may or may not pop into the Staging Grid due to an un-initialized
item. Running Multiple times resets that and functions
appropriately.
This is most apparent when the staging grid is totally blank. A T-1 will remain in the 1st row of the grid without a finish time recorded. Once a few times are processed, it will catch up, but not on the first test run. |
|
Version 19.10 - January 2019 |
|
New Features |
|
| Seasonal Base Release | Initial release for 2019 |
| COM ports | Modified the way we look for and list available COM ports. In some cases, this will show ports that are not 100% registered with Windows as per the requirements. We still recommend the FTDI chip set if possible. Such devices are well known, offer excellent performance and support the new Windows OS's. |
|
Enhancements |
|
| Pax Time Report | If the Print Pax with Total option was selected the Raw time was evident for pax classes. With this release the Pax Time + Raw Time is shown if this option is ON. |
| Live Streaming | The Streaming Reset and Catch up features have been tuned to better handle instances where Live Timing was turned OFF then ON and when events are re-loaded and Live Streaming restarted. Prior to this a auto-clear may have been executed when Live Streaming and thus cleared prior streamed data. A quick fix for this issue was to force a Streaming Reset and then accept the last row of the staging grid. This forced all rows to be pushed automatically. With v18.40+ this is no longer necessary. |
| COM Crash | If you have Thresholds set for false triggering detection and NOT using T-LINKS, v18.x could potentially control a COM crash and force you to exit the application. |
| Print Final as Text | Final results ignored the 'class' field intentionally in prior versions. It is not printed in all cases. |