-
I'm using fprime v3.1.1 and building a deployment that incorporates TlmPacketizer for telemetry packetization. In the only examples I can find online, they define a {Deployment}Packets.xml file that gets autocoded, and the autocoded file is used in the topology build-up to set the packet list of the TlmPacketizer. However, it looks like that autocoding capability was only included in v3.2.0. How was this done in v3.1.1 and earlier? For added context, it looks like the Ref/ application on v3.1.1 has a RefPacketsAi.xml but it isn't included in the build anywhere. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 17 replies
-
Can you clarify what you mean there? Packets.xml doesn’t get autocoded, it has to be hand-written by projects, since they need to specify the packet spec. *Packets.xml indeed is required for when using TlmPacketizer. Ref and all the tutorials/references I know about use TlmChan, so technically this Packets.xml file is not required. The reason we keep it in sync is so that projects can swap TlmChan for TlmPacketizer in the instances.fpp and things should work out of the box. |
Beta Was this translation helpful? Give feedback.
You are right the telemetry packet autocoder was integrated after we delivered the TlmPacketizer component. The autocoded files are required for the telemtry packetizer to work correctly. You have several options to consider on how to resolve this.
cmake/autocoder
, copy in thepackets.cmake
from the abovedevel
…