LedgeLink — Wireless Sensor Gateway for CAN

Put the driver into the telemetry stream

Driver heart rate on the CAN bus.

LedgeLink receives compatible Bluetooth Low Energy heart-rate data and broadcasts it directly onto the racecar CAN network, ready to display, log, and analyze alongside vehicle telemetry.

Plug it in. LedgeLink does the rest. Connect power, ground, CAN-H, and CAN-L. There is no device menu to manage, no conventional Bluetooth pairing, and no phone or companion app in the in-car data path.

LedgeLink signal flowA heart-rate wearable sends data over Bluetooth Low Energy to LedgeLink, which publishes it to the vehicle CAN bus for a dash, logger, or telemetry system. Heart-rate wearableStandard BLE HRSCAN busRacecar networkDash / loggerTelemetry system LedgeLinkTelemetry interface
Heart-rate wearable → LedgeLink → CAN bus → dash, logger, or telemetry system.

Driver telemetry

Your driver generates data too.

Race teams collect enormous amounts of information about what the car is doing. LedgeLink adds another channel: what the driver is doing.

01 / Receive

Standards-based BLE

Receives the Bluetooth SIG Heart Rate Service (0x180D) and Heart Rate Measurement characteristic (0x2A37) from compatible wearables.

02 / Broadcast

Direct to CAN

Places BPM and source-validity data onto the car's CAN network without routing the live data through a phone.

03 / Analyze

One telemetry timeline

Display or log heart rate beside lap, engine, chassis, and other vehicle channels supported by your dash or logger.

Wearable compatibility

Built around the standard heart-rate service.

LedgeLink should work with monitors, watches, chest straps, and other wearables that expose the standard Bluetooth Low Energy Heart Rate Service. Some watches require a “Broadcast Heart Rate” or similarly named mode. Devices using proprietary Bluetooth-only protocols may require specific support.

Hands-off in normal operation. LedgeLink discovers, selects, and reconnects to supported devices automatically. Once installed, the driver does not configure LedgeLink, pair devices, open an app, press a button, or select a source before driving.

Physically tested

Garmin Fenix 8 Pro

With heart-rate broadcasting enabled, LedgeLink received the standard BLE heart-rate measurement and placed BPM on CAN.

Because LedgeLink listens for the standardized Bluetooth SIG Heart Rate Service, it should also work with any compatible BLE wearable that broadcasts heart rate using that service. Some devices may require their heart-rate broadcast mode to be enabled.

Physically tested

HandPlus B2 / Chileaf S332

In addition to BPM, LedgeLink can place the wearable's additional temperature channels, BODY_TEMP field, and battery level onto CAN for logging and analysis.

Each HandPlus also supplies a unique six-byte HRM identifier that LedgeLink transmits with the heart-rate message. Assigning a HandPlus to a driver lets the wearable identify that driver's heart-rate source in logged CAN data.

Buy the tested HandPlus B2 on Amazon (opens in a new window)

The precise meanings of the proprietary TEMP1 and TEMP2 channels have not yet been conclusively established.

Endurance racing

Automatic driver identification.

LedgeLink has been tested with the MOKO driver-ID wristbands and pucks used with Flagtronics in endurance-racing environments, including WRL and ChampCar. It can place the detected six-byte driver identifier, signal strength, and validity onto CAN so logged telemetry can follow the active driver during driver changes without manual selection.

Two useful identification paths. A supported Flagtronics-style tag identifies the active driver independently of the heart-rate monitor. A HandPlus wearable also carries its own identifier in the LedgeLink heart-rate frame, allowing a team to associate that assigned wearable with its driver in logged data.

CAN integration

Four wires. Documented messages.

The purpose-built board is designed for 12 V racecar installation with +12 V, Ground, CAN-H, and CAN-L. It connects to an existing, properly terminated CAN bus and does not add permanent bus termination.

Factory-default CAN message map
CAN IDMessagePeriodContents
0x720DriverTag200 msDriver ID, RSSI, validity
0x721HeartRate200 msHRM ID, BPM, source and validity
0x722HandPlus200 msTemperature channels, BODY_TEMP, battery, validity
0x723ModuleHealth1000 msInternal module die temperature and validity

Factory-default configuration works out of the box on a matching network: base ID 0x720, standard 11-bit CAN 2.0, 1 Mbit/s. CAN base address, bitrate, and message periods remain configurable for other installations.

Production status

Purpose-built hardware is in progress.

The dedicated production PCB is in fabrication. When the first boards arrive, they will move through electrical, RF, CAN, enclosure, harness, and in-car validation before release.

  • Production PCB in fabrication
  • 12 V vehicle architecture
  • Electrical and RF validation next
  • Harness, enclosure, and in-car validation to follow

LedgeLink launch updates

Join the product-specific list for availability information and product updates.

Motorsport telemetry only. LedgeLink is intended solely for motorsport telemetry and informational use. It is not a medical device and must not be used for diagnosis, treatment, medical monitoring, or safety-critical decisions.