Pro face connection to Mitsubishi DIASYS Netmation

4.3 System Data Area (LS Area)

The system data area (LS area) of Pro face can also be mapped to the aforementioned device addresses of Netmann. Efficient state exchange between HMI and PLC can be achieved through system area settings. Please refer to the GP Pro EX reference manual for specific LS area address allocation.

Error Messages and Troubleshooting Guide

Communication failure is the most common issue on site. Pro face will display a formatted error message on the screen: 'Number: Device Name: Error Message (Error Occurrence Area)'. Understanding this information is the key to quickly solving problems.

5.1 Error Display Format

Number: Error code.

Device Name: The name set for the external device in GP Pro EX, which defaults to PLC1.

Error message: A textual description of the error.

Error occurrence area: It may be an IP address (displayed as "IP address (decimal): MAC address (hexadecimal)"), device address (such as "Address: CDO0001"), or error code received from Netmation (such as "Error Code: 1 [01]").

5.2 PLC specific error codes

When Pro face sends a command to Netmation, Netmation may return the following standard MODBUS exception code:

Error code (decimal) reason common trigger message

01 unsupported function codes RHxx034/RHxx035

02 Address does not exist or exceeds the range RHxx036/RHxx037

03 Data value not accepted (such as writing illegal value) RHxx034/RHxx035

Troubleshooting steps:

For error 01: Check if MODBUS function codes that Netmation does not support are used in GP Pro EX (such as some variations of batch write hold registers). Try using single character reading and writing instead.

For error 02: Confirm if the device address being accessed (such as CDO9000) is within the valid range of Netmation. Refer to the Netmation manual to verify address limits.

For error 03: Check if the data type written is correct (such as writing a hexadecimal value to a numeric address), or if the value is out of range.

5.3 Unique Error Messages

The following error message only appears in the DIASYS Netmation MODBUS TCP driver and is strongly related to redundant CPU configuration:

RHxx128：There is two primary CPU

Pro face detected two CPUs claiming to be in the main control state simultaneously. This is usually due to inconsistent Netmation redundancy configurations or network partitioning. Solution: Check the synchronization link of the redundant CPU, restart the backup CPU or reconfigure the redundant parameters.

RHxx129：There is not primary CPU

Indicates that no main CPU has been detected. Possible reasons: Both CPUs are in a faulty or offline state, or the control state detection address (CDOxxxx) is configured incorrectly. Firstly, confirm the CPU status indicator light on the Netmation side, and then check if the "Check Control Mode" address set in Pro face matches the actual control status address in Netmation.

RHxx130：This project data has too many nodes

In the current project, Pro face is attempting to establish connections with over 16 Neumann nodes simultaneously. This driver supports up to 16 concurrent connections. Please reduce the number of devices or re plan the network grouping.

5.4 General Communication Troubleshooting Process

Physical connection check: Is the Ethernet cable properly plugged in? Is the switch powered on? Is the corresponding port indicator light flashing?

IP address verification: Check its IP address in HMI offline mode and use PC ping to test whether the IP and Netmation CPU IP are reachable.

Port reachability: Use MODBUS scanning tools (such as ModScan) to test if Netmann's TCP port (default 59710) is open.

Configuration consistency: Ensure that the IP, port number, timeout, and other parameters in Pro face match exactly with the Netmation side. Please note that in redundant mode, the IP addresses of the primary and backup CPUs cannot be reversed.

Log analysis: Some Pro face models support exporting communication logs, which can further locate errors.

Engineering Practice Suggestions

To ensure long-term stable operation of the system, please follow the following additional recommendations:

IP address planning: Static IP addresses are uniformly allocated by network administrators and recorded. Avoid using automatic access control (DHCP).

Redundant CPU status monitoring: In addition to Pro face automatic monitoring, it is recommended to display the current status of the active CPU on the HMI screen (for example, by reading the control status address and reflecting it in the indicator light element), to facilitate the operator's understanding of the system health.

Connection limit: Each Pro face can connect up to 16 Netmann nodes simultaneously. If a project requires monitoring more than 16 CPUs, consider increasing the number of HMIs or using data gateway aggregation.

Firmware version compatibility: Before first use, confirm that the Pro face firmware version and GP Pro EX version support the driver (refer to the official release instructions).

Offline mode debugging: After completing the basic settings in GP Pro EX, download the project to HMI, and then enter offline mode to check the communication parameters again - modifications in offline mode will overwrite the project settings, which is an effective means of quickly correcting errors on site.