Open up the race and go into timing screen.
Under the TV tab make sure display chip time is selected and then publish results. It's worked for me in the past.
If not hit display by gun time and see what that gives you.
| Sep 23 ![]() | ![]() ![]() | ||
| Sep 23 ![]() | ![]() ![]() | ||
| Sep 23 ![]() | ![]() ![]() | ||
| ![]() ![]() | ![]() ![]() | ||
She sent me links, screen shots, and her database so that I could look into it. Everything she sent seemed to confirm that. I then stepped through the code and confirmed that the correct times were being passed to the correct fields in the XML that the program sends to the API.
That's all I've done into it so far. Is it possible that other software is sending with JSON and the problem exists only with the XML submission?
I'm on vacation (Destin, FL) this week with the family, so I'll have to wait until I can safely pull out the computer with worrying about the wife hitting me with a bat for trying to work, but of course I'll handle any emergencies immediate and I'm responding to as many emails as possible by phone.
I'll dig deeper into this as soon as I can and report back what I find.
1) if timing multiple events at the same time, say a 5k and 10k, if you push results of the 5k, ART will push blanks to the 10k results. Not a huge deal, but it doesn't seem efficient to have to push all results if they aren't completed yet.
2) If you had 200 registrations and 150 finishers, ART will push 50 blanks to RSU. Although I notice that if you publish on a subsequent day, the blanks aren't uploaded.
It all works, which is fine for me, but just making mention of these items.