Help: new install is not working

[Tonio16]

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

5.30.0

What happened?

Hello

I was using node-red and your node-red-contrib-modbus on a old Pi to read/write the data on ventillation system, Drexel aerosmart L. It was working since years.

I move to a LXC on proxmox with node-red and so I installed the last version of the node, 5.30.0.
On this new install, I have always the same error messages. I was stupide enough to update my pi and now it's also not working on. I don't understand what I am doing wrong there.

"Client -> fsm broken state after failed Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1"
and
"Client -> fsm failed state after sending Get More About It By Logging Serial@/dev/ttyUSB0:19200bit/s default !

after a while I have:
"Error: Port Not Open"
Client -> fsm init state after reconnecting Serial@/dev/ttyUSB0:19200bit/s default Unit-Id: 1

Here my settings

And the flow

I tried this:
#436 (comment)
It was making my modbus-flex-getter to initialize in an ending loop.

I tried from my laptop with modbus doctor: ok
From another proxmox VM and a different software (jeedom, plugin mymodbus), it's also working.

Server

Modbus-Server Node

How can this be reproduced?

Update from a quite old node version (2020?) to the last version

What did you expect to happen?

No change of behavior within the node versions.

Other Information

My ventilation system is based on a RS232 Modbus RTU.
It's uint32 or int32. I have to make a different request for each register and to wait at least 300ms between each enquery. I expect that the new queueing system is of interest in this case.

Tx

Antoine