...
Technical Manual | TM-20210309-TP-26 iProtect Access / Security | Installation |  |
|
| Table of Contents |
|---|
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.
...
moduleId: The ID of this SAM card on the node. This ID must be used by the reader toselect to select this SAM card for the decoding of the card.
...
Connected: Shown whether the AM SAM card is online.
| Note |
|---|
For the Reader Manager < version 06.00.07 It is important to fully configure all SAM cards that are included in the Charon, even when they are not being used. |
3.2 SAM applications
The applications that are present on the SAM cards are listed in:
...
If there are 4 SAM cards present in a Charon then there will be 4 different reader scripts with samId=0,1,2 and 3. By provisioning these scripts to the readers on the line you can determine which reader uses which SAM, and in this way spread the load. These scripts are called use_SamX.xml with X=0,1,2,3.
| Info |
|---|
For the Reader Manager version 5.03.41 or later, a new command |
| Note |
|---|
For the Reader Manager < version 06.00.07 It is important to fully configure all SAM cards that are included in the Charon, even when they are not being used. |
4.2 Reader keys
Loading the correct keystore in the SAM and instructing the SAM which generation keys to use is a process that requires a number of steps.
Initially the SAM will contain only one application (with AID 92f7 and TKH Security specific keys).
By provisioning a keystore file that contains the TKH Specific keys (RM-SAM.ktl) to the Readermanager node, the Readermanager has the correct keys to communicate with the SAM. Once this has successfully been provisioned to the Readermanager this provisioning element can be removed from the node.
Now the SAM will accept project specific configuration cards. With these cards the keysets can be configured that are used to read the access cards.
First of all a configuration card must be presented that changes the TKH Security specific keys to Customer/Rijkspas specific keys.
Now the first customer configuration card (G0 G0) can be offered to the reader. The customer specific applications are loaded in the SAM. If you have 4 SAMs in the Charon module connected to a Pluto you will have to present the G0->G0 card to 4 readers to configure all SAMs.
If, in the future it is necessary to start using the next generation keyset on the SAM card, you can offer the G0->G1 configuration card to the corresponding reader.
...
iProtect will generate an event in case the configuration card changes the keyset.
| Info |
|---|
For the Reader Manager version 5.03.41 or later, and in conjunction with the The configuration card should be then applied into the reader as long as this LED keeps being blue, until the usual beep is heard and the reader LED returns to its original color (red in most cases). If in this situation the card is retired but the LED in the reader keeps blue, a new application of the configuration card is required in order to program the SAM with the new keys. |
...
5 Reader configuration preparation step-by-step
...
Reader manager: ≥ 05.03.13
Reader keystore: project specific keystore (example: project-x.ktl)
Reader script per SAM (4x) (example: combi-sam0_v3.xml, combi-sam1_v3.xml,
…)Combi script for dualityReader script per SAM (4x) (example: static-rijkspas-sam0.xml, static-rijkspassam1.
xml, …)Rijkspas only script to disable duality
Reader manager keystore SAM (example: reader-manager_SAM.ktl)
...
Reader manager: ≥ 05.03.13
Reader keystore: project specific keystore (example: project-x.ktl)
Reader script per SAM (4x) (example: combi-sam0_v3.xml, combi-sam1_v3.xml,…)Reader script per SAM (4x) (example: static-rijkspas-sam0.xml, static-rijkspassam1.xml,…)
Reader manager keystore SAM (example: reader-manager_SAM.ktl)
...