TBPM FrontEnd Software Design Review

1
TBPM Front-End Software Design Review

• L.Piccoli
• April 20 2004

2
Contents

• Generic Framework Diagram
• Control Task
• Data Acquisition Tasks
• Data Buffers and Data Sources
• Buffer Readout
• Alarms
• Triggers
• ACNET
• Tevatron BPM Diagram
• Class Diagram

3
Data Source (EchoTek or buffer)
Data
Data
Data Acquisition Task
Trigger Queue
Trigger
Data Buffer
Data
Spawn Suspend Resume Delete
TCLK State Devices
Alarm
2ms, 1sec
Buffer Readout Task
Control Task
Trigger
Alarm Queue
Alarm
Alarm/Clear
TCLK State Devices
Control request Triggers
Status
Data request
Alarm Task
Request Queue
Data
Control Queue
Data request
Mode change Control request
Alarm
MOOC/Backdoor
4
Control Task

• Receive external commands (from MOOC)
• Mode change, set diagnostics, calibration
• Control data acquisition tasks
• Start, stop, pause and resume
• Receive state device changes and TCLKS
• Configure EchoTek and timing board on mode
  changes

5
Data Acquisition Tasks

• Receive commands and triggers through input queue
• When a trigger is received
• Get data from a Data Source
• Store data into a Data Buffer
• A Data Source can be either Hardware or an
  internal Data Buffer

6
Buffers

• Data Source
• Define operations for retrieving data
• Data Buffer
• Provide interface for storing data in the
  front-end memory
• Data Buffer is a Data Source
• Reading hardware or an internal buffer should be
  transparent for the Data Acquisition Tasks

7
Buffer Readout

• Handled by Buffer Readout Tasks
• Number of tasks settable
• Request comes through the MOOC callback, which
  makes a request to the Buffer Readout Task
• Task selects buffer based on the request
• Data is packed according to online specifications
  (doc 860)

8
Alarms

• Any task can generate alarms within the system
• Internal alarms are handled by an Alarm Task
• Input alarm queue
• Alarm Task decides what internal alarms or
  combination of alarms trigger an external alarm
• Control Task or user command can clear alarm
  conditions

9
Triggers

• Created by Trigger Generators
• Type of triggers
• TCLKs
• State Device Changes
• Time events (2 ms, 1 sec)
• Triggers are sent to the input queues of the Data
  Acquisition Tasks
• Tasks are in a loop doing data acquisition and
  waiting for triggers

10
ACNET

• ACNET communication is handled by a set of
  callbacks, providing
• Standard communication with the system
• Reduced number of entry points
• Support other communication mechanisms besides
  ACNET (e.g. backdoor)

11
EchoTek
Queue
2ms
Task
Trigger
BPM Fast Abort Buffer
Hardware
BPM Slow Abort Buffer
1sec
Trigger
Data Buffer
EchoTek
Data Source Buffer
Turn by Turn Buffer
EchoTek
Injection Turn by Turn Buffer
BPM Fast Abort Buffer
BPM Profile Buffer
BPM Fast Abort Buffer
Alarm
BPM Display Buffer
1sec
BLM
Trigger
Data request
BLM Fast Abort Buffer
BLM Display Buffer
Alarm
Suspend Resume
Data
Timing
Alarm/Clear
Calibration
Status
Alarm State
Data request
Alarm
Trigger
TCLK State Devices
Mode change Control request
MOOC/Backdoor
12
Software Portability

• Generic framework allows reusability of
• Data acquisition model
• Data buffer model
• Control model
• Event model
• Alarm system
• Only classes that contain code for the new
  environment need to be written
• Define control operations (mode change, hardware
  configuration)
• Define data types and structures
• Hardware access classes
• Specific data acquisition routines
• Alarm conditions

13
Class Diagram