This guide is applicable for users who will be utilizing Loop Boxes at splits points.
***Loop Boxes either repeat or store/dump data to another decoder. When exported, the DecoderID that pushes out is the decoder receiving the data, not the LoopBoxID. This manual will help the timer set up RaceResult12 to push the LoopBoxID if an active timing system is being used***
There are 2 changes necessary to make this work:
Setting Up the User Defined Files
Navigate to the Main Window Tab in RR12
Click Participant Data
Select User Defined Fields/Fcts.
Add the following User Defined Fields
First
Name: LoopBoxDevice
Expression: choose([RD_ChannelID];[CH1];[CH2];[CH3];[CH4]; [CH5];[CH6];[CH7];[CH8])
Second
Name: CH1
Expression: choose([RD_LoopID];1;2;3;4;5;6;7;8)
Third
Name: CH2
Expression: choose([RD_LoopID];1;2;3;4;5;6;7;8)
Fourth
Name: CH3
Expression: choose([RD_LoopID];1;2;3;4;5;6;7;8)
Fifth
Name: CH4
Expression: choose([RD_LoopID];1;2;3;4;5;6;7;8)
Sixth
Name: CH5
Expression: choose([RD_LoopID];1;2;3;4;5;6;7;8)
Seventh
Name: CH6
Expression: choose([RD_LoopID];1;2;3;4;5;6;7;8)
Eighth
Name: CH7
Expression: choose([RD_LoopID];1;2;3;4;5;6;7;8)
Ninth
Name: CH8
Expression: choose([RD_LoopID];1;2;3;4;5;6;7;8)
Rename each Loop on the appropriate CH (channel) line with your corresponding LoopBoxDevice name with “ “ on either side.
Ex: Channel2, Loop1 is “A2220” which is an active extension
Please note: if an active extension is being used, the exporting format set up in step 2 will remove the DecoderID and replace it with the LoopBoxDevice. This means you will need to set up a stream in RaceDay Scoring for the Active Extension.
Ex: Channel2, Loop2 is “A2287” which is a LoopBox repeating back to CH2L1
Ex: Channel5, Loop1 is “A2144” which is a USB Box
Setting up the Exporter (TCP/IP):
Navigate to the Timing tab in RR12
Click Exporters + Tracking
Add a TCP/IP Exporter
Name: Anything you’d like…DIRECT is perfect
Timing Point: <All Timing Points>
Filter: Blank
Export Data: Custom
Custom Field:
[RD_ID] & ";" & if([RD_Transponder]<>"";[RD_Transponder];[RD_IDBib]) & ";" & date("yyyy-mm-dd") & ";" & format([RD_Time];"hh:mm:ss.kkk") & ";" & [RD_OrderID] & ";" & [RD_Hits] & ";" & [RD_RSSI] & ";;" & if([RD_LoopID]>0;1;0) & ";" & [RD_ChannelID] & ";" & [RD_LoopID] & ";;" & [RD_WakeupCounter] & ";" & ([RD_Battery]/10) & ";" & ([RD_Temperature]-100) & ";" & [RD_StatusFlags] & ";" & if([RD_LoopID]<1;[RD_DecoderID];[LoopBoxDevice])
The underlined/bolded section says that if the LoopID is less than 1 (meaning 0), then the DecoderID will be exported, if there is a LoopID present then it will use the LoopBoxDevice which is defined in the User Defined Fields. For track boxes (active and passive) there is a channel, but no loop, so the Device ID will be used. This allows the user to set and forget the exporter, as this exporter will also work with passive systems as the decoder name will populate as needed.
Destination: TCP/IP
IP/Server Name: localhost
Port: 3601
LineEnd: CRLF
Save Settings
The same process for TCP/IP exports should be used for file exports.