User manual

MEX ASPERA-3
Ref.:
ME-ASP-MA-0002
Issue:
Issue 1 Rev. 4
Date:
15/2/2002
Page:
Page 26 of 58
ASPERA-3 EGSE User Manual
IFSI
CNR
3.1.3 Command List
As a general rule all commands are case insensitive
Commands instructions are coded as a single text line beginning with the command ID (acronym) and
followed by parameters (if any):
ID [p1 p2 … pn]
ID and parameters are separated by ‘space’, ‘tab’ or ‘,’ (comma separator is not allowed in commands
at system level).
Characters following ‘;’ or ‘#’ are comments.
Lines of comments beginning with ‘#’ in column one, are saved in the command archive file.
Hexadecimal constants use the C coding convention (i.e. 0x5A5A).
There are five types of commands each type with its own definition file:
• SCOE internal: These commands are used to set scoe program flags/variable (which remain
constant up to the next setting). The commands are defined in the first section of
/Mex/include/dspcmtbl.h and mustn’t be modified.
• Low level: these commands are sent directly to the mexilt module and operate at the lowest
level. The commands are defined in second section of /Mex/include/dspcmtbl.h and mustn’t be
modified.
• High level: these commands are composed by an acronym possibly followed by parameters and
generate a standard packet telecommand. The commands are translated in the scoe module to
low level commands and transmitted to mexilt. The commands are defined in
/Mex/CmdLut/TeleCommand.txt and are intended to be modified by the user.
• Macro: these commands just substitute the macro acronym with whatever follows in the macro
definition line. A macro acronym may be followed by parameters in that case the parameters
are appended at the end of the macro translation line. The commands are defined in
/Mex/CmdLut/Macro.txt and are intended to be generated/modified by the user.
• Command sequence instructions: these are pseudo programming-language instructions that
control the flow of commands in the sequences. The commands are defined in
/Mex/CmdLut/LocProc.txt and in /Mex/include/dspcmtbl.h and mustn’t be modified.
The following flow diagram shows the command verification and implementation algorithm