EKEY KNX CONNECT
YOUR FINGER.YOUR KEY.
– with this slogan the Austrian company ekey biometrics systems has risen to the top within the European market in the field of fingerprint access solutions. ekey puts authorization into the customer’s hands! Keys, cards, and codes can be lost, forgotten, or stolen. Your finger is always on hand! ekey’s wide range of products includes biometric or code-based access control for doors, gates, alarm systems, and time recording. Quality made in Austria. As a premium partner, independent of the type of solutions provided for connecting the ekey with the KNX-Bus, we continuously provide support to deal with any ekey related question. Feel free to contact us.
Worldwide standard for smart homes
For 28 years, KNX is a worldwide standard with a strong international community. KNX provides a reliable and resilient technology prepared for future developments. Furthermore, KNX is the international solution for high-quality smart homes including a variety of functions such as central based control regarding residential engineering, shading devices, keyless access control, time-dependent ventilation and heating control as well as video monitoring and security systems. The focus lies on comfort and flexibility as well as on economic feasibility and energy efficiency. The concepts of smart home technology are suitable for private properties as well as commercially used buildings.
EKEY KNX CONNECT connects both EKEY and KNX functions !
GENERAL DESCRIPTION
The brand-new module EKEY KNX CONNECT offers an easy integration of the ekey MULTI- and NET-series into the KNX-system. Additionally, the KNX-module requires the following ekey products:
- ekey net CVLAN RS-485 module in order to connect RS-485 and LAN (Cat. No. 100340)
- ekey home CV LAN RS-485 module in order to connect RS-485 and LAN (Cat. No. 100460)
The EKEY KNX CONNECT is based on ISE SMART CONNECT KNX PROGRAMMABLE, connecting your ekey system with the KNX-bus in a reliable way. In order to communicate with the ekey system an IP-based-interface is used. By creating Programmables, it is possible to provide the customer with a cost-efficient product choice. Due to a favourable price in both purchase and further developments, the product offers a highly convincing price-performance ratio. In terms of advanced developments, Mircosoft.NET is implemented, which allows us to quickly provide EKEY KNX CONNECT with program extensions and changes if needed. Nevertheless, costumers are able to update and download new program files themselves by using a common internet browser and having access to a fitting device.
Communication
EKEY KNX CONNECT and the ekey system communicate through an UDP-interface corresponding to a LAN RS-485 net converter. In case certain activities occur within a RS-485-Bus system, the described converter sends a defined data package interpreted by a data sink which consequently is enabled to set a specified computing event. Additionally, the converter supports four protocol types: rare, rare v2, home und multi. Hence, configurating protocol types and network settings by means of a software regarding ekey net/home converter LAN, the following settings are required:
ekey.NET
-
Version
ekey.net software support is granted from version 4.4.3.. Support regarding CVLAN NET modules require firmware version 3.2.56.2 at least.
-
UDP transmission
box must be ticked.
-
IP address of receiver
IP address of EKEY KNX CONNECT needs to be applied and configurated by using ETS, preferably generated statically (avoiding a DHCP allocation).
-
Spacer
please apply “_”.
-
Protocol type
select “rare v2”.
-
Receiver port
selected value has to show the same value as in KNX parameters. Please note that ports need to be assigned a greater value than 49151 due to being considered dynamic ports and therefore having no influence on the local network.
ekey.MULTI
-
Version
latest firmware version is required regarding CVLAN home modules (multi).
-
UDP transmission
box must be ticked.
-
IP address of receiver
IP address of EKEY KNX CONNECT needs to be applied and configurated by using ETS, preferably generated statically (avoiding a DHCP allocation).
-
Spacer
please apply “_”.
-
Protocol type
select “rare v2”.
-
Receiver port
selected value has to show the same value as in KNX parameters. Please note that ports need to be assigned a greater value than 49151 due to being considered dynamic ports and therefore having no influence on the local network.
EKEY KNX CONNECT
After having installed and professionally connected EKEY KNX CONNECT with a power supply as well as KNX bus and a local network, programming and parameterising a new module by assistance of ETS (from V4 onward) has been enabled. Corresponding files and required data point lists for both NET and MULTI are to be found at the end of this website. In addition to that, the latest version of product file can be obtained through the ETS online catalogue by searching „ise smart connect KNX Programmable“. Following the successful completion of adding EKEY KNX CONNECT to an existing KNX-project, the data point list can be uploaded into the context menu by selecting “plug-in” onto the device.
Afterwards, EKEY KNX CONNECT can be configurated using the parameter settings. Here, only configurations regarding the protocol types („MULTI“ or „NET“ ) and UDP-port are required. Please note that the device needs to be assigned an IP.
ETS application offers a variety of 14 communication objects in terms of the net-version and a total of 13 communication objects regarding the multi version. New data entries are added every time an action is sent through the UDP-protocol caused by the ekey system.
We provide the following objects with ekey.NET installations:
With ekey.MULTI installations we provide the following objects:
Description of the communication objects (NET)
| Number | Name | Description | Type |
| 1 | Version | Version of UDP packet | 4 bytes unsigned |
| 2 | ActionCode | Eventcode in ekey configuration (in net e. g. 19= deny: unknown) | 4 bytes unsigned |
| 3 | TerminalID | Internal ID of device (shown for each device in ekey net admin as internal ID) | 4 bytes unsigned |
| 4 | SerialScanner | Serial number of finger scanner | 14 bytes string |
| 5 | RelayID | Switching relay ID (1=relay 1, 2=relay 2, …) | 8 bit unsigned |
| 6 | UserID | Internal ID of user (shown for each user in ekey net admin as internal ID) | 4 bytes unsigned |
| 7 | FingerID | Identification feature 0 = not defined, 1 = left pinky finger, 2 = left ring finger, 3 = left middle finger, 4 = left index finger, 5 = left thumb, 6 = right thumb, 7 = right index finger, 8 = right middle finger, 9 = right ring finger, 10 = right pinky finger, 13 = pincode, 16 = RFID | 4 bytes unsigned |
| 8 | Event | Eventname as 16-digit alphanumeric ANSI-string without null-termination* | 14 bytes string |
| 9 | Date | Date of the event | 3 bytes date |
| 10 | Time | Time of the event | 3 bytes time |
| 11 | Name | Name of user as null-terminated unicode string* | 14 bytes string |
| 12 | StaffID | Staff ID as null-terminated unicode string* | 14 bytes string |
| 13 | TerminalID HexStr | Internal ID device as Hex value | 14 bytes string |
| 14 | Updated | Trigger is set to 0 by default and changes to 1 for 1s after each update | 1 bit switch |
Description of the communication objects (MULTI)
| Number | Name | Description | Type |
| 1 | PacketType | Packet type | 14 bytes string |
| 2 | UserID | Usernumber (Default 0000) | 14 bytes string |
| 3 | UserName | Username, xx.. alphanumeric -.. undefined | 14 bytes string |
| 4 | UserStatus | 0.. user disabled, 1.. user enabled , „-„.. undefined | 14 bytes string |
| 5 | FingerID | 1. left pinky finger, 2. left ring finger, 3. left middle finger, 4. left index finger, 5. left thumb, 6. right thumb, 7. right index finger, 8. right middle finger, 9. right ring finger, 0. right pinky finger, „-„.. no finger | 14 bytes string |
| 6 | KeyID | 1.. key 1, 2.. key 2, 3.. key 3, 4.. key 4, „-„.. undefined | 14 bytes string |
| 7 | SerialScanner | Digit 1-6 = item number, digit 7-8 = production week, digit 9-10 = production year, digit 11-14 = consecutive number | 14 bytes string |
| 8 | NameScanner | Name of finger scanner | 14 bytes string |
| 9 | ActionCode | 1. open, 2. deny unknown finger, 3. deny time window A, 4. deny time window B, 5. deny disabled, 6. deny „only user“, 7. finger scanner not connected with control unit, 8. digital input 1 1) if activation is done with a digital input, the field SerialScanner is undefined | 14 bytes string |
| 10 | InputID | 1. digital input 1, 2. digital input 2, 3. digital input 3, 4. digital input 4, „-„.. no digital input | 14 bytes string |
| 11 | Date | Date of the event | 3 bytes date |
| 12 | Time | Time of the event | 3 bytes time |
| 13 | Updated | Trigger is set to 0 by default and changes to 1 for 1s after each update | 1 bit switch |
GIRA HOMESERVER LOGIC MODULES
Additionally, two logic modules are offered in terms of the GIRA home server. Due to these logic modules an easy solution is provided in regards to evaluating communication objects received by the EKEY KNX CONNECT device concerning KNX controlled actions. As following the most important values are: SerialScanner, ActionCode, UserID and FingerID. Please download the different modules (net/ multi) at the end of this website.
