...
Hardware | Description | Extra information | Versions | ||
iProtect | SMS | - | From: 9.03.02 Recommended from: 10.01.xx | ||
Pluto | Reader manager | - | From 5.00.41 Recommended from: 5.03.23
| ||
Hardware control applet | only needed when using iProtect version 9.10.xx and lower | From: 3.00 | |||
Orion | Door controller | Bootloader | From: 2.3.0.15 Recommended from: 2.4.2.17 | ||
Firmware | From: 1.4.40 Recommended from: 1.5.18.86 | ||||
Sirius | I Serie | - | From firmware: 1.5.32 | ||
Sirius | IX serie |
| From firmware: 2.0.5.a.1 | ||
SimonsVoss | SmartIntego VCN SI2
| Use with iProtect version 09.03.02 and higheruntil iProtect 10.03. | 2.1.6411.25403 | ||
Use with Smartintego VCN version: 2.1.6411.25403 | Access DB Engine Runtime 2007 | ||||
SmartIntego VCN AX
| Use with iProtect version 10.01.xx and higher | From 3.0.7600.18050 | |||
SimonsVoss lock firmware | SV SI2 Cylinder | 5.4.16 | |||
SV SI2 handle | 5.6.09 | ||||
SV AX handle and Cylinder | 1.1.519 | ||||
Card | Mifare DESFire | - | ev1 and ev2 |
5.6.09 | |||
SV AX handle and Cylinder | 1.1.519 | ||
Card | Mifare DESFire | - | EV1,EV2 and EV3 |
| Note |
|---|
SV SI2 is compatible only up to iProtect version 10.03. Before upgrading to iProtect 10.04, you must transition to the AX protocol. Please refer to the relevant chapter for further details. https://tkhsecurity.atlassian.net/wiki/spaces/KB/pages/9507766290/iProtect+-+SimonsVoss+VCN#7.2-Update-Smartintego-VCN-version%2C-2.6-to-3.0 |
2 Installing the SimonsVoss software
...
DESFire default interpretation (for regular readers)
Enrolment interpretation (for enrolment readers)
Update interpretation (for update readers, and VCN locks)
...
| Note |
|---|
From iProtect 10.04, the Update card data interpretation must be used instead of the Enrollment interpretation at the Enrollment readers. |
3.1 Configuring the card presentation
...
Click in iProtect™ Aurora on the menu item Access | settings | card coding | card number presentation
...
Enter the following data:
Start: 5
Length: 6
Code: the DESFire system code
| Note |
|---|
Setting the system code in hexadecimal format is crucial for optimal performance. |
Click on the created interpretation and go to “facility”.
...
Click in iProtect™ Aurora on the menu item Installation | Hardware | Reader.
Click on the “Search” button and select the Reader that is planned for card enrolment.
Enter the following data:
Name: Specify a logical name
Card data interpretation: Enter the enrolment card data interpretation which is made in chapter 3.1.1
| Note |
|---|
From iProtect 10.04, the Update card data interpretation must be used instead of the Enrollment interpretation at the Enrollment readers. |
Save the data.
Before a card can be enrolled, an offline access profile bust be created. For more information of the availability see chapter 6.2.3.
...
Click in iProtect™ Aurora on the menu item Installation | Hardware | Reader.
Click on the “Search” button and select the Reader that is planned for card update.
Enter the following data:
Name: Specify a logical name
Card data interpretation: Enter the enrolment Update card data interpretation which is made in chapter 3.1
...
Lock: firmware in the lock, presented as X.X.XX
Reader: firmware in the reader, presented as X.XX.XX
6.1.4 4 Unlock time
Default door open time used when a valid card is presented.
...
From iProtect version 10.01.xx Smartintego version 3.0 can be used. Smartintego 3.0 uses however another key set to communicate with the card, AX locks will only work with this key set. For this reason, a migration is needed when Smartintego is updated from version 2.6. to 3.0. This chapter describes the migration steps.
| Note |
|---|
Updating to version 3.x is essential, as iProtect 10.04 will not provide support for version 2.6. |
7.2.1 Migrate the existing cards to the new AX config.
...