RE: Autosave PVs showing up as INVALID(UDF_ALARM)

[Iain Marcuson via Tech-talk <tech-talk at aps.anl.gov>]

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