Introduction
As you encounter error codes on your controllers, you may come across some that are unfamiliar, or unclear as to what they mean. This article will dive into a few of them, both the cause, and whether or not there is cause for alarm.
CMOS Error
This one appears in Minitracks and Pro2's, and indicates the controller may be failing to hold time.
On a Minitrack, the error reads: "Controller date is invalid. Please set and reboot. If this problem persists, the CMOS battery may be dead -- contact support"
On a Pro2, the error reads: "System clock is not holding time. Contact support - CMOS Battery may need to be replaced"
In either case, the first and primary aspect you will want to check is whether or not the controller still holds time (within a few seconds) if you turn it off and turn it back on. If the date on the controller resets to the distant past, it definitely needs to be sent in to have the CMOS battery replaced.
However, if you don't see a significant change when you boot the controller back up, the CMOS battery is still good. You may just want to keep an eye on that controller in the coming months to ensure it continues to boot up without significant time loss.
"Tag Data Drive not Open"
If you see this on a Minitrack, it indicates the internal drive has become corrupted and needs service.
In some cases, a controller will give this error errantly, but if it consistently gives you this Tag Data Drive error, you will need to take action to ensure the data integrity on that controller. The next step is to reach out to ChronoTrack Support for further instruction. Generally there is a temporary workaround that can be done, but eventually the controller will need to be sent in for service.
Logging Full
You may find this error message on a Minitrack: "Log drive almost full. Logs will be truncated soon"
This drive has nothing to do with tag data, but rather refers to the log that records system processes and events. If logs are truncated and some of that information is lost, it is no cause for alarm. The problem should sort itself out in a matter of days.
However, if a week or more goes by and that error message continues to appear, please contact support and we will look into it further with you.
Reader Disconnect
On a Pro2, this error reads "Lost connection to Reader 1 (or Reader 2)" followed by the IP address of the reader.
This error can be a one-off, but if it happens repeatedly, the next step is to contact support. We will look into what might be causing it and how to proceed.
If your controller loses connection to the reader(s) during a race, leave the controller on and contact support right away so that we can help save your data.