HERMES Testing Environment

Local simulation of REVERB's EPS, SATT-4 Radio, Iridium Radio, and Antenna Deployer.

---

Highly

Expandable

REVERB

Mechanical

Environment (for)

Simulation

---

Generators

Generators describe what the behavior of the modules on the satellite will be. This influences what kind of data pFS will read and put into the SFR.

Generator name	APRS	Iridium	Antenna Deployer	EPS
BOOT	No uplink
STARTUP	Uplink when downlink
NORMAL	Uplink commands sent through runstack / interactive
LOW_POWER	Uplink commands sent through runstack / interactive
DANGER	APRS serial throws exception

Generator Shifts

If the generator is changed during a run of HERMES, here is how each module will respond

APRS

STARTUP -> NORMAL OR STARTUP -> LOW_POWER

HERMES will send a message to pFS to indicate antenna deploy was successful

ANY -> DANGER

pFS will not be able to interface with the SATT-4

Commands

Commands are run through the interactive shell or runstack. They help pull out information from pFS to examine what is actually occurring during simulations.

Headers	Args	What it does
print	module	Prints all the stuff in the module
sfr	state field name	Prints the value of the state field in the SFR
flag	error flag name	Prints the status of the error flag in the SFR
action	action name	Triggers the action
get_state	n/a	Gets the mode pFS is in
change_generator	generator name (specified above)	Shifts the generator used by Hermes modules
send	radio command	Sends the given command to pFS via the given radio (\n added automatically if not present)

Actions

Actions are events which could occur during flight. Triggering an action simulates the event in orbit. Actions can be run via commands or the runstack.

Module + Action name	What it does
APRS;disconnect	The APRS serial port will always throw an error when used
APRS;connect	The APRS serial port will work as expected
EPS;brownout	Simulates a brownout event where the battery voltage drops significantly