Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

Agilent U2300 series

I don't know what you did but the images are not there. The properties show that they are on your c driver and obviously no one has access.

 

I'm confused as to what drivers you actually have installed. What 'IVI' did you download from Agilent? What software from NI did you install? If you actually installed drivers/utility programs from both NI and Agilent, why? Since you are using LabVIEW, there should have been nothing from Agilent that you needed except the USB driver. Certainly nothing related to IVI since you are using the plug and play driver. Maybe if you deleted everything and installed just what you need, you would have better luck.

Message 11 of 14
(2,059 Views)

Hello Marti,

      I have a new KnowledgeBase article for you to take a look at: Instrument Driver Troubleshooting Guide.  Please go through it and see if it helps.

 

Also, based on your testing, how can the instrument driver be modified so that it avoids placing the instrument in the unresponsive state?

 

Cheers,

 

NathanT

Message 12 of 14
(2,040 Views)

 

Hello again,

 

Sorry for the mess with the pictures. I just did copy/paste from a Word file and realized the mess to late to edit.  

I finally found a solution to my problem following Dennis' advice.  

 

 Concerning the drivers, I followed this FAQ from Agilent,

http://www.home.agilent.com/agilent/faqDetail.jspx?cc=US&lc=eng&ckey=1123468&nid=-11143.0.00&id=1123...

 

so I assumed the Agilent IVI-COM driver was necessary. Actually, in my opinion, it is stated quite clearly in the driver readme file...

As it seemed to be a critical item I tried with different driver versions to solve the problem, without success. 

 

Now, following Dennis' advice, I've tried to remove all Agilent Software installed and then reinstall just the lower-level driver, 

http://www.home.agilent.com/agilent/redirector.jspx?action=doc&lc=eng&cc=US&id=893513&ltype=External...

 

It has been the solution to my problem. Thank you very much, I actually didn't think it would work, finally I can start developing the little test VI.

 

Concerning NathanT question I'm afraid I have no answer. I just descrived my error case.

 

 

Martí,

 

0 Kudos
Message 13 of 14
(2,032 Views)

Hello Marti,

      I am happy to hear that you are sucessfully communicating with the instrument now.

 

Cheers,

 

NathanT

0 Kudos
Message 14 of 14
(2,003 Views)