Experimental Physics and Industrial Control System
|
Partial success so far, I was able to get the TSEL to grab the timestamp from another record that was set by TSE default 0 (sys clock I think this is?). When I set TSE to -2 can you not write to the TIME field of a record like this
Caput mydevice:abc.TIME 2020-12-14 14:38:49.021827
I was hoping to simulate my digitizer setting the timestamp in my waveform record TIME field.
From: Tech-talk <tech-talk-bounces at aps.anl.gov> On Behalf Of
Manoussakis, Adamandios via Tech-talk
Sent: Monday, December 14, 2020 1:32 PM
To: EPICS tech-talk <tech-talk at aps.anl.gov>
Subject: RE: Timestamping Confusion
Thank you both for the insight, it seems best for us to go a similar path of using TSEL to copy the timestamp from the digitizer to each of our waveform records and using TSE set to -2 to stop the IOC from overwriting the time field (please
correct me if I am wrong on this). I think I just need to understand the best way to get the first timestamp and then use TSEL to pass it along to the other records.
Ralph when you stated to have the digitizer send the timestamp with the data, would I just have my digitizer set the TIME field in the waveform record then?
Thanks for the comments Michael, when you are dealing with hundreds of waveform records and the timestamps are being taken when each record is processed (I would assume these would all be off by some delay if multiple softIOCs are running)
do you then just have a master time waveform to lineup all your other signals to t0? It seems the digitizer would have a time stamp of t0 for all of its signals but the epics records would not all align at the same timestamp since each one isn't processed
at t0 to be timestamped.
The EPICS Device Support needs to know the timestamp t0 (preferably sent with the data by the digitizer) and write it to each record's timestamp when it updates the record.
In that case, by configuring their TSE to -2, all waveform records can use the digitizer timestamp. That timestamp can even be forwarded (using TSEL) through post-processing chains, so that processed data may still use the timestamp that
the digitizer sent with the raw data at the beginning of the chain.
|
- Replies:
- RE: Timestamping Confusion Manoussakis, Adamandios via Tech-talk
- Re: Timestamping Confusion Johnson, Andrew N. via Tech-talk
- References:
- Timestamping Confusion Manoussakis, Adamandios via Tech-talk
- Re: Timestamping Confusion Michael Davidsaver via Tech-talk
- RE: Timestamping Confusion Manoussakis, Adamandios via Tech-talk
- Re: Timestamping Confusion Ralph Lange via Tech-talk
- RE: Timestamping Confusion Manoussakis, Adamandios via Tech-talk
- Navigate by Date:
- Prev:
Help Erika Jones via Tech-talk
- Next:
RE: Timestamping Confusion Manoussakis, Adamandios via Tech-talk
- 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: Timestamping Confusion Manoussakis, Adamandios via Tech-talk
- Next:
RE: Timestamping Confusion Manoussakis, Adamandios via Tech-talk
- 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, 14 Dec 2020 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|