You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Formatter PR 75 introduces a new downlink packet for Formatter/system health diagnosis.
Assuming this PR is accepted, the GSE could use a parser to display data in these health packets.
Info for implementation
For background, the health packets look like this:
But the 8 byte header is stripped off by the logger. So the data on disk will be the concatenation of 46 byte frames.
The parser will be simple, just digest the bytes of the packet based on the above structure. There are some error tables that use bit flags, so iterate over those and return a dict where the flags are named descriptively. Reference for the flag values is here, in Parameters.h.
One thought: it would be convenient to include a string value name for each system in addition to the bare hex code. That can be done via lookup to systems.json. Include some module-level code at top of this parser file (to run each time it is imported) to try to find and open systems.json, and make a table of name-hex code pairs.
The text was updated successfully, but these errors were encountered:
Why
The Formatter PR 75 introduces a new downlink packet for Formatter/system health diagnosis.
Assuming this PR is accepted, the GSE could use a parser to display data in these health packets.
Info for implementation
For background, the health packets look like this:
But the 8 byte header is stripped off by the logger. So the data on disk will be the concatenation of 46 byte frames.
The parser will be simple, just digest the bytes of the packet based on the above structure. There are some error tables that use bit flags, so iterate over those and return a dict where the flags are named descriptively. Reference for the flag values is here, in Parameters.h.
One thought: it would be convenient to include a string value name for each system in addition to the bare hex code. That can be done via lookup to
systems.json
. Include some module-level code at top of this parser file (to run each time it is imported) to try to find and open systems.json, and make a table of name-hex code pairs.The text was updated successfully, but these errors were encountered: