Documentation

OsprioMini

OsprioMini is the compact Osprio hardware platform for host-connected OSDP work. It runs one firmware personality at a time and is designed for two primary jobs: passive monitoring and active emulation.

It is the hardware tier aimed at lab users, developers, and engineers doing development, testing, and debugging from a host-connected setup.

Platform overview ​

Hardware overview ​

OsprioMini is the smaller, more focused member of the Osprio hardware family. In practical use it provides:

  • host-connected control for desktop-oriented workflows
  • direct OSDP bus attachment
  • a shared update path across both firmware personalities
  • status LEDs used for mode, activity, and fault signaling

In normal use, the hardware stays the same while the active behavior changes depending on the firmware personality loaded onto the device.

Runtime model ​

Two-app model ​

OsprioMini currently has two user-facing firmware apps:

  • Monitor: for passive capture and live bus inspection
  • Emulator: for active device simulation and test-oriented workflows

Only one of these apps is active at a time. Moving between monitoring and emulation is not a mode toggle inside one runtime. It is an app change on the device.

Shared behavior ​

From a user perspective, both firmware personalities share a few common traits:

  • they are managed from the same hardware platform
  • they share the same general update path
  • they expose device status through the same physical indicators
  • they are intended to work with the same higher-level Osprio software ecosystem

What changes is the job the device is performing on the bus.

LEDs and status behavior ​

OsprioMini uses simple visual status feedback to show idle, active, and fault conditions.

  • yellow is used for idle or attention states
  • green is used for active running or capture states
  • yellow pulses indicate traffic or activity
  • red signals fault or recovery conditions

Bootloader and update path ​

Both apps share the same update path. From a product perspective, that means Monitor and Emulator are not separate hardware products. They are separate firmware personalities on the same board.

User-facing roles ​

Hardware role on the bus ​

The active firmware personality changes how the device behaves on the bus:

  • Monitor uses a listen-only path for passive capture
  • Emulator actively participates in test and simulation workflows

That separation is important when planning test setups. The same hardware connector serves both jobs, but not with the same runtime behavior.

Monitor app ​

Use the Monitor personality when you need passive observation of live traffic.

It is best suited for:

  • capture and inspection of bus activity
  • debugging or support sessions where you do not want the device to participate on the line
  • generating evidence for later review in host software

Emulator app ​

Use the Emulator personality when you need the device to behave like part of the system under test.

It is best suited for:

  • CP or PD style simulation
  • repeatable lab and integration testing
  • profile-driven validation workflows
  • active participation on the bus rather than passive observation

Best fit ​

Choose OsprioMini when the job is primarily host-driven and you want compact hardware dedicated to one active role at a time.

It is especially well suited to:

  • development benches
  • protocol and integration testing
  • debugging sessions
  • repeatable lab workflows where a full field device would be unnecessary