1 / 7

Roadmap

Roadmap. Pixel ROD with full FPGA and basic DSP programming [mid/end Jan 03] Basic Pixel library (access registers, DACS, masks, step masks, basic scan) [mid Feb 03] Interface with TurboDAQ GUI [end Feb/mid Mar 03] Basic interface with DAQ-1 system [May 03] (simple)

haruko
Download Presentation

Roadmap

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Roadmap Pixel ROD with full FPGA and basic DSP programming [mid/end Jan 03] Basic Pixel library (access registers, DACS, masks, step masks, basic scan) [mid Feb 03] Interface with TurboDAQ GUI [end Feb/mid Mar 03] Basic interface with DAQ-1 system [May 03] (simple) Start developing efficient calibration procedures on multi-module setups (DSP+SBC) Start developing monitor/reset procedures (mainly DSP) Support for BOC/TIM Basic DCS interface Study and implementation of a calibration/ configuration DB P. Morettini

  2. Questions • Which is the minimum set of primitives we need? In my mind: • Configure, Send Command, Send sequence of Trigger+Strobe on the master DSP • Dump Events and Make Histograms on the slave DSPs • Better to interface to TurboDAQ via network or by porting the library to Windows (or both) ? • What is needed to use a ROD at the test beam? When? • Power supplies? P. Morettini

  3. Initial allocation of tasks • Basic ROD setup -> LBL • RodModule -> Tom • Basic Pixel Library -> GE • GUI Interface -> ? • BOC/TIM/Opto -> Wuppertal? ( + SCT ) • DCS interface -> Wuppertal? P. Morettini

  4. SCT and Pixel Function Libraries • Beside the system tests we want to start using the ROD as soon as possible on real detectors. We need a software layer to interface the ROD with the end user applications. We would like to have a single software environment for all the applications. • The structure we are implementing consists of: • a generic interface to the ROD and TIM functions (RODModule and TIMModule). We expect these modules to be detector independent, since they support intrinsic ROD capabilities; • a detector (SCT or Pixel) specific function library which implements all the relevant actions the applications must perform of the front-ends; the actions ranges form accessing single FE registers to performing basic scan sequences. P. Morettini

  5. Software support for the ROD Event Display Data Flow Hits, Histograms MRS Messages ROD Crate DAQ DAQ-1 Run Control State transitions GUI or script interpreter Hits, Histograms, Messages Commands Configuration Files/DB Text Editor or Script SCT / Pixel Functions Library DDC DCS RodModule TimModule P. Morettini

  6. Organization of the Pixel Lib • My idea is to follow the structure of the hardware, so one software object mapping a ROD, containing: • 6-26 MCC objects • 16x(6-26) FE objects • a DCS interface • a Calib/Config DB interface • a RodModule and a TimModule objects • The various functions will be available at the corresponding detector level. • An object can use the methods of another object to complete its task. For example, to execute a command a FE object can: • use RodModule to execute the corresponding primitive • create a command stream, send it to its MCC object which will add the MCC preamble and send the result as a parameter to the generic SendCommand ROD primitive. P. Morettini

  7. Pixel Lib examples • // Create a PixelROD object • myROD = new PixelROD(ConfigFileName); • // Get the number of MCC connected • nMCC = myROD->getNMCC(); • // Set a MCC register • myROD->MCC(1)->SetRegister(“FEEN”,0xfff0); • // Configure all the modules • myROD->LoadConfig(); • // Configure a single module • myROD->MCC(3)->LoadConfig(); • // Configure a single FE • myROD->MCC(3)->FE(8)->LoadConfig(); P. Morettini

More Related