LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

agilent 34970a and Labview 8.2.1

Hello again,
 
I probably confused you somewhat.  The LV 7.1 is running on another test setup.  In that setup, I am communicating via com 2 with no adapter to an Agilent 34970a.
 
On this new setup, I am trying to get LV 8.2.1 running,  the drivers that installed with 8.2.1 are the NI-Visa 4.1.  When opening MAX comm 1 and comm 2 both have exclamation points so there is no data and no error.  I attached the usb to serial adapter which is assigned comm 3.  Using MAX, when I execute a viWrite with *IDN?\n  I get a return count of 6 and status of 0.  Seems normal with no error.  Executing a viRead it returns Hewlett-Packard, 34970a, 0, 13-2-2\r\n return count 33 and status of 0.  Looks normal.  Then I try the advanced scan vi that downloaded with the project vi's.  If I don't put in a channel I don't get an error--the Agilent lights the rmt indicator.  If I put in any channel such as 101 I get an error which is -138
 
Thanks again for your help.
 
Everett
0 Kudos
Message 11 of 15
(2,026 Views)
I got the same error when I ran the function. Maybe because 8.2.1 runs faster (or improvements in VISA), I was able to eliminate the errors by placing a 250msec delay before the Conf Scan and Conf Trigger functions in the case statement.
0 Kudos
Message 12 of 15
(2,017 Views)
Hello and thanks for the reply,  I put a delay in the volt config case but still get the error.  My comm settings are 9600 baud, 8n1 and xon/xoff.
0 Kudos
Message 13 of 15
(2,009 Views)

Conf Scan and Conf Trigger are not in the voltage configure case.

I ran it at the default setting of 57600 instead of 9600.

Message Edited by Dennis Knutson on 05-29-2007 12:26 PM

Message 14 of 15
(2,007 Views)
Thanks everyone
 
I am up and running.  Adding the delays and taking the baud rate to 57600 allows me to configure and read 2 34901a's with most inputs used.
 
Everett
0 Kudos
Message 15 of 15
(1,992 Views)