REDNet Status overview Rok Stefanic Ziga Kroflic rok

REDNet - Status overview Rok Stefanic Ziga Kroflic (rok. stefanic@cosylab. com) (ziga. kroflic@cosylab. com) the best people make cosylab

Outline n Quick overview n 1) What has been done so far n 2) What is working n 3) What needs to be done Cosylab 2011 2

Quick overview VAA Activates a Run (+ run file) MTG redistributes the Run file with a list of cycles MTG Generates timing events from the requested cycle VAA requests the generation of a cycle from the run list Receiver components generate responses (digital signals, irq, triggers…) Cosylab 2011 3

1) What has been done so far n GREEN – task went well n ORANGE – slight issues with the task n RED – task was underestimated, more effort spent Cosylab 2011 4

1) What has been done so far n REDNET MTR XML (fml) configuration file o interface defined via shared variables n Timing receiver SW implementation o Dynamically loaded FECOS component o Interface to other FECOS components running on the crate o Interface to Win. CC OA via shared variables(!) § o o Interface implemented partially –> Done Subscription to responses (AIGPO, STB, STL, Fecos event) Acknowledge via MAPS § Cosylab 2011 Does not work yet due to FECOS/MAPS bug 5

1) What has been done so far n Timing receiver HW implementation o Response generation is implemented § § Pulse/toggle on auxiliary interface (4 optic/TTL outputs) Pulses on PXI star trigger lines from MRF EVR to other cards Debugging and correcting inproper backplane connectors § § o Command reception must be implemented -> Done § § o n Timing event distribution to other cards over PXI shared RT trigger bus on PXI backplane Distribution of received timing events to FECOS components HW resource issues to store all data associated with Activate. Run Solved by introduction of “Lightweight” Activate. Run command Revised EVR reset sequence to resolve booting problem MTR design documentation o Interfaces and functionality defined, the documentation needs to be updated -> Users manual for subscribing to responses still needs to be documented Cosylab 2011 6

1) What has been done so far n REDNET MTG XML (fml) configuration file o interface defined via shared variables n Timing master SW implementation o Configuration of component from XML file o SIM interface o Cycle generation § § o Acknowledge mechanism § o Parsing and execution of timing events from sequence files Emission of commands and events over RT and Non-RT link Mechanism implemented in MTG, but does not work in the whole system yet because of FECOS/MAPS bug Heartbeat Cosylab 2011 7

1) What has been done so far n Timing master HW implementation o Deterministic emission of event sequences for 5 execution slots via RT link o Emission of commands via RT link o Emission of heartbeat event via RT link o Emission of asynchronous events over RT link o Emission of events via non-RT link n MTG design documentation o Interfaces and functionality defined, the documentation needs to be reviewed and updated n Test cases o Done up to functionality needed for last i. Week Cosylab 2011 8

2) What is working n Main Timing Receiver o Generation of responses to received timing events on all interfaces § § o SW injection of timing events from LV § o provides generation of timing sequences locally on the receiver 10 MHz clock distribution § o Auxiliary interface Shared real-time trigger Shared trigger lines Software IRQ MRF EVR extracts clock signal from optic link and distributes it over PXI backplane to other cards (PCC Flex. RIO Modules) Full receiver configuration § § Cosylab 2011 by other FECOS components from configuration in shared variables and XML 9

2) What is working n Main Timing Generator o Full receiver configuration § from configuration in shared variables o SIM interface to VAA o MRF EVG low level device support § o Cycle generation § o Allows access to registers and memory in MRF EVG FPGA Emission of event sequences Heartbeat Cosylab 2011 10

3) What needs to be done n MTG Lab. View FECOS component o Dynamic loading of the MTG component § o Synchronous SIM interface enahancements § § o § MAPS is not working properly yet! MAPS messages need to be revised, tags defined Acknowledge functionality § o Add synchronous counterparts to all SIM commands Next. Cycle with Start Immediately MAPS interface to receivers § o Not done yet because of unexpected issues Done but needs to be tested when MAPS is fixed Integration with scratchpad § Cosylab 2011 Because of specifics of timing system, Red. Net cannot use FECOS scratchpad service. Scratchpad behaviour needs to be implemented in the MTG 11

3) What needs to be done n MTG FPGA implementation o Integration with GPS time module § § o Use 10 MHz clock reference Acquire absolute time Time distribution service n MTR FPGA implementation o Time distribution service o Timestamping of events o Propagation delay compensation n PXIe EVR o Migrate and test MTR FPGA functionality on new PXIe EVR cards Cosylab 2011 12

3) What needs to be done n System integration and testing o Testing with large number of different FECOS components that use REDNET services o Testing of MTR on Win and RT systems n Documentation o Continuous update of design documentation o Adding high level test cases and test cases for new functionalities o Users manual for subscription of FECOS components to MTR responses o Review and revise requirements Cosylab 2011 13

Thank you for your attention Questions? Cosylab 2011