Kimaldi Kreta3 Assembly instructions

Kimaldi Electronics, S.L.
Ctra. Rubí, 292-B Pol.Ind. Can Guitard
08228 Terrassa (Barcelona) CIF B61802302
www.kimaldi.com
Tel: [phone] Fax: [phone]
E-mail: [email protected]
Installation and
Programming Manual
Kreta3
FingerVein Offline
v. 1.24

Table of Content s
Date19/9/11 Page 2 of 131
Contents
1. About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3. Technical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1. Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2. User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.3. Supported identification methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1. Circuit Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.2. Connection details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.3. Auxiliary circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.4. Actuation parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
5. Host communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.1. Kreta-Classic protocol via RS-232 . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.2. IP Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
5.2.1. Kimaldi Localisation Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.2.2. Kreta-Classic protocol via TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.2.3. Kreta-Classic protocol via UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.2.4. KSP protocol via UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.2.5. KSP via UDP protocol, Backchannel mode . . . . . . . . . . . . . . . . . . . 18
5.2.6. KSP via TCP protocol (TCP-client) . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.3. Addressing and Localisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.3.1. MAC Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.3.2. IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.3.3. KSP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.4. Format for the data transmission to the reader (“Extra Data”) . . . . . . 20
5.4.1. “Extra Data” format through UART or TCP/IP . . . . . . . . . . . . . . . . 20
5.4.2. “Extra Data” format via UDP / KSP . . . . . . . . . . . . . . . . . . . . . . . . . 21
6. User interface configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.1. Default user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
6.2. External user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
6.3. Auxiliary Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
6.4. Kreta3 with double user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
7. Kreta3-UI module configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.1. Programming method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.1.1. Configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
7.1.2. Data formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Tabl e o f C o n tent s
Date19/9/11 Page 3 of 131
7.2. Configuration examples, readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.2.1. Main Reader, Hexadecimal, RS-232 . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.2.2. Auxiliary Reader, Hexadecimal, RS-232 . . . . . . . . . . . . . . . . . . . . . 28
7.2.3. Main Reader, Clock&Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.2.4. Auxiliary Reader, Clock&Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7.2.5. Primary or Auxiliary Readers, Decimal RS-232 . . . . . . . . . . . . . . . . 29
7.2.6. Stand-alone Readers, RS-232 (Mifare, chip) . . . . . . . . . . . . . . . . . . 29
7.2.7. Multiple reader configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.2.8. Activation of reading via digital input . . . . . . . . . . . . . . . . . . . . . . . 30
8. General presentation on Kreta3 module operation . . . . . . . . . . . . . . . . . . . 32
8.1. Attendance Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
8.1.1. Main reader readings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
8.1.2. Auxiliary reader readings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
8.2. Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
8.2.1. Main reader accesses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
8.2.2. Auxiliary reader accesses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
8.3. Automatic Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.3.1. Through the main reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.3.2. Through the auxiliary reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.4. Terminal locked. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.5. Free access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
8.6. Automatic change in access conditions . . . . . . . . . . . . . . . . . . . . . . . 37
8.7. Full capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
9. Additional functions of the Kreta3 module . . . . . . . . . . . . . . . . . . . . . . . . . . 38
9.1. Alarm management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
9.1.1. Door alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
9.1.2. Reader alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
9.1.3. Antipassback alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.1.4. Alarm deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.1.5. Readings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
9.1.6. Partial alarm deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
9.2. Task Programmer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
9.2.1. Shift Change Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
9.2.2. Automatic change in access conditions . . . . . . . . . . . . . . . . . . . . . . . 43
9.2.3. Automatic adjustment to summer time . . . . . . . . . . . . . . . . . . . . . . . 45
9.3. Access control auxiliary functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
9.3.1. Antipassback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
9.3.2. Multipost antipassback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
9.3.3. Access balance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
9.4. Capacity Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
9.5. Personalised Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
9.6. Online control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
9.6.1. Battery condition and digital input monitoring . . . . . . . . . . . . . . . . . 48
9.6.2. Relay activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
9.6.3. Online reception of readings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
9.6.4. Semi-Online Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
9.7. Battery monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Tabl e o f C o n tent s
Date19/9/11 Page 4 of 131
9.8. Exit pushbutton . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
9.9. Access control semaphore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
9.9.1. “Three status” mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
9.9.2. “Two status” mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
9.10. Remote FW updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
9.11. Information on exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
10. Programming model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
10.1. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
10.1.1. Parameter array, Kreta3-DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
10.1.2. Parameter array, Kreta3-UI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
10.1.3. Message array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
10.1.4. Day array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
10.1.5. Month array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
10.1.6. IP Configuration - TCP and UDP Sockets . . . . . . . . . . . . . . . . . . . 59
10.1.7. Printer message array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
10.2. Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
10.2.1. Clock/Calendar Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
10.2.2. Public Holiday Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
10.2.3. Schedules Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
10.2.4. Weekly Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
10.2.5. Incidents Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
10.2.6. Concepts Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
10.2.7. Permissions Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
10.2.8. Exceptions Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
10.2.9. Readings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
10.2.10. Personalised Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
11. Description of the instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
11.1. General operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
11.1.1. Write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
11.1.2. Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
11.2. Configuration operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
11.2.1. Write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
11.2.2. Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
11.2.3. Apply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
11.2.4. Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
11.3. Data base operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
11.3.1. DeleteTable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
11.3.2. DeleteRecord . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
11.3.3. DeleteByCode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
11.3.4. Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
11.3.5. Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
11.3.6. Size&Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
11.3.7. Retrieve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
11.3.8. RetrieveNext . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
11.3.9. RetrieveNextByCode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Tabl e o f C o n tent s
Date19/9/11 Page 5 of 131
11.4. Operations on peripherals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
11.4.1. Write CFG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
11.4.2. Read CFG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
11.4.3. Scan FP 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
11.4.4. Firmware Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
11.4.5. Database Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
11.4.6. Communications error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
11.5. Peripheral equipment operations (Stand-alone reader RS-232) . . . . 86
11.5.1. Send Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
11.6. Operations on peripherals (Kreta3-UI module) . . . . . . . . . . . . . . . . 87
11.6.1. Write CFG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
11.6.2. Read CFG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
11.6.3. Apply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
11.6.4. Default . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
11.6.5. Relay Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
11.6.6. Communication ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
11.6.7. Digital inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
11.6.8. Firmware Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
12. Biometric identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
12.1. Types of biometric identification . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
12.2. Configuration of biometric readers . . . . . . . . . . . . . . . . . . . . . . . . . . 93
12.3. Configuration examples, biometrics . . . . . . . . . . . . . . . . . . . . . . . . . 94
12.3.1. Biometric identification modules . . . . . . . . . . . . . . . . . . . . . . . . . . 94
12.3.2. Reduced biometric identification, 1:n . . . . . . . . . . . . . . . . . . . . . . . 95
12.4. Basic instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
12.4.1. Retrieve sensor version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
12.5. Capture of biometric information . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
12.5.1. Capture of biometric information . . . . . . . . . . . . . . . . . . . . . . . . . . 96
12.6. Sensor memory management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
12.6.1. Add user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
12.6.2. Request number of users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
12.6.3. Delete user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
12.6.4. Delete all users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
12.7. Operation details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
12.7.1. Configuration of the FIM biometric module . . . . . . . . . . . . . . . . . . 99
12.7.2. User database management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
12.7.3. Format for the biometric data transmission (“Extra Data”) . . . . . 103
12.7.4. Local user creation procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
12.8. User permissions with “Biometric exceptions” . . . . . . . . . . . . . . . 105
12.9. High level operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
12.9.1. Biometric identification module . . . . . . . . . . . . . . . . . . . . . . . . . . 106
13. Printing of reading tickets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
13.1. Terminal configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
13.2. Ticket personalisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
13.2.1. Message personalisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
13.2.2. Modification of the design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Tabl e o f C o n tent s
Date19/9/11 Page 6 of 131
AppendixA. Programming model summary . . . . . . . . . . . . . . . . . . . . . . . . . . 112
A.1. Configuration diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
A.2. List of commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
AppendixB. Templates for integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
B.1. Kreta3 drills . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
List of Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
List of revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Kreta3 - FingerVein Offline
Installation and Programming Manual
www.kimaldi.com Page 7 of 131
1. About this Manual
This manual applies to the Kreta3 and FingerVein-OffLine terminals, dedicated to
Attendance Control and Access Control. In terms of Firmware level, it corresponds to
firmware version 0x6B.32 (‘k2’) and after.
From this point onwards and unless otherwise stated, all the characteristics and functions
described in this manual apply to the Kreta3, will also apply to the FingerVein-OffLine.
Reading this manual before installing the Kreta3 module is essential. In order to install
the OEM product, it is essential that you read chapter 6.: “User interface configuration”
and chapter 7.: “Kreta3-UI module configuration” .
Kimaldi Electronics reserves the right to make any changes to the Hardware or Firmware
of the Kreta3 module, if deemed necessary. In such cases, a new version of this manual
shall be published.
2. Description
The Kreta3 module is a high performance terminal, adaptable, by configuration, to many
very different combinations of readers, actuators, and user interfaces.
It accepts two types of biometric identification technology:
- Fingerprint: using the FIM2030 sensor from Nitgen.
- Vascular: using the FingerVein sensor from Hitachi.
Based on a product which is 100% compatible with the Kreta v1 both at interface,
software and connectivity levels, the Kreta3 Module adds speed, flexibility and
application features for Access and/or Attendance control in Offline operations:
• Offline Access Control Application
• Offline Attendance Control Application
• Data base with 7,500 permissions, 3,000 exceptions and 15,000 readings1
• Double Access and/or Attendance Control or Entrances and Exits (allows up to 2
identical user interfaces): 2x20 alphanumeric display and 4x4 keypad.
• Connectivity to Host: Integrated RS-2322and Ethernet3, optional WiFI.
• Connectivity with readers: each user interface supports a Clock&Data reader, a
biometric reader and/or RS-232 reader.
1. Other configurations of the Database available on special order
2. It has a RS-232 output adaptable to USB. Contact Kimaldi for further details.
3. TCP and UDP protocols.

Kreta3 - FingerVein Offline
Installation and Programming Manual
www.kimaldi.com Page 8 of 131
• Biometrics support:
- Up to 2 biometric identification sensors per terminal1.
- Possibility for using biometric technology2:
- Fingerprint:
- Up to 4,000 users according to sensor.
- Identification modes: 1:1, 1:N, 1:n
- Vascular biometrics:
- Up to 1,000 users.
- Identification modes: 1:1 and 1:N
• Security: segregatable user interfaces, leaving the Database and relays in a safe
area.
• Extra functionalities:
- Door control alarm
- Shift change warning signal
- Automatic change in access conditions
- Antipassback
- Capacity control
- Personalised messages / hour totals
- Remote FW updating.
- Programming change to summer / winter time
Internally, the Kreta3 module is organised in two subelectronics capable of segregating,
in the following manner:
1. DB module: includes the database, relays and connectivity to the Host. It is
designed to be installed in a safe area, for example a false roof.
2. UI module (“Main UI”): includes all the part of the User Interface (card readers,
biometrics, display, keypad, buzzer). It is designed to be exposed to interaction with
the user, generally assembled in a plastic box or panel.
3. If an auxiliary reader is required, it will constitute a second UI module (“Auxiliary
UI”), for which we can choose an equal (display and keypad) or lower (LEDs)
degree of functionality than the Main UI.
1. Using an auxiliary UI electronics is necessary to use a second biometric reader.
2. There is no biometric information compatibility between the different biometric technologies
(fingerprint and vascular).

Kreta3 - FingerVein Offline
Installation and Programming Manual
www.kimaldi.com Page 9 of 131
3. Technical Characteristics
3.1. Specifications
Dimensions: OEM electronics: 134 x 131 x 25 mm
Stainless steel box: 142 x 209 x 82 mm; Weight 1.5 kg
Office box1: 160 x 220 x 65 mm; Weight 750 g.
Power Supply: Voltage:
- Kreta3: 5 Vdc ± 10%
- FingerVein-OffLine: 12 Vdc ± 10%
Current: 1A typical (according to amount and type of readers)
Contact relays: 42contact relays, normally open, 24V / 1A
Display: LCD Display, 20x2 characters
Keypad: Matrix keypad with 4 rows x 4 columns
Digital inputs: 53relay type digital inputs. In open circuit (contact open) its
logic value will be 0. In contact with earth (contact closed),
logic value 1.
Buzzer: 1 Internal buzzer (operates together with the main reader and
keypad)
Clock & Data input: In the UI module, allows the connection of a device that
transmits in Clock&Data with ABA encoding, Track 2.
RS232 Interface: 3 configurable serial ports: communication with the Host or
with card readers. Baud Rate: 9600, 19200 or 38400. Other
parameters: n,8,1.
Output for external reader power supply: 5 Vdc for power supply of the auxiliary reader
with a current capacity of 200 mA.
Ethernet Connection: Protocols: TCP/IP, UDP, ARP, DHCP, ICMP (ping) Speed:
10/100 BaseT
Connector: RJ-45
Real Time Clock
Microcontroller: Double (DB + UI), 32 bit RISC architecture
Clock frequency: 60 MHz in DB electronics, 48 MHz in UI
Memory: 1024 kb, SRAM, non-volatile (with CR2032 lithium battery)
1. Option not yet available for FingerVein-OffLine.
2. Four serial relays, two more optional
3. There is a sixth input in the UI module, for an Anti-Tamper sensor

Kreta3 - FingerVein Offline
Installation and Programming Manual
www.kimaldi.com Page 10 of 131
3.2. User interface
Input elements:
Green key (“Enter”) Indicates Incident 01 (“Entrance”), and is also used to
validate the introduction of the incident code.
Red key (“Exit”) Indicates Incident 02 (“Exit”), and is also used to cancel and
restart the introduction of the incident code.
F1 key / Up Allows an incident other than that which is activated by
default to be indicated (Mass Reading mode). Browsing key
for incident selection.
F2 key / Down Browsing key for incident selection. Enables the input of an
up to 8 digit identification code using the keypad, if
configuration allows.
CLR key Deletes and restarts the input of the 8 digit code using the
keypad.
0...9 keys Allows numeric codes to be input (normally the incident code
or PIN).
ENTER key Allows validating the incident code input.
Output elements:
LCD Display We have a 20 character x 2 line display. The first line
indicates the date and time, whilst the second line is used to
guide the user through their interaction with the equipment.
Buzzer Signals correct operation of the keypad, as well as the success
or failure of the user identification process.

Kreta3 - FingerVein Offline
Installation and Programming Manual
www.kimaldi.com Page 11 of 131
3.3. Supported identification methods
The Kreta3 module comprises the following methods for identifying people:
• Proximity, 125 kHz: connection via Clock&Data or RS-232.
• Proximity, 13.56 MHz, ISO 14443-A (Mifare): connection of a Kimaldi KRD13M
reader is possible via Clock&Data1or RS-232.
• Fingerprint biometrics: connection via RS-232 to FIM2030 modules for 4,000
users. 1:N or 1:1 identifications can be carried out in combination with a
proximity reader.
• Vascular biometrics: connection via RS-232 to FIM2030 modules for 1,000 users.
1:N or 1:1 identifications can be carried out in combination with a proximity
reader.
• Microprocessed card (ISO 7816, T=0) or memory card (SLE4442): Kimaldi
SC6000 or SC42 readers allow connection via Clock&Data or RS-232.
• DNIe: Spanish electronic National Identity Document. can be connected via
Clock&Data (ABA, Track 2) or RS-232 (decimal or ASCII-Hex format).
• Magnetic strip: can be connected via Clock&Data (ABA, Track 2) or RS-232
(decimal or ASCII-Hex format).
• Bar code: normally via RS-232 (decimal format).
• Other formats (DESFire, HiD, etc.) available according to project.
1. Only for Cascade Level 1 cards

Kreta3 - FingerVein Offline
Installation and Programming Manual
www.kimaldi.com Page 12 of 131
4. Installation
4.1. Circuit Diagram
CAUTION!
When handling this product, take the necessary antistatic precautions
to avoid possible damage to the sensitive electronic devices.
J3
RELAY 1-A RELAY 1-B RELAY 2-A RELAY 2-B RELAY 3-A RELAY 3-B RELAY 4-A RELAY 4-B
J2
5V out GND Tx-232 UI-2 Rx-232 UI-2 DIN_1 DIN_2 DIN_3 DIN_4
1 2 3 4 5 6 7 8
1 2 3 4 5 6 7 8
J14: TTL-0
1
J16: Keypad
J17: Display
J12: Reader
J15: DIN_1-UI
J7: Ethernet
Back-up Battery
J11
RELAY UI-2-B RELAY UI-2-A RELAY UI-1-B RELAY UI-1-A
J10
GND DATA TTL-0 CLOCK TTL-0 CLS TTL-0 5V out GND TX-232-Read RX-232-Read
8 7 6 5 4 3 2 1 4 3 2 1
Anti-Tamper
1
1
J5: KiWi
Jumpers: App_ID
UART1-DB
UART2-UI
UART1-UI
UART0-DB
UART0-UI
UART2-DB

Kreta3 - FingerVein Offline
Installation and Programming Manual
www.kimaldi.com Page 13 of 131
4.2. Connection details
Power supply jack:
Without FingerVein biometric reader the terminal is powered at 5V (jack on the
Kreta3-DB electronic board)
With FingerVein biometric reader the terminal is powered at 12V (jack in the
KiWi terminal (12V to 5V voltage converter)
J2 - Main Connector
Pin 1 - Positive power supply pole for Auxiliary UI (5 Vcc).
Pin 2 - Negative power supply pole for Auxiliary UI (GND).
Pin 3 - TX signal for communication with Auxiliary UI.
Pin 4 - RX signal for communication with Auxiliary UI.
Pin 5 - Entrance Door sensor (Digital Input 1)
Pin 6 - Pushbutton for Main User Interface (Digital Input 2)
Pin 7 - Exit Door sensor (Digital Input 3)
Pin 8 - Pushbutton for Auxiliary User Interface (Digital Input 4)
J3 - Relay Connector
Pin 1 - Pole A of the Entrance Door Relay (Relay 1)
Pin 2 - Pole B of the Entrance Door Relay (Relay 1)
Pin 3 - Pole A of the Alarm Relay (Relay 2)
Pin 4 - Pole B of the Alarm Relay (Relay 2)
Pin 5 - Pole A of the Exit Door Relay (Relay 3)
Pin 6 - Pole B of the Exit Door Relay (Relay 3)
Pin 7 - Pole A of the Shift Change Signal Relay (Relay 4)
Pin 8 - Pole B of the Shift Change Signal Relay (Relay 4)
J5: Connection to KiWi module.
J7: Ethernet Connector (RJ45 connection)
J10 - Connector to Card Readers / Printer
Pin 1 - Signal Rx 232 to the device (Pin no. 2 connector SubD male)
Pin 2 - Signal Tx 232 to the device (Pin no. 3 connector SubD male)
Pin 3 - Negative power supply pole (GND) (Pin no. 5 connector SubD male)
Pin 4 - Output +5 VDC
Pin 5 - CLS signal (TTL_0)
Pin 6 - Clock signal (TTL_0)
Pin 7 - Data signal (TTL_0)
Pin 8 - Power supply negative (GND)
J11 - Connector to Signal Relays (optional)

Kreta3 - FingerVein Offline
Installation and Programming Manual
www.kimaldi.com Page 14 of 131
J12: Connection to FIM or FingerVein biometric identification module.
Pin 1 - Output +5 VDC (Do not connect to FingerVein)
Pin 2 - UART1-UI - Signal Tx 232 to reader
Pin 3 - UART1-UI - Signal Rx 232 to reader
Pin 4 - Power supply negative (GND)
J14 - Connector TTL_0 to Card Reader:
Pin 1 - Data signal (TTL_0)
Pin 2 - Clock signal (TTL_0)
Pin 3 - CLS signal (TTL_0)
Pin 4 - Output +5 VDC
Pin 5 - Power supply negative (GND)
J15: Digital input DIN_1-UI. Input activated when it is connected to GND, deacti-
vated if left without connection.
Jumpers:
Application_ID - Encoded by two jumpers. By default, the value is 3.
Back-up Battery: this is a 3V lithium battery, size CR2032. If a low battery level is
detected, we recommend replacement of the battery whilst the equipment is on. This
therefore avoids configuration and unit database losses.
In addition, we have the connections to Keypad and Display for the OEM version of the
equipment:
J16: 4x4 Keypad connector
Pin 1 - Column 3 (OUT) Pin 5 - Row 0 (IN)
Pin 2 - Column 2 (OUT) Pin 6 - Row 1 (IN)
Pin 3 - Column 1 (OUT) Pin 7 - Row 2 (IN)
Pin 4 - Column 0 (OUT) Pin 8 - Row 3 (IN)
J17: Connector to 20x2, with incorporated Backlit.
4.3. Auxiliary circuits
The Kreta3 Module allows connection to an auxiliary User Interface (UI) that
implements the elements required for identifying and signalling, either simply (KBio2-
UI, KRD13M v2) or fully (BioMax2-UI).
For Attendance Control, these features allow user interfaces to be duplicated, therefore
having two terminals in just one product.

Kreta3 - FingerVein Offline
Installation and Programming Manual
www.kimaldi.com Page 15 of 131
4.4. Actuation parts
The Kreta3 Module has from 4 to 6 relays on the board itself. The functions of these
relays are as follows:
• Relay 1: opening the door. This relay is activated for both entry and exit, i.e. both
by a correct identification from the main reader and from the auxiliary reader. If
the unit is configured for two doors, Relay 1 acts on the entrance door (main
reader).
• Relay 2: alarm siren. This relay acts as the door alarm siren.
• Relay 3: exit door opening. This relay is only activated if we have the unit
configured for two doors. Relay 3 corresponds to the exit door, activated by the
auxiliary reader.
• Relay 4: shift change siren. This relay acts as the shift change siren, if the siren is
activated.
Low demand, with the possibility for assembling two extra relays on the main UI, for
signalling mass entrances/exits or signalling indicator:
• Relay 1-UI: “Entry” signal in “Mass Reading” mode. An indicator light can be
activated to indicate "Entry" mode. If CFG-UI_TimeRelay has a non-null value,
it allows activating a luminous indicator corresponding to a green semaphore.
• Relay 2-UI: “Exit” signal in “Mass Reading” mode. An indicator light can be
activated to indicate "Exit" mode. If CFG-UI_TimeRelay has a non-null value, it
allows activating a luminous indicator corresponding to a red semaphore.

Kreta3 - FingerVein Offline
Installation and Programming Manual
www.kimaldi.com Page 16 of 131
5. Host communications
The Kreta3 module allows various communication routes with the Host. Establishing
this communication is the first step towards correctly configuring the Kreta3. The Kreta3
module is permanently listening to these channels, and will return a response via the
channel from which the command was received.
The configuration parameters dealt with in this chapter are:
• $0D: CFG_ResponseChannel. Read only We can consult this field to know in
which channel the last communication has occurred.
• $1C: CFG_SerialPortHost. Default value: $00
The detailed programming model can be found in Table 12.1 and in chapter 11.2..
5.1. Kreta-Classic protocol via RS-232
The UART1 port relates, by default, to communications with the Host via RS-232. This
communication is established, by default, at 9600 bps, with 8 bits, no parity and one stop
bit. The serial frames are constructed by placing the starting character <STX> (ASCII
$02) before the instruction and placing the character <ETX> (ASCII $03) at the end of
the block. The unit will do the same with any responses that it issues.
For the configuration byte CFG_SerialPortHost, however, we have other alternatives:
• Communication speed can be configured to 9600, 19200 or 38400 baud. To do so,
the CFG_SerialPortHost byte must take the following values $00, $01 or $02,
respectively.
• Values other than those indicated above, are used for many purposes, as we will see
later. In these cases, the UART1 port stops interacting with the Host. If this
occurs, the UART2 port is automatically configured with the value $00, so that a
“back door” is left open to connect to the Kreta3. This UART2 is only available
in TTL levels and is accessed via the J5 connector (refer to section 4.1), by
means of a USB adaptor cable supplied by Kimaldi.
In cases where the use of adapter boards for other protocols is required (for example,
WiFi, TCP/IP, Bluetooth...), this will be done from this UART1 port.
The CFG_ResponseChannel parameter takes the value $01.
5.2. IP Communications
To access the IP communication services, the network parameters must be configured
correctly. Configuration can be carried out using the Kreta-Classic protocol, via RS-232,
although we will normally use the Kimaldi Localisation Service detailed below. Once
the equipment is configured, we will have two different protocols through TCP or UDP
Sockets.

Kreta3 - FingerVein Offline
Installation and Programming Manual
www.kimaldi.com Page 17 of 131
5.2.1. Kimaldi Localisation Service
It is possible to detect the Kreta3 modules that are connected to our local area network
by using the Kimaldi Localisation Service:
• IP configuration: once the unit is localised from its MAC Address, we are able to
configure its IP parameters and restart the unit.
• The localisation request from the Host to the Kreta3 module is done using port
2000.
• The reception of frames at the Host from the Kreta3 module is done using port
2001.
There is a DLL which allows this Service to be integrated into any software application.
For more detailed information on the low level protocol, refer to the SLK Programming
Manual.
5.2.2. Kreta-Classic protocol via TCP
The Kreta-Classic protocol is also available through a TCP Socket, so that it is totally
compatible with the KiWi2 converter module:
• The Kreta3 module is in server mode. Therefore, frames can be accepted from any
Host (refer to SLK-Security in Subsection 10.1.6.) The connection socket will
always be started by the Host. Kreta3 will only generate TCP events while this
socket is active.
• The transmission of commands from the host to the Kreta3 module is done through
the port that we choose on the Host (Local Port of the Host). We will configure
TCP Port-RemoteHost to 0000 (refer to Subsection 10.1.6., parameter $1E).
• The frames are received at the Kreta3 module using port 1001 (Remote Port from
the Host).
Serial frames will consist of ASCII-Hex values according to the frame format described
in chapter 11. The <STX>,<ETX> delimiting characters will be included.
The CFG_ResponseChannel parameter does not apply in this case, as TCP events cannot
be generated spontaneously (i.e., events will not be generated until the Host has initiated
the socket).
In contrast, it is possible to have an open TCP against a computer other than the one we
have declared as Remote Host. We have to be very cautious in this case, as there may be
two Hosts acting simultaneously on Kreta3.
5.2.3. Kreta-Classic protocol via UDP
The Kreta-Classic protocol is also available via a UDP Socket.
• We should define the IP address of our Host beforehand (IP-RemoteHost).
• The transmission of commands from the host to the Kreta3 module is done through
the port that we choose on the Host (Local Port of the Host). From the Kreta3
point of view, this is the Remote Host Port, which can be configured (Port-

Kreta3 - FingerVein Offline
Installation and Programming Manual
www.kimaldi.com Page 18 of 131
RemoteHost; refer to Subsection 10.1.6., parameter $07) and which is 5001 by
default.
• The frames are received at the Kreta3 module using port 5000 (Remote Port from
the Host).
From then on, frames can be sent in an identical format to the serial frames, including
delimiting characters <STX>,<ETX>.
The CFG_ResponseChannel parameter takes the value $07.
5.2.4. KSP protocol via UDP
Finally, the Kreta3 module allows operation with the new Kimaldi Stackable Protocol
(KSP). KSP operates through another UDP Socket:
• The transmission of commands from the Host to the Kreta3 module is always done
through Host port 60011, and using Broadcast IP frames. This means that a
special block format will be used which will allows us to specify the node at KSP
level.
• The frames are received at the Kreta3 module using port 6000 (Remote Port from
the Host).
• One important advantage in relation to the Kreta-Classic protocol, is that the Host
may receive all Online Event blocks, generated from any Kreta3, through only
one Socket on port 6001. These blocks also carry the address of the node that
generated them.
There is an ActiveX control for interacting with the Kreta3 module through KSP. Refer
to the corresponding manual for more details.
The CFG_ResponseChannel parameter takes the value $08.
5.2.5. KSP via UDP protocol, Backchannel mode
The KSP Port-RemoteHost remote port can be configured (refer to Subsection 10.1.6.,
parameter $1F) of the KSP-UDP protocol with the value 6000 instead of the normal
6001. In this situation, all the Kreta3 units connected to the network will have visibility
of the frames sent to the Host. This will let us implement a Backchannel for the different
Kreta3 units to share information from the Online events that are generated.
When the KSP-UDP operates in Backchannel mode, it is not advisable to have the Host
with the 6000 port open. If it were to be necessary to establish this connection, consult
Kimaldi.
1. In reality, it is a configurable parameter, although modifying it is not advisable. Refer to KSP-
Port-RemoteHost in Subsection 10.1.6.

Kreta3 - FingerVein Offline
Installation and Programming Manual
www.kimaldi.com Page 19 of 131
5.2.6. KSP via TCP protocol (TCP-client)
In Subsection 5.2.2. we saw how the TCP Socket works in server mode, answering
requests that may arrive from any Host. There is also an additional option, consisting of
enabling an application in server mode in the Host (this is obtained via the KSP-OCX)
and configuring the Kreta3 terminals as clients. This function is very similar to the
Subsection 5.2.4., but on TCP instead of UDP. To enable this channel, you should:
• Define the IP-RemoteHost (the same one used for the UDP sockets).
• Define the Host port we will have to connect to (TCP Port-RemoteHost). We will
typically use the 6601 port.
• Communication with Kreta3 is carried out via the 6600 port.
The CFG_ResponseChannel parameter takes the value $0C.
5.3. Addressing and Localisation
The Kreta3 module can be addressed from its IP, but also has a logical address to be
integrated in a KSP network. For this reason, there will several addressing modes. The
different addresses of a Kreta3 module can be consulted in the Group 3 instructions
(refer to chapter 11.2.: “Configuration operations” ) or at the Kimaldi Localisation
Service (refer to the SLK Programming Manual).
5.3.1. MAC Address
The MAC Address of a Kreta3 module is unique and assigned by the manufacturer. It is
labelled above the electronics in hexadecimal format.
5.3.2. IP Address
The IP address of each Kreta3 module will be assigned by the user based on the
characteristics of the local area to which it is connected. It can also be assigned by the
LAN server, if we have the DHCP protocol activated. This is generally a configuration
field, which can be modified by the user through the Kimaldi Localisation Service or any
service for connection to the Host (refer to all configuration fields in Subsection 10.1.6.).
5.3.3. KSP Address
If we communicate with the Kreta3 module via KSP (Subsection 5.2.4.), its
corresponding address is also determined using the DIP Switches. This protocol always

Kreta3 - FingerVein Offline
Installation and Programming Manual
www.kimaldi.com Page 20 of 131
uses extended addressing, so the module address will have two parts. From most to least
significant, they are:
- KSP Application ID: this has a value between 11 and 14 ($0B and $0E), obtained
by adding 11 to the JP1, JP2 value.
- KSP Node ID: it is a 8 bits value, ranging between 1 and 254, that we have stored
in the configuration byte KSP-Address_Low.
JP2 is the heaviest bit, followed by JP1. The jumpers take logic value 1 when the bridge
is on and 0 if not. KSP-Address_Low takes by default the value of the lightest byte of the
MAC Address, although it can be changed.
The Kreta3 module reads the configuration of the jumpers and KSP-Address_Low when
it receives power. Therefore, if the address is to be changed, the power should be
momentarily disconnected or code 313 should be sent in order for the changes to take
effect.
5.4. Format for the data transmission to the reader (“Extra Data”)
In cases where dealing with biometric readers and in cases where we have to programme
reading sequences on stand-alone readers such as KRD13M or KMD42Plus, or to send
the scripts to the printer, we need to send information "through" the Kreta3 module.
These frames will not be interpreted by the Kreta3 module, and they will therefore be
dealt with in a different way to normal data blocks.
For the reasons already mentioned, the block sent directly to the readers will be called
“Extra Data”, and will be transmitted after a block separating character (the “End
Transmission Block” character or <ETB>, ASCII $17)
The “Extra Data” format will be different, depending on whether the block is sent via the
RS-232 port (or any communication converter connected via the RS-232) TCP/IP or via
UDP.
5.4.1. “Extra Data” format through UART or TCP/IP
[Length][Data][CRC]
- [Length]: 4 bytes in ASCII-Hex format. The maximum supported length is 912
($0390).
- [Data]: String of 2*[Length] bytes. Contains the binary information
expressed in ASCII Hex. For example, one byte with a value of $3F will be
encoded as ‘3F’, which refers to bytes [$33 $46].
- [CRC]: 2 bytes in ASCII-Hex format. This constitutes the sum of all of the
ASCII-Hex [Length] and [Data] bytes in 255 module, this value is then
later converted to ASCII-Hex.
Remember that “Extra Data” will be preceded by the <ETB> character (End
Transmission Block, ASCII $17), and the frame will be closed with the <ETX> (ASCII
$03)character.