jan iversen
jan iversen
> Does this error flag only get set after all retries have been attempted for cases where no register data was received? The error flag get set when there are...
The error flag get set for unrecoverable error, retry is no an error, that is a perfect normal network situation. ModbusException is, as documented, raised for internal errors, the error...
The 3 distinct ways you refer to, seems to be because you missed to read the comments...exceptionResponse can come anytime from a device, but are a valid response (indicating some...
> Yeah I'm thinking it would be a good idea to unify the error handling so that all error conditions just raise different exceptions, maybe with all error being different...
so to sum it up, the library is at it is, just like other libraries , each with its own set of pros and cons….. You are welcome to change...
The app need to deal with exception response, since it is not an error but tells e.g. that the device is busy.
Please try with version 3.6.9, I remember that we have made changes to this problem.
Closing as no longer relevant (can be reopened if its still a problem with 3.6.9)
I have no suggestions, the serial library is only used in serial transport and there are no other libraries being used. serial_for_url is essential for pymodbus since it allows simulating...
It is easiest to run locally "pytest --cov"