Race Timing System: Connect the FX9600

Connect the FX9600

Zebra's HTTP POST guide specifies FX9600/FX7500 firmware 3.10.x or later. Confirm your firmware and IoT Connector availability before setup. This kit accepts documented SIMPLE/INVENTORY single-tag events, individually or as a JSON array. Other modes, compressed payloads, and alternative batching envelopes are rejected rather than guessed. Disable envelope batching for initial testing and use per-read events with timestamps.

Use the FX9600 web interface: Communication → Zebra IoT Connector → Configuration → Add Endpoint → HTTP POST. Configure the Tag Data Interface to use that endpoint. Set Basic authentication to the same username/password as the receiver. Import the receiver's CA certificate into the reader and enable peer/host verification for HTTPS.

Receiver endpoint for a reader named fx9600-main:

https://YOUR_TIMING_COMPUTER:8765/reads/fx9600-main

The computer and reader must have a reachable network path. Create/use a server certificate matching the computer's DNS name or IP and supply the certificate chain plus private key below. Certificate issuance is environment-specific; the kit does not disable reader certificate verification.

Set environment variables in the process running the receiver:

• ZEBRA_TIMING_USER: Basic-auth username, defaults to reader.
• ZEBRA_TIMING_PASSWORD: your receiver password, at least 12 characters. This is separate from your Sports Hub API key.

Run explicitly in the foreground:

python3 zebra_timing.py --config my_meet.json --db my_meet.sqlite3 serve --bind 0.0.0.0 --cert server-cert.pem --key server-key.pem

Open https://YOUR_TIMING_COMPUTER:8765/ and authenticate to view the dashboard. Press Ctrl+C to stop. LAN listening requires HTTPS; loopback-only testing can use the default HTTP listener (serve without bind/cert/key). Do not point the reader at 127.0.0.1: that address refers to the reader itself, not the computer.

Start tag reading through the reader's controls. Enabling the endpoint does not itself start RF inventory. HTTP 200 acknowledges durable database insertion, not final acceptance of a race result. HTTP 422 means the payload or configured reader/antenna is unsupported/invalid; do not ignore it. The app only captures data; it does not remotely change RF power, antenna settings, firmware, or start/stop inventory.

Example accepted payload:

{"type":"SIMPLE","timestamp":"2026-10-10T13:00:01.000Z","data":{"format":"epc","idHex":"300000000000000000000001","antenna":1,"peakRssi":-45,"reads":1}}

The configured URL identifies the reader; the timestamp identifies read time. Network receipt time is archived separately and is never used as finish time. Reader clocks and the gun-start clock must be synchronized. Configure/read-test the reader before the race; sample payload compatibility does not establish physical timing accuracy.