search

BallAerospace / COSMOS

Ball Aerospace COSMOS
https://ballaerospace.github.io/cosmos-website/
Other
360 stars 129 forks source link

Using COSMOS 4.5.2, how do I configure COSMOS to recognize and assign the correct telemetry packets #1766

Closed HollandMcQ2 closed 2 years ago

HollandMcQ2 commented 2 years ago

I have a COSMOS 4.5.2 app running with hundreds of command definition files and hundreds of telemetry packet definitions defined. I have specific commands that I can run to enable/disable telemetry. I am looking for a way to configure COSMOS such that when it receives a telemetry packet from my target it correctly assigns it to the correct corresponding telemetry definition I have setup.

Currently when telemetry is received from my target I get a message telling me that telemetry is received with a packet length of x but defined length of y. The packet being received is always the same one and is alphabetically the last packet defined.

Is there a way for me to configure COSMOS to recognize all of the other telemetry packets I have defined that have different packet lengths that correspond to the telemetry I am receiving?

jmthomas commented 2 years ago

Do you have ID_ITEMs defined in your telemetry definitions?

HollandMcQ2 commented 2 years ago

I do not, that is probably the issue. I will update when I try that

HollandMcQ2 commented 2 years ago

That fixed y problem, thank you