The RTC timestamp message from the memorator needs to be accommodated by sunlink. To do this, various changes in the DBC were made. Additionally bug fixes and quality of life features were implemented.
Changes:
~The DBC now interprets message 0x751 as being from the MEMORATOR node and it interprets the 8 data bytes a double.~
NOW the DBC message will interpret byte[0] as seconds, byte[1] as minutes, byte[2] as hours, byte[3] as day, byte[4] as month, byte[5] as year. Note that daylight savings is byte[6] but is currently not being displayed as it is not used for any calculations or anything in general. The reason for this is to directly transfer data from the memorator's timeGetDate function and copy it into the RTC type defs in firmware.
gps_fix signal added to TEL diagnostic message in DBC. I removed gps_sync_fail and gps_fail as they are not being used anymore (we do not sync with GPS anymore).
Now there is flexibility in what messages to display in the pretty printed tables in the terminal with the --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.
This required changes in multiple places where I need to use the sendToParser function and as such testing will be required to ensure nothing went wrong
Action Items:
Test MemoratorUploader.py to ensure changes in it did not cause any issues
Purpose:
Changes:
timeGetDatefunction and copy it into the RTC type defs in firmware.--table-on <OPTIONS>flag. An example is--table-on 0x751to display the 0x751 messages only (super useful for quick debugging and checking if certain messages are correctly formatted.sendToParserfunction and as such testing will be required to ensure nothing went wrongAction Items:
MemoratorUploader.pyto ensure changes in it did not cause any issuesDetailed Monday Update Monday Update