Omron NA Series HMI Connection Guide

The NX series security controller communicates with HMI through its built-in EtherNet/IP port (network gateway). Note: Ports on EtherNet/IP units cannot be connected, only CPU built-in ports can be connected.

Controller settings: In Sysmac Studio, assign a fixed IP address to the network gateway and set the subnet mask and default gateway. Link speed recommendation is' automatic '.

HMI settings: basically the same as connecting to the NJ/NX/NY series. Add external devices to the device reference, select "Ethernet" for the communication driver, and enter the IP address of the security controller. Variable import supports data types such as BOOL, BYTE, WORD, WORD, SINT, INT, DINT, REAL, LREAL, STRING, as well as array and structure members.

Special precautions:

The variables of the safety controller usually have safety attributes, and the HMI can only read the status and cannot force the writing of safety outputs (this is a requirement of safety design).

If the structural variables of the safety controller are used in the project, they must be imported from the controller function and cannot be manually copied and pasted.

Connecting Programmable Multi Axis Controllers (CK3 Series): Typical Applications of Modbus/TCP

The CK3 series Programmable Multi Axis Controller is configured using PowerPMAC IDE and supports Modbus/TCP protocol. The NA series HMI communicates with Modbus/TCP clients.

Controller side settings (PowerPMAC IDE):

In "Tools" ->"Options" ->"PowerPMAC" ->"Network Settings", configure the IP address, subnet mask, and default gateway.

Enter the command Sys.ModbusServerEnable=1 in the terminal to enable the Modbus/TCP server.

HMI terminal settings:

In the HMI settings of Sysmac Studio, configure the IP address for Ethernet port 1 (to be on the same network segment as the controller).

Add external device in device reference: supplier Omron, series selection CK3 (specific model), communication driver "Modbus/TCP".

Fill in the IP address of the controller, timeout time (recommended 1-2 seconds), and communication startup waiting time (optional).

Manually add variables in the device variable table. The data type must be FLOAT (32-bit floating-point number). The address format includes I0, M0, P0, Q [0]. 0, etc. Please refer to the appendix of the manual for the scope.

Due to the fact that the Modbus/TCP protocol itself does not distinguish data types, the NA series treats all data as single precision floating-point numbers, so it is important to pay attention to numerical conversion when reading and writing.

Key points of network installation and electromagnetic compatibility

Regardless of the protocol used, the correct installation of the physical layer is the foundation of communication reliability.

Cable selection: 100BASE-TX recommends using AWG24 × 4P STP cable (such as NETSTAR-C5E SAB). It is recommended to use shielded twisted pair cables for serial port cables.

Shielding grounding: The shielding layer of Ethernet cables should be grounded at one end on the switch side to avoid ground circulation caused by grounding at both ends. The shielding layer of the serial RS-422A cable should be connected according to the principle of "ungrounded HMI side" (as shown in Figure b), and the D-SUB fixing screw of CJ1W-CIF11 must be tightened to ensure functional grounding connection.

Switch selection: For EtherNet/IP networks, it is recommended to use switches that support IGMP Snooping (multicast filtering) and L4 QoS (such as OMRON W4S1 series) to prevent multicast data from flooding and affecting real-time performance. Non managed switches do not have these functions and are only suitable for small independent networks.

Power and Grounding: The HMI power supply must use a DC24V power supply with reinforced insulation or double insulation, with a grounding resistance of less than 100 Ω. Do not ground the 24V side, as it may cause a short circuit (only applicable to non isolated NA5- □ W □□□ - V1, while NA5- □ W □□□□ - V1 is not affected for isolated types).

Environmental Protection: The NA series HMI should be installed inside the control cabinet, and the panel thickness should comply with UL Type 1 (1.6~6.0mm) or Type 4X (1.6~4.5mm, with high-pressure waterproof accessories). Avoid direct sunlight, oil mist, corrosive gases, and strong electromagnetic fields.

Common troubleshooting and precautions

7.1 Communication interruption or timeout

Check IP address: Ensure that HMI and controller are on the same subnet and there are no conflicts.

Check firewall settings: If the controller has enabled packet filtering, the IP address of the HMI must be allowed to pass through.

Security communication mismatch: If the controller enables security communication and the HMI Runtime version is lower than 1.16, the connection cannot be established. Upgrade the runtime version of the project or disable secure communication with the controller.

Serial port parameters are inconsistent: baud rate, data bits, stop bits, and parity bits must be exactly the same as the PLC.

FINS node number conflict: Within the same Ethernet segment, all FINS nodes must have unique node numbers.