HMI / web visualization gateways

HMI1002-Lite-E

Collect Modbus RTU device data using 1 Ethernet port, 2 RS485 ports and a 512-point capacity. Connect field devices to BACnet or Modbus supervisory systems and use the gateway’s MQTT service for building or industrial monitoring applications.

Serial ports2

RS485 ports2

Ethernet ports1

Acquisition protocol coverageListed protocols · Modbus RTU

Acquisition protocolsModbus RTU

Forwarding protocolsBACnet / Modbus / MQTT / OPC UA

Physical interfacesEthernet / RS485

Acquisition rolesModbus RTU Client

Output rolesBACnet Server / Modbus Server / MQTT Server / OPC UA Server

Point capacity512

Device capacity64

Built-in touchscreen—

HMI configuration—

USB Type-C power—

4G connectivity—

WiFi—

LoRaWAN—

Start using this model

Review the model documents, then prepare the files needed for connection and commissioning.

HMI1002-Lite-E

No related files are listed in this language. Contact technical support to confirm the documents you need.

General commissioning guide

Connection, point mapping, live-value checks and troubleshooting.

View general steps Confirm required files

Connection and configuration preparation

Review how devices connect, then prepare the field point list and supporting files.

01
Field devices
- Confirm the driver against the device brand, full model and communication documentation
02
Device-side acquisition
- Modbus RTU
03
HMI1002-Lite-E
- Ethernet × 1
- RS485 × 2
04
System-side forwarding
- BACnet
- Modbus
- MQTT
- OPC UA
05
Compatible system types
- BACnet building management system
- Modbus system
- MQTT platform
- OPC system

Arrows show connection order. Check model wiring instructions and the project point list for terminals, port assignments and read/write directions.

Communication roles

Acquisition side: Modbus RTU Client
Forwarding side: BACnet Server / Modbus Server / MQTT Server / OPC UA Server

Recorded capacity

512 points / 64 devices

Check before connecting

Check the device brand, model, driver version and interface. Use the wiring diagram to confirm terminals and port assignments.
Prepare a point list with addresses or objects, data types, byte order, units and read/write permissions.
Confirm the role at each end and the device address, serial settings, or IP address and port.
Check point count, device count and physical port count separately, then confirm capacity for the actual data volume.

Files for configuration

Model documentsNo dedicated file listed
Request
User manualNo dedicated file listed
Request
Wiring diagramNo dedicated file listed
Request
Configuration tools and supporting filesNo dedicated file listed
Request

Statuses reflect files associated in the current language. Contact technical support with this model to confirm other supporting resources.

How to choose within a series

Match device-side protocols and the host system first, then check ports, wireless connections and capacity. Candidates below use confirmed model specifications.

Current model groupHMI1002

You need multiple serial and Ethernet protocols

Check models confirmed to cover all acquisition protocols for serial and Ethernet connections. Check protocol scope and physical port counts separately. Confirm dedicated CAN, KNX TP and 2-wire MBus connections for the specific model.

Confirmed candidates6 models

HMI1002-ARM
All serial and Ethernet acquisition protocols
Forwarding: BACnet/IP / BACnet MS/TP / Modbus / MQTT / Database / OPC UA
HMI1002-ARM-4G
All serial and Ethernet acquisition protocols
Forwarding: BACnet / Modbus / MQTT / Database / OPC UA
HMI1002-ARM-WiFi
All serial and Ethernet acquisition protocols
Forwarding: BACnet / Modbus / MQTT / Database / OPC UA

Show 3 more models

HMI1002-ARM(CAN)
All serial and Ethernet acquisition protocols
Forwarding: BACnet / Modbus / MQTT / Database / OPC UA
HMI1002-ARM(LoRaWAN)
All serial and Ethernet acquisition protocols
Forwarding: BACnet / Modbus / MQTT / Database / OPC UA
HMI1002-ARM(NXP)
All serial and Ethernet acquisition protocols
Forwarding: BACnet / Modbus / MQTT / Database / OPC UA

View full group specifications

The site uses OPC, Modbus and BACnet families

Start by checking these three families for HMI1002-Lite and the listed variants with the same scope. For other acquisition protocols, check models with the corresponding coverage.

Confirmed candidates4 models

HMI1002-Lite
Acquisition families: OPC / Modbus / BACnet
Forwarding: BACnet/IP / BACnet / Modbus / MQTT / Database / OPC UA
HMI1002-LITE-4G
Acquisition families: OPC / Modbus / BACnet
Forwarding: BACnet / Modbus / MQTT / Database / OPC UA
HMI1002-Lite-WiFi
Acquisition families: OPC / Modbus / BACnet
Forwarding: BACnet / Modbus / MQTT / Database / OPC UA

Show 1 more models

HMI1002-Lite(NXP)
Acquisition families: OPC / Modbus / BACnet
Forwarding: BACnet / Modbus / MQTT / Database / OPC UA

View full group specifications

Device-side acquisition only needs Modbus RTU

The listed HMI1002-Lite-E variants have confirmed Modbus RTU acquisition. Lite-E scope differs by series; this rule does not apply to every Lite-E model.

Confirmed candidates3 models

HMI1002-Lite-E
Listed acquisition protocols: Modbus RTU
Forwarding: BACnet / Modbus / MQTT / OPC UA
HMI1002-Lite-E(4G)
Listed acquisition protocols: Modbus RTU
Forwarding: BACnet / Modbus / MQTT / OPC UA
HMI1002-Lite-E(WiFi)
Listed acquisition protocols: Modbus RTU
Forwarding: BACnet / Modbus / MQTT / OPC UA

Continue filtering by protocol

The device protocol is fixed

Check each model’s listed acquisition protocols and the required host-system protocol. A model suffix alone does not establish equivalent acquisition capability.

Confirmed candidates1 models

HMI1002-KNX-TP
Listed acquisition protocols: KNX TP
Forwarding: Modbus / BACnet / MQTT / Database / OPC UA

View full group specifications

Acquisition scope needs confirmation

These models have no listed acquisition scope suitable for this decision. Check their model notes and provide device make, model and protocol documentation.

Models to verify1 models

HMI1002-MBus
Acquisition scope unconfirmed
Forwarding protocols unconfirmed

View full group specifications

This guidance narrows the candidates. Confirm communication roles, read/write direction, the point list, wiring and model-specific resources before final selection.

“Unconfirmed” means documentation does not establish a value; it does not mean zero or unsupported.

Overview & technical information Selection checklist FAQ (3)Related content

Product overview

Configure the device point list in X2View and upload the project to the gateway. The owner-confirmed acquisition scope is Modbus RTU only.

Selection and reading guide

The owner-confirmed acquisition scope is Modbus RTU only; this rule was reconfirmed on 2026-10-02.
Before mapping points, read the Modbus address-base notes on page 3; acquisition decimal/hexadecimal addresses and forwarding addresses use different stated bases.

Model document guide

File unavailable in this language; purpose and functions: page 3; specification references: pages 2, 3, 5

Current product specifications

Specifications are sourced from the supplied 2026 product catalog. Unspecified values remain unconfirmed.

Parameter	Specification
Total serial ports	2
RS485 ports	2
Ethernet ports	1
Point capacity	512
Device capacity	64
Acquisition protocols	Modbus RTU
Forwarding protocols	BACnet / Modbus / MQTT / OPC UA
Acquisition roles	Modbus RTU Client
Forwarding roles	BACnet Server / Modbus Server / MQTT Server / OPC UA Server
Physical interfaces	Ethernet / RS485

Acquisition follows the model rule confirmed by the owner on 2026-10-01 and reconfirmed on 2026-10-02. Broader acquisition lists in older documents do not define the current scope. Hardware, forwarding and edition conditions are retained.

Model datasheets

File unavailable in this language

Selection checklist

Why this matches

Acquisition protocolsModbus RTU
Forwarding protocolsMQTT

Confirm before selecting

Protocol compatibility is the first step. Check the device model, communication roles, point count and wiring. Capabilities that are not documented require confirmation.

Not yet documented：RS232 ports / CAN ports / KNX TP ports / Two-wire MBus ports / DI digital inputs / DO digital outputs / AI analog inputs / AO analog outputs / USB Type-C power / 4G connectivity / WiFi / LoRaWAN / HMI configuration / Built-in touchscreen / Product type

View parameter evidence

Acquisition protocols · Modbus RTUModel rule confirmation (2026-10-02) · 2026-10-02

Forwarding protocols · MQTT

转发端支持的协议 BACnet、Modbus、MQTT、OPC UA

2026产品目录 · HMI1002-Lite-E.pdf · 2026资料集 · Page 2

Continue filtering and comparing

Related FAQs

Find configuration and usage guidance linked to this content. Refer to documentation for the exact model and version.

What does X mean, and how do acquisition and forwarding protocols differ?

X denotes the acquisition-side protocols. Also check forwarding protocols, communication roles, physical interface types and port counts.

Read the full answer

Why does selecting several protocols return no results, and how do manual names work?

Multiple protocols require an AND match. Manual names are kept exactly, and undocumented compatibility is never treated as confirmed support.

Read the full answer

How should I verify acquisition support for ARM, Lite and E models?

Check the latest owner-confirmed model rules: serial/Ethernet coverage for ARM/A9 and industrial touchscreens, the HMI1002-Lite protocol families, and the Modbus RTU-only HMI1002-Lite-E variants.

Read the full answer

HMI1002-Lite-E

Start using this model

General commissioning guide

Field devices

Device-side acquisition

HMI1002-Lite-E

System-side forwarding

Compatible system types

Communication roles

Recorded capacity

Check before connecting

Files for configuration

How to choose within a series

You need multiple serial and Ethernet protocols

The site uses OPC, Modbus and BACnet families

Device-side acquisition only needs Modbus RTU

The device protocol is fixed

Acquisition scope needs confirmation

Product overview

Selection and reading guide

Model document guide

Current product specifications

Model datasheets

Selection checklist

Related FAQs

Related content

HMI1001-ARM

HMI2002-Lite-E

HMI1001-ARM-WiFi

Your next connection starts here.