Introduction

a) a Camac module (CFICC- CFI CAMAC card)

or b) a DRX11T Q-bus interface and Edinburgh card (QFI) or the equivalent UNIBUS cards

The CFIFC/CFICC combination is known as 'CFI'; the CFIFC/DRX11T combination as 'QFI'.

The program is a menu-driven program that accepts a number of commands. This program uses the CERN libraries and most of the user-callable subroutines are implemented (although not all are fully tested).

The program requests commands from the user with the prompt 'QFI>' or 'QFI>' depending on the hardware combination. Enough letters of the command must be typed so that it is unique.

A number of the commands require parameters, and if these are not supplied on the command line, they will be prompted for. It is recommended that users unfamiliar with this program and the FASTBUS and CERN calls use the prompted input mode, since the parameters must be entered in the correct order.

Additional Information on:

• EXAMPLES

CFIMENU has been modified and updated Sept-Oct 1990 as follows: <ul> <li> Support for access to remote crates (connected via an SSP cable segment) has been added.

<li> CFIMENU help file (i.e. this file) has been updated. </ul>

<b> Older updates:</b> <ul> <li>Block transfers to and from CAMAC are now supported. More than one CAMAC crate can be accessed more easily. The CAMAC commands have been extensively modified. This means old command files that use the CAMAC command need to be altered to run with the new version.

<li> CFIMENU commands can now be entered with only enough letters so that they are unique - they need no longer be typed in full. The same applies to BRDRV and CAMAC commands.

<li> CAMAC commands can now be entered in command files - see HELP CAMAC COMMAND_FILE

<li> Commands BRDRV and OPTION can also now appear in command files - see (e.g.)HELP BRDRV COMMAND_FILE.

<li> Output on the screen for block reads can be turned on or off with a flag (command BLKFLG). See HELP BLKFLG for details.

<li> LUNs have been altered to be VAX compatible

<li> Repeating of CFIMENU FASTBUS commands has now been implemented. This is useful for debugging. Also repeating of command files is supported (see HELP REPEAT).

<li> A flag OUTFLG has been provided to switch off output of data to the screen, which is useful for speeding up the repetion of FASTBUS operations (see HELP OUTFLG).

<li> Repeating a CAMAC command has been implemented. See HELP CAMAC LOOP.

<li> CAMAC CNAF command will repeat the last command on entering carriage return instead of the values N,A,F. See HELP CAMAC CNAF. </ul>

FCAM

Initializes the list processor software and sets up the hardware configuration (or PATH). FCAM does not issue a CAMAC C or Z nor does it issue a Fastbus RB (reset bus). It initiates no Fastbus activity.

This command is performed automatically by CFIMENU on entering the program.

FMINI

Initialize the CFI Fastbus Module to operate as a Fastbus master. It does not issue a CAMAC C or Z, and does not issue a Fastbus RB (reset bus).

This command is performed automatically by CFIMENU on entering the program after the FCAM command.

FREL

Fastbus Release Bus - if AS and AK lines are left high (on error), either this command or FMINI will reset them.

Note - this command works only in the LOCAL crate.

FLIST

If the required parameter is not supplied, it will be prompted for.

Initialize a CFI list. This routine MUST be called before any routine that uses DELAYED or LIST MODE.

LISTID must be supplied as a decimal number between 1 and 64, or a USER DEFINED NAME

This routine will set up the option FOUSER=1 (i.e. delayed processing enabled).

All FASTBUS commands typed after FLIST and before the command FLEX (execute list) will form part of the list, and will not be executed until FLEX is sent.

A CFIMENU internal flag, FLISTP, is set by the command FLIST, and cleared by FLEX. This flag causes suppression of the usual output on the terminal screen of data read from FASTBUS. If the command FLFIL (see HELP FLFIL) is used to terminate the list rather than FLEX, the flag FLISTP will not be cleared. In this case, the FLISTP must be cleared by the user with the command CLRLST.

(If immediate processing is used, FLIST is called internally.)

Additional Information on:

• Examples

If the required parameter is not supplied, it will be prompted for.

For use in stored/list mode, i.e. when option FOUSER=1. Fills the end-of-list element and executes the list. The option FOUSER is automatically cleared to re-enable immediate processing, and the internal CFIMENU flag FLISTP is also cleared.

LISTID must be supplied as a decimal number between 1 and 64, or a USER DEFINED NAME . A list of LISTID must have been previously initialized using FLIST.

A list may be executed any number of times by repeating the FLEX command.

A CFIMENU internal flag, FLISTP, is set by the command FLIST, and cleared by FLEX. This flag causes suppression of the usual output on the terminal screen of data read from FASTBUS. If the command FLFIL (see HELP FLFIL) is used to terminate the list rather than FLEX, the flag FLISTP will not be cleared. In this case, the FLISTP must be cleared by the user with the command CLRLST.

Additional Information on:

• Examples

If the parameters are not supplied, they will be prompted for.

For use in stored/list mode, i.e. when option FOUSER=1. Fills the next list element in the list with the 2 numbers, ELEM1, ELEM2 supplied by user. A list of LISTID must have been previously initialized using FLIST.

The list elements are actually 8-byte F-Codes defined by CERN to build up various FASTBUS operations. See CERN software documentation for listings of F-Codes. The F-Codes for a list are stored in the internal array CNTRL, and this array may be dumped out by using the command STATUS (see help STATUS).

<b>LISTID</b> must be supplied as a decimal number between 1 and 64, or a USER DEFINED NAME . <b>ELEM1</b> contains the F-code, and must be a number (in hexadecimal) or a USER DEFINED NAME. <b>ELEM2</b> contains data or is dummy, and must be a number (in hexadecimal) or a USER DEFINED NAME.

A CFIMENU internal flag, FLISTP, is set by the command FLIST, and cleared by FLEX. This flag causes suppression of the usual output on the terminal screen of data read from FASTBUS. If the command FLFIL is used to terminate the list rather than FLEX, the flag FLISTP will not be cleared. In this case, the flag FLISTP must be cleared by the user with the command CLRLST.

This routine would be used only for test and debugging purposes.

FELEM

If the parameters are not supplied, they will be prompted for.

FELEM calls FLIST,FLFIL and FLEX to generate and immediately execute the F-Code supplied in ELEM1,ELEM2. F-Codes are codes defined by CERN used internally to build up various FASTBUS operations.

LISTID must be supplied as a decimal number between 1 and 64, or a USER DEFINED NAME . ELEM1 contains the F-code, and must be a number (in hexadecimal) or a USER DEFINED NAME. ELEM2 contains data or is dummy, and must be a number (in hexadecimal) or a USER DEFINED NAME.

This routine would be used only for test and debugging purposes.

CLRLST

A CFIMENU internal flag, FLISTP, is set by the command FLIST, and cleared by FLEX. This flag causes suppression of the usual output on the terminal screen of data read from FASTBUS. If list processing is selected, and not terminated by FLEX (for example if the command FLFIL (see HELP FLFIL) is used , or a command file is aborted that has set the CFI into list mode) the CFI may be left in list mode with the flag FLISTP set.

In this case, output to the terminal will be suppressed by the flag FLISTP, and all commands will be added to a list and not executed. To recover from this condition, the FLISTP must be cleared by the user with the command CLRLST, which also clears the option FOUSER.

FWAIT

If the required parameter is not supplied, it will be prompted for.

Set up software timeout for data transfers to CFI (i.e. using DATA channel).In the case of CFI/CAMAC hardware, a large number gives less chance of a time-out. If FWAIT is not called, default value of TIMER is 100. The QFI timeout cannot be changed except as below.

For both QFI and CFI, a value of zero for TIMER will turn off the timeout, and is thus useful for single stepping.

NOTE - use only in the LOCAL crate (no support for remote crates)

FTWAIT

If the required parameter is not supplied, it will be prompted for.

Set up software timeout for command transfers to CFI (i.e. using COMMAND channel). In the case of CFI/CAMAC hardware, a large number gives less chance of a time-out. If FWAIT is not called, default value of TIMER is 5000. The QFI timeout cannot be changed except as below.

For both QFI and CFI, a value of zero for TIMER will turn off the timeout, and is thus useful for single stepping.

NOTE - use only in the LOCAL crate (no support for remote crates)

FMODE

If the parameters are not supplied, they will be prompted for.

FMODE is used to control interface operation. The parameters all take the default values if FMODE is not called. To show the present values of the parameters, use command SHOMOD.

Data transfer mode control

 TMODE: 0 = Stored output data, stored input data (default)
 	1 = Stored output data, direct input data 
        -1 = Direct output data, stored input data (default)
  

(N.B. WRITE to FASTBUS ==> OUTPUT data, READ from FASTBUS ==> INPUT data )

CFI Block transfer control

 DMALAM: 0 = DMA transfers not used (default)
 PDP/VAX # = Station no. of End-LAM source with prog. LAM grader
 	  = GL No. of End-LAM if not prog. LAM grader
  

List synchronisation control

SYNCH: 0 = List execution NOT synchronised to front panel (default); 1 = List execution synchronised to front panel signal

List execute loop control

 EXLOOP: 0 = CFI Reply sent without execution
 	1 = Execute list once (Default)
 	N = Execute list N times
 

List load/execute control

 EXLOAD: 0 = load and execute (default)
 	1 = execute without loading
        -1 = load without execution
 

List check control

NOCHEK: 0 = check all buffer lengths associated with list (default) 1 = do not check buffer lengths

SHOMOD

SHOMOD is used to show the present values of the parameters that control interface operation. These parameters can be changed using the command FMODE. The parameters all take the default values if FMODE is not called.

Data transfer mode control

TMODE: 0 = Stored output data, stored input data (default) 1 = Stored output data, direct input data 2 = Direct output data, stored input data (default)

CFI Block transfer control

DMALAM: 0 = DMA transfers not used (default) PDP/VAX # = Station no. of End-LAM source with prog. LAM grader = GL No. of End-LAM if not prog. LAM grader

List synchronisation control

SYNCH: 0 = List execution NOT synchronised to front panel (default) 1 = List execution synchronised to front panel signal

List execute loop control

EXLOOP: 0 = CFI Reply sent without execution 1 = Execute list once (Default) N = Execute list N times

List load/execute control

EXLOAD: 0 = load and execute (default) 1 = execute without loading -1 = load without execution

List check control

NOCHEK: 0 = check all buffer lengths associated with list (default) 1 = do not check buffer lengths

FCMRP

If the parameters are not supplied, they will be prompted for.

FCMRP sends a COMMAND to the CFI (ICOMM), and waits for and reads the REPLY (IREP).

FARB

Parameter: ARBL

If the required parameter is not supplied, it will be prompted for.

FARB set the arbitration level to ARBL for use during succeeding Arbitration cycles. No FASTBUS operation is performed.

If ARBL = 0, the master asserts GK without arbitration ARBL > 0, Master obeys the AI protocol ARBL < 0, master does not obey AI protocol

Note - this command works only in the LOCAL crate.

FREQ

FREQ requests and participates in an asbitration cycle at level ARBL. To change ARBL, use FARB.

Note - this command works only in the LOCAL crate.

FLOOP

If the required parameter is not supplied, it will be prompted for.

Sets EXLOOP the loop execution counter. EXLOOP defaults to 1 if FLOOP not called. (EXLOOP also can be set by FMODE).

FBYTE

If the required parameter is not supplied, it will be prompted for.

Sets NBYTE the software transfer count byte width. If not called, NBYTE defaults to 1.

FRC

FRC : FASTBUS Single word read CSR space.

If the parameters are not supplied, they will be prompted for.

Parameters:

PRIMAD is the primary address of the module, and must be a number (in hexadecimal) or a DEFINED PRIMARY ADDRESS (see SHODEF) or a USER DEFINED NAME (see SHODEF, DEFINE). For a module in a REMOTE crate (connected with an SSP cable segment) it must contain the BSI routing information (see Help ROUTING).

SECAD is the secondary address of the module, and must be a number (in hexadecimal) or a USER DEFINED NAME.

If PRIMAD is less than FF (hex), the operation will be performed in the local (master) crate (i.e. the crate that contains the CFIFC - the CFI FASTBUS card) using the CERN software calls. If PRIMAD is larger than FF (hex), the operation will be performed in one of the remote crates (connected by a cable segment via SSPs) according to the BSI routing information contained in PRIMAD (see HELP ROUTING for more information)

Additional Information on:

• Examples

FRD : FASTBUS Single word read Data space.

If the parameters are not supplied, they will be prompted for.

Parameters:

PRIMAD is the primary address of the module, and must be a number (in hexadecimal) or a DEFINED PRIMARY ADDRESS (see SHODEF) or a USER DEFINED NAME (see SHODEF, DEFINE). For a module in a REMOTE crate (connected with an SSP cable segment) it must contain the BSI routing information (see Help ROUTING).

SECAD is the secondary address of the module, and must be a number (in hexadecimal) or a USER DEFINED NAME.

If PRIMAD is less than FF (hex), the operation will be performed in the local (master) crate (i.e. the crate that contains the CFIFC - the CFI FASTBUS card) using the CERN software calls. If PRIMAD is larger than FF (hex), the operation will be performed in one of the remote crates (connected by a cable segment via SSPs) according to the BSI routing information contained in PRIMAD (see HELP ROUTING for more information)

Additional Information on:

• Examples

FWC : FASTBUS Single word write CSR space.

If the parameters are not supplied, they will be prompted for.

PRIMAD is the primary address of the module, and must be a number (in hexadecimal) or a DEFINED PRIMARY ADDRESS (see SHODEF) or a USER DEFINED NAME (see SHODEF,DEFINE). For a module in a REMOTE crate (connected with an SSP cable segment) it must contain the BSI routing information (see Help ROUTING).

SECAD is the secondary address of the module, and must be a number (in hexadecimal) or a USER DEFINED NAME.

IOBUF is the single word (32 bits) to be written to the module. It must be a number (in hexadecimal) or a USER DEFINED NAME.

If PRIMAD is less than FF (hex), the operation will be performed in the local (master) crate (i.e. the crate that contains the CFIFC - the CFI FASTBUS card) using the CERN software calls (by default). If PRIMAD is larger than FF (hex), the operation will be performed in one of the remote crates (connected by a cable segment via SSPs) according to the BSI routing information contained in PRIMAD (see HELP ROUTING for more information)

Additional Information on:

• Examples

FWD : FASTBUS Single word write Data space.

If the parameters are not supplied, they will be prompted for.

Parameters:

PRIMAD is the primary address of the module, and must be a number (in hexadecimal) or a DEFINED PRIMARY ADDRESS (see SHODEF) or a USER DEFINED NAME (see SHODEF, DEFINE). For a module in a REMOTE crate (connected with an SSP cable segment) it must contain the BSI routing information (see Help ROUTING).

SECAD is the secondary address of the module, and must be a number (in hexadecimal) or a USER DEFINED NAME.

IOBUF is the single word (32 bits) to be written to the module. It must be a number (in hexadecimal) or a USER DEFINED NAME.

If PRIMAD is less than FF (hex), the operation will be performed in the local (master) crate (i.e. the crate that contains the CFIFC - the CFI FASTBUS card) using the CERN software calls (by default). If PRIMAD is larger than FF (hex), the operation will be performed in one of the remote crates (connected by a cable segment via SSPs) according to the BSI routing information contained in PRIMAD (see HELP ROUTING for more information)

Additional Information on:

• Examples

FRDB: FASTBUS block read of Data space.

If the parameters are not supplied, they will be prompted for.

Parameters:

PRIMAD is the primary address of the module, and must be a number (in hexadecimal) or a DEFINED PRIMARY ADDRESS (see SHODEF) or a USER DEFINED NAME (see SHODEF, DEFINE). For a module in a REMOTE crate (connected with an SSP cable segment) it must contain the BSI routing information (see Help ROUTING).

SECAD is the secondary address of the module, and must be a number (in hexadecimal) or a USER DEFINED NAME.

MAXLEN is the maximum number of transfers (i.e. number of 32-bit words) to be read from FASTBUS (in DECIMAL). The block read will end on either MAXLEN being reached, or an SS=2 (end of block) from the slave module. MAXLEN must be supplied as a decimal number between 1 and 500, or a USER DEFINED NAME .

If PRIMAD is less than FF (hex), the operation will be performed in the local (master) crate (i.e. the crate that contains the CFIFC - the CFI FASTBUS card) using the CERN software calls (by default). If PRIMAD is larger than FF (hex), the operation will be performed in one of the remote crates (connected by a cable segment via SSPs) according to the BSI routing information contained in PRIMAD (see HELP ROUTING for more information)

Additional Information on:

• Examples

FRCB: FASTBUS block read of CSR space.

If the parameters are not supplied, they will be prompted for.

Parameters:

PRIMAD is the primary address of the module, and must be a number (in hexadecimal) or a DEFINED PRIMARY ADDRESS (see SHODEF) or a USER DEFINED NAME (see SHODEF, DEFINE). For a module in a REMOTE crate (connected with an SSP cable segment) it must contain the BSI routing information (see Help ROUTING).

SECAD is the secondary address of the module, and must be a number (in hexadecimal) or a USER DEFINED NAME.

MAXLEN is the maximum number of transfers (i.e. number of 32-bit words) to be read from FASTBUS (in decimal). The block read will end on either MAXLEN being reached, or an SS=2 (end of block) from the slave module. MAXLEN must be supplied as a decimal number between 1 and 500, or a USER DEFINED NAME.

If PRIMAD is less than FF (hex), the operation will be performed in the local (master) crate (i.e. the crate that contains the CFIFC - the CFI FASTBUS card) using the CERN software calls (by default). If PRIMAD is larger than FF (hex), the operation will be performed in one of the remote crates (connected by a cable segment via SSPs) according to the BSI routing information contained in PRIMAD (see HELP ROUTING for more information)

Additional Information on:

• Examples

FWDB: FASTBUS block write to Data space.

If the parameters are not supplied, they will be prompted for.

Parameters:

PRIMAD is the primary address of the module, and must be a number (in hexadecimal) or a DEFINED PRIMARY ADDRESS (see SHODEF) or a USER DEFINED NAME (see SHODEF,DEFINE). For a module in a REMOTE crate (connected with an SSP cable segment) it must contain the BSI routing information (see Help ROUTING).

SECAD is the secondary address of the module, and must be a number (in hexadecimal) or a USER DEFINED NAME.

MAXLEN is the maximum number of transfers (i.e. number of 32-bit words) to be written to FASTBUS. MAXLEN must be supplied as a decimal number between 1 and 500, or a USER DEFINED NAME.

OUTBUF is the data (in hex.) to be written to the FASTBUS module. A number MAXLEN of 32-bit words will be requested and used to fill OUTBUF.

If PRIMAD is less than FF (hex), the operation will be performed in the local (master) crate (i.e. the crate that contains the CFIFC - the CFI FASTBUS card) using the CERN software calls (by default). If PRIMAD is larger than FF (hex), the operation will be performed in one of the remote crates (connected by a cable segment via SSPs) according to the BSI routing information contained in PRIMAD (see HELP ROUTING for more information)

Additional Information on:

• Examples

FWCB: FASTBUS block write to CSR space.

If the parameters are not supplied, they will be prompted for.

Parameters:

PRIMAD is the primary address of the module, and must be a number (in hexadecimal) or a DEFINED PRIMARY ADDRESS (see SHODEF) or a USER DEFINED NAME (see SHODEF, DEFINE). For a module in a REMOTE crate (connected with an SSP cable segment) it must contain the BSI routing information (see Help ROUTING).

SECAD is the secondary address of the module, and must be a number (in hexadecimal) or a USER DEFINED NAME.

MAXLEN is the maximum number of transfers (i.e. number of 32-bit words) to be written to FASTBUS. MAXLEN must be supplied as a decimal number between 1 and 500, or a USER DEFINED NAME.

OUTBUF is the data (in hex.) to be written to the FASTBUS module. A number MAXLEN of 32-bit words will be requested and used to fill OUTBUF.

If PRIMAD is less than FF (hex), the operation will be performed in the local (master) crate (i.e. the crate that contains the CFIFC - the CFI FASTBUS card) using the CERN software calls (by default). If PRIMAD is larger than FF (hex), the operation will be performed in one of the remote crates (connected by a cable segment via SSPs) according to the BSI routing information contained in PRIMAD (see HELP ROUTING for more information)

Additional Information on:

• Examples

FWDM: FASTBUS single word Broadcast write data space

If the parameters are not supplied, they will be prompted for.

Parameters:

PRIMAD is the broadcast primary address, and must be a number (in hexadecimal) or a USER DEFINED NAME (see SHODEF, DEFINE). For a module in a REMOTE crate (connected with an SSP cable segment) it must contain the BSI routing information (see Help ROUTING). The crate(s) to which the broadcast applies are determined by the setting of the LOCAL BIT (see Help SSP BROADCAST).

SECAD is the secondary address, and must be a number (in hexadecimal) or a USER DEFINED NAME.

IOBUF is the data (in hex.) to be written to the FASTBUS module. A number MAXLEN of 32-bit words will be requested and used to fill OUTBUF.

FWCM

FWCM: FASTBUS single word Broadcast write CSR space

If the parameters are not supplied, they will be prompted for.

Parameters:

PRIMAD is the broadcast primary address, and must be a number (in hexadecimal) or a USER DEFINED NAME (see SHODEF, DEFINE). For a module in a REMOTE crate (connected with an SSP cable segment) it must contain the BSI routing information (see Help ROUTING). The crate(s) to which the broadcast applies are determined by the setting of the LOCAL BIT (see Help SSP BROADCAST).

SECAD is the secondary address, and must be a number (in hexadecimal) or a USER DEFINED NAME.

IOBUF is the data (in hex.) to be written to the FASTBUS module. A number MAXLEN of 32-bit words will be requested and used to fill OUTBUF.

FRDM

FRDM: FASTBUS single word Broadcast read data space

If the parameters are not supplied, they will be prompted for.

Parameters:

PRIMAD is the broadcast primary address, and must be a number (in hexadecimal) or a USER DEFINED NAME (see SHODEF, DEFINE). For a module in a REMOTE crate (connected with an SSP cable segment) it must contain the BSI routing information (see Help ROUTING). The crate(s) to which the broadcast applies are determined by the setting of the LOCAL BIT (see Help SSP BROADCAST).

SECAD is the secondary address, and must be a number (in hexadecimal) or a USER DEFINED NAME.

FRCM

FRCM: FASTBUS single word Broadcast read CSR space

If the parameters are not supplied, they will be prompted for.

Parameters:

PRIMAD is the broadcast primary address, and must be a number (in hexadecimal) or a USER DEFINED NAME (see SHODEF, DEFINE). For a module in a REMOTE crate (connected with an SSP cable segment) it must contain the BSI routing information (see Help ROUTING). The crate(s) to which the broadcast applies are determined by the setting of the LOCAL BIT (see Help SSP BROADCAST).

SECAD is the secondary address, and must be a number (in hexadecimal) or a USER DEFINED NAME.

FRDMB

FRDMB: FASTBUS block read multi-listener (broadcast) of Data space.

Note - this command works only in the LOCAL crate.

If the parameters are not supplied, they will be prompted for.

Parameters:

PRIMAD is the primary address of the module, and must be a number (in hexadecimal) or a DEFINED PRIMARY ADDRESS (see SHODEF) or a USER DEFINED NAME (see SHODEF, DEFINE).

SECAD is the secondary address of the module, and must be a number (in hexadecimal) or a USER DEFINED NAME (see SHODEF, DEFINE).

MAXLEN is the maximum number of transfers (i.e. number of 32-bit words) to be read from FASTBUS. The block read will end on either MAXLEN being reached, or an SS=2 (end of block) from the slave module. MAXLEN must be supplied as a decimal number between 1 and 500, or a USER DEFINED NAME .

FRCMB

FRCMB: FASTBUS block read multi-listener (broadcast) of CSR space.

Note - this command works only in the LOCAL crate.

If the parameters are not supplied, they will be prompted for.

Parameters:

PRIMAD is the primary address of the module, and must be a number (in hexadecimal) or a DEFINED PRIMARY ADDRESS (see SHODEF) or a USER DEFINED NAME (see SHODEF, DEFINE).

SECAD is the secondary address of the module, and must be a number (in hexadecimal) or a USER DEFINED NAME.

MAXLEN is the maximum number of transfers (i.e. number of 32-bit words) to be read from FASTBUS. The block read will end on either MAXLEN being reached, or an SS=2 (end of block) from the slave module. MAXLEN must be supplied as a decimal number between 1 and 500, or a USER DEFINED NAME.

FWDMB

FWDMB: FASTBUS block read write multi-listener (broadcast) of Data space.

Note - this command works only in the LOCAL crate.

If the parameters are not supplied, they will be prompted for.

Parameters:

PRIMAD is the primary address of the module, and must be a number (in hexadecimal) or a DEFINED PRIMARY ADDRESS (see SHODEF) or a USER DEFINED NAME (see SHODEF, DEFINE).

SECAD is the secondary address of the module, and must be a number (in hexadecimal) or a USER DEFINED NAME.

MAXLEN is the maximum number of transfers (i.e. number of 32-bit words) to be written to FASTBUS. MAXLEN must be supplied as a decimal number between 1 and 500, or a USER DEFINED NAME.

OUTBUF is the data (in hex.) to be written to the FASTBUS module. A number MAXLEN of 32-bit words will be requested and used to fill OUTBUF.

FWCMB

FWCMB: FASTBUS block read write multi-listener (broadcast) of CSR space.

Note - this command works only in the LOCAL crate.

If the parameters are not supplied, they will be prompted for.

Parameters:

PRIMAD is the primary address of the module, and must be a number (in hexadecimal) or a DEFINED PRIMARY ADDRESS (see SHODEF) or a USER DEFINED NAME (see SHODEF, DEFINE).

SECAD is the secondary address of the module, and must be a number (in hexadecimal) or a USER DEFINED NAME.

MAXLEN is the maximum number of transfers (i.e. number of 32-bit words) to be written to FASTBUS. MAXLEN must be supplied as a decimal number between 1 and 500, or a USER DEFINED NAME.

OUTBUF is the data (in hex.) to be written to the FASTBUS module. A number MAXLEN of 32-bit words will be requested and used to fill OUTBUF.

FRDSA

FRDSA: Read Data space secondary address (NTA)

If the parameter is not supplied, it will be prompted for.

Note - this command works only in the LOCAL crate.

Parameter:

PRIMAD is the primary address of the module, and must be a number (in hexadecimal) or a DEFINED PRIMARY ADDRESS (see SHODEF) or a USER DEFINED NAME (see SHODEF, DEFINE).

FWDSA

FWDSA: Write Data space secondary address (NTA)

If the parameters are not supplied, they will be prompted for.

Note - this command works only in the LOCAL crate.

Parameters:

PRIMAD is the primary address of the module, and must be a number (in hexadecimal) or a DEFINED PRIMARY ADDRESS (see SHODEF) or a USER DEFINED NAME (see SHODEF, DEFINE).

IOBUF is the single word (32 bits) to be written to the module. It must be a number (in hexadecimal) or a USER DEFINED NAME.

FRCSA

FRCSA: Read CSR space secondary address (NTA)

If the parameters is not supplied, it will be prompted for.

Note - this command works only in the LOCAL crate.

Parameter:

PRIMAD is the primary address of the module, and must be a number (in hexadecimal) or a DEFINED PRIMARY ADDRESS (see SHODEF) or a USER DEFINED NAME (see SHODEF, DEFINE).

FWCSA

FWCSA: Write CSR space secondary address (NTA)

If the parameters are not supplied, they will be prompted for.

Note - this command works only in the LOCAL crate.

Parameters:

PRIMAD is the primary address of the module, and must be a number (in hexadecimal) or a DEFINED PRIMARY ADDRESS (see SHODEF) or a USER DEFINED NAME (see SHODEF, DEFINE).

IOBUF is the single word (32 bits) to be written to the module. It must be a number (in hexadecimal) or a USER DEFINED NAME.

FBWHO

Find out which modules are in the LOCAL FASTBUS crate (i.e. the crate in which the CFI card is located). Use TREE command if a cable segment is implemented.

FBWHO uses either a polling method where CSR0 of each slot will be read, or by broadcasting a command to assert T-pins.

This version of CFIMENU checks the slots of the IORFI modules (see HELP IORFI) and does not poll the IORFIs.

After performing FBWHO, a list of DEFINED PRIMARY ADDRESSES is set up. The LeCroy TDC,ADC,CAT and SSP, and Struck Branch driver all have automatically defined primary addresses.

e.g. if there is one CAT module with a primary address (slot no.) of 6, then the string "TDC" will be assigned the value "6". For all commands in the program that require a primary address value, the string "TDC" could be used instead of "6". See HELP DEFINE EXAMPLES

The DEFINED PRIMARY ADDRESSES are displayed using the SHODEF command.

FBWHO (or TREE) should be performed on entry to the CFIMENU program to take advantage of the DEFINED PRIMARY ADDRESSES set up. Without performing a command FBWHO (or TREE), no primary addresses are defined.

Additional Information on:

• COMMAND_FILE

Sets up a USER DEFINED NAME, by assigning a character string to a numerical value. Up to 20 user defined names are allowed. Names that have been set up with DEFINE may be shown with the command SHODEF.

These defined names can be used instead of the numerical values as parameters to CFIMENU commands.

Parameters:

NAME is a character string of up to 6 characters. It must not be one of the strings used as a DEFINED PRIMARY ADDRESS. If the NAME supplied is already a defined symbol, the previous definition will be overwritten.

VALUE is a number in hexadecimal which is to be assigned to the character string.

Additional Information on:

• EXAMPLES

This command outputs a list of both DEFINED PRIMARY ADDRESSES (set up by command FBWHO or TREE) and USER DEFINED NAMES set up by the command SHODEF.

The defined names are character strings that are assigned to numerical values. These defined names can be used instead of the numerical values as parameters to CFIMENU commands.

OPTION

Runs a subroutine CFIOPT to set up or clear a CFI hardware or software option.

Note - options cannot be set up in a remote crate, as they are not supported by the BSI software routines for SSPs.

CFI Hardware processing options: <ul> <li> FOGERR: Leave bus status unchanged on any error abort <li> FONOAR: No arbitration cycle <li> FONOPA: No primary address cycle <li> FOEG: Master asserts EG <li> FOGKUP: Retain bus mastership at end of operation <li> FONOSA: No secondary address cycle <li> FONODC: No data cycle(s) <li> FOASUP: Retain AS/AK lock at end of operation <li> FOBLKE: Define SS=2 as Block Transfer error end <li> FOBUFE: Define MAXLEN transfers as Block Transfer <li> NONE if you have changed your mind </ul> CFI Software compile options <ul> <li> FOUSER = 1 Compile user list elements, delay processing <li> FOEMRD = 0 Read data into INBUF when processing <li> FOEMRD = 1 Embed read data in List Element when processing <li> FOBFWD = 0 Write data from OUTBUF when processing <li> FOBFWD = 1 Embed write data in List Element for processing <li> FOIG = 1 Compile list elements but ignore when processing </ul>

CFIOPT is a simple menu-driven program, whose commands are listed below. <ul> <li> ST - output status of hardware and software options set <li> SH - set up a hardware option <li> SS - set up a software option <li> CH - clear all hardware options <li> CS - clear all software options <li> CL - clear all options <li> OH - clear one hardware option <li> OS - clear one software option <li> HE - help <li> EX - exit </ul> If the command "SH" is given, the CFI hardware processing options listed above will be shown. If no option is desired, enter "NONE" and the program will return to the main menu.

If the command "SS" is given, the CFI software processing options listed above will be shown. If no option is desired, enter "NONE" and the program will return to the main menu. If one of the software options other than FOUSER is selected, FOUSER will be set automatically.

To return to CFIMENU from CFIOPT, type "EX".

Additional Information on:

• COMMAND_FILE

Output control/status array (written to disc as file STATUS.TMP).

In stored/list mode, CNTRL contains the list elements that make up a list. These list elements ( or F-codes) are CERN internal codes listed in the CERN software document.

This command would normally be used when testing the CFI.

NOTE - this array will not be correctly filled when the SSP BSI software is used (i.e. on access to remote crates).

CLEAR

Execute a FAST CLEAR using the CAT (LeCroy specific command).

Parameter: CLEAR takes a parameter, the answer to the question: "Clear local crate <L> or all known crates <A>? " The parameter ANS takes the values "A" or "L".

If just the LOCAL crate is to be cleared, a value of '8D' is broadcast to the crate (using FWDM). If ALL the known crates (connected by an SSP cable segment) are to be cleared, several broadcasts are performed, according to a table automatically setup when TREE is called. The broadcast occurs on every known crate in the system. See EXAMPLES for details.

Note that if TREE has not been called before a CLEAR command is given, a broadcast to ALL crates is not allowed, and only a broadcast in the local crate will be performed. A message will be displayed to this effect.

Additional Information on:

• Examples

Reads back the set-up registers of CAT,TDC,ADC (LeCroy specific command). A CAT and at least one TDC or ADC must be present. If there are no DEFINED PRIMARY ADDRESSES (produced by command FBWHO or TREE) the routine will return with an error message. If there is more than one of each type of module, the user is required to enter the primary address of one of the modules.

If REPORT is called prior to commands ANATDC, the output of ANATDC and will be in terms of nanoseconds, rather than buckets, since the frequency reference of the TDC will be known. REPORT assumes that the frequency reference is from the CAT at present.

Additional Information on:

• COMMAND_FILE

This is a CFIMENU command that has been provided for reading out the ADC. For efficiency, it is necessary to set up a number of FASTBUS options when reading the ADC, as it can be read out only in single word reads, rather than a single block read as in the case of the TDC. ADCRD requires to be told the number of ADC words to read. This number MUST be 3 or more to use this command. Otherwise use FASTBUS command FRD.

ANAADC

Parameters: none

Decodes data from ADC

ANAADC will only work if the ADC is read in list mode, as in that case the ADC data is read out into an array. In immediate mode, the data for each channel is output and then lost, so ANAADC cannot be used. In list mode, the ADC should be the only module read, since ANAADC assumes that all the data is ADC data.

To read the ADC in list mode, use standard command file @ADCLST (see HELP @) followed by ANAADC, or enter commands FLIST,ADCRD, FLEX,ANAADC.

(The program TCAT_CERN is normally used for testing the LeCroy modules).

TDCRD

This routine is provided for convenience. It performs a block read of a TDC leading or trailing edge data. It should be preceeded by a fast clear (if using CAT in test mode).

At least one TDC should be present in the crate. TDCRD relies on finding the primary address of the TDC module as a DEFINED PRIMARY ADDRESS.

If there are no DEFINED PRIMARY ADDRESSES (produced by command FBWHO) the routine will return with an error message. If there is more than one of each type of module, the user is required to enter the primary address of one of the modules.

The command ANATDC may be used immediately after this command to analyse the TDC data (see HELP ANATDC).

(The program TCAT_CERN is normally used for testing the LeCroy modules).

Parameters:

SECAD is the secondary address, and the user is prompted for leading or trailing edge data. Enter "0" for leading edge, "1" for trailing edge.

MAXLEN is the maximum number of transfers (i.e. number of 32-bit words) to be read from FASTBUS. The block read will end on either MAXLEN being reached, or an SS=2 (end of block) from the slave module.

MAXLEN must be supplied as a decimal number between 1 and 500, or a USER DEFINED NAME.

ANATDC

Decodes data read from TDC. Previous command should be TDCRD.

This command is provided for convenience in testing and debugging the LeCroy Fastbus TDC. It is called immediately after a block read of TDC data in immediate (or delayed ) mode. The block read may be accomplished either using TDCRD or FRDB. If REPORT has been previously called (see HELP REPORT), TDCRD outputs the TDC data in units of nanoseconds. Otherwise, the TDC data is output in terms of buckets.

N.B. In delayed mode, the contents of the list must be TDC data only, as ANATDC attempts to interpret all the data as TDC data.

MENU

COMMAND_FILES

@

CFIMENU accepts command files. These contain CFIMENU commands, but for most commands, all the parameters to be supplied must be in the correct format on the same line as the command (see HELP @ EXAMPLES ). The exceptions are the parameters for the FBWHO, BRDRV,CAMAC,REPORT and OPTION commands. These take no in-line parameters. The parameters for these commands must be supplied on lines following the CFIMENU command. Examples of command files incorporating these specific commands is available by typing (for example) HELP CAMAC COMMAND_FILE.

CFIMENU expects the default file extension to be ".CCM" . If no file extension is supplied, CFIMENU will look for FILENAME.CCM in the current default directory of the user. If such a file is not found, the file CFILIB:FILENAME.CCM will be looked for. This enables some standard CFIMENU files to be kept for general use in the account CFILIB: . ("CFILIB:" is a logical symbol set up to point to the CFIMENU account).

Standard files are provided (see HELP @ FILES), to perform various useful functions.

Comments may be included in the command file, but must be preceded by an exclamation mark "!". In the special cases of the commands FBWHO,OPTION,REPORT,BRDRV and CAMAC, comments are not always allowed. See (for example) HELP CAMAC COMMAND_FILE.

USER DEFINED SYMBOLS and DEFINED PRIMARY ADDRESSES may be used in the file, but these must be defined (using the FBWHO or DEFINE command ) either in the file, or prior to running the file.

For repeating a command file, and using command REPEAT within a command file, see HELP REPEAT REPEATING_COMMAND_FILES.

Additional Information on:

• STANDARD_FILES
• Examples

To prevent this occurring, a file CFILIB:IORFI.DAT must be kept up to date with the locations of the IORFI modules. CFIMENU accesses this file and checks all commands before executing them, to make sure that an IORFI is not being addressed.

Additional Information on:

• INITIALIZE

FWRB writes to the FASTBUS signal RB (Reset Bus) in crate CRATE on the VME Branch Bus.

CRATE must be a number (in decimal) or a USER DEFINED NAME.

Note - this command works only in the LOCAL FASTBUS crate. For RESET BUS in a REMOTE crate, use the command FB_RESET_BUS (see Help FB_RESET_BUS).

FB_RESET_BUS

The SSP at primary address PRIMAD will pulse the FASTBUS line RB (Reset Bus).

If the parameter is not supplied, it will be prompted for. If "default" is selected for this parameter, a search will be performed for an SSP in the system (using TREE command).

This command allows the RB line to be pulsed in a REMOTE crate connected via an SSP cable segment. PRIMAD must contain the BSI routing information for the SSP in the remote crate (see Help ROUTING).

To pulse the RB line in the local crate, the command FWRB (see Help FWRB) may also be used.

BRDRV

This command is provided to exercise the registers of the Struck Branch Driver (STR320). An address (or the default value) will be requested the first time the commands BRDRV or CAMAC are executed. The command BRDRV causes a menu-driven program to be run. The prompt BRDRV> appears, and a menu-item is requested. To return to CFIMENU, the command EXIT is used. Only enough letters of the commands need be entered so that they are unique.

Additional Information on:

• SET_TIMOUT
• EN_LOG_ADDR
• DEV_ALLOC
• SR_EN
• SR_ASS
• SET_SS7_EN
• SET_Q_BIT0
• SET_Q_BIT1
• SET_BLK_BIT0
• SET_BLK_BIT1
• WAIT_EN
• CLR_TIMOUT
• DI_LOG_ADDR
• DEV_DEALL
• SR_DI
• SR_RESET
• CLR_SS7_EN
• CLR_Q_BIT0
• CLR_Q_BIT1
• CLR_BLK_BIT0
• CLR_BLK_BIT1
• WAIT_DI
• RESET
• CAMAC_Z
• READ_CSR0
• READ_CSR1
• READ_CSR3
• READ_CSR7
• TST_ALIAS
• EXIT
• MENU
• COMMAND_FILE

This command is provided to exercise CAMAC crates connected to the FASTBUS crate via a FASTBUS Struck Branch Driver. A CAMAC crate with an Elliott crate controller is needed.

The FIRST TIME either of the commands BRDRV or CAMAC are executed, the GA (or slot) of the FASTBUS branch driver will be requested (in hexadecimal). If the value is not known, enter carriage return. This will cause a scan of the crate to be executed in order to find the slot of the branch driver. Entering the slot yourself will save time, especially if the crate is full.

Also the FIRST TIME BRDRV or CAMAC are executed, an address (or the default value) will also be requested the first time the commands BRDRV or CAMAC are executed. Enter carriage return to use the default value.

The command CAMAC causes a menu-driven program to be run. The number of the CAMAC crate to be used can be entered using the command CRATE. This crate number become the default crate, so all operations on the crate are directed to the default crate (except in the special case of block transfers and CNAF - see e.g. HELP CAMAC CNAF). If a default crate value is not entered, it will be prompted for. To change the default crate value, use the CRATE command (see HELP CAMAC CRATE).

The prompt CAMAC> then appears, and the program then requests a menu item.The command MENU lists the menu of available commands. See HELP MENU for a list of the commands (in English). To return to CFIMENU, the command EXIT is used. Only enough letters of the command need be entered so that it is unique.

Additional Information on:

• MENU
• Z_CRATE
• C_CRATE
• SET_INH
• CLR_INH
• TST_INH
• EN_DEM
• DI_DEM
• TST_DEM_EN
• TST_DEM_PR
• LOAD_ST
• RD_GR_LAM
• CNAF
• EXIT
• LOOP
• CRATE
• READ_CSR0
• X_RESET
• X_SET
• Q_STOP_BLOCK
• MULDEV_BLOCK
• UNIDEV_BLOCK
• HELP
• DIS_DIRECT
• EN_DIRECT
• DIS_BLK_OUT
• EN_BLK_OUT
• DEC_DATA
• OCT_DATA
• HEX_DATA
• COMMAND_FILE

FB address - Primary address (logical or geographic) of module to be tested. Defined symbols are also accepted.

Test selection popup - Use VT100 cursor keys to select required test, then press return. See subtopics.

Number of passes - select number of times test is to be repeated. For random tests, increasing this number increases the confidence.

CSR/data space popup - Select with cursor, then hit return.

First and last addresses - select as required. These may be the same, so that a read/write register may be tested. For the memory limits of an SSP, see HELP SSP MEMORY.

Mask - select a hexadecimal value for bits that are not to be tested, e.g. 0 will test all bits, FFFFFF00 will test bits 0-7. This is useful for testing RAM that is not 32-bit width, or for checking remaining bits when there is one bit stuck.

Additional Information on:

• Two_pass_count
• Random
• One_pass
• Block_transfer

The default is that display of the block read or write data is enabled.

Note that turning off BLKFLG will also turn off display of the data from any list of commands, even if the commands themselves are single word reads, e.g. this sequence of commands

 QFI>BLKFLG 0
 QFI>FLIST 1
 QFI>FRC FF 0
 QFI>FRD CAT 4
 QFI>FLEX 1
 

would result in the number of words read being displyed, but no data. The reason is that the command to execute list performs a block read to read the data from the CFI.

OUTFLG

The default is that display of the data is enabled.

RDPAR

REPEAT

 QFI>REPEAT 2
 QFI>FRC FF 0
 

would result in the command FRC FF 0 being performed a total of 3 times.

Note that only commands that perform FASTBUS operations can be repeated. Other commmands will return a message to say that repeating this command is not supported.

The flag OUTFLG has been provided for use with the REPEAT command. By setting OUTFLG to 1 (see HELP OUTFLG) display of data on the screen can be switched off. This speeds up repetion of the command, which is useful for debugging purposes.

Additional Information on:

• REPEATING_COMMAND_FILES

By default, the local crate (where the CFI Fastbus card and the MASTER SSP are located) is accessed directly using the CFI. It is not necessary to have an SSP in the crate in this case. However, if an SSP is present, it is possible to force the SSP do the communication by first using the command CABLE (see Help CABLE). The command CRATE will reset the default condition (see Help CRATE).

Not all the CFIMENU commands are supported by the BSI software, i.e. some commands CAN ONLY BE DONE IN THE LOCAL CRATE. A message is output to warn the user, if an attempt is made to use these on a remote crate.

Additional Information on:

• DIAGNOSTICS
• MEMORY
• LOADING
• BROADCASTS

To communicate with remote FASTBUS crates connected with an SSP cable segment, the BSI routines (written at BNL) are used.

The Buffered Segment Interconnect, or BSI, is a set of routines which permit access to FASTBUS slaves in other FASTBUS segments, be they cable or crate, through a chain of SSPs. A default routing table has been defined which permits access to any slave on a segment which is separated from the originating master's segment by as many as two intervening segments.

The default routing table is very simple; the 32 bits of the primary address word are broken up into four bytes. Only the lowest-order byte is a true geographical FASTBUS address; the other three comprise the SEGMENT IDENTIFIER.

The three bytes of the SEGMENT IDENTIFIER are used as (up to) three separate geographical addresses. The originating master (be it host-computer with FASTBUS interface, or an SSP) looks at the segment identifier (upper three bytes of the primary address word) and if it is non-zero, uses the high-order byte of the segment identifier as the geographical address of an SSP through which the transaction will be "routed". The originating master then strips off this highest non-zero byte and passes the new primary address on to the SSP indicated by that byte. That SSP in turn does the same, until there are no non-zero bytes in the three-byte segment identifier. The SSP at the end of the line directly engages the slave. Access over multiple segments is completely transparent due to the way the BSI routines are set up.

For more details, see BNL$SSP:SSP_PROGRAMMER.MEM

Additional Information on:

• Example

It will scan a crate based on the BSI routing information that the user supplies. It is really superseded by the TREE command, which automatically scans all the cable and crate segments, but may still prove useful for testing.

CRATE

This is a command borrowed from SSPAR

CABLE

This is a command borrowed from SSPAR

TREE

This command will scan automatically the SSP cable segment and all crates it can find, including the local crate (i.e. the crate containing the CFI). It is similar to the FBWHO command, except FBWHO scans only the local crate.

Depending on the parameter supplied, the SSPs will either all be loaded with the file BNL$SSP:ARBTST.SSP, or none of them will be loaded. Note that all communication with remote crates depends on all the SSPs being downloaded with code including the BSI software. All the data acquistion software contains the BSI software, but if the power on the crate(s) has been turned off, the SSPs must be reloaded.

Parameter:

TREE takes a parameter, the answer to the question: " Load SSP <L> or not <N> ?" The parameter takes the value "L" or "N". See examples for details. If the parameter is not supplied, it will be prompted for.

TREE uses a polling method where CSR0 of each slot will be read.

After performing TREE, a list of DEFINED PRIMARY ADDRESSES is set up. The LeCroy TDC,ADC,CAT and SSP, and Struck Branch driver all have automatically defined primary addresses.

e.g. if there is one CAT module with a primary address (slot no.) of six, then the string "TDC" will be assigned the value "6". For all commands in the program that require a primary address value, the string "TDC" could be used instead of "6".

The DEFINED PRIMARY ADDRESSES are displayed using the SHODEF command.

This command should be performed on entry to the CFIMENU program to take advantage of the DEFINED PRIMARY ADDRESSES set up. Without performing a command TREE (or FBWHO), no primary addresses are defined.

This command is a modified version of the SSPAR command.

Additional Information on:

• Examples

CFIFLG

By default, all (supported) calls are routed through the BNLSSP software. If the operation is to be performed on the LOCAL crate, the CFI software will eventually be called.

By setting flag true, the BNLSSP software is effectively bypassed.

This command is used for debugging purposes.

To force the routing to be via an SSP (or not) see HELP CRATE and HELP CABLE.

ERRORS

Error conditions may occur on first starting the program.

If the CFI fails to initialize correctly with FCAM and/or FMINI, check that the CAMAC crate (if used ) and the FASTBUS crate are powered up and on-line, and that you are using the correct package for the hardware. (If you are using a QFI system, the prompt from CFIMENU should be "QFI>".

FCAM will also fail if another user has booked the interface.

Once FMINI and FCAM are successful, errors may be generated on any command. If an error occurs from the CFI, the error handler CFIERR is called. This should decode the error code, and give an explanatory message.

If after FCAM and FMINI are successful, an error FERLAM from the CFI software (in case of CFI Camac coupler ) or a device time-out (in the QFI case) this may indicate that any IORFIs in the crate have not been initialized. See HELP IORFI INITIALIZE for instructions. If the problem is not with the IORFI initialization, try a FREL or FMINI and then repeat the command.

Another master may have control of the bus, in which case no amount of initializing of this master will help.

If you perform commands and no error messages occur but no output appears on the screen, you may be stuck in list mode or suppressed output mode. Execute the command CLRLST. This will reset the CFI to direct mode.

If all else fails, exit and reenter the program. If still unsuccessful, switch off Fastbus crate, reinitialize the IORFIs, and try again.

LOGICALS

CFILIB,FBCERN,BRU$LIBRARY,BNL$SSP

BUILDING

Additional Information on:

• SOURCES
• LINK