RE: asynAddress, asynPortDriver maxAddr, and addr in setXXXParam

[Emmanuel Mayssat <emayssat@outlook.com>]

What happen when placed after the iocInit? 

It works!!!

Indeed, the asynSetTraceMask call was just before (no dbLoadXXX in between).

Now, it is just after. 

The behavior is different. 

The -1 asynAddress is now behaving as expected.

Thanks,

--

E

---

Subject: Re: asynAddress, asynPortDriver maxAddr, and addr in setXXXParam
From: eric@norum.ca
Date: Thu, 18 Apr 2013 09:41:19 -0700
CC: rivers@cars.uchicago.edu
To: emayssat@outlook.com

Note that

asynSetTraceMask "myPort",-1,0x9

will have an effect only on addresses that are registered at the time that the asynSetTraceMask is invoked.

Addresses which are registered later as the result of things like dbLoadRecords will not have their trace mask set.

What happens if you move the asynSetTraceMask to after the iocInit?

On Apr 18, 2013, at 9:28 AM, Emmanuel Mayssat <emayssat@outlook.com> wrote:

> From: rivers@cars.uchicago.edu
> If you want to print ASYN_TRACE_ERROR and ASYN_TRACEIO_DRIVER messages for a records with ANY asyn address then you do
> asynSetTraceMask "myPort",-1,0x9
> Is this what you are asking?

Yes, except that the -1 asynAddress is what I had initially... 

and that doesn't work for ANY address (but for address 0).

But setting the asynTrace flags for each asynAddress works as expected.

PS: asyn 4-12 + epics-base 3.14.11 + fedora 8 IOC

PS: I am using ASYN_MULTIDEVICE as previously recommended

FYI

--

Emmanuel

-- 
Eric Norum
eric@norum.ca