EIR-OPS-020: GMOD Configuration


Objective

To facilitate the Operator in configuring the GMOD Experiment.


Introduction

This procedure will guide the Operator through the different parameters and actions that can be used to configure the GMOD experiment/payload.

Once the configuration of GMOD is as required, the GMOD experiment can be set up by following the relevant sections in the EIR-OPS-021: GMOD Experiment Set Up.

Important

These sub-procedures have been grouped together in this procedure as they are all related to configuring parameters related to the GMOD payload. However, each of the sub-procedures is a stand-alone procedure that can be followed individually to achieve the objectives/assess the settings stated in the sub-procedure titles (Sections B - I, however, do require that GMOD is powered ON - see Section A). The Operator should use EIR-OPS-021: GMOD Experiment Set Up to see how you can use some of the below sections sequentially.


Procedure

This procedure contains a number of sub-procedures as follows:

A. Power On and Check Status

B. Bias Offset Settings - Configure and Enable Bias Offset, Disable Bias Offset

C. Boost Converter Settings - Enable Boost Converter, Disable Boost Converter

D. Constant Current Settings - Enable Constant Current, Disable Constant Current

E. External Trigger Settings

F. SIPHRA Configuration

G. Lightcurve and Spectrum Configuration

H. OBC Triggering Configuration

I. Mode Change

J. Set Up 16 Channel TTE Streaming

K. Turn Off GMOD

Note

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


A. Power On and Check Status

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 set up the parameters/actions that will be used during the pass in MCS before the pass begins!

A.1.

  • Invoke the action platform.EPS.TurnOnGMOD to turn on GMOD.

TC Details

MCS Operation

Invoke

Action/Param Name

platform.EPS.TurnOnGMOD

Data Expected with TC

No

TM Details

Data Expected from TC

No ( + ACK )

A.2.

  • Get the parameter platform.EPS.actualSwitchStates with First row = 0 and Last row = 9 to assess whether GMOD is now on.

  • Ensure that PDMs 3, 6 and 9/rows 2, 5 and 8 are ON/1.

Warning

PDM 8 is drawing parasitic power. Therefore, when you Get the platform.EPS.actualSwitchStates parameter it will always read as ON/1 even when it is powered OFF.

TC Details

MCS Operation

Get

Action/Param Name

platform.EPS.actualSwitchStates

Data Expected with TC

First row, Last row

Data Size

2 bytes, 2 bytes

Data Info

The first and last rows/indexes of the parameter to get

Allowed Value(s)

0 - 9, 0 - 9

Expected Value(s)

0, 9

TM Details

Data Expected from TC

actualSwitchStates[0:9] ( + ACK )

Data Size

List[0:9] of booleans

Data Info

If actualSwitchStates[n] = 1, PDM n is ON

Allowed Value(s)

0,0,0,0,0,0,0,0,0,0 (all OFF) - 1,1,1,1,1,1,1,1,1,1 (all ON)

Expected Value(s)

X,X,1,X,X,1,X,X,1,X (PDMs 3, 6 + 9 = 1. Other PDMs may be 0 or 1)

A.3.

  • Get the parameter payload.GMOD.FirmwareVersion to further verify that GMOD is now on.

  • Assess whether the firmware version is as expected given the last firmware programmed onto the MSP.

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.FirmwareVersion

Data Expected with TC

No

TM Details

Data Expected from TC

FirmwareVersion ( + ACK )

Data Size

2 bytes

Data Info

Version of the firmware currently running on the GMOD MSP

Allowed Value(s)

0000 - FFFE

A.4.

  • Get the parameter payload.GMOD.GMODMode to assess whether GMOD is operating in the expected mode following power on.

  • Ensure Idle Mode/1 is returned.

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.GMODMode

Data Expected with TC

No

TM Details

Data Expected from TC

GMODMode ( + ACK )

Data Size

Int4

Data Info

Current operational mode of GMOD

Allowed Value(s)

1 - 5

Expected Value

1

Where…

GMODMode

Mode

1

Idle

2

Experiment

3

CPLD Programme

4

Safe

5

Experiment16

A.5.

  • Get the parameter payload.GMOD.ResetCounter to determine the number of times the GMOD payload has reset since the MSP was last programmed.

  • Assess whether the returned parameter value is as expected given its last known value.

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.ResetCounter

Data Expected with TC

No

TM Details

Data Expected from TC

ResetCounter ( + ACK )

Data Size

1 byte

Data Info

Number of resets since the firmware was last programmed

Allowed Value(s)

0 - 127

A.6.

  • Get the parameter payload.GMOD.LastResetType to determine the type of GMOD reset(s) that have occurred.

  • Continue to get this parameter until 0 is returned.

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.LastResetType

Data Expected with TC

No

TM Details

Data Expected from TC

LastResetType ( + ACK )

Data Size

1 byte

Data Info

Last GMOD reset type(s)

Allowed Value(s)

00 - 2E

Where…

LastResetType

Reset Type

02

Brownout

04

Unknown

06

SW reboot

14

SW reboot

16

Watchdog reset


B. Bias Offset Settings

Configure and Enable Bias Offset

B.1.

  • Get the parameter payload.GMOD.biasOffsetEnable .

  • If 0 (i.e. disabled) is returned, skip ahead to Step B.4.

  • Else, proceed to the next step.

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.biasOffsetEnable

Data Expected with TC

No

TM Details

Data Expected from TC

biasOffsetEnable ( + ACK )

Data Size

Boolean

Data Info

Bias Offset is Disabled (0) or Enabled (1)

Allowed Value(s)

0, 1

B.2.

  • Set the parameter payload.GMOD.biasOffsetEnable to 0.

TC Details

MCS Operation

Set

Action/Param Name

payload.GMOD.biasOffsetEnable

Data Expected with TC

Yes

Data Size

Boolean

Data Info

Bias Offset is Disabled (0) or Enabled (1)

Allowed Value(s)

0, 1

Expected Value(s)

0

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).


B.4.

  • Set the parameter payload.GMOD.BiasOffsetValue to the value specified by the GMOD Team.

TC Details

MCS Operation

Set

Action/Param Name

payload.GMOD.BiasOffsetValue

Data Expected with TC

Yes

Data Size

2 bytes

Data Info

Bias Offset Value

Allowed Value(s)

0000 - 0A8F (which corresponds to 0V - 3.3V)

Expected Value(s)

Value specified by the GMOD Team

TM Details

Data Expected from TC

No ( + ACK )

B.5.

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


B.6.

  • Set the parameter payload.GMOD.biasOffsetEnable to 1.

TC Details

MCS Operation

Set

Action/Param Name

payload.GMOD.biasOffsetEnable

Data Expected with TC

Yes

Data Size

Boolean

Data Info

Bias Offset is Disabled (0) or Enabled (1)

Allowed Value(s)

0, 1

Expected Value(s)

1

TM Details

Data Expected from TC

No ( + ACK )

B.7.

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


B.8.

  • Get the parameter payload.GMOD.BiasOffsetVoltage .

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.BiasOffsetVoltage

Data Expected with TC

No

TM Details

Data Expected from TC

GMOD.BiasOffsetVoltage ( + ACK )

Data Size

2 bytes

Data Info

ADC value connected to DACB output

Allowed Value(s)

0000 - 0FFF

Disable Bias Offset

B.9.

  • Set the parameter payload.GMOD.biasOffsetEnable to 0 to disable the Bias Offset.

TC Details

MCS Operation

Set

Action/Param Name

payload.GMOD.biasOffsetEnable

Data Expected with TC

Yes

Data Size

Boolean

Data Info

Bias Offset is Disabled (0) or Enabled (1)

Allowed Value(s)

0, 1

Expected Value(s)

0

TM Details

Data Expected from TC

No ( + ACK )

B.10.

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



C. Boost Converter Settings

Enable Boost Converter

C.1.

  • Get the parameter payload.GMOD.boostConverterEnable .

  • If 1 (i.e. enabled) is returned, skip ahead to Step C.4.

  • Else, proceed to the next step.

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.boostConverterEnable

Data Expected with TC

No

TM Details

Data Expected from TC

boostConverterEnable ( + ACK )

Data Size

Boolean

Data Info

Boost Converter is Disabled (0) or Enabled (1)

Allowed Value

0, 1

C.2.

  • Set the parameter payload.GMOD.boostConverterEnable to 1 to enable the boost converter.

TC Details

MCS Operation

Set

Action/Param Name

payload.GMOD.boostConverterEnable

Data Expected with TC

Yes

Data Size

Boolean

Data Info

Boost Converter is Disabled (0) or Enabled (1)

Allowed Value(s)

0, 1

Expected Value(s)

1

TM Details

Data Expected from TC

No ( + ACK )

C.3.

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


C.4.

  • Get the parameter payload.GMOD.BiasVoltage .

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.BiasVoltage

Data Expected with TC

No

TM Details

Data Expected from TC

BiasVoltage ( + ACK )

Data Size

2 bytes

Data Info

ADC values connected to bias voltage

Allowed Value(s)

0000 - 0FFF

Disable Boost Converter

C.5.

  • Set the parameter payload.GMOD.boostConverterEnable to 0 to disable the Boost Converter.

TC Details

MCS Operation

Set

Action/Param Name

payload.GMOD.boostConverterEnable

Data Expected with TC

Yes

Data Size

Boolean

Data Info

Boost Converter is Disabled (0) or Enabled (1)

Allowed Value(s)

0, 1

Expected Value

0

TM Details

Data Expected from TC

No ( + ACK )

C.6.

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



D. Constant Current Settings

Configure and Enable Constant Current

D.1.

  • Get the parameter payload.GMOD.ConstantCurrEnable .

  • If 0 (i.e. disabled) is returned, skip ahead to Step D.4.

  • Else, proceed to the next step.

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.ConstantCurrEnable

Data Expected with TC

No

TM Details

Data Expected from TC

ConstantCurrEnable ( + ACK )

Data Size

Boolean

Data Info

Enable (1) or Disable (0) Constant Current

Allowed Value

0, 1

D.2.

  • Set the parameter payload.GMOD.ConstantCurrEnable to 0.

TC Details

MCS Operation

Set

Action/Param Name

payload.GMOD.ConstantCurrEnable

Data Expected with TC

Yes

Data Size

Boolean

Data Info

Enable (1) or Disable (0) Constant Current

Allowed Value(s)

0, 1

Expected Value(s)

0

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).


D.4.

  • Set the parameter payload.GMOD.ConstantCurrValue to the desired DACA value specified by the GMOD Team.

TC Details

MCS Operation

Set

Action/Param Name

payload.GMOD.ConstantCurrValue

Data Expected with TC

Yes

Data Size

Int16

Data Info

DACA value that controls Constant Current.

Allowed Value(s)

0000 - 0FFF (hex)

Expected Value(s)

Value specified by the GMOD Team

TM Details

Data Expected from TC

No ( + ACK )

D.5.

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


D.6.

  • Set the parameter payload.GMOD.ConstantCurrEnable to 1.

TC Details

MCS Operation

Set

Action/Param Name

payload.GMOD.ConstantCurrEnable

Data Expected with TC

Yes

Data Size

Boolean

Data Info

Enable (1) or Disable (0) Constant Current

Allowed Value(s)

0, 1

Expected Value(s)

1

TM Details

Data Expected from TC

No ( + ACK )

D.7.

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


Disable Constant Current

D.8.

  • Get the parameter payload.GMOD.ConstantCurrEnable .

  • If 0 (i.e. disabled) is returned, this section of the procedure is complete (i.e. do not proceed with the remaining steps in this section).

  • Else, proceed to the next step.

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.ConstantCurrEnable

Data Expected with TC

No

TM Details

Data Expected from TC

ConstantCurrEnable ( + ACK )

Data Size

Boolean

Data Info

Enable (1) or Disable (0) Constant Current

Allowed Value

0, 1

D.9.

  • Set the parameter payload.GMOD.ConstantCurrEnable to 0.

TC Details

MCS Operation

Set

Action/Param Name

payload.GMOD.ConstantCurrEnable

Data Expected with TC

Yes

Data Size

Boolean

Data Info

Enable (1) or Disable (0) Constant Current

Allowed Value(s)

0, 1

Expected Value(s)

0

TM Details

Data Expected from TC

No ( + ACK )

D.10.

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



E. External Trigger Settings

Note

This section will allow you to configure the external trigger frequency which will initiate manual readouts of SIPHRA at a fixed frequency while in Experiment Mode (i.e. GMODMode = 02).

E.1.

  • Get the parameter payload.GMOD.ExternalTrigFreq .

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.ExternalTrigFreq

Data Expected with TC

No

TM Details

Data Expected from TC

ExternalTrigFreq ( + ACK )

Data Size

uint16

Data Info

The external trigger frequency.

Allowed Value(s)

0013 - FFEE (hex)

E.2.

  • Set the parameter payload.GMOD.ExternalTrigFreq to the value specified by the GMOD Team.

TC Details

MCS Operation

Set

Action/Param Name

payload.GMOD.ExternalTrigFreq

Data Expected with TC

Yes

Data Size

unint16

Data Info

The external trigger frequency.

Allowed Value(s)

0013 - FFEE (hex)

Expected Value(s)

Value specified by the GMOD Team

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. SIPHRA Configuration

F.1.

  • The Operator should confirm with the GMOD team that the correct file to configure the SIPHRA register addresses is available/ready for use in the next step.


F.2.

Important

As you are about to perform an uplink, ensure that MCS’s Transfer Window is visible to the Operator before proceeding.

  • To configure the SIPHRA registers, Uplink the file from Step F.1 to the parameter payload.GMOD.ASICReg with:

    • First row = 0,

    • Last row = 27, and

    • with resize ticked.

TC Details

MCS Operation

Uplink

Action/Param Name

payload.GMOD.ASICReg

Data Expected with TC

Yes

Data Size

4 bytes; 4 bytes; 112 bytes

Data Info

First Row = 0, Last Row = 27, Tick Resize, File to uplink

Allowed Value(s)

0-27, 0-27, 0-1, File with SIPHRA Register values

Expected Value(s)

0, 27, 1, File with SIPHRA Register values

TM Details

Data Expected from TC

No ( + ACK )

Note

There are 2 parameters that can be Set to write the ASIC Reg table on the GMOD MSP. The first is the ASICReg parameter which, when Set, immediately writes the values to the ASIC Reg table on the GMOD MSP. The second is the InitASICRegBuffer parameter. This parameter differs in that it is a buffer on the OBC (not that MSP) that is used by the InitialiseGMOD action. When the Operator writes values to this parameter they do not get written the MSP until the InitialiseGMOD action is called. As the below steps do not call the InitialiseGMOD action, the ASICReg parameter will be used. To see an example of where the InitASICRegBuffer parameter is used, see Section B of the EIR-OPS-021: GMOD Experiment Set Up procedure.


F.3.

  • Wait for the Transfer Window on MCS to indicate that the uplink has completed successfully.


F.4.

  • Downlink the SIPHRA registers using the parameter payload.GMOD.ASICReg and with:

    • First row = 0,

    • Last row = 27.

  • Confirm (e.g. via visual inspection or an MD5 checksum) that the downliked file matches the file from Step F.1.

TC Details

MCS Operation

Downlink

Action/Param Name

payload.GMOD.ASICReg

Data Expected with TC

Yes

Data Size

4 bytes; 4 bytes

Data Info

First Row, Last Row

Allowed Value(s)

0 - 27, 0 - 27 (dec)

Expected Value(s)

0, 27 (dec)

TM Details

Data Expected from TC

ASICReg file ( + ACK )

Data Size

112 bytes

Data Info

ASIC register values to be set as part of the InitialiseGMOD action

Allowed Value(s)

Many

Expected Value

Contents of the downlinked file should match the file from Step F.1.

F.5.

  • Invoke the action payload.GMOD.writeRegToSIPHRA to write the contents of the ASIC Register table on the MSP to the SIPHRA registers.

TC Details

MCS Operation

Invoke

Action/Param Name

payload.GMOD.writeRegToSIPHRA

Data Expected with TC

No

TM Details

Data Expected from TC

No ( + ACK )

F.6.

  • Get the parameter payload.GMOD.WriteRegStatus to assess whether the contents of the SIPHRA configuration file were written to SIPHRA correctly.

  • Ensure 1 (i.e. success) is returned.

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.WriteRegStatus

Data Expected with TC

No

TM Details

Data Expected from TC

WriteRegStatus ( + ACK )

Data Size

bit3

Data Info

Successful = 1, In Progress = 0, Failed = 2

Allowed Value(s)

0, 1, 2

Expected Value

1


G. Lightcurve and Spectrum Configuration

G.1.

  • Prior to setting up streaming of data from GMOD to the OBC, the parameters listed in the table below must be reviewed (e.g. via Get TCs and/or previous pass notes), and may need to be changed (i.e. via a Get - Set - Get ).

  • If the GMOD Team have specified that one or more of the parameters in the table below needs to be configured, follow Steps G.2-G.4 for each of the parameters.

Parameter Name

Data Size

Data Info

Allowed Values

LCBinWidth

uint16

The bin width (in milliseconds) to be used for the ‘normal’/logged lightcurve buffer.

1-65535 (dec)

LCADCEventLims

uint16 [2]

The upper and lower limits to be used when assessing whether ADC event data should be added to the ‘normal’/logged LC buffer. Row 0 is the lower limit and row 1 is the upper limit.

0-65535 (dec)

SpecLowerADCBinLim

uint16

The lower limit to be used when assessing whether ADC event data should be added to the ‘normal’/logged spectrum buffer.

0 - 4095 (dec)

SpecADCBinWidth

uint8

The bin width (in ADC channels) to be used for the logged spectrum buffer.

1 - 16 (dec)

SpecIntTime

uint16

The integration time (in seconds) to be used for the ‘normal’/logged spectrum buffer.

1-65535 (dec)

G.2.

  • Get the parameter payload.GMOD.XXXX , where XXXX is the parameter name from the table above.

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.XXXX

Data Expected with TC

Parameter-dependant

TM Details

Data Expected from TC

XXXX ( + ACK )

G.3.

  • If the parameter value is not as desired, Set the payload.GMOD.XXXX parameter to the desired value now.

TC Details

MCS Operation

Set

Action/Param Name

payload.GMOD.XXXX

Data Expected with TC

Yes

TM Details

Data Expected from TC

No ( + ACK )

G.4.

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



H. OBC Triggering Configuration

Important

Early in the mission, and possibly during the mission, the GRB trigger threshold may need to be modified (increased/decreased) based on the GMOD data downlinked. The GMOD team should be consulted before changing the trigger threshold.

H.1.

  • Prior to setting up OBC Triggering, the parameters listed in the table below must be reviewed (e.g. via Get TCs and/or previous pass notes), and may need to be changed (i.e. via a Get - Set - Get ).

  • If the GMOD Team have specified that one or more of the parameters in the table below needs to be configured, follow Steps H.2-H.4 for each of the parameters.

Parameter Name

Data Size

Data Info

Allowed Values

BkgWindowLen

uint16

The number of triggering lightcurve buffer bins to be used when calculating the background signal strength. NOTE: BkgWindowLen/SigWindowLen should be an integer prior to proceeding with triggering checks (to allow for proper signal window scaling) and the BkgWindowLen set must be less than SigWindowOffset.

1-65535 (dec)

SigWindowLen

uint16

The number of triggering lightcurve buffer bins to be used when calculating the signal strength. NOTE: BkgWindowLen/SigWindowLen should be an integer prior to proceeding with triggering checks (to allow for proper signal window scaling) and (SigWindowLen + SigWindowOffset + 1) must not exceed the max trigger buffer size

1-65535 (dec)

SigWindowOffset

uint16

The number of triggering lightcurve buffer bins to offset when calculating the signal strength. NOTE: (SigWindowLen + SigWindowOffset + 1) must not exceed the max trigger buffer size

1-65535 (dec)

SigSquaredThreshold

uint32

The square of the signal trigger threshold to be used for GRB trigger checks.

TrigBinWidth

uint16

The bin width (in milliseconds) to be used for the triggering lightcurve buffer.

1-65535 (dec)

TrigADCEventLims

uint16 [2]

The upper and lower limits to be used when assessing whether ADC event data should be considered valid for trigger checks. Row 0 is the lower limit and row 1 is the upper limit.

0-65535 (dec)

AllowedTrigTimeGap

uint16

The allowed time gap (in millseconds) between TTEs for them to be assessed within the one light curve for triggering.

0-65535 (dec)

AllowedTrigElapsedTime

unint32

The total elapsed time (in millseconds) allowed for one trigger.

ProtectTimeAroundTrig

uint16

Defines the amount of time in seconds before (row 0) and after (row 1) a trigger during which TTEs should be protected in a linear channel due the possibility of a GRB signal in the data.

0-65535 (dec)

TrigSpecTimeMultipliers

uint8 [2]

Multipliers used to define the start and integration times of trigger-associated spectrums, where Spectrum Start Time = Trigger Start Time - (Trigger Elapsed Time in seconds * [Row 0 of this Parameter]) AND where the Spectrum Integration Time = (Trigger Elapsed Time in microseconds * [Row 1 of this Parameter]). Note that Row 1 of this parameter must be greater than 0 and is initialised as 1. Additionally, given Row 0 (which defines the Spectrum Start Time), take care when setting Row 1, such that the spectrum generated actually includes the trigger.

0/1-255 (dec)

TrigLCTimeMultipliers

uint8 [2]

Multipliers used to define the start time and bin width of trigger-associated LCs, where LC Start Time = Trigger Start Time - (Trigger Elapsed Time in seconds * [Row 0 of this Parameter]) AND where the LC bin width = (Trigger Elapsed Time in milliseconds * [Row 1 of this Parameter])/number of bins. Note that Row 1 of this parameter must be greater than 0 and is initialised as 1. Additionally, given Row 0 (which defines the LC Start Time), take care when setting Row 1, such that the LC generated actually includes the trigger.

0/1-255 (dec)

TrigFoMSlope

uint16

The negative slope to be used in the FoM function that determines the Delta SigSquared required to update the beacon buffers, where (Required Delta SigSquared) = (-TrigFoMSlope x Delta End Time) + (TrigFoMIntercept).

0-65535 (dec)

TrigFoMIntercept

uint16

The y-intercept to be used in the FoM function that determines the Delta SigSquared required to update the beacon buffers, where (Required Delta SigSquared) = (-TrigFoMSlope x Delta End Time) + (TrigFoMIntercept).

0-65535 (dec)

H.2.

  • Get the parameter payload.GMOD.XXXX , where XXXX is the parameter name from the table above.

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.XXXX

Data Expected with TC

Parameter-dependant

TM Details

Data Expected from TC

XXXX ( + ACK )

H.3.

  • If the parameter value is not as desired, Set the payload.GMOD.XXXX parameter to the desired value now.

TC Details

MCS Operation

Set

Action/Param Name

payload.GMOD.XXXX

Data Expected with TC

Yes

TM Details

Data Expected from TC

No ( + ACK )

H.4.

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



I. Mode Change

I.1.

  • Get the parameter payload.GMOD.GMODMode to check which mode GMOD is currently operating in.

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.GMODMode

Data Expected with TC

No

TM Details

Data Expected from TC

GMODMode ( + ACK )

Data Size

Int4

Data Info

Mode of GMOD

Allowed Value(s)

01, 02, 03, 04, 05

Where…

GMODMode

Mode

01

Idle

02

Experiment

03

CPLD Programme

04

Safe

05

Experiment16

I.2.

  • If the mode is not as desired, Set the GMODMode parameter to the desired value now.

Important

If the Operator wishes to enter Experiment16 Mode (0x05), payload.GMOD.Protect16ChStatus should first be set to FALSE. Operators should be aware though that GMOD erases all previously generated/stored 16 Channel TTE data on entry to this mode. Therefore, the Operators should follow Section J prior to entering this mode if needed!

TC Details

MCS Operation

Set

Action/Param Name

payload.GMOD.GMODMode

Data Expected with TC

Yes

Data Size

Int4

Data Info

Mode of GMOD

Allowed Value(s)

01, 02, 03, 04, 05

TM Details

Data Expected from TC

No ( + ACK )

I.3.

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

Important

If GMOD is being left on and generating data for a long period of time, the GMOD team should be consulted about configuring the OBC to stop GMOD generating data while passing through the South Atlantic Anomaly (SAA), a region with high levels of radiation. A TimeAction component can be used to invoke an action/set a parameter based on time. The EIR-OPS-037: Set-Up a TimeAction procedure can be followed to set up two TimeActions, one to set the payload.GMOD.GMODMode to Idle (0x01) prior to SAA entry and one to set the payload.GMOD.GMODMode to Experiment (0x02) at SAA exit so GMOD starts generating data again.



J. Set Up 16 Channel TTE Streaming

J.1.


J.2.

  • Get the parameter payload.GMOD.LastPage16AddrRx several times, with ~3 seconds between each TC, to read the memory address of the last 16 channel TTE page received by the OBC from GMOD.

  • Ensure the parameter value is NOT changing between TCs, which confirms that the OBC is not currently receiving this data type from GMOD.

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.LastPage16AddrRx

Data Expected with TC

No

TM Details

Data Expected from TC

LastPage16AddrRx ( + ACK )

Data Size

uint16

Data Info

Updates with the memory address of the last 16 channel TTE page received by the OBC from the MSP.

Allowed Value

000000 - 007FFF (hex)

Expected Value(s)

Not changing between TCs

J.3.

  • Get the parameter payload.GMOD.LastPage16Addr to read the memory address of the last 16 channel TTE page stored to GMOD’s flash memory.

  • Record the value returned for use in the next step.

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.LastPage16Addr

Data Expected with TC

No

TM Details

Data Expected from TC

LastPage16Addr ( + ACK )

Data Size

uint16

Data Info

Memory address for the last stored 16 channel TTE page

Allowed Value

000000 - 007FFF (hex)

J.4.

  • Invoke the action payload.GMOD.Stream16Enable with the action argument set as the payload.GMOD.LastPage16Addr parameter value noted in the previous step.

TC Details

MCS Operation

Invoke

Action/Param Name

payload.GMOD.Stream16Enable

Data Expected with TC

MemAddr

Data Size

2 bytes

Data Info

GMOD flash memory address to stream data from

Allowed Value(s)

000000 - 007FFF (hex)

Expected Value(s)

LastPage16Addr from Step J.3.

TM Details

Data Expected from TC

No ( + ACK )

J.5.

  • Get the parameter payload.GMOD.LastPage16AddrRx several times, with ~3 seconds between each TC, to read the memory address of the last 16 channel TTE page received by the OBC from GMOD.

  • This time, ensure the parameter value is changing, which confirms that the OBC is now receiving this data type from GMOD.

TC Details

MCS Operation

Get

Action/Param Name

payload.GMOD.LastPage16AddrRx

Data Expected with TC

No

TM Details

Data Expected from TC

LastPage16AddrRx ( + ACK )

Data Size

uint16

Data Info

Updates with the memory address of the last 16 channel TTE page received by the OBC from the MSP.

Allowed Value

000000 - 007FFF (hex)

Expected Value(s)

Changing between TCs

J.6.

  • Query the parameter core.Storage.channelContent several times, with ~10 seconds between each TC, with Parameter Index in Block set to 24 (dec).

  • Ensure the returned TM, which gives the number of rows in the channel, is changing, which confirms that 16 channel TTE data is being successfully stored by the OBC.

TC Details

MCS Operation

Query

Action/Param Name

core.Storage.channelContent

Data Expected with TC

Parameter Index in Block

Data Size

4 bytes

Data Info

Channel ID

Allowed Value(s)

1 - 88 (dec)

Expected Value(s)

24 (dec)

TM Details

Data Expected from TC

Number of rows in GMOD 16Ch TTE storage channel ( + ACK )

Data Size

4 bytes

Data Info

Number of rows in GMOD 16Ch TTE storage channel

Allowed Value

0 - 65535 (dec)

Expected Value(s)

Changing between TCs


K. Turn Off GMOD

K.1.

  • Prior to power OFF, GRB triggering should be disabled. To do this, Set the payload.GMOD.GRBTriggeringEnabled parameter to 0.

TC Details

MCS Operation

Set

Action/Param Name

payload.GMOD.GRBTriggeringEnabled

Data Expected with TC

Yes

Data Size

bit1

Data Info

Enable (1) or Disable (0) GRB Triggering

Allowed Value(s)

0 - 1

Expected Value(s)

0

TM Details

Data Expected from TC

No ( + ACK )

K.2.

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


K.3.

  • Invoke the action platform.EPS.TurnOffGMOD to turn OFF GMOD.

TC Details

MCS Operation

Invoke

Action/Param Name

platform.EPS.TurnOffGMOD

Data Expected with TC

No

TM Details

Data Expected from TC

No ( + ACK )

K.4.

  • Get the parameter platform.EPS.actualSwitchStates with First row = 0 and Last row = 9 to assess whether GMOD is now OFF.

  • Ensure that PDMs 3, 6 and 9/rows 2, 5 and 8 are OFF/0.

Warning

It will take ~40 seconds for PDM 3 to return as OFF/0.

Warning

PDM 8 is drawing parasitic power. Therefore, when you Get the platform.EPS.actualSwitchStates parameter it will always read as ON/1 even when it is powered OFF.

TC Details

MCS Operation

Get

Action/Param Name

platform.EPS.actualSwitchStates

Data Expected with TC

First row, Last row

Data Size

2 bytes, 2 bytes

Data Info

The first and last rows/indexes of the parameter to get

Allowed Value(s)

0 - 9, 0 - 9

Expected Value(s)

0, 9

TM Details

Data Expected from TC

actualSwitchStates[0:9] ( + ACK )

Data Size

List[0:9] of booleans

Data Info

If actualSwitchStates[n] = 1, PDM n is ON

Allowed Value(s)

0,0,0,0,0,0,0,0,0,0 (all OFF) - 1,1,1,1,1,1,1,1,1,1 (all ON)

Expected Value(s)

X,X,0,X,X,0,X,X,0,X (PDMs 3, 6 + 9 = 0. Other PDMs may be 0 or 1)

END OF PROCEDURE