Transcript
REDNET Prototype overview Rok Stefanic (
[email protected])
the best people make cosylab
Outline
What does REDNET provide to the users
What we have done in CWO2
What follows in CWO3
Cosylab 2010
2
What does REDNET provide to the users How it looks like prepare data
•
SCS
BDCS
Users and Control Systems PVSS
VAA Supervisory Interface (SI)
User Interface (UI) MTG FECOS
process data in hard realtime
•
1.
LabVIEW code running on crate controller
MTG FECOS Component
MTG PXI Crate
PXI
Fanout
MRF EVG
PXI
Cosylab 2010
3.
MTR FECOS Other FECOS Component components Equipment
receivers w/ equipment
LabVIEW code running on crate controller FECOS
Auxiliary Interfaces
decode events and poke equipment
Transport Layer
MTR MTG MTG
PXI Crate
•
Slow Equipment Interface
Transport
(non real-time feedback link)
2.
Fast Equipment Interface
make sure everybody gets it @ the same time (200m = ~1ms)
•
(real-time optic connection)
MRF EVG
Controlled Equipment Equipment under control
Equipment under control
Equipment under control
3
What does REDNET provide to the users How it works BDCS
PVSS
VAA
UI
R
Requests for activation of accelerator runs
VAA announces a Run
SI
Server
Retrieval and storing the MTG accelerator cycle files to the MTG local storage
GPS Receiver
Res
Req
Req
Database
GPS Current time
Req
Res
GPS 10 MHz clock signal GPS 1PPS Trigger signal
MTG prepares the cycles
Loading of cycles belonging to a requested run from local storage into memory
FECOS Component
Internal HW interface (cPCI)
RAM
PXI backplane Internal HW interface (cPCI)
hard drive
MRF EVG
PXI - System Controller
Loading of individual cycles into the EVG module
Req
ProfiBUS
Fast Equipment Interface - FEI (real-time fiber optic link)
Res
Slow Equipment Interface - SEI (Gigabit Ethernet)
Interlock
FEI Fanout Ack
Acknowledging received commands
Device specific FECOS Component
Device specific configuration retrieval (desired responses...)
MTR FECOS Component
Emission of timing events and commands
MTRPXI PXI MTR MTR PXI
Device specific FECOS component configures the MTR with desired responses GPS 10 MHz clock signal extraction from the FEI and its distribution to PXI modules
Internal HW interface (cPCI)
PXI backplane
RAM
Internal HW interface (cPCI)
Timing Events
hard drive
MRF EVR
PXI - System Controller T
FlexRIO
FlexRIO
ProfiBUS Commands
Reception of timing events and commands
X
Receivers generate responses (dig. outputs, irq, triggers…)
Auxiliary Interface AI1
Equipment under control
Cosylab 2010
FEI
Distribution of timing events to all receiver components
VAA asks the MTG to start the run
MTG generates timing events
MTG PXI Ack
Auxiliary Interface AI2
Auxiliary Interface AI3
Interlock
Generation of responses to received timing events
4
What does REDNET provide to the users MTG
PXI crate Controller LV RT MRF EVG
5 Execution slot tables (priorities) 1ms granularity of event emission Emission of asynchronous timing events 10 Hz heartbeat timing event (time grid) GPS time and clock distribution Cosylab 2010
5
What does REDNET provide to the users MTR – controlling the devices
PXI Controller LV RT MRF EVR Other PXI modules Cosylab 2010
Digital/optical outputs Re-distribution of timing events to PXI cards Trigger neighbor PXI cards LabView application notification
6
What does REDNET provide to the users MTR - controlling the devices
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
What does REDNET provide to the users Responses – Auxiliary interface outputs
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
What does REDNET provide to the users Responses – Redistribution of events to PXI cards
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
What does REDNET provide to the users Responses – Triggering PXI cards
Trigger pulses generated on PXI star trigger lines
Useful for simple devices (ADC cards etc.) which only need trigger signals
Cosylab 2010
10
What does REDNET provide to the users Responses - LabView application notification
IRQ to CPU @ specific timing event
Received event delivered to FECOS components running in parallel
Cosylab 2010
11
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
What have we done in CWO2 REDNET Prototype
Cosylab 2010
13
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
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
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
Thank you for your attention Questions?
Cosylab 2010
