Experimental Physics and
Industrial Control System
| 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 | 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 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: SynApps sscan record: timestamp issue for BUSY DATA and EXSC fields; causing problem archiving with Phoebus Archive engine |
| From: | Ralph Lange via Tech-talk <tech-talk at aps.anl.gov> |
| To: | EPICS Tech Talk <tech-talk at aps.anl.gov> |
| Date: | Tue, 14 Sep 2021 14:49:03 +0200 |
On Tue, 14 Sept 2021 at 12:20, Kuldeep Joshi via Tech-talk <tech-talk at aps.anl.gov> wrote:
I am getting the following output from camonitor for BUSY DATA and EXSC field of sscan record. I see in camonitor the timestamp for the sscan BUSY field is same for busy state and not busy.
The timestamp of an EPICS record is defined as the time when the record was processed for the last time. If a record is sending multiple monitor updates on the same field during a single processing, their timestamps will be the same.
If you rather want the timestamps of each update to be the time when that particular update was sent, have a look at the "ts" (timestamp) filter in EPICS Base.
Cheers,
~Ralph
- References:
- SynApps sscan record: timestamp issue for BUSY DATA and EXSC fields; causing problem archiving with Phoebus Archive engine Kuldeep Joshi via Tech-talk
- Navigate by Date:
- Prev: Re: SynApps sscan record: timestamp issue for BUSY DATA and EXSC fields; causing problem archiving with Phoebus Archive engine Mark Rivers via Tech-talk
- Next: Re: SynApps sscan record: timestamp issue for BUSY DATA and EXSC fields; causing problem archiving with Phoebus Archive engine Mooney, Tim M. 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: SynApps sscan record: timestamp issue for BUSY DATA and EXSC fields; causing problem archiving with Phoebus Archive engine Mark Rivers via Tech-talk
- Next: Re: SynApps sscan record: timestamp issue for BUSY DATA and EXSC fields; causing problem archiving with Phoebus Archive engine Mooney, Tim M. 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
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·