viewof defbBtMode = Inputs.select(["BLE peripheral advertising", "BLE observer / beacon scan", "BR/EDR inquiry"], {label: "Discovery family", value: "BLE peripheral advertising"})
viewof defbBtAdvInterval = Inputs.range([20, 2000], {value: 250, step: 10, label: "Advertising or inquiry opportunity interval (ms)"})
viewof defbBtScanInterval = Inputs.range([10, 2000], {value: 300, step: 10, label: "Scan interval (ms)"})
viewof defbBtScanWindow = Inputs.range([5, 1000], {value: 60, step: 5, label: "Scan window (ms)"})
viewof defbBtPermission = Inputs.select(["Granted and foreground", "Granted with background policy", "Denied or unavailable"], {label: "Application permission state", value: "Granted and foreground"})
viewof defbBtPairing = Inputs.select(["No pairing; public beacon data only", "Pair then authorize GATT access", "Bond and test reconnect", "BR/EDR pair then discover SDP profile"], {label: "Trust and service route", value: "Pair then authorize GATT access"})Discovery And Pairing Explorer
Discovery And Pairing Explorer
animation
bluetooth
ble
protocols
Try Keep Scan window (ms) at 60 and Scan interval (ms) at 300. Change Application permission state from Granted and foreground to Denied or unavailable.
Observe The defaults show Receiver scan duty of 20.0% and a Coarse discovery planning horizon of 550 ms plus unmodelled delays. Selecting Denied or unavailable changes the heading to a blocked-discovery warning while those numbers stay the same.
Explain Receiver scan duty divides the smaller of the scan window and interval by the interval: 60 / 300 gives 20.0%. The planning horizon adds the opportunity interval to the scan interval: 250 + 300 gives 550 ms.
Technical boundaries. The arithmetic assumes the effective scan window cannot exceed the scan interval. Random delay, interference, scheduling, and retries are named in the output but never simulated. Permission and trust selections provide displayed evidence; the tool does not perform device discovery, pairing, or service authorization.
Discovery And Pairing Explorer
Start by naming the protocol family. BR/EDR inquiry and SDP, BLE advertising/scanning and GATT, and Bluetooth Mesh provisioning are different procedures. Do not use “beacon,” “pairing,” or “service discovery” as if they identify the same packets or security state.
For BLE, the primary advertising channels are 37, 38, and 39. They create discovery opportunities; they do not prove that every channel was heard or that the later connected data-channel map is healthy. Once connected, the link layer uses data channels and adapts its channel map. A review therefore keeps advertising visibility, connection establishment, pairing/bonding, GATT discovery, authorization, and sleep/reconnection as separate evidence rows.
Run the explorer twice with the same radio settings but different permission state, then with a shorter scan window. This separates an application-policy failure from a radio-duty-cycle trade-off. In the bench record, capture controller and OS versions, advertised identity and privacy behavior, channels observed by a sniffer, scan policy, permission prompt and denial path, pairing method, service/profile discovery, authorization result, current trace, reconnect after sleep, bond deletion, owner transfer, and factory reset.