Wiki

Technical reference for system integrators and engineers.

BLE Ext Advertising

Sensor telemetry does not have to travel over UWB. The same Sensor TLV payload can ride BLE extended advertising, broadcasting connectionless to any listener in range.

No ranging session, no pairing — a phone, a gateway or an observing anchor can receive telemetry without joining a UWB schedule.

One payload, two carriers

Sensor TLV payload identical bytes either way UWB sensor-data frame frame type 0x25 inside a TDMA sensor slot BLE extended advertising connectionless broadcast any listener in range sensor carrier — parameter 0x7C 0 = UWB frames · 1 = BLE ext advertising
Only the envelope changes. A record broadcast over BLE and the same record delivered over UWB decode through exactly one code path.

Requirements

Extended advertising with a full sensor payload needs a BLE controller and stack that support extended advertising. Devices with that capability can transmit or receive the BLE ext-adv sensor carrier; the receive (decode-and-forward) path lets an anchor aggregate telemetry broadcast by nearby tags.

The advertising PHY and TX power are themselves runtime parameters (0x81, 0x82), so range and robustness are tunable per deployment without a firmware change:

ParameterIDValues
Sensor carrier0x7C0 = UWB frames, 1 = BLE ext advertising
BLE advertising PHY0x810 = 1M, 1 = Coded (long range)
BLE TX power0x82int8, dBm

Why a second carrier

BLE ext advertising reaches listeners that are not part of a UWB TDMA schedule. Because it reuses the Sensor TLV format unchanged, adding it cost no new record definitions and no second decoder — the format follows the transport, but the payload does not change.

The Coded PHY trades data rate for range; the 1M PHY provides the higher rate.