EPICS Controls Argonne National Laboratory

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  <20202021  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  <20202021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Timestamp reset event in EVR
From: Di Wang via Tech-talk <tech-talk at aps.anl.gov>
To: Michael Davidsaver <mdavidsaver at gmail.com>
Cc: tech-talk at aps.anl.gov
Date: Wed, 18 Mar 2020 01:13:07 +0900
Hi Michael,

  I found an event lost situation in my MRF VME-EVR-230RF, so I am wondering how will mrfioc2 handle the event received right after the timestamp reset event (i.e. 125) ?

We might send event code only 1 tick (i.e. 9 nanosecond) later than before one, so the 'right after' could be very fast. Here is a brief example.

Event       Timestamp
1           953053925.999,917,620
125       953053925.999,977,626  <-----TS reset event
2 <-----lost, and the timestamp should be 953053926.999,977,650
3            953053926.000,100,043
4            953053926.000,450,210


  I understand that when TS reset event is received the 32-bit seconds register will be reset, and below callback function would be called, but I still do not understand the process logic and the reason of event lost.

https://github.com/epics-modules/mrfioc2/blob/7bee26590cb5fea8117d0a12920bc281ab1c7cd8/evrMrmApp/src/drvem.cpp#L1430

  For you convenience, some information might help:
epics 3.15.5, devlib 2-2.10, mrfioc 2-2.2.0 (I added several functions to buffer the events in drvem.cpp) event clock: 114 MHz, repetition rate: 50 Hz, more than 120 events are monitored

Regards,
Di WANG
Linac Control Group, KEK


Replies:
Re: Timestamp reset event in EVR Michael Davidsaver via Tech-talk

Navigate by Date:
Prev: Re: How can I add multiple serial ports in a single IOC? Lang, Keenan C. via Tech-talk
Next: RE: caproto-monitor exits when IOC exits too Allan, Daniel 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  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: RE: caproto-monitor exits when IOC exits too Allan, Daniel via Tech-talk
Next: Re: Timestamp reset event in EVR Michael Davidsaver 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  <20202021  2022  2023  2024 
ANJ, 17 Mar 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·