Industrial touchscreens

I10-2004

web HMI touchscreen for field-data collection and local touch operation, with browser access to the monitoring project from a phone, tablet or PC. Provides 2 Ethernet ports, 4 serial ports, 2048-point capacity.

Serial ports4

RS485 ports4

Ethernet ports2

Product typeTouchscreen

Acquisition protocol coverageAll acquisition protocols for serial and Ethernet connections

Forwarding protocolsBACnet / Modbus / MQTT / Database / OPC UA

Physical interfacesRS485 / Ethernet

Point capacity2048

Built-in touchscreenSupported

HMI configurationSupported

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.

I10-2004

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
- All listed acquisition protocols for serial and Ethernet
03
I10-2004
- Ethernet × 2
- RS485 × 4
- Built-in HMI / WEB visualization
- Physical touchscreen
04
System-side forwarding
- BACnet
- Modbus
- MQTT
- Database
- OPC UA
05
Compatible system types
- BACnet building management system
- Modbus system
- MQTT platform
- Database application
- 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: Not specified in the records; verify against the field device and supervisory system
Forwarding side: Not specified in the records; verify against the field device and supervisory system

Recorded capacity

2048 points

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 groupI10

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 candidates2 models

I10-1031
All serial and Ethernet acquisition protocols
Forwarding: BACnet / Modbus / MQTT / Database / OPC UA
I10-2004
All serial and Ethernet acquisition protocols
Forwarding: BACnet / Modbus / MQTT / Database / OPC UA

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 (1)Related content

Product overview

Key functions

Local touch operation

Download the HMI project to the touchscreen for on-site data display and touch operation.

Visual monitoring

Organize device data in HTML5 HMI screens with real-time curves and chart displays.

Logic and scheduling

Supports graphical programming and mixed JS/PLC logic, with schedules and triggers for project-specific control tasks.

Local data history

Includes an InfluxDB time-series database with configurable storage intervals for retaining field data.

Alarm notifications

Supports alarm notifications through WeChat, SMS, DingTalk, email; configure the required channels for the project.

External database storage

Supports storing data in MySQL, Microsoft SQL Server, InfluxDB, Apache Doris, PostgreSQL for integration with existing data-management systems.

Connections and integration

The model rule confirmed on 2026-10-02 covers all serial and Ethernet acquisition protocols in the reviewed protocol list. System-side interfaces are BACnet, Modbus, MQTT, Database and OPC UA. Check wiring, communication roles and point mappings for the actual hardware edition.

Typical applications

Building-device integration and centralized monitoring; Industrial-device acquisition and monitoring; Lighting-device connectivity and management.

Model selection essentials

Model configuration: 2 Ethernet ports, 4 RS485 channels, 2048 points.

Current product specifications

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

Parameter	Specification
Total serial ports	4
RS485 ports	4
Ethernet ports	2
Point capacity	2048
Forwarding protocols	BACnet / Modbus / MQTT / Database / OPC UA
Physical interfaces	RS485 / Ethernet
HMI visualization	Supported

Model datasheets

File unavailable in this language

Selection checklist

Why this matches

Acquisition protocolsModbus RTU_UDP

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：Acquisition roles / Output roles / Device capacity / 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

View parameter evidence

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

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

I10-2004

Start using this model

General commissioning guide

Field devices

Device-side acquisition

I10-2004

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

Product overview

Key functions

Local touch operation

Visual monitoring

Logic and scheduling

Local data history

Alarm notifications

External database storage

Connections and integration

Typical applications

Model selection essentials

Current product specifications

Model datasheets

Selection checklist

Related FAQs

Related content

I15-1031

I32-1031

I4-1001-0200

Your next connection starts here.