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: Re: Question about two minor issues with IOCs
From: "Mooney, Tim M. via Tech-talk" <[email protected]>
To: "[email protected]" <[email protected]>, "Wlodek, Jakub" <[email protected]>
Date: Thu, 16 Jan 2020 17:31:32 +0000
Hi Jakub,

The first issue seems to be an error message from device support that is only coincidentally associated with normal-status messages from autosave.

I don't understand the second issue.  You might get more information by inserting this:

epicsThreadSleep(5.)

before the call to create_monitor_set().  This should tell us if the buffer messages actually do result from actions by autosave.

Tim Mooney ([email protected]) (630)252-5417
Beamline Controls Group (www.aps.anl.gov)
Advanced Photon Source, Argonne National Lab


From: Tech-talk <[email protected]> on behalf of Wlodek, Jakub via Tech-talk <[email protected]>
Sent: Thursday, January 16, 2020 9:52 AM
To: [email protected] <[email protected]>
Subject: Question about two minor issues with IOCs
 
Hi all,

I have been working on setting up some new USB cameras at a beamline recently, and I noticed two errors showing up in the IOC
shell, though the IOCs for the cameras actually work fine after startup. I wanted to ask if anyone knows why these show up, and how
to resolve them. To make sure it wasn't specific to the driver I had written, I compiled ADSimDetector against the same base, asyn etc,
and I still saw them showing up:

The first seems to be an issue with autosave, as this shows up right after reboot_restore starts:
----------------------------------------------------------------------------
reboot_restore: entry for file 'auto_settings.sav'
reboot_restore: Found filename 'auto_settings.sav' in restoreFileList.
*** restoring from './autosave/auto_settings.sav' at initHookState 6 (before record/device init) ***
reboot_restore: done with file 'auto_settings.sav'

Error (511,511) PV: 13SIM1::TIMEZONE devStringinEnvVar (init_record) Illegal INP parm field


The second issue happens after the auto_settings.req file is loaded:
------------------------------------------------------------------------------
create_monitor_set("auto_settings.req", 30, "P=13SIM1:")
callbackRequest: cbLow ring buffer full
callbackRequest: cbLow ring buffer full
callbackRequest: cbLow ring buffer full

And is buffer full message is repeated ~30 times.

After all of these messages, I get a message that all the PVs are connected, and the IOC runs with no issues, which is puzzling to me.
If anyone could give me some advice on the source and solution to these that would be great.

Regards,
Jakub Wlodek

References:
Question about two minor issues with IOCs Wlodek, Jakub via Tech-talk

Navigate by Date:
Prev: Question about two minor issues with IOCs Wlodek, Jakub via Tech-talk
Next: EDM website and status J. Lewis Muir 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: Question about two minor issues with IOCs Wlodek, Jakub via Tech-talk
Next: RE: Question about two minor issues with IOCs Mark Rivers 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, 16 Jan 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·