|
Version 18.40 - October 2018 |
|
New Features |
|
| 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. |
|
Version 18.30 - September 2018 |
|
New Features |
|
| Maintenance Update | Consolidated update consisting of shared framework changes common to all AXWare Systems products. |
| Networking Status |
|
|
Enhancements |
|
| Announcer Window | Minor changes to Announcer window for more efficient loading of staged entries and runs for history. |
|
Bug Fixes |
|
| YEP Points | For normal events, running a YEP report would result in a blank list. |
|
Version 18.20 - April 2018 |
|
New Features |
|
|
Raw Time Standings for Pax Classes. |
To allow classes to be managed like Pax Classes but standings
based on raw times (like an open class), set the pax Factor for the Pax Class
= 1.000. Any other factor will force the
Pax Class to have standings based on factored times respectively. For Heat Assignments any Pax classes (and their entries) can be made to run with their base classes. |
|
Bug Fixes |
|
| Superclasses |
|
| Communication Buffering | Fixed a condition that appeared to spit out numerous times in a super fast sequence. This was a result of a data buffer issue in extremely rare conditions. |
| Pax Report | Pax Time report place the Pax time into the Total Time field due to a oversight introduced in v18.10 (Pax Time with Total). Work around was to create a new Pax Template to remove the Total Time and replace it with the Raw Time. |
| Pax and Raw time reports | Differential and From 1st have been fixed. They were reporting differentials from the class standings. |
|
Version 18.10 - Jan 2018 |
|
New Features |
|
| Live Timing Streaming |
New features have been added to Live Timing mostly in the Live Timing Streaming services
area. All event types are now
support including:
|
| AXWare ORM |
In support of AXWareTS and AXWareProTS, AXWare ORM has received many
enhancements that support the Live Streaming processes
|
|
Enhancements |
|
| Pax Time with Total |
|
| Best Pax Time | Announcer Window - Added Best Pax Time data to the history. |
|
Row Height Registration Staging Grids |
In order to provide more flexibility when selecting different Fonts, the
row height is can be adjusted to compensate for fonts that are fairly
large or tall. Pick a font, and
adjust the row height as necessary. To adjust the height, position your mouse between the left side heading (row column) on any row in the grid and drag it up or down to change the row height. |
|
Bug Fixes |
|
| Re-Classing |
|
| Class Header in Reports | Extra class heading could have been printed in HTML reports if the class break occurred at the page size (number of lines per page - which should have been ignored). |
| Announcer Window | If the Run History was set to the max (20 entries), a crash or hang could occur regardless of whether or not the announcer window was active. The Announcer Manager keeps a real-time account of entries and in this case it inadvertently caused a data error. |
| Networking | In the Synchronization stage, the HTML Style sheet was accidentally set to the Announcer Style sheet. |