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  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  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  <2024
<== Date ==> <== Thread ==>

Subject: caput with ca_put_callback
From: Hinko Kocevar via Tech-talk <tech-talk at aps.anl.gov>
To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Fri, 19 Apr 2024 12:30:02 +0000
I'm playing around with the motor record (motorMotorSim) and how one could abort the motion in progress.

With initial position at 0 I do the following in three terminals ; executing commands one after another:

TERM1:
$ camonitor IOC:m1.RBV
IOC:m1.RBV                     2024-04-19 14:17:15.641496 0  
IOC:m1.RBV                     2024-04-19 14:17:22.458046 0.02  
IOC:m1.RBV                     2024-04-19 14:17:22.558330 0.09  
...
IOC:m1.RBV                     2024-04-19 14:17:37.500906 14.99  
IOC:m1.RBV                     2024-04-19 14:17:37.601177 15  


TERM2:
$ caput -l -c -w 20 IOC:m1.VAL 15
Old : IOC:m1.VAL                     2024-04-19 14:17:15.641496 0  
New : IOC:m1.VAL                     2024-04-19 14:17:37.601294 15  


TERM3:
$ caput -l -c -w 20 IOC:m1.STOP 1
Old : IOC:m1.STOP                    2024-04-19 14:17:23.059605 0  
New : IOC:m1.STOP                    2024-04-19 14:17:37.601294 0  


The TERM3 caput to .STOP is waiting TERM2 caput to .VAL to finish.

If the caput command in TERM3 is not using the ca_put_callback then the motor motion is aborted immediately as seen below:

TERM1:
$ camonitor IOC:m1.RBV
IOC:m1.RBV                     2024-04-19 14:24:48.447635 0  
IOC:m1.RBV                     2024-04-19 14:24:54.863364 0.02  
IOC:m1.RBV                     2024-04-19 14:24:54.963617 0.09  
...
IOC:m1.RBV                     2024-04-19 14:24:57.269834 2.3  
IOC:m1.RBV                     2024-04-19 14:24:57.370032 2.31  


TERM2:
$ caput -l -c -w 20 IOC:m1.VAL 15
Old : IOC:m1.VAL                     2024-04-19 14:24:48.447635 0  
New : IOC:m1.VAL                     2024-04-19 14:24:57.370032 2.31  


TERM3:
$ caput -l -w 20 IOC:m1.STOP 1
Old : IOC:m1.STOP                    2024-04-19 14:24:57.069324 0  
New : IOC:m1.STOP                    2024-04-19 14:24:57.085839 0  


can someone explain what is going on in the first case with caput command both using ca_put_callback ?

Thanks,
//hinko

Replies:
Re: caput with ca_put_callback Torsten Bögershausen via Tech-talk

Navigate by Date:
Prev: Device- and Signal-Naming Convention Thomas Birke via Tech-talk
Next: Re: caput with ca_put_callback Torsten Bögershausen 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  2021  2022  2023  <2024
Navigate by Thread:
Prev: Device- and Signal-Naming Convention Thomas Birke via Tech-talk
Next: Re: caput with ca_put_callback Torsten Bögershausen 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  2021  2022  2023  <2024
ANJ, 19 Apr 2024 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·