UWB Interface

11a - Interface Status

Indicates if the interface is running or stopped. When running the sniffer will be capturing packets

11b - UWB interface configuration

The ... menu next to each UWB interface contains five entries:

Load Default Settings – opens a preset picker with named configuration profiles (for example DS-TWR Android, DS-TWR iOS, and numbered Config ID presets). Applying a preset sets both the PHY and session configuration in one step, with a preview of the values before applying.

Timeline Grid – toggles the bottom-docked UWB slot timeline panel for this interface.

Show PHY errors – toggles display of PHY/RX error frames (FCS/STS/CIA errors). Off by default; when errors are present a Corrupt Frames counter appears in the packet list footer.

UWB Config – the PHY configuration described below.

Session Config – the session configuration described below.

The UWB Phy configuration

prf_mode: BPRF 62.4 MHz, the standard FiRa mode used by the iOS and Android DS-TWR configurations and the default. HPRF 124.8 MHz and HPRF 249.6 MHz are FiRa's optional higher-rate modes; they are greyed out on boards whose radio does not support HPRF, which today is every board except the Murata Type2BP.
channel: Supported channels: 5 and 9.
data_rate: UWB data rate index (850 kbps / 6.8 Mbps). With HPRF: 6.81, 7.80, 27.2 or 31.2 Mbps.
tx_preamb_len: Preamble length index (value depends on PRF and mode). With HPRF: 32 or 64 symbols.
rx_pac: PAC size (0 = 8 symbols, 1 = 16, 2 = 32, etc.).
tx_code: TX preamble code
rx_code: RX preamble code. With HPRF: 25 to 32.
sfd_type: Standard (IEEE) or non-standard SFD. With HPRF: 802.15.4z.
phr_mode / phr_rate: PHR configuration for packet headers.
sfd_timeout: Maximum SFD search window.
sts_mode: STS (Scrambled Timestamp Sequence) mode.
sts_length: Number of STS segments.
pdoa_mode: PDoA (Phase Difference of Arrival) mode.

Selecting HPRF switches these lists to the HPRF values and greys out the settings HPRF does not use. 27.2 and 31.2 Mbps, and PRF 249.6 MHz, are accepted by the current Type2BP firmware but have not received any traffic on the bench; the dialog warns when you pick one.

Session Configuration

session_id (optional): The ranging session identifier. If null, the sniffer

accepts any session ID seen over the air.

controller_address (optional): The MAC address of the UWB session controller.

Null means do not restrict capture to a specific controller.

controlee_addresses (optional): The list of UWB devices acting as controlees.

Null means capture all controlees.

slots_per_round: Number of time slots available in each ranging round.
ranging_round_usage: Defines how the ranging round is structured (for example

two-way ranging, TDoA patterns, etc.).

sts_config: Configuration of the Scrambled Timestamp Sequence (STS). Controls

if and how STS is applied.

multi_node_mode: Indicates whether the session supports multi-node ranging or

only a single controller–controlee pair.

slot_duration: Duration of each slot in microseconds.
mac_fcs_type: Type of MAC frame check sequence (checksum) used.
rframe_config: Selects the ranging frame configuration (RFRAME type) which

determines modulation and frame format.

preamble_code_index: The preamble code used for both transmitting and

receiving.

sfd_id: Identifier for the Start-of-Frame Delimiter (SFD) type.
psdu_data_rate: Data rate used for the PSDU (payload). Common rates are 850

kbps and 6.8 Mbps.

preamble_duration: Duration of the UWB preamble.
channel_number: The UWB channel used when deriving session keys (part of the

session key digest).

constant: Fixed digest constant (must be 0x03).
digest_session_id: Session ID used in the session key digest.

The session information is required to decrypt the packets. Currently only Static STS encryption is supported: Dynamic STS and Provisioned STS are not yet implemented, and CCC Digital Key frames are recognised but not decrypted.

The session_id, controller_address and controlee_addresses are optional and will be learned from packet capture. When used with a mobile phone, these parameters will be random and hence cannot be known before the ranging session has started.

If session_id, controller_address and controlee_addresses are not entered the packet sniffer will decrypt, decode and display all sessions that matching the configuration.

In certain use cases the session parameters can be extracted from the BLE data. Support for this is currently limited. For more information contact us at contact@bluwbee.com.

11c - Start and Stop the sniffer

This allows the user to start and stop a specific sniffer interface

Tips

If the sniffer status is started but no packets are being displayed in the preview list check:

There are no active filter filtering expected packets
The session and phy configuration is set correctly for the expected UWB

ranging session