# Timing Interface

The **Timing Interface** is the heart of the CloudBox system, giving you real-time visibility and control over race timing sessions. Accessible directly from the CloudBox dashboard, it allows you to start, pause, and stop sessions while monitoring the latest tag detections as they happen. The interface is designed to keep you in control of the event with clear indicators, session counters, and detailed passing data.

<figure><img src="/files/Ic2tdPI2LKHCh8Z30aiA" alt=""><figcaption><p>Timing interface</p></figcaption></figure>

## Key Features

### Session Controls

* **Start**: Initiates a new timing session. The CloudBox begins detecting RFID tags and recording passings.
* **Pause**: Temporarily suspends the recording of passings without ending the session. This is useful if you want to stop recording momentarily without creating a new session or backup file.
* **Stop**: Ends the current session. No further passings are recorded until a new session is started.

At the top-right of the interface, the session state is always visible (e.g., *STOPPED*), along with the total number of passings collected.

### Latest Passings Table

The table displays up to the last **1000 passings** detected during the active session, with the most recent at the top. Each row corresponds to a single passing and contains the following data:

* **#**: Sequential number of the passing in the session.
* **tagStr / EPC**: The unique RFID tag identifier (Electronic Product Code or string representation).
* **Timestamp**: Exact time of detection, displayed in `DD/MM/YYYY, HH:mm:ss` format.
* **Seen**: Number of times this tag has been detected in the read cycle.
* **RSSI** *(if provided)*: The signal strength at which the tag was read, expressed in dBm. A stronger signal (closer to 0, e.g., -25 dBm) usually means the tag was close to the antenna, while weaker values (e.g., -90 dBm) suggest greater distance or obstacles. Not all passings will include this field, depending on the reader model and configuration.
* **Ant.**: The antenna ID that detected the tag (especially useful when using multiple antennas).
* **Lat. / Long.**: GPS coordinates of the CloudBox at the time of detection (if GPS is enabled).

This live-updating table allows you to confirm that tags are being captured correctly during the event.

### Real-Time Updates

* Passings appear instantly in the table as they are read.
* All connected clients viewing the interface receive real-time updates, ensuring timers and operators stay synchronized.

## How to Use the Timing Interface

1. **Start a Session**\
   Click **Start** to begin capturing RFID tag detections. Passings will appear immediately in the table as they are detected.
2. **Pause a Session**\
   Use the **Pause** button to temporarily halt recording without closing the session. No new passings will be logged until you resume.
3. **Stop a Session**\
   Click **Stop** to end the session. A new session will be created the next time you press **Start**.

## Understanding the Data

* **EPC/tagStr**: Unique identifier that links to a participant in your race timing software.
* **Timestamp**: Essential for precision in results—each passing is logged to the millisecond.
* **Seen**: Helps identify how long a tag have been on the field during a read cycle.
* **RSSI**: Indicates how strong the tag’s signal was at the time of reading. This helps evaluate antenna coverage and tag proximity.
* **Antenna ID**: Indicates which antenna read the tag, useful for multi-point setups.
* **GPS Coordinates**: Provides location data, particularly valuable for mobile setups or races spanning wide areas.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.runonrufus.com/rufus-cloudbox/interface/timing-interface.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.