Read & Write nodes not Initializing with Node V17+

Question

Read & Write nodes not Initializing with Node V17+

Patrick-Work opened this issue 2 years ago · 7 comments

Which node-red-contrib-modbus version are you using?

5.23.3 (but same issue with 5.25.0)

What happened?

The Read and write nodes failed to initialize when the Modbus server is on the same Win10 PC after updating from Node V16.16.0 to V18.13.0. External connections still work.

Server

Other/External server

How can this be reproduced?

The attached flow works with Node.js 16.16.0 on Win10 pro. (had to rename to .txt)
I ran node-v18.13.0_x64.msi to install it over V16.

The read and write nodes failed to initialize to the server. Externally everything works as expected.

Then unistalled V18 and reinstalled V16 by MSI and the flow works again.

This also happens when I disable the Node-Red Modbus server and run a Python Modbus server.
And a Flex Getter behaves the same.
IssueWithNodeV18.txt

What did you expect to happen?

I expected the read & write nodes to connect to the Modbus server as they did with Node V16.

Other Information

No response

Answer 1 · 2023-01-15T18:58:16.000Z

@Patrick-Work please, try another port then 502 or try to start node-red as or with administrator rights as in Linux. Well known ports get more and more protected from newer frameworks, sdks and operating systems, which means you need to be admin or privileged user in the system to use well known ports (like 1-1024). Did you check node v18 for release notes in that point?

Answer 2 · 2023-01-15T19:10:23.000Z

I'll give that a try, but the ports are open externally. Port 502 works with V18 when an external server is read. Also, I'll try using 127.0.01 instead of the computer name for the read nodes.

Answer 3 · 2023-01-15T19:41:33.000Z

Yes, it's a port issue. Disabling the firewall fixes this issue. And using another port also does so. Thank you,

Answer 4 · 2023-01-15T19:56:45.000Z

@Patrick-Work you're welcome!

Answer 5 · 2023-01-16T19:40:59.000Z

Could someone guide me in how to find this issue? I created a simple Node.js server and client on the same PC using jsmodbus and they can communicate internally and externally using port 502. I tried to repeat the firewall check and it is not behaving the same as last night when I was trying multiple ports on my company network. Not sure if I triggered anything.

I have to re-open this issue as it is not a firewall issue. I can reach the port externally, unless I use the server with this package. Then it does not work.

Any guidance would be great! I have tried other modules. One worked but cannot handle more than one read or write node.

Thank you in advance,

Answer 6 · 2023-01-16T22:49:13.000Z

I ran Node-Red in debug and below is what I saw with V16 vs V18. I xxx'ed out the PC info. There seems to be another difference. The server's IP has to be 0.0.0.0 for the external connections. This was not the case with V16 as seen below.
Any advice to identify the issue is greatly appreciated. Thank you,

With Node V16:
16 Jan 17:18:00 - [info] Started modified flows
contribModbus:server Modbus Server listening on modbus://MachineName:502 +9m
contribModbus:server Modbus Server client connection +2s
contribModbus:server Modbus Server client to {"address":"10.xxx.xxx.xxx","family":"IPv4","port":502} from 10.yyy.yyy.yyy 55242 +1ms

With Node V18:
16 Jan 17:30:49 - [info] Starting flows
contribModbus:queue:core queue serial lock command node name: undefined id: 66540599b3c16b87 +0ms
contribModbus:queue:core queue serial lock command node name: undefined id: 781b141420ae0a61 +2ms
contribModbus:queue:core queue serial lock command node name: undefined id: 33d3fce76d1519c6 +1ms
16 Jan 17:30:49 - [info] Started flows
contribModbus:server Modbus Server listening on modbus://MachineName:502 +0ms
contribModbus:queue:core queue serial unlock command node name: undefined id: 781b141420ae0a61 +22s
contribModbus:queue:core queue serial lock command node name: undefined id: 781b141420ae0a61 +1ms
contribModbus:queue:core queue serial unlock command node name: undefined id: 781b141420ae0a61 +25s
contribModbus:queue:core queue serial lock command node name: undefined id: 781b141420ae0a61 +0ms

Also:
16 Jan 17:34:45 - [info] Started flows
contribModbus:server Modbus Server listening on modbus://0.0.0.0:502 +23s
contribModbus:queue:core queue serial unlock command node name: undefined id: 781b141420ae0a61 +3s
contribModbus:queue:core queue serial lock command node name: undefined id: 781b141420ae0a61 +1ms
contribModbus:server Modbus Server client connection +3s
contribModbus:server Modbus Server client to {"address":"10.xxx.xxx.xxx","family":"IPv4","port":502} from 10.yyy.yyy.yyy 55691 +2ms
contribModbus:queue:core queue serial unlock command node name: undefined id: 781b141420ae0a61 +6s
contribModbus:queue:core queue serial lock command node name: undefined id: 781b141420ae0a61 +2ms
contribModbus:queue:core queue serial unlock command node name: undefined id: 781b141420ae0a61 +6s
contribModbus:queue:core queue serial lock command node name: undefined id: 781b141420ae0a61 +1ms

Lastly:
16 Jan 17:36:28 - [info] Started flows
contribModbus:server Modbus Server listening on modbus://127.0.0.1:502 +58s
contribModbus:queue:core queue serial unlock command node name: undefined id: 781b141420ae0a61 +3s
contribModbus:queue:core queue serial lock command node name: undefined id: 781b141420ae0a61 +1ms
contribModbus:queue:core queue serial unlock command node name: undefined id: 781b141420ae0a61 +6s
contribModbus:queue:core queue serial lock command node name: undefined id: 781b141420ae0a61 +1ms

Answer 7 · 2023-03-20T01:58:24.000Z

This issue is stale because it has been open 60 days with no activity. It will be closed in 30 days, but can be saved by removing the stale label or commenting.