PORTANODE
plen

Custom drivers

Custom drivers, built to order for access control

When a device or system has no ready-made connector, we write one to order: the driver, the protocol adapter and the event layer that talks to the access control platform, such as Gamanet C4 or ATS8600.

Discuss Your Integration

What a custom driver includes

  • A Gamanet C4 driver (.c4driver package) that reproduces devices, states and events in C4.
  • An ATS8600 connector for devices and systems outside the standard offering.
  • A protocol adapter: serial interface, TCP, log files or a vendor API.
  • Error, retry and buffering handling so events are not lost after a link outage.
  • Authentication and channel encryption, plus delivery acknowledgements.
  • Tests, a device simulator and protocol documentation.

How it works

  1. 01

    Device or protocol

    Serial, TCP, log files, vendor API.

  2. 02

    Custom driver

    Parser, state machine, error and retry handling.

  3. 03

    Integration layer

    Event normalisation, rules, buffering and audit.

  4. 04

    Access platform

    Gamanet C4, ATS8600 or an external application.

From our projects

  • The "Veno PIR" C4 driver for Gamanet C4 2024 (.NET Framework 4.6.1, DriverFramework 3.x): reproduces panels, zones, sensors, partitions and doors, derives zone alarms from sensors and imports the structure with a wizard.
  • A mediating service (.NET 8) next to the external system, connected to the driver over a TLS channel with HMAC authentication and acknowledgements.
  • Automated tests, including an end-to-end test of the whole channel.

What we need for the analysis

  • protocol documentation or the device interface,
  • a test device or a simulator,
  • the access platform version and licenses,
  • a description of the events and states that should reach the system.

Frequently asked questions

What is a custom-built driver?
Software written for a specific device or system that connects it to the access control platform. It is built when no ready-made connector exists or the standard one does not meet the requirements.
Which systems do you write drivers for?
We have delivered drivers and connectors for Gamanet C4 and integrations with ATS8600. Other platforms and devices are assessed individually based on protocols and documentation.
Can any device be integrated?
Not always. Feasibility depends on protocols, available documentation, vendor APIs, licenses and hardware. We confirm it during analysis, before agreeing the scope of work.

Describe your installation and we will assess feasibility.

Tell us which systems you want to connect. We reply with an initial assessment and technical questions.

Discuss Your Integration

Related integrations

ATS8600, Gamanet, C4, VENO, Novus, HID and 2N are trademarks of their respective owners. They are used only to describe the compatibility of our integration services. We are not an official partner of the vendors named, unless stated otherwise.