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 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 <2014> 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024
<== Date ==>		<== Thread ==>

Subject:	RE: getAddress method behaviour
From:	"Heesterman, Peter J" <[email protected]>
To:	"'Mark Rivers'" <[email protected]>
Cc:	"EPICS Tech-Talk \([email protected]\)" <[email protected]>
Date:	Tue, 23 Dec 2014 10:04:21 +0000

Hi Mark,

I attach 2 reports.

(FYI, I am working with 2 separate IOC apps. 
The second being a TCP server that is intended to simulate the I/O behaviour of the pump(s).
I don't currently have access to the 'real' hardware.)

Cheers,

Peter.

-----Original Message-----
From: Mark Rivers [mailto:[email protected]] 
Sent: 23 December 2014 02:43
To: Heesterman, Peter J
Cc: EPICS Tech-Talk ([email protected])
Subject: RE: getAddress method behaviour

What does the following show?

asynReport 10 YOUR_PORT_NAME


Mark

________________________________________
From: Heesterman, Peter J [[email protected]]
Sent: Monday, December 22, 2014 9:23 AM
To: Mark Rivers
Cc: EPICS Tech-Talk ([email protected])
Subject: RE: getAddress method behaviour

Hi Mark,

I am passing the former.

BTW, I have configured the IOC with ASYN_MULTIDEVICE, and maxAddr 5.

Cheers,

Peter.

-----Original Message-----
From: Mark Rivers [mailto:[email protected]]
Sent: 22 December 2014 15:21
To: Heesterman, Peter J
Cc: EPICS Tech-Talk ([email protected])
Subject: Re: getAddress method behaviour

I suspect you are passing the wrong pasynUser to getAddres(). Are you passing the one that was passed into writeInt32 or the pasynUserSelf? You should pass the former.

Mark

Sent from my iPhone

On Dec 22, 2014, at 9:12 AM, Heesterman, Peter J <[email protected]<mailto:[email protected]>> wrote:

Hi Mark,

I’m sorry to trouble you.

In my application I am seeking to connect multiple devices (i.e. multiple pumps, in this case).

So, for example, I have record names like:
TURBOSIM:5:WarningTemperature (5 being the last of 5 devices connected).

I had expected asynPortDriver::getAddress to emit the index of the device being addressed (0..4, in this example).

But the only address value I can detect being emitted from the method, is 0 (e.g. when called within readInt32).
I believe it is being invoked with asynUser(s) that are correctly associated with a specific device.

What could I be missing?

Many thanks,

Peter.

TURBOSIM multiDevice:Yes canBlock:Yes autoConnect:Yes
    enabled:Yes connected:Yes numberConnects 1
    nDevices 1 nQueued 0 blocked:No
    asynManagerLock:No synchronousLock:No
    exceptionActive:No exceptionUsers 0 exceptionNotifys 0
    traceMask:0x1 traceIOMask:0x0 traceInfoMask:0x1
    interposeInterfaceList
        asynOctet pinterface 0F43E4C8 drvPvt 007F2E08
    interfaceList
        asynCommon pinterface 0F43D380 drvPvt 007EFAC8
        asynDrvUser pinterface 0F43D468 drvPvt 007EFAC8
        asynOctet pinterface 0F43D3CC drvPvt 007EFAC8
        asynInt32 pinterface 0F43D38C drvPvt 007EFAC8
        asynFloat64 pinterface 0F43D3BC drvPvt 007EFAC8
    addr 0 autoConnect Yes enabled Yes connected Yes exceptionActive No
        exceptionActive No exceptionUsers 0 exceptionNotifys 0
        blocked No
        traceMask:0x1 traceIOMask:0x0 traceInfoMask:0x1
Port: TURBOSIM
  Timestamp: <undefined>
  Input EOS[0]: 
  Output EOS[0]: 
Parameter list 0
Number of parameters is: 10
Parameter 0 type=asynInt32, name=RUNNING, value=1, status=0
Parameter 1 type=asynInt32, name=RESET, value=0, status=0
Parameter 2 type=asynInt32, name=FAULT, value=0, status=0
Parameter 3 type=asynInt32, name=WARNINGTEMPERATURE, value=0, status=0
Parameter 4 type=asynInt32, name=WARNINGHIGHLOAD, value=0, status=0
Parameter 5 type=asynInt32, name=STATORFREQUENCY, value=500, status=0
Parameter 6 type=asynInt32, name=CONVERTERTEMPERATURE, value=50, status=0
Parameter 7 type=asynFloat64, name=MOTORCURRENT, value=10.000000, status=0
Parameter 8 type=asynInt32, name=PUMPTEMPERATURE, value=40, status=0
Parameter 9 type=asynFloat64, name=CIRCUITVOLTAGE, value=30.000000, status=0
Parameter list 1
Number of parameters is: 10
Parameter 0 type=asynInt32, name=RUNNING, value=1, status=0
Parameter 1 type=asynInt32, name=RESET, value=0, status=0
Parameter 2 type=asynInt32, name=FAULT, value=0, status=0
Parameter 3 type=asynInt32, name=WARNINGTEMPERATURE, value=0, status=0
Parameter 4 type=asynInt32, name=WARNINGHIGHLOAD, value=0, status=0
Parameter 5 type=asynInt32, name=STATORFREQUENCY, value=500, status=0
Parameter 6 type=asynInt32, name=CONVERTERTEMPERATURE, value=50, status=0
Parameter 7 type=asynFloat64, name=MOTORCURRENT, value=10.000000, status=0
Parameter 8 type=asynInt32, name=PUMPTEMPERATURE, value=40, status=0
Parameter 9 type=asynFloat64, name=CIRCUITVOLTAGE, value=30.000000, status=0
Parameter list 2
Number of parameters is: 10
Parameter 0 type=asynInt32, name=RUNNING, value=1, status=0
Parameter 1 type=asynInt32, name=RESET, value=0, status=0
Parameter 2 type=asynInt32, name=FAULT, value=0, status=0
Parameter 3 type=asynInt32, name=WARNINGTEMPERATURE, value=0, status=0
Parameter 4 type=asynInt32, name=WARNINGHIGHLOAD, value=0, status=0
Parameter 5 type=asynInt32, name=STATORFREQUENCY, value=500, status=0
Parameter 6 type=asynInt32, name=CONVERTERTEMPERATURE, value=50, status=0
Parameter 7 type=asynFloat64, name=MOTORCURRENT, value=10.000000, status=0
Parameter 8 type=asynInt32, name=PUMPTEMPERATURE, value=40, status=0
Parameter 9 type=asynFloat64, name=CIRCUITVOLTAGE, value=30.000000, status=0
Parameter list 3
Number of parameters is: 10
Parameter 0 type=asynInt32, name=RUNNING, value=1, status=0
Parameter 1 type=asynInt32, name=RESET, value=0, status=0
Parameter 2 type=asynInt32, name=FAULT, value=0, status=0
Parameter 3 type=asynInt32, name=WARNINGTEMPERATURE, value=0, status=0
Parameter 4 type=asynInt32, name=WARNINGHIGHLOAD, value=0, status=0
Parameter 5 type=asynInt32, name=STATORFREQUENCY, value=500, status=0
Parameter 6 type=asynInt32, name=CONVERTERTEMPERATURE, value=50, status=0
Parameter 7 type=asynFloat64, name=MOTORCURRENT, value=10.000000, status=0
Parameter 8 type=asynInt32, name=PUMPTEMPERATURE, value=40, status=0
Parameter 9 type=asynFloat64, name=CIRCUITVOLTAGE, value=30.000000, status=0
Parameter list 4
Number of parameters is: 10
Parameter 0 type=asynInt32, name=RUNNING, value=1, status=0
Parameter 1 type=asynInt32, name=RESET, value=0, status=0
Parameter 2 type=asynInt32, name=FAULT, value=0, status=0
Parameter 3 type=asynInt32, name=WARNINGTEMPERATURE, value=0, status=0
Parameter 4 type=asynInt32, name=WARNINGHIGHLOAD, value=0, status=0
Parameter 5 type=asynInt32, name=STATORFREQUENCY, value=500, status=0
Parameter 6 type=asynInt32, name=CONVERTERTEMPERATURE, value=50, status=0
Parameter 7 type=asynFloat64, name=MOTORCURRENT, value=10.000000, status=0
Parameter 8 type=asynInt32, name=PUMPTEMPERATURE, value=40, status=0
Parameter 9 type=asynFloat64, name=CIRCUITVOLTAGE, value=30.000000, status=0
    int32 callback client address=0F3E3510, addr=0, reason=0, userPvt=03685320
    int32 callback client address=0F3E3510, addr=0, reason=0, userPvt=03687890
    int32 callback client address=0F3E3510, addr=0, reason=0, userPvt=03689E08
    int32 callback client address=0F3E3510, addr=0, reason=0, userPvt=0368C378
    int32 callback client address=0F3E3510, addr=0, reason=0, userPvt=0368EEA8
    int32 callback client address=0F3E2440, addr=0, reason=1, userPvt=0369D768
    int32 callback client address=0F3E2440, addr=0, reason=1, userPvt=0369DED8
    int32 callback client address=0F3E2440, addr=0, reason=1, userPvt=0369E7E0
    int32 callback client address=0F3E2440, addr=0, reason=1, userPvt=0369F0E8
    int32 callback client address=0F3E2440, addr=0, reason=1, userPvt=0369F9F0

TURBO multiDevice:Yes canBlock:No autoConnect:Yes
    enabled:Yes connected:Yes numberConnects 1
    nDevices 1 nQueued 0 blocked:No
    asynManagerLock:No synchronousLock:No
    exceptionActive:No exceptionUsers 0 exceptionNotifys 0
    traceMask:0x1 traceIOMask:0x0 traceInfoMask:0x1
    interposeInterfaceList
        asynOctet pinterface 0F43E4C8 drvPvt 023F0ED8
    interfaceList
        asynCommon pinterface 0F43D380 drvPvt 023EFAF8
        asynDrvUser pinterface 0F43D468 drvPvt 023EFAF8
        asynOctet pinterface 0F43D3CC drvPvt 023EFAF8
        asynInt32 pinterface 0F43D38C drvPvt 023EFAF8
        asynFloat64 pinterface 0F43D3BC drvPvt 023EFAF8
    addr 0 autoConnect Yes enabled Yes connected Yes exceptionActive No
        exceptionActive No exceptionUsers 0 exceptionNotifys 0
        blocked No
        traceMask:0x1 traceIOMask:0x0 traceInfoMask:0x1
Port: TURBO
  Timestamp: <undefined>
  Input EOS[0]: 
  Output EOS[0]: 
Parameter list 0
Number of parameters is: 10
Parameter 0 type=asynInt32, name=RUNNING, value=1, status=0
Parameter 1 type=asynInt32, name=RESET, value=0, status=0
Parameter 2 type=asynInt32, name=FAULT, value=0, status=0
Parameter 3 type=asynInt32, name=WARNINGTEMPERATURE, value=0, status=0
Parameter 4 type=asynInt32, name=WARNINGHIGHLOAD, value=0, status=0
Parameter 5 type=asynInt32, name=STATORFREQUENCY, value=500, status=0
Parameter 6 type=asynInt32, name=CONVERTERTEMPERATURE, value=50, status=0
Parameter 7 type=asynFloat64, name=MOTORCURRENT, value=10.000000, status=0
Parameter 8 type=asynInt32, name=PUMPTEMPERATURE, value=40, status=0
Parameter 9 type=asynFloat64, name=CIRCUITVOLTAGE, value=30.000000, status=0
Parameter list 1
Number of parameters is: 10
Parameter 0 type=asynInt32, name=RUNNING, value=1, status=0
Parameter 1 type=asynInt32, name=RESET, value=0, status=0
Parameter 2 type=asynInt32, name=FAULT, value=0, status=0
Parameter 3 type=asynInt32, name=WARNINGTEMPERATURE, value=0, status=0
Parameter 4 type=asynInt32, name=WARNINGHIGHLOAD, value=0, status=0
Parameter 5 type=asynInt32, name=STATORFREQUENCY, value=500, status=0
Parameter 6 type=asynInt32, name=CONVERTERTEMPERATURE, value=50, status=0
Parameter 7 type=asynFloat64, name=MOTORCURRENT, value=10.000000, status=0
Parameter 8 type=asynInt32, name=PUMPTEMPERATURE, value=40, status=0
Parameter 9 type=asynFloat64, name=CIRCUITVOLTAGE, value=30.000000, status=0
Parameter list 2
Number of parameters is: 10
Parameter 0 type=asynInt32, name=RUNNING, value=1, status=0
Parameter 1 type=asynInt32, name=RESET, value=0, status=0
Parameter 2 type=asynInt32, name=FAULT, value=0, status=0
Parameter 3 type=asynInt32, name=WARNINGTEMPERATURE, value=0, status=0
Parameter 4 type=asynInt32, name=WARNINGHIGHLOAD, value=0, status=0
Parameter 5 type=asynInt32, name=STATORFREQUENCY, value=500, status=0
Parameter 6 type=asynInt32, name=CONVERTERTEMPERATURE, value=50, status=0
Parameter 7 type=asynFloat64, name=MOTORCURRENT, value=10.000000, status=0
Parameter 8 type=asynInt32, name=PUMPTEMPERATURE, value=40, status=0
Parameter 9 type=asynFloat64, name=CIRCUITVOLTAGE, value=30.000000, status=0
Parameter list 3
Number of parameters is: 10
Parameter 0 type=asynInt32, name=RUNNING, value=1, status=0
Parameter 1 type=asynInt32, name=RESET, value=0, status=0
Parameter 2 type=asynInt32, name=FAULT, value=0, status=0
Parameter 3 type=asynInt32, name=WARNINGTEMPERATURE, value=0, status=0
Parameter 4 type=asynInt32, name=WARNINGHIGHLOAD, value=0, status=0
Parameter 5 type=asynInt32, name=STATORFREQUENCY, value=500, status=0
Parameter 6 type=asynInt32, name=CONVERTERTEMPERATURE, value=50, status=0
Parameter 7 type=asynFloat64, name=MOTORCURRENT, value=10.000000, status=0
Parameter 8 type=asynInt32, name=PUMPTEMPERATURE, value=40, status=0
Parameter 9 type=asynFloat64, name=CIRCUITVOLTAGE, value=30.000000, status=0
Parameter list 4
Number of parameters is: 10
Parameter 0 type=asynInt32, name=RUNNING, value=1, status=0
Parameter 1 type=asynInt32, name=RESET, value=0, status=0
Parameter 2 type=asynInt32, name=FAULT, value=0, status=0
Parameter 3 type=asynInt32, name=WARNINGTEMPERATURE, value=0, status=0
Parameter 4 type=asynInt32, name=WARNINGHIGHLOAD, value=0, status=0
Parameter 5 type=asynInt32, name=STATORFREQUENCY, value=500, status=0
Parameter 6 type=asynInt32, name=CONVERTERTEMPERATURE, value=50, status=0
Parameter 7 type=asynFloat64, name=MOTORCURRENT, value=10.000000, status=0
Parameter 8 type=asynInt32, name=PUMPTEMPERATURE, value=40, status=0
Parameter 9 type=asynFloat64, name=CIRCUITVOLTAGE, value=30.000000, status=0
    int32 callback client address=0F3E3510, addr=0, reason=0, userPvt=03735B98
    int32 callback client address=0F3E3510, addr=0, reason=0, userPvt=03737410
    int32 callback client address=0F3E3510, addr=0, reason=0, userPvt=037386C0
    int32 callback client address=0F3E3510, addr=0, reason=0, userPvt=03739970
    int32 callback client address=0F3E3510, addr=0, reason=0, userPvt=0373AC20
    int32 callback client address=0F3E2440, addr=0, reason=4, userPvt=0373BE30
    int32 callback client address=0F3E2440, addr=0, reason=3, userPvt=0373C740
    int32 callback client address=0F3E2440, addr=0, reason=4, userPvt=0373D958
    int32 callback client address=0F3E2440, addr=0, reason=3, userPvt=0373E268
    int32 callback client address=0F3E2440, addr=0, reason=4, userPvt=0373F480
    int32 callback client address=0F3E2440, addr=0, reason=3, userPvt=0373FD90
    int32 callback client address=0F3E2440, addr=0, reason=4, userPvt=03741568
    int32 callback client address=0F3E2440, addr=0, reason=3, userPvt=03741E78
    int32 callback client address=0F3E2440, addr=0, reason=4, userPvt=03743090
    int32 callback client address=0F3E2440, addr=0, reason=3, userPvt=037439A0
    int32 callback client address=0F3E2440, addr=0, reason=6, userPvt=03744AF0
    int32 callback client address=0F3E2440, addr=0, reason=8, userPvt=03745C48
    int32 callback client address=0F3E2440, addr=0, reason=5, userPvt=03746558
    int32 callback client address=0F3E2440, addr=0, reason=6, userPvt=037476A8
    int32 callback client address=0F3E2440, addr=0, reason=8, userPvt=03748800
    int32 callback client address=0F3E2440, addr=0, reason=5, userPvt=03749110
    int32 callback client address=0F3E2440, addr=0, reason=6, userPvt=0374A820
    int32 callback client address=0F3E2440, addr=0, reason=8, userPvt=0374B978
    int32 callback client address=0F3E2440, addr=0, reason=5, userPvt=0374C288
    int32 callback client address=0F3E2440, addr=0, reason=6, userPvt=0374D3D8
    int32 callback client address=0F3E2440, addr=0, reason=8, userPvt=0374E530
    int32 callback client address=0F3E2440, addr=0, reason=5, userPvt=0374EE40
    int32 callback client address=0F3E2440, addr=0, reason=6, userPvt=0374FF90
    int32 callback client address=0F3E2440, addr=0, reason=8, userPvt=037510E8
    int32 callback client address=0F3E2440, addr=0, reason=5, userPvt=037519F8
    float64 callback client address=0F3DBF00, addr=0, reason=9, userPvt=037442B0
    float64 callback client address=0F3DBF00, addr=0, reason=7, userPvt=03745408
    float64 callback client address=0F3DBF00, addr=0, reason=9, userPvt=03746E68
    float64 callback client address=0F3DBF00, addr=0, reason=7, userPvt=03747FC0
    float64 callback client address=0F3DBF00, addr=0, reason=9, userPvt=03749FE0
    float64 callback client address=0F3DBF00, addr=0, reason=7, userPvt=0374B138
    float64 callback client address=0F3DBF00, addr=0, reason=9, userPvt=0374CB98
    float64 callback client address=0F3DBF00, addr=0, reason=7, userPvt=0374DCF0
    float64 callback client address=0F3DBF00, addr=0, reason=9, userPvt=0374F750
    float64 callback client address=0F3DBF00, addr=0, reason=7, userPvt=037508A8

Replies:: Re: getAddress method behaviour Pearson, Matthew R.; RE: getAddress method behaviour Mark Rivers

References:: getAddress method behaviour Heesterman, Peter J; Re: getAddress method behaviour Mark Rivers; RE: getAddress method behaviour Heesterman, Peter J; RE: getAddress method behaviour Mark Rivers

Navigate by Date:: Prev: RE: getAddress method behaviour Mark Rivers; Next: Bug in 3.14 and 3.15: "*.FLNK is a Channel Access Link ..." Dirk Zimoch; 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: getAddress method behaviour Mark Rivers; Next: Re: getAddress method behaviour Pearson, Matthew R.; 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

ANJ, 17 Dec 2015

· Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System