BoardBridge Console

Device

Statusdisconnected
Name—
Config (0x0005)—

Decoded state (0x0002)

—

Raw CTS bytes (0x0003)

802.15.4 frame

The firmware injects whatever PSDU we build — so this page owns the whole frame. If no FCF works, the scoreboard's XBee is likely in Digi mode (MM=0/3) and expects a MaxStream header; the fix is to set that XBee to MM=2 (strict 802.15.4), not to guess. See Help.

Payload

These exact bytes already drove this console to Game 7:00.00 / Shot 30.00 / Score 1–0. Zero encoder risk — if the board reacts, connectivity + FCF are proven. Sent as … chunked frames.
PSDU: —

TX log

Scoring emulator

Drives the board with no console attached. This page ticks the clocks and injects module readouts wrapped in the Frame Lab FCF + address mode currently selected. (Eventually the ESP32 itself will own the tick — this is the software stand-in.)
Game
7
:
0
0
.
0
0
Shot
3
0
.
0
0
Modules driven

Scan — find the network (BoardBridge-Polo)

Three ways to hunt for the scoreboard's radio without a WA-3, all on the connected board-bridge C6. Survey hears anything transmitting. Sweep drives a readout across channels/PANs so you can watch the board react. Probe pings for a silent receiver. Needs firmware with the radio-control char (0x0006).
Radio controlnot connected

1 · Passive survey (find transmitters)

Hops each channel in promiscuous mode and tallies every frame + PAN ID it hears. A receive-only scoreboard XBee stays silent here — this finds a live WA-3, an XBee in TX, or other 15.4/Zigbee nets.
Now scanning—

2 · Behavioral sweep (find the board)

Steps through channel × PAN, transmitting a readout on each so you can watch the physical board light up — the definitive "it's listening here" test, no address guessing. PAN goes in the frame; the channel is retuned on the C6.
idle

3 · ACK-probe (find a silent receiver) experimental

Sends a unicast frame with the ACK-request bit set; a powered, address-matched 15.4 receiver auto-ACKs in hardware. Only works if the target XBee ACKs (MM=1/2) and you know its short address — so treat a no-ACK as inconclusive, not proof of absence.

Sniffer (BoardBridge-Sniffer)

Flash a spare C6 with tools/sniffer and connect to it to see raw 802.15.4 frames on a channel. Only shows traffic if something is transmitting — a WA-3, an XBee in transparent TX, or another C6 running board-bridge. A receive-only scoreboard XBee is RF-silent.
Sniffer servicenot connected

Captured frames

What this is

Bench remote for the ESP32-C6 board-bridge — a DIY Colorado Time Systems WA-3 replacement. It talks BLE to the C6, shows the decoded scoreboard state and raw CTS bytes, and (via the firmware's inject characteristic 0x0004) lets you put arbitrary 802.15.4 frames on the air to drive a scoreboard directly.

Resolving the FCF without a WA-3

You have no WA-3 on the console side, so the scoreboard itself is the oracle:

  1. Replay the real capture (Frame Lab → Replay) with FCF 21 08. Watch the board.
  2. No reaction → try candidate 01 08 (spec broadcast, ACK-request clear), then 41 48 (source + PAN-compression).
  3. Still nothing → the scoreboard XBee (S1) is almost certainly in Digi mode (MM=0 default or MM=3) and drops frames without a MaxStream header. Set that XBee to MM=2 (802.15.4 with ACKs) or MM=1 (no ACKs) via XCTU, then raw frames land.

Channel vs module

The console's serial protocol is module-addressed; the "channel" (1–21) is a UI label it maps to a module internally. Our decoder recovers the module number directly. Default addressing here is module; the toggle lets you prove that against the real board. Game=module 0x01, Shot=module 0x13.

Requirements

Chrome on Android (or desktop Chrome/Edge) over https (or localhost / a trusted file). Grant Bluetooth (and, on Android, nearby-devices/location) when prompted. iOS Safari has no Web Bluetooth.