# MItsubishi Device Connection for Q-Series PLC

**URL:** <https://forum.inductiveautomation.com/t/mitsubishi-device-connection-for-q-series-plc/77713>\
**Category:** General Discussion\
**Created:** [August 10, 2023, 6:35pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-device-connection-for-q-series-plc/77713 "2023-08-10T18:35:01Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tucker\_Gustavesen](https://avatars.discourse-cdn.com/v4/letter/t/43a26b/32.png) [@Tucker\_Gustavesen](https://forum.inductiveautomation.com/u/Tucker_Gustavesen)\
**Post date:** [August 10, 2023, 6:35pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-device-connection-for-q-series-plc/77713/1 "2023-08-10T18:35:01Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 10, 2023, 6:39pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-device-connection-for-q-series-plc/77713/2 "2023-08-10T18:39:39Z")

</div>

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.)

---

<div class="post-metadata">

**Author:** ![Tucker\_Gustavesen](https://avatars.discourse-cdn.com/v4/letter/t/43a26b/32.png) [@Tucker\_Gustavesen](https://forum.inductiveautomation.com/u/Tucker_Gustavesen)\
**Post date:** [August 10, 2023, 6:50pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-device-connection-for-q-series-plc/77713/3 "2023-08-10T18:50:00Z")

</div>

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/6/e61a2a22e0bc4b950f7606be18387c6698f2c600.png)  
Fair enough! here's a screenshot from my device connection settings

---

<div class="post-metadata">

**Author:** ![Tucker\_Gustavesen](https://avatars.discourse-cdn.com/v4/letter/t/43a26b/32.png) [@Tucker\_Gustavesen](https://forum.inductiveautomation.com/u/Tucker_Gustavesen)\
**Post date:** [August 10, 2023, 6:52pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-device-connection-for-q-series-plc/77713/4 "2023-08-10T18:52:19Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 10, 2023, 6:56pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-device-connection-for-q-series-plc/77713/5 "2023-08-10T18:56:16Z")

</div>

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.)

---

<div class="post-metadata">

**Author:** ![Tucker\_Gustavesen](https://avatars.discourse-cdn.com/v4/letter/t/43a26b/32.png) [@Tucker\_Gustavesen](https://forum.inductiveautomation.com/u/Tucker_Gustavesen)\
**Post date:** [August 10, 2023, 7:01pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-device-connection-for-q-series-plc/77713/6 "2023-08-10T19:01:33Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 10, 2023, 7:19pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-device-connection-for-q-series-plc/77713/7 "2023-08-10T19:19:12Z")

</div>

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).

---

<div class="post-metadata">

**Author:** ![Tucker\_Gustavesen](https://avatars.discourse-cdn.com/v4/letter/t/43a26b/32.png) [@Tucker\_Gustavesen](https://forum.inductiveautomation.com/u/Tucker_Gustavesen)\
**Post date:** [August 10, 2023, 10:17pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-device-connection-for-q-series-plc/77713/8 "2023-08-10T22:17:04Z")

</div>

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/2/72a4675908a04ade16457122de6d42adf92d2e5a.png)  
Looks like wireshark is seeing some traffic at least

---

<div class="post-metadata">

**Author:** ![jcjc74836](https://avatars.discourse-cdn.com/v4/letter/j/439d5e/32.png) [@jcjc74836](https://forum.inductiveautomation.com/u/jcjc74836)\
**Post date:** [August 10, 2023, 10:53pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-device-connection-for-q-series-plc/77713/9 "2023-08-10T22:53:31Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 11, 2023, 12:21am UTC](https://forum.inductiveautomation.com/t/mitsubishi-device-connection-for-q-series-plc/77713/10 "2023-08-11T00:21:57Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![william.bowen](https://avatars.discourse-cdn.com/v4/letter/w/8c91f0/32.png) [@william.bowen](https://forum.inductiveautomation.com/u/william.bowen)\
**Post date:** [August 11, 2023, 6:21am UTC](https://forum.inductiveautomation.com/t/mitsubishi-device-connection-for-q-series-plc/77713/11 "2023-08-11T06:21:10Z")

</div>

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.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/d/5d9901559a73a5c09cd47590af2aa2ff6980c56a.png)

---

<div class="post-metadata">

**Author:** ![Tucker\_Gustavesen](https://avatars.discourse-cdn.com/v4/letter/t/43a26b/32.png) [@Tucker\_Gustavesen](https://forum.inductiveautomation.com/u/Tucker_Gustavesen)\
**Post date:** [August 11, 2023, 12:35pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-device-connection-for-q-series-plc/77713/12 "2023-08-11T12:35:00Z")

</div>

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

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/b/4b6e26e375236a0487c59e8ebc85597d0d8d3392.png)

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

---

<div class="post-metadata">

**Author:** ![jcjc74836](https://avatars.discourse-cdn.com/v4/letter/j/439d5e/32.png) [@jcjc74836](https://forum.inductiveautomation.com/u/jcjc74836)\
**Post date:** [August 11, 2023, 2:03pm UTC](https://forum.inductiveautomation.com/t/mitsubishi-device-connection-for-q-series-plc/77713/13 "2023-08-11T14:03:29Z")

</div>

![WhatsApp Image 2023-08-11 at 9.00.54 AM](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/6/067dee7f852cece963d3314042e9008f8bbb3c21.jpeg)  
Use the configuration like this, define another port for ignition communicaation.
