Edited English translation of the original Chinese case. The original images and on-screen Chinese text are retained. Model names and example settings describe that source version; check current model documents for a new project.
Requirement: one data source, more than one system
The source starts with a Modbus RTU integration problem: several supervisory controllers or touch panels need the same device data. Its proposal separates device polling from access by the supervisory systems, using a MOD2004-Lite gateway and the X2Modbus configuration environment.
This is not a proposal to connect several independent RTU masters directly to the same bus. The gateway polls the field devices and presents the resulting data through separately configured server connections.
Proposed connection and point mapping
Original multi-system Modbus connection diagram
- Connect field slave devices to COM1 and configure the points to be acquired. On this path the gateway acts as the Modbus master and polls the devices.
- Configure the gateway's service-side point mappings so that supervisory systems can read the acquired data.
- The original diagram describes three separate RTU master connections. The source also describes Modbus TCP server access for TCP clients.
The number of supported links and the detailed port arrangement must be checked against the exact hardware and software version. The diagram is not a capacity statement for other models.
Meter-integration example: EBI and Elster
The second part of the source concerns equipment integration at Honeywell's new headquarters. Electricity-meter data was already being supplied through an existing Modbus path to the HEM energy platform associated with Honeywell EBI. The meter manufacturer, Elster, also had an Enacto platform that needed the same meter data.
The documented arrangement uses gateway COM1 to acquire the meters, COM2 as an RTU Server feeding an Elster RTU gateway, and the Ethernet interface as a Modbus TCP connection to EBI. During the commissioning described in the source, the two serial paths used matching communication settings, and the gateway register addresses were mapped one-to-one to the meter registers.
Original integration or configuration screenshot 1
Original integration or configuration screenshot 2
Original integration or configuration screenshot 3
Recorded outcome and limits
The source reports that the meter data was connected to both EBI and the Elster energy platform and describes communication as stable. It supplies no latency measurements, load-test results or independent acceptance data. Treat this as the source author's project account, not a quantified performance guarantee.
For a new installation, confirm device addresses, serial settings, register types, address mapping and the required client/server roles before expanding from one verified point to the complete point list.