# Mitsubishi MC Protocol Read Node Not connected or timeout

**URL:** <https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733>\
**Category:** Industrial\
**Created:** [11 March 2022 20:56 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733 "2022-03-11T20:56:15Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![jts450](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@jts450](https://discourse.nodered.org/u/jts450)\
**Post date:** [11 March 2022 20:56 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/1 "2022-03-11T20:56:15Z")

</div>

I am not able to establish communication to Mitsubishi PLC. here are some of the setup screens on PLC and Read node. I have tried to change some of the node setting and I am yet to establish connection. Any Idea for me to try?

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/b/8ba90eb05f56602331105dea8190d6322da437dd.png)

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/a/0/a0fedd86b4ae2115d304e5f7426a5aa9b23fc42f.png)

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/7/07b8ea1057b43053e14fd8eda2d7e5422e2f39d0.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:** [11 March 2022 21:34 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/2 "2022-03-11T21:34:55Z")

</div>

Install node-red-node-ping, can your node-red ping the plc?

Have you turned the PLC off/on after changing settings?

How have you set the ports on the plc? (Show screenshot)

---

<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:** [11 March 2022 21:35 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/3 "2022-03-11T21:35:52Z")

</div>

Here is a thread that might help

> [@Mitsubishi Q02CPU comm. through Q71E71-100](https://discourse.nodered.org/t/mitsubishi-q02cpu-comm-through-q71e71-100/50842):
>
> Hi! I am currently trying to read a Q02CPUs tags through a Q71E71-100 ethernet card that was installed into the Mitsubishi PLC. I am trying to access the Ethernet card through the default open UDP ports 5000/5001 or the default open TCP ports 5002 which my mitsubishi experienced colleague recommended. Connection with IPs etc are all OK. I've seen this post: [Q-series [solution]](https://discourse.nodered.org/t/mitsubishi-q-series-node-red-help/33337/5) And tried to verify possible errors with it but no success, I am getting a "Error: timeout" when trying to poll and r…

---

<div class="post-metadata">

**Author:** ![jts450](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@jts450](https://discourse.nodered.org/u/jts450)\
**Post date:** [11 March 2022 21:57 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/4 "2022-03-11T21:57:31Z")

</div>

Looks like I can ping. I was able to ping in CMD

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/5/1/51ff7f50393e329b05b0a8e7ba06e62c66346006.png)

We did not turn it off yet. will try that

---

<div class="post-metadata">

**Author:** ![jts450](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@jts450](https://discourse.nodered.org/u/jts450)\
**Post date:** [11 March 2022 22:17 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/5 "2022-03-11T22:17:23Z")

</div>

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/b/a/ba093552f104878d0558279ccd7fe65d58a84157.png)  
Ok got it working by changing built in ethernet port open settings

---

<div class="post-metadata">

**Author:** ![jts450](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@jts450](https://discourse.nodered.org/u/jts450)\
**Post date:** [11 March 2022 22:18 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/6 "2022-03-11T22:18:36Z")

</div>

From Subject Received Size Categories   
Jason Meyer 2:18 PM 114 KB

---

<div class="post-metadata">

**Author:** ![jts450](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@jts450](https://discourse.nodered.org/u/jts450)\
**Post date:** [11 March 2022 22:19 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/7 "2022-03-11T22:19:16Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![jts450](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@jts450](https://discourse.nodered.org/u/jts450)\
**Post date:** [11 March 2022 22:54 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/8 "2022-03-11T22:54:01Z")

</div>

using the read node I though i would be able to monitor this PLC value for whenever it changes and not have to use an Inject to see the value thru a debug node? I realize this may be a basic Node-Red question...

[  
{  
"id": "08a482e7a2022352",  
"type": "switch",  
"z": "c409bd4bcb4231c2",  
"name": "=500",  
"property": "payload",  
"propertyType": "msg",  
"rules": [  
{  
"t": "eq",  
"v": "500",  
"vt": "str"  
}  
],  
"checkall": "true",  
"repair": false,  
"outputs": 1,  
"x": 350,  
"y": 1420,  
"wires": [  
[  
"4771c477e05effe7"  
]  
]  
},  
{  
"id": "944050346ac58354",  
"type": "MC Read",  
"z": "c409bd4bcb4231c2",  
"name": "D03804",  
"topic": "",  
"connection": "8bf9ce709d0bac70",  
"address": "D03804",  
"addressType": "msg",  
"outputFormat": "1",  
"errorHandling": "throw",  
"outputs": 1,  
"x": 160,  
"y": 1420,  
"wires": [  
[  
"08a482e7a2022352"  
]  
]  
},  
{  
"id": "4771c477e05effe7",  
"type": "debug",  
"z": "c409bd4bcb4231c2",  
"name": "",  
"active": true,  
"tosidebar": true,  
"console": false,  
"tostatus": false,  
"complete": "payload",  
"targetType": "msg",  
"statusVal": "",  
"statusType": "auto",  
"x": 570,  
"y": 1420,  
"wires":   
},  
{  
"id": "8bf9ce709d0bac70",  
"type": "MC Protocol Connection",  
"name": "PLC1",  
"host": "192.168.3.39",  
"port": "3001",  
"protocol": "UDP",  
"frame": "3E",  
"plcType": "Q",  
"ascii": false,  
"PLCStation": "",  
"PCStation": "",  
"PLCModuleNo": "",  
"network": "",  
"octalInputOutput": false,  
"timeout": "1000"  
}  
]

---

<div class="post-metadata">

**Author:** ![jts450](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@jts450](https://discourse.nodered.org/u/jts450)\
**Post date:** [11 March 2022 22:54 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/9 "2022-03-11T22:54:47Z")

</div>

[flows.json](https://discourse.nodered.org/uploads/short-url/9gecHBASLsyWzh7s14EVBON3YjF.json) (1.8 KB)

---

<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:** [11 March 2022 22:57 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/10 "2022-03-11T22:57:19Z")

</div>

You can use the rbe/filter node to differentiate changes.

My advice it to program the plc to out all values of interest into 1 contiguous area (e.g D1000-D1199) and read all values at once then use buffer-parser to convert the values into book/string/float/int. That way, there are less requests and all data is concurrent.

---

<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:** [11 March 2022 22:57 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/11 "2022-03-11T22:57:37Z")

</div>

In order to make code readable and usable it is necessary to surround your code with three backticks (also known as a left quote or backquote `````)

````auto
``` 
   code goes here 
```

````

You can edit and correct your post by clicking the pencil ✏ icon.

See this post for more details - [How to share code or flow json](https://discourse.nodered.org/t/how-to-share-code-or-flow-json/506)

---

<div class="post-metadata">

**Author:** ![jts450](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@jts450](https://discourse.nodered.org/u/jts450)\
**Post date:** [11 March 2022 23:16 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/12 "2022-03-11T23:16:55Z")

</div>

ok but it does not report on change of value in the debug still. do i need to put something in front of the MC read node to trigger on change?

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/2/3/23f3c2b41711209030078728cc70dc2567cc351f.png)

---

<div class="post-metadata">

**Author:** ![jts450](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@jts450](https://discourse.nodered.org/u/jts450)\
**Post date:** [11 March 2022 23:22 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/13 "2022-03-11T23:22:03Z")

</div>

```auto
[
    {
        "id": "08a482e7a2022352",
        "type": "switch",
        "z": "c409bd4bcb4231c2",
        "name": "=500",
        "property": "payload",
        "propertyType": "msg",
        "rules": [
            {
                "t": "eq",
                "v": "500",
                "vt": "str"
            }
        ],
        "checkall": "false",
        "repair": false,
        "outputs": 1,
        "x": 390,
        "y": 1540,
        "wires": [
            [
                "4771c477e05effe7"
            ]
        ]
    },
    {
        "id": "944050346ac58354",
        "type": "MC Read",
        "z": "c409bd4bcb4231c2",
        "name": "D03804",
        "topic": "",
        "connection": "8bf9ce709d0bac70",
        "address": "D03804",
        "addressType": "msg",
        "outputFormat": "1",
        "errorHandling": "throw",
        "outputs": 1,
        "x": 200,
        "y": 1540,
        "wires": [
            [
                "08a482e7a2022352"
            ]
        ]
    },
    {
        "id": "4771c477e05effe7",
        "type": "debug",
        "z": "c409bd4bcb4231c2",
        "name": "",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "payload",
        "targetType": "msg",
        "statusVal": "",
        "statusType": "auto",
        "x": 610,
        "y": 1540,
        "wires": []
    },
    {
        "id": "c51acb6bb427d696",
        "type": "rbe",
        "z": "c409bd4bcb4231c2",
        "name": "",
        "func": "rbe",
        "gap": "",
        "start": "",
        "inout": "out",
        "septopics": true,
        "property": "payload",
        "topi": "topic",
        "x": 370,
        "y": 1620,
        "wires": [
            [
                "8b043a0ebe68d63a"
            ]
        ]
    },
    {
        "id": "43737051c3b45b63",
        "type": "MC Read",
        "z": "c409bd4bcb4231c2",
        "name": "D03804",
        "topic": "",
        "connection": "8bf9ce709d0bac70",
        "address": "D03804",
        "addressType": "msg",
        "outputFormat": "0",
        "errorHandling": "throw",
        "outputs": 1,
        "x": 200,
        "y": 1620,
        "wires": [
            [
                "c51acb6bb427d696"
            ]
        ]
    },
    {
        "id": "8b043a0ebe68d63a",
        "type": "debug",
        "z": "c409bd4bcb4231c2",
        "name": "",
        "active": true,
        "tosidebar": true,
        "console": false,
        "tostatus": false,
        "complete": "payload",
        "targetType": "msg",
        "statusVal": "",
        "statusType": "auto",
        "x": 610,
        "y": 1620,
        "wires": []
    },
    {
        "id": "8bf9ce709d0bac70",
        "type": "MC Protocol Connection",
        "name": "PLC1",
        "host": "192.168.3.39",
        "port": "3001",
        "protocol": "UDP",
        "frame": "3E",
        "plcType": "Q",
        "ascii": false,
        "PLCStation": "",
        "PCStation": "",
        "PLCModuleNo": "",
        "network": "",
        "octalInputOutput": false,
        "timeout": "1000"
    }
]

```

---

<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:** [11 March 2022 23:47 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/14 "2022-03-11T23:47:16Z")

</div>

Yes. The MC protocol node does not poll the plc. You will need to use an inject set to repeat every X seconds.

---

<div class="post-metadata">

**Author:** ![jts450](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@jts450](https://discourse.nodered.org/u/jts450)\
**Post date:** [14 March 2022 14:59 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/15 "2022-03-14T14:59:52Z")

</div>

hmm... ok for my application I kind of need to see the update faster than every second. To your knowledge is there another Open System protocol that polls with a Mitsubishi PLC or can I use another node in front of the MC read node besides an Inject since it seems I am limited to 1 second?

---

<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:** [14 March 2022 15:28 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/16 "2022-03-14T15:28:24Z")

</div>

> [@jts450](#):
>
> for my application I kind of need to see the update faster than every second

Why exactly? Please explain.

> [@jts450](#):
>
> To your knowledge is there another Open System protocol that polls with a Mitsubishi PLC

Not on node-red.

> [@jts450](#):
>
> or can I use another node in front of the MC read node besides an Inject since it seems I am limited to 1 second

Yes, & I will tell you after you answer the first question (I dont mean to question your capabilities but sometimes people believe they MUST poll faster than 1 sec to catch something like a button press - but a simple ladder mod can be used instead)

---

<div class="post-metadata">

**Author:** ![jts450](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@jts450](https://discourse.nodered.org/u/jts450)\
**Post date:** [14 March 2022 16:40 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/17 "2022-03-14T16:40:43Z")

</div>

> [@Steve-Mcl](#):
>
> Why exactly? Please explain.

In the PLC a bit turns on about 2 times a second in which I then need to trigger my scanner to turn on for 200-400ms

---

<div class="post-metadata">

**Author:** ![jts450](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@jts450](https://discourse.nodered.org/u/jts450)\
**Post date:** [14 March 2022 16:45 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/18 "2022-03-14T16:45:00Z")

</div>

General Question: in your opinion is Nod-Red an reliable application in an industrial environment? I mean as long as the PC hardware chosen or setup is.

---

<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:** [14 March 2022 17:03 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/19 "2022-03-14T17:03:33Z")

</div>

> [@jts450](#):
>
> General Question: in your opinion is Nod-Red an reliable application in an industrial environment?

Yes it is reliable. Is/Was for me. But you have to realise network delays, non deterministic nature of Ethernet & the fact that mitsi Ethernet comms are (in my experience) notoriously unreliable (ok, so TCP isnt great but the UDP comms were a bit more stable)

> [@jts450](#):
>
> PLC a bit turns on about 2 times a second in which I then need to trigger my scanner to turn on for 200-400ms

This sounds like it is more suited to field network integration.

- What is "the scanner"?
- What field networks does the scanner support?
- What do you do with the scanner results? Process them in node-red?
- How "repeatable" / accurate is the timing? are you talking about some moving production line?
  - I ask because MC Protocol over ethernet is non deterministic. Additionally, in Q series (and below) the network stack is part of the overall PLC SCAN - meaning if your ladder instructions cause a delay, the COMMS will not be services until after the ladder scan (meaning jitter/variation in timing)

  

* * *
  

PS, the answer to the other question is: you can enter 0.25 into the inject repeat to achieve a 250ms pulse. NOTE: you will need to use an RBE/filter node to check that the value has changed otherwise you would trigger this "scanner" repeatedly.

---

<div class="post-metadata">

**Author:** ![jts450](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@jts450](https://discourse.nodered.org/u/jts450)\
**Post date:** [14 March 2022 18:38 UTC](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733/20 "2022-03-14T18:38:10Z")

</div>

[Matrix 220 Data Sheet \_ English A4 (1).pdf](https://discourse.nodered.org/uploads/short-url/p5aVMO6XsPXEwqPjFc6ZgZEpNFt.pdf) (1.6 MB)  
This should answer the first 2 questions

-For the scanner results we are reading them into node-red thru TCP/IP and then having Node-Red write to an MS Sql server instance on a server in addition to writing to a locally installed MS Sql server instance in the event the network or server goes down we can sync the databeses.

-Repeatable.. The product moves thru the machine at a repeatable rate but sometimes there is no product in that position so the machine does not trigger a scan.

[Next page](https://discourse.nodered.org/t/mitsubishi-mc-protocol-read-node-not-connected-or-timeout/59733.md?page=2)