ZeroTrace Companion
Connection Settings
Default port, baud rate, auto-reconnect, AirLeak firmware mode, BLE active scanning, and custom device profiles.
The connection section controls how Companion talks to your devices over USB serial.
Default connection
| Setting | What it does |
|---|---|
| Last port | The COM port Companion was last connected to (used for auto-reconnect) |
| Baud rate | The default baud rate for new connections — typically auto-determined from the device type |
| Auto-reconnect | When enabled, Companion attempts to reopen the last connection on launch |
Last port
This setting is updated automatically whenever you successfully connect to a device. It enables the "Companion remembers" behaviour — open Companion, your usual device is connected, and you're ready to work.
Baud rate
For known devices, Companion picks the right baud rate automatically:
- ZeroTrace HID and BLE Logger: 115,200.
- ZeroTrace AirLeak: 921,600.
You override the default only when working with custom firmware that uses a non-standard baud rate. See custom firmware.
Auto-reconnect
Off by default. When you turn it on:
- Companion attempts to reopen the last-connected port on launch.
- If the reconnect fails (port no longer exists, device unplugged, port busy), the device picker opens normally.
- You can manually disconnect and re-pick to override.
For kiosk-style deployments where Companion is meant to be always-on against a specific device, enable auto-reconnect.
AirLeak firmware mode
| Setting | What it does |
|---|---|
| AirLeak firmware mode | When connecting to a port, treat the device as an AirLeak (high-speed baud, AirLeak workspace) |
This is a hint for the auto-detection probe. By default Companion probes both standard and high-speed baud rates and picks whichever responds. If you know your device is an AirLeak, enabling this skips the slower-baud probe.
BLE active scan
| Setting | What it does |
|---|---|
| BLE active scan | When in AirLeak mode, the device sends BLE active-scan requests (asks devices for their full advertising payload) |
Active scan reveals more device detail than passive scan but is detectable — devices being scanned can in principle log the scan request. For surveillance-detection work this matters; for routine monitoring it's usually fine.
The default is passive scan (off). Enable active scan when you need the additional fidelity and are comfortable with the active-scan trade-offs.
Active scanning is also subject to local regulation in some jurisdictions. Confirm your scope before enabling for extended captures.
Selected device
| Setting | What it does |
|---|---|
| Selected device type | Hint for which device type Companion expects — affects the auto-detection prioritisation |
Set to "Auto" by default. Override only when auto-detection consistently mis-identifies your device (rare).
Custom device profile
This subsection lets you define a custom device profile for non-standard firmware. Fields:
- Name — label in the picker.
- Baud rate — the rate Companion opens the port at.
- Probe command — what Companion sends during the handshake.
- Expected banner — what Companion looks for in the response.
- Workspace — which view to open after connection.
Save profiles persist; you can define multiple profiles and Companion will try each during auto-detection.
What's not in connection settings
- Per-port persistent settings — Companion does not store "always use mode X for port Y" — the device dictates its own configuration.
- Per-device firmware settings — manage those on the device itself, via dashboard or the Web UI.
- Network configuration — Companion talks to USB serial only; no Wi-Fi connection settings here.