RUFUS Help
RUFUS CloudBox
RUFUS CloudBox
  • Introduction to RUFUS CloudBox
  • GETTING STARTED
    • Getting Started with RFID Technology
    • Introduction to Race Timing
    • RFID for Race Timing
    • Networks 101: Understanding the Basics for Race Timing
    • CloudBox Ports & Characteristics
  • PROTOCOL
    • How to Connect to the CloudBox
    • Protocol Commands and Responses
    • Receiving Timing Data Passings During a Session
  • CONNECTIONS
    • Connecting to the CloudBox: LAN, WiFi, and 4G Overview
    • Connecting the CloudBox via Ethernet Cable
    • Connecting the CloudBox via WiFi Access Point
    • Connecting the CloudBox to an External WiFi Network
    • Connecting Two or More CloudBox in the Same Network via a Hub or Router
    • Connecting the CloudBox to a 4G Network
  • Interface
    • Accessing the CloudBox Interface: General Guide
    • Timing Interface
    • Status Interface
    • Configuration Interface
    • Backup Interface
    • GPS Interface
    • Cloud Interface
  • General Operations
    • RFID Reader Configuration
    • RFID Reader Installation
    • Knowing your CloudBox IP Address
    • Boot Sequence
    • Starting and Stopping a Timing Session
    • Accessing Backup Files on the CloudBox
    • Time Synchronization Methods
    • LED Signals and Alarm Notifications
    • Connecting your CloudBox with RUFUS Race Manager (locally)
    • Connecting your CloudBox with Wiclax (locally)
  • ADVANCED OPERATIONS
    • Firmware Update
    • Network Configuration
    • GPS Service
    • Backup Rewind Function
    • IoT Service
    • 4G Modem
  • Cloud
    • Introduction to CloudBox Cloud Service
    • Binding the CloudBox with the RUFUS Cloud Service
    • Accessing Stored Cloud Timing Sessions
    • Connecting your CloudBox with RUFUS Race Manager (remote)
  • Care and maintenance
    • Warning!
    • Battery Care
    • Taking Care of your CloudBox
    • General Recommendations
    • Special Note on UHF Cables
  • Common problems
    • FAQ
    • Common Problems and Troubleshooting
Powered by GitBook
On this page
  • Key Features of the Timing Interface
  • How the Interface Works
  • Understanding the Passing Data
  • Considerations When Using the Timing Interface
  • Summary
  1. Interface

Timing Interface

PreviousAccessing the CloudBox Interface: General GuideNextStatus Interface

Last updated 8 months ago

The Timing Interface is a crucial component of the CloudBox system, designed to provide real-time visibility into race timing sessions. This interface, accessible through the CloudBox dashboard, allows users to start and stop timing sessions and view the last 1000 passings in a session. Each passing is accompanied by detailed information such as the tag's EPC (Electronic Product Code), timestamp, antenna ID, and signal strength (RSSI).

In this article, we'll explore the key functionalities of the Timing Interface, including how to manage a timing session and understand the data displayed.

Key Features of the Timing Interface

  1. Start/Stop Timing Sessions:

    • The interface provides START READS and STOP buttons to control the timing session.

    • Clicking START READS will initiate the reading of RFID tags, while STOP will halt the session. This allows for precise control over the timing process during an event.

  2. Passing Data Table:

    • The table in the interface displays up to the last 1000 passings received by the CloudBox. The columns in the table represent the following data points:

      • #: The sequential order of the passings.

      • tagStr / EPC: The unique identifier (EPC) of the RFID tag or the string representation.

      • Timestamp: The exact time the tag was read, formatted as YYYY-MM-DD HH:mm:ss.sss.

      • Seen: The number of times the tag has been detected by the RFID reader in the read cycle.

      • RSSI: The signal strength at which the tag was read (in dBm), providing insight into the proximity of the tag to the antenna.

      • Ant.: The antenna ID from which the tag was detected (useful if the CloudBox is using multiple antennas).

      • Lat. and Long.: The latitude and longitude coordinates (if GPS is enabled), indicating the tag's location at the time of the reading.

  3. Real-Time Notifications:

    • Every time a new passing is detected by the CloudBox, a notification is sent to all connected clients.

  4. Session Count:

    • At the bottom of the table, the session count is displayed, indicating the total number of passings detected during the current session.

How the Interface Works

  1. Starting a Timing Session:

    • Click the START READS button to begin a new session. The CloudBox will start reading RFID tags and displaying the information in the table as passings are detected.

    • Passings will be continuously updated in the table, showing the most recent information at the top.

  2. Viewing Passings:

    • The table updates automatically as new passings are received, displaying up to 1000 passings. Each row in the table represents a unique detection event, providing key information like the tag’s EPC, timestamp, and signal strength.

    • The table allows timing personnel to quickly assess the current status of the race and ensure that tags are being read as expected.

  3. Stopping a Timing Session:

    • To end a session, click the STOP button. This halts the reading process, and no further passings will be detected until the session is restarted.

Understanding the Passing Data

Each passing provides critical data for analyzing the race:

  • EPC/tagStr: Each tag has a unique identifier (EPC), which is essential for identifying individual participants or objects in the race. This information is automatically linked to participant data within your timing software.

  • Timestamp: Precise timing is essential in any race event. The timestamp ensures that each passing is recorded accurately, down to the millisecond, allowing for reliable race results.

  • RSSI (Signal Strength): This metric indicates how close the tag was to the antenna when it was read. A stronger (more negative) signal (e.g., -20 dBm) suggests proximity, while a weaker signal (e.g., -100 dBm) could indicate that the tag was further away.

  • Antenna ID: If multiple antennas are in use, this column shows which antenna detected the tag. This is useful for monitoring tags passing through different timing points.

  • Latitude/Longitude: If the CloudBox is GPS-enabled, the latitude and longitude fields provide the exact location of the passing. This is especially useful in mobile or geographically distributed races (e.g., marathons or triathlons).

Considerations When Using the Timing Interface

  1. Network Access:

    • To access the Timing Interface, ensure you are connected to the CloudBox either via Ethernet or WiFi. You can access the interface by navigating to cloudbox.local or the CloudBox’s IP address in a web browser.

    • If multiple CloudBox devices are on the same network, remember to access each device using its unique IP address.

  2. Real-Time Notifications:

    • The CloudBox sends real-time notifications to connected clients with every passing.

  3. Session Management:

    • Proper session management is essential. Be sure to start and stop sessions according to your event schedule to avoid overlapping or missing passings.

Summary

The Timing Interface is an essential tool for race event timing, providing users with real-time visibility into tag detections, detailed passing data, and the ability to start and stop sessions as needed. With up to 1000 passings displayed at a time and real-time notifications to connected clients, the interface ensures that your timing system can stay synchronized and provide accurate results during the event.

By leveraging this interface, race organizers and timing personnel can manage timing sessions effectively, ensuring the highest level of accuracy and reliability in any event.