!------------------------------------------------------------------------------ ! This file holds a list of Master Command File requests ! Comments start with an exclamation mark ("!") anywhere on a line. ! See end of file for more syntax information. !------------------------------------------------------------------------------ ! Revision: 11-Dec-2003 ! This file is a template ! and a list of the syntax rules for Master Command Files Call_Download_Fpga: "%CONFIG%\Test_download.dcf" Call_Reg_IO: "%TRICS%\L1FW_SCT\reset_scalers.rio" Call_Vme_IO: "%CONFIG%\Test_Vme.vio" Call_CBus_IO: "%CONFIG%\Test_cbus.cio" Call_Self_Msg: "%CONFIG%\Test_coor_commands.msg" Call_TT_Info: "%CONFIG%\Test_Dac_Pedestals.tti" Send_Msg_To_Self: "L1FW_Spec_Trig 0 Coor_Enable" Ignore_L1CT: 1 Serial_DAQ_Ctrl: 2 Call_File: \users\default\another.mcf !------------------------------------------------------------------------------ ! 11-Dec-2003 ! * Recommended file extension is ".MCF" (but not required). ! ! Syntax rules: ! ! - Blank lines are ignored. ! ! - Comments start after an exclamation mark ("!") anywhere on a line. ! ! * Recognized Keywords are (with colon required) ! Call_Download_Fpga: (Execute the specified FPGA Download Command File) ! Call_Reg_IO: (Execute the specified Register IO Command File) ! Call_Vme_IO: (Execute the specified VME IO Command File) ! Call_CBus_IO: (Execute the specified CBUS IO Command File) ! Call_Self_Msg: (Execute the specified Self Message Command File) ! Call_TT_Info: (Execute the specified Trig Tower Info Command File) ! Send_Msg_To_Self: (Send TRICS the specified COOR->L1FW command) ! Ignore_L1CT: (Include/Ignore L1 Calorimeter Trigger) ! Serial_DAQ_Ctrl: (Set Serial DAQ Control Method; allowed values are ! 0= Executing .TTI Remembers Values WITHOUT Programming DACs ! Init L1CT Will NOT Program DACs ! 1= Executing .TTI Remembers Values WITHOUT Programming DACs ! Init L1CT Programs DACs Using Remembered Values ! 2= Executing .TTI Remembers Values AND Program DACs ! Init L1CT Will NOT Program DACs ! 3= Executing .TTI Remembers Values AND Program DACs ! Init L1CT Programs DACs Using Remembered Values ! Reminder: The default behavior of Trics V10.5.A is #2 ) ! Call_File: (Recursive call to another Master Command File) ! MilliSecond_Sleep: (Suspend execution of the command file) ! ! - Keywords are NOT case-sensitive. ! ! - Each Keyword must be followed by one and only one character string. ! ! - a Keyword and its matching Value may be separated by any number of spaces, ! and/or Tabs, but must appear on the same line. ! ! - Successive Keyword/Value pairs may be separated by any number of spaces, ! Tabs and/or Carriage_Returns (blank lines), or comments. ! ! * The "Call_xxxxx" keywords cause the specified command file to be ececuted. ! The Syntax rules and allowed keywords within the called file depend on ! the type of file being called. Only the syntax proper to the type of ! command file called is allowed within the called file. ! ! * In order to limit the total number of command files, Master Command Files ! can also directly send COOR commands without needing to call an external ! Self Message Command File. ! The "Send_Msg_To_Self:" keyword causes the specified COOR to L1FW Command ! Message to be send to TRICS_II on the dedicated ITC port. ! cf. Syntax_Rules_Self_Message.Msg for more details on using this keyword/ ! ! - The "MilliSecond_Sleep:" Keyword causes the execution of the command file ! to be suspended for the number of milliseconds specified in the associated ! value (integer values only). ! ! - The "Ignore_L1CT" Keyword allows changing the system control flag that ! describes whether the L1 Calorimeter Trigger is part of the system or not. ! Only the values 0 and 1 are allowed with this Keyword. ! "Ignore_L1CT: 1" ignores L1CT (we can put this line in the PRE-init-auxi). ! "Ignore_L1CT: 0" includes L1CT (which is the default). ! ! - The "Call_File" Keyword causes a recursive call to read the specified ! Master Command File. ! ! - Full local Keyword/Value context present before the Call_File Keyword ! is still valid after. i.e. Context changes made in the Called file are ! NOT propagated back to the Calling file. ! ! - The syntax rules within a called file are the same as described here. ! The local Keyword/Value context present before the Call_File Keyword ! is imported into the Called File. i.e. You can define some Keyword Values ! in the Calling File which will be valid inside the Called File. ! !------------------------------------------------------------------------------ ! * Symbols have limited purpose in the context of Master Command Files ! (they can only be used with the "MilliSecond_Sleep" keyword or to ! propagate into called files). ! ! Symbols may be defined and used in command files. ! A symbol name must start with a dollar sign "$". ! ! A symbol is defined by giving it a numeric value. ! A symbol is defined using a Keyword/Value syntax where the Keyword is ! the symbol's name, starting with its own dollar sign but with an additional ! equal character appended to the end of the symbol name, while the value ! is the desired symbol value. ! e.g. To define a symbol named "$Slot_AONM" and give it a value "5" ! enter the following: ! $Slot_AONM= 5 ! The equal sign "=" is required and must appear directly after the last ! character of the symbol name, with no space or tab in-between. ! Any number of spaces, or tabs may appear between the symbol definition and ! its value, but the symbol and its value must appear on the same line. ! Previously defined symbols can be re-defined to change their value. ! Previously defined symbols cannot be un-defined. ! ! A symbol may be used anywhere a value is required, i.e. in any Keyword/Value ! pair and the symbol value will be substituted. e.g. ! Slot: $Slot_AONM ! A symbol must have been defined before it can be used. ! There are no predefined symbols. ! Symbols are NOT case sensitive. ! Symbol names may include any alpha numeric characters (e.g. _[(}./$< ), ! (but no space, tabs, or end of line). For clarity one should avoid ! using embedded quotation marks, equal signs, colon. ! A symbol value may be used to define another new symbol. ! ! All symbols defined before a "Call_File" Keyword are propagated into ! the Called File. i.e. You can define symbols in the Calling File ! and use those symbols (or modify them) inside the Called File. ! Symbols created or modified inside a Called File are NOT propagated ! back to the Calling file. !------------------------------------------------------------------------------