Operation Manual - Aurum Controller
The Aurum has been discontinued and is no longer sold for new projects. This documentation remains available to support existing installations. For new projects or replacements, contact the Iongrade sales team.
The Aurum controller has an internal HTTP server and all of its configuration is done through a browser. This manual describes each screen of the web configuration interface.
To access the configuration, you must put the controller into Configuration mode, connect to the WiFi network it generates, and point the browser to 192.168.4.1. The step-by-step procedure is in the Installation Manual.
Login
When you connect the browser to the controller, you are asked for a user name and password. The default values are:
- User:
admin - Password:
aurumpwd
Main Menu
The initial configuration screen presents the following options:
- Comunic (Communication) — configuration of the network communication parameters.
- Hardware — configuration of the devices physically connected to the controller.
- Acesso (Access) — configuration of the controller's control mode.
- Arquivos (Files) — backup and restore functions.
- Upgrade — controller firmware update.
- Info — general information about the controller.
- Reboot — restarts the device.
Communication
The Comunic menu gives access to the following screens:
- Conexão (Connection) — defines the media type (WiFi or Ethernet) used to connect the controller to the network when it is in operation.
- WiFi — WiFi network parameters, if the controller is going to use a wireless connection.
- Ethernet — wired network parameters (RJ45 connector).
- MQTT — parameters to access the MQTT communication server (Broker).
- UDP — parameters of the UDP communication channel.
Connection
On this screen you define the media type the controller will use to connect to the communication network when it is in operation mode. The options are:
- WiFi (Wireless)
- Ethernet (RJ45)
Make the necessary changes and click Salvar (Save) to confirm.
WiFi
Use this screen to enter the data and access parameters of the WiFi network that will be used in operation mode.
Make the necessary changes and click Salvar to confirm.
Ethernet
Use this screen to enter the data and access parameters of the Ethernet (RJ45) network that will be used in operation mode.
Make the necessary changes and click Salvar to confirm.
MQTT
On this screen you enter the communication parameters to establish the connection with the MQTT communication server. Information about the physical installation of the controller is also provided.
| Field | Description |
|---|---|
| Conexão | Defines whether the board must connect to the Accelero Cloud MQTT broker, to a custom MQTT broker, or to no MQTT broker at all. When the Automático (Automatic) option is selected, only the Facility ID field needs to be filled in. |
| Facility ID | Unique identification of the installation. All controllers of the same installation must have the same Facility ID. E.g.: empresax, edificioz. |
| TLS | Check this option if the controller must establish communication with the MQTT broker in secure mode (Transport Layer Security). The server must allow this communication mode. |
| Broker | URL address of the communication server used in the installation. |
| Port | Number of the communication port with the MQTT broker. |
| User name | User name to access the MQTT broker. |
| Password | Password to access the MQTT broker. |
| Device ID | Unique and exclusive identification of each controller in the installation. E.g.: catraca1, porta2. |
Make the necessary changes and click Salvar to confirm.
When the connection is made through Accelero Cloud, only the Facility ID parameter must be configured, exactly as defined in the control system that will manage the controllers.
UDP
On this screen you enter the parameters to establish a connection over the UDP protocol. Through this connection, other devices can send information to the controller — such as cards/tags read on other devices.
- Porta (Port) — communication port to be used. If it is set to
0(zero), the service is turned off.
When the UDP connection is used, it is recommended that the controller's IP address be static, since this address must be configured on the device that will send data over this connection.
Hardware
The Hardware menu gives access to the following screens:
- Horário (Time) — adjustment of the controller time and NTP server parameters.
- Leitores (Readers) — types of readers that will be connected to the controller.
- UARTS — types of devices connected to the serial ports.
- Relés (Relays) — operation mode and timing of the output relays.
- Display — display operation mode.
- Timers — general timings (password entry, biometrics, etc.).
- TOTP — TOTP (Time-based One-Time Password) parameters.
- Testes (Tests) — hardware operation tests.
Time
On this screen you can set the controller to keep its internal clock synchronized with an external date/time server (NTP Server):
- Usar servidor NTP (Use NTP server) — when checked, the controller uses an NTP server to adjust its local clock automatically.
- NTP Hostname — URL of the NTP server.
- Fuso horário (Time zone) — time zone of the location where the controller is installed.
- Horário de verão (Daylight saving time) — automatically adjusts for daylight saving time.
- Horário do dispositivo (Device time) — current date and time of the controller.
- Enviar hora local (Send local time) — sends the date/time of your computer to the controller.
Make the necessary changes and click Salvar to confirm.
Readers
The Aurum controller has three interfaces for connecting card readers of the ABATrack, Wiegand, and other formats. On this screen, enter the type of reader that will be connected to each interface.
Make the necessary changes and click Salvar to confirm.
UARTs
The Aurum controller has communication ports (UARTs) for connecting various types of devices, such as QR Code reading modules, Bluetooth modules, biometric scanners, printers, etc.
- UART1 is associated with channel 1.
- UART2 and UART3 are associated with channel 2 of the controller.
On this screen, enter which type of device will be connected to each UART and click Salvar to confirm.
Relays
The Aurum controller has four relays for driving external devices (LOCK1, LOCK2, ALRM1, and ALRM2):
- The LOCK1 and ALRM1 relays are associated with channel 1; LOCK2 and ALRM2 with channel 2.
- The LOCK relay is triggered whenever the controller grants access on the channel.
- The ALRM relays are triggered on denied access. In some control modes, the relays may take on other functions.
On this screen, configure the normal state (default) of each relay — off (OFF) or on (ON) — and the time (in seconds) that each relay stays on when triggered.
For controlling doors with electromagnetic locks, the ON option is normally used for the relay's normal state.
Display
The Aurum controller display can operate showing locally generated messages (default) or showing the messages sent by the server.
This screen lets you choose the operation mode of each of the display's two lines and define a standard message for the online/offline states when the chosen mode is the one with server messages.
Make the necessary changes and click Salvar to confirm.
Timers
On this screen you set the time limits (in seconds) for some user actions:
- Timeout password — maximum time to wait for the user's password entry.
- Timeout biometria (Biometrics timeout) — maximum time to wait for biometric identification.
- Timeout Id escort (Escort Id timeout) — maximum time to wait for the identification of an escort.
- Timeout captura dados (Data capture timeout) — maximum time to wait for a card entry in capture mode (card creation).
- Timeout resposta servidor (Server response timeout) — maximum time to wait for the server response to a query.
- Timeout porta aberta (Door open timeout) — time limit to generate a door-open alarm.
- Timeout user porta retardo (Delayed door user timeout) — maximum time to wait for the user's re-identification in Delayed Door mode.
- Tempo default porta retardo (Delayed door default time) — timing adopted in Delayed Door mode when operating in contingency (offline).
Make the necessary changes and click Salvar to confirm.
TOTP
On this screen you set the parameters of the TOTP (Time-based One-Time Password) control:
- Habilitado (Enabled) — enables the TOTP feature.
- Key — secret key to be used.
- Duração (Duration) — time window, in seconds, for TOTP validation.
- Tolerância (Tolerance) — number of tolerance time windows. That number of windows before and after the current time will be considered.
Make the necessary changes and click Salvar to confirm.
Tests
On this screen you can check the operation of the devices connected to the controller:
- When you present a card to one of the readers connected to the controller, the data read is shown on the respective channel.
- The state of the signal inputs (REX and PAS/DOOR) is also updated in real time on the screen.
Access
The Acesso menu gives access to the following screens:
- Bloqueio (Blocking) — defines the type of device to be controlled (door, turnstile, vehicle barrier, etc.).
- Canais (Channels) — control characteristics of each of the controller's three channels.
- Cartões (Cards) — functions for adjusting the local card list.
- Mensagens (Messages) — configuration of the messages shown on the display.
- Logs — reading of the events recorded by the controller (used in stand-alone operation).
Blocking Device
The Aurum controller is ready to control several types of devices. Use this screen to inform which device it must control.
The available control modes are:
- Turnstile with unidirectional readers — complete turnstile: the first reader at the entry, the second at the exit, and the third installed in the visitor card collection box.
- Turnstile with bidirectional reader — one bidirectional card reader and a second reader in the collection box. The collection box reader must be connected in the position of reader 3.
- One door — control of one door with the first reader at the entry and the second at the exit.
- Two doors with unidirectional readers — control of two doors, with the first reader at the entry of the first door and the second at the entry of the second door. The exits are triggered by buttons on the REX1 and REX2 inputs.
- Two interlocked doors — control of two doors in interlocking mode (mantrap). The first reader at the entry of the first door and the second at the entry of the second door; the exits are triggered by buttons on the REX1 and REX2 inputs. The state of the doors is monitored by the DOOR1 and DOOR2 inputs. Opening one door is only allowed if the other is closed.
- Combo interlocked doors — control of one door in interlocking mode (mantrap) with an external signal, using either a reader or release buttons (REX1 and REX2), one on each side of the door. The door state is monitored by the DOOR1 input and the release command is given by the LOCK1 relay. The DOOR2 input receives an external signal that enables/disables operation, and the NO contact of the LOCK2 relay signals other Aurum units that must block their operation. This way, two or more Aurum units can perform interlocked control — just connect the DOOR2 inputs and the LOCK2 relays of all Aurum units in parallel with a pair of wires.
- Two vehicle barriers with automatic passage — control of two vehicle barriers. Access is considered completed without the need for passage confirmation (PASS1 and PASS2 inputs).
- Blocking with delay — control of a door with opening timing (delay configurable in the system). Upon authorization, the controller starts a timer and, at the end, requests the user's identification again — only on the second authorization is the blocking device released. During the timing, the LOCK2 relay stays on (useful for a signaling device). If an identifier with the duress flag is presented, the ALARM2 relay is triggered during the process.
- Logger record — passage recording mode only. The controller records the events but does not perform any type of control.
In Combo interlocked doors mode, note that the pair of wires must respect the polarity of the DOOR2 inputs — one of the wires is connected to GND.
Make the necessary changes and click Salvar to confirm.
Channels
The Aurum controller has three control channels. Specific verification rules can be defined for each channel. Configure the parameters below and click Salvar.
- Exigir senha (Require password) — enables offline password control on the channel. For it to work: the channel must be configured to verify the password, there must be a device with a keypad for password entry, and the user must have a password.
- Exigir escort (Require escort) — in offline mode, grants access to a user who requires an escort only when an authorized user releases their passage. For it to work: the channel must be flagged to verify the escort, the user to be escorted must have the escort required flag, and the releasing user must be flagged as an authorized escort (escort).
- Exigir biometria (Require biometrics) — requires the user to identify themselves with a biometric sensor. For it to work: the channel must be flagged to verify biometrics, there must be a biometric capture device associated with the channel, and the user must have registered biometric data.
- Ignorar VSV (Ignore VSV) — forwards access requests immediately to the server, without checking authorization in the local list.
- Tratar User Id (Handle User Id) — makes the controller accept the user's identification code as the identifier, instead of a card code (useful, for example, with a biometric scanner that sends the user code).
- Não usar relé ALARM (Do not use ALARM relay) — in case of denied access, does not trigger the channel's alarm relay.
- Tempo passagem (Passage time) — time period for the user to pass through the blocking device. If it is shorter than the time defined for the channel's LOCK relay, the Aurum uses the relay time.
- Anti repetição (Anti-repetition) — time interval for successive badge readings to be disregarded on the channel.
Cards
The Cartões menu gives access to the following screens:
- Modo (Mode) — adjustment of the control mode of the user list stored in the controller's memory.
- Apagar (Delete) — deletes the data of the local card list.
- Enviar (Send) — upload of a card list when the controller is going to operate in fully stand-alone mode (without communication).
Mode
The Aurum controller keeps a list of users in its internal memory (local list), updated by the control software. Access control can use the local list and/or query the server. On this screen you define how the controller handles that list.
Card list:
- Lista local + servidor (Local list + server) — with communication OK, the server is queried (except for cards flagged not to be queried). In case of a communication failure, the controller checks whether the user exists in its list to make the decision.
- Sempre consulta servidor (Always query server) — all requests are forwarded to the server. In case of a communication failure, the controller handles only duress cards locally.
- Nunca consulta servidor (Never query server) — uses only the local list for authorizations.
Duress — defines the controller's action when a card flagged as a "duress card" is presented in contingency mode (when online, the action is determined by the server):
- Abertura automática (Automatic opening) — grants access regardless of any other rule. Generates a "duress" event sent to the server when the connection is reestablished.
- Aplicar políticas de acesso (Apply access policies) — applies the access policies normally (which may block access), but generates a "duress" event sent to the server when the connection is reestablished.
Make the necessary changes and click Salvar to confirm.
Delete
The screen shows the total capacity of the local card list and the number of cards in use. Use the Apagar button to clear the local list.
Clearing the list may take a few seconds. Wait about 30 seconds and refresh the screen.
Send
The Aurum controller can operate in stand-alone mode (without communication and without control software). To do this, you must inform it about the users with access permission, their time ranges, etc. This function allows you to send a file with this data to the controller.
The file format is simple but standardized, and can be created in a text editor. Use the Escolher arquivo (Choose file) button to locate it and the Upload button to start the transmission.
Contact technical support about the card file format.
Messages
All the messages the controller shows on the display can be freely configured on this screen — for example: Access granted, Access denied, among others.
Make the necessary changes and click Salvar to confirm.
Logs
When the controller operates in stand-alone mode, the event records continue to be stored in memory. This function lets you check the state of the records, generate a report (download), and clear the data:
- Status logs — storage capacity, current number of records, and date/time of the oldest record.
- Relatório (Report) — defines the start and end dates to create a file with the records for the period. The Download button creates and sends the file (standardized format).
- Excluir logs (Delete logs) — clears the event records. Enter the cutoff date and click Excluir.
Files
The Arquivos menu gives access to the following screens:
- Backup — creates and downloads a file with all the controller's configuration data.
- Restore — sends a backup file to restore the settings.
- Upload — sends a specific file to the controller.
Backup
Use this screen to download a file with all the controller's configuration data.
Click Iniciar (Start) to download the file. A window opens asking where to save it. This file can be used in the Restore function whenever you want to restore the configuration. Click Voltar (Back) to return to the previous menu.
Restore
Use this screen to send a file with the controller's configuration data. The file must be in the proper format, as created by the Backup function.
Click Escolher arquivo to select it and Enviar arquivo (Send file) to start the transfer. Click Voltar to return to the previous menu.
Upload
Use this screen to send a specific file to the controller. The files must be in the proper format. The screen shows the space currently available in the controller's memory.
Click Escolher arquivo to select it and Enviar arquivo to start the transfer. Click Voltar to return to the previous menu.
Upgrade
This function allows you to send a new firmware version to the device when necessary. There are two types of update:
- FIRMWARE — update of the executable code.
- FSYS — update of the file system.
In some situations both updates are required. Choose the type by clicking the specific button, or click Voltar to return to the initial menu.
FIRMWARE Upgrade
On this screen you select a file with a new firmware version to update the device.
Click Escolher arquivo to select the file and then Enviar novo firmware (Send new firmware) to start the transfer.
At the end of the update, the device restarts automatically. Since it returns to normal operation mode, the Access Point is deactivated. To go back to configuration mode, repeat the procedure described in Enabling Configuration mode.
FSYS Upgrade
On this screen you select a file with a new version of the file system (FSYS) to update the device.
Click Escolher arquivo to select the file and then Enviar novo fsys (Send new fsys) to start the transfer.
At the end of the update, the device restarts automatically. Since it returns to normal operation mode, the Access Point is deactivated. To go back to configuration mode, repeat the procedure described in Enabling Configuration mode.
Info
This page shows technical information about the controller:
- Dispositivo (Device) — device type.
- Série (Series) — device series.
- Modelo (Model) — device model.
- Número de série (Serial number) — manufacturing serial number.
- Factory ID — factory identification.
- Firmware — firmware version.
Reboot
On this page you can restart the Aurum remotely.
Type REBOOT in uppercase in the confirmation field and click the Reiniciar (Restart) button.