You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running the rtuslave_example.py at 19200 bps to test a modbus master. Everything functions nicely except that periodically the RTU Server/slave interprets the first byte (slave id) as a complete packet and then complains about a CRC error.
I was able to patch this issue for my own testing by adding a time.sleep(0.001) in the _do_run function after the first blocking serial read (line 271) in modbus_rtu.py. However this function should probably be refactored so that it waits for another byte before it starts to parse a response.
I don't have the time to fix this myself but hopefully this can get patched or it will help someone with a similar problem.
Regards, Dominique
The text was updated successfully, but these errors were encountered:
Hello,
I am running the rtuslave_example.py at 19200 bps to test a modbus master. Everything functions nicely except that periodically the RTU Server/slave interprets the first byte (slave id) as a complete packet and then complains about a CRC error.
I was able to patch this issue for my own testing by adding a time.sleep(0.001) in the _do_run function after the first blocking serial read (line 271) in modbus_rtu.py. However this function should probably be refactored so that it waits for another byte before it starts to parse a response.
I don't have the time to fix this myself but hopefully this can get patched or it will help someone with a similar problem.
Regards, Dominique
The text was updated successfully, but these errors were encountered: