Practical reference for configuring and understanding the three Socket export protocols available in TsConnector for timing devices.
Contents
Overview
TsConnector can stream live timing using different Socket export protocols.
Each protocol is designed for a specific type of scoring or analytics software. Make sure to select the protocol expected by the downstream system.
All protocols are configured from the Socket Export window. The selected Protocol determines which configuration fields are available.
This is the protocol to use:
TsV1
Use this if you have already migrated from TSConnector 1 to TSConnector 2. This version is backward compatible with the previous TSConnector.
TsV2
Recommended for new integrations. It is the preferred protocol for building from scratch.
CTP01
Select this if you will be working with Runscore or RaceDay.
Available protocols
| Protocol | TsV1 | TsV2 | CTP01 |
|---|---|---|---|
| Role | Server (fixed) | Server or Client | Client (fixed) |
| Wire format | JSON, numeric tag | Enriched JSON | protocol compatible with programs such as Raceday or Runscore text (~ separated, CRLF) |
| Typical use | Legacy integrations | Modern integrations | -compatible software as Raceday or Runscore |
| Connection handling | Server always listening | Auto-reconnect in Client mode | Reconnect with resume |
Read types
| Type | Name | Description |
|---|---|---|
| 0 | Wave / gun time | Reference events such as wave start or gun signal |
| 1 | First-seen | Immediate detection, low latency, not recommended for official timing |
| 2 | Best-seen | Optimized detection, recommended for official results |
Common configuration fields
| Field | Description | Applies to |
|---|---|---|
| Protocol | Selects TsV1, TsV2, or CTP01 | All |
| Role | Server or Client mode | TsV2 |
| Host | Target host or IP address | TsV2 Client, CTP01 |
| Port | TCP port | All |
| Filter read type 1 | Excludes First-seen reads | All |
| Use UTC time | Emits timestamps in UTC | CTP01 |
TsV1 – Legacy JSON
TsV1 is the historical Socket export format. It is intended for systems that require numeric tags.
Role
- Server only
- TsConnector listens on the configured port
- Scoring software connects as a TCP client
Message format
JSON array terminated by a carriage return (\r).
[{"Chip":123456,"Moment":"2026-04-22T10:15:42.1234567Z","TimingPoint":"Finish","Type":2,"Antenna":2,"Source":"Reader-01"}]
TsV2 – Enriched JSON
TsV2 is the recommended modern format. It supports alphanumeric tags and provides extended metadata.
- Local and UTC timestamps
- RSSI (signal strength)
- Full EPC
- Server and Client modes
CTP01 – Chronotrack protocol
CTP01 is a stateful, text-based protocol widely supported by Chronotrack-compatible scoring software.
- Command-based handshake
- Push and pull modes
- Automatic reconnect with resume
Resilience and reconnect
- Automatic TCP reconnect
- Bounded internal buffer
- Persistent connection identity (CTP01)
Troubleshooting
No data received
- Verify Host and Port
- Check firewall rules
- Confirm Server / Client roles
Incorrect timestamps
- TsV1 and TsV2 use local time by default
- In TsV2, use UtcMoment for UTC processing
- In CTP01, review the Use UTC time option
Comments
Article is closed for comments.