Bug Report - 1.6.7.1

[Steve Hudson]

2 evening races tonight went very well with just a couple non-reads at the chip start.

However, during the setting up pre-race, all of a sudden when both races were set to Chip Start and with plenty of time before race start and only my test chip tag around (but not in proximity), ART produced dozens and dozens of PINK clock entries. And these were for Bib Nos not in the system and nothing like the Bib Nos between the 2 races : values in the thousands.

Very quickly, I re-set the whole event and, thankfully, the mass of clock entries did not reappear.

[Steve Hudson]

3 trail races today. All of a sudden PINK clock entries appeared once again. Refresh made no difference. Exit and re-entry to ART made no difference. Database sent to Brian.

[Christopher Regan]

Haven't run into this but sounds like something related to

• 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. For your safety, this feature is only available on the timing screen if it's NOT race day.

[Ted Finch]

One source of random reads are shop loyalty cards and another is parking tags on the wind screen of vehicles.

On Sunday we set up the chip start across the road and did the usual Reader Test. A resident drove slowly over the mats leaving a trail of multiple character reads on the screen. At least we knew that the reader was working!!

If a chip with a non numeric code is read you may get a read but no data. I think ART will only recognise a numeric code. So perhaps somewhere in range you have a tag with an alphanumeric code.

Cheers

Ted

Keep it Simple Timing

[Steve Hudson]

But surely, Ted, if there was a tag in proximity with an alphanumeric code, it would forever get recognised and the clock screen would get blitzed in pink ?

I recognise the occasional entry and one can usually grasp what the offender is. But I would, with respect, point more towards the recent random generator facility. The only significance so far as I can guess is when >1 race have their clock running on the clock screen but not necessarily ‘live’ (I have only had one race at a time wanting to have tags being read, so far).

[Steve Hudson]

I’ve just looked at my video of the finish line when the pink time records started. There is nothing I can see that triggers the times. But, the burst of time records was almost exactly 5 seconds (to the 1/100 of a second) - does this ring a bell, Brian ? Only a thought.