Experimental Physics and
Industrial Control System

I am a little confused about the use of asynPortDriver().

I have a VMEbus system with 4 Highland arbitrary waveform generators ( 1x V346, 3 x V344).
Each of these cards holds 8 channels.

Therefore I call asynPortDriver with 4 (nCards) * 8 (NUM_CHANNELS) (= 32) addresses:

AwgPort::AwgPort(const char *portName, epicsUInt16 a, epicsUInt16 nrCards)
    :asynPortDriver(portName, nrCards * NUM_CHANNELS,// NUM_PARAMS,
            asynInt32Mask | asynInt16ArrayMask | asynInt32ArrayMask | asynFloat64Mask | asynFloat64ArrayMask | asynOctetMask | asynDrvUserMask,
            asynInt32Mask | asynInt16ArrayMask | asynInt32ArrayMask | asynFloat64Mask | asynFloat64ArrayMask,
                    ASYN_MULTIDEVICE,
                    1, // autoconnect
                    0, // prio
                    0)

"Somehow" everything looks good too.
I'm just confused that with the asynReport I always get displayed "8"  as nDevices:

tIocSh> asynReport 1,awgport
awgport multiDevice:Yes canBlock:No autoConnect:Yes
    enabled:Yes connected:Yes numberConnects 1
    nDevices 8 nQueued 0 blocked:No
    asynManagerLock:No synchronousLock:No
    exceptionActive:No exceptionUsers 1 exceptionNotifys 0
    traceMask:0x1 traceIOMask:0x0 traceInfoMask:0x1
    addr 0 autoConnect Yes enabled Yes connected Yes exceptionActive No
        exceptionActive No exceptionUsers 0 exceptionNotifys 0
        blocked No
        traceMask:0x1 traceIOMask:0x0 traceInfoMask:0x1
    addr 1 autoConnect Yes enabled Yes connected No exceptionActive No
        exceptionActive No exceptionUsers 0 exceptionNotifys 0
        blocked No
        traceMask:0x1 traceIOMask:0x0 traceInfoMask:0x1
    addr 2 autoConnect Yes enabled Yes connected No exceptionActive No
        exceptionActive No exceptionUsers 0 exceptionNotifys 0
        blocked No
        traceMask:0x1 traceIOMask:0x0 traceInfoMask:0x1
    addr 3 autoConnect Yes enabled Yes connected No exceptionActive No
        exceptionActive No exceptionUsers 0 exceptionNotifys 0
        blocked No
        traceMask:0x1 traceIOMask:0x0 traceInfoMask:0x1
    addr 4 autoConnect Yes enabled Yes connected No exceptionActive No
        exceptionActive No exceptionUsers 0 exceptionNotifys 0
        blocked No
        traceMask:0x1 traceIOMask:0x0 traceInfoMask:0x1
    addr 5 autoConnect Yes enabled Yes connected No exceptionActive No
        exceptionActive No exceptionUsers 0 exceptionNotifys 0
        blocked No
        traceMask:0x1 traceIOMask:0x0 traceInfoMask:0x1
    addr 6 autoConnect Yes enabled Yes connected No exceptionActive No
        exceptionActive No exceptionUsers 0 exceptionNotifys 0
        blocked No
        traceMask:0x1 traceIOMask:0x0 traceInfoMask:0x1
    addr 7 autoConnect Yes enabled Yes connected No exceptionActive No
        exceptionActive No exceptionUsers 0 exceptionNotifys 0
        blocked No
        traceMask:0x1 traceIOMask:0x0 traceInfoMask:0x1
Port: awgport

Danke Heinz

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Replies:

RE: asynPortDriver nDevices? Mark Rivers via Tech-talk

Navigate by Date:

Prev: vxworks boot problem whitetiger1123 via Tech-talk

Next: RE: asynPortDriver nDevices? Mark Rivers 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: Re: vxworks boot problem Mark Rivers via Tech-talk

Next: RE: asynPortDriver nDevices? Mark Rivers 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