Open
Conversation
negativ values (2 Bytes), less decode errors
change the whole logic of data decoding to get formatet dates.
|
{ MBUS_CODE::TIME_POINT_DATE , 0x6C , 1, 0}, |
Author
|
Describe what you want to do and read the M-Bus documentation. I do not understand your question. I think the library is no longer supported by the author. If you want to decode, use the MBusinoLib. It is a greatly expanded fork of this library and should now support almost all devices. PS: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The code snipped prevent the libary to come out of step if a DIFE is used. DIFE fields are NOT analyzed, but now you can read out the whole telegram without a failure and get some usefull data. Tested with a Engelmann Sensostar U, which use some DIFE.
One another question:
Why the time points are commented out?