OsprioView — Capture Workspace
Live

OSDP Protocol Analyzer & Bus Sniffer

See the bus. Decode the truth

Capture Workspace is the Osprio View OSDP protocol analyzer — a bus sniffer that records live RS-485 traffic, decodes every OSDP command and reply into readable protocol data, inspects the secure channel, and replays saved captures offline. It is the fast way to monitor and debug OSDP communications from one named workspace.

OSDP Protocol Analyzer

Everything an OSDP protocol analyzer should do

01

Live RS-485 OSDP capture

Connect capture-capable hardware, click Start, and command and reply traffic streams into the packet table the moment it hits the bus. Watch OSDP communications unfold live instead of reconstructing them after the fact.

Captured packets are held in the active workspace session, with a running packet count in the header, so you always know how much you have collected — and the device stays reserved for that session while it runs.

02

Structured OSDP packet decode

Every frame is broken down into readable protocol data rather than raw bytes. Move through the start-of-message marker, address, sequence, payload, and checksum as structured fields you can actually reason about.

Select any packet and the workspace opens a details panel below the table — decoded sections, packet structure, protocol fields, and both raw and derived values — so you can drill into one exchange while traffic keeps streaming above it.

03

Secure channel inspection

Capture does not stop at the clear-text framing. Inspect OSDP secure-channel handshake state as it progresses, so you can see how — and whether — a secure session was actually established.

When the key context is available, decrypted payloads are surfaced too, turning an otherwise opaque encrypted exchange into something you can read and verify.

04

Targeted capture

The Advanced Capture dialog constrains what gets collected before you start, and every section is optional — a blank section simply means no constraint. Filter to as many as eight specific PD addresses to record only the devices you care about.

Arm a start trigger and the device waits in an ARMED state, recording nothing until a matching OSDP frame appears, then begins with that frame. Matches key off a command or reply code, optionally narrowed to a PD address and a direction.

Auto-stop conditions close the session on the first one that fires — a specific packet match, a packet count, or a duration — so you capture the exchange you came for, not the whole shift.

05

Cut the noise, keep the truth

On a busy bus, polling buries everything interesting. Fold POLL/ACK collapses each contiguous run of POLL and ACK packets into a single discard marker, so secure-channel setup, events, and real command and reply exchanges stand out instead of scrolling past in a flood.

And when the device has to drop packets or reports under sustained load, it reports how many — and the workspace surfaces those counts, so a gap in the capture is visible rather than silently missing.

06

Encrypted export

Save the full capture, just the visible or filtered subset, or only your current selection. You can fold POLL/ACK runs out of the saved file at export time, keeping the archive focused on the traffic that matters.

Exports are written as .ovb, the handoff format between live collection and offline review. Add a password and the result is an encrypted .ovb that prompts for its password whenever it is reopened — safe to share even when the traffic is sensitive.

07

Offline session review

Saved captures reopen for offline review right inside Capture — the workflow that used to live in a separate Analysis workspace now lives here. Open an .ovb through the native file picker, the browser file-input fallback, or a recent-file shortcut from the current session.

A reopened capture loads into a read-only session: no Start or Stop, no device ownership, no device-side side effects — but the same packet table and details panel as a live run. Because it never touches hardware, you can inspect collected evidence with no Osprio device connected, or while another workspace owns the hardware.

Encrypted archives prompt for their password before importing, and malformed content, a wrong password, or a file-access failure surfaces an error instead of leaving you with a half-loaded session.

FAQ

We get these questions a lot

Will capturing interfere with a live OSDP bus?

No. Capture Workspace listens passively on the RS-485 bus — it records command and reply traffic without injecting frames, so a production CP and PD exchange keeps running untouched while you watch it.

Can it decode OSDP secure channel traffic?

When the secure channel key context is available, Capture Workspace inspects the handshake and shows decrypted payloads, so encrypted OSDP sessions are as readable as clear-text ones.

Can I export an OSDP capture for sharing?

Captures export to the encrypted .ovb format — full, filtered, or selection-only — and can be password-protected for sharing sensitive OSDP traffic.

Have a question? Ask us →

Related OSDP Tools

Explore the rest of the toolkit

Hardware

Choose your Osprio hardware