REDNET Prototype overview Rok Stefanic the best people make cosylab

Outline What does REDNET provide to the users What we have done in CWO2 What follows in CWO3 Cosylab

What does REDNET provide to the users How it looks like SCS 1. MTG 2. Transport 3. receivers w/ equipment Cosylab prepare data process data in hard real- time make sure everybody gets the same time (200m = ~1  s) decode events and poke equipment

MTG prepares the cycles VAA asks the MTG to start the run Receivers generate responses (dig. outputs, irq, triggers…) What does REDNET provide to the users How it works Cosylab VAA announces a Run MTG generates timing events

What does REDNET provide to the users MTG Cosylab PXI crate Controller LV RT MRF EVG 5 Execution slot tables (priorities) 1  s granularity of event emission Emission of asynchronous timing events 10 Hz heartbeat timing event (time grid) GPS time and clock distribution

What does REDNET provide to the users MTR – controlling the devices Cosylab Digital/optical outputs Re-distribution of timing events to PXI cards Trigger neighbor PXI cards LabView application notification Cosylab PXI Controller LV RT MRF EVR Other PXI modules

What does REDNET provide to the users MTR - controlling the devices Cosylab No configuration files needed. Device specific application requests the MTR which responses it needs (+ parameters such as timing event, pulse delay, width…) Multiple interfaces can be used concurrently Cosylab

What does REDNET provide to the users Responses – Auxiliary interface outputs Cosylab Pulses or output toggle Configurable pulse delay and width (< 10 ns steps) Each digital/optic output can have different configuration (ES, event, delay, width, type) Cosylab

What does REDNET provide to the users Responses – Redistribution of events to PXI cards Cosylab Received timing event is distributed to other PXI modules EVR distributes timing event value and execution slot to which the event belongs Cosylab

What does REDNET provide to the users Responses – Triggering PXI cards Cosylab Trigger pulses generated on PXI star trigger lines Useful for simple devices (ADC cards etc.) which only need trigger signals Cosylab

What does REDNET provide to the users Responses - LabView application notification Cosylab IRQ to specific timing event Received event delivered to FECOS components running in parallel Cosylab

What we have done in CWO2 Documentation  Requirements in detail  Top level architecture and design  Test cases  All documentation as Enterprise Architect models Fully mastered the MRF EVG and EVR cards  LabView + cPCI + FPGA Gbps fiber link Prototype  MTG Supervisory app  Emission of timing events, commands, asyn. events, acknowledgments, uses FECOS… Cosylab

What have we done in CWO2 REDNET Prototype Cosylab

What have we done in CWO2 REDNET Mock-up demo Listing of available sequence files on HDD Sequence file editing Emission and reception:  Timing events  Commands  Asynchronous timing events Acknowledgments  Each MTR sends ACK  MTG lists all received ACKs Cosylab

What have we done in CWO2 REDNET Prototype contd. Response generation:  I/O signals on MRF EVR  Received events distributed over PXI RT trigger bus (PCC)  SW notifications  User can configure responses Cosylab

What follows in CWO3 Internal architecture design for the MTG and MTR:  LabView application  FPGA (MRF EVG & EVR) Implementation of the system  Full size accelerator cycles  HDD utilization management  Full auxiliary interface outputs support  Heartbeat event generation  MTR & MTG configuration (xml files)  Execution slot support  Synchronization with GPS  … Cosylab

Cosylab 2010 Thank you for your attention Questions?