Re: AsynInt32 SCAN=I/O Intr response

[Eric Norum via Tech-talk <tech-talk at aps.anl.gov>]

On Feb 23, 2022, at 3:41 PM, Mark Rivers <rivers at cars.uchicago.edu> wrote:

Ø  If I run the asynReport with interest level 1, all the records show up.  Here’s the report for the ai record shown above:

 

asynReport is not reporting on records, it is reporting on asyn port driver devices.

Right.  But why do the addresses associated with the ai records show up as connected and those with the longin records show up as  not connected?  The asynInt32 code in my driver is clearly the same for both.

 

What type of driver is KD1?  It seems like something you wrote?  Perhaps your driver needs to call pasynManager->exceptionConnect() for that address to let asynManager know that it is connected?

Perhaps, but why not for the addresses associated with the ai records?

And it’s not clear to me where I’d put this call.

 

Mark

It’s a driver I wrote based on asynStandardInterfaces.h.  Only the asynInt32 interface uses callbacks.  Here’s the salient code in the Configure routine.

    /*

     * Register ASYN interfaes

     */

    pInterfaces = &pdpvt->asynInterfaces;

    pInterfaces->common.pinterface        = &commonMethods;

    pInterfaces->int32.pinterface         = &int32Methods;

    pInterfaces->octet.pinterface         = &octetMethods;

    pInterfaces->float64Array.pinterface  = &float64ArrayMethods;

    pInterfaces->int8Array.pinterface     = &int8ArrayMethods;

    pInterfaces->int32CanInterrupt        = 1;

    status = pasynStandardInterfacesBase->initialize(pdpvt->portName,

                                                     pInterfaces,

                                                     pdpvt->pasynUser, pdpvt);

— 

Eric Norum

eric at norum.ca