User Guide

Start from the Scanner tab to discover nearby Bluetooth devices and pick a target quickly.

• Scan controls (stop / play / fast), search box, and filter chips.
• Device cards with name, manufacturer, battery, and online state.
• Direct Connect action for each device.

• Use fast scan during discovery, then switch to normal scan to reduce noise.
• Filter by Named or Favorites when too many devices are present.
• Tap Connect on your target device to enter interrogation flow.

After connection, this page gives a full status snapshot and all discovered services/characteristics.

• Signal, connection state, service count, and quick actions (Export/Broadcast/Navigation).
• Service sections with characteristics you can inspect and debug.
• AI diagnostics entry point for one-click analysis.

• Confirm connection is healthy before writing payloads.
• Open a characteristic row to enter read/write debug mode.
• Use Broadcast when you need raw advertising details from the same device.

Apply a project-friendly alias so your team can identify test units instantly.

• Edit Device Name dialog with restore and save controls.
• Keyboard input for quick alias updates on-site.

• Use naming convention like LineA-Node03 or AirPods-Test-01.
• Tap Restore Original if you need to match manufacturer naming again.
• Save before exporting logs so reports remain consistent.

The core terminal for payload write/read verification across HEX, Text, Binary, and Decimal modes.

• Send mode selector and payload input area.
• Live send output with ACK/write verification feedback.
• Receive mode section and quick actions: Select Packet / Send.

• Pick an encoding mode matching your firmware protocol.
• Send a known safe command first to confirm path integrity.
• Review output text to validate write success and expected response.

Reuse saved command packets to avoid manual retyping and improve regression consistency.

• Bottom sheet packet picker with packet name, payload, and mode.
• Quick add entry point for creating new reusable packets.

• Define packets for handshake, version check, and diagnostics.
• Use packet names that encode intent, for example auth init.
• Combine with Step 8 logs to compare packet outcomes across builds.

Use signal-aware navigation assistance when you need to physically locate the connected device.

• Map context with target marker and live progress indicator.
• Distance, mode, and real-time status panel.

• Walk slowly and monitor signal/percentage trends.
• If signal drops, rotate and re-approach from another direction.
• Tap Found when target confirmation is complete.

Maintain a clean command library for team-wide reuse and quick test setup.

• Packet list by name and mode, plus add button.
• A dedicated tab to centralize command management.

• Create one packet set per firmware feature area.
• Keep packet names short but explicit for faster lookup.
• Review stale packets after protocol revisions.

Track every key event in one place: scanning, connection, writes, reads, and diagnostic outputs.

• Timestamped rows with level tags (INFO / CONN / etc.).
• Clear, Export, and mode controls for practical analysis.
• AI Insights entry at the bottom for instant summary.

• Export logs right after reproducing an issue.
• Mark key commands in packet names to correlate log events faster.
• Use clear before a fresh test run to isolate noise.

Convert raw communication history into actionable hints for protocol and pairing troubleshooting.

• Device context, log sample size, and protocol hint card.
• Confidence score to help prioritize next debugging actions.

• Read AI hints after at least one full connect/read/write cycle.
• Use confidence score as guidance, then validate against raw logs.
• Apply recommendations, rerun packet tests, and compare outcomes.