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 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
<== Date ==> <== Thread ==>

Subject: RE: Default value to field SCAN
From: Mark Rivers <rivers@cars.uchicago.edu>
To: Gabriel de Souza Fedel <gabriel.fedel@lnls.br>, "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Tue, 3 Jan 2017 13:11:30 +0000
Those dbScan warnings are very unusual.  It makes me think there is something wrong with the timer system, because, for example the 0.5 second scan thread appears to be running much faster than 0.5 seconds, since it is averaging 0.00 seconds.  What operating system is this? 

Mark

________________________________________
From: tech-talk-bounces@aps.anl.gov [tech-talk-bounces@aps.anl.gov] on behalf of Gabriel de Souza Fedel [gabriel.fedel@lnls.br]
Sent: Tuesday, January 03, 2017 5:57 AM
To: tech-talk@aps.anl.gov
Subject: Default value to field SCAN

Hi,

When I create records and don't set the field SCAN, what is the default
value? There is an way to change this?

I'm having problems with a set of records without SCAN field that are
consuming a lot of CPU, and receiving this messages:

dbScan warning from '.2 second' scan thread:
         Scan processing averages 0,00 seconds (0,00 .. 0,02).
         Over-runs have now happened 283681 times in a row.
         To fix this, move some records to a slower scan rate.

dbScan warning from '.5 second' scan thread:
         Scan processing averages 0,00 seconds (0,00 .. 0,03).
         Over-runs have now happened 290049 times in a row.
         To fix this, move some records to a slower scan rate.

dbScan warning from '.1 second' scan thread:
         Scan processing averages 0,00 seconds (0,00 .. 0,03).
         Over-runs have now happened 278431 times in a row.
         To fix this, move some records to a slower scan rate.


If i remove small choices from dbd file (.1, .2 and .5 seconds) solves
the problem. Apparently the records are being created with all SCAN
values...some idea to solve this?

Regards,

--
Gabriel Fedel
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)
gabriel.fedel@lnls.br | +55 (19) 3512 1226
www.lnls.cnpem.br


Replies:
Re: Default value to field SCAN Gabriel de Souza Fedel
References:
Default value to field SCAN Gabriel de Souza Fedel

Navigate by Date:
Prev: Re: Asyn support Stefen Paul
Next: Re: Default value to field SCAN Gabriel de Souza Fedel
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
Navigate by Thread:
Prev: Re: Default value to field SCAN Henrique Almeida
Next: Re: Default value to field SCAN Gabriel de Souza Fedel
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
ANJ, 14 Feb 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·