Bug Report - Tag Read file can be incomplete

[Ted Finch]

I have noticed that at recent events the Tag Read file can be incomplete. 

Chip times are recorded as expected but not all read data appears in the Tag Read file.

Has any one else experienced this?

Cheers

Ted

Keep it Simple Timing.

[Brian Agee]

I know this was reported shortly after the 6.6 update was released, but was fixed with a later release. When you click on the "Help" menu what file version does it show? If you're not running 1.6.6.4 then update the software and I believe that should help.

[Steve Hudson]

Used latest 1.6.6.5 together with last years version - as separate results - and both worked 100% chip starts and 100% finish. All Live Export and all Tag records written to respective data files. All's worked brilliantly, thanks Brian.

[Raphael Leal]

Version 1.6.6.7 when trying to import tagreads file.

[Brian Agee]

I had that same error when I was timing a race a couple of weeks ago that had a few thousand reads. If it's an emergency right now to import this then I can give you access to the 6.7 Beta version that I plan to push out Monday. This new version has a complete overhaul on how it handles database connections to help ensure two processes are not trying to write to the database at the same time (causing a malformed, corrupt, or locked database). This update has significant enhancements in many other areas too, so I'm looking forward to pushing it out.

Here is a preview of what's included so far with version 6.7:

• Enhancements:
  • Implemented security update for RunSignUp, which they will push out early next week. So this is another required update for everyone when they push that out.
  • Totally restructured how the system handles database commands that alter data in the database so that there is no chance of two separate processes trying to write to the database at the same time.
  • Added a "Tag Read Simulator" feature that allows you to "pressure test" your system by flooding random tag reads in as fast as one every 100th of a second. This feature is only available if it's NOT race day.
  • Improved efficiency when handling a flood of tag reads coming in at the same time.
  • When pulling in multiple races or performing a participant "Sync" for multiple races, the software will now remember the highest bib # assigned and use that as the starting bib # for the next race as it's importing the data.
  • Added the ability to CTRL+V the license key into the screen that prompts for a key.
  • Updated process that checks for internet access to a more modern approach, which should improve speed and reliability.
  • Added option to do a Partial or Full sync with RunSignUp. Partial syncs only pull participant records that have been updated since the last sync.
  • Added ability to import chip start times without having to start the race or mark it as "capturing chip start times".
  • Added back ability to manually enter chip start times as people take off, this is useful for Stair Climb races or other events where one or two people start at a time. Basically the checkbox for "Capture Chip Start" and "Capture Chip Finishes" are now visible at all times, not just if you have a reader added in the software.
  • The import screen will now treat "Hidden" and "X" as a Hidden gender.
  • Added "99999" marker read to live export file when "All Reads" is selected - which is typically used for the RaceDay Scoring export.
  • "Require Bib #" will now be checked by default going forward. This is the safer option than leaving it unchecked.
  • The Open Race and Timing screen should be a lot "snappier" when they load. No more partial screen loading while it draws everything for a second or two.
• Bug Fixes:
  • Fixed bug with syncing Teams in the RunSignUp Test environment.
  • Fixed bug with importing chip start files for pre-assigned starting times.

[Raphael Leal]

So, the step by step to import a tag read file is (correct me if I´m wrong):
(Before everything I had to edit the txt file and split the chip starts time (TRUE) and save another txt with the Finish times (FALSE).

Reset the race or duplcate the race you´re trying to fix or to simulate the issue
Check "Capture Chip Starts"
Import the chip starts tag read file of that race
Uncheck  "Capture Chip Starts"
Check  "Capture Chip Finish"
*Import the finish time file

The chip starts file must contain the follow line:

"Race Started:" "Short name of the race", "DD/MM/YYYY HH:MM:SS"

Example: "Race Started: 5K,26/04/2026 07:59:54"