Experimental Physics and
Industrial Control System

Hi James,

It's normal for the time stamp to stay the same while the scaler is counting.

.CNT field is posted before the data.  Then the time stamp is set to the current time.
Then .VAL is posted after the data.  Maybe the timing of the time stamp should be rethought.

If you write to the .CNT fiels with a caPutCallback (or a putCallback link) the data will
be posted before the callback is sent.

.SS and .US are not intended for device support.

Tim


________________________________________
From: [email protected] [[email protected]] on behalf of James Rezende Piton - LNLS [[email protected]]
Sent: Friday, March 28, 2014 4:13 PM
To: [email protected]
Subject: Scaler expected behaviour

Dear all,

Is that the expected behaviour with a scaler record?

With camonitor we get:

SAXS1:SCALER01.S2              2014-03-28 17:15:59.223015 150289
SAXS1:SCALER01.S1              2014-03-28 17:15:59.223015 2.9883e+08
SAXS1:SCALER01.S2              2014-03-28 17:15:59.223015 150372
SAXS1:SCALER01.S1              2014-03-28 17:15:59.223015 2.9896e+08
SAXS1:SCALER01.S2              2014-03-28 17:15:59.223015 150437
SAXS1:SCALER01.S1              2014-03-28 17:15:59.223015 2.9909e+08
SAXS1:SCALER01.S2              2014-03-28 17:15:59.223015 150489
SAXS1:SCALER01.S1              2014-03-28 17:15:59.223015 2.99231e+08
SAXS1:SCALER01.S2              2014-03-28 17:15:59.223015 150556
SAXS1:SCALER01.S1              2014-03-28 17:15:59.223015 2.9936e+08
SAXS1:SCALER01.S2              2014-03-28 17:15:59.223015 150631
SAXS1:SCALER01.S1              2014-03-28 17:15:59.223015 2.9949e+08
SAXS1:SCALER01.S2              2014-03-28 17:15:59.223015 150686
SAXS1:SCALER01.S1              2014-03-28 17:15:59.223015 2.9962e+08
SAXS1:SCALER01.S2              2014-03-28 17:15:59.223015 150741
SAXS1:SCALER01.S1              2014-03-28 17:15:59.223015 2.9975e+08
SAXS1:SCALER01.S2              2014-03-28 17:15:59.223015 150811
SAXS1:SCALER01.S1              2014-03-28 17:15:59.223015 2.9988e+08
SAXS1:SCALER01.S2              2014-03-28 17:15:59.223015 150883
SAXS1:SCALER01.CNT             2014-03-28 17:15:59.223015 Done
SAXS1:SCALER01.S1              2014-03-28 17:15:59.223015 3e+08
SAXS1:SCALER01.S2              2014-03-28 17:15:59.223015 150945

We have SAXS1:SCALER01.RATE = 60, .TP = 30 and .FREQ = 1e+07. Our
EPICS base is 3.14.11 and scaler record as in std-2-8.

a) the timestamp is frozen. Is that normal?

b) how to ensure I can read the updated counts immediately after .CNT
goes "Done"? Or perhaps one should wait a minimal time before reading
the final count?!

c) are .SS and .US relevant fields to a scaler device support developer?

Thanks!

James
LNLS, Brazil

References:

Scaler expected behaviour James Rezende Piton - LNLS

Navigate by Date:

Prev: Scaler expected behaviour James Rezende Piton - LNLS

Next: Re: MJPEG Video Display for CS-Studio Xihui Chen

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: Scaler expected behaviour James Rezende Piton - LNLS

Next: Multiple IOCs on one Linux host Ralph Lange

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