ADLINK GW-01 Industrial IoT Gateway Configuration and Debugging Guide



ADLINK GW-01 Industrial IoT Gateway Protocol Configuration and Deployment Guide

ADLINK GW-01 is a compact IIoT gateway designed specifically for industrial field data acquisition and protocol conversion, equipped with TI Sitara AM3352 ARM Cortex-A8 1GHz processor, built-in 512MB SDRAM and 4GB eMMC storage, supporting 2 10/100M Ethernet and 2 serial ports (RS-232 and RS-422/485), and equipped with 19.2V to 28.8V isolated power supply and isolated communication port. Its core value lies in the pre installed iM Connect protocol conversion software, which can natively support over 300 PLC protocols (covering mainstream brands such as OMRON, Mitsubishi, Siemens, etc.) when running, and seamlessly integrate with mainstream cloud platforms through OPC UA, MQTT, and RESTful APIs. Based on product technical specifications, this article systematically outlines hardware installation points, protocol configuration methods, cloud docking processes, serial port and network debugging techniques, as well as common on-site troubleshooting strategies, to help automation engineers quickly complete gateway deployment and system integration.

Product positioning and applicable scenarios

GW-01 is positioned to address the pain points of heterogeneous device interconnection in industrial sites. In traditional production lines, different brands of PLCs use their own proprietary protocols, resulting in the inability to unify data aggregation. As a protocol conversion middleware, GW-01 can connect multiple PLCs simultaneously (via serial port or Ethernet), standardize data into MQTT/OPC UA format, and upload it to the cloud or SCADA system. Typical applications include:

Old equipment data collection and remote monitoring (replacing discontinued data collection modules)

Unified data interface for multi brand PLC production lines

Data source of edge computing and predictive maintenance system

Instrument data integration of energy management system

Its metal casing, DIN rail installation, PCB three proof paint protection, and wide temperature operation (-20 ° C to 70 ° C) ensure stable operation in harsh industrial environments.

Hardware specifications and installation preparation

2.1 Core Parameters

Project specifications

CPU TI Sitara AM3352 ARM Cortex-A8 1GHz

512MB SDRAM (optional 1GB)

Storage 4GB eMMC (optional 8GB)

Network 2 × 10/100Mbps Ethernet (RJ45)

Serial port 1 x RS-232, 1 x RS-422/485 (terminal block)

USB 1 x USB Host (for recovery or peripherals)

Power 3-pin terminal, 19.2~28.8V DC isolation

Size 120 × 85.45 × 31.25 mm, weight 0.45kg

Install 25mm DIN rail

Working temperature -20 ° C~+70 ° C

Protective three proof paint coating, ESD 4kV/8kV

2.2 Unboxing List

GW-01 host x 1

25mm DIN rail buckle x 1

M3 x 6mm flat head screw x 2

Restore USB drive x 1 (including system recovery image)

Quick setup manual x 1

2.3 Installation precautions

Power wiring: Please refer to silk screen printing for terminal definition and pay attention to polarity (V+, V -, FG). Isolating the power supply effectively prevents ground loop interference, and it is recommended to use shielded twisted pair cables.

Serial port wiring:

The RS-232 port (COM1) is a standard 9-wire system (TXD, RXD, GND, etc.) used to connect older PLCs or HMIs.

The RS-422/485 port (COM2) is a differential signal (A, B, GND) that can be connected to a multi station RS-485 network. Pay attention to terminal resistance matching (usually 120 Ω).

Network ports: Two Ethernet ports can be configured as different subnets or in one up one down (WAN/LAN) mode to isolate the on-site control network from the office network.

Grounding: The casing needs to be reliably grounded (FG terminal) to improve anti-interference ability.

Basic operation of iM Connect software platform

GW-01 comes pre installed with Linux kernel (3.14) and iM Connect runtime. Users can configure the gateway IP address through a web browser (supporting Chrome/Firefox) without installing dedicated PC software.

3.1 Initial Startup and Network Configuration

Turn on the power and wait for about 60 seconds for the system to complete startup.

Obtain IP through DHCP (enabled by default), or set a static IP in the serial console (logged in via RS-232).

Enter http://<Gateway IP>in the browser, and the default username/password is admin/admin (forcibly changed upon first login).

The main interface displays the system status (CPU load, memory, temperature, network interface).

3.2 Protocol Driver Management

IM Connect has a built-in protocol library that covers:

Japanese: OMRON (Host Link, FINS), Mitsubishi (FX, Q-series MELSEC), Panasonic, Yaskawa

European and American series: Siemens (S7-200/300/400/1200/1500 via TCP/IP or MPI/PPI）、Allen-Bradley（DF1、EtherNet/IP）、Modbus（RTU/ASCII/TCP）、Profibus DP（ Additional hardware and software support are required

Others: Schneider, GE, Honeywell, etc

When adding a new device, select the corresponding protocol driver, configure communication parameters (serial port baud rate, data bits, stop bits, parity; Ethernet IP/port, station number, etc.), and the system will automatically generate a data label table.

3.3 Data Point Configuration

Users can manually create variables (register address mapping) or automatically enumerate PLC memory areas through the "scanning device" function (supported by some protocols). The supported data types include Bool, Int16, UInt16, ∝, Float, String, etc. Each data point can be set with a collection period (such as 100ms~60s) and a change threshold (dead zone) to reduce network load.

Cloud platform integration and data release

GW-01 supports three mainstream cloud deployment methods, which can be flexibly selected according to the backend system.

4.1 MQTT Release

Configure Broker Address (such as AWS IoT Core, Azure IoT Hub, EMQX, etc.)

Set client ID, username/password (or TLS certificate)

Define publishing theme templates (such as factory/line1/plc1/tag1)

Support QoS 0/1/2, can enable reserved messages and will messages

The data payload format can be JSON or CBOR (Efficient Binary)

4.2 OPC UA Server

GW-01 can be equipped with an OPC UA server, which exposes the collected data points as OPC UA nodes for upper computers (such as SCADA, MES) to access through standard OPC UA clients. Support:

Anonymous/username password/certificate authentication

Data subscription and event notification

Historical data cache (optional, requires external database)

4.3 RESTful API

Provide HTTP/HTTPS interface, third-party applications can read the current value or modify the written data (such as remote control output) through GET/POST requests. The API adopts JSON format and supports cross domain access.

Configuration process:

Create a "Cloud Connection" instance in iM Connect and select the target type.

Fill in the server address and authentication credentials.

Select the data labels that need to be uploaded (batch selection is available).

Set upload cycle (such as once per second) or "upload when changing".

Enable heartbeat packet (keep connection active).

Test the connection status and check the logs to confirm that the data has arrived.

Key points for serial port and network debugging

5.1 Troubleshooting of Serial Communication Malfunctions

RS-232: Confirm the transmission and reception cross connection (Tx → Rx, Rx → Tx, GND → GND). Use a serial debugging tool (such as PuTTY) to simulate the device on the PC side and verify that the gateway serial port is transmitting and receiving normally.

RS-485: Check if the terminal resistance is enabled when multiple stations are in operation (120 Ω for each station). Ensure that all devices are grounded (GND connected). In half duplex mode, the switching time between sending and receiving should match the baud rate to avoid data conflicts.

Isolation impact: Isolating the power supply may introduce voltage drop, ensuring that the potential difference between external devices and the GND of the gateway is within the allowable range.

5.2 Network Connection Diagnosis

Use the ping command to test the connectivity between the gateway and PLC/cloud.

Check if the firewall allows MQTT (1883/8883), OPC UA (4840), and HTTP (80/443) ports.

Dual network ports can be configured as bridging mode or routing mode, depending on the actual topology.

If cross network segment is required, set default gateway and static route.

5.3 Protocol timeout and retry mechanism

Each device can set a timeout period (default 3 seconds) and retry count (default 3 times) separately.

When the PLC response fails, the gateway automatically retries and records an error log.

It can be configured to retain the last value or set it to an "invalid" state after disconnection, making it easier for the upper layer to determine the health of the device.

System maintenance and firmware upgrade

6.1 Factory reset

Using the included recovery USB drive (or self-made):

Insert the USB flash drive into the USB Host port.

Restart the gateway, the system automatically detects the USB flash drive and enters recovery mode.

Follow the on-screen prompts (via web or serial console) to select either restore factory image or update firmware.

6.2 Data Backup and Import

In the web interface, configuration files (including all devices, tags, and cloud connection parameters) can be exported for batch deployment of multiple gateways.

Regularly backup to external storage to prevent accidental loss of configuration.

6.3 Log Monitoring

The system logs running information, error events, communication timeouts, etc.

Support remote syslog forwarding for centralized monitoring.

Quickly determine the status through LED indicator lights (power, operation, error), as defined in the manual.

Common faults and solutions

7.1 Unable to access web configuration page

Check if the gateway IP is on the same subnet as the PC, and try using the DHCP assigned address or default 192.168.1.100 (if not changed).

Connect COM1 (RS-232) using a serial port cable, log in through the terminal (115200, 8N1), and use ifconfig to view the actual IP address.

Press and hold the restore button (if available) to reset the network configuration.

7.2 PLC communication is frequently interrupted

Confirm that the shielding layer of the communication cable is well grounded to avoid strong electrical interference.

Reduce the acquisition frequency (such as extending from 100ms to 500ms) and decrease the bus load.

Check if the communication settings on the PLC side (such as station number and baud rate) match the gateway.

Check if there are any 'timeout' or 'crc error' in the log and adjust the timeout parameters accordingly.

7.3 Frequent disconnection of cloud connection

Test network stability to ensure that the gateway can continuously ping the cloud server.

Check MQTT keep alive settings (recommended for 60s).

If using certificate authentication, confirm that the certificate has not expired and the format is correct.

When enabling TLS, ensure gateway time synchronization (NTP), otherwise certificate verification will fail.

7.4 Data value jumps or anomalies

Check whether the byte order (big end/small end) of PLC data type matches, which can be adjusted in the label properties.

Confirm if the register address offset is correct (such as Modbus addresses starting from 0 or 1).

Enable data dead zone filtering and ignore minor changes (such as<1% not updating).

7.5 Gateway overheating or frequent restarts

Check if the working environment temperature exceeds 70 ° C, ensure good ventilation, and avoid approaching heating equipment.

Verify if the power supply voltage is stable, as transient fluctuations may cause a reset.

Check the system load. If the CPU exceeds 80% for a long time, consider optimizing the collection strategy or upgrading to a 1GB memory model.

Expanding Applications and Secondary Development

GW-01 is based on Linux system, and advanced users can log in via SSH (requires activation) for customized development:

Install custom Python/C applications and collect data through shared memory or local sockets.

Add non-standard protocol drivers (requires iM Connect SDK or self-developed).

Integrate third-party edge computing frameworks (such as Node RED, AWS Greengrass).

But the official recommendation still focuses on web configuration to maintain system stability and technical support consistency.

Maintenance cycle and spare parts recommendations

Regularly (quarterly) check whether the serial port and network cable connectors are oxidized, and replace them if necessary.

Backup the configuration file every six months and store it on the on-site maintenance computer.

Reserve a gateway of the same model as a spare part, which can be quickly replaced in case of hardware failure of the main device, and can be restored by importing the backup configuration.

Follow the ADLINK official website for updates on iM Connect software to obtain new protocol drivers and security patches.