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

Changes to support stored telemetry #814

Closed
ryanatball opened this Issue Jun 21, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@ryanatball
Member

ryanatball commented Jun 21, 2018

  1. New standard PACKET_TIMEFORMATTED and PACKET_TIMESECONDS items on all packets. These will default to the packet received time, but can be overridden in the packet definition files to be derived from other items in a packet. This timestamp will be used as the “actual” time of the packet, so this will become the default for TlmGrapher, DART, etc. RECEIVED_TIMEFORMATTED and RECEIVED_TIMESECONDS will remain the time at which COSMOS first received the packet.

  2. New internal “stored” flag in the COSMOS Packet class. This flag would be set by the interface code or a protocol. For example, it could get set based on the AOS Transfer frame Replay flag. If the stored flag is set it will cause the packet to not affect the CmdTlmServer Current Value Table. It will also be passed as a new parameter to limit responses so they can react differently to stored telemetry if necessary.

  3. New COSMOS log file format that adds a new “flags” field to the header in the file before each packet. The first defined flag will be “stored”. The second defined flag will be “extra” which will indicate the presence of additional extradata in an optional section before the packet data (this will allow for future expansion of arbitrary additional data associated with the packet). The rest of the bits will be reserved.

  4. Updated COSMOS PREIDENTIFIED PROTOCOL with the same change as the log file format (this is the default COSMOS format for streamed packets over Ethernet). This will be the default, but can be disabled to get back to the old format if necessary.

  5. Optional different log writer (and corresponding log file) for stored telemetry. Streams will be intermingled with the new stored flag to help sort out or ignore stored.

  6. New utility to analyze log files for limits violations (just print to STDOUT). This utility will probably grow in functionality in the future, but for now this would be the primary purpose.

@ryanatball

This comment has been minimized.

Member

ryanatball commented Jul 10, 2018

closed by #813

@ryanatball ryanatball closed this Jul 10, 2018

@ryanatball ryanatball added this to the v4.3.0 milestone Aug 30, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment