Proxy class for a GTM board of the flavor of Nevis (BB, ZDC)
BUSY functions to control the granule BUSY over VME
Configuration Commands and retrieval of configuration parameters
Function that coordinate the GTM-FEM-DCM interdependence
Functions inherited from PU that make up the global state transitions
print, dump, list functions and accessors
Resetting the glink on the GTM
static member function that affect all instances of the GTMs
Accessors common to all PU
Architectural common member functions for all PU
Simple implementation of RTTI (see note above)
State transitions
virtual functions for generic configuring, starting/updating/continuing a state transition
Proxy class for a GTM board of the flavor of Nevis (BB, ZDC). These two subsystems require a slight change from the generic GTM which is implemented in the overloaded member function download and updatePu.
Note that we have to send arcnet files to two different type of devices: the timing device and the FEM. The former gets its download at initialisation, the second at download time.The following things happen during the state transition functions:
- Initialise: (same as the generic GTM)
1. Raise the GTM VME busy, 2. Reset GTM, 3. Reset GLink, 4. initialise FEMs- Download:
1. download FEMs, 2. load modebits, 3. reset Glink, 4. global start.
bool updatePu( int iStatus, int eState_on_success )
rcGTMNevis(const char *name, const char *pud_name, long vme_address, const char* pcServerName = NULL)
pud_name - : name of the corresponding design
vme_address - : address in the VME crate
pcServerName - : name of the server that manages this object
this page has been generated automatically by doc++
(c)opyright by Malte Zöckler, Roland Wunderling
contact: doc++@zib.de