Running The Meet

If the SST console software quits responding during a meet it usually means that the computer has lost communications with the SST timer.  The most likely cause of this is that the USB port is set to a power saving mode, which means that the port is

Make sure that the SCB files (or the Startlist file) are in the same directory as the .gen file.

This happens typically if the Start cable is bad. Especially if it starts happening after multiple races have been run without a problem.  Replace the cable and the problem should be corrected.  The other possibility is that you are using a starter with a “Normally Closed” start

If the results are being saved to the meet manager computer, and communications between the two computers is lost, the results files are written to the SST computer in the “Documents\SST Timer” directory. When the communications comes back the files can be moved to the meet management

SST gives the operator approximately 10 seconds to recognize that. Just hit the “F Arm” button and the lane will be reactivated.

Just click the “Force Finish” button on the SST console. It will end the race and be ready for the next race.  If you miss the chance to Force Finish and the referee starts the next race, you will receive the Unexpected Start window. Click the Force

I get the following error when I try to “Get Times” in meet manager: This generally happens because meet manager was restarted after the start of the meet.  If this is the case, from the “Run” screen click on “Interfaces”, “Timer (GNET)” and then “Select data set stored from