Skip to main content
NN_144621844-Participant
4-Participant
August 10, 2026
Solved

Connect PLC to Kepware through Ethernet Module

  • August 10, 2026
  • 1 reply
  • 46 views

PLC type: Mitsubishi Fx5U

Ethernet Module: USR W630 (Wi-Fi to serial)

The proposal PLC connects directly to Kepware through the Ethernet port and is working fine, and I want to try to connect through the Wi-Fi.

My diagram is PLC - ethernet → USR W630 ))) Wi-Fi → Kepware.

The purpose of the Ethernet module is to work like an Ethernet bridge. I follow this link to set up the PLC: https://industrialmonitordirect.com/blogs/knowledgebase/mitsubishi-fx5u-kepware-slmp-connection-configuration?srsltid=AfmBOop2S78y27FdOU68Ot9BDMhwFP3ieD8WG3x2a4zojZ9K_RskSMqR.

In Kepware, I tried using the Mitsubishi Ethernet method to set up it, but it always shows that the reading is failing. I tried with this tutor. 

The problem is when I tried through Modbus TCP/IP to reading the PLC values. It looks like no problem, and I got the value of the PLC address. 
Does everyone have these problems, or any suggestions for my situation? Thank you first.

Best answer by MRohilla

Greetings ​@NN_14462184,

Since direct FX5U-to-Kepware Ethernet communication is working, the Kepware Mitsubishi driver configuration appears to be correct.

The issue is likely related to the USR-W630 operation mode. The Mitsubishi Ethernet driver requires transparent transport of MC Protocol/SLMP Ethernet packets. If the W630 is configured as a serial tunnel, virtual COM server, or protocol gateway rather than a true Layer 2 Ethernet bridge, Kepware's Mitsubishi Ethernet communications will fail.

The fact that Modbus TCP communication succeeds indicates the Wi-Fi connection itself is operational. We recommend verifying whether the W630 supports transparent Ethernet bridging for Mitsubishi SLMP/MC Protocol traffic and performing a Wireshark capture to confirm that the PLC is receiving and responding to the Mitsubishi packets.

If transparent Ethernet bridging is not supported by the W630, an industrial Wi-Fi Ethernet bridge/access point that operates at Layer 2 would be required.

Regards,
Mohit

1 reply

MRohillaCommunity ManagerAnswer
Support
August 13, 2026

Greetings ​@NN_14462184,

Since direct FX5U-to-Kepware Ethernet communication is working, the Kepware Mitsubishi driver configuration appears to be correct.

The issue is likely related to the USR-W630 operation mode. The Mitsubishi Ethernet driver requires transparent transport of MC Protocol/SLMP Ethernet packets. If the W630 is configured as a serial tunnel, virtual COM server, or protocol gateway rather than a true Layer 2 Ethernet bridge, Kepware's Mitsubishi Ethernet communications will fail.

The fact that Modbus TCP communication succeeds indicates the Wi-Fi connection itself is operational. We recommend verifying whether the W630 supports transparent Ethernet bridging for Mitsubishi SLMP/MC Protocol traffic and performing a Wireshark capture to confirm that the PLC is receiving and responding to the Mitsubishi packets.

If transparent Ethernet bridging is not supported by the W630, an industrial Wi-Fi Ethernet bridge/access point that operates at Layer 2 would be required.

Regards,
Mohit

Terms & ConditionsAccessibility statement