User Guide

UMEC Modbus Gateway: device operation guide

This site explains how to use the gateway in real operation: start the device, configure Modbus lines, add equipment, monitor values, work with dashboards, automation, logs, integrations, and service actions.

For operators For commissioning For service work No firmware code required

What the gateway does

The gateway brings field Modbus devices into one local web interface. It stores configuration, polls devices, shows value freshness, sends commands, runs local scenarios, keeps logs, and, when needed, connects the site to outside systems.

Local core

The device should remain useful on site even without cloud access: polling, Control, scenarios, and logs work locally.

Three Modbus channels

RTU 1 and RTU 2 are physical RS-485 lines. TCP is the network integration channel.

Visible diagnostics

Errors should be observable: stale/offline state, Modbus Log, Scenario Log, Storage, and runtime statuses provide support evidence.

Main value: UMEC Space

By itself, the gateway solves an important local job: it reads Modbus, shows values, and sends commands. Its maximum impact appears when it works with UMEC Space IoT Cloud Platform. Existing Modbus equipment then becomes part of the platform: visible on dashboards, in mobile applications for business users and end users, and available for alerts, notifications, remote control, and integrations. Customer sign-up and site operation happen in UMEC Space Dashboard; mobile access uses UMEC Home for iPhone, UMEC Home for Android, and UMEC Business for Android.

From local Modbus to IoT

Sensors, meters, drives, and controllers become observable digital objects rather than register maps inside a cabinet.

One platform interface

Dashboards, mobile applications, notifications, and roles let different users work with the same site without reading Modbus maps.

Local proof is still required

Lines, devices, values, and commands are verified first. UMEC Space then adds remote visibility and control.

UMEC Space Why gateway + platform deliver the main business value: dashboards, mobile apps, alerts, notifications, and remote control.
Quick Start Minimal first-start sequence: login, mode, network, line, device, Control.
Commissioning Detailed commissioning: lines, devices, channels, commands, Scanner, and Inspector.
Operations Daily use: live values, commands, freshness, charts, and normal-state cues.
Agent Tool Local AI agent tool and skill downloads for safe gateway inspection, token-based testing, and maintenance actions.
Dashboards and Automation Operator panels and local scenarios for routine visibility and automatic actions.
Topologies Typical ways to connect RS-485 lines, TCP devices, MQTT, SCADA clients, and NAT rules.
Diagnostics and Storage And Logs How to find fault causes, collect evidence, and preserve important files.
Settings, Integrations, Maintenance Administrative modes, MQTT/gateway behavior, updates, reboot, recovery, and factory reset.

Section map

UMEC Space

Why gateway + platform create the main business impact.

Quick Start

Short first-start route and expected result.

Commissioning

Line, device, channel, and command setup.

Operations

Daily monitoring, commands, and data freshness.

Agent Tool

Download the local agent tool and Skill package for safe AI-assisted gateway work.

Dashboards

Operator panels, widgets, default dashboard, and warnings.

Automation

Conditions, actions, scenario modes, and Scenario Log.

Topologies

Connection examples for RS-485, TCP devices, MQTT, SCADA, and NAT.

Diagnostics

Scanner, Inspector, stale/offline states, faults, and evidence.

Storage And Logs

Files, SPIFFS, SD Card, Modbus Log, and safe file actions.

Settings

Operating mode, network, time, lines, MQTT, TCP/NAT, and maintenance.

Integrations

UMEC Space, Generic MQTT, Modbus TCP, tunnels, NAT, and bridge.

UI Reference

Screen-by-screen explanation of the embedded web interface.

Template Formats

Devices, channels, commands, and operator-visible JSON structures.

The main principle

Establish stable local operation first: the device is reachable, lines are configured, values are fresh, commands are verified, and logs are readable. Only then enable external integrations and complex scenarios.