Node-Red Uncaught Exception due Modbus Server node.

I’m submitting a … (check one with “x”)

Problem

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

Current behavior

Uncaught Exception on Node-RED. After a lost connection from Modbus master, the Modbus Server node shows an error that makes Node-Red to forced stop.

Expected behavior

After a lost connection from Modbus master, the Modbus Server must show the connection error but Node-Red should remain active.

Minimal reproduction of the problem with instructions

1. Load data into Modbus Server Buffer.
2. Start a Modbus Request from another device.
3. Start / Stop the connection from remote device.

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 :

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

• Description of the connecting Modbus system:

  • Name : Modbus Simulator
  • Version : 3.53
  • Vendor : Calta Computer Systems Limited
  • Link : https://

• node-red-contrib-modbus version: v5.13.3

• Node: (min. 10.x) node --version = v12.19.1

[R-LopezV]

Redshift1: As a workaround you can use an external Modbus/TCP server, and writing the necessary values using Node-Red to it

Yeah, we’re working on that right now, thanks for the idea.

@biancode I hope all of you have had a better year so far. I appreciate all of you working on this in spite of your personal situations.

biancode: it is Open-Source and the community could contribute or users could sponsor for fixing issues faster 😉 It will be fixed with the next v5.22+ - but keep in mind, then the flow should handle the error state of the node

To be honest I’m not super savvy on JS, but I could give it a try… As for the flow handling the error, it’s more than enough personally. That would make fixing my mistakes on the node’s config much faster.

[biancode]

Yes - two years - the last two years were and are not easy with all the issues from our real life. @R-LopezV it is Open-Source and the community could contribute or users could sponsor for fixing issues faster 😉

It will be fixed with the next v5.22+ - but keep in mind, then the flow should handle the error state of the node