This chapter outlines the general command flow and configuration in GSEOS.
Defining your commands
You start out defining your commands by creating command definition file(s). Once you have created the command definitions you have to load them into GSEOS. You can do this manually by opening your file with the File/Open menu. However, if you plan on automatically loading your command definition on system startup you can enter the file in the gseos.ini configuration file [Config] section.
Accessing your commands
Once your commands are defined you can inspect them using the GSEOS Explorer. To easily access your commands you can add them to a command menu for hierarchical access or place the command on a command button with inclusion on a screen.
To issue your commands you will use the GseosCmd.ExecCmd() function. This function takes your command as a string and queries for any missing arguments, compiles the command, and generates the CmdString block. If this is a critical command it will also pop up a dialog box asking the user to acknowledge the command before sending it. The CmdString block will be intercepted by the Command Decoder which will generate a BinCmd block containing the proper binary command data. This block will in turn be processed by the BIOS which issues the binary command as required by your instrument.
Below is an example from a command menu file:
Menuitem Set &Time, GseosCmd.ExecCmd("EGSE_SET_TIME()")
Menuitem Set &Subsecond Time, GseosCmd.ExecCmd("EGSE_SET_SUBSECOND_TIME()")
If you disable the command decoder (shown below) commanding will effectively be disabled (unless you generate a BinCmd block by some other means like playing it back from the recorder).
