Error: Port Not Open

[JorgeAlberto91MS]

I'm submitting a ... (check one with "x")

Support/Advice

• support/advice request => Please do not submit support requests here, instead use the link to our support page, please!

Feature

• ( ) feature request

What is the motivation / use case for changing the behavior?

Simple question to get some hint

• ( ) simple question => please visit the Wiki, the YouTube tutorials and the Info tab by clicking on the node inside Node-RED before
• ( ) help wanted => you read all information and watched relevant YouTube tutorials, but you need more help

Problem

• (x) bug report => please search github for a similar issue or PR and test Modbus problems with the modbus-serial package before submitting
• (x) unexpected behavior => please visit the Wiki before

Current behavior

If only exist Modbus flex-getter on the flows, when a consult to slave device is made, the debug window shows Error: Port not Open

Expected behavior

Minimal reproduction of the problem with instructions

1. Use only flex-getter nodes.
2. Make a consult to slave device.
3. If a "Modbus Read" node is used the problem dissapear.

Your Environment

Please tell us about your environment:

• ( x) I am using just the Node-RED package and got modbus-serial package installed with it
• ( ) I have installed modbus-serial package global from source (using git clone)
• ( ) I have installed modbus-serial as a global package (using npm i -g)

Yes, modbus-serial is the name but it does all, TCP and Serial.
The node-modbus package is just for the Modbus Server node.

• Device :

  • (x) macOS: v
  • (x) Linux: v
  • ( ) Windows: v
  • ( ) Raspbian: v
  • ( ) Other:
    • Name:
    • Version:

• Description of the connecting Modbus system:

  • Name :
  • Version:
  • Vendor :
  • Link : https://

• node-red-contrib-modbus version: vX.X.X

• Node: (v14.x)
  node --version = vX.X.X

[biancode]

Normally there should be no difference. All nodes using the client (config-node) to handle the connection and the connection handling is the work of the client node. Means a read node should get the same problem if you use the same client inside the nodes.

Test with just a flex-reader has no problem with a serial port client in test. The port was not to open, then I set the serial simulator to be ready again and the flex-getter can read well.

flows.json.zip

Maybe you can make a short video to show the problem?
Happy wiring!

tested with v5.22.0

[github-actions]

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.