Contact
Contact Bus Scope Support
When you need help with Bus Scope, you are talking to the engineering team that built it. We do not use a tiered support desk.
If you hit a bug or unexpected behavior, include what is needed to reproduce the issue: the operating system version, the specific sequence of actions that caused the failure, and whether reinstalling or rolling back to an older version changed the result.
For license recovery, transfer, or invoice assistance, include the purchase email and any relevant order numbers. To protect user privacy, activation records are only modified when the email matches or purchase proof is provided.
Reach support directly at contact support or use the form below to submit a structured report.
To reduce back-and-forth, say whether the request is about installation, licensing, a crash, an incorrect result, performance, or product scope. Do not send full customer data first; describe the file type, file size, steps that trigger the issue, and whether a sanitized sample is available.
Bus Scope support is focused on getting a concrete workflow working again, not on generic product theater. Reproduction steps, screenshots, short log excerpts, or a clear boundary around the failing file let us answer with a fix, a workaround, or a defect that needs follow-up in a later build.
Enter a valid email address to send the request.
Support context
What to include for Bus Scope
Inspect live USB traffic, decode device evidence, and retain structured .bscope sessions for firmware and hardware debugging.
The most useful report connects the failure to a concrete task: input file, device, stream, clinic record, music workflow, export target, operating system, app version, license state, and the last action before the problem appeared.
Relevant product areas
- Live adapter and device selection. Select USB capture adapters, lock a device target, and keep capture state visible while traffic arrives.
- Transfer timeline and filtering. Filter by endpoint, direction, transfer type, text, hex, and device context while keeping rows dense and inspectable.
- Packet detail and raw payload evidence. Inspect setup fields, raw bytes, descriptor evidence, class decoder output, status, and diagnostic references.
Workflow details
Built for firmware teams, hardware labs, and device vendors who need a repeatable answer to why USB enumeration, descriptors, endpoints, or transfers fail.
License and purchase context
For Bus Scope, the public paid path includes Professional at Optional one-time unlock. If the request is about activation, include the purchase email, current machine, operating system, and exact activation message.
Optional license for durable session handoff and polished reports.