SmartIntego settings: Difference between revisions
Telcredstaff (talk | contribs) No edit summary |
Telcredstaff (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
There are a few settings that are necessary in order for locks from SimonsVoss SmartIntego to work correctly. |
There are a few settings that are necessary in order for locks from SimonsVoss SmartIntego to work correctly. A few overall settings are found in the [[Delegation|Organization Owner]] view and must match the programming of the SmartIntego locks (done with the SmartIntego software from SimonsVoss). |
||
First, it is necessary to define whether the card ID is Mifare UID or data stored in the card memory itself. This setting is done in the Organization Owner view and must match the programming of the SmartIntego locks (done with the SmartIntego software from SimonsVoss). |
|||
| ⚫ | |||
First, it is necessary to define whether the card ID is Mifare UID or data stored in the card memory itself. If the card ID comes from the card memory, it is also necessary to specify how long (how many bytes) the card ID is. This setting has to match both the physical cards and the programming of the SmartIntego locks. For example, if DESFire application is used, and the card ID stored on the cards is four bytes, this settings should be '4'. |
|||
| ⚫ | |||
Revision as of 17:54, 4 November 2021
There are a few settings that are necessary in order for locks from SimonsVoss SmartIntego to work correctly. A few overall settings are found in the Organization Owner view and must match the programming of the SmartIntego locks (done with the SmartIntego software from SimonsVoss).
First, it is necessary to define whether the card ID is Mifare UID or data stored in the card memory itself. If the card ID comes from the card memory, it is also necessary to specify how long (how many bytes) the card ID is. This setting has to match both the physical cards and the programming of the SmartIntego locks. For example, if DESFire application is used, and the card ID stored on the cards is four bytes, this settings should be '4'.
If the privilege has been defined with this type, the credential ID will be stored in the lock's own whitelist. In contrast, for privileges of type Regular, it is the controller that makes the access control decision.