| Version 15.70 - August 2015 - Maintenance Update |
|
Enhancements |
|
|
NEW AXWareStaging |
This version introduces our first of many AXWare DM (Distributed
Management) components that allow you to more easily manage and control
your events. These are all based on Android devices as explicit timing
hardware components. AXWareStaging: is a staging app that allows you to easily and quickly stage vehicles on the T&S computer. Very much akin to a bar code scanner but with simplicity in mind, the app loads the registration list from the T&S computer and stages entries with 1 button click. The app displays the Registration List in Class or Car Number order and allows you to easily scroll, view and stage entries, all while supporting your class structure. Clear and concise. This is the first of several AXWare DM Android based applications
that will provide additional timing and scoring functionality. Prerequisites: Networking Module for AXWareTS and a high performance WIFI Router (with optional AP for extending the range). |
| * NEW * Print Options Reports |
|
| Updated GUI Framework | GUI framework was updated to revision 24.2 |
| Networking |
|
| Staging - Auto-insert | Improved performance for the auto-insert process which is only used if the 'non-registered' entry is to be registered as it is entered in the staging grid. Note: this function should only be executed if you know for certain that entry needs to be Registered. This Quick/short hand function is used to reduce event slow downs. Once Registered, data will be consolidated normally. Use the Registration Edit functions to update the driver's name and other data as necessary. |
| Event Loading |
Enhanced start up process to inform you of any problems with the Class
Definitions or other files during the Load process. You may see warnings when the Class definition file does not contain any classes (class file was not found). In such a case the system will attempt to define classes based on the classes found in the Registration list and as a result Pax or Bump entries will not be managed as intended. This affects differentials and any statistics recorded for any existing runs. The issues should be fixed prior to continuing any data edits. |
| Results Upload to ORM |
|
| Final Results | Due to popular demand the headings for any reports that display the run times now display as "Run #". For reports that span the times across multiple rows, the report will contain "Run #..". |
| Event and Membership Settings | Several settings were saved in the registry but not necessarily in the Event or Membership File. This has been remedied and should reduce the need to reset some settings when files are moved between machines. |
| Live Timing Options |
|
|
Bug Fixes |
|
| Staging - Delete Row |
The Delete Row function removes a row completely from the Staging Grid
however it posed problems when deleting a row with Actively Timer
running (for timers with individual starts and finishs). It would
in force the next time 1 row above the deleted row. Now the
system will NOT allow you to delete rows on which active timing is
running. In fact, the Delete Row should almost never be used since
it alters the timing sequence and log.
|
|
Networking & Staging - Move Up |
When in Networking the last row of the staging grid was update correctly on the machine being edited, but was not correctly updated on any networked machines. This left a stale (duplicate) entry in the last row of the staging grid on the other machines. Entering a new entry on the Server (or Audit Client) on that row would updated the entries appropriately. |
| Staging - Delete Row | Deleting the last blank row is no longer permitted. The Staging Grid should always contain 1 blank row as the data entry row. |
| Logging Manager | Fixed an overrun condition in the Log manager that could potentially overwrite some logging data. Fast processors could see this condition in rare cases...albeit, it is a behind the scenes condition. |
| Version 15.60 - July 2015 - Maintenance Update |
|
Enhancements |
|
| Check For Updates | Using Check For Updates will now allow you to re-install Base Versions of the product whenever necessary. This will make future Base Installations easier and not requiring using the Control Panel. |
|
Insert New Entry & Networking Updates during |
Due to the increased performance of the Networking, some modifications were
necessary to the Insert/Edit entry dialog. In prior versions when networking
was active, networking updates were delayed by design resulting in
potential class & number conflicts.
Now network updates are managed quickly, and entries are validated prior to saving (registering/modifying the entry). In addition in order to provide a 'faster' and more robust class & number reservation, when the "Avail #" button is pressed is or your focus changes off of the car number, that entry is immediately reserved. This allows the networking management to properly exchange this information, retaining entry lists, bar codes in real time. |
|
Bug Fixes |
|
| Time Slip Printing | If delayed printing was being used, there were conditions that could force the Time Slip print process to sleep for a very long time making it appear as if it was not working (it was but just would not wake up for a many hours). |
| Membership Card Printing | When printing on sheet fed cards (Avery 8873 style) prior versions ignored the page break. It appeared that the only the 1st page was printed while in fact it printed into non-paper space (which was ignored). From this version onwards, correct paging control is in place (10 cards per page). |
|
Memberships and Bar Code Support |
|
| Car Numbers | If using post-fixed letters for car numbers, staging entries could at times not find the vehicle due to a casing mismatch. This only occurred if "Use Upper Case for Classes" was NOT selected. Car Numbers with letters are now always upper case. Ex: 23A, 46B etc. |
| Network Name on Clients |
|
| Version 15.50 - May 2015 - Critical & Maintenance Update |
|
Enhancements |
|
| Networking |
|
| Loading Events and Heat Assignments | Particularly for Heats by Class (default) - classes not assigned to a heat are summarized following the loading of the event, in the Registration Log. |
| Insert New Registration | Prior to this version, if a different class was selected when the New Registration Dialog popped up, the first entry in that class was auto-filled in. This required either clearing entry or setting the auto-clear ON. This is no longer required. If the car number if blank...any class can be selected without auto-filling the dialog. |
| Time Splits | Added Event Date which was missing although could be substituted with "Today's Date" during the event. |
|
Bug Fixes |
|
|
Changing Number of |
|
|
Network Client & |
Display control was inadvertently left de-activated on Networking Clients. All but the Registration Clients can configure and use Displays to help distribute resources and offer flexibility in your setup. |
| Re-Accepting Staging Data | When re-accepting staging data, slower machines or large numbers of runs can result in a 'busy' state and the re-accept will prematurely abort itself. This was a result of a too short of a timeout interval. |
| Log Manager | The logging processes have inherently been tasked with more work and as a result a potential crash condition was found. This condition was eliminated and should provide for a more robust system. |
| Version 15.40 - April 2015 - "Critical" |
|
Enhancements |
|
| GUI Frame work update |
|
| Timing Processing | Enhanced timing data management to improve processing speed. Data itself is not affected. |
| Time Slips |
|
| TCPIP Server Address |
Since DHCP can assign a different address to your machine, the IP Address
is always reset when the software is started. You may still override the
address using the Networking/Server IP address option or by pressing the
Server IP button on the Registration window. This is only important to the Timing Server since it must contain the existing IP for clients to connect to it. The IP Address that is shown in the Server IP button must be used on all Networking Clients. |
| Print Templates (empty files) | Not a normal or common issue, however if a template file is empty (no column selections) the report will either contain no data or minimal depending on the type of report being generated. This version will default to the built in templates if this condition occurs. |
|
Bug Fixes |
|
| GUI Sound Control | We found a major application error in the GUI Framework that has been there for a considerable amount of time (many versions). The sound process manager could randomly cause the application to crash but the cause is unknown nor do we have a viable fix. Thus the GUI sound manager is permanently turned OFF (disabled). This does not in any way affect normal application sounds. Note: we did not explicitly use the GUI sound manager. It was an inherited function of the framework supporting menus. |
| Networking - Audit Client |
|
|
***Critical *** |
A potential random crash may occur on certain installations due to the Logging Manager. The speed of your computer (due to disc access and speed of peripherals) and additional processes being active (Networking, logging options etc) may play a small role in this condition. Faster processes have a better chance of never seeing this condition at all while the slower machines may exhibit random Access Violations. |
|
Clarification |
NOTE: the Access Violations dialog is a error dialog that a replacement for the general Windows General Failure dialogue but has no additional function. It's strictly a indicator of a program crash. The fact that it is displayed indicates a software problem that can be anything from a software defect to a driver crash, settings issue, disc issues, memory issues, most anything. It's strictly there to indicate the problem. If you see this dialog, please contact AXWare Systems. |
| Print Templates |
|
| Display Output | An overrun condition was detected on an internal communications buffer for the Display output. Although this condition is rare, it was evident when using the Verbose and Wireless options. This condition occurred when data was buffered but the system was processing other items before sending it out. The overrun condition could result in a program crash. |
| Time Slip Printing | If the print settings, including Fonts has been changed when time slip printing was active, the program may crash due to special column handling. |
|
Version 15.30 - Mar 2015 -
|
|
Enhancements |
|
| Announcer Window |
|
| ORM Uploads |
|
| Live Timing - Live By Class Template | We exposed the Live By Class Template which is responsible for the content of Class based report pages when using Live Timing Structured configuration. |
| Networking | Improved synchronization management for Networking clients especially when clients are turned on and off on the numerous times, either on the same machine or different machines. |
| Edit Insert or Copy Insert | Improved handling of entries when Unique Car Numbers is active. In particular when Unique Car Numbers is ON doing a Copy and Insert will no longer auto-clear the entry when a new car is selected. It is left up to you to Clear the Entry if desired. The 'Copy' function allows you to Co-driver and multi driver entries. |
|
Bug Fixes |
|
| Points & Membership Files | Fixed a problem for missing membership files and running Points Update. The Points Update does a better job in verifying if the specified membership file exists...if not, it pops up an error. |
| Networking |
|
| Edit Insert or Copy Insert | If unique car numbers is active, it is possible for a duplicate entry to be created. |
| Version 15.20 - Feb 2015 |
|
Enhancements |
|
| Announcer Window |
|
|
Bug Fixes |
|
| Pax Super Class | Pax Super Classes were accidentally ignored in the last few versions (since 14.60). Non-paxed super classes were unaffected. |
| Time Slips | Printing Time slips on Networking Clients printed 2 labels per entry. The first was printed when the time started for a vehicle (for timers with individual start & finish management). |
| Version 15.10 - Jan 2015 |
|
Enhancements |
|
| COM Port Management |
We have taken strides in providing more robust COM interface
management to eliminate potential crashes relating to USB and COM port
instabilities.
In part the fatal crashes that may occur in Windows (due to driver crashes) is now being captured. As a result the software has improved control over fatal errors and can controllably exit and save the data as needed, when possible. NOTE: it is very important to understand Windows configurations and how USB drivers impact it. It is not possible to recover from all fatal driver errors however and the use of quality USB devices and drivers is highly recommended for overall performance. Please use USB RS232 devices designed your particular Windows OS version. Windows 7 and 8.x now require updated and certified devices. Older devices that work on XP or earlier OS's, may or may not function as expected and are grounds for crashes. Please visit our forum for USB information. BSOD (Blue screens): If you experience BSOD, those are attributed to low level driver or core component crashes within the Windows OS (not AXWareTS). BSOD must be fixed before you can declare your configuration stable or continued crashes will occur at random times. |
| Error Management |
Due to the various configurations for Windows machines and the different OS
configurations and versions, we are introducing improved critical and
fatal error management (Windows crashes and exceptions).
Due to the nature of some of these errors, the software will attempt to save data whenever possible, but there are conditions where the software is unable do so however. A major source of instability issues has been in the qualify of USB COM drivers that some of our users are using. As a result we are trying to control fatal conditions and doing our best to recover quickly and easily from such problems. |
|
Opening/Closing COM Ports |
In prior versions, opening and closing COM ports (Timer, Display and even Scanner ports), could result in a crash when done in quick succession. We have enhanced the COM handler so this no longer occurs. |
| Time Slips | Minor enhancements to force use of entire label for time slip printing. Prior to this, the time slip was offset 1 letter to the right and 1 row down. |
|
Bug Fixes |
|
Prior: Release Notes: version 14.x