LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

problem with Agilent B2900 Series drives

Solved!
Go to solution

Hello,

 

I am new to Labview. I downloaded the  3rd party drives (Agilent B2900 Series - USB, Ethernet, IEEE 488.2 (GPIB) Driver for LabVIEW - National Instruments (n...) and tried to control my keysight B2912. My constructed VI does not work properly, and it sees because one the sub VI contained in the 3rd party drives  has some problems.

Here attached the screenshots and the sub VI.

I am looking for help from expert who can help me to figure it out.

 

Thanks a lot in advance !

 

Songtian

PrtSc.jpg

 

0 Kudos
Message 1 of 14
(446 Views)

What is the message in your output error ?

Have you checked that the Visa ressource name exists and is ok ?

0 Kudos
Message 2 of 14
(429 Views)

 

Hi Defaphe,

 

Thanks for replying.

 

I always got error out showing below:

Agilent B2900 Series.lvlib:Error Query.vi<ERR>
Instrument reports:
-113,"Undefined header"
+0,"No error"

 

The VISA resource name seems fine.

 

Thanks.

Songtian

 

 

 

 

 

0 Kudos
Message 3 of 14
(423 Views)

Track back your header.

 

found this in the forum if it helps

https://forums.ni.com/t5/LabVIEW/113-undefined-header-0-no-error/td-p/4183574

 

Have you tested the library examples ?

 

Can you please post your project or main vi to, at least, check if you do not have a race condition issue.

0 Kudos
Message 4 of 14
(416 Views)

Thanks.

 

I do tested the example and found the same problem.

What I found if I delete the sub IV named configure source, the project will run without showing error. 

 

Here, I attached my project (I-V Cheker.vi) and one the the example VI from the library.

 

 

Download All
0 Kudos
Message 5 of 14
(412 Views)

How do you define a float number ? 2.0 or 2,0 

One problem with the driver is the use of %g in their  use of format into string. 

Your device expects 2.0, make sure that you send that when sending numbers to the device.

 

How does the whole string to Visa write look like?

0 Kudos
Message 6 of 14
(401 Views)

Put a probe on the fully concatenated string in the "B2900 Configure Source.vi". Copy that string here and we should be able to pick out the error. 

 

Like previously stated, its probably a poorly formatted number.   But it could be that the newer B2912 uses slightly different SCPI commands. 

 

The driver page states its only been tested with a B2902.

 

Craig

0 Kudos
Message 7 of 14
(378 Views)

Not familiar with the format of string. I just found %g is using in other sub VI which works normally.

Here I attached the probed whole string:

 

:SOUR1:VOLT:RANG:AUTO ON;AUTO:LLIM 2.000000;RANG 2.000000;:SOUR1:VOLT 0.000000;VOLT:TRIG 0.000000;:SOUR1:FUNC DC;FUNC:MODE VOLT;TRIG:CONT ON;

 

Thanks.

0 Kudos
Message 8 of 14
(363 Views)

Hi, I am attaching the whole string here:

 

:SOUR1:VOLT:RANG:AUTO ON;AUTO:LLIM 2.000000;RANG 2.000000;:SOUR1:VOLT 0.000000;VOLT:TRIG 0.000000;:SOUR1:FUNC DC;FUNC:MODE VOLT;TRIG:CONT ON;

 

Thanks.

 

 

0 Kudos
Message 9 of 14
(362 Views)

Hi, with your kind help, I get some update on the issue.

 

I found if I delete the command of RANG, it works normal without reporting an error. The whole string becomes:

 

:SOUR1:VOLT:RANG:AUTO ON;AUTO:LLIM 2.000000;:SOUR1:VOLT 0.000000;VOLT:TRIG 0.000000;:SOUR1:FUNC DC;FUNC:MODE VOLT;TRIG:CONT ON;

 

 

Original one is: 

 

:SOUR1:VOLT:RANG:AUTO ON;AUTO:LLIM 2.000000;RANG 2.000000;:SOUR1:VOLT 0.000000;VOLT:TRIG 0.000000;:SOUR1:FUNC DC;FUNC:MODE VOLT;TRIG:CONT ON;

 

Wish to hear from you again.

 

Thanks

 

0 Kudos
Message 10 of 14
(343 Views)