Electronic Locks
The Access Commander system provides access control via the 2N Fortis electronic locks, which are unlocked by the MIFARE ® DESFire® RFID cards. Each electronic lock is assigned an encryption key during configuration. The lock keys are then stored on the RFID cards of the authorized users. If the keys match on the card and in the lock, the locking mechanism is unlocked.
One RFID access card can be used for access to up to 90 doors with the 2N Fortis locks, depending on the number of the time profiles applied. If the card memory capacity is exceeded, data writing to the card will fail. The write failure event is recorded in the system Access Log. If Lock Groups are used, more doors can be written to a single card than the case is with individual assignment.
Fortis Commander
Fortis Commander is a standalone application that interconnects the Fortis electronic locks with the Access Commander system. The application sets the locks according to the project file created in Access Commander, which contains the lock configuration. The file is encrypted and can only be used for one specific installation.
Installation
Fortis Commander is designed to be installed on a Windows computer with Bluetooth Low Energy (BLE) support.
The app can be found at 2N Download Centre.
Download the installation package from the link provided.
Run the installer and complete the installation by following the on-screen instructions.
Project File
The project file is created in Access Commander and contains the complete project configuration. The file is encrypted and password protected.
Lock Settings in Access Commander
Before uploading keys to individual locks, you must pair Access Commander with Fortis Commander.
Log in to Access Commander.
Go to .
Click in .
Create the master encryption key.
Caution
The master encryption key cannot be displayed or changed later.
Note
According to the master encryption key (MEK), 2N Access Commander generates a set of encryption keys. Thus, the key should be unique and sufficiently secure. As the key set is based on the master encryption key, projects with one and the same master encryption keys generate the same sets of keys. If a project is lost, you can create a new project with the same master encryption key and continue encryption.
Having generated the keys and set the password for the project file, you can download the project file, which represents an image of the electronic lock configuration in the Access Commander system.
On the tab, click , to download the Fortis Commander electronic lock configuring application.
Caution
Project information is sensitive data. Protect it from abuse.
Install and open the Fortis Commander application.
Click to open the downloaded project file in the File Explorer.
In the open dialog box, enter the project file password.
After opening the project file, select and tap the service card on the lock.
Click Assign to assign the lock to the project.
Disconnect the device and click .
When the configuration is complete, open Access Commander. Go to the and click the button again. Upload the project file.
Note
When moving the lock between installations or when making a claim, you must perform Factory Reset. This operation resets the lock to factory settings and removes all previous configuration.
Configuration Update Instructions
Make changes in Access Commander.
Download a new project file.
Upload the file to Fortis Commander and make the required changes to the locks.
If you make other changes in Access Commander, always download a new project file.
Caution
Make sure to download a new project file for every configuration change in Access Commander – never use an older file already uploaded to Fortis Commander.
Permanent Locking/Unlocking
The app allows you to permanently lock and unlock the lock. The function is used for service interventions or emergency control without the use of a card.
Collection of events from electronic locks using RFID cards / chips
Open .
Select the event type:
Collect access and system events - All access and system events are recorded on the card/chip and written to the System Log and Access Log.
Collect only system events - only system events are logged, access events are not stored on cards.
Do not collect events on tabs - no events are written to the tab; they can only be accessed through Fortis Commanderu.
Tip
Selecting the appropriate event set can reduce system load and storage utilization. However, detailed logging is important for diagnostics and safety audits.
The card stores a maximum of 16 first events. Events can be read in two ways:
In Access Commander, click on the
icon in the search box in the header and load the tab.Using a device with 2N OS, events are read from the card and sent to Access Commanderu.
Open and click on .
Open the file in Fortis Commander.
In the Fortis Commander app, connect to the electronic lock.
Upload the updated file back to Access Commander.
Once uploaded, the events are displayed in and .
Service Operations
The following operations are available for Fortis Cylinder:
Disassembly – disassembly of locks for service purposes.
Battery Replacement – replacing the battery in the lock.
Caution
The service operations are not relevant for other types of locks.
Note
Press the button for permanent locking to switch the lock from the service mode to the normal mode.
Card Update
User access cards need to be updated on a regular basis. The user updates the card by tapping it on the 2N IP device to which the user has valid access rights. The card must be held against the reader until the door opening switch is activated. The door opening switch is not activated until the lock accesses have been updated.
You can change the default ten-day validity of the cards in .
Caution
If you change the lock access rights in Access Commander, the changes will not be reflected on the user access card until the card has been updated on a 2N device card reader! For security reasons, we recommend that a shorter validity period is set for the cards to ensure they are updated regularly.
The IP readers in the devices that allow for card updates and their settings are described in the Subs. IP Device Reader Settings.
Compatible Cards
Note
For the purposes of this documentation, the term card refers to any compatible identifier using the MIFARE DESFire technology.
Cards with random ID cannot be used for opening the 2N Fortis electronic locks.
Cards with PICard technology cannot be used for opening the 2N Fortis electronic locks.
Time Profiles on Electronic Locks
Electronic locks support time profiles with the following limitations:
Holidays do not apply.
You can set up to 4 different time intervals per day.
4 daily interval schedules can be defined within one time profile.
Tip
This means that you can have different settings for Monday, Tuesday, Wednesday and Thursday, for example, but you must use one of the existing settings for Friday, Saturday, and Sunday.
Caution
If the time profile violates the specified restrictions, the access rule will be ignored and the user will not be granted access.
Lock Settings in Access Commander
Before uploading keys to individual locks, you must pair Access Commander with Fortis Commander.
Log in to Access Commander.
Go to .
Click in .
Create the master encryption key.
Caution
The master encryption key cannot be displayed or changed later.
Note
According to the master encryption key (MEK), 2N Access Commander generates a set of encryption keys. Thus, the key should be unique and sufficiently secure. As the key set is based on the master encryption key, projects with one and the same master encryption keys generate the same sets of keys. If a project is lost, you can create a new project with the same master encryption key and continue encryption.
Having generated the keys and set the password for the project file, you can download the project file, which represents an image of the electronic lock configuration in the Access Commander system.
On the tab, click , to download the Fortis Commander electronic lock configuring application.
Caution
Project information is sensitive data. Protect it from abuse.
Install and open the Fortis Commander application.
Click to open the downloaded project file in the File Explorer.
In the open dialog box, enter the project file password.
After opening the project file, select and tap the service card on the lock.
Click Assign to assign the lock to the project.
Disconnect the device and click .
When the configuration is complete, open Access Commander. Go to the and click the button again. Upload the project file.
Note
When moving the lock between installations or when making a claim, you must perform Factory Reset. This operation resets the lock to factory settings and removes all previous configuration.
Configuration Update Instructions
Make changes in Access Commander.
Download a new project file.
Upload the file to Fortis Commander and make the required changes to the locks.
If you make other changes in Access Commander, always download a new project file.
Caution
Make sure to download a new project file for every configuration change in Access Commander – never use an older file already uploaded to Fortis Commander.
Permanent Locking/Unlocking
The app allows you to permanently lock and unlock the lock. The function is used for service interventions or emergency control without the use of a card.