Skip to main content

Operation Manual - Indium Controller

Discontinued product

The Indium 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 Indium 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.

Before you start

To access the configuration, you must put the controller in Configuration mode, connect to the WiFi network it generates, and point the browser to 192.168.4.1. The step-by-step instructions are in the Installation Manual.

Login​

login screen

When you connect the browser to the controller, a user name and password are requested. The default values are:

  • User: admin
  • Password: indiumpwd
main menu screen

The configuration home screen presents the following options:

  • Comunic (Communication) — network communication parameter configuration functions.
  • Hardware — configuration functions for the devices physically connected to the controller.
  • Acesso (Access) — configuration functions for the controller's control mode.
  • Arquivos (Files) — file functions (backup/restore).
  • Upgrade — access to the controller firmware update screen.
  • Info — access to general information about the controller.
  • Reboot — restarts the device.

Communication​

communication screen

The Comunic (Communication) 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 while in operation.
  • WiFi — WiFi network parameters, if the controller is going to use a wireless connection.
  • Ethernet — wired network parameters (RJ45 connector).
  • UDP — UDP communication channel parameters.
MQTT / Accelero Cloud communication

The controller's integration with the MQTT broker (including the connection to Accelero Cloud) has separate documentation and is not detailed in this manual.

Connection​

connection screen

On this screen you define the media type the controller will use to connect to the communication network while in operation mode. The options are:

  • WiFi (Wireless)
  • Ethernet (RJ45)

Make the necessary changes and click Salvar (Save) to confirm.

WiFi​

wifi screen

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 (Save) to confirm.

Ethernet​

ethernet screen

Use this screen to enter the data and access parameters of the Ethernet network (RJ45) that will be used in operation mode.

Make the necessary changes and click Salvar (Save) to confirm.

UDP​

udp screen

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.
Static IP address

When using the UDP connection, 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​

hardware screen

The Hardware menu gives access to the following screens:

  • Horário (Time) — controller time adjustment 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 timeouts (password entry, biometrics, etc.).
  • TOTP — TOTP (Time-based One-Time Password) parameters.
  • Testes (Tests) — hardware operation tests.

Time​

ntp time screen

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) — the controller's current date and time.
  • Enviar hora local (Send local time) — sends your computer's date/time to the controller.

Make the necessary changes and click Salvar (Save) to confirm.

Readers​

readers screen

The Indium controller has two 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 (Save) to confirm.

UARTs​

uarts screen

The Indium controller has two 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 is associated with channel 2 of the controller.

On this screen, enter the type of device that will be connected to each UART and click Salvar (Save) to confirm.

Relays​

relays screen

The Indium controller has four relays for triggering 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 an access denied condition. 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) each relay stays on when triggered.

Electromagnetic locks

For controlling doors with electromagnetic locks, the ON option is normally used for the relay's normal state.

Display​

display screen

The Indium controller's display can operate by showing locally generated messages (default) or by 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 server messages.

Make the necessary changes and click Salvar (Save) to confirm.

Timers​

timers screen

On this screen you set the time limits (in seconds) for some user actions:

  • Timeout password (Password timeout) — 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 an escort's identification.
  • 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's 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 (Save) to confirm.

TOTP​

totp screen

On this screen you set the TOTP (Time-based One-Time Password) control parameters:

  • 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 many windows before and after the current time are considered.

Make the necessary changes and click Salvar (Save) to confirm.

Tests​

tests screen

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 PASS/DOOR) is also updated on the screen in real time.

Access​

access screen

The Acesso (Access) menu gives access to the following screens:

  • Bloqueio (Blocking device) — defines the type of device to be controlled (door, turnstile, barrier, etc.).
  • Canais (Channels) — control characteristics of each of the controller's two 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​

blocking device screen

The Indium controller is prepared to control several types of devices. Use this screen to specify which device it must control.

The available control modes are:

  • Turnstile with unidirectional readers — complete turnstile: the first reader at the entrance and the second reader at the exit.
  • Turnstile with bidirectional reader — one bidirectional card reader and a second reader installed in the visitor card collection box.
  • One door — control of one door with the first reader at the entrance and the second at the exit.
  • Two doors with unidirectional readers — control of two doors, with the first reader at the entrance of the first door and the second at the entrance of the second door. The exits are triggered by buttons on the REX1 and REX2 inputs.
  • Two barriers with automatic passage — control of two vehicle barriers. Access is considered completed without the need for passage confirmation (PASS1 and PASS2 inputs).

Make the necessary changes and click Salvar (Save) to confirm.

Channels​

channels screen

The Indium controller has two control channels. Specific verification rules can be defined for each channel. Configure the parameters below and click Salvar (Save).

  • Exigir senha (Require password) — enables offline password control on the channel. For it to work: the channel must be configured to verify a 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 marked to verify escort, the user to be escorted must have the escort required flag, and the person granting access must be marked as an authorized escort (escort).
  • Exigir biometria (Require biometrics) — requires the user to identify themselves through a biometric sensor. For it to work: the channel must be marked to verify biometrics, there must be a biometric capture device associated with the channel, and the user must have registered biometric data.
  • Ignora VSV (Ignore VSV) — forwards access requests to the server immediately, 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).
  • Tempo passagem (Passage time) — the period of time for the user to pass through the blocking device. If it is shorter than the time set for the channel's LOCK relay, the Indium uses the relay time.
  • Anti repetição (Anti-passback repeat) — time interval during which successive badge reads are ignored on the channel.

Cards​

cards screen

The Cartões (Cards) menu gives access to the following screens:

  • Modo (Mode) — adjustment of the control mode for the user list stored in the controller memory.
  • Apagar (Erase) — erases the data of the local card list.
  • Enviar (Upload) — upload of a card list when the controller is going to operate in fully stand-alone mode (without communication).

Mode​

cards mode screen

The Indium controller keeps a user list 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 this list.

Card list:

  • Local list + server — when communication is OK, the server is queried (except for cards marked not to be queried). If communication fails, the controller checks whether the user exists in its list to make the decision.
  • Always query the server — all requests are forwarded to the server. If communication fails, the controller handles only duress cards locally.
  • Never query the server — uses only the local list for authorizations.

Duress — defines the controller's action when a card marked as a "duress card" is presented in contingency mode (when online, the action is determined by the server):

  • Automatic opening — authorizes access regardless of any other rule. Generates a "duress" event sent to the server once the connection is reestablished.
  • Apply access policies — normally applies the access policies (which may block access), but generates a "duress" event sent to the server once the connection is reestablished.

Make the necessary changes and click Salvar (Save) to confirm.

Erase​

erase cards screen

The screen shows the total capacity of the local card list and the number of cards in use. Use the Apagar (Erase) button to clear the local list.

tip

Clearing the list may take a few seconds. Wait about 30 seconds and refresh the screen.

Upload​

upload cards screen

The Indium 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 it 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.

File format

Contact technical support about the card file format.

Messages​

messages screen

All the messages the controller shows on the display can be freely configured on this screen — for example: ACESSO AUTORIZADO, ACESSO NEGADO, among others.

Make the necessary changes and click Salvar (Save) to confirm.

Logs​

logs screen

When the controller operates in stand-alone mode, event records continue to be stored in memory. This function allows you to 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) — sets 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 (Delete).

Files​

files screen

The Arquivos (Files) menu gives access to the following screens:

  • Backup — creates and downloads a file with all of the controller's configuration data.
  • Restore — sends a backup file to restore the settings.
  • Upload — sends a specific file to the controller.

Backup​

backup screen

Use this screen to download a file with all of 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 when you want to restore the configuration. Click Voltar (Back) to return to the previous menu.

Restore​

restore screen

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 (Choose file) to select it and Enviar arquivo (Send file) to start the transfer. Click Voltar (Back) to return to the previous menu.

Upload​

upload screen

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 (Choose file) to select it and Enviar arquivo (Send file) to start the transfer. Click Voltar (Back) to return to the previous menu.

Upgrade​

upgrade screen

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 necessary. Choose the type by clicking the specific button, or click Voltar (Back) to return to the home menu.

FIRMWARE Upgrade​

firmware upgrade screen

On this screen you select a file with a new firmware version to update the device.

Click Escolher arquivo (Choose file) to select the file and then Enviar novo firmware (Send new firmware) to start the upload.

Automatic restart

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 Activating Configuration mode.

FSYS Upgrade​

fsys upgrade screen

On this screen you select a file with a new file system (FSYS) version to update the device.

Click Escolher arquivo (Choose file) to select the file and then Enviar novo fsys (Send new fsys) to start the upload.

Automatic restart

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 Activating Configuration mode.

Info​

info screen

This page presents 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​

reboot screen

On this page you can restart the Indium remotely.

Type REBOOT in uppercase in the confirmation field and click the Reiniciar (Restart) button.