Indium Access Controller
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 access controller is a rugged device developed specifically for high-performance access control solutions that require flexibility to integrate with a wide range of devices.
Overview

Designed to operate with IoT communication protocols, the Indium allows easy integration with the most diverse access control systems.
The hardware is designed to operate safely and reliably under the most varied environmental conditions. It includes electronic circuits specifically designed to protect the components against electrical surges. The signal inputs are built with optocouplers that fully isolate the sensors from the controller's internal circuits.
It can connect to the communication network using wireless technology (WiFi) or through a 10/100-Base-T Ethernet UTP cable. It has a high-precision internal clock and can be configured to access an external NTP server.
The controller has an internal HTTP server and is configured through a browser. It provides interfaces for two card readers, two serial ports, and one display connection. It accepts ABATrack/Wiegand readers, QR Code scanners, a Bluetooth module, a printer, and an audio module. It is powered by 12 VDC.
It is prepared to control several types of blocking devices such as turnstiles, doors, barriers, and mantraps — the type of blocking device to be controlled is configurable.
The controller also keeps a local contingency list of up to 100,000 users, allowing access decisions to be made even when communication with the server fails.
Key Features
- IoT connectivity: WiFi (Wireless) or Ethernet 10/100-Base-T (RJ45)
- Up to two Wiegand/ABATrack readers and up to two serial readers
- Four command relays for physical control of several devices (LOCK1, LOCK2, ALRM1, ALRM2)
- Local contingency list: up to 100,000 users stored in the controller memory
- Simple configuration through a local web server enabled for this specific purpose
- QR Code ticket printer connection
- Integration with several market software packages through the open OpenION protocol (open IoT protocol) or through customizations for specific purposes
- Power supply: 12 VDC
Technical Specifications
| Specification | Value |
|---|---|
| Power supply | 12 VDC, 350 mA (typical, with peripherals) — 120 mA without readers/modules |
| Reader interfaces | 2x inputs for standard ABATrack and Wiegand readers (Wiegand 26, Wiegand 32, Wiegand 34, among others) |
| Serial interfaces | 2x inputs for readers with serial communication (biometric sensors, OCR devices, Bluetooth modules, among others) |
| Virtual inputs | 2x virtual inputs for connection with TCP/IP devices |
| Output relays | 4x relays capable of energizing loads of 1A/120VAC or 2A/30VDC |
| Virtual outputs | Several virtual outputs (event generation) via TCP/IP for integrations over Ethernet networks |
| Communication | WiFi and Ethernet RJ45 10/100-Base-T |
| Firmware | Remote update over a TCP/IP network in push mode (firmware sent to the controller) or pull mode (controller fetches the firmware automatically) |
| Connectivity | Communicates natively through the open OpenION protocol (open IoT protocol); can communicate through custom protocols |
| Clock/calendar | Internal clock that keeps date/time even during power failures |
Channel and Port Concept
The Indium controller operates with the concept of channels and ports.
Channels
The controller has two control channels. A user can be enabled for access on each channel separately.
Channel 1 is associated with the REX1 and PAS/DOOR1 signal inputs, and with the LOCK1 and ALRM1 relays. Channel 2 is associated with the REX2 and PAS/DOOR2 signal inputs, and with the LOCK2 and ALRM2 relays. The two card readers are directly associated with channels 1 and 2.
| Channel | Signal Inputs | Relays |
|---|---|---|
| Channel 1 | REX1, PAS/DOOR1 | LOCK1, ALRM1 |
| Channel 2 | REX2, PAS/DOOR2 | LOCK2, ALRM2 |
Ports
The Port concept controls the entry of user identifiers. Each port represents a possible identification source on each channel. Port 1 is linked to the two ABATrack/Wiegand card readers; the serial ports (UARTs) are linked to Port 2.
| Port | Channel 1 | Channel 2 |
|---|---|---|
| 1 | Reader 1 | Reader 2 |
| 2 | UART 1 | UART 2 |
| 3 | Web 1 | Web 2 |
| 4 | MQTT 1 | MQTT 2 |
| 5 | QR Code 1 | QR Code 2 |
This way, the control software can enable/disable a user on ports/channels according to the control needs.
Examples:
- A user can be enabled to pass through a channel exclusively using QR Code identification.
- A user can be enabled to pass through a channel using a proximity card or a Bluetooth reader connected to the channel's UART.
Applications
The Indium controller is fully configurable and allows the control of the following devices:
- Bidirectional turnstile
- Event turnstile
- Vehicle barriers
- Doors
- Mantraps
- Interlocked doors (two or multiple)
- Doors with opening delay (vaults)
- Data Logger
Next Steps
- Installation Manual — electrical connections and physical installation