Master Command Files Dialog Menu:
                Definition of High Level Command Buttons

Updated: 3-Apr-2002: Trics V10.0 Rev E

Command files attached to the buttons of the "Run Master Command File" Menu 

    Button Name                         Master Command File Name 
    -----------                         ------------------------

    "Configure All FPGAs"           -> %CONFIG%\\Request_Configure_FPGAs.mcf
                                    (send COOR message asking for FPGA Config)

    "Initialize L1FW, L2FW, L1CT"   -> %CONFIG%\\Request_Full_Initialize.mcf
                                    (send COOR message asking for Full Init)
                           
    "Initialize SCL"                -> %CONFIG%\\Request_SCL_Initialize.mcf
                                    (send COOR message asking for SCL Init)
                                    (Note: SCL Init is surrounded by 1s min
                                     of L1FW pause before and after; 
                                     Resume only if it wasn't already paused)
                                  

    "UnNamed 0"                     -> %CONFIG%\\UnNamed_0.mcf

    "UnNamed 1"                     -> %CONFIG%\\UnNamed_1.mcf

    "UnNamed 2"                     -> %CONFIG%\\UnNamed_2.mcf


------------------------------------------------------------------------
Misc Notes (now old news):

1) We have a new directory to hold a new type of configuration files.
This is the "official" place where we keep the "standard" trics 
configuration files (as opposed to test files, lower level files, etc).

The name for this new directory depends on the site: it is 
\Trics\D0_Config at Fermilab and \Trics\MSU_Config at MSU.  

The \Trics base Directory is (has to be) on the same disk as the TRICS 
executable, which is drive "C:" on MSUL1A and D0TCC1 at the moment.

There is a new logical name (a.k.a. DOS environment variable)defined 
within TRICS for this new directory : CONFIG.
CONFIG is defined by trics to point to the site-dependent corresponding 
directory.
A file named \Trics\D0_Config\M21.PutPut can be referenced as 
"%CONFIG%/M21.PutPut" from inside any command file at fermilab.


2) The convention to use for the file extension of these new 
"Master Command Files" (a.k.a. MCF) is ".mcf"
The only commands allowed in a MCF file (at the moment) are 
to call other command files: Register IO, VME IO, CBUS IO, or 
Download FPGA command files.  
The keywords are (including the trailing colon, as usual):

    Call_Download_Fpga: "%CONFIG%\Test_download.dcf"
    Call_Reg_IO:        "%TRICS%\L1FW_SCT\reset_scalers.rio"
    Call_Vme_IO:        "%TRICS%\config\Test_Vme.vio"
    Call_CBus_IO:       "%TRICS%\config\Test_cbus.cio"

Like for ALL other command file keywords, they are NOT case sensitive.
(cf. the "Syntax Rules" button on the Master Command Files Dialog
for more details)


3) Any "sub-file" that is called from a master command file (or called 
by lower sub-files) should include the full path name of the file to 
execute.  This is mostly an issue for the files directly attached to 
buttons, as there are no chance to pick up a default directory setup in
advance if the directory was not hand selected like we were used to 
until now.

If that becomes an issue, we can 
    - add a "set default directory command"
    - force the default directory to the directory 
    of the MCF every time (or while) it is invoked


4) If an error occurs while processing a MCF, execution is aborted
and the error is flagged with red messages on the console window.

This is the way all command files are behaving. 
The only exception is with the Download command files where we 
flag the error but continue the download until the end of the DCF.
It may not be very apparent, but if a Register IO command fails, 
the following commands are not executed.

We can of course change the definition and make any/all types
of command files behave differently.