# Mitsubishi Q-Series PLC

**URL:** <https://discourse.nodered.org/t/mitsubishi-q-series-plc/100668>\
**Category:** Industrial\
**Created:** [27 March 2026 10:51 UTC](https://discourse.nodered.org/t/mitsubishi-q-series-plc/100668 "2026-03-27T10:51:51Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shina](https://avatars.discourse-cdn.com/v4/letter/s/ce73a5/32.png) [@Shina](https://discourse.nodered.org/u/Shina)\
**Post date:** [27 March 2026 10:51 UTC](https://discourse.nodered.org/t/mitsubishi-q-series-plc/100668/1 "2026-03-27T10:51:51Z")

</div>

Please, I am encountering a timeout issue while trying to request data from a Mitsubishi PLC. I have checked every configuration setting on GX Works2 as to why Node-RED isn't able to request data from the Mitsubishi Q-Series PLC, but it isn't working.  
The MC Read node shows " **Ready**", which probably means it is connecting to the PLC, but it then shows **"Timeout"** when I try to read a register. Something is likely blocking this request from Node-RED, and I don't want to make any changes that I’m not well-informed about.  
Here is a screenshot of my **Ethernet Operation Setting** , **Open setting** and **MC Read Node Configuration** window in GX Works2. Any advice on what might be blocking the data request?

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/c/ac74f7d082d59d0eccd981244fd20a0c7ece8af3.jpeg)

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/4/1444b3e6868ac4052149356e1571953eaa552e73.png)

---

<div class="post-metadata">

**Author:** ![Shina](https://avatars.discourse-cdn.com/v4/letter/s/ce73a5/32.png) [@Shina](https://discourse.nodered.org/u/Shina)\
**Post date:** [27 March 2026 10:53 UTC](https://discourse.nodered.org/t/mitsubishi-q-series-plc/100668/2 "2026-03-27T10:53:14Z")

</div>

Here´s the screenshot for the Open Setting

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/b/1b59fb96132135f3c8d477876cbc9e51befc66b8.jpeg)

---

<div class="post-metadata">

**Author:** ![mudwalker](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@mudwalker](https://discourse.nodered.org/u/mudwalker)\
**Post date:** [27 March 2026 11:47 UTC](https://discourse.nodered.org/t/mitsubishi-q-series-plc/100668/3 "2026-03-27T11:47:36Z")

</div>

So far, there is no information regarding Node-RED, this makes it very difficult to help you.

Which version of Node-RED?  
Which added NR Node and Revision/method are you using to ‘talk to’ PLC?  
The NR flow?  
Any Debug messages?

GX Works2 What is this and what part does it play in ‘the System’?

You have to realise that there may not be too many people familiar with the equipment and software you are using. However, there are some people who may be able to help if you help them understand your configuration.

---

<div class="post-metadata">

**Author:** ![Shina](https://avatars.discourse-cdn.com/v4/letter/s/ce73a5/32.png) [@Shina](https://discourse.nodered.org/u/Shina)\
**Post date:** [27 March 2026 12:33 UTC](https://discourse.nodered.org/t/mitsubishi-q-series-plc/100668/4 "2026-03-27T12:33:53Z")

</div>

Version : v4.1.2  
Node; node-red-contrib-mcprotocol version 1.2.1  
No debug messages. GX Works2 is Mitsubishi’s official programming and configuration software for the **PLC**. Attached to this post, is a screenshot of the NR flow.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/c/dc7a9832f479157900856dcea21ab492f80021c2.png)

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [27 March 2026 14:22 UTC](https://discourse.nodered.org/t/mitsubishi-q-series-plc/100668/5 "2026-03-27T14:22:21Z")

</div>

Spot the mismatch:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/6/1619f89031dde4649f802a2c3c837a2ff0f94cdc.jpeg)

As documented in the node, UDP is by far the preferred / stable method.

And knowing Mitsi Q series PLCs as I do, I recommend setting up extra spare ports like 5010, 5011, 5012 for the day the just _stop working_ and you need to reset the PLC. With spare ports setup, you can simply adjust node-red to one of the spare ports.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [26 May 2026 14:22 UTC](https://discourse.nodered.org/t/mitsubishi-q-series-plc/100668/6 "2026-05-26T14:22:52Z")

</div>

Closed on 26 May 2026 14:22 UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
