Writing Spacecraft Events

Spacecraft events change component properties, configure supported error models, or invoke supported guidance and rendezvous behavior.

Direct component change

{
  "Enabled": true,
  "Name": "Low Bit Rate",
  "Time": 100.0,
  "Repeat": false,
  "Interval": 1.0,
  "Type": "Spacecraft",
  "Assets": [],
  "Target": "Transmitter",
  "Data": {
    "Bit Rate": 500.0
  }
}

Studio first tries the full Target as a component name. Keep authored component names stable.

Targeting an error model

Component-or-class name - Error model class

Example:

{
  "Enabled": true,
  "Name": "Packet Corruption",
  "Time": 300.0,
  "Repeat": false,
  "Interval": 1.0,
  "Type": "Spacecraft",
  "Assets": [],
  "Target": "Transmitter-TransmitterPacketCorruptionErrorModel",
  "Data": {
    "Packet Corruption Fraction": 0.2
  }
}

Common recipes

Storage full

"Target": "Storage",
"Data": {
  "Capacity": 100000
}

Storage corruption

"Target": "Storage",
"Data": {
  "Corruption Fraction": 0.1,
  "Corruption Intensity": 0.2
}

Solar-panel degradation

"Target": "SolarPanel-SolarPanelDegradationErrorModel",
"Data": {
  "Degradation Rate": 100000.0
}

Battery intermittent connection

"Target": "Battery-IntermittentConnectionErrorModel",
"Data": {
  "Intermittent Mean": 1,
  "Intermittent Std": 2
}

Battery leakage

"Target": "Battery-BatteryLeakageErrorModel",
"Data": {
  "Power Leakage Rate": 0.001
}

Guidance noise

"Target": "Computer-GuidanceComputerNoiseErrorModel",
"Data": {
  "Noise Factor": 0.005,
  "Randomize": true
}

Reaction wheel stuck

"Target": "Reaction Wheels",
"Data": {
  "Stuck Index": 0
}

Use the corresponding nominal or reset preset to restore the intended state when the exercise requires recovery.

Sensor fault states

GPS Sensor, Magnetometer, EM Sensor, and Gyroscope can accept supported fault-state values. Use the preset for that sensor and installed Studio version rather than assuming one numeric fault value applies to every sensor.

Hyphens in component names

Studio tries the full target name before interpreting a hyphen as a component/model separator. A component named Thruster 4 (-X) can therefore still be targeted by its full name.

Testing a fault

  1. test one event at an early time
  2. confirm the event is listed in Admin
  3. run past the trigger
  4. confirm the intended component changes
  5. confirm unrelated spacecraft do not change
  6. reset
  7. move the event to its final time

Use relevant component references when selecting values:

Next, configure environmental or packet effects.