Documentation

Devices in Osprio View

This page explains devices from Osprio View's point of view. It focuses on how hardware appears in the app, why a device may be visible in one workspace but not another, and what the device actions and status states mean.

For product positioning, hardware selection, and transport-level details, use Osprio Hardware, Osprio Pro, and Osprio Mini.

Start with the workspace model ​

Device behavior in Osprio View is workspace-aware.

  • Capture shows devices available for capture workflows; reviewing a saved .ovb capture in Capture needs no live device.
  • Emulator shows devices available for emulation workflows.
  • Conformance needs two devices at once — one running the Conformer app and one running the Capture app.
  • App Switcher is used when the device needs to change app role before another workspace can use it.

The same physical device may not appear in every list at the same time. Osprio View filters hardware by capability, current role, and session ownership.

What device actions mean in the UI ​

The exact controls vary slightly by workspace, but the common actions are:

  • Pair Device: open the pairing dialog to authorize a new device. Its Pair USB device and Rescan controls live inside this dialog, reached from the pair link in the empty-device hint.
  • click a device card: bind (connect) that device to the active workspace session
  • Info: show basic device identity and state
  • Detect: blink the device's LED to identify which physical unit it is

Pairing matters mostly in the browser build. In the desktop build, devices are auto-discovered by the app runtime rather than through a browser permission prompt.

Why a device may be visible in one workspace only ​

Capture workspace ​

Capture only lists devices that Osprio View can use for capture traffic collection.

A device may be hidden or unavailable here because:

  • another tab already owns it
  • it is connected but not ready for capture work
  • the runtime still needs authorization
  • the device is running the wrong app role

Emulator workspace ​

Emulator only lists devices that Osprio View can use for emulation work.

A device can be available here even when it is absent from Capture, and the reverse is also true.

If the hardware must change app role before emulation can continue, use App Switcher instead of assuming the device list is stale.

Browser pairing and WebUSB ​

Osprio View currently runs in two runtime styles:

  • browser mode, where device authorization is granted through the browser
  • desktop mode, where access is handled by the installed app

If you are using the browser build, complete this flow before expecting hardware workflows to work reliably:

  1. open the target workspace
  2. if the device is not listed, open the Pair Device dialog from the pair link in the empty-device hint
  3. click Pair USB device and select the device in the browser chooser
  4. click Rescan in the dialog if it does not appear immediately
  5. click the device card to connect it to the workspace

If pairing has not happened yet, the workspace cannot treat the hardware as available no matter how healthy the device itself is.

Availability and status states ​

Common device states in Osprio View include:

  • Connect: the device is available for this workspace
  • Connecting...: the workspace is trying to bind the device
  • In Use: another tab or session already owns it
  • Busy: the device is visible but not available for the requested action

These states come from Osprio View's shared device and session managers. A device being connected at the transport level does not mean it is free for every workspace tab.

Osprio Pro and Osprio Mini from the app's perspective ​

From Osprio View's side, the key distinction is not every hardware detail but whether the device can satisfy the current workspace.

  • Osprio Pro can cover more than one workflow without feeling tied to a single bench role.
  • Osprio Mini is commonly used for bench and development workflows, but app switching matters more because capture and emulator roles are separated.

If you need to decide which product fits the job, use the hardware pages instead of relying only on workspace device lists.

When a device does not show up or stays unavailable ​

Use this quick order:

  1. confirm you are in the correct workspace
  2. pair or authorize the device if needed
  3. Rescan from the Pair Device dialog
  4. confirm the device is running the correct app role
  5. confirm another tab does not already own it
  6. reconnect the cable or retry the link if applicable

If the device still appears but cannot be used, continue with Connection Problems.