We just completed our first event today and other than the fact we had snow messing with our sensors things went really well!

Our only real Axtime glitch was that we had to enter in times from the AC4 manually for the first 4-5 cars and couldn't figure out how to get them to import automatically but on car 6 it just started to import times automatically and did so for the rest of the day.

Aside from that the software was fantastic and it's light years ahead of Axware! It was by far the easiest registration we've ever had and it worked seamlessly with MS Reg.

While we did it without wireless results for the first event, we're looking forward getting that set-up before our next event on June 12th. We just need a little more help in doing so. Maybe some better instructions on exactly what we need to do step by step.

There's no way to find a time that was recorded and assign a driver to it. So if I miss a driver before they finish, now suddenly they need to be entered manually.

Times that are not assigned to a driver in the queue don't get recorded at all. This happens to us all the time during worker changeovers. If we forget to turn the eyes off, people start spurious runs when there are no drivers in the queue, Those times are clocked, but disappear into etherspace.

There's no way to shift the entire queue of drivers against runs if there's an 'Off by one' error while queuing. Though, this is probably not a big deal if the CQ is doing a good job.

There is a method of doing this in the TK screen. In the Recent Runs area, click on the incorrect run. If there was a car wrongly inserted in the queue, click Remove Driver But Keep Times. That will delete the incorrect car and move all the times down 1 to fill the gap. Alternatively, if the queue is right but something is wrong with the time, click Change This Driver's Time. Then you can edit the incorrect time for the run and it bumps all the following times up 1. That method will pull the next driver from the queue into Recent Runs to be assigned the last time in the bump.

That being said, we are not terribly good at doing these corrections on the fly, yet, but we're getting in practice.

While we did it without wireless results for the first event, we're looking forward getting that set-up before our next event on June 12th. We just need a little more help in doing so. Maybe some better instructions on exactly what we need to do step by step.

That's really easy, and I can't recommend it enough. You need an internet link for your main computer only. Tether it to a phone if you have one - data usage is light. I bought a NetZero dongle for about $70 and signed up for the free data plan, which is more than enough monthly data for several events. The dongle installs itself and connects easily via a little popup console, but of course, that will vary depending on what you get.

To enable RM Live, you'll need a cloud key, which Chris should have given you as part of your package. Under Club Home / System Configuration, enter the cloud key in the field near the bottom of the screen. If you're using AXti.me backups, it's probably already there.

Once the computer is uplinked with your mobile internet connection on the day of the event, go to the Event Home and click Event Setup. Turn on Online Live Results via the little slider switch right above the run groups configuration. That should be all you need to do, but it never hurts to also click the Sync To RM Live button on the Event Home screen, below the various task buttons and above the Results buttons.

The event should sync automatically every 20-30 seconds or so without further input. Keep an occasional eye on your data connection to make sure it's still live, but that's really all there is to it.

Times that are not assigned to a driver in the queue don't get recorded at all. This happens to us all the time during worker changeovers. If we forget to turn the eyes off, people start spurious runs when there are no drivers in the queue, Those times are clocked, but disappear into etherspace.

Actually, axtime records EVERY timer trip even when no cars are in the queue. Go into 'raw times'. For example, here's our event from Saturday where someone forgot to turn the eyes off during run session changeover http://take.ms/oCUUR

No, you can't assign these raw times to a driver, but the raw times screen is useful for other things ... like the exact start and end time for run group sessions, average car release rate, how long we actually took for lunch, etc :-)

While we did it without wireless results for the first event, we're looking forward getting that set-up before our next event on June 12th. We just need a little more help in doing so. Maybe some better instructions on exactly what we need to do step by step.

Printing registrants at the beginning of the day to ensure numbers and classes are correct before the event starts? I can't seem to find a good way to do this.

To print out registrants at the beginning of the day just go the event and export. Open the CSV in excel and there's your drivers. For example, I just created our June 12th event and imported what people have already registered in MSR. Did an export and here's what I see http://take.ms/xztTR

There is a method of doing this in the TK screen. In the Recent Runs area, click on the incorrect run. If there was a car wrongly inserted in the queue, click Remove Driver But Keep Times. That will delete the incorrect car and move all the times down 1 to fill the gap. Alternatively, if the queue is right but something is wrong with the time, click Change This Driver's Time. Then you can edit the incorrect time for the run and it bumps all the following times up 1. That method will pull the next driver from the queue into Recent Runs to be assigned the last time in the bump.