rednet prototype overview rok stefanic ([email protected])[email protected] the best...
TRANSCRIPT
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 usersHow 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 =
~1s)
• decode events and poke
equipment
MTGMTG
LabVIEW code running on crate controller
Transport Layer
Fast
Equ
ipm
ent I
nter
face
(re
al-t
ime
opt
ic c
onn
ect
ion)
PVSS
MTG
MTG FECOS Component
MRF EVG
Equipment
BDCS
VAA
Fanout
MTR
MTR FECOS Component
MRF EVG
PXI Crate
FECOS
Equipment under
control
PXI
Users and Control Systems
FECOS
Slow
Equ
ipm
ent I
nter
face
(no
n re
al-t
ime
feed
bac
k lin
k)
PXI
LabVIEW code running on crate controller
Controlled Equipment
PXI Crate
User Interface (UI)
Supervisory Interface (SI)
Auxi
liary
In
terf
aces
Equipment under
control
Equipment under
control
Other FECOS components
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 usersHow it works
Cosylab 2010 4
MTR PXIMTR PXI
MTG PXI
Server DatabaseR
PXI - System Controller
FECOS Component
hard drive
RAM
VAAPVSS
BDCS
UI SI
MRF EVG
FEI Fanout
Internal HW interface (cPCI)
Internal HW interface (cPCI)
Fast Equipment Interface - FEI (real-time fiber optic link)
Slo
w E
qu
ipm
en
t In
terf
ace
- S
EI
(Gig
ab
it E
the
rne
t)
ProfiBUS
TX
MTR PXI
MRF EVR
Internal HW interface (cPCI)
Internal HW interface (cPCI)
FlexRIOFlexRIO ProfiBUS
AuxiliaryInterface
AI1
AuxiliaryInterface
AI2
AuxiliaryInterface
AI3Interlock
Interlock
FEI
Req Req
ResReq
Ack
Timing Events
Commands
Equipment under control
Load
ing
of c
ycle
s be
long
ing
to a
req
uest
ed r
un fr
om lo
cal
stor
age
into
mem
ory
Req
uest
s fo
r ac
tivat
ion
of a
ccel
erat
or r
uns
Loading of individual cycles into the EVG module
Emission of timing events and commands
Distribution of tim
ing events to all receiver com
ponents
Retrieval and storing the MTG accelerator cycle files to the MTG local storage
Rec
eptio
n of
tim
ing
even
ts a
nd c
omm
ands
Acknowledging received commands
Res
Generation of responses to received timing events
Device specific FECOS component configures the MTR with desired responses
GPS Receiver
GPS 1PPS Trigger signal
PXI backplane
GPS 10 MHz clock signal
GPS Current time
GPS 10 MHz clock signal extraction from the FEI and its distribution to PXI modules
PXI - System Controller
Device specificFECOS
Component
hard drive
MTRFECOS
Component
RAM PXI backplane
Req
Res
Ack
Device specific configuration retrieval(desired responses...)
VAA announces a Run
MTG generates timing events
What does REDNET provide to the usersMTG
Cosylab 2010 5
PXI crate Controller LV RT MRF EVG
5 Execution slot tables (priorities) 1s 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 usersMTR – 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
What does REDNET provide to the usersMTR - 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
What does REDNET provide to the usersResponses – 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
What does REDNET provide to the usersResponses – 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
What does REDNET provide to the usersResponses – 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
What does REDNET provide to the usersResponses - LabView application notification
Cosylab 2010 11
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 CWO2REDNET Prototype
Cosylab 2010 13
What have we done in CWO2REDNET 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 CWO2REDNET 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
Cosylab 2010
Thank you for your attention
Questions?