User manual

MEX ASPERA-3
Ref.:
ME-ASP-MA-0002
Issue:
Issue 1 Rev. 4
Date:
15/2/2002
Page:
Page 41 of 58
ASPERA-3 EGSE User Manual
IFSI
CNR
• The configuration-tabbed dialog shows two extra windows, the most important is the TM
request used to manually request the telemetry packets to the CCS.
• The first window in the Status/HK tabbed dialog is slightly different and shows the full history
of commands flow from/to CCS. In the figure is shown the initial automatic command
exchange used by CCS to initiate the connection to the SCOE:
CCS send SCOE Reply
CTL CS_START
CTL CS_STATUS 0
TIMESYNC 2000,362 …..
TIMEREPORT
TIME REPORT 2000,362 ….
3.2.3 Command List
Here again there are few differences with ILT:
• The ‘,’ is not allowed as separator in command parameters as the comma character is used in
the CCS parameters strings as separator. Never use a space separator in CCS parameters string.
• There are no Low Level commands as the mexilt program is not used.
• A new set of CCS Protocol Commands is implemented.
• Only few of SCOE internal commands are meaningful:
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.
• ASPERA telecommand: these commands are composed by an acronym possibly followed by
parameters and generate a standard RPRO telecommand request (TC-R SYM_TC). The
commands are defined in /Mex/CmdLut/TeleCommandSLT.txt and mustn’t be modified.
• CCS protocol command: these commands are composed by an acronym possibly followed by
parameters and generate a standard RPRO packet command. The commands are defined in
/Mex/CmdLut/Rpropkt.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/MacroSLT.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 mustn’t be modified.