Documentation

Introduction to OsprioView

OsprioView is a tabbed OSDP workspace application. You do not launch separate tools for capture, emulation, offline review, and device utility flows. Instead, you open a workspace tab for the job you want to perform and keep related tabs open side by side.

Start with the workspace model ​

The first screen in a new tab is the workspace chooser.

From there you choose one of three operational paths:

  • Capture for live monitor-device traffic collection and read-only review of saved .ovb captures
  • Emulator for slot, profile, and runtime emulation work
  • App Switcher for changing the firmware app running on supported hardware

This choice matters because each workspace has different device requirements, runtime controls, and close behavior.

What stays the same across the app ​

No matter which workspace you open, OsprioView keeps the same shell around it.

That shared shell provides:

  • the top tab strip
  • contextual help tabs
  • diagnostics and debug logging
  • theme controls
  • tab-close guards for active or dirty sessions

Tabs are long-lived sessions, not simple page navigations. You can keep a help tab open while capture or emulator work continues in another tab.

Choose the right first path ​

Use Capture for live traffic or saved evidence ​

Choose Capture to monitor a real OSDP link and collect packets from hardware — and to reopen a saved .ovb capture for offline review when you already have evidence.

Live path:

  1. connect or pair a monitor-capable device
  2. start capture
  3. inspect packets live
  4. save the result as .ovb

Offline path:

  1. open a saved .ovb file from a Capture tab
  2. enter a password if the archive is encrypted
  3. inspect packets and decoded details in read-only mode

Use Emulator when you need active bus behavior ​

Choose Emulator when you need to configure an emulation profile, write it to hardware, and run CP or PD behavior from OsprioView.

Typical path:

  1. select a device and slot
  2. configure or load a profile
  3. start emulation
  4. use the runtime actions pane and logs to drive the session

Use App Switcher when the device is in the wrong role ​

Choose App Switcher when the hardware needs to change the firmware app it is running before capture or emulator work can continue.

This matters most on Osprio Mini, where capture and emulator capabilities are not exposed at the same time.

Device setup before you expect hardware workflows to work ​

Runtime matters ​

OsprioView currently runs in two styles:

  • browser mode with WebUSB
  • desktop mode with native USB access through Tauri

If you are in the browser build, hardware access depends on pairing or authorizing the device first. In the desktop build, that permission flow is handled by the app runtime instead of the browser.

First hardware checklist ​

Before debugging workspace-specific issues, confirm the basics:

  1. you are in the correct workspace for the job
  2. the device is paired or authorized if required
  3. the device appears in the workspace list
  4. the device is running the right app role for that workspace

If you are using the browser build, review Devices in OsprioView before troubleshooting anything deeper.

The cleanest way to get oriented is:

  1. read UI Basics
  2. review Devices in OsprioView
  3. open the workspace that matches the job
  4. keep diagnostics available if you are working with hardware
  5. open help tabs alongside the live workspace when needed

If you are working with Osprio Mini and the required workspace does not show the expected capability, run App Switcher Workspace first.

Where to go next ​