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  2020  <20212022  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  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: Autosave PVs showing up as INVALID(UDF_ALARM)
From: Iain Marcuson via Tech-talk <tech-talk at aps.anl.gov>
To: "Mooney, Tim M." <mooney at anl.gov>, "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Thu, 4 Feb 2021 22:26:41 +0000

I checked that the PROC field does process the record, and it does.  I mistyped the fanout record name at startup, which is why those were not propagating, but they are now and I do not have an issue with undefined records.  My problem is now that the records are not propagating to the hardware.  If I process an individual record, the value propagates, but not when I run the fanout record.  Is there a way to slow down the fanout processing, or is this a job for the sequencer?

 

Thank you,

 

Iain.

 

From: Mooney, Tim M. <mooney at anl.gov>
Sent: Wednesday, February 03, 2021 2:59 PM
To: tech-talk at aps.anl.gov; Iain Marcuson <iain.marcuson at sydortechnologies.com>
Subject: Re: Autosave PVs showing up as INVALID(UDF_ALARM)

 

Hi Iain,

 

You could try writing to the PROC field to verify that processing the record clears the UDF field.  If it does, then you could set the TPRO field in the database, and reboot, to check that the fanout record is actually processing the record.

 

Tim Mooney (mooney at anl.gov) (630)252-5417
Beamline Controls Group (www.aps.anl.gov)
Advanced Photon Source, Argonne National Lab


From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Iain Marcuson via Tech-talk <tech-talk at aps.anl.gov>
Sent: Wednesday, February 3, 2021 1:11 PM
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: Autosave PVs showing up as INVALID(UDF_ALARM)

 

I am using autosave in an IOC.  Several PVs show up as INVALID(UDF_ALARM).  Autosave is set to restore in pass 1, and the PVs appear to be in the autosave .sav files.  In addition, I use a series of fanout records to try to force processing of the PVs, although I again get the Undefined status.  Are there any items I can check to try to resolve this?

 

Thank you,

 

Iain Marcuson

Software Engineer, Sydor Technologies

585.278.1168 | www.SydorTechnologies.com

Skype: iain.marcuson at sydorinstruments.com

 


Replies:
Re: Autosave PVs showing up as INVALID(UDF_ALARM) Arnold, Ned D. via Tech-talk
References:
Autosave PVs showing up as INVALID(UDF_ALARM) Iain Marcuson via Tech-talk
Re: Autosave PVs showing up as INVALID(UDF_ALARM) Mooney, Tim M. via Tech-talk

Navigate by Date:
Prev: Re: EPICS Codeathon: March 8 to March 12 Ben Franksen via Tech-talk
Next: Re: Autosave PVs showing up as INVALID(UDF_ALARM) Arnold, Ned D. 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  <20212022  2023  2024 
Navigate by Thread:
Prev: Re: Autosave PVs showing up as INVALID(UDF_ALARM) Mooney, Tim M. via Tech-talk
Next: Re: Autosave PVs showing up as INVALID(UDF_ALARM) Arnold, Ned D. 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  <20212022  2023  2024 
ANJ, 04 Feb 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·