Differences

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

--- software:timingunits:supportedunits [2023/02/02 13:10] – henrik
+++ software:timingunits:supportedunits [2024/10/02 07:47] (current) – external edit 127.0.0.1
@@ Line 5: / Line 5: @@
 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.
-|                        ^ Type  ^ Sync  ^ Replay ^ Remote  ^ Gun  ^ Notes ^
+|                        ^ Type  ^ Sync  ^ Replay ^ Remote  ^ Gun/impulse  ^ Notes ^
-^ Black Box     | P         | X          | X          | X                | X                   | [[https://blackboxtiming.com|Read more]]   |
+^ Black Box     | P         | X          | X          | X                | X                   | [[https://blackboxtiming.com/boxes|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)          |   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         |                      | Decoder with/without active extension, USB Timing Box and TrackBox supported. Remote Decoder 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    |          |           |                      | 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 21: / 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  =====