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  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: SYNC not updating VAL - motor
From: "Mooney, Tim M." <[email protected]>
To: Márcio Paduan Donadio <[email protected]>, "[email protected]" <[email protected]>
Date: Mon, 7 Apr 2014 17:07:41 +0000
Hi Marcio,

I think that's fixed in R6.8.
Tim

From: [email protected] [[email protected]] on behalf of Márcio Paduan Donadio [[email protected]]
Sent: Monday, April 07, 2014 8:59 AM
To: [email protected]
Cc: Márcio Paduan Donadio
Subject: SYNC not updating VAL - motor

 

                               Dear all,

 

                I’m using motor record 6-5. Let’s say my record’s name is simply RECORD. Some of the PVs are:

-          RECORD.LLM = 1350

-          RECORD.HLM = 1410

-          RECORD.VAL = 0

-          RECORD.RDBL = “A_VALID_PV”

-          RECORD.URIP = 1

-          RECORD.RRES = 1   

 

After boot, I wrote 1 in RECORD.STUP and RECORD.RBV received the value of the PV in RDBL, that was 1400. RECORD.VAL remained 0, as expected. But when I wrote 1 in RECORD.SYNC, the VAL field didn’t not change.

 

So I tried another test. I changed RECORD.LLM to -1 and I wrote 1 in RECORD.SYNC again. This time, the VAL field was updated to 1400.

 

I think that, if RBV is inside limits, there is no reason to block VAL update using SYNC.

 

Thank you,

 

                Márcio Paduan Donadio

                Computer Engineer – CNPEM / LNLS (Brazilian Synchrotron)

               


References:
SYNC not updating VAL - motor Márcio Paduan Donadio

Navigate by Date:
Prev: RE: Streamdevice 2.6 autoconnection failure using drvAsynSerialPort Mark Rivers
Next: asyn/areaDetector: minimize number of warning messages Piccoli, Luciano
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: SYNC not updating VAL - motor Márcio Paduan Donadio
Next: Streamdevice 2.6 autoconnection failure using drvAsynSerialPort Mazanec Tomáš
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  <20142015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 17 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·