Join GitHub today
modbus_report_slave_id doesn't understand exception responses #27
When the response comes in, it somehow ends up in the regular checks in check_confirmation, instead of the path for exception replies. This results in a message in the debug about an unexpected function, when it should be properly decoding teh exception like, "function not supported"
(Testing with a device that doesn't support the slave id function)