# Devices Menu

The **Devices Menu** in **RUFUS Race Manager (RRM)** allows users to manage both **Local** and **Cloud** timing devices. From this menu, users can view and configure the devices available for their events, ensuring that each timing device is correctly assigned and operational.

<figure><img src="/files/xWALLtOf4k4xGoY2Atrm" alt=""><figcaption><p>Devices Menu</p></figcaption></figure>

## Overview of Devices Menu

The **Devices Menu** is divided into two categories:

### Cloud Devices

* Cloud devices are connected via the **RUFUS Cloud** and are bound to the user's company account.
* Examples of cloud devices can include a **Custom timing device**, **CloudBox**, or the **RUFUS Timing App**.
* To view and assign cloud devices to an event, the user must have an **Internet connection**.

### Local Devices

* Local devices are connected directly to the **desktop versions** of **RRM** (Windows and Mac).
* Examples of local devices include the **One4All 5** system and the **RUFUS CloudBox**.
* Local devices are not availabe in the **web version.**

### Compatible Local Timing Devices

You can connect locally the current compatible timing devices:

* **Macsha One4All 5 Base and PRO systems**
* **RUFUS CloudBox**
* **Race Results Decoder 5000S Series**

## Backup Files

You can treat backup files as if they were additional timing devices. Backup files, often generated by timing hardware at the source, contain passings—essential data entries that record participants’ id and timestamp. By importing and analyzing a backup file, you ensure that all recorded passings are processed through the same logic pipeline as real-time device data. To assign backup files to checkpoints, users can simply click on the **Backup file** button. This action will open the **Process Backup Files** modal,&#x20;

## Assigning Devices to an Event

To assign a device to an event, users can simply click on the device listed in the **Devices Menu**. This action will open the **Add Device** modal, providing the corresponding options to bind the device (whether local or cloud) to the event. Proper assignment ensures that passing data is accurately collected and associated with the correct event checkpoints.


---

# 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-race-manager/timing-devices-integration/devices-menu.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.