# Exporter

Exporters need to be created when you want to have IDCamPro react upon the arrival of new passings triggered by new raw data instead of [connecting local to the decoder](/dbnetsoft/idcampro/configuration/timing.md).

In order to receive raw data passings and IDCamPro can act upon them , RR12 exchange needs to define an exporter to send data to us. 

## Online

Our RemoteRedirect webservice provides a bridge between RR12 working online that can only access public web servers and IDCamPro running locally. 

{% hint style="info" %}
Protocol is https and host is raceresult.remoteredirect.com:\
`https://raceresult.remoteredirect.com`
{% endhint %}

The following exporter need to be configured in RR12 (Timing - Exporters & Tracking - Exporters):

| URL                                                                                                    | Export Data                                                                                              |
| ------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------- |
| <p>HTTP(S) Post</p><p><code><https://raceresult.remoteredirect.com/api/raceresult/exporter></code></p> | <p>Custom</p><p><code>\[Event.ID] & ";" & \[RD\_TimingPoint] & ";"&\[Bib] & ";" & \[RD\_Time]</code></p> |

## Offline

When working offline (e.g. checking out the event and using the local race result Web Server, IDCamPro acts a REST API server to receive exporter data.

{% hint style="info" %}
Protocol is http (not https) and host is localhost:8181 (no www, take care with the :):\
`http://localhost:8182`
{% endhint %}

| URL                                                                                    | Export Data                                                                                           |
| -------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| <p>HTTP(S) Post</p><p><code><http://localhost:8182/api/raceresult/exporter></code></p> | <p>Custom<br><code>\[Event.ID] & ";" & \[RD\_TimingPoint] &";"& \[Bib] & ";" & \[RD\_Time]</code></p> |

{% hint style="warning" %}
RRexchange and IDCamPro use different local ports in order to be able to run side-by-side on the same computer.
{% endhint %}

## Online & Offline

*Name* can be defined as you like, e.g. RRExchange. *Timing Point/Split* and *Filter* can be set to whatever you need, however you can always filter in RRExchange as well - so best is to leave it on *All*.&#x20;

{% hint style="info" %}
In case you want to keep the mapping in IDCamPro and not do it in RR12, you can replace *\[Bib]* with *\[RD\_Transponder]* - then RR12 transmits the active transponder code and IDCamPro is doing the mapping.
{% endhint %}


---

# 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://docs.dbnetsoft.com/dbnetsoft/idcampro/configuration/race-result-12-14/exporter.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.