Omron NA Series HMI Connection Guide

Omron NA Series HMI Connection Guide

In modern factory automation systems, stable and efficient communication between human-machine interface (HMI) and controller is the core link to achieve intelligent manufacturing. The OMRON NA series programmable terminals have become the preferred choice for many system integrators due to their powerful graphical capabilities and flexible communication interfaces. However, facing different platforms such as NJ/NX/NY series motion controllers, CS/CJ/CP series traditional PLCs, NX series safety controllers, and programmable multi axis controllers, engineers often need to switch between multiple communication protocols (EtherNet/IP, FINS, Modbus/TCP, Host Link) and correctly configure IP addresses, variable mappings, and serial port parameters. This article will elaborate on the connection methods, key setup steps, and solutions to common problems between NA series HMI and various OMRON controllers from a practical engineering perspective, helping on-site engineers quickly complete equipment integration and troubleshooting.

System Connection Overview: Choosing the Right Method, Achieving More with Less Effort

The NA series HMI supports two physical connection media: Ethernet and serial interface. Ethernet is suitable for high-speed and large data applications, supporting various industrial protocols such as EtherNet/IP, FINS over UDP, Modbus/TCP, etc; The serial interface (RS-232C/RS-422A) is suitable for older PLCs or cost sensitive applications, using the Host Link protocol.

When planning the system architecture, engineers need to choose the connection method based on the controller model and network load:

Direct connection: Use a crossover cable to directly connect the HMI to the controller, suitable for single machine debugging or small devices.

Switch connection: Connect multiple HMIs and controllers through Ethernet switches, suitable for distributed control systems, enabling data sharing and redundant monitoring.

Regardless of the method, shielded twisted pair cables that comply with the IEEE802.3 standard must be used, and attention should be paid to the grounding method of the shielding layer - it is usually recommended to use single ended grounding to avoid ground loop interference. For serial port connection, the RS-422A method requires the use of an additional CJ1W-CIF11 conversion unit, and the transmission distance should not exceed 50 meters.

Connecting NJ/NX/NY series controllers: perfect integration of native EtherNet/IP

The NJ/NX/NY series controllers have built-in EtherNet/IP ports, making them the ideal partner for NA series HMI. Both are configured through Sysmac Studio software without the need for any third-party tools.

2.1 Controller end settings

In the multi view browser of Sysmac Studio, open "Controller Settings" ->"Built in EtherNet/IP Port Settings". The following parameters must be configured:

IP address: Fixed IP, such as 192.168.1.10, subnet mask 255.255.255.0.

Default gateway: Set if there is a need for cross network communication, otherwise leave blank.

Link settings: It is recommended to use "auto negotiation".

If secure communication is required, the HMI runtime version must be 1.16 or higher. You can check whether secure communication is currently enabled in the "External Device Settings" section of the system menu. Attention: Runtime 1.15 and below versions cannot establish a connection with controllers that enable secure communication.

2.2 HMI terminal settings

In the HMI project of Sysmac Studio, double-click on "HMI Settings" ->"TCP/IP Settings" to assign an IP address (such as 192.168.1.20) on the same network segment as the controller to Ethernet port 1 of the HMI. Then, add external connected devices in the "Device Reference":

Equipment supplier: Omron

Equipment series: Choose NJ/NX/NY according to the actual situation

Communication driver: Ethernet

For controllers already registered in the current project, the system will automatically recognize them and there is no need to manually add them. For unregistered external controllers, manual input of IP address and timeout time (usually set to 2-5 seconds) is required.

2.3 Variable Import and Mapping

The NA series HMI supports direct reading of global variables from NJ/NX/NY controllers. There are three ways to import variables:

Import from controller: Click the "Import" button to automatically read all global variables in the controller. This is the most recommended way to ensure the integrity of data types and structures.

Copy and paste: Copy the required variables from the controller's global variable table and paste them into the HMI's device variable table. However, please note that structural variables cannot be imported in this way and must be imported using the import function.

Excel file import: Prepare an Excel file in the specified clipboard format (UTF-16 LE encoding, tab separated), and then import it.

The supported data types include BOOL, INT, DINT, LINT, UINT, WORD, REAL, LREAL, STRING, TIME, DATE, etc. Array elements, structure members, and enumeration variables are all accessible, with array indices starting from 0.

When mapping, drag the device variables onto the global variables of the HMI to use them directly on the screen. Please note that if the controller is set to secure communication, the project file must be runtime 1.16 or higher.

Connecting CS/CJ/CP series PLCs: Detailed explanation of three mainstream protocols

The traditional CS/CJ/CP series PLC (hereinafter referred to as CJ series) provides multiple communication methods, and the NA series HMI supports the following three types:

3.1 Ethernet FINS Communication

FINS (Factory Interface Network Service) is a proprietary network protocol of OMRON that enables cross segment data exchange over Ethernet.

PLC end settings:

Use CX Programmer software to configure Ethernet units (such as CJ1W-ETN21 or built-in ports) in the "Unit Settings". IP address, subnet mask, and default gateway need to be set.

In the "FINS/UDP" tab, the UDP port number remains at default 9600, the IP address translation method is selected as "Auto Generate (Dynamic)" or "Auto Generate (Static)", and "Dynamically Change Remote IP" is disabled.

For EtherNet/IP units such as CS1W-EIP21S/CJ1W-EIP21S, FINS is disabled by default at the factory and must be manually enabled (refer to the corresponding operating manual).

The node address is set through the rotary switch in front of the unit, with a range of 01~7E (1~126 decimal), and cannot be duplicated within the same network.

HMI terminal settings:

In the HMI settings of Sysmac Studio, configure the IP address of Ethernet port 1 and click the "FINS Settings" button, enter the network address (usually 0) and routing table (if necessary).

Add external device in 'Device Reference': supplier Omron, series CJ, communication driver 'FINS Ethernet'. Then fill in the network address, node address (consistent with the FINS node number of the PLC), frame length (CP series set to 1016 or below), timeout time, etc.

The node address will be automatically generated from the last bit of the IP address, but it can also be manually specified.

Variable import: You can copy global variables through CX Programmer or import CXT files/Excel files. The accessible address range includes CIO area, HR area, AR area, DM area, EM area (supported by CJ2), timer/counter PV and completion flag, etc.

3.2 EtherNet/IP Communication (Label Data Link)

Models in the CJ series with built-in EtherNet/IP ports or CJ1W-EIP21 units support label based CIP message communication. The NA series HMI can directly use network variables (labels) in the PLC without worrying about physical addresses.

PLC end settings:

Register global variables as network variables in CX Programmer. The "Network Variables" and "Open Only" checkboxes must be selected, and either the input or output direction must be chosen.

Configure the IP address, subnet mask, etc. of the EtherNet/IP port.

HMI terminal settings:

Add external device in device reference: Select "CIP Ethernet" for communication driver.

In communication configuration, you can enter an IP address or specify the destination through a routing path (such as 1, 192.168.1.10).

When importing variables, click the "Import" button to read all network variables from the PLC. The correspondence between data types is basically the same as that of the NJ series.

Note: The NA series does not support address based CIP communication and can only use tag names.

3.3 Serial Host Link Communication

For old PLCs without Ethernet interfaces, serial port connection is the most reliable choice. The NA series HMI provides an RS-232C port that can be directly connected to the RS-232C port of a PLC; If long-distance or multi-point connection is required, it can be converted to RS-422A through the CJ1W-CIF11 conversion unit.

PLC end settings (CX Programmer):

In the "Serial Port" tab of "PLC Settings", select the communication mode as "Host Link".

Communication speed: Consistent with HMI (such as 9600, 19200, etc.).

Parameters: Data bit 7, stop bit 2, even parity check (i.e. "7,2, E").

HMI terminal settings:

In the HMI settings of Sysmac Studio, click on "Serial Port Settings", select "Connect to External Devices" as the application, and fill in the same baud rate, data bits, stop bits, and checksum as the PLC.

Add external device in device reference: Select 'Host Link' for communication driver.

The variable import method is similar to Ethernet FINS, but please note that the serial communication speed is slow and avoid mapping large arrays or structures. If necessary, it is recommended to split the large array into multiple small variables or only map the addresses actually used.

Cable production: It is recommended to use finished wires such as XW2Z-200T or solder D-SUB 9-pin plugs for RS-232C cables. When connecting RS-422A, the DIP switches of CJ1W-CIF11 need to be set to Pin1=ON (terminal resistance), Pin2=OFF, Pin3=OFF, Pin6=ON (RTS control). The shielding layer should be grounded at one end, usually on the side of the conversion unit.

Connecting NX series safety controllers: balancing safety and monitoring

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.

DIP switch error for CJ1W-CIF11: When using RS-422A 4-wire system, Pin2=OFF，Pin3=OFF； If using a 2-wire system, Pin2=ON. Terminal resistor Pin1 is only turned on at both ends of the device.

7.2 Variables cannot be read or have incorrect values

Data type mismatch: For example, mapping UINT in the controller to Short in HMI can result in symbol errors. Check the data type correspondence table in the manual.

Address out of bounds: For the CJ series, when accessing the EM area, it is necessary to ensure that the current bank exists (only CJ2 supports multiple banks).

Structure import failed: Do not manually copy structure variables, you must use the 'Import from Controller' function.

Online editing causes interruption of variable access: When using Sysmac Studio for online editing of a controller, the HMI briefly pauses variable access to the controller. If editing variables that do not involve HMI references, and the Runtime version is ≥ 1.13 and the controller firmware is sufficiently new, this process will be omitted and access will not be interrupted.

7.3 Performance degradation

Avoid mapping large arrays or structures: this is particularly evident when connecting through serial ports. Suggest mapping as needed or accessing array elements separately.

Reduce timeout: If the network quality is good, setting the timeout to 1 second can speed up error recovery.

Using switch multicast filtering: In EtherNet/IP networks, unfiltered multicast packets can consume a significant amount of bandwidth.

7.4 Touch screen no response or abnormal display

The backlight brightness setting is too dark: it can be adjusted in the system menu, or the default brightness can be restored through the item properties.

Touch calibration drift: Regularly perform touch calibration to avoid accidental triggering of edge objects.

Glove wearing operation: Capacitive touch screens are not sensitive to thick gloves. It is recommended to use specialized touch gloves or reduce the thickness of gloves.