Proxy class for a GTM board of type TEC in the run control server
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 type TEC in the run control server. The TEC has the funny behavior that we must start the GTM before the download the FEM files. Otherwise the local controller on the FEM board cannot talk to Arcnet. This is implemented in the redefined member function updateDownload that overrides the default behavior of the generic GTM.The following things happen during the state transition functions:
- Initialise: (same as generic GTM)
1. Raise the GTM VME busy, 2. Reset GTM, 3. Reset GLink, 4. initialise FEMs- Download:
1. Reset GTM, 2. load modebits, 3. reset GLink, 4. global start, 5. download FEMs,
- Start_run: (same as generic GTM)
Lower the busy once everybody is running- End_run: (same as generic GTM)
Raise the busy before talking to other components.
rcGTMTec(const char *name, const char *pud_name, long vme_address, const char* pcServerName )
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