We've compiled a few error scenarios experienced as we've assisted our customers through the CTS System 5/6 or Gen7 setup process. Our experience is hopefully your gain to help you troubleshoot if you run into any issues.
Covered in this Article:
- Meet Maestro & CTS Timing Console Communication Process
- Error Scenario: Can't Connect to Gen7
- Error Scenario: Unable to detect any devices
- Error Scenario: Meet Maestro detects ports but they are busy
- Error Scenario: "Please install the corresponding PL2303 driver to support Windows 11"
- Error Scenario: The Timer Console is in the ‘Setups’ Menu
- Error Scenario: Attempting to Change Meet Stuck on Loading Meet Options
- Error Scenario: Meet Maestro is importing the wrong times
- Error Scenario: Alphanumeric Event Numbers Unsupported
Meet Maestro & CTS Timing Console Communication Process
Communication between the CTS timing console and Meet Maestro happens through a serial port. Serial ports have been around a long time, so long in fact that most modern computers no longer have serial ports.
- For CTS System 5/6 you connect your meet management computer to the timing console through a USB to Serial Port (example device) cable.
- For CTS Gen7 the USB to serial port conversion is handled inside the timing console and so a simple USB cable is sufficient.
Error Scenario: Can't Connect to Gen7
Receiving ‘Data Integrity Check’ error, followed by ‘Access Denied’ errors.
Solution: CTS provided a button to ‘Reset the Meet Management interface’. This scenario will be removed once it is completely resolved.
Error Scenario: Unable to detect any devices
When you initialize the timing system, if it halts on this step and provides the error - Unable to detect CTS System 5/6 console (or Gen7), then Maestro does not see any serial ports in your system. There is likely a hardware or Windows driver issue. Follow the debug steps below.
➧ Step 1: Click Restart Connection button. Click Retry button if it does not solve the issue initially.
➧ Step 2: Click Restart Maestro button.
➧ Step 3: If the issue still persists, verify the cables are connected
For Gen7, there are two ports on the Gen7 console. Make sure the USB cable is plugged into the port with the 'clipboard and stopwatch' icon. If the cable is plugged into the wrong port, Device Manager in windows will list 3-4 consecutive ports instead of a single port.
➧ Step 4: Verify that Windows detects the serial port
- Open Device Manager
- Verify that your device is displayed under ‘Ports (COM & LPT)’.
» Note: Windows selects the COM port number for you and it may differ from this example (‘5’ in this case). Make note of the number as we will use it in a later step.
- If the ‘Ports’ category is missing, Windows did not detect your device! To tell Windows to scan for devices select the menu Action -> Scan for hardware changes
- If ‘Ports’ is still missing, unplug the device from your computer, wait 5 seconds, plug in the device.
- If ‘Ports’ is still missing, unplug your cable, restart your computer, plug in the cable.
- If it is still missing, your cable is likely faulty or damaged.
» Note: At this point, it may be helpful for you to Contact Colorado Time Systems for additional troubleshooting assistance.
➧ Step 5: Verify that Windows has valid drivers installed
Right-click on your device. Select Properties.
A device with a properly installed driver will look like this. If you see errors in Device status, try updating your driver. If you are still having trouble Contact Colorado Time Systems for additional troubleshooting assistance.
➧ Step 6: At this point, Maestro should be able to connect to the device.
Error Scenario: Meet Maestro detects ports but they are busy
When initializing the timing system, if it halts on this step and lists one or more ports with errors that say Resource busy then there are two typical causes:
- There is another software application running on your system that has a ‘lock’ on the device.
- The Windows driver mistakenly thinks an application has a ‘lock’.
➧ Step 1: Close any other applications which might try to talk to a CTS console.
➧ Step 2: Open Device Manager
➧ Step 3: Open the section titled ‘Ports (COM & LPT)’.
➧ Step 4: Unplug the USB cable from your computer. You should see a COM Port device disappear from the list.
➧ Step 5: Reconnect the cable. You should see the device reappear. Take note of the COM port number.
➧ Step 6: Retry the connection in Meet Maestro.
Error Scenario: "Please install the corresponding PL2303 driver to support Windows 11"
If you see the message "Please install corresponding PL2303 driver to support Windows 11 and further OS" under Ports this means that your USB-to-RS232 serial cable adapter uses a chipset made by Prolific and the version of the Prolific driver software installed does not support Windows 11. The driver software needs to be updated to resolve this issue.
IMPORTANT NOTE: in some cases, it is the most recent Prolific driver version that is incompatible, thus reverting to a previous/older version of the driver may be required.
Please refer to these external troubleshooting guides to resolve this specific issue:
- Fixed: Prolific USB to Serial Driver not Working on Windows 11/10 (Includes Video)
- Fix: "Please Install Corresponding PL2303" Driver Issue on Windows 11
Error Scenario: The Timer Console is in the ‘Setups’ Menu
If this error state is detected, we will provide a configuration error message. Exit the 'Setups' screen on the CTS by pressing 'Quit'. Once you have resolved the issue, you can select to RETRY.
Error Scenario: Attempting to Change Meet Stuck on Loading Meet Options
If you are attempting to change the selected meet and see the ERROR DETECTING MEETS, click on Restart Connection in the Troubleshooting section.
» Note: If you receive an error "Unable to detect CTS System 5/6 console or Gen 7" then follow the steps outlined above.
Error Scenario: Meet Maestro is importing the wrong times
If you have imported your first race and the times do not match your expectation, you probably have selected the wrong set of meet data to import from CTS timing console. Meet Maestro allows you to select past meets from which to import data. Usually, if the imported data does not match your expectations, it is because you have the wrong meet selected.
➧ Step 1: In the timing system bar in Meet Maestro, determine the date and time of the selected meet.
➧ Step 2: In the CTS console
- Select ‘Stored Data’
- Usually, the CTS will show you data from the current meet. The first race should match the date and time of your test race or first race of the meet. This time and date should match Meet Maestro. If it does not skip to step 3.
- If the meet data in the CTS console does not match your meet, press the ‘Quit’ button to return to the main swim interface. Verify the console’s date and time (upper right corner) matches today’s date and time. If it does not, you will need to find your meet’s date and time in ‘Stored Data’ relative to the console’s date and time.
➧ Step 3: Once you know the date and time of the CTS meet, return to Maestro. In Maestro, press the gear icon.
➧ Step 4: Under Selected Meet, press Change
➧ Step 5: Select a meet matching the date and time from the CTS meet.
Error Scenario: Event labels are incorrect in my CTS Interface
There are a few potential reasons:
➧ Reason 1: Sometimes, the CTS interface does not immediately update after writing the Event Sequence.
- Press Next Event (on the CTS Console)
- Press Edit Event Heat then enter event and heat numbers (on the CTS Console)
➧ Reason 2: Someone changed the Event Sequence data using the CTS console.
- Use the Maestro Timing Setup interface to rewrite the event sequence to the CTS Console
Alphanumeric events are not supported by the CTS Consoles.
» Tip: We strongly recommend users not use alphanumeric event numbers with the console.
It will sort of work but only if all alpha events have the same distance. For example ‘1A’ and ‘1B’ are both 50 yards, but different competition categories or age groups. If you have no choice here is what happens:
- There will be one event ‘1’ in the CTS, not ‘1A’, ‘1B’, ‘1C’, ‘1D’
- The event description in the console for event ‘1’ will match the last alpha. ‘1D’ for example
- The auto-detection of new race data will not work for events ‘1B’, ‘1C’, and ‘1D’
If the alpha events have different distances, then the last distance will win and the console will be confused about the number of lengths and therefore capture the final time too early or late.