The locations of all your electronics modules are stored in table ELECLOC. ELECLOC has five columns: MOD_ID, MOD_TYPE, BRANCH, CRATE, and SLOT. (These attributes are hardwired into the software.) An example that would serve the needs of the detectors discussed in the previous sections would look as follows:
Table: Example of table ELECLOC
The first column contains a unique name of every module. It may
be a real hardware identifier containing the manufacturer's serial number
(like 'a69592'),
or it may be a logical name derived from the detector, the purpose of the
module, or its crate and slot number. The first three entries of the
above example are the three high voltage controllers from our discussion
of table DET_CONF (see table ):
they are taken from column HV_CTRL for the HV key
attributes SIG_LAND, DET_PLA, and 8PACK. Their type (hvc40) is not
arbitrary, but has to be like this. The first three letters tell the
software that these modules are HV controllers, and the number '40'
indicates the main frame type 1440. (For 4032 frames, MOD_TYPE has to
be 'hvc32', and for DAC-driven HV supplies, MOD_TYPE has to be
DA1800.)
The following four entries are taken from the example of electronics
addresses for the LAND detector (table ).
'cf1234' is a GSI module of type 8102,
and it sits in the CAMAC branch which in this example is number 2. The TDC
and the two QDCs sit in the fastbus branch # 1. The first three letters
of MOD_TYPE have to be 'TDC' in the case of 't56565', so that the software
knows that 't56565' is found in column TDC_ID and not QDC_ID, and the
same holds for the letters 'qdc' in the type of 'q98989' and 'qdc666'.
fopi
Fri Oct 25 16:39:46 CST 1996