The Alicat driver requires a 10 msec turnaround delay (between reception of one reply and issuing another request.) I have built this delay into Modbus::RTU, but it should be configurable, as it probably depends on the connected devices.
We currently have two drivers based on Modbus::RTU.
The SCoPEx Prop Motor Controller driver
The Alicat Flow Controller driver
Both need to be tested with any changes. Specifically the PropMtr needs to be tested with this hard-coded turnaround time.
Note that this sort of turnaround delay is probably required in any 2-wire RS485 communication, but it is probably not worth restructuring the class hierarchies.
The Alicat driver requires a 10 msec turnaround delay (between reception of one reply and issuing another request.) I have built this delay into Modbus::RTU, but it should be configurable, as it probably depends on the connected devices.
We currently have two drivers based on Modbus::RTU.
Both need to be tested with any changes. Specifically the PropMtr needs to be tested with this hard-coded turnaround time.
Note that this sort of turnaround delay is probably required in any 2-wire RS485 communication, but it is probably not worth restructuring the class hierarchies.