Is BusScope a multi-bus analyzer?
No. BusScope is intentionally USB-only. It does not expose TCP, UDP, RTSP, CAN, serial, BLE, or a generic protocol workbench surface.
USB capture workflow references.
Short, operational notes for platform capture, licensing, .bscope sessions, and troubleshooting.
.bscope sessions
`.bscope` files are SQLite-backed session files. They keep packets, payload retention, statistics, diagnostics, descriptor evidence, decoded events, and timeline state together.
HelpCapture USB traffic
Select a capture adapter first, then select a USB device when the platform backend exposes device inventory.
HelpLicense and activation
BusScope uses the same commercial loop as the other Hannes Software desktop products.
HelpPlatform capture
Linux capture uses usbmon. BusScope expects normal-user GUI operation and escalates only the helper action that loads usbmon or applies device ACLs.
HelpTroubleshooting
If the adapter is unavailable, check the platform capability message first. Missing usbmon access or missing USBPcap are environment issues, not packet parser failures.
FAQ
Common questions
Is the pricing the same as RtspInspector?
Yes. BusScope uses the same $19 lifetime strategy, the same machine-bound license.dat flow, and the same personal/team license model.
What capture backend does each supported OS use?
Linux uses the /dev/usbmonN binary API. Windows uses an installed USBPcap/USBPcapCMD. BusScope does not support macOS and there is no macOS package planned.
Can I export customer reports?
Not yet. The current public surface is capture, inspection, diagnostics, and .bscope session retention. Export/report workflows should not be promised until they ship.
What is the difference between personal and team licenses?
The desktop capabilities are the same. Team purchase only means one billing email can receive multiple machine-bound license codes.