-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add crc error message #109
Conversation
libs should only print errors to stderr as a last resort. but as it is already used (occasionally), it seems ok. AFAIK, there is currently no better way to get errors out of libsml... (#93 is WIP) So if nobody objects, this should be merged. |
this seems to relate to #103 |
@devZer0: your commit has the username set to the formatting isn't ideal, as it now seems the comment "Workaround for Holley DTZ541" also imho the message could be more helpful. i would write this like:
|
I was thinking whether returning e.g. a "fake" sml reading that maps to obis error codes like S.1.1.16 (device status) S.1.1.7 (failed readout attempts) would make it easier processable. |
we shouldn't be doing such a thing. |
thanks for reminder, i'm totally busy at the moment, so i'm fine if you drop my commit or replace with something other/better |
example message from devZer0/libsml-testing#13
also see discussion there