The bridge between a timing device and the events that receive its reads
Every time a timing device reads a tag, that read must be delivered to a destination: an event, a set of Commentators, or third-party timing software. An export determines where those reads are sent.
What is an export?
An export is a destination connection within TSCloud. Its purpose is to determine where reads generated by a timing device should be sent.
When a timing device (TS2+, TS3, or any other compatible device) detects a tag, it generates a read. That read must be associated with a specific event in order to have meaning.
The export is the mechanism that routes those reads to the appropriate software or service.
An export is not a concept specific to copernico. It is a TSCloud concept, acting as the layer responsible for distributing reads between devices and destinations.
How is an export created?
Exports are created from copernico or TSConnector.
During configuration, the export is associated with a Timing Point, indicating where reads from a timing device should be delivered.
A Timing Point can represent:
- Start
- Finish
- Intermediate split point
- Any other timing control point
| Platform | Typical Use |
|---|---|
| copernico | Events and tools such as Commentators |
| TSConnector | Integration with third-party timing software |
N-to-N relationship between devices and destinations
The relationship between devices and destinations is a many-to-many (N-to-N) relationship.
- A single timing device can have multiple active exports at the same time.
- A single destination can receive reads from multiple timing devices.
Practical example
The timing device TS2+ 1 can simultaneously have:
- An export to an event in copernico.
- An export to a set of Commentators in copernico.
- An export to an event managed through TSConnector.
All reads generated by that device can be sent through all these exports simultaneously.
Likewise, another timing device can also point to one or more of those same destinations without causing any conflicts.
Exports are not exclusive. Multiple devices can send reads to the same destination, and a single device can send reads to multiple destinations at the same time.
What cannot be done from Device Exports
From the Device Exports view in my.timingsense.com, it is not possible to create or delete exports.
This view is intended exclusively for monitoring and operating on exports that have already been configured.
From Device Exports, customers can:
- View configured exports.
- Review status, type, and date range.
- Enable or disable exports (Enable / Disable).
- Download reads in CSV format.
Export creation and deletion are always performed through copernico or TSConnector.
Device Exports allows you to see where reads from a timing device are being sent.
Device Telemetry allows you to analyse the activity and historical behaviour of the device itself.
Quick summary
| Question | Answer |
|---|---|
| What is an export? | A TSCloud connection that routes reads to a specific destination. |
| Where is it created? | In copernico or TSConnector. |
| Can a timing device have multiple exports? | Yes. The relationship is N-to-N. |
| Can customers create or delete exports from my.timingsense.com? | No. They can only view, enable, disable, and export reads. |
Comments
Article is closed for comments.