Failure to connect with devices（Ethernet connection）

Please revise following settings.

[Port Setting]

• Protocol：Change according to whether a communication protocol with a PLC is UDP / IP or TCP /IP.
• Adapter IP Address：Make sure it is localhost、or IP address of PC.
• Adapter port number:
  Make sure it is 0（Auto assignment）
  Specify that number, if a port number to be connected on a PLC side is fixed.
  We recommend 0 (Auto assignment) when using TCP/IP.
• Device address：
  Make sure that whether PING command successfully executed for this IP address. [PING test] can be used only when an OPC server is launched as "Execute as administrator" in a right-click menu under UAC-enabled situation. If you will not launch that way, please check with using Windows command prompt.。
• Device port address：Specify a port number on a PLC side. You need to set an open configuration of port depending on a PLC.

[Device setting]

• Please refer to User’s Guide (PLC setting) because settings will be changed depending on a connecting device.

​【Notes】

• When PING command successfully executed, but the communications fails, the port number may not be correct one. You need to verify an open setting of PLC and configure correctly.
• In TCP / IP connection, models which can be configured to check whether it is on keep alive on a PLC side, be sure to set it is so. If it is not on keep alive setting, communications may not be restored after disconnection.
• Please leave network setting 0, PC number 255, unit station number 0 as default network setting in case of MELSEC Ethernet connection's own station access (Direct connection of Ethernet network)
• Please reset a PLC after writing parameters, because there is a possibility that parameters are not reflected in a PLC.

<Still cannot to connect>

Cause of connection failure can be various factors such as hardware and software.

If you cannot connect even after checking the user's guide, please contact our Technical support after checking a product version, a device configuration, a presence or absence of the communication log.

Since it may be difficult to investigate causes if there is no connection log, we recommend that you take the setting to automatically save communication logs.

 Please refer to User’s guide for settings.