MItsubishi Device Connection for Q-Series PLC

I'm having trouble connecting a Q-series MELSEC PLC to my local 8.1 gateway. I have the Mitsubishi TCP module and I've specified the device's IP, used the default port, and I've given the IP address of my network adapter to be used to connect to it.

Though I can ping the device just fine, my device connection on the gateway isn't connecting to it.

Would anyone happen to know if I'm missing something?

You'll have to actually show us your settings and the details of your network. (You probably are missing something, but we certainly can't see what it might be.)


Fair enough! here's a screenshot from my device connection settings

I'm connected through a small unmanaged switch between my PC and the built in ethernet port on the controller (Q03UDV). I'm not too used to using Mitsubishi PLCs either, which certainly doesn't help me

Looks right. Is your Windows firewall turned off (or set to allow that port through)?

(You don't need to set the local address if there's only one NIC in the subnet.)

it wasn't, but I have now turned the firewall off and still no luck connecting

You've exhausted my knowledge of this protocol. But I would run a brief capture with wireshark just to verify that connection attempts are actually going out (and maybe rejections coming back).

1 Like


Looks like wireshark is seeing some traffic at least

You have to make some configurations in your PLC project, I make the mitsubishi connection several times.

1 Like

The [RST, ACK] is a combo packet from the controller back to Ignition that says "I see you trying to connect but no you cannot." That is a rejection.

Either the protocol is not turned on in the PLC or all available connection slots on that port are already occupied.

1 Like

Have you configured the Open Settings in the Built-in Ethernet port parameters? You will need to set up MC Protocol and specify a port.

1 Like

Okay, I'm all set now I definitely had to set up an SLMP module on the PLC's ethernet config;

I'm going to double check today, but I had left GXWorks2 online with the device after creating that module, so I think it was taking that port and preventing the gateway from connecting. Once I power cycled, Igntion got the port and then I was unable to go online with it in GXWorks, so I'll probably just need to add a second module with another port that my project editor can use

WhatsApp Image 2023-08-11 at 9.00.54 AM
Use the configuration like this, define another port for ignition communicaation.

1 Like