OSDP Tools: Protocol Analyzer, Emulator & Provisioning

What is OSDP

Modern access control,
on an open standard

OSDP — the Open Supervised Device Protocol — is the IEC 60839-11-5 standard for how access control panels talk to the readers, keypads, and controllers in the field. It is secure, bidirectional, and vendor-neutral: one open protocol for the whole bus.

For nearly forty years that bus spoke Wiegand — a one-way, unencrypted signaling scheme still wired into most card readers in service today. Its weaknesses are now well understood, and as encryption and line supervision become baseline security expectations, standards bodies and government procurement increasingly specify OSDP for new and upgraded installations. The changeover is gradual, but the direction is set.

Capability	Legacy Wiegandincumbent · since the 1980s	OSDPtoday's standard
Communication	One-way — reader to panel only	Bidirectional command and reply
Data security	Unencrypted — credentials sent in the clear	AES-128 Secure Channel encryption
Line supervision	Unsupervised — a cut wire goes unnoticed	Continuously supervised — tamper and line faults detected
Bus topology	Point-to-point — one device per home run	RS-485 multidrop — up to 126 devices on one bus
Standardization	Proprietary, ~40-year-old wiring scheme	Open IEC 60839-11-5 standard — interoperable across vendors

scroll to compare →

In the field

Typical OSDP deployments

A real building runs many of these buses at once. One management server talks IP to a set of access control units — typically one ACU per floor or zone — and each ACU drives a single RS-485 OSDP bus. Every device on that floor multidrops onto it: card readers, biometric readers, turnstiles, boom barriers. One open protocol, one bus per controller, many devices.

Typical OSDP building deployment: a central management server connects over IP to one access control unit (ACU) per floor; each ACU drives a single RS-485 OSDP bus carrying multiple devices — card readers, biometric readers, turnstiles and boom barriers — that multidrop onto it.

Capabilities

What OSDP brings to the bus

Secure Channel

AES-128 encrypted, authenticated sessions keyed per device (SCBK) — credentials never travel in the clear.

RS-485 multidrop

A single twisted pair carries up to 126 peripheral devices over long cable runs, replacing dedicated home runs.

Supervision

The panel polls continuously, so tamper, line cuts, and lost devices surface immediately instead of going silent.

CP & PD roles

A Control Panel drives the bus while Peripheral Devices reply — a clear, deterministic communication model.

PD capabilities

Every peripheral advertises what it supports — readers, inputs, outputs, LEDs, and secure channel — so a panel can discover and adapt to each device.

File transfer support

Stream firmware images and other payloads to a device over the bus — the foundation for over-the-air updates in the field.

Managed devices

OSDP turns readers into managed endpoints — panels can identify, configure, secure, update, and control devices remotely over the same RS-485 bus.

Open & interoperable

Published by SIA as IEC 60839-11-5, so readers and panels from different vendors work together on one bus.

OSDP is powerful.
Osprio makes it visible, testable, certifiable, and deployable.

OSDP is an open standard, but working with it has always meant bespoke scripts, borrowed lab gear, and a lot of guesswork about what's really on the wire. Osprio replaces all of that with four focused workspaces — capture the bus, emulate any device, qualify against the spec, and provision in the field. Each one takes a part of the protocol that's traditionally slow and error-prone and turns it into a repeatable, shareable workflow you can trust all the way from the bench to the field.

01

Visible

Capture live OSDP traffic and decode every command and reply as it happens. The Capture workspace shows you exactly what's on the wire.

02

Testable

Stand in as a CP or PD in software, automate card swipes, and inject faults. The Emulator workspace validates edge cases before hardware exists.

03

Certifiable

Drive a structured conformance plan against a PD. The Conformance workspace produces a detailed, repeatable compliance report.

04

Deployable

Commission PDs on site — set address and baud, then key the secure channel. The Provisioner workspace gets devices live in the field.

Who it's for

Find the Osprio that fits your job

Five ways teams work the OSDP bus — and the workspace and hardware built for each.

Systems integrators

Get a reader and controller talking — and find out why they won't.

Works best with OsprioMini

Capture the bus →

Test & QA engineers

Exercise a device against a simulated CP or PD, automate regression, and inject faults.

Works best with OsprioMini

Emulate any device →

Field installers & commissioning techs

Address, key, and bring up PDs at the panel — untethered.

Works best with OsprioPro

Provision in the field →

Compliance & certification engineersAvailable

Prove a PD meets the OSDP spec, with a repeatable report.

Works best with OsprioMini

Run conformance →

Firmware & product developers

Build your own OSDP reader or PD without writing the stack.

Works best with Your own board+ Mini to verify

Start with the SDK →

Not sure where you fit?

Compare the full lineup side by side and find the workspace and hardware for your workflow.

Compare the product line →

Products

The Osprio product line

Professional OSDP workflows, from bench to field

Two hardware platforms sit underneath one universal software product, with workspaces nested inside that software layer.

Hardware

OsprioMiniAvailable

The compact OSDP bench companion

Compact host-powered hardware for running one Osprio View workspace at a time over USB-C and RS-485.

One workspaceUSB-CRS-485Field upgrades

Learn more →

OsprioProActive Development

The field-carry OSDP workstation

Battery-backed field hardware for running every Osprio View workspace, offline jobs, Bluetooth sessions, and secure provisioning flows.

Multi-workspaceBluetoothOffline modeSecure element

Learn more →

Weighing the options? Compare the hardware platforms →

Software

Osprio View - Capture WorkspaceLive

See the bus. Decode the truth

The OSDP protocol analyzer and bus sniffer: watch live OSDP traffic on the wire, decode every command and reply, and reopen saved captures offline.

Protocol analyzerSecure channelOffline replay

Explore the OSDP protocol analyzer →

Osprio View - Emulator WorkspaceLive

Test the device you have against the device you need

The OSDP emulator: stand in as a CP or PD on the bus, send commands and events from the UI, and automate them with reusable action cards.

CP + PD rolesFault injectionScripted flows

Explore the OSDP emulator →

Osprio View - Provisioner WorkspaceLive

Secure-channel commissioning without the field pain

The OSDP provisioning and commissioning tool: set address and baud, then key the SCBK in install mode — live one at a time or as a batch.

Address + baudSCBK keyingInstall mode

Explore the OSDP provisioning tool →

Osprio View - Conformance WorkspaceAvailable

Compliance claims become repeatable evidence

OSDP conformance testing: drive a structured conformance plan against a PD and take away a detailed, repeatable compliance report.

Semi-automatedCommand coverageCompliance report

Explore OSDP conformance testing →

Weighing the options? Compare the software plans →

Open Source Core

Built on LibOSDP — the most popular OSDP implementation

Every Osprio product is built on top of LibOSDP, a battle-tested open-source library that handles the full SIA OSDP v2.2 protocol surface — secure channel, file transfer, multi-drop, and more.

Full CP and PD mode support
Secure channel with AES-128 and key management
OSDP file transfer (FT) for OTA firmware
Runs on Linux, RTOS, and bare-metal targets
Non-blocking, event-driven architecture

GitHub ↗libosdp guide ↗

osdp_cp_setup.c

#include <osdp.h>

osdp_pd_info_t pd_info[] = {
    { .address = 1, .baud_rate = 9600 }
};

int command_handler(void *data, int pd_idx,
                    struct osdp_cmd *cmd) {
    // react to PD commands here
    return 0;
}

int main() {
    osdp_t *ctx = osdp_cp_setup(1, pd_info);
    osdp_cp_set_command_callback(ctx, command_handler, NULL);
    while (1) {
        osdp_cp_refresh(ctx);
    }
}