Version 16.70 - Nov 2016

New Features
Live Timing	Added the ability to provide Class Header Dividers into the Live Timing Results. As of v16.60, the headers were collapsed to reduce the amount of space it needed to scroll through them.  This mainly affected Heat and Non-structured Live Timing Results. Added ability to provide Headers and Footers to Live Timing to allow you to provide specific content as needed. The headers and footers are HTML files that must contain valid HTML syntax and format.
WEB Servers Updated ORM Membership Points Upload	Early in Oct 2016 our web servers were updated and minor side affects resulted that require minor changes to our upload processes, mainly for Membership Points and other FTP functions from within the AXWareTS software. In support of the new web servers and the update requirements this and newer versions must be used to provide ORM integration for Membership control. In the meantime, upload Membership Results must be done from within ORM if older versions are being used and the Uploads fail.
Reset Timer And Reset Finish	Consolidated the processing of both the Reset Timer (Reset Start) and Reset Finish functions into the main timing loop. This also affects the OFF and STOP button functions in the Staging Grid and provides a safer and consolidate approach to handling these processes.
Enhancements
Live Timing	If uploading Live Results to ORM, and an HTTPS error occurred in the background, the uploads would stop. To get the uploads to start working again, Upload button had to be cycled to force the process to reset. added Live Timing Scheduling info to the Headers
Process Management	several processes have been improved to provide more balanced data control (this is all internal). This included adding Reset Timer and Reset Finish management into the timing process to force it to be more inline with other timing controls.

Bug Fixes
Edit Entries	A overzealous validation would not pop up an entry for editing. As a workaround, Registrations had to be edited in place in the grid.
Reset Finish	In rare instances the Reset Finish could cause the Timer management to Halt. This exhibits itself as a non-responsive keyboard or application.  Structural changes have been implement to manage the Reset within the timing process to provide safer control.
Time Slips	The time slip was forced be a MMSSFFF format and if the options were SSFFF the time was not printed but "Time:" was.  This version fixes that and supports the MMSSFFF format as well as the prior SSFFF format.

Version 16.60 - Oct 2016

New Features
NCCC Points	Update to 2016 NCCC Rules. Updated Exhibit class points accumulation Updated Points allocations for Race Points and in support of Excluded and Non-points classes.
Live Results	Live Results now can optionally contain real time Run History for up to 10 most recent runs.  This option is set the Live Timing setup dialog allowing you to set the History ON or OFF.  Once ON, both the Structured, and File Based results will contain the summary.  The History contains various items from the staging entry including real-time standings, differentials and real time class position, pax and raw positions, and pax time (if so configured). Enhanced HTML and style sheet features enhance the look and feel of Live Timing and reduces that amount of data to scroll throw. Various Format changes to Live Results to reduce any extra spaces - this drastically helps viewing Live Results from Smart Devices and smaller screens. Excluded classes are automatically included during Live Timing, but are not included in the official results (as per the definition of the setting). Heat Based Live Timing now provides a Home Page and explicit Heat Pages that each contain the respective classes running in them. Pax Classes - Spanning Heats - For Live Timing and Heat style output, the list of classes per heat now includes any Pax Classes that Span across heats. Spanning Pax classes run in heats where the their base class runs.
NCCC Live Timing Support NEW	Major changes have been made to provide the same live timing support as for non-NCCC versions. Prior to this, several of the components although active were not 100% in place. Classes with slashes and other non-valid characters for WEB content (as well as file naming conventions) are now supported by stripping these characters from the Class names.  Ex: 1SC/D, is reduced to 1SCD for web and file naming conventions during Live Timing (very important for uploading to WEB servers).
Active Heat	The active heat is now saved with the event and reset to the last selected heat when the event is reloaded. This provides more consistent heat control and reduces the numbers of items that the T&S person must reset if or when the event is loaded.  As a side note, this was done to force the proper heat when Live Timing is active.
Enhancements
Announcer Window	Template was modified to force History to have the Total Time show up before the Best Time.  This can be modified by Print Templates, we decided the new order was a better default. If you have a Custom Template for Announcer History, your display will not be affected. The Announcer Window is first started, it is now pre-loaded with the configured number of staged entries (On Deck) and the last set of runs (Run History). Prior to this, the Announcer window would load as runs were logged.  However if the announcer window was stopped and re-started, it would remain blank until runs started coming in again.
Staging - Penalty Edits	When penalties were update for prior runs, the differentials and stats in the staging grid were update manually using the (Re-Accept Entry's Runs - staging function). This is no longer necessary and all consecutive runs are re-consolidate and update  respectively. This helps keep the Announcer Window and Live Timing also synchronized based on any updates.
Live Results	Improved the switching of Live Results formats in real-time. This includes switching from Heat based to Full Live Results generation.
Report Formats	Many updates to the Style Sheets have been carried out to improve content formatting, readability, and moving towards updated HTML rules. Formats and Colors for Reports has changed (style sheet changes). Includes normal reports and Live Timing. Updates to exiting style sheets (all report*.css files) were made and several new css files were added (black and grey versions). Many existing colors were altered to provide a more consistent format. To make use of these formats execute the File/Create New Data Folder and press <enter>. All style sheets will be copied to your working data folder. You can copy them manually if desire by copying them from <install folder>\reports*.css to your <data folder>.

Bug Fixes
Event Run Statistics	The First and Last car time is based on local time and supports DST. Minor display fix times between noon and 1pm (12:00 and 12:59.59). Printing Run Statistics ignore the Heat columns. They were displays proper but ignored for printing.
Announcer Window on Clients (Announcer & Audit)	It was possible for the On Deck list to become out of synch after a long disconnect from the T&S server while timing continued.  Workaround: restarting the client and reconnecting to the T&S server to force a complete refresh. This is no longer necessary.
Announcer Window	The Pax and Raw Positions were not being invoked in the History section of the Announcer Screen.
Live Timing Results	Certain Live Timing Results cache and copy the results to the configured destination.  When Live Timing Results are being generated, a sharing violation could occur due to external circumstances. If this occurs, Live Timing Results would fail to updated and would therefore not stay current. An attempt to by pass this issue has been put into place but may still fail if these files are being opened and manipulated by external processes (3rd party apps, editors etc). In this case, Live Timing will still not be able to update. If you have 3rd party or other applications using any of the Live Timing Result data files - the effectiveness and real-time nature is significantly affected and will result in failures. Note: Browsers and web servers (local hotspots) are not affected.
Print Templates	When Total Time column was set to print before the Runs, the Live Timing Class results would leave out Run 1 from the Results, especially when the runs were split across multiple rows (Number of Runs per row - Report Options).
Live Timing	It was possible for Live Timing to suspend itself if the Settings were altered at an exact time.  The Live Timing Printing process would appear to wait on the settings to complete but that may in rare circumstances never occur. The only way to fix that was to save the Event, stop Live Timing,  Close the Event, and reload the event and restart Live Timing. This reset all print jobs.

Version 16.50 - August 2016

New Features
AXWareStaging Android App	Many enhancements to the AXWareStaging App including a scrollable list of prior staged vehicles, Passcode for security when connecting to the T&S Server, slightly larger stage buttons and better management of connections. Note: AXWareStaging v2.3 - requires Networking Module
Re-accepting Staging Data	To provide improved feedback on when the re-accept is running, a status window will not pop up during this process. It is recommended that you wait until the status window disappears before trying to execute other actions (the software does not prevent you from doing other tasks - event though some may affect data and potentially the re-accept process).
Enhancements
Segment Timing	Auto-reset for Segment Threshold times when switching heats. This clears the prior running average times that were recorded for each segment allowing the software to validate or invalidate times based on the threshold settings. Lows and highs are set to negative values. Segment times are now managed following a Reset Finish.  Although not used all too often, prior versions ignore segment times when a Reset Finish was carried out.
Delete Bogus entries	In cases where garbage data is somehow loaded into the registration grid, there is no easy way to remove it. Minor fix to allow such deletions but requires you to be in Non-Unique car number mode so that bad data cannot be ignored.
NCCC Worker Points Table	Prior to this version the worker points table, when loaded was limited to 25 workers.  This is no longer the case and the table is no unlimited. The Work Table has been extended to split the Worker names (first + last), with the additional data columns for Travel, Total and Remarks.
Clarification - Class Definitions	Spaces are not valid characters for Classes.  As such if you have spaces in your class definitions and have registered entries (or membership entries), it is recommended to edit your classes and update your registrations/membership lists accordingly.  When spaces are found, a warning will be displayed but removal of them is left up to you.  Please modify your classes and lists accordingly. Some features of the software will not function properly if spaces are part of the Class definitions.
Segment Timing	If the number of segments was altered in an existing event, the T-Link Status dialog did not reflect the change in the number of units displayed. The T-LINK Status dialog now resets and refreshes with the configured number of sectors. Improved warning messages indicating statuses of T-LINKS that are not configured within the software but are active. For ex: if unit B is actually configured as C, and no segment are configured, a a warning is displayed in the status dialog as well as the staging status window.
Networking Staging Grid Updates	Staging grid ignored statistics for entrants that exceeded the number of configured runs. This is no longer that case  in order to keep things consistent.  Side Affect: also affects updating the Announcer Window if it's active.
Announcer Window	Prior to this version, the Announcer window would not display non-registered entrants - this is no longer the case. Network Clients ignored runs that exceeded the max configured runs - this is no longer the case. Off penalty was ignored on the T&S and clients.
AXWareDM	Added Font selection options akin to AXWareTS for the grids and status windows.

Bug Fixes
NCCC	Insert New Entry would show a Standing Grid busy on inserting new drivers.  Enter a car number in staging could times pop up a warning about non-registered entry. This would occur if no open entry exists and the software attempt to verify if a ladies entry exists.  In any case, the entry was stage and the error should be ignored.
Tie Breakers	Tie breakers are automatically handled by AXWareTS by -0.001 from the Total Time for the entry with the 2nd faster run (it's the faster entry).  However, if the tie is found when sorting on Pax or generating a Pax Report, the adjustment is made an the standings are auto-resorted by Total Time (thus resulting in an incorrect Pax Order).
Deleting Registrations or Members	If a space was found in the class field, the entry would not delete.  Spaces are not valid characters in the class field and should not be used. Classes like "CAM S" should in fact be "CAMS" and similar.  Hyphens can be substitutes, ex: "CAM-S".
Networking T&S Server Class Definitions	It was possible for the class definitions to be pointing to the wrong data folder when creating events one machine and moving them to another.  The data folder retained the old location while the status windows showed the proper location, resulting in potentially no class definitions. This error appeared when connecting a client to the T&S Server.  An error stating no class definitions were found (empty class def file was synchronized).  Work around was to re-load the Class Definitions on the Timing Server and reconnect the Clients.
AXWareDM load settings	When AXWareDM is started it always reported that the program settings needed to be updated but this was not the case.

Version 16.40 - June 2016

New Features
Networking	The work assignments were not part of the synchronization process when connecting to the T&S Server and have been added to the mix.
Enhancements

Bug Fixes
Insert/Edit Registration Entry	The reclass function was not working from inside the Insert/Edit Registration dialog. The original class was missing from the function invocation and thus nothing appeared to happen.
Networking Standing Grid Busy Message	The sort manager incorrectly set it's state when a reclass, insert or delete was received from another client (or the T&S server). This caused several sort warning messages.  Although data was not affected, it slowed down the interface during this state.  Adjustments have been put in place to properly set the sort state and eliminate the interface 'slow-down' which looks very close to a hang condition/

Version 16.30 - May 2016

New Features

Enhancements

Bug Fixes
Start New Event 2 Day Events	When creating 2 day events, an error stating that a file was not found was reported but should not have been. It did not impact any processing or data.
Sending times to a Display on Networking Clients	Times were not sent to a Display on Network Client - the display flag was inherently always OFF.
Staging Busy Message	A validation and safety check was put in place in v16.20 that would report a "Staging Busy" message over zealously. It did not impact data, but intrusively displayed the error repeated.

Version 16.20 - April 2016

New Features
Enhancements
Networking	Revamped Caching control provides improved data exchanges for newly connected clients as well as any cached data that is pending to be sent to and from the T&S and client respectively. T&S Caching mechanism was enhanced  to support unhealthy connections (frequent disconnects). The T&S cache provides updates for the client while the client cache provides updates to the T&S server as appropriate.  Prior versions required some data exchanges before the caches were exchanged between the client and T&S Server to start the data exchange. As of this version, the exchanges are forced when a new connection is detected, thus updating the data between the networking computers immediately. NEW - A Passcode (password) is not necessary for allowing the AXWareStaging App to connect securely. Requires AXWareStaging App update to the latest version to provide this feature.  Prior versions did not use a passcode. You can leave the password blank in AXWareTS to support older versions of the AXWareStaging App Clarification: Editing penalties in real-time by a Networking Client should be carried out by the AXWareDM penalty manager. It is designed to only deal with penalties...thus reducing any potential data manipulations (unlike the Audit Client which has access to the entire data set). NEW Behavior for Networking Clients: You now have the ability to force a auto-reconnect that will try to connect to the T&S Server whenever a disconnect occurs.   The auto-connect is configured the first time a disconnect occurs. When/If this happens check the Auto-Connect check box and press Connect. After that, any further disconnects will pop up the Reconnect Dialog and will automatically try to connect.  No buttons will need to be pressed.  Press Cancel to terminate the re-connect process. To inform you of disconnects, the Reconnect Dialog will always pop up and show you that it trying to reconnect is in progress. If a Manual Disconnect is done, the auto-connect is turned OFF.
Bumping Class	New function to Un-bump entire class where entries are placed into their original classes
Import Registrations Overwrite	New setting that allows overwriting existing entries during the import based on matched class+number+driver name.  When a match is found, the rest of the data fields are overwritten. The default import process ignores existing entries so that original data is retained.  Also the merge import was a partial overwrite where only blank fields were updated allowing you to carry out step style imports to modify fields accordingly. This setting is sticky...meaning when ON, it will do Update/Overwrites for all imports.
Sorting Processes	The sort process has been modified to provide better process management.  In addition we have added a feature that notifies the user if the sort process is taking too long (this should normally never happen) but if it does, the sorting is aborted and the program will continue normally. Tie breakers - restating - when ties occur (based on Total Time) the 2nd fastest run will be used to decide the tie breaker by adjust the faster cars Total Time by -0.001 so that the sort processes act easily on the data set.  Refer to the Help Doc for more details. The adjustment also prevents the system from having to 'check' ties continually...thus improving performance.   Additionally - the Tie breaker process has been been reorganized, placed in a safer controlled process and greatly sped up when it sparks off.

Bug Fixes
Networking	If you are using the AXWare DM (penalty manager), the staging grids on announcer clients was not being updated when penalty changes were not always reflected.  As a result, the penalties on Announcer and Audit Clients had unofficial penalties. Fixed conditions when Connecting to the T&S server and some information was left blank but was actually required during the Synchronization process. Items such as event name, style sheets etc. should have been provided but the validate on prior versions was sparse. In some cases, cached items could be flagged as completed when in fact a disconnect may have occurred during sending of cached data. This was more apparent on poor connections when disconnects could occur was quickly as a client was connected.  Audit Client - when Timing data is exchanged between the T&S Server and Audit client that includes running timer information. However this caused a small thrash/overwrite condition that could on some systems overwrite updated data on the T&S computer due to the propagation of the running timer information from the Audit client back to the Timing server, especially if penalties were modified on the Audit Client at exactly the same time Timing data rolled into the T&S Server.  This running timer information should have been ignored and it now is. Audit Client and T&S Server: Overwritten staged entries are now properly updated if a different entry is entered into an existing staged entry, the runs may not be cleared for the 'old' entry and run numbers were not updated in the staging grid.  This was usually corrected on the T&S server by simply continuing runs however, if the edit was carried out many rows above the current timing rows, the run numbers may not have been updated correctly. Automated synchronization requests could be forced inappropriately from the Audit Client. Resulting in multiple redundant exchanges.  This was seen in extreme conditions only or when penalties were being entered for cars on course.  Editing penalties in real-time penalty should be best carried out by the AXWareDM penalty manager.
Membership File	If deleting entries via the Membership Grid View via delete selected entry - the program may crash due to a unchecked list parameter.
Insert New Entry/Edit Entry	With Unique Car Numbers active, a unique car number check was over zealous in some cases, incorrectly reporting that an entry already exists.  Special condition - if ALL entries are bumped or pax entries, the a unique car number could be missed and reported as non-existing.
Final Report	If Bumping is ON and a past event is loaded, the final report may skip some entries in pax classes in the final report.
Bumping Class	Bumped entries were automatically placed into the Class Tree View regardless whether the entry was Registered or not.
Class Tree View Tooltips	We found a overwrite condition that could cause the application to terminate abruptly (critical crash). The condition surfaced when very long driver, color and car descriptions were being used.  The overwrite was due to a limit in the Windows Tool Tip object.
AXWareDM and Audit Client	If the audit client was active, and the Audit Client entered a penalty for a vehicle, the AXWareDM would not see it.  Although this should not affect the data it was not correct and now the data flows as expected.
AXWareDM - NCCC	The NCCC Versions popped up a Warning message about AXWareTS not being installed properly.  This has been corrected.
AXWareDM	If the Penalty Manager  entered a ReRun  for a run, the run number was not adjusted on the T&S Server.

Version 16.10 - Jan 2016

New Features
**** NEW **** Introduction of the DM Manager (Distributed Module Manager)	Starting with v16.x a new Networking Client is being introduced that provides Distributed Management (DM Manager).  Currently the DM Manager consists of a Penalty Manager Client allowing you to manage penalties from a computer other than the T&S Timing Server/Timing Computer.  The Penalty Manager obtain the staging sequence and other pertinent data and provides direct controls designed for quick and easy penalty data entry. Explicit control of up to 6 corner stations is provided allowing you to track penalties on a per corner basis with reporting features for audit control and management. Penalties are consolidated for each corner and sent to the T&S Server.  Data entry can be entered by the keyboard (normal data entry) or extended with our Android application for a seamless integration using WIFI communications. The DM Manager allows up to 6 Corner Stations to connect via AXWareTS Corner Android application.  This application provides sequencing of cars on course with explicit and direct penalty entry via simply button clicks.  Cars are scrolled in a sequence as they are staged and when they exit the course.  The sequencing is managed automatically with the running cars always at the top of a List for quick view and access.  Buttons support your club's penalty definitions and include Dnf's, Reruns, Off Course (broken cars), and 1-6 cone counts, and include a CLN (Clean Run) button. The buttons send the penalty immediately to the DM Manager which in turn sends the compiled penalties from all corners to the T&S Server.  The exchange is extremely fast and and provides penalty control real-time. AXWareTS Corners requires a PassCode to be entered for the event, set by the DM Manager during setup. This provides a password like access for security purposes. A new password should be provided for each event or as necessary. Uses fast and reliable TCP communications over extended WIFI networks.  The networks you provide will determine range and WIFI reliability. AXWare Systems will provide some recommendations for WIFI configurations.
Enhancements
TTOD for 2 day events	TTOD reports have been expanded to provide TTOD for both days regardless of which day is currently active.   Prior versions only provided TTOD of the active day.
Pax and Raw Time Reports	By design prior versions did not reset the Pax & Raw report position when exclusions or certain report settings affected the actually order. This was done to provide a visual feedback about other vehicles being left out of the report (albeit, some find this confusing).  Now the positions are sequenced in order regardless of exclusions and report options. If the 1st car of the report was an excluded entry or an entry that dropped off the report due to report options, the differential columns did not reset to start with a 0.000 diff on the first car (again this was to provide some visual feedback that other cars were quicker).  This too is no longer the case and the 1st car in the report based on the settings now starts with the appropriate 0.000 differential times.
Announcer Window - History section	Added Best Time as another default data column in the History section to provide more information to the announcer.  Prior to this the Best Time had to be added to the Announcer Window (History) section explicitly.
File/Recent File List	Due to the introduction of the AXWareDM components, the NCCC versions and the normal AXWareTS application, we have split the recent file list into individual their distinct products.  In prior versions the recent file list was shared.

Bug Fixes
Pax Report and Bump Classes	For bumped classes under Pax control, the Raw Time is now displayed in the Total column. Prior versions only displayed raw time in the Total  Column for Pax classes explicitly.
Timing Ties	Breaking a Tie is automatically handled by using the 2nd fastest run of each entry to break the tie. The faster vehicle will get a time that is auto-adjusted by subtracted 1/1000th from their fast time.  This keeps the data and pax data intact. Prior to this version the Pax time was improperly updated when the tie was updated. It used the raw time, which was not correct.

Prior: Release Notes: version 15.x