Preconditions before the first switchover
First establish whether the controller supports OSDP. If it does not, the migration starts with replacing or upgrading the controller, not with the readers. Without this information, ordering OSDP readers ends with devices that work as Wiegand and bring no benefit.
The second precondition is the inventory: reader type, cable length, number of wires and direction. The permissible cable length for OSDP is in the order of several hundred metres, and for Wiegand about 150 m, but the values depend on the cabling and must be confirmed in the manufacturer's specification.
Stage 1: choose the gates to start with
Start with the gates that have the greatest exposure to people from outside, and with new installations. Wiegand sends data in clear text, so every gate accessible from outside is a candidate for early migration. A test gate in a place with little traffic lets you check the procedure before touching production traffic.
Plan the work outside the peak of the shift. At a transit gate, leave a temporary passage with a guard, so that the work window does not block deliveries.
Sample migration schedule for 12 gates
Stage 2: cabling and RS-485 topology
OSDP runs on an RS-485 link, and several readers can work in a chain on one bus, whereas Wiegand requires a separate bundle for each reader. This is an opportunity to tidy the installation, but also a pitfall: existing Wiegand bundles rarely have twisted pairs and proper RS-485 terminations.
Check whether the existing cable can be reused. If not, the cost of new cable is often lower than the cost of looking for interference on a faulty link. Every reader in the chain must have a unique address, and the bus must have proper termination.
- type and condition of the cable on the section to the controller
- twisted pairs and shielding on the route near high-current power supply
- unique addresses of readers in the chain
- bus termination and reader power supply
- spare time to test each section separately
Stage 3: enabling Secure Channel and testing
OSDP in installation mode, without Secure Channel, sends data in clear text; encryption must be explicitly enabled and the key exchanged in both the reader and the controller. Migrating the cabling without enabling Secure Channel ends with a bidirectional, supervised link that is still unencrypted.
The OSDP controller constantly supervises the state of the reader, so the acceptance test includes disconnecting the reader and checking the alarm. This is a gain that Wiegand did not have, and it is worth showing it to management in the acceptance report.
Stage 4: cards and events in external systems
Moving from Wiegand to OSDP alone does not secure the card: if the card is 125 kHz or another unprotected technology, it can be cloned in front of the reader. The cabling migration should not be announced as closing the card security topic.
InnerWeb is an independent system complementing the client's systems, so changing the reader-to-controller protocol does not require changes on the InnerWeb side, as long as the KD system keeps sending events. After each gate is switched over, check in the log that punches from it still arrive.
Most common pitfalls
The first pitfall is mixing reader addresses after replacement: two readers with the same address on one bus give unstable operation. The second is the lack of spare time for tests, because a gate switchover ends in the eyes of the crew at the moment the doors open.
The third is the lack of a rollback plan. For each gate, keep a way back to the old reader for the duration of the service window, so that a failure does not extend the downtime.
Video
Frequently asked questions
Can the old Wiegand cable be used for OSDP?
Sometimes, but it requires checking the cable type, the twisting of the pairs and the termination of the RS-485 bus. The parameters must be confirmed in the manufacturer's specification.
Does the migration require stopping the plant's work?
No, if it is carried out gate by gate, in windows outside the peak and with a rollback plan. A single gate usually requires a short service window.
After the migration, does the integration with InnerWeb have to change?
No, as long as the KD system keeps sending punch events. After each gate it is worth checking that the events still arrive.
Sources
Planning a gate migration?
Describe your gate layout and KD vendor. We will help make sure punch events do not disappear from InnerWeb during the switchovers.
Let's talk