CimonHmiMaster
Purpose
CIMON HMI Ethernet protocol variable read and write driver
Open the plugin
Enter "Development Configuration → Collection Configuration", create a device and select "CimonHmiMaster" in "Collection Plugin".
Supported channels and data types
| Channel type | Pre-configuration check |
|---|---|
| TCP Client | Confirm network reachability of the device IP, port, and gateway to the device. |
| UDP | Confirm the local binding address, port and firewall rules, and check the source of the packet. |
Optional data types: Boolean, Int16, UInt16, Int32, UInt32, Float, String
Plugin properties
Protocol parameters
| Setting | Description |
|---|---|
| PLC CPU model | Default: 6; fill in: drop-down selection. PLC CPU model; used to verify the official address range of each device area |
| Frame number | Default: 1; Range: 0~127; Fill in: text input. Frame number; must match PLC or virtual server configuration, range 0 to 127 |
Address rules
- CIMON WORD address: X, Y, M, L, K, F, D, S, TC, TS, CC, CS.
- The last bit of X/Y/M/L/K/F must be 0 when performing WORD access. For example, X10 means WORD 1.
- Boolean is read-only and uses decimal WORD address and bit number, such as D1.15; the bit number range is 0 to 15.
- TC and CC are read-only device areas; the range of a single request is 1 to 512 WORD.
Functions
| Function | Purpose |
|---|---|
| Read and write | Read a confirmed point and write only to an approved test point. |
| Messages | View sent and received frames, protocol fields, and error details. |
Device debug
Enter "Development Configuration → Collection Configuration", select the current device and click "More Functions", then open "Debug".
Read and write
Perform read or write verification according to the current plugin address rules; confirm on-site security and permissions before writing.
Messages
Check the device's message sending and receiving and protocol logs to locate message format, connection and parsing problems.
Verify the configuration
Use a confirmed on-site address to perform reading. The return value, data type and byte order should be consistent with the point list; after the writable point is written, it should be read back according to on-site requirements.
Troubleshooting
- Address reading failed: Check the station number, register or node ID one by one according to the address rules on this page, and confirm that the data type is consistent with the device point list.
Related links
- Collection configuration: View channel, device and common variable configuration.
- Plugin Index: Find other collection or data-forward plugins.