Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
software:timingunits:supportedunits [2022/04/05 06:56]
henrik [Supported timing units]
software:timingunits:supportedunits [2022/08/03 09:01] (current)
henrik [SPORTident]
Line 11: Line 11:
 ^ RFID Timing Ultra       | P         | X           | X                                              | ^ RFID Timing Ultra       | P         | X           | X                                              |
 ^ MyLaps | P/A  | (X)   | (X)         | (X)          |                    | Requires external software in most cases. Units supporting P3 protocol works with no additional software.  | ^ MyLaps | P/A  | (X)   | (X)         | (X)          |                    | Requires external software in most cases. Units supporting P3 protocol works with no additional software.  |
-^ race result | P/A  | X   | X         | X                              | Remote requires race result login* |+^ race result | P/A  | X   | X         | X                              | Decoder with/without active extension, USB Timing Box and TrackBox supported. Remote Decoder requires race result login* |
 ^ Trident Time Machine | P/A  | X    | X         | X          | X                       | ^ Trident Time Machine | P/A  | X    | X         | X          | X                       |
 ^ SPORTident | A  |     | (X)         | (X)          |                     | Works via plugin added to SPORTident ReaderUI*  | ^ SPORTident | A  |     | (X)         | (X)          |                     | Works via plugin added to SPORTident ReaderUI*  |
Line 24: Line 24:
  
 ===== race|result remote  ===== ===== race|result remote  =====
-To use race|result remote, you must have a race|result website login and your units must be set to upload to your customer ID.+To use race|result remote, you must have a race|result website login and your units must be set to upload to your race|result customer ID.
  
-For BBT to connect to the remote units, you need to enter a race|result API key into an advanced setting (server settings or event-specific settings):\\ +For BBT to connect to the remote units, you need to create an API key and give this key to BBT.
-//raceresult.apikey//\\+
  
-You can find or create this API key when logging into the race|result online portal.+You can find or create this API key when logging into the race|result online portal (Account -> Customer Area -> API keys in the left menu). 
 +Enter an arbitrary title so you can remember what the key is for (such as Black Box Timing), and click the Generate-button. You can then click the Show-icon to reveal the API key.
  
-After changing settings, please restart the timing server and the option will appear. +You now have two options: 
- +  - Enter the API key into an advanced setting (server settings or event-specific settings) called //raceresult.apikey//After changing settings, please restart the timing server and the option will appear. 
-Optionally, you can have your login automatically added to all the BBT installations belonging to your license. Contact us for more information about this option.+  - You can have your key automatically added to all the BBT installations belonging to your license. Contact us for more information about this option.
  
  
Line 41: Line 41:
 You then select the Black Box Timing plugin in ReaderUI, and it will open a connection to BBT, where you can add the units. You then select the Black Box Timing plugin in ReaderUI, and it will open a connection to BBT, where you can add the units.
  
-Please note that the units will only show up in BBT after the first punch readout, but you can use the "ALL" unit (possibly with an antenna/codenumber filter).+Please note that the units will only show up in BBT after the first punch readout, but you can use the "ALL" unit (optionally with an antenna/codenumber filter).