Open CAN Interface

Direct Access to the Castle’s Communication System

PS Locks communicate via a robust CAN bus.

The open interface allows system integrators to integrate lock communication into their own control systems and applications.

Technical Basis

• CAN 2.0A

• 11-bit identifier

• 50 kbit/s

• Line topology

• Linux SocketCAN

• CAN interface, for example can0

The CAN interface is particularly well-suited for applications in which multiple locks need to be reliably operated via a shared bus line.

Up to 126 stops per bus route

A CAN bus line can be used with a large number of locks, depending on the system addressing and network configuration.

With the OIP implementation, up to 126 locks can be managed per bus line.

This makes the platform suitable for both small, standalone units and larger cabinet and locker systems.

The actual number possible depends on the bus architecture, cabling, power supply, device addressing, and the components used.

Automatic Device Detection

Zero-Config Setup

The OIP simplifies the setup of new locks.

Newly connected devices can be automatically detected on the CAN bus. They can then be assigned a fixed logical ID and a descriptive name.

For example, a technical device address becomes:

CAN Node 17 → Spindle 12

or:

CAN Node 24 → Women’s Locker Room – Locker 24

The assignment can be made via the web dashboard or the API.

Web Dashboard

All locks in one place in the browser

The OIP provides a modern, web-based user interface.

Once accessed via a standard web browser, the connected locks are available centrally.

Dashboard Features

• Overview of All Connected Locks

• Display of the current lock status

• Door Status Display

• Direct Operation

• Open

• Continuous On

• Lock

• Device Identification

• Displaying Events

• Display of Error Conditions

Status changes can be transmitted directly to the web interface via Server-Sent Events (SSE).

This means you don’t need to manually reload the page.

Custom Names and Configuration

Technical IDs become easy-to-understand attachments

Each lock can be given a unique name.

Examples:

• Lockers 01

• Lockers 02

• Tool Cabinet 07

• Men’s Locker Room 12

• Hotel Room 204

• Supply Cabinet A-17

The configuration is permanently saved and remains in effect even after the gateway is restarted.

This makes the OIP suitable even for larger systems with many identical locks.

Event and Audit Log

Complete Traceability

For professional systems, the traceability of operating procedures and events is important.

The OIP can record relevant events with timestamps and store them in a central event log.

These may include, for example:

• RFID Scans

• Opening Procedures

• Locks

• manual operations

• Alarms

• Error

• Changes in State

• System Events

The audit log is available both in the web interface and via the software interface for further processing.

REST API

Integration with Your Own Software

The OIP provides a modern HTTP-based REST API.

This allows external applications to query and control the connected locks without having to communicate directly with the CAN bus.

Possible Integrations

• Cabinet Management Software

• Access Control Systems

• Hotel Software

• Building Automation Systems

• Production Systems

• ERP/MES Systems

• in-house web applications

• mobile applications

• Cloud Applications

The API establishes a clear separation between the application and the hardware-level CAN communication.

OpenAPI & Swagger

Developer-Friendly Interface

The REST API can be documented and tested using OpenAPI/Swagger documentation.

This allows developers to quickly understand the available endpoints and build their own integrations.

Typical tasks include, for example:

Search for a castle

→ Retrieve device and status information

Unlock the lock

→ Send an open command to a specific compartment

Change Configuration

→ Manage Operating Parameters and Assignments

Retrieve Events

→ Analyze Historical Events

Receive Live Status Updates

→ Process status changes via SSE

System Architecture

Hardware and software are clearly separated

The OIP is based on a modular architecture.

Castle Plain

PS Lock’s Electronic Furniture Locks

↓

Fieldbus Level

CAN Bus / CAN 2.0A

↓

Gateway Level

Linux / Raspberry Pi / Industrial PC

↓

Software Layer

Linux SocketCAN + OIP

↓

Integration Level

REST API + SSE

↓

Application Layer

Web Dashboard / Customer Software / Third-Party System

This architecture makes it possible to run the Schloss hardware independently of the actual user application.

Software Technology

The OIP is based on established open-source technologies.

Technology Stack

• Linux

• SocketCAN

• Python

• FastAPI

• REST API

• Server-Sent Events (SSE)

• SQLite

• HTML / JavaScript

• TailwindCSS

This ensures that the platform remains transparent and can be flexibly expanded by developers and system integrators.

Hardware Requirements

Compact Gateway Hardware

A Raspberry Pi or another Linux-based industrial computer, for example, can be used as a gateway.

Typical Structure

• Raspberry Pi or Linux IPC

• CAN Interface / CAN Shield

• CAN Bus Wiring

• Ethernet or Wi-Fi

• PS Lock’s Electronic Furniture Locks

The specific hardware selection depends on the number of locks, the installation environment, the power supply, and the requirements of the respective system.

Developer Support

Develop Your Own Application

The open architecture allows developers to create their own applications and control systems based on the PS Locks platform.

Depending on the project’s status, the repository contains, among other things, sample code and tests.

Of interest to integrators

• Python Examples

• CAN Communication

• API Integration

• Device Detection

• Lock Control

• Status Monitoring

• Event Processing

• automated tests

Open Source and Transparent Integration

No Black Box

An open interface facilitates the long-term integration of electronic locks into customer-specific systems.

Instead of relying solely on a proprietary turnkey solution, developers can understand how the system communicates and build their own software architecture on that foundation.

This is particularly interesting for OEMs and system integrators who want to maintain control over their own software, user interface, and business logic.

Typical Applications

One platform—many uses

Fitness & Sports

Lockers for gyms, swimming pools, and sports facilities.

Company

Electronic employee lockers for offices, production facilities, and logistics areas.

Hotels

Cabinet and storage solutions that integrate with existing software systems.

Educational Institutions

Lockers for schools, universities, and training centers.

Industry

Tool cabinets, supply cabinets, and controlled storage.

Public Institutions

Lockers in government offices, recreational facilities, and areas open to the public.

Who is the Open Integration Platform intended for?

For anyone who wants to install their own cabinet system

The OIP is intended specifically for:

System Integrators

Integration of locks into existing building, access, or management systems.

Cabinet and Locker Manufacturers

Development of proprietary locker systems featuring electronic PS Locks technology.

OEMs

Integration of lock hardware into our own products and overall systems.

Software Developer

Development of proprietary applications based on the REST and CAN interfaces.

Building Automation

Integration of electronic cabinet systems with higher-level building and management systems.

From hardware to complete integration

You determine the system architecture

PS Locks provides the electronic lock hardware and the open communication platform.

The OIP also provides a gateway that simplifies integration into modern IP-based applications.

This allows for the implementation of various system architectures:

Direct CAN Integration

For custom control systems and embedded systems.

OIP Gateway

For quick integration via Ethernet and REST API.

Web Dashboard

For commissioning, diagnostics, and manual operation.

Third-party system

For integration with existing cabinet, building, or access control software.

Technical Specifications

Repository & Developer Resources

Get started with integration right away

You can find the software and developer resources in the repository:

GitHub:
https://github.com/sigar-nxp/CAN

There, developers can view the available components, examples, and tests and prepare to integrate them into their own system environment.

FAQ

Can PS Locks be controlled directly via CAN?

Yes. The locks feature a CAN-based communication interface that allows them to be integrated into customer-specific control systems and software.

Do I need the OIP for CAN communication?

No. The OIP is an additional gateway and software layer. Direct integration via CAN is also possible.

Can I develop my own software?

Yes. The open interface is particularly useful for integrators, OEMs, and software developers who want to create their own applications.

Can I manage multiple locks at the same time?

Yes. The locks can be connected centrally via the CAN bus. The maximum number depends on the specific bus topology and system configuration. In the configuration described, the OIP supports up to 126 addressable locks per bus line.

Can I check the status of a lock?

Yes. Depending on the lock model used, status information such as bolt, door, and RFID status can be read.

Is there a web interface?

Yes. The OIP features a web-based dashboard for commissioning, monitoring, and manual control.

Is there a REST API?

Yes. The OIP provides an HTTP-based REST interface for integration with external applications.

Can I integrate the locks into an existing building or cabinet management system?

Yes. The locks can be integrated into higher-level systems via CAN or the OIP REST API.

What hardware do I need for the OIP?

Typically, a Raspberry Pi or a Linux-based industrial PC with a CAN interface and a network connection.

Ready for your own closet solution?

Develop your application on an open platform.

Whether it’s a single locker, a large locker system, or a fully integrated locker management system:

With PS Locks, you get electronic furniture locks with an open communication interface and a flexible foundation for custom integrations.

Select Hardware
Discover the available PS Locks locking solutions.

Technical Documentation
Learn more about CAN communication and integration.

Try out OIP
Use the gateway to establish a fast connection between the CAN bus and an IP network.

Developer Repository
https://github.com/sigar-nxp/CAN

PS Locks – Open Integration

Electronic locks. Open interfaces. Proprietary systems.

Design the cabinet solution that fits your application.