EIR-OPS-035: Configure the FDIR Systems

Objective

To change settings related to the FDIR software on-board the spacecraft.

Introduction

Using this procedure, the Operator can configure different parts (i.e.checks/watchdogs/timeouts) of the FDIR software on-board the spacecraft.

Procedure

Steps are provided below for the following (standalone) sub-procedures:

Important

These sub-procedures have been grouped together in this procedure as they are all related to configuring the FDIR software on-board the spacecraft. However, each of the sub-procedures are standalone procedures that can be carried individually to achieve the objectives stated in the sub-procedure titles.

A. Changing the BATV Critical Monitor Limits
B. Disabling the BATV Critical Monitor Check
C. Changing the Gyro Rate Critical Monitor Limits
D. Disabling the Gyro Rate Critical Monitor Check
E. Disabling the Critical Monitor Entirely
F. Editing the No-GS-TC Watchdog Timeout
G. Disabling the No-GS-TC Watchdog Timeout
H. Editing the EPS Watchdog Timeout

Note

A communication window is required for each of these sub-procedures.

A. Changing the BATV Critical Monitor Limits

A.1.

Get the cdh.monitoring.CriticalMonitor.checkListPacked parameter with First row = Last row = 0.

TC Details
MCS Operation	`Get`
Action/Param Name	`cdh.monitoring.CriticalMonitor.checkListPacked`
Data Expected with TC	Yes
Data Size	4 bytes, 4 bytes
Data Info	`First row` , `Last row`
Allowed Value(s)	0-16, 0-16
Expected Value(s)	`First row` = `Last row` = 0 (i.e. the index of the BATV check)
TM Details
Data Expected from TC	`cdh.monitoring.CriticalMonitor.checkListPacked` ( + ACK )
Data Size	20 bytes
Data Info	Packed records on the monitoring checks
Allowed Value(s)	Many

The first 2 bytes of the TM returned correspond to the Parameter ID of the monitored parameter.
The next 2 bytes are the row number of the parameter being monitored.
The next 8 bytes are then the upper (4 bytes) and lower (4 bytes) limits used to define the ‘valid’ range for the parameter. If the parameter exceeds these limits, the monitor will raise an event.

A.2.

Using the TM returned in the above step, convert the 4-byte upper and lower battery voltage limits to actual voltage values according to the following conversion - battery voltage (in volts) = ADC (in decimal) x 0.008993.

A.3.

Using the information provided in Step A.2, determine what the upper and lower Limits in the checkListPacked parameter should now be set to.

A.4.

Again, Get the cdh.monitoring.CriticalMonitor.checkListPacked parameter with First row = Last row = 0.
Using the TM returned in the data field, edit the upper and lower limit bytes to equal the updated/desired limits (in hex) and click Set .

TC Details
MCS Operation	`Set`
Action/Param Name	`cdh.monitoring.CriticalMonitor.checkListPacked`
Data Expected with TC	Yes
Data Size	4 bytes, 4 bytes, 20 bytes
Data Info	`First row` , `Last row` , `checkListPacked`
Allowed Value(s)	0-16, 0-16, N/A
Expected Value(s)	`First row` = `Last row` = 0, N/A
TM Details
Data Expected from TC	No ( + ACK )

A.5.

Confirm the Set in the previous step with a Get (i.e. confirm the value was set successfully).

B. Disabling the BATV Critical Monitor Check

Danger

Are you sure you want to disable the battery voltage monitor? This monitor ensures that the spacecraft enters Safe Mode (i.e. a low-power state where all non-critical subsystems are powered OFF) if the battery gets depleted below nominal levels.

B.1.

Get the cdh.monitoring.CriticalMonitor.checkEnabled parameter with First row = Last row = 0.

TC Details
MCS Operation	`Get`
Action/Param Name	`cdh.monitoring.CriticalMonitor.checkEnabled`
Data Expected with TC	Yes
Data Size	4 bytes, 4 bytes
Data Info	`First row` , `Last row`
Allowed Value(s)	0-16, 0-16
Expected Value(s)	0, 0
TM Details
Data Expected from TC	`checkEnabled` ( + ACK )
Data Size	boolean
Data Info	Whether the BATV critical monitor is enabled (1) or disabled (0)
Allowed Value(s)	0-1
Expected Value(s)	1 (i.e. BATV monitor check enabled)

B.2.

Set the cdh.monitoring.CriticalMonitor.checkEnabled parameter with First row = Last row = 0 to 0 (i.e. monitor disabled).

TC Details
MCS Operation	`Set`
Action/Param Name	cdh.monitoring.CriticalMonitor.checkEnabled`
Data Expected with TC	Yes
Data Size	4 bytes, 4 bytes, boolean
Data Info	`First row` , `Last row` , BATV monitor check enabled (1)/disabled (0)
Allowed Value(s)	0-16, 0-16, 0-1
Expected Value(s)	0, 0, 0 (i.e. BATV monitor check disabled)
TM Details
Data Expected from TC	No ( + ACK )

B.3.

Confirm the Set in the previous step with a Get (i.e. confirm the value was set successfully).

C. Changing the Gyro Rate Critical Monitor Limits

C.1.

Get the cdh.monitoring.CriticalMonitor.checkListPacked parameter with First row = Last row = 1.

Note

When setting this parameter the LSByte (i.e. the Monitor Flags byte) should be set to 0x01 or else a NACK will be returned.

TC Details
MCS Operation	`Get`
Action/Param Name	`cdh.monitoring.CriticalMonitor.checkListPacked`
Data Expected with TC	Yes
Data Size	4 bytes, 4 bytes
Data Info	`First row` , `Last row`
Allowed Value(s)	0-16, 0-16
Expected Value(s)	`First row` = `Last row` = 1 (i.e. the index of the Gyro Rate check)
TM Details
Data Expected from TC	`cdh.monitoring.CriticalMonitor.checkListPacked` ( + ACK )
Data Size	20 bytes
Data Info	Packed records on the monitoring checks
Allowed Value(s)	Many

The first 2 bytes of the TM returned correspond to the Parameter ID of the monitored parameter.
The next 2 bytes are the row number of the parameter being monitored.
The next 8 bytes are then the upper (4 bytes) and lower (4 bytes) limits used to define the ‘valid’ range for the parameter. If the parameter exceeds these limits, the monitor will raise an event.

Note

The parameter being monitored by this check is the total gyro rate squared.

C.2.

Using the TM returned in the above step, convert the 4-byte upper and lower total gyro rate squared limits to actual values (in degrees) according to the following conversion - total gyro rate squared (in degrees) = ADC (in decimal) / (96 x 96).

C.3.

Using the information provided in Step C.2, determine what the upper and lower limits in the checkListPacked parameter should now be set to.

C.4.

Again, Get the cdh.monitoring.CriticalMonitor.checkListPacked parameter with First row = Last row = 1.
Using the TM returned in the data field, edit the upper and lower limit bytes to equal the updated/desired limits (in hex) and click Set .

TC Details
MCS Operation	`Set`
Action/Param Name	`cdh.monitoring.CriticalMonitor.checkListPacked`
Data Expected with TC	Yes
Data Size	4 bytes, 4 bytes, 20 bytes
Data Info	`First row` , `Last row` , `checkListPacked`
Allowed Value(s)	0-16, 0-16, N/A
Expected Value(s)	`First row` = `Last row` = 1, N/A
TM Details
Data Expected from TC	No ( + ACK )

C.5.

Confirm the Set in the previous step with a Get (i.e. confirm the value was set successfully).

D. Disabling the Gyro Rate Critical Monitor Check

Danger

Are you sure you want to disable the gyro rate monitor? This monitor ensures that the spacecraft enters Safe Mode (i.e. a low-power state where all non-critical subsystems are powered OFF) if the spin rate of the satellite exceeds nominal levels.

D.1.

Get the cdh.monitoring.CriticalMonitor.checkEnabled parameter with First row = Last row = 1.

TC Details
MCS Operation	`Get`
Action/Param Name	`cdh.monitoring.CriticalMonitor.checkEnabled`
Data Expected with TC	Yes
Data Size	4 bytes, 4 bytes
Data Info	`First row` , `Last row`
Allowed Value(s)	0-16, 0-16
Expected Value(s)	1, 1
TM Details
Data Expected from TC	`checkEnabled` ( + ACK )
Data Size	boolean
Data Info	Whether the gyro rate critical monitor is enabled (1) or disabled (0)
Allowed Value(s)	0-1
Expected Value(s)	1 (i.e. gyro rate monitor enabled)

D.2.

Set the cdh.monitoring.CriticalMonitor.checkEnabled parameter with First row = Last row = 1 to 0 (i.e. monitor disabled).

TC Details
MCS Operation	`Set`
Action/Param Name	cdh.monitoring.CriticalMonitor.checkEnabled`
Data Expected with TC	Yes
Data Size	4 bytes, 4 bytes, boolean
Data Info	`First row` , `Last row` , gyro rate monitor check enabled (1)/disabled (0)
Allowed Value(s)	0-16, 0-16, 0-1
Expected Value(s)	1, 1, 0 (i.e. gyro rate monitor disabled)
TM Details
Data Expected from TC	No ( + ACK )

D.3.

Confirm the Set in the previous step with a Get (i.e. confirm the value was set successfully).

E. Disabling the Critical Monitor Entirely

Danger

Are you sure you want to disable the Critical Monitor? This monitor ensures that the spacecraft enters Safe Mode (i.e. a low-power state where all non-critical subsystems are powered OFF) if the battery gets depleted below nominal levels or the spin rate of the satellite exceeds nominal levels.

E.1.

Get the cdh.monitoring.CriticalMonitor.enabled parameter.

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

E.2.

Set the cdh.monitoring.CriticalMonitor.enabled parameter to 0 (i.e. monitor disabled).

TC Details
MCS Operation	`Set`
Action/Param Name	`cdh.monitoring.CriticalMonitor.enabled`
Data Expected with TC	`enabled`
Data Size	boolean
Data Info	Whether the critical monitor is enabled (1) or disabled (0)
Allowed Value(s)	0-1
Expected Value(s)	0 (i.e. critical monitor disabled)
TM Details
Data Expected from TC	No ( + ACK )

E.3.

Confirm the Set in the previous step with a Get (i.e. confirm the value was set successfully).

F. Editing the No-GS-TC Watchdog Timeout

F.1.

Get the mission.ModeManager.NoTCWatchdogTimeout parameter.

TC Details
MCS Operation	`Get`
Action/Param Name	`mission.ModeManager.NoTCWatchdogTimeout`
Data Expected with TC	No
TM Details
Data Expected from TC	`NoTCWatchdogTimeout` ( + ACK )
Data Size	1 byte
Data Info	The number of days without a TC before the no-GS-TC watchdog triggers
Allowed Value(s)	00-FF (Hex)
Expected Value(s)	3 (default)

F.2.

Set the mission.ModeManager.NoTCWatchdogTimeout parameter to the desired timeout period (in days).

TC Details
MCS Operation	`Set`
Action/Param Name	`mission.ModeManager.NoTCWatchdogTimeout`
Data Expected with TC	`NoTCWatchdogTimeout`
Data Size	1 byte
Data Info	The number of days without a TC before the no-GS-TC watchdog triggers
Allowed Value(s)	00-FF (hex)
TM Details
Data Expected from TC	No ( + ACK )

F.3.

Confirm the Set in the previous step with a Get (i.e. confirm the value was set successfully).

G. Disabling the No-GS-TC Watchdog Timeout

Danger

Are you sure you want to disable the no GS-TC-Watchdog? This watchdog ensures that the spacecraft autonomously acts to try to regain a nominal working state in the case where no TCs are received/accepted by the spacecraft from the UCD GS in a significant period of time. This watchdog provides protection against a scenario where the spacecraft somehow enters a configuration where the GS’s TCs are not received/accepted by the spacecraft.

G.1.

Get the mission.ModeManager.NoTCWatchdogTimeout parameter to ensure the watchdog is active (i.e. ensure that the NoTCWatchdogTimeout parameter != 0).

TC Details
MCS Operation	`Get`
Action/Param Name	`mission.ModeManager.NoTCWatchdogTimeout`
Data Expected with TC	No
TM Details
Data Expected from TC	`NoTCWatchdogTimeout` ( + ACK )
Data Size	1 byte
Data Info	The number of days without a TC before the no-GS-TC watchdog triggers
Allowed Value(s)	00-FF (Hex)
Expected Value(s)	3 (dec/default)

G.2.

To now disable the no-GS-TC watchdog, Set the mission.ModeManager.NoTCWatchdogTimeout parameter to 0.

TC Details
MCS Operation	`Set`
Action/Param Name	`mission.ModeManager.NoTCWatchdogTimeout`
Data Expected with TC	`NoTCWatchdogTimeout`
Data Size	1 byte
Data Info	The number of days without a TC before the no TC watchdog triggers
Allowed Value(s)	00-FF (hex)
Expected Value(s)	0
TM Details
Data Expected from TC	No ( + ACK )

G.3.

Confirm the Set in the previous step with a Get (i.e. confirm the value was set successfully).

H. Editing the EPS Watchdog Timeout

H.1.

Get the platform.EPS.watchDogTimeout parameter.

TC Details
MCS Operation	`Get`
Action/Param Name	`platform.EPS.watchDogTimeout`
Data Expected with TC	No
TM Details
Data Expected from TC	`watchDogTimeout` ( + ACK )
Data Size	1 byte
Data Info	EPS watchdog timeout in minutes
Allowed Value(s)	0-90 (dec)
Expected Values(s)	4 (dec/default)

H.2.

Set the platform.EPS.watchDogTimeout parameter to the desired timeout period (in minutes).

TC Details
MCS Operation	`Set`
Action/Param Name	`platform.EPS.watchDogTimeout`
Data Expected with TC	`watchDogTimeout`
Data Size	1 byte
Data Info	Watchdog timeout in minutes
Allowed Value(s)	0-90 (dec)
TM Details
Data Expected from TC	No ( + ACK )

H.3.

Confirm the Set in the previous step with a Get (i.e. confirm the value was set successfully).

END OF PROCEDURE