User manual

MEX ASPERA-3
Ref.:
ME-ASP-MA-0002
Issue:
Issue 1 Rev. 4
Date:
15/2/2002
Page:
Page 43 of 58
ASPERA-3 EGSE User Manual
IFSI
CNR
3.2.3.2
ASPERA telecommand
These commands execute a CCS Telecommand Request [RD1] using a private ASPERA acronym.
Each Aspera telecommand can be defined as a line in the file Mex/CmdLut/TeleCommandSLT.txt (see
appendix 6.3), the line is composed by three fields possibly followed by comments (“; any comment”):
ASPERA TC acronym RPRO TC symbolic name Parameters string
With:
ASPERA TC acronym: Any convenient name for the telecommand, usually should be the
same acronym used at ILT.
RPRO TC symbolic name: The symbolic name of the command as reported in the CCS
database.
Parameters string: Any string of “constant” parameters
The requesting command is composed by the ASPERA TC acronym
possibly followed by a string of
“variable” parameters.
The program look in the Mex/CmdLut/TeleCommandSLT.txt file for a line beginning with the given
ASPERA TC acronym
. If such a line exists, the program construct and transmit a CCS telecommand
request (TC-R SYM_TC) using the corresponding RPRO TC symbolic name
(in field3a) and
Parameters string
in the variable length data field. The string of parameters in the requesting command
(if any) is appended to the Parameters string.
Example:
If in
TeleCommandSLT.txt file exists a line like:
ASPXXX ZS00004 R0001:=NO,R0008:= ;just a non existent command
The requesting command:
ASPXXX 51,R0012:=6
is translated as a CCS telecommand request (TC-R SYM_TC) with:
TC symb. name = ZS00004
Data parameters = R0001:=NO,R0008:=51,R0012:=6