I changed to UDP From TCP for Mitsubishi PLC Fx3u but did not work in NodeRED
as per the previous Topic @Steve-Mcl told me to Change it from TCP to UDP and i did but its not working now
What do you see? how did you setup PLC? are node-red server and PLC on same network?
I just see timeout error in nodeRED and both are in same network both are pinging
@Steve-Mcl
{
"POLLING": "ENABLED",
"payload": null,
"_msgid": "e722627803c06cc2",
"_event": "node:30608999c586eb0a",
"topic": "D40,9",
"_linkSource": [
{
"id": "0530ddbb9d9908a47f8fc8a21d81",
"node": "93091528e94e02c3"
}
],
"mcReadDetails": {
"request": {
"outputFormat": "Array",
"address": "D40,9",
"timeStamp": 1761575618296
},
"response": {
"isGood": false,
"quality": [
"Unknown",
"Unknown",
"Unknown",
"Unknown",
"Unknown",
"Unknown",
"Unknown",
"Unknown",
"Unknown"
],
"TAG": "D40,9",
"addr": "D40,9",
"timeTaken": 4501,
"timeStamp": 1761575622797,
"value": [
0,
0,
0,
0,
0,
0,
0,
0,
0
],
"valueType": "INT",
"deviceCode": "D",
"deviceCodeNotation": "Decimal",
"deviceCodeType": "WORD",
"digitSpec": "",
"dataType": "INT",
"dataTypeByteLength": 2,
"deviceNo": 40,
"problem": true
},
"error": true
},
"error": {
"message": "Error",
"source": {
"id": "05cd47ebd2cf785f",
"type": "MC Read",
"name": "",
"count": 1
},
"stack": "Error\n at handleError (/home/omsoftware/.node-red/node_modules/node-red-contrib-mcprotocol/nodes/read.js:74:17)\n at PLCItem.myReply [as cb] (/home/omsoftware/.node-red/node_modules/node-red-contrib-mcprotocol/nodes/read.js:207:11)\n at MCProtocol.readResponse (/home/omsoftware/.node-red/node_modules/node-red-contrib-mcprotocol/mcprotocol/mcprotocol.js:1797:14)\n at MCProtocol.packetTimeout (/home/omsoftware/.node-red/node_modules/node-red-contrib-mcprotocol/mcprotocol/mcprotocol.js:465:8)\n at Timeout.<anonymous> (/home/omsoftware/.node-red/node_modules/node-red-contrib-mcprotocol/mcprotocol/mcprotocol.js:1383:24)\n at listOnTimeout (node:internal/timers:583:11)\n at process.processTimers (node:internal/timers:519:7)"
}
}
@Steve-Mcl ,
Can you Please Tell me what i am missing. or am i wrong
Not without information
Can you show me the settings you have made in the config node?
@Steve-Mcl ,
here is the config
Test1:
- Try changing the PLC to 5500 / 5500
- power off / on the PLC (to apply new settings)
- Change the config to match
@Steve-Mcl ,
Hi there i dont know whether it will work on that or not are your sure about the solution you gave because before i have using TCP with the above config it was working
No. That's why I called it Test1
If it does not work I will probably provide a Test2
FYI: I have not used that particular PLC model, I am not familiar with your network hardware, routing, settings, etc, etc, etc. In short, I dont have enough details (nor do I have enough time to ask for and wait for answers) so I am taking a logic step-wise approach and asking you to "try stuff".
Are they on the same network segment? IE connected to the same router, not through another router or wifi mesh or similar.
@Colin ,
Yes there is a special router for the plc and device we separated the router for them and they are in same network .
What details are required more please specify me so i can try to provide you with that.
Please try the suggestion first.
If that doesn't work, we will explore other ideas.
I don't fully understand that sentence, but if there are two routers between you and the plc then udp may not get through, even if logically you are on the same network.
@Colin ,
In simple word there is only 1 router for plc and device
It's not that then.
@Steve-Mcl and @Colin,
I have updated to ur port and tried but still not worked timeout and also i tried port 5000
which screenshot is below
i have got updated in nodered but still i cant use it
Bear in mind that i know zero about industrial PLCs.
Steve suggested using port 5500 both in the PLC config and in Node-red. Did you try this?
To my untutored eyes it looks like the PLC is sending data to port 5001 while Node-red is listening on port 5000?
1 Like
avoid 5000 and 5001
5000 is often the UDP default for protocols that support Auto Open UDP Port features, or when configured for certain SCADA systems/HMIs.
|5001 is often the default TCP for communication like SCADA, HMIs, or other clients connecting to the PLC's dedicated Ethernet module (e.g., QJ71E71).
