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  <20112012  2013  2014  2015  2016  2017  2018  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018 
<== Date ==> <== Thread ==>

Subject: About pvPut dafault behavior
From: <jun-ichi.odagiri@kek.jp>
To: "EPICS tech-talk" <tech-talk@aps.anl.gov>
Date: Fri, 25 Feb 2011 09:31:24 +0900
Dear all;

I'm looking into the following site to check if pvPut of seq-2.0.11
works synchronously or asynchronously (with NO compiler option and
NO explicit SYNC/ASYNC option, just a pvPut(pvname) call).

http://www-csr.bessy.de/control/SoftDist/sequencer/Manual.html

In "Notes on Release 2.0 (Synchronous/asynchronous override on gets and 
puts)",

it says as follwos:

"pvGet and pvPut both accept an optional SYNC or ASYNC argument that, 
for pvGet, overrides the default as set using the -a option and, for 
pvPut, overrides the default synchronous behavior."

So, I thought pvPut(pvname) works synchronously. However, it say in
"Asynchronous Use of pvPut" as follows:

"Normally the pvPut operation completes asynchronously. In the past it 
has been the responsibility of the programmer to ensure that the 
operation completed (typically by monitoring other variables). However, 
the function pvPutComplete can now be used for this."

So, I'm getting confused.

Does pvPut(pvname) work synchronously, or asynchronously by default?

Sorry in advance if I'm bothering you all due to my poor ability in
reading English.

p.s.
I observed strange behavioir of pvPut(pvname, SYNC) when it tries to
put a value form an IOC to another IOC over the network. Calling
pvPut(pvname) works just fine. I might report it later after I check
it again and if I conform that the problem really exists or not.

Jun-ichi Odagiri
High Energy Accelerator Research Organization (KEK)




Replies:
Re: About pvPut dafault behavior Benjamin Franksen

Navigate by Date:
Prev: Re: Asyn record DBD Rolf Keitel
Next: Does areadetector drvier support Procilica GE1650 CCD? Silver
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018 
Navigate by Thread:
Prev: problem with VxWorks RTC (seems to be caused by tpmac Delta Tau communications, creates problems with autosave) Jay Steele
Next: Re: About pvPut dafault behavior Benjamin Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  <20112012  2013  2014  2015  2016  2017  2018 
ANJ, 18 Nov 2013 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·