Omega Quantum-AQ |
Top Previous Next |
The Quantum-AQ INTERFACE is designed to exchange data through a file sharing interface with the Omega Quantum-AQ Timing Console. Results from each race are transferred directly from the timing console and stored as a file in the MM database directory without any keyboard data entry. No cable is required to connect MM with the Quantum.
Setting Up The INTERFACE for the Quantum-AQ Click on Set-Up from the Main Menu Bar and then Timing Console INTERFACE. Now click on the Quantum-AQ radio button and then OK. The Quantum-AQ computer with its software and the MM computer should be networked together and mapped to share the MM database folder wherever that is. So there are two possibilities.
How to Create the Meet Schedule for the Quantum-AQ
How to Select a Data Set for your Meet A Data Set is a set of results for a given meet or session of a meet. Each time a race is completed and saved in the Quantum-AQ, it creates a result file in the shared data folder and this file has the extension .qaq. The first 3 characters of the file name are numbers from 001 to 999. These three character numbers define the Data Set number. So when you select a data set, you are selecting a data set of results based on the first three characters of the result files. It is very important to have selected the correct data set.
To select a Data Set, click on Run / Timer and click on Select Data Set stored from QAQF. The INTERFACE will display a window with the date and time and the number of races that have been stored for the current data set that MM is pointing to. Remember, you could be running a three day meet and The INTERFACE must know what "data set of meet data" you want to access.
Click on the Next Meet or Previous Meet buttons to select the appropriate data set. Because there is a date and time shown for when the first file in the data set was created, you can usually figure out which data set to select. This is handy if you have to go back to a previous session's results and pull over a DQ'd athlete's splits and time.
If new Data Sets with a new data set number have been added since starting MM, you can click Update Data Set and all data sets will be refreshed for selection.
How to Create Start Lists for the Quantum-AQ To create start lists for the Quantum-AQ system with an alpha-numeric scoreboard, you must have HY-TEK's Scoreboard Interface option and select Network File Sharing IST or Quantum-AQ from MM's Set-up / Scoreboard Interface menu. When you are ready to start the meet, click Run / Scoreboard (QAQF) / Create Start List and a file named quantum.slx will be created and placed in MM's database folder. MM will create a start list file of the whole meet regardless of the status of the events. So if an event is Un-Seeded, but you have imported or manually entered athletes or relays into lanes, the start lists will still be created for that event. Note that the only time the start list is updated is when you click Run / Scoreboard / Create Start List. So, if you make changes to the lanes during the meet, you need to recreate start lists in order to update the start lists. Note: There is a new format in MM 7.0 for the Quantum-AQ file sharing for the scoreboard where up to two records can be exported along with the start list in a separate file named quantum.rec.
Reading in Results From the Run Menu, there are two ways to read in times from the stored result files:
Click one of the links below for how to bring times in from the timer.
HY-TEK recommends using method #1 which assumes the timing operator is entering the proper event and heat number.
From the Run screen, press F3 or click the Get Times button to cause MM to scan the result files for one with the matching event, heat number, and round (Prelims, Semis, or Finals). If found, the results and splits will be instantly entered.
From the Run screen, press F2 or click the Race# button. Enter a Race# to cause MM to scan the result files for one with the matching Race number. If found, the results and splits will be instantly entered. Note that each stored race has a race number with the first one stored being race #1, the second being race #2, etc. This allows for unique selection of any race in cases where the event, heat number, and round stored are incorrect. Each data set starts over with race number #1.
|