On CASSINI we only used GSEOS for the MIMI instrument. In this scenario GSEOS is used also throughout all
mission phases. The initial setup was I&T in the bench test configuration. Here we customized a
driver for the Ballard Technologies MIL-1553 board for the use with GSEOS. The driver is a universal
BIOS that allows to configure the bus timing with a simple configuration file.
We tried to get a end-to-end test system, on CASSINI this involved the generation of
SASF files and IEBs. SASF files allow the execution of instrument commands in a
time tagged fashion and are a spacecraft wide scripting tool. GSEOS can read and execute
SASF files as well as generate these files.
Generation of SASF files is done by point-and-clicking on the instrument commands which are
laid out in a hierarchical GSEOS menu. Each invocation of an instrument command is logged to
a log file with markup. A parser can read this marked up log file and generate the
according SASF script. This script can then be run directly in GSEOS for testing purposes
and delivered to JPL upon satisfactory execution.
Besides interfacing to the 1553 hardware in bench test configuration, the MIMI GSEOS can also
communicate to the MOC servers. We can retrieve archived and realtime playback data. This allows
us a very quick turn-around time to determine system functionality. The advantage of this setup is
the familiarity of the user interface throughout all development and operation cycles.
We recently also implemented alarm monitors that can notify users via email and pager.