Experimental Physics and
Industrial Control System

"Mark Rivers" <[email protected]> · Sat, 26 Mar 2011 18:28:09 -0500

Hi Robert,

I don't know much about VXI-11.  Does the E5810 handle Universal Device Clear or Selected Device Clear in the same way as a local GPIB controller?

Mark

________________________________

From: Robert Emery [mailto:[email protected]]
Sent: Sat 3/26/2011 1:42 AM
To: Mark Rivers
Cc: [email protected]
Subject: Re: GPIB DCL

Thanks for the reply Mark.

Restarting the IOC does not fix the problem.  I have to power cycle the
power supply.

I tried "Selected Device Clear" via the asynRecord ACMD field.  This had
no effect and did not write anything out through the ethernet port. 
asynTrace produced:

epics>  2011/03/25 23:30:03.964 ISMGateway addr 1 queueRequest priority 0
not lockHolder
2011/03/25 23:30:03.964 ISMGateway schedule queueRequest timeout
2011/03/25 23:30:03.964 ISMGateway callback
2011/03/25 23:30:03.964 ISM:Get: asynCallbackProcess, state=3
2011/03/25 23:30:03.964 ISMGateway 1 vxiAddressedCmd b791d30a
2011/03/25 23:30:03.964 ISMGateway 1 vxiAddressedCmd
2011/03/25 23:30:06.115 ISMGateway addr 1 vxiAddressedCmd requested 6
but sent -1 bytes
2011/03/25 23:30:10.468 ISM:Get: Error in GPIB Addressed Command write,
ISMGateway 1 vxiAddressedCmd requested 6 but sent -1 bytes

2011/03/25 23:30:10.468 ISMGateway addr 1 queueRequest priority 0 not
lockHolder
2011/03/25 23:30:10.468 ISMGateway schedule queueRequest timeout
2011/03/25 23:30:10.468 ISMGateway callback
2011/03/25 23:30:10.468 ISM:Get: asynCallbackProcess, state=3
2011/03/25 23:30:10.468 ISM:Get flush
2011/03/25 23:30:10.468 ISMGateway 1 vxiWrite numchars 5
2011/03/25 23:30:11.616 ISMGateway vxiIfc
2011/03/25 23:30:11.618 ISM:Get: nwrite=5, status=1, nawt=0
2011/03/25 23:30:12.764 ISMGateway vxiIfc
2011/03/25 23:30:12.766 ISM:Get: inlen=0, nbytesTransfered=0,
ntranslate=0

I also tried "Clear Device" via the asynRecord UCMD field with similar
results.

epics>  2011/03/25 22:55:08.317 ISMGateway addr 1 queueRequest priority 0
not lockHolder
2011/03/25 22:55:08.317 ISMGateway schedule queueRequest timeout
2011/03/25 22:55:08.317 ISMGateway callback
2011/03/25 22:55:08.317 ISM:Get: asynCallbackProcess, state=3
2011/03/25 22:55:08.317 ISMGateway vxiUniversalCmd 14
2011/03/25 22:55:10.415 ISM:Get: GPIB Universal command ISMGateway
vxiUniversalCmd failed

2011/03/25 22:55:10.416 ISMGateway addr 1 queueRequest priority 0 not
lockHolder
2011/03/25 22:55:10.416 ISMGateway schedule queueRequest timeout
2011/03/25 22:55:10.416 ISMGateway callback
2011/03/25 22:55:10.416 ISM:Get: asynCallbackProcess, state=3
2011/03/25 22:55:10.416 ISM:Get flush
2011/03/25 22:55:10.416 ISMGateway 1 vxiWrite numchars 5
2011/03/25 22:55:11.568 ISMGateway vxiIfc
2011/03/25 22:55:11.572 ISM:Get: nwrite=5, status=1, nawt=0
2011/03/25 22:55:12.768 ISMGateway vxiIfc
2011/03/25 22:55:12.770 ISM:Get: inlen=0, nbytesTransfered=0,
ntranslate=0

On 3/25/11 9:52 PM, Mark Rivers wrote:
> If you open the asynGPIBSetup.adl screen from asynRecord.adl you can issue a Device Clear.  You can see if that clears the problem.
>
> Does restarting the EPICS IOC fix the problem, or do you have to power-cycle the power supply?
>
> Mark
>
>
> ________________________________
>
> From: [email protected] on behalf of Robert Emery
> Sent: Fri 3/25/2011 11:36 PM
> To: [email protected]
> Subject: GPIB DCL
>
>
>
> I am using EPICS 3.14.12, ASYN 4.15 to control a Kikusui power supply
> via an Agilent E5810.  After I use an ASYN record to send a request to
> the power supply with bad syntax, the power supply will not reply to any
> further requests until I have cycled the power on the supply.  When I
> try to repeat this situation without EPICS, using only the web interface
> of the E5810 to send GPIB requests, the power supply will respond to
> requests after it has received one with bad syntax.  I do not know how
> the E5810 is getting around the problem.  I tried setting the ifc
> (interface clear) flag in the vxi11Configure command.  Using the
> asynSetTraceMask I can see that the ifc command is issued after sending
> a GPIB request with bad syntax, and on the scope I can see the IFC line
> go low, but this does not solve the problem.  I wanted to try sending a
> dcl (clear device) command.  Is there an easy way to do this with ASYN?
> I saw a reference to a command IBDCL in asynGPIB, but I'm not sure how
> to access this.
>
> Thanks,
>
> Rob Emery
> UW Medical Center
>
>
>

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System