Build and certify OSDP systems
with ease.
A full suite of hardware and software tools for engineering teams integrating Open Supervised Device Protocol — from bus capture and emulation to field deployment.
Success: OSDP v2.2 Verified!
A full suite of hardware and software tools for engineering teams integrating Open Supervised Device Protocol — from bus capture and emulation to field deployment.
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 |
AES-128 encrypted, authenticated sessions keyed per device (SCBK) — credentials never travel in the clear.
A single twisted pair carries up to 126 peripheral devices over long cable runs, replacing dedicated home runs.
The panel polls continuously, so tamper, line cuts, and lost devices surface immediately instead of going silent.
A Control Panel drives the bus while Peripheral Devices reply — a clear, deterministic communication model.
Every peripheral advertises what it supports — readers, inputs, outputs, LEDs, and secure channel — so a panel can discover and adapt to each device.
Stream firmware images and other payloads to a device over the bus — the foundation for over-the-air updates in the field.
Published by SIA as IEC 60839-11-5, so readers and panels from different vendors work together on one bus.
Keypads, LEDs, buzzers, biometrics, and output control — OSDP carries far more than a single credential number.
Capture the bus, emulate any device, certify against the spec, and provision in the field — each Osprio workspace turns one hard part of the protocol into a repeatable workflow.
Capture live OSDP traffic and decode every command and reply as it happens. The Capture workspace shows you exactly what's on the wire.
Stand in as a CP or PD in software, automate card swipes, and inject faults. The Emulator workspace validates edge cases before hardware exists.
Drive a structured conformance plan against a PD. The Conformance workspace produces a detailed, repeatable compliance report.
Commission PDs on site — set address and baud, then key the secure channel. The Provisioner workspace gets devices live in the field.
Professional OSDP workflows, from bench to field
Two hardware platforms sit underneath one universal software product, with workspaces nested inside that software layer.
The compact OSDP bench companion
Compact host-powered hardware for running one Osprio View workspace at a time over USB-C and RS-485.
The field-carry OSDP workstation
Battery-backed field hardware for running multiple Osprio View workspaces, offline jobs, Bluetooth sessions, and secure provisioning flows.
Weighing the options? Compare the hardware platforms →
See the bus. Decode the truth
Watch live OSDP traffic on the wire and decode every command and reply. Reopen saved captures for offline review.
Test the device you have against the device you need
Stand in as a CP or PD on the bus. Send commands and events from the UI and automate them with reusable action cards.
Secure-channel commissioning without the field pain
Commission PDs in the field: set address and baud, then key the SCBK in install mode — live one at a time or as a batch.
Compliance claims become repeatable evidence
Drive a structured OSDP conformance plan against a PD. Take away a detailed, repeatable compliance report.
Weighing the options? Compare the software plans →
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.
#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);
}
} From bare-metal firmware porting to architecture reviews, our consulting services bring our OSDP expertise directly into your products.
Porting LibOSDP to bare-metal, FreeRTOS, Zephyr, or custom embedded Linux with tight memory and timing budgets.
Vendor-specific commands, secure-channel extensions, and interoperability hardening for production edge cases.
Hands-on review of your OSDP system design before it solidifies — cheaper to fix on paper than in silicon.
A ready-to-ship Zephyr SDK with LibOSDP integrated and a dedicated OSDP driver layer — skip months of setup work.