You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Quick note, based of the description and tags, sequencers in F´ already exists and is built-in to the refs. There are a few things that need to be done though to make it mission-ready.
Based of design patterns in Ingenuity and many other satellites, you'd want to create a main sequence file that is very carefully and checked extensively to ensure that it cannot fail that sets up parameters and initiates other sequences. This is mainly to prevent the deployment binary from completely fatal asserting if a particular command gets hanged.
To facilitate this, you will probably need to create a bunch of sequencers and connect them to the dispatcher. Many Missions had at least 16 sequencers, but it is likely Proves will need less than this.
IMO unit testing and system testing will help a lot in the future for testing the sequence files. That way it'll be a good check if proper commands are being executed per the sequence.
We need to create a sequencer to schedule satellite commands to happen at various times!
FPrime Reference
https://nasa.github.io/fprime/UsersGuide/gds/seqgen.html
The text was updated successfully, but these errors were encountered: