Differences

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

--- software:timingunits:supportedunits [2022/03/18 09:01] – [race|result remote] henrik
+++ software:timingunits:supportedunits [2024/10/02 07:47] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 {{indexmenu_n>2}}
-====== Supported units ======
+====== Supported timing devices ======
-Below is listed the types of units that can currently be connected to directly from the software.
+The BBT timing software is compatible with most common open timing software and hardware. Below is a constantly growing list of timing hardware which are fully supported by the BBT timing software. Please contact us if your timing device is not on the list, as we are happy to see if it can be added.
-We are happy to add more unit types to the list. Contact us for more information or to request support for a specific unit type.
+|                        ^ Type  ^ Sync  ^ Replay ^ Remote  ^ Gun/impulse  ^ Notes ^
+^ Black Box     | P         | X          | X          | X                | X                   | [[https://blackboxtiming.com/boxes|Read more]]   |
-|                        ^ Type  ^ Sync  ^ Replay ^ Remote  ^ Gun  ^ Notes ^
-^ Black Box     | P         | X          | X          | X                | X                   | [[https://blackboxtiming.com|Read more]]   |
 ^ Ipico Elite     | P         | X           | X         |                 | X                   | Replay stops timing temporarily |
 ^ Ipico Lite       | P         | X           | X         |                 |                     | Replay via file |
 ^ 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)          |   X                  | Requires external software in most cases (T&S). 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 API key* |
 ^ Trident Time Machine | P/A  | X    | X         | X          | X                     |   |
 ^ SPORTident | A  |     | (X)         | (X)          |                     | Works via plugin added to SPORTident ReaderUI*  |
 ^ Impinj reader | P  | X    |          |           |                      |   |
-^ Zebra/Motorola RFID reader | P  | X    |          |           |                      |   |
+^ Zebra/Motorola RFID reader | P  | X    |          |           |                      | LLRP and TCP connection methods supported. |
+^ Feibot | P/A  | X    | X        |           |  X                    | U, P and Q series devices  |
+^ Generic | P/A  |     |         |           |                      | Generic TCP connection support for custom devices and integrators. [[tcpimporter|Read more]]  |
 Type: (P)assive and (A)ctive systems\\
@@ Line 24: / Line 23: @@
 Replay: Can the unit be replayed after e.g. a network failure?\\
 Remote: Can we receive readings from the unit via a cloud-service?\\
-Gun: Can the software detect start pistol/marker impulses from the unit?\\
+Gun/impulse: Can the software detect start pistol/marker impulses from the unit or connected devices such as pressure sensors or photo cells?\\
+===== Impulse triggers (photo cells, pressure sensors etc.) =====
+On some device types you can attach external hardware for triggering impulses, such as a pressure sensor for cycling time trial races.
+These impulses can be configured in the software and be paired with a "spotter" device, which will tell the software which participant said impulse is triggered by.
 ===== 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):\\
-//raceresult.apikey//\\
-You can find or create this API key when logging into the race|result online portal.
+For BBT to connect to the remote units, you need to create an API key and give this key to BBT.
-After changing settings, please restart the timing server and the option will appear.
+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.
-Optionally, you can have your login automatically added to all the BBT installations belonging to your license. Contact us for more information on this.
+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.
+  - 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 44: / Line 48: @@
 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).