Error −1073807264

[dpopovich]

I am using an Agilent 82357B USB-GPIB adaptor with my LabVIEW program. I have used these combinations before with no problems. Currently I am using LabVIEW 2010 SPI 32bit with Agilent Connection IO Expert version 16.2.15823.0

*I now, after some time get a " −1073807264The interface associated with this session is not currently the controller in charge" error. I have read through all the information I can find about using the Agilent USB-GPIB adaptor and the settings to enable NI488 and software installation. So far nothing has stopped this from happening. Right now I believe that the only difference from using this before and now is the revision levels of LabVIEW and the Agilent Connection Expert. I am attaching the setup info that I have found and followed.

Anybody else experience this?

I have now purchased an NI GPIB-USB Adaptor and will try it in my setup.... of course I expect it to work, but am disappointed in "standard" interface protocols.

[Mike.F]

Hi,

Yes you are right, the difference is the revision levels of LabVIEW and the Agilent Connection Expert.

I found these two articles that explains how  you can use both National Instruments (GPIB) and Agilent/HP controllers in the same system.

1. Using HP Agilent 82357A/82357B GPIB in Measurement & Automation Explorer (MAX) or LabVIEW

2.Can I Use Both National Instruments (GPIB) and Agilent/HP (HPIB) Controllers in the Same System?

Best Regards

Miguel Fonseca

Applications Engineer

National Instruments http://www.ni.com/support

[dpopovich]

Yes, attached similar Agilent 82357B information in my post.

It now seems that the solution for my problem may be very simple. I currently believe that the power settings on the lab pc's that I was using to run a LabVIEW program that uses an Agilent 34970A DAQ simply

was going into "Standby Mode" after 15 minutes and this is where the GPIB communication was interrupted. 

I have modified the power setting to "Never" go into standby... I will see if this is actually what was happening.

*Note: Even though I think the standby of the pc is the problem. If I startup the Agilent IO Connection expert while my LabVIEW program is communicating via the GPIB to the DAQ it seems that this also interrupts the

communication with the same error. Presumably the Agilent Connection IO expert software interrupts the Labview GPIB calls.

-I will post again when I am certain of these two points.

-Thanks

David P.