A wireless LED clock you drive from a phone, a laptop, or an API.

For solo operators who want to roll the clock to a finish chute and run an event without any infrastructure, Bluetooth is the fastest path. Pair time is around three seconds. Latency from button press to LED change is around eight milliseconds, line of sight. Range is roughly thirty meters with reliable reception inside metal-frame trailers and broadcast trucks.

The bluetooth clock pairing uses BLE 5.2 with bonded connections, so reconnection after a brief signal loss is automatic. RSSI is reported live on the control surface so you can see your link quality before you commit to running the gun start.

For whole-venue access — broadcast graphics on the LAN, multiple operators in different rooms, integration with event management software — the wifi digital clock mode joins your venue's existing Wi-Fi network. Latency runs 10–20 ms on a clean LAN; operator count is bounded only by the network. Configuration data is encrypted in transit; each operator has token-scoped access.

Wi-Fi mode lives alongside Bluetooth, not instead of it. You can hold a Bluetooth control surface in the trailer for start-of-day setup and switch to Wi-Fi at the broadcast booth without restarting the clock.

For timing companies wiring jClock into a chip system, the third path is a typed API. REST endpoints for configuration (mode, ceiling, start point, brightness, network). WebSocket for live state (current time, battery, signal, firmware). Each clock holds up to four simultaneous operators, and connections are token-scoped so a chip reader can drive the count while a director holds the pause button.

The API surface is versioned and ETag-tagged. Latency over the open internet is roughly forty milliseconds with a normal connection — fast enough for visible-to-the-eye feedback on a control surface.