Summary of CSC Track-Finder Trigger Control Software

Darin Acosta

University of Florida

9 November 2004

Trigger Software Meeting 2Darin Acosta, University of Florida

CSC Track-Finder Configuration & Testing

BoardsHigher level SP02 command panel windows

Java interface to XDAQ-based software framework

LUT loading

9 November 2004

Trigger Software Meeting 3Darin Acosta, University of Florida

Firmware & LUT loading The look-up tables on the CSC Sector Processor are

loaded via a HAL-based command line program Can be called from the Java GUI, or from a script that loads all

needed LUTs We can program multiple chips and boards in parallel

(many identical tables) Updates to the board firmware stored in EPROMs are

loaded via a custom VMEJTAG program based on software by National Semiconductor and SBS

Callable from command-line scripts Recently incorporated into the “JAL” package developed by

H.Sakulin, and successfully tested! We will port our environment to use JAL for firmware

loading, in order to strive for a uniform software architecture

9 November 2004

Trigger Software Meeting 4Darin Acosta, University of Florida

Test Software Most test software to validate the on-board SP

functionality as well as to perform interface tests between boards are written as HAL-based command line programs

Again callable from the Java GUI For example, last week we successfully conducted a

second DT/CSC Track-Finder integration test Program loads data into FIFO on CSC TF, then injects data to

DT TF (or in loop-back to CSC TF) which is captured and read out.

We expected to use an “inject pattern” command distributed via the TTC to conduct the test, but in practice last week we triggered on the data itself.

CSC and DT software are different products and not integrated. In practice this was not much of a handicap, but for in-situ

trigger tests at CMS we should evolve to a common control

9 November 2004

Trigger Software Meeting 5Darin Acosta, University of Florida

TestBeam DAQ and Beyond For the 2004 beam tests, we could log CSC Track-

Finder data through the VME controller using a standalone HAL program or through an XDAQ-based event-builder

We partitioned the XDAQ modules so that everything could be controlled either through the Track-Finder GUI, the Testbeam Run Control, or any other control software that sends i2o messages

9 November 2004

Trigger Software Meeting 6Darin Acosta, University of Florida

XDAQ Partitioning

TrackFinder Crate

GUI PC (Linux)

TF PC (Linux)

Network Switch

GUIDriver

TFDriver

SBS (Bit3)

TFGUI

I2o Messages

SOAP Messages

HAL

Hardware Level

Software Level

PC Level

PC Level

Other apps can

send messages to here

9 November 2004

Trigger Software Meeting 7Darin Acosta, University of Florida

The Integrated EMU GUI

The Track-Finder GUI has been extended to include the XDAQ-based run control system for CSC beam tests

Controls 4 crates: 2 Peripheral crates, Track-Finder crate, TTC crate

DB calls to store configuration parameters

Evolving to become a Slicetest control