> For the complete documentation index, see [llms.txt](https://docs.dbnetsoft.com/dbnetsoft/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dbnetsoft.com/dbnetsoft/idcampro/configuration/timing/race-result-devices.md).

# RACE RESULT Devices

<figure><img src="https://dbnetsoft.github.io/IDCamProDocumentation/configuration/timingdevices/images/raceresult.png" alt=""><figcaption></figcaption></figure>

The following devices are supported:

* System 5000 directly via local network (port 3601)
* Ubidium directly via local network
* Exporter setup on local webserver in RR12

### Configuration <a href="#configuration" id="configuration"></a>

#### Active <a href="#active" id="active"></a>

As there can be many remote devices and/or loops connected to a decoder or RR12 event file, differentiation is based on channel and loop IDs.

| Key                    | Values                  | Example                        |
| ---------------------- | ----------------------- | ------------------------------ |
| Start/Impulse Channels | `M<channelId>-<loopId>` | `M3-1` for loop 1 on channel 3 |
| Recording Channels     | `<channelId>-<loopId>`  | `2-1` for loop 1 on channel 2  |
| Bib Channels           | `<channelId>-<loopId>`  | `5-1` for loop 1 on channel 5  |

{% hint style="info" %}
Ubidium does not transmit channel and loop information, so here a trigger is only M without channel and loop id.
{% endhint %}

#### Passive <a href="#passive" id="passive"></a>

| Key                | Values   | Default                                             |
| ------------------ | -------- | --------------------------------------------------- |
| Start Channels     | `M`      | `M`                                                 |
| Recording Channels | `M`, `F` | `M F` for recording on both a trigger and a passing |
| Bib Channels       | `F`      | `F`                                                 |

`M`stands for manual input on the active extension by either a lightbeam or a push button.

Rising/falling edge cannot be used.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.dbnetsoft.com/dbnetsoft/idcampro/configuration/timing/race-result-devices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.