Quick Start

Start the gateway without unnecessary detours

This page gives a short practical route: open the interface, choose the mode, configure communication, add the first device, and confirm that live values are arriving.

15-30 minutes for a basic check User-level actions only Local operation first

Expected result

After quick start, the gateway should open in a browser, use the selected language, have an operating mode, see at least one Modbus line, and show live values for at least one device on the Control page.

Before connecting

Prepare a laptop with Ethernet or a USB-Ethernet adapter, an Ethernet cable, gateway power, and, for RS-485 checks, at least one known Modbus device with known serial parameters. Wired access is the best first step because it does not depend on the site's Wi-Fi profile.

Parameter First-access value Comment
Gateway Ethernet IP 192.168.4.2 Deterministic Ethernet static profile when no saved configuration exists.
Netmask 255.255.255.0 Set the laptop to the same subnet, for example 192.168.4.10.
Browser address http://192.168.4.2 If the device is already configured for DHCP or another static IP, use the actual site address.
Username admin The current repository bench materials use the local admin account.
Password admin Factory local access is normally admin/admin unless delivery notes or the integrator define another password. Change it after login.

First Ethernet connection

Power the gateway Wait until startup is complete. Do not change settings before the device is reachable.
Connect laptop and gateway by Ethernet For direct connection, set the laptop to a static address in the same subnet, for example 192.168.4.10 with mask 255.255.255.0.
Open the gateway address In the browser open http://192.168.4.2. If it does not open, check laptop IP, cable, power, and VPN/proxy settings.
Log in and change the password Use first-access credentials, then open Settings -> Credentials and set the production password.
Access works The web interface opens, login succeeds, and the top status row plus section navigation are visible.
Resolve the network The page opens on DHCP or a previously configured address instead of 192.168.4.2. Record the actual site address.
Stop and investigate The interface does not open or login fails. Do not move to Modbus, MQTT, or scenarios until access is stable.

First-start sequence

Open the web interface Connect to the device network and open the gateway address in a browser. If the interface is unreachable, solve network access before touching Modbus settings.
Choose language and log in On the login page choose RU or EN. The choice is stored in the browser and applies to other pages.
Check the top status row After login, look at Uplink, Cloud, Gateway, and Automation. These indicators show actual runtime state, not just section names.
Set the operating mode In Settings choose UMEC Space, Generic MQTT, or MQTT Disabled. For the first local launch, keeping external integration disabled is acceptable when the site is not connected to an upper-level system yet. If UMEC Space is selected, customer registration and the provisioned gateway check happen in UMEC Space Dashboard.
Set network and time Check Wi-Fi/Ethernet, DHCP/static IP, DNS, and time. Wrong time makes log analysis much harder.
Configure the Modbus line In Setup choose RTU 1, RTU 2, or TCP. For RS-485 set baud rate, parity, data bits, stop bits, and line mode. Do not expect live values in Control yet: a working line and at least one device definition are required first.
Add a device Enter address, name, model, serial number, channels, and commands. For TCP devices, check tunnel binding if several tunnels are enabled.
Verify Control Open Control, choose the line and the device. Confirm that the line is not paused, values are fresh, required channels are selected for the chart, and commands are visible and work as expected.

Three completion paths after local proof

Prove local operation first: the device exists in Setup, appears in Control, values update, and commands return an understandable result. Only then choose the final integration path.

Mode Use when Check after local Control
MQTT_DISABLED The gateway remains local with no outside broker or cloud. Dashboards, local scenarios, Storage, Modbus Log, and clear line statuses.
UMEC_SPACE The recommended high-impact path: dashboards, mobile app, alerts, notifications, and remote control through UMEC Space. Cloud runtime, MQTT connection, correct provisioning; BLE pairing is available only in this mode. Check the gateway in Dashboard, mobile access through UMEC Home or UMEC Business.
MQTT_GENERIC Data must be published to a third-party MQTT broker. Broker URL, auth/TLS, redacted password, publish/subscribe topic preview, and actual message publishing.

Final check after adding a device

Ready Control shows the device, channels update, selected channels appear in the realtime chart, and a command returns a clear result.
Needs checking The device is listed, but values are stale/offline, the line is paused, polling is disabled, or the command returns an error.
Stop and investigate Line settings cannot be saved, the device does not respond even in Scanner/Inspector, or runtime state reports a line-owner error.

Minimum settings by area

Area Action Healthy signal
Login Choose language and sign in with an operator or administrator account. The protected shell opens with runtime status pills and navigation.
Settings Set operating mode, network, time, and line modes. The section shows success or a clear reason why saving was rejected.
Setup Create line/device data, channels, and commands. The device appears on the selected line and is not mixed with another line.
Control Select the device, check values, and mark channels for charts. Values are fresh, errors are visible, and charts update without page jumps.
Storage and logs Confirm that configuration files and logs are available for service work. The file tree opens and the selected file can be viewed or downloaded.

What not to do in the first hour

  • Do not enable external integration before local polling is verified.
  • Do not edit JSON in Storage when the same task can be done through Setup.
  • Do not use factory reset for a normal communication issue with one device.
  • Do not confuse RTU transparent mode and TCP mode: TCP is a separate integration channel.

Primary visual checkpoints

Login

Login page in English.
The starting point: language, credentials, and login errors should be understandable to the operator.

Device in Setup

Device editor in English.
Check name, address, model, serial, channels, and commands before moving to Control.

Live values

Control page with live values in English.
A successful quick start ends here: the device is selected, values update, and a command is available.

Where to go next

If first start is successful, continue with Commissioning. For regular use, read Operations. For operator screens, move to Dashboards.