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.

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.

Protocol is https and host is raceresult.remoteredirect.com: https://raceresult.remoteredirect.com

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

URL	Export Data
HTTP(S) Post https://raceresult.remoteredirect.com/api/raceresult/exporter	Custom [Event.ID] & ";" & [RD_TimingPoint] & ";"&[Bib] & ";" & [RD_Time]

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.

Protocol is http (not https) and host is localhost:8181 (no www, take care with the :): http://localhost:8182

URL	Export Data
HTTP(S) Post http://localhost:8182/api/raceresult/exporter	Custom [Event.ID] & ";" & [RD_TimingPoint] &";"& [Bib] & ";" & [RD_Time]

RRexchange and IDCamPro use different local ports in order to be able to run side-by-side on the same computer.

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.

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.