ADLINK GW-01 Industrial IoT Gateway Configuration and Debugging Guide

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.