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 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
<== Date ==> <== Thread ==>

Subject: issue with either camonitor or pcaspy in 3.15?
From: Jameson Graef Rollins <jrollins@ligo.caltech.edu>
To: EPICS tech-talk <tech-talk@aps.anl.gov>
Date: Thu, 02 Nov 2017 14:14:56 -0700
Hi, all.  I'm noticing a strange behavior when using the camonitor
command line tool in EPICS 3.15.  I'm seeing a behavior change between
3.15 and 3.14.

I have a test pcaspy IOC running that is serving four channels.  (As an
aside, I am also slightly suspicious that the problem could be in
pcaspy, but I'm not sure).  I launch the IOC, so it has so far seen no
client connections.  I then connect with camonitor:

$ camonitor T1:TEST-{A,B,C,D}
T1:TEST-A                      2017-11-02 13:57:42.126037 0  
T1:TEST-B                      2017-11-02 13:57:42.126067 0  
T1:TEST-C                      2017-11-02 13:57:42.126055 0  
T1:TEST-D                      2017-11-02 13:57:42.126082 0  

So far so good.  I then use caput to change one the values, but
camonitor outputs something for all channels it's monitoring, even the
ones that haven't changed:

T1:TEST-A                      2017-11-02 13:57:50.067417 1  
T1:TEST-C                      2017-11-02 13:57:42.126055 0  
T1:TEST-B                      2017-11-02 13:57:42.126067 0  
T1:TEST-D                      2017-11-02 13:57:42.126082 0  

Note that this here is specifically what I see as the problem: camonitor
is reporting changes on channels that have no changes.  This is
different behavior than I was seeing in 3.14.

If I think do another put, I only see the one channel change:

T1:TEST-A                      2017-11-02 13:57:55.484140 2 

If I kill camonitor and reconnect things seem to work as expected:

$ camonitor T1:TEST-{A,B,C,D}
T1:TEST-A                      2017-11-02 14:06:30.586715 2  
T1:TEST-B                      2017-11-02 14:02:11.625264 0  
T1:TEST-C                      2017-11-02 14:02:11.625251 0  
T1:TEST-D                      2017-11-02 14:02:11.625278 0  

When I do a put only the one channel changes:

T1:TEST-A                      2017-11-02 14:06:47.025503 3  

I don't see this behavior with the pyepics epics.camonitor function.
That would seem to point to it being an issue with camonitor cli.
However the fact that things behave as expected on subsequent
connections makes me think it might be pcaspy startup issue.

Any ideas?

jamie.

Attachment: signature.asc
Description: PGP signature


Replies:
Re: issue with either camonitor or pcaspy in 3.15? Wang Xiaoqiang

Navigate by Date:
Prev: Re: concurrent put callbacks Pearson, Matthew R.
Next: RE: concurrent put callbacks Andrew C. Starritt
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
Navigate by Thread:
Prev: RE: concurrent put callbacks Andrew C. Starritt
Next: Re: issue with either camonitor or pcaspy in 3.15? Wang Xiaoqiang
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
ANJ, 03 Nov 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·