# Connecting Local Devices

Local devices in RUFUS Race Manager are used to collect race timing data directly from the field.

They are physically connected to the timing computer, typically via **Ethernet or WiFi**, and communicate using **TCP sockets**. This allows real-time data transfer with full control over device behavior.

## Adding a Local Device

To add a local device, open the **Add Device** modal and configure the device.

<figure><img src="/files/UVPMEFkBOylBEl011rDD" alt=""><figcaption><p>Add Local Device Modal</p></figcaption></figure>

### Device Configuration Options

You can add a device in two ways:

#### Standard Configuration

Provide the full connection details:

* **IP Address**: The device network address.
* **Port Number**: The TCP port used for communication.
* **Checkpoint(s)**: The checkpoint(s) where the device is installed.
* **Bounce Time**: Time (in seconds) to ignore repeated reads from the same chip.

This option is used when the device is already installed and its network configuration is known.

#### Configuration Pending

Enable **Configuration pending** to register the device without defining its network settings.

In this mode:

* **IP Address** and **Port Number** can be left empty.
* The device can still be assigned to one or more **checkpoints**.
* Network configuration can be completed later.

This is useful when preparing the event in advance, before the device is physically installed or its network details are available.

### Assigning Devices to Checkpoints

Each device must be linked to one or more checkpoints.

This ensures that passings received from the device are associated with the correct location in the race.

Checkpoint assignment can be done at creation time, even when using **Configuration Pending**.

### Completing Configuration Later

Devices added with Configuration Pending can be updated at any time.

Once the device is available:

1. Edit the device.
2. Enter the **IP Address** and **Port Number**.
3. Save the configuration.

The device will then be ready to establish a connection and start receiving passings.

## Compatible Local Devices

RRM supports the following local timing devices:

* **Macsha One4All 5 Base and PRO systems**
* **RUFUS CloudBox**
* **RaceResult**
* **LLRP RFID Readers**&#x20;
* **Mylaps**
* **Feibot**&#x20;
* **Ultra RFID**&#x20;
* **Westhold**

## When to Use Local Devices

Local devices are recommended when a stable, direct connection to the timing system is required.

Typical use cases include:

* Locations with limited or unstable internet connectivity.
* Events requiring high reliability and low latency.
* Setups where timing must operate independently from cloud services.

Local devices provide full control over timing data and ensure consistent operation during the race.


---

# 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/connecting-local-devices.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.