1. REDNET Prototype overview Rok Stefanic (rok.stefanic@cosylab.com)rok.stefanic@cosylab.com the best people make cosylab

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

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

4. 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 2010 4 VAA announces a Run MTG generates timing events

5. What does REDNET provide to the users MTG Cosylab 2010 5 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

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

7. What does REDNET provide to the users MTR - controlling the devices Cosylab 2010 7 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 2010 7

8. What does REDNET provide to the users Responses – Auxiliary interface outputs Cosylab 2010 8 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 2010 8

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

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

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

12. 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 + 2.5 Gbps fiber link Prototype  MTG Supervisory app  Emission of timing events, commands, asyn. events, acknowledgments, uses FECOS… Cosylab 2010 12

13. What have we done in CWO2 REDNET Prototype Cosylab 2010 13

14. 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 2010 14

15. 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 2010 15

16. 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 2010 16

17. Cosylab 2010 Thank you for your attention Questions?