EIR-OPS-006: Commissioning

Objective

To carry out commissioning phase operations of EIRSAT-1 to ensure the spacecraft is fully functional following launch.

Introduction

The EIRSAT-1 commissioning phase will continue for a number of weeks following launch. During this time, extensive functional checks of the system will be performed. Key operational steps required for nominal operations will also be carried out during this time. These functional checks and operational steps are grouped within this procedure.

Important

This procedure will require multiple communication passes and multiple days/weeks.

Procedure

This procedure is composed of many sub-procedures, as listed below. Initially, the satellite will be transitioned into Commissioning Mode by following the steps in Section A below. Then the Operator will work through the below sub-procedures. These contain the critical subsystem functional tests and operational checks.

Note

Following the ‘Transition to Commissioning Mode’ and ‘TC Authentication’ procedures, the remaining sub-procedures do not necessarily need to be carried out in the order presented below. However, procedures ending in ‘Operation’ should only be completed after the relevant ‘Health Check’ procedure for that subsystem has been performed. The ‘EMOD Reprogramming’ procedure must also be performed prior to any EMOD activities. Lastly, ideally, payload operations should be the last item to consider in the commissioning of the spacecraft.

This commissioning procedure contains the following sub-procedures:

• Commissioning Procedures
  • EIR-OPS-006.1: TC Authentication
  • EIR-OPS-006.3: EPS/BAT Health Check
  • EIR-OPS-006.4: ADCS Health Check
  • EIR-OPS-006.5: GPS Health Check
  • EIR-OPS-006.6: GMOD Health Check
  • EIR-OPS-006.7: EMOD Reprogramming
  • EIR-OPS-006.8: EMOD Health Check
  • EIR-OPS-006.9: ADCS/GPS Operations
  • EIR-OPS-006.10: GMOD Operations
  • EIR-OPS-006.11: EMOD Operations

Once the above sub-procedures have been successfully completed, and all subsystems appear healthy and fit for nominal operations, the Operators may proceed to EIR-OPS-012: Set Up Nominal Operations .

A. Transition to Commissioning Mode

Important

You are about to send the first TC of this procedure - Have you completed the EIR-OPS-003: Start a Communication Pass procedure? A Communication Pass must be started prior to carrying out the operations planned for the pass. Don’t forget to open and set up the parameters/actions that will be used during the pass in MCS before the pass begins!

A.1.

• Invoke the action mission.ModeManager.TransitionToCommissioningMode .

TC Details
MCS Operation	Invoke
Action/Param Name	mission.ModeManager.TransitionToCommissioningMode
Data Expected with TC	No
TM Details
Data Expected from TC	No ( + ACK )

A.2.

• Get the mission.ModeManager.Mode parameter.

• Confirm that 01 (i.e. Commissioning Mode) is returned.

TC Details
MCS Operation	Get
Action/Param Name	mission.ModeManager.Mode
Data Expected with TC	No
TM Details
Data Expected from TC	Mode ( + ACK )
Data Size	1 byte
Data Info	Current Operational Mode of EIRSAT-1
Allowed Value(s)	00 - 04 (see table above)
Expected Value(s)	01 (i.e. Commissioning Mode)

Where…

Mode	Operational Mode
00	Separation Sequence
01	Commissioning
02	Nominal
03	WBC
04	Safe

A.3.

• To assess whether the mode change occurred without error, Get the mission.ModeManager.ExitErrorCount parameter.

• Ensure 0 is returned.

TC Details
MCS Operation	Get
Action/Param Name	mission.ModeManager.ExitErrorCount
Data Expected with TC	No
TM Details
Data Expected from TC	mission.ModeManager.ExitErrorCount ( + ACK )
Data Size	1 byte
Data Info	Error count from last mode exit
Allowed Value(s)	00 - FF (Hex)
Expected Value(s)	0 (i.e. no errors)

A.4.

• Also Get the mission.ModeManager.EntryErrorCount parameter.

• Ensure 0 is returned.

TC Details
MCS Operation	Get
Action/Param Name	mission.ModeManager.EntryErrorCount
Data Expected with TC	No
TM Details
Data Expected from TC	mission.ModeManager.EntryErrorCount ( + ACK )
Data Size	1 byte
Data Info	Error count from last mode entry
Allowed Value(s)	00 - FF (Hex)
Expected Value(s)	0 (i.e. no errors)

A.5.

• As this is the very first mode change on-orbit, we will now check some of the more critical parameters to verify that the mode change occurred without error. As part of this, Get the mission.SeparationSequence.State parameter.

• Ensure 66 (dec) / 42 (hex) is returned.

TC Details
MCS Operation	Get
Action/Param Name	mission.SeparationSequence.State
Data Expected with TC	No
TM Details
Data Expected from TC	State ( + ACK )
Data Size	1 byte
Data Info	The current State of EIRSAT-1
Allowed Value(s)	00 - 09, 42 (hex)
Expected Value(s)	66 (dec) / 42 (hex) (i.e. the Separation Sequence Finished State)

A.6.

• Get the parameter mission.ModeManager.NominalEntryEPSSwStatesBitmap .

• Ensure that 200 (hex) / 1000000000 (bitfield) is returned.

TC Details
MCS Operation	Get
Action/Param Name	mission.ModeManager.NominalEntryEPSSwStatesBitmap
Data Expected with TC	No
TM Details
Data Expected from TC	NominalEntryEPSSwStatesBitmap ( + ACK )
Data Size	2 bytes
Data Info	A bitmap describing the switch states to be set for the 10 EPS PDMs
Allowed Value(s)	0000 - 03FF (Hex)
Expected Value(s)	200 (hex) / 1000000000 (bitfield) (i.e. PDM 10 ON only)

A.7.

• Finally, Get the platform.cdh.monitoring.CriticalMonitor.enabled parameter.

• Ensure that 1 is returned.

Note

This monitor being enabled is required to trigger Safe Mode.

TC Details
MCS Operation	Get
Action/Param Name	platform.cdh.monitoring.CriticalMonitor.enabled
Data Expected with TC	No
TM Details
Data Expected from TC	enabled ( + ACK )
Data Size	boolean
Data Info	Boolean indicating whether the monitor is enabled (1) or disabled (0)
Allowed Value(s)	0 - 1
Expected Value(s)	1 (i.e. Critical Monitor enabled)

A.8.

• The transition to Commissioning Mode has now been completed and checked.

• Proceed with the next commissioning procedures: EIR-OPS-006.1: TC Authentication .

END OF PROCEDURE