Experimental Physics and Industrial Control System
|
Hello, Bob.
We are in the project phase of Sirius' beamlines control system. We did the requirements gathering with the researchers and no one cited the synchronization with the accelerator timing system, with one exception: the pump and probe experiments. So it seemed
that it was a special case.
But some time ago I was evaluating a Zebra Box and asked a friend that works with beamlines in the USA to comment about his impressions on this system. Among some things he told me that Zebra Box lacks from direct connection with the EVG and that is an
important feature because he needed to get the global timestamp from it.
So, I thought that, maybe, we don't know yet that we will need to synchronize events during some other experiments like quick exafs, fly scan mapping, and tomography. That's why I'm talking to you guys, that have more experience on beamline's timing system.
Thank you very much,
--
Márcio Paduan Donadio
Engenheiro de Computação - Software de Operação das Linhas de Luz
Laboratório Nacional de Luz Síncrotron – (LNLS)
Centro Nacional de Pesquisa em Energia e Materiais (CNPEM)
+ 55 (19) 3512-3520 - [email protected]
www.lnls.cnpem.br
Em 09-11-2016 17:52, bob dalesio escreveu:
First a disclaimer: The actual EPICS developers always have a better answer about the technology as is.
That said, I will take a shot at it:
Hi Marcio,
This is really a question that starts at the beam line.
What do they want? Do they care about the energy? at what precision?
There are independent timing systems implemented in FPGAs with different specifications. If you cannot buy hardware, working with this firmware allows you to build your own.
EPICS time stamps can be derived from different timing sources. If you use PTP, as I understand it, you have to purchase a master as well (is that right?). So, it is important to know what your beam lines want and your cost constraints.
EPICS itself in version 3 has time to the nsec. The MRF timing hardware time stamp resolution is 8 nsec. The jitter is < 10 psec. It can easily be extended to the beam lines. Slow signals, like beam energy, can be sent over the timing
system along with time stamp information that could be put into the metadata for the experiment. LCLS II timing has sub nsec time derived at the EVR from the EVG (both homemade at SLAC). PVAccess has 64 bits for subsecond instead of 32 bits. It also has a
user defined extension for pulse ID or other user defined identifier.
- Bob
|
- Replies:
- RE: Opinion on timing system for synchrotron beamlines isa.uzun
- References:
- Opinion on timing system for synchrotron beamlines Márcio Paduan Donadio
- Re: Opinion on timing system for synchrotron beamlines bob dalesio
- Navigate by Date:
- Prev:
RE: Native NI LabVIEW/EPICS integration Mark Rivers
- Next:
Re: Native NI LabVIEW/EPICS integration Luca Cavalli
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Opinion on timing system for synchrotron beamlines bob dalesio
- Next:
RE: Opinion on timing system for synchrotron beamlines isa.uzun
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
|
ANJ, 10 Nov 2016 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|