Installation Manual | TM-20230511 iProtect Access / Security | Functionalities | OSDP Survision LPR Camera |
This manual represents the knowledge at the above-mentioned time. TKH security works non-stop to improve her products. For the most recent technical information please contact your consultant or dealer.
1. Introduction
The Micropak 5 is an advanced, standalone license plate recognition (LPR) camera designed to deliver high performance with minimal setup. Built for ease and efficiency, the Micropak 5 offers trigger-free operation, capturing high-speed vehicle plates up to 155 mph (250 km/h) with exceptional accuracy and speed. Its compact design integrates all necessary LPR functions within the camera itself, eliminating the need for an external server.
Key features include adjustable recognition distances from 5 to 49 feet and real-time monitoring for enhanced security. The device supports both European and American plate formats and provides instant data output on plate position, traffic direction, and more.
Micropak 5 is equipped with infrared or white-light LEDs for optimal visibility, and it’s housed in a durable, weather-resistant aluminum body. Built with embedded AI, it offers flexible data outputs, multiple connection options, and can be easily integrated into iProtect.
2. Support and license
Below is an overview of support for both the hardware and the software, including the necessary license:
Version | License |
---|---|
Version 10.4.14 | iProtect basic license |
Sufficient reader license |
2.1 Supported cards (License plates)
European and American plates
3. What is OSDP
Open Supervised Device Protocol (OSDP) is an access control communications standard developed by the Security Industry Association (SIA) to improve interoperability among access control and security products.
OSDP was approved as an international standard by the International Electrotechnical Commission in May 2020 and has been published as IEC 60839-11-5.
OSDP V2.2 which is based on the IEC 60839-11-5 standard, was released in December 2020.
OSDP readers are only supported by stacked Orions (RS485 connection)
4. Installation
4.1 Connecting the LPR camera to the Orion
The LPR camera connects directly to the Orion Kp bus connector via a fixed cable, with a maximum distance of 15 meters between the camera and the Orion unit. Additionally, the camera operates using an external 24V power supply.
Cable color | Signal | ABC connector Orion KpBus (RS485) |
---|---|---|
Brown | + 24V | |
Grey | GND | |
Green | RS485 A | A |
White | RS485 B | B |
Yellow | RS GND | CC |
Max. cable distance between Orion and the LPR reader = 15 Mtr.
The LPR reader must be connected to an 24V external power supply.
The KpBus connector can only be used when the PRT2 port is not being used.
5. Implementation
5.1 General
OSDP readers are completely handled by the nodemanager, so the nodemanager should run to obtain access by a OSDP card reader.
The readermanager is not involved by handling the OSDP protocol
5.2 Configure the reader in iProtect
Follow the steps below to configure an OSDP reader:
Connect the LPR camera to the Orion (see chapter “Connecting the reader”)
Press the discover button in the line dialog of the Pluto.
Wait until the discover process is ready: Read-in event=> Read-in event: Stop, Line: xxx…
Refresh the line dialog of the Pluto, if an OSDP device is detected it will be shown as a Node below the Prt2 port of the Orion.
Change the OSDP compatibility setting at the OSDP node to “ASCII Raw data”
Right mouse click at the OSDP node in the treeview and click on “add reader”
Fill in the logic unique name of the reader.
Click on the save button.
The discover function for OSDP devices checks for the following settings:
Baudrate: 9600, 19K2, 115K2 baud, They are all non-parity, 8 bit, 1 stop bit
Device address: 0, 1, 2, 3, 4, 5, 6, 7, 8, 13, 14, 24
If other settings are necessary, set these settings manually.
5.3 OSDP reader settings
For OSDP readers there are some specific settings.
It’s possible to setup the buzzer time when a card is recognized, this can be done at the door behavior tab of the reader.
Buzzer time | card recognized | |
---|---|
Setting | Behavior |
Empty | No buzzer when card is recognized |
1 - 15 | buzzer time (1/10 sec) |
Most used setting for buzzer time = 2
6. Card encoding
To enable license plate recognition, a card configuration must be created within iProtect. To do this, go to Access > Settings > Card Configuration and use the wizard provided in this section.
7. License Plate Configuration in iProtect
A license plate functions similarly to a standard card within the iProtect system. To activate this feature, you must connect the LPR (License Plate Recognition) reader to a reader group, which is then associated with an access profile.
Access is granted to a vehicle when its license plate is linked to a valid access profile that corresponds with the LPR reader.
For detailed instructions on configuring an access profile in iProtect, please refer to this document: *Access rights in iProtect™.
For guidance on how to assign a card (License Plate) to a person, you can follow this document: https://tkhsecurity.atlassian.net/wiki/spaces/KB/pages/9171076589/Assign+cards+to+people?atl_f=PAGETREE.
8. Secure channel
OSDP v2 with Secure Channel has AES-128 encryption to ensure that communication between the targeted devices is strict and secure.
All OSDP devices have a known standard Secure Channel Base Key (SCBK), according to the OSDP specification. The SCBK is a key shared between the peripheral/reader and the controller, which is used once to initiate encryption. The SCBK allows the controller (Pluto/ApolloN) to send a challenge command (critical information that the peripheral/reader can use to initiate a Secure Channel session). Note that OSDP security is not limited to the Secure Channel Base Key. The SCBK is used only once at the start of the session before auto-generated session keys are used to encrypt the OSDP data.
If the security status is “Active scbkd” at the node you can set a random key with the button <Set keys (SC)>. If pressed the key is set into the reader and stored in the controller (Pluto / ApolloN)
Refresh the page to see the results.
The button <Set keys (SC)> generates and stores a key into the reader
The OSDP secure channel key himself is only visible for Root and Installer users
Once a key is set into the reader it cannot be cleared or rewritten by the system if the current key is not known. (not allowed in the OSDP protocol, security risk). If the key must be cleared (Reset) follow the procedure what is delivered by the reader manufacturer.