-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
LAD Table does not show string telemetry items #3323
Comments
@trgarvey Hi! It sounds like it might be a telemetry metadata issue. Are you seeing this issue with the Open MCT-YAMCS adapter? |
Yes, it happens with the YAMCS adapter, so it could be specific to that. However, the items not displayed in the LAD table are consistently identified as “telemetry strings” as opposed to “telemetry points”, and a standard “telemetry table” will interpret those same points as strings correctly. In the example below, “CCSDS Type” should be “false” as well as “CCSDSSecH”. Both display correctly in a telemetry table.
[cid:[email protected]]
Tom Garvey | Mission Operations Lead
Astrobotic Technology, Inc.
1016 N.Lincoln Avenue
Pittsburgh, PA 15233
www.astrobotic.com<http://www.astrobotic.com/>
From: Andrew Henry <[email protected]>
Sent: Thursday, September 24, 2020 6:16 PM
To: nasa/openmct <[email protected]>
Cc: Tom Garvey <[email protected]>; Mention <[email protected]>
Subject: Re: [nasa/openmct] LAD Table does not show string telemetry items (#3323)
@trgarvey<https://github.com/trgarvey> Hi! It sounds like it might be a telemetry metadata issue. Are you seeing this issue with the Open MCT-YAMCS adapter?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#3323 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANYASSE6HKCKM64LIXYHVITSHPAJ3ANCNFSM4QKYMI2A>.
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.
|
Just an update that this issue also occurs with enumerated constants. However- other OpenMCT objects are able to decode the same enumerations correctly, so it appears to be a bug specific to the LAD table. This makes the LAD table much less useful. |
See VIPEROMCT-58 for testing steps. |
Closing as the relevant PR was merged. |
Verified Fixed. |
When a string telemetry item is placed into a LAD table, it does not display either the string or the timestamp. However, the same item will show up correctly on a standard telemetry table. Telemetry "points" with numeric values, on the other hand, seem to work fine.
This was tested with a "string telemetry" item that normally displays as "true/false".
The text was updated successfully, but these errors were encountered: