Updated DBC to contain Memorator Node and RTC Timestamp #87
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.
Purpose:
Changes:
The DBC now interprets message 0x751 as being from the MEMORATOR node and it interprets the 8 data bytes a double.timeGetDate
function and copy it into the RTC type defs in firmware.--table-on <OPTIONS>
flag. An example is--table-on 0x751
to display the 0x751 messages only (super useful for quick debugging and checking if certain messages are correctly formatted.sendToParser
function and as such testing will be required to ensure nothing went wrongAction Items:
MemoratorUploader.py
to ensure changes in it did not cause any issuesDetailed Monday Update
Monday Update