RUFUS Help
RUFUS Race Manager
RUFUS Race Manager
  • Introduction to RUFUS Race Manager
  • GETTING STARTED
    • Introduction to Race Timing and Race Timing Software
    • Excel 101: Handling Participant Data
    • Networks 101: Understanding the Basics for Race Timing
    • System Requirements for RUFUS Race Manager
  • installation and setup
    • Installing RUFUS Race Manager
    • Initial Configuration
    • User Interface Overview
  • event management
    • Creating a New Event
    • Managing Events
    • Event Settings
    • Event Control View
  • Participant Management
    • Participants Menu
    • Manually Adding Participants
    • Import Participants from List
    • Editing Participant Details
    • Participant Statuses
    • Participant Passings
    • Organizing Participants
  • Checkpoints
    • Understanding Checkpoints
    • Checkpoints Menu
    • Creating Checkpoints
    • Checkpoint Dashboard
    • Checkpoint-Race View
  • Races
    • Races Menu
    • Creating Races
    • Race Dashboard
  • SEGMENTS
    • Understanding Segments
    • Segments Menu
    • Creating Segments
    • Time Visualization
    • Race-Segment View
  • GROUPS AND AGE GROUPS
    • Groups Menu
    • Groups
    • Age groups
  • Timing Devices Integration
    • Introduction to Timing Devices
    • Devices Menu
    • Connecting Local Devices
    • Connecting Cloud Devices
    • Analyzing Backup Files
    • Event-Devices View
    • Rewind Passings
  • Collecting and Managing Timing Data
    • Understanding the Data Collection Process
    • Timing on Race Day
    • Adding Manual Passings
    • Monitoring Live Timing Data
    • Editing Timing Data
    • Passing Statuses
    • Reprocess Passings
  • Classification and Results Processing
    • Understanding Classifications
    • Results Menu
    • Viewing Race Results
    • Generating Reports
  • PUBLISHING IN THE RUFUS EVENT APP
    • Publishing the Event
    • Publishing Participant Information
    • Publishing Race Results
  • Offline Mode and Data Synchronization
    • Working Offline with RRM
    • Data Synchronization
  • Troubleshooting and Support
    • Common Issues and Solutions
    • Frequently Asked Questions (FAQs)
  • Updates and New Features
    • Upcoming Features
    • Keeping RRM Updated
    • Changelog
  • Best Practices and Tips
    • Optimizing Race Timing Workflow
    • Data Management Best Practices
Powered by GitBook
On this page
  • How to Connect Local Devices
  • Add Device Modal Fields
  • Assigning Local Devices to an Event
  • When to Use Local Devices
  1. Timing Devices Integration

Connecting Local Devices

PreviousDevices MenuNextConnecting Cloud Devices

Last updated 3 months ago

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.

How to Connect Local 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:

Add Device Modal Fields

  • 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.

Assigning Local Devices to an Event

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.

When to Use Local Devices

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.

Add Local Device Modal