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: read status nin "" 0 error with
From: Mark Rivers <[email protected]>
To: "'Eric Norum'" <[email protected]>
Cc: Ana Malagon <[email protected]>, EPICS mailing list <[email protected]>
Date: Wed, 10 Dec 2014 22:18:45 +0000

> Would changing the -1 to 19 in the existing commands in the existing location work, too?

 

I would suspect not, because that device would not exist at that time.  But perhaps doing so creates the device?

 

Ana said changing -1 to 19 worked, but was that with the command before iocInit or after iocInit?

 

Mark

 

 

From: Eric Norum [mailto:[email protected]]
Sent: Wednesday, December 10, 2014 2:47 PM
To: Mark Rivers
Cc: Ana Malagon; EPICS mailing list
Subject: Re: read status nin "" 0 error with

 

Would changing the -1 to 19 in the existing commands in the existing location work, too?

 

 

On Dec 10, 2014, at 12:42 PM, Mark Rivers <[email protected]> wrote:

 

--------
WARNING: At least one of the links in the message below goes to an IP address (e.g.10.1.1.1), which could be malicious. To learn how to protect yourself, please go here: https://commons.lbl.gov/x/_591B
--------

> I’m at a loss then.  I have no idea why enabling ASYN diagnostic messages is having no effect.

 

I know why it is happening.  Ana is doing this before iocInit.

asynSetTraceMask("L0", -1, 0xFF)

The problem is that using the address of -1 on asynSetTraceMask set the trace mask of all device address that are currently connected to that asyn port.  However, at that point the GPIB device at address 19 has not yet been connected, so its asynTraceMask does not get set.

The solution is to move that line to after iocInit.  You won’t see any trace information that should happen as part of iocInit, but you will see everything after that command is issued.

We might want to change the way asynSetTraceMask($(PORT), -1, MASK) works to avoid this confusion.  Someone else ran into this a couple of weeks ago.

Mark

 

 

 

 

-- 
Eric Norum
[email protected]

 


Replies:
Re: read status nin "" 0 error with Eric Norum
References:
read status nin "" 0 error with Ana Malagon
Re: read status nin "" 0 error with Eric Norum
Re: read status nin "" 0 error with Ana Malagon
Re: read status nin "" 0 error with Eric Norum
RE: read status nin "" 0 error with Mark Rivers
Re: read status nin "" 0 error with Eric Norum

Navigate by Date:
Prev: dxp R3-4 released Mark Rivers
Next: Re: read status nin "" 0 error with Eric Norum
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: Re: read status nin "" 0 error with Eric Norum
Next: Re: read status nin "" 0 error with Eric Norum
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 ·