HMI Connection

Connect the HMI to the RS-232 or RS-485 channel shown for your product. The table lists each product's standard configuration. UART (Serial3) is a TTL-level port, and this guide does not use it for the HMI connection.

1. Connect RX to TX and TX to RX.
2. On most ILOGICS products, RS-232 terminals are labeled RX and TX, and UART terminals are labeled RXD and TXD. If your product uses other labels, follow its product page.
3. On some HMIs the GND of the communication line is isolated. If communication fails, check the GND connection.

1. Connect terminals of the same polarity directly: plus to plus, minus to minus.
2. The labels A/B differ by manufacturer. Check the HMI manual to see which one corresponds to + and -.
3. Short runs can work without termination. If the run is long or communication fails, connect a terminating resistor of about 120 Ω at each end of the line.
4. MPINO and MPAINO products have no built-in terminating resistor. If the product is at the end of the line, connect 120 Ω between 485+ and 485-.
5. If the HMI is at the other end of the line, check whether it has built-in termination and whether it is enabled. Enable it if available. Otherwise connect 120 Ω between the HMI's + and -.
6. Do not connect a terminating resistor to devices in the middle of the line.

The product and the HMI must use the same protocol, station number, baud rate, data bits, parity, and stop bits. Choose Modbus TCP only when you build a separate Ethernet conversion setup.

With Modbus RTU and Modbus TCP, the product's M0 and D0 are mapped to numeric communication addresses. The actual numbers come from the address table for your development tool. LS Electric Cnet and Mitsubishi MC are more direct, because you enter the product's memory names such as M0 and D0.

M0 and D0 in this table are product memory names. On LS Electric, M2I, and EasyView HMIs, Cnet addresses are entered as M000 and D000. %MX00000 and %DW0 are the variable names used inside Cnet messages. For other HMIs, check the address format of the selected Cnet driver.

For Mitsubishi MC, use the A-compatible 1C, Format 1 ASCII, Sum Check driver that this SDK supports. The SDK handles BR/BW/WR/WW requests for X/Y/M/D.

Modbus TCP cannot be used with the serial wiring on this page alone. It needs a separate setup with the optional M-ETHER connected to a serial channel of the product. The Arduino IDE and MPINO STUDIO2 examples that follow use serial communication. For the converter and the HMI's IP and port settings, follow the manual for each device.

The serial settings in this guide are MPINO-8A4R-S · RS-232 Serial1 · station 1 · 9600 bps · 8 data bits, no parity, 1 stop bit. Once you have chosen a channel and a protocol, continue with the one development tool you use.

The examples in this guide were checked at the code and settings level. They are not transmission results from a specific HMI model and cable. Check your actual connection by following Checking Operation and Troubleshooting.

Write the program in Arduino IDE →

Write the program in MPINO STUDIO2 →