Kimaldi

Control de Acceso y Presencia - Biometría - RFID

You are here: Home / Biometric Systems / Kimaldi / Kimaldi Kapri Online Bio and RFID – Fingerprint, RFID and Mobile Access
Kimaldi Kapri Online Bio and RFID

Kimaldi Kapri Online Bio and RFID – Fingerprint, RFID and Mobile Access

Access Control Solutions and T&A and Production Control Terminal by fingerprint, RFID tags (cards, wristbands and key fobs) and mobile.

Real time online operation, with Ethernet connection, WiFi (optional) and various communication options, including a Cloud protocol that allows direct connection to the cloud without the need to install anything on the LAN.

Contact
Categories: ,

Product Description

    • Biometric ID terminal
    • 2.4” IPS Graphics Display and Touch Keyboard
    • 3 Relays and 4 Digital Inputs
    • Ethernet Connection and Wifi Option
    • Web Programming
    • CLOUD Protocol: Cloud Direct Connectivity
    • Other Protocols to Work within the LAN
    • WebServer Device Configuration
    • Options: Mifare/Desfire Card Reader and BLE Reader
    • Integration module

Kimaldi Kapri Online Bio y RFID_huella

3 Relays and 4 Digital Inputs

Kapri Online Bio includes 3 relays to activate electric locks, turnstiles, barriers, alarms or other devices.

The device has 4 digital inputs to monitor the status of door sensors, limit switch sensors, etc.
The device is equipped with an Anti-Tamper Sensor.

 

Ethernet Connection and Wifi Option

The device is connected via Ethernet and communication with the application always takes place via the exchange of JSON objects. It is easy to integrate regardless of the programming language or operating system you use.

Kapri Online Bio is available in a Wifi version.

CLOUD Protocol: Cloud Direct Connectivity

This is the most suitable option for extranet web applications. In these environments, and often for safety concerns, only the devices can initiate contact, as the cloud-based software is often not permitted to initiate contact with the devices. Kapri Online Bio initiates communications, and when an event occurs, such as a card being read, it sends a POST command to the cloud application/API Server. The application then sends a set of commands to be executed by the terminal, such as displaying messages on the screen and activating relays to allow access.

Cloud Protocol Characteristics:

– Kapri initiates all communications.
– Communications are secure when the cloud uses the https protocol.
– No installation of drivers, .DLLs, services, etc. required.
– Easy installation. It does not have to be installed locally.

For more information, please check the Kapri CLOUD tab.

Other protocols for working within the LAN

Kapri Online Bio offers the following communication protocols:

  • JSON-TCP/IP
  • KTP
  • HTTP

* For more information, see the Communication Protocols Tab.

Options: Mifare/Desfire Card Reader and BLE Reader 

As an option, a 125kHz RFID reader or a Mifare/Desfire Card Reader (which allows reading the UID and memory sectors of the card) can be added.

The BLE option allows users to identify themselves by means of a high-security virtual card on their mobile phone.

Integration Module

Kimaldi Kapri Bio is available in an integration module finish for installation on turnstiles, barriers and gates.

Specifications

Power Supply

5 VDC +/-10%
Maximum Consumption

1500 mA
RS-232

2 internal ports:
– RFID reader
– Biometric reader
TTL

2 internal ports:
– Clock&Data reader, ABA Track-2.
– Wiegand 26, 34 and free reader
Digital Inputs

4 digital inputs active to ground, inactive on O.C.
Relay

3 relays, power-free, 24V/1A (24/1A: 500,000 switching operations)
2 relays with NC and NO contacts, and 1 NO relay
AntiTamper

1 antitamper input
Buzzer

1 in-circuit integrated
RTC

1 in-circuit integrated
keyboard

16-key capacitive touch
Ethernet

10M/100M/1000M
Wifi

Optional
Operating Temperature

-20ºC a 50ºC
Display

2.4'', IPS, 320 x 240
Dimensions (mm)

135.68*131.54*41
Biometric Technology

Fingerprint
RFID Technology

125 kHz, 13,56 MHz
RFID Solutions

Access Control, Readers for industrial applications

Kapri communicates via TCP/IP (Ethernet cable or WiFi). Communication with the application is always done through the exchange of JSON objects.

To make configuration easier, you can access the browser by connecting to the Kapri WebServer and, from there, selecting the communication protocol.

The equipment offers the following protocols:

JSON-TCP/IP

The terminal provides a TCP/IP communication port through which it will send and receive JSON objects. This port can work as Server or Client depending on how it is configured.

This is the most suitable option for applications in languages which do not allow the use of web protocols, but which can handle standard TCP/IP sockets.

KTP

It is a Kimaldi proprietary protocol with a KTP network driver. It performs the following functions:

– It automatically locates LAN terminals.

– It provides an API interface to the software

– It provides a SocketIO channel for event management.

– It encrypts communications with AES256.

This is the best option for those intranet applications having to manage several devices whose IP address is unknown. The application interacts exclusively with the KTP network driver/controller. In addition, KTP allows different applications to control different terminals, by grouping them on the same LAN.

HTTP

The terminal provides an API Server interface that supports POST and GET commands. There is an option for the terminal to send events via SocketIO to avoid the application polling. No driver installation is required. The application needs to know the IP of the terminal.

This is the best option for intranet web applications, as in these environments these applications can freely access devices.

CLOUD

The terminal always initiates communications. When an event such as a card being read occurs, the terminal sends a POST command to the application/cloud API server. In response, the application sends a batch of commands, such as displaying messages on the screen and activating relays to allow access in order to be executed by the terminal.

The Cloud protocol is characterized by:

– Kapri initiates all communications.

– Communications are secure when the cloud uses the https protocol.

– No driver installation is required.

– The application does not need to know the IP of the terminal.

This option is most suitable for extranet web applications. In these environments, the cloud application is usually not allowed to initiate communication for security reasons. Hence, only terminals can initiate that.

CLOUD

The terminal always initiates communications. When an event such as a card being read occurs, the terminal sends a POST command to the application/cloud API server. In response, the application sends a batch of commands, such as displaying messages on the screen and activating relays to allow access in order to be executed by the terminal.

The Cloud protocol is characterized by:

– Kapri initiates all communications.

– Communications are secure when the cloud uses the https protocol.

– No driver installation is required.

– The application does not need to know the IP of the terminal.

This option is most suitable for extranet web applications. In these environments, the cloud application is usually not allowed to initiate communication for security reasons. Hence, only terminals can initiate that.

Since there is no dependence on the end-user infrastructure, Kapri terminals are easy to relocate.

Kapri Brochure

You may also like…