The complete field tells if the data field is complete yet or not.
So if complete==no that means the data value to be considered needs to be concatenated with the next packet data field value, as long as the complete value is still no.
So in this case, the data value we want to packet 2 is aaaaaabbbbbcccccc.
It is important to get the values from multiple packets together as specified here because we want to apply a decompression algorithm on top of this value (we were thinking of the CCSDSpy converters) and the algorithm only works on the full data stream, in this example the value aaaaaabbbbbcccccc.
In our case, the values for field_A and field_C of packets 3 or 4 do not matter and can be ignored, but I don't know if this would be true in similar use cases.
Do you know how this could be implemented in CCSDSpy ? Maybe the converter could be an object instance which is persisted for the full CCSDS packet streams ? So that we can buffer the data field value until the field is complete and decompression can be applied to it ? From the documentation there https://docs.ccsdspy.org/en/latest/user-guide/converters.html is sounds to be the case.
We have packets with this structure:
The
completefield tells if thedatafield is complete yet or not.So if
complete==nothat means the data value to be considered needs to be concatenated with the next packetdatafield value, as long as the complete value is stillno.So in this case, the data value we want to packet 2 is
aaaaaabbbbbcccccc.It is important to get the values from multiple packets together as specified here because we want to apply a decompression algorithm on top of this value (we were thinking of the CCSDSpy converters) and the algorithm only works on the full data stream, in this example the value
aaaaaabbbbbcccccc.In our case, the values for
field_Aandfield_Cof packets 3 or 4 do not matter and can be ignored, but I don't know if this would be true in similar use cases.Do you know how this could be implemented in CCSDSpy ? Maybe the converter could be an object instance which is persisted for the full CCSDS packet streams ? So that we can buffer the
datafield value until the field is complete and decompression can be applied to it ? From the documentation there https://docs.ccsdspy.org/en/latest/user-guide/converters.html is sounds to be the case.