Now that the main bulk of ADCS command functions are complete, the Commissioning Manual requires that certain ADCS telemetry requests be repeatedly polled every few seconds over the course of between several minutes to one full orbit (see Sections 2.2 and 2.3 of the Commissioning Manual for more details).

In total there are 30 telemetry request functions that must be called in various combinations, of which there are 18 combinations which we care about for commissioning.

This function will need to take inputs:

• Which functions to poll (either the specific functions to poll)
• The period to poll them over (in seconds; either 1 second or 10 seconds)
• How long to poll them for (either time in minutes/hours or else enable/disable; need to check what's most appropriate for the "1 orbit" condition)

Note that all of these inputs can be replaced with a single input: the numbered commissioning step to execute, in exchange for less freedom of operation.

What it will need to do:

• Check the ACP Execution State telemetry to ensure that Time Since Iteration Start > 500 ms (see Section 2.3)
• Call the appropriate telemetry request functions and load them into their structs (the Current ADCS State telemetry request may also be necessary)
• Save the structs to memory (preferably with timestamp, which is another ADCS telemetry request or can be from the OBC)
• Do this all periodically until the time of polling is complete, then downlink the data when next possible.

This downlink will be for ground processing, and varies depending on the commissioning step.