Chapter 1. Theory of Operation

Table of Contents
1.1. Initializing Driver
1.1.1. Environment
1.1.2. Debugging Output
1.1.3. Allocating Handles
1.2. Initializing TEM Hardware
1.2.1. Initializing the GGLT
1.2.2. Initializing the GTEM
1.3. Event Taking Configuration
1.3.1. Memory Allocation Callback
1.3.2. Event Handler Callback
1.3.3. Event Loop
1.4. Triggering

Commanding and taking event data from the TEM requires two VME LAT COMM I/O Boards – one for command I/O with the TEM and one for triggering and event read out. The software driver provides a C language functional interface for creating opaque handles to the Command/Response COMM Board (hereafter GTEM) and to the mini-GLT COMM Board (hereafter GGLT). These handles are passed as arguments to subsequent methods appropriate to each type of COMM Board (see Chapter 2 and Chapter 3).

Initializing the system for running consists of initializing the driver handles for the two VME LAT COMM I/O Boards, configuring the GTEM registers and configuring the GGLT registers.