Documentation

OsprioPro

OsprioPro is the full featured Osprio field hardware platform. It combines on-device interaction, battery-backed operation, wireless connectivity, direct bus attachment, removable storage, and managed firmware update into one handheld device instead of relying on a host-connected single-app workflow.

It is the hardware tier aimed at provisioners and field-carry users who need a self-contained device rather than a bench accessory.

Platform overview ​

Hardware overview ​

The current product shape includes:

  • onboard display
  • directional input controls
  • direct bus connectivity
  • wireless connectivity
  • microSD storage
  • buzzer and user LEDs
  • battery monitoring and charging control
  • managed boot and update behavior

The firmware also supports multiple hardware revisions behind the same product surface.

What makes OsprioPro different ​

OsprioPro is not just a USB accessory for host software. The current architecture gives it its own local runtime:

  • a Zephyr-based application firmware
  • an onboard LVGL and EEZ Studio user interface
  • persistent settings in NVS
  • battery-aware power management
  • mobile and external control paths
  • managed update and recovery flow

That makes it the richer, more autonomous hardware tier in the Osprio family.

User-facing operation ​

On-device workflow model ​

The current main menu exposes five top-level user-visible areas:

  • Emulator
  • Monitor
  • Provision
  • Settings
  • About

This is important because the device is not presented as a single-purpose monitor or emulator. The firmware is structured as a device UI with multiple operational surfaces.

On-device UI and feedback ​

The current UI stack uses LVGL on the OLED display with a 5-way pad for navigation.

User-visible behavior includes:

  • horizontally navigated main menu
  • dedicated Monitor, Emulator, and Provision sections
  • Settings and Advanced settings paths
  • About and version information
  • a live status bar that reflects battery, Bluetooth, SD card, and USB state

This allows OsprioPro to remain usable in field scenarios where a nearby desktop app is not the primary control surface.

Connectivity and storage ​

OsprioPro currently exposes multiple control and transport paths.

Bus connection ​

The device includes a direct bus connection used for monitor, emulator, and provisioning-oriented work.

Wireless ​

Wireless connectivity is built into the platform and currently supports:

  • battery data
  • system information
  • emulator profile transfer
  • provisioner profile transfer
  • settings control

This is intended as a real device interface, not just a debug channel.

USB ​

USB is used for:

  • firmware update and recovery paths
  • debugging and shell access
  • monitor-mode host attachment in the current firmware architecture

Storage and persistence ​

OsprioPro uses persistent storage in two ways:

  • NVS for device settings and internal state
  • microSD for removable storage workflows

The on-device status bar and firmware architecture both treat storage as part of the active device behavior rather than a future add-on.

Operational roles ​

The current firmware layout points to three distinct OSDP-facing jobs.

Monitor ​

Monitor mode supports live bus capture and host-side review workflows. The on-device UI exposes Live Capture, and the device presents clear running-state feedback while monitoring is active.

Emulator ​

Emulator mode uses stored profiles and supports on-device selection before entering an active emulator runtime. It is designed for repeatable simulation and validation work.

Provision ​

Provisioning is a first-class surface in the device UI, not just a future placeholder. The current firmware includes provisioner profiles and step-oriented provision flows, which reflects a broader field-operations role than capture alone.

Field behavior and lifecycle ​

Power and field behavior ​

OsprioPro includes a battery-aware power management system with three operating states:

  • Active
  • Low Power
  • Deep Sleep

In the current design:

  • low power turns the display off while keeping more of the system alive
  • deep sleep suspends display, wireless connectivity, bus activity, and some background work
  • d-pad activity wakes the device back up

This is the core field distinction between OsprioPro and smaller host-dependent hardware.

Security and update model ​

The current firmware architecture includes:

  • managed boot flow
  • signed update flow
  • direct update path
  • recovery path

From a user and operator perspective, this means the platform is designed for signed updates and recovery rather than ad hoc flashing.

Best fit ​

Use OsprioPro when the job needs:

  • battery-backed field operation
  • provisioning and field rollout work
  • direct on-device interaction without relying entirely on a host
  • wireless-connected workflows
  • richer local UI and settings control
  • monitor, emulator, and provisioning functions on one device

If the job is primarily host-driven and can tolerate a one-app-at-a-time firmware model, OsprioMini is the simpler hardware path.