Raw Data is going into a UNKNOWN packet of the UNKNOWN target .

[PratikAher20]

I am new to the COSMOS community and having fun learning and configuring it. I am trying to build the software for ground station to get the CCSDS space packets and decode them with their respective items which I have already define in the cmd_tlm.txt file. The problem I am facing here is like, after connecting the software I did received the raw data (hexadecimal packets in CCSDS format) but they are routed to the UNKNOWN packet of the UNKNOWN target. As per the documentation provided I had also define one item as ID_ITEM to avoid going the raw data into UNKNOWN packet, but still it is doing the same.

[ryanmelt]

Probably something wrong with your ID_ITEM not matching the raw data. If you can post the raw data, and the ID_ITEM definition we can probably help.

[PratikAher20]

TELEMETRY IS1 beacon BIG_ENDIAN "Health and status from the instrument" <%= render "_ccsds_tlm.txt", locals: {apid: 1} %> ID_ITEM CALLERSIGN 0 96 STRING "IS-1 BCT" BIG_ENDIAN This is how I have define the ID_ITEM. As Raw data contains first 12 bytes as a string. Also the raw data is seen in the IS1 target in the interface tab of command telemetry server but in the tlm packets tab the same raw data goes into an UNKNOWN target. And the raw data in the tlm packets tab in IS1 target shows all zero values. Is there any internal routing issue??

[ryanmelt]

If this is after the CCSDS header, then you should be using APPEND_ID_ITEM, not ID_ITEM. Right now you are overlapping the header definition.

[PratikAher20]

TELEMETRY IS1 beacon BIG_ENDIAN "Health and status from the instrument" ID_ITEM CALLERSIGN 0 96 STRING "IS-1 BCT" BIG_ENDIAN <%= render "_ccsds_tlm.txt", locals: {apid: 1} %> Ok so if i use the above definition will it route correctly now?

[PratikAher20]

Sorry but it's still not working. It is is giving error as ERROR: Unknown 272 byte packet starting: