Connecting Local Devices
Last updated
Last updated
Local devices in RUFUS Race Manager (RRM) are essential for collecting and managing race timing data accurately. Local devices are physically connected to the timing computer, either via Ethernet, WiFi, or other methods, and communicate using TCP sockets. This direct connection allows for real-time data transfer and greater control over the devices.
To connect a local device to RRM, users need to configure the device through the Add Device modal. The following fields must be filled out:
IP Address: Enter the IP address of the local device. This address is required to establish communication between the timing computer and the device.
Port Number: Specify the port used for communication. This is typically a TCP port through which data is transmitted.
Checkpoint(s): Select one or more checkpoints where the device is located. This step is crucial as it links the device to specific points in the race, allowing RRM to accurately associate passings with the correct location.
Bounce Time: Set the bounce time, which represents the interval (in seconds) during which the system will ignore repeated passings from the same device. This prevents duplicate readings, ensuring that each passing is recorded only once.
Once the required information is entered, users can assign the device to the event. This ensures that the timing data collected by the local device is properly linked to the event, allowing for accurate race analysis and classification.
Local devices provide an advantage in reliability and data control, especially in situations where network connectivity may be inconsistent. Proper configuration of these devices is key to seamless event timing.
Local devices are recommended for events where network reliability may be a concern, as they provide a direct and stable connection to the timing computer. They are ideal for:
Remote locations where internet connectivity is poor or unavailable.
High-stakes events where the accuracy and reliability of timing data are critical.
Situations where real-time data transfer is required without relying on cloud services.
Local devices offer greater control over timing data and are less dependent on external factors like internet connectivity, making them an excellent choice for ensuring consistent and dependable race timing.
