RUFUS Help
RUFUS Race Manager
RUFUS Help CenterRUFUS CloudBoxRUFUS Cloud Public APIRUFUS Race ManagerRUFUS Timing AppRUFUS CloudRUFUS Event App
RUFUS Race Manager
RUFUS Help CenterRUFUS CloudBoxRUFUS Cloud Public APIRUFUS Race ManagerRUFUS Timing AppRUFUS CloudRUFUS Event App
  • 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 Cloud Devices
  • Add Device Modal Fields
  • Important Considerations for Cloud Devices
  • When to Use Cloud Devices
  1. Timing Devices Integration

Connecting Cloud Devices

PreviousConnecting Local DevicesNextAnalyzing Backup Files

Last updated 2 months ago

Cloud devices in RUFUS Race Manager (RRM) allow for flexible, remote connectivity, leveraging the cloud infrastructure to manage race timing data. These devices connect to the RUFUS Cloud and can be used for race timing across different locations, providing centralized management and monitoring. To connect a cloud device, users only need to assign it to an event within RRM.

How to Connect Cloud Devices

To connect a cloud device to RRM, users need to configure the device through the Add Device modal. The following fields must be completed:

Add Device Modal Fields

  • Checkpoint(s): Select one or more checkpoints where the device is installed. This ensures that the device is accurately assigned to specific points in the race, allowing RRM to manage and record participant passings correctly.

  • 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 helps to avoid duplicate readings, ensuring that each passing is only recorded once.

Since the cloud device is already bound to the user's cloud account, users do not need to enter the IP address or port information. Instead, they simply assign the device to specific checkpoints in the event.

Important Considerations for Cloud Devices

  • Event Assignment: Cloud devices can only be assigned to one event at a time. Once the device has completed its use in an event, it must be disconnected from the event before it can be assigned to another. This ensures that devices are uniquely linked to one event, avoiding conflicts in data collection.

  • Internet Connectivity: Cloud devices require an active internet connection to communicate with the RUFUS Cloud and to transmit passings data to RRM.

When to Use Cloud Devices

Cloud devices are recommended for events that require remote connectivity and centralized data management. They are ideal for:

  • Multi-location events where data needs to be collected from multiple locations and transmitted centrally.

  • Events with reliable internet access, allowing for seamless data transmission to the cloud.

  • Scenarios where remote monitoring and control of timing devices are needed, providing flexibility for race managers.

Add Cloud Device Modal