Daisy-chain of multiplexers

For the convenience of the experimenters, there is a daisy-chain of multiplexers foreseen which delivers the control output from one GSI constant fraction channel (time, energy, and walk) to one oscilloscope. This feature is a 'must' for the LAND collaboration whose electronics is sitting in the cave. If you do not want to use it, skip this section.
The daisy-chain requires three pieces of information:

• For each CFD module, you need to have an attribute MUX_LOG which contains a logical name of a multiplexer into which the three outputs of the CFD module are sent. An example for the LAND CFD from table  is shown in table . The logical name 'cr07sl01' just contains crate and slot number of 'cf1234'.
• There has to be a table with the name MUXLONG and the attributes MUX_LOG, MUX_ID, MUXADDR, MUX_SET, and MUX_NEXT (table ). This table translates the logical name MUX_LOG into the identifier of a physical module, the address in that module, and its setting. MUXADDR is a vector of three components which contains the addresses of the three outputs from the CFD. MUX_SET is a scalar: The three outputs are assumed to run on parallel paths through the multiplexer chain. MUX_NEXT points to the next logical name of a multiplexer. The entry MUX_NEXT = 'nil' terminates the chain.
• The multiplexers need to be listed in table ELECLOC. Their type has to be RM2400 or RM4800, so the software knows how many addresses there are. (In principle, one could have used table LIMITS for that purpose, but alas, I am wiser now writing this description than I was writing the software...) In our case, the identifiers 'mux001' and 'mux005' need to appear in table ELECLOC (table ), because they refer to the physical modules to which the CAMAC commands are sent.

 
Table: Pointer to multiplexer chain of LAND CFD 'cf1234'  

 
Table: Multiplexer chain of LAND CFD 'cf1234'  

 
Table: Two multiplexers in table ELECLOC