LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Using LabView with Agilent MSO9104A Drivers (Error -1073807346)

Making some progress.  Now I have the option for Add Network Device, with a dropdown to specify a VISA TCP/IP connection.  I still can't find or add the scope.  I tried manually adding the scope.  I tried the "Auto-detect LAN instrument"  but it didn't find the scope.  This was the error popup" 

 

Could not open a VISA session to "TCPIP0::169.254.151.68::inst0::INSTR" VISA error code 0xBFFF0011

 

Insufficient location information or the device or resorce is not present in the system.

 

Any other suggestions. 😉

0 Kudos
Message 11 of 20
(1,483 Views)

Is the scope actually on the same subnet as the directions say for the auto-detect option? Have you tried the manual entry where you specify the IP Address?

0 Kudos
Message 12 of 20
(1,477 Views)

I'm not really sure about that.  I did see that note.   I'm not an IT type so that part of this is greek.  When I type IPCONFIG, at a dos shell, I get two IP addresses:

 

10.178.76.100 for ethernet connection 2 and

169.254.71.183 (preferred), for ethernet connection 1 (I guess, it doesn't have the 1)

 

Those are the only two IP returned with IPCONFIG.

 

The IP for my instrument is: 169.254.151.68

 

Does that help?   Yes, I did try to enter a manual IP and it looks like it accepts it, but I still have the same error.  And when I "Validate" I get the error posted two posts up.  Also, just to check the function, I also entered a completely bogus IP and get exactly the same response.  So there doesn't appear to be any checking on the IP.  It just accepts whatever is entered.  Also, when I enter the correct IP, there is a yellow exclamation point, indicating a problem.  That is why I get the error on Validate.

 

I even tried to hard code the resource name, by putting "TCPIP::169.254.151.68::inst0::INSTR" as the input, instead of using the control and it gave me the same error about "insufficient location information".

 

Very strange.

0 Kudos
Message 13 of 20
(1,470 Views)

It's on a different subnet (the third number). I would suggest moving it. I typically use a dedicated subnet for my Ethernet instruments. Do you have to share the instrument?

0 Kudos
Message 14 of 20
(1,465 Views)

No, I don't have to share.  But for now, I'm just trying to get this working.  I'll worry about sharing problems later. 🙂

 

I'm not sure how to move it.  How would I go about changing the subnet, for this instrument?  I'm not connected to any router or access point.  My scope is attached directly to my PC via an ethernet cable.  I use this same type of connection when I want to connect to the DAQs.  Essentially, I just unplugged the cable from my DAQ and connected it to the scope, just for testing.

0 Kudos
Message 15 of 20
(1,462 Views)

Set the IP for the instrument to 169.254.71.xxx where xxx is not 0,255, or the same as the pc.

0 Kudos
Message 16 of 20
(1,454 Views)

Thanks, I'm trying to do that now.  The Control Panel isn't the way it used to look so I have to do a lot of searching to find the right place. 🙂

0 Kudos
Message 17 of 20
(1,452 Views)

Apparently that wasn't the problem.  I changed the IP to 169.254.71.200.  I then had it do the auto-detect and it still couldn't see it.  I manually entered the IP and got the same results, "insufficient location information".

 

Also, when I click the "Open VISA test panel" in MAX, I get the same error, "insufficient location information".

 

I wonder if it has anything to do with this type of scope.  I have old data in MAX showing another scope worked fine and was detected.  I switched scopes to a much nicer PC based scope.  Agilent MSO 9104A.   I can communitate with it just fine, using a browser.  Just can't communicate at all with labview. 

 

Also, there are two IP that come up when I use ipconfig.  One starts with 169.254.71.xxx and the other marked connection 2, is 10.178.76.xxx.  My old data for the other scope started with 10.xxx.xxx.xxx.  Just on a hunch I tried those numbers and they didn't fare any better.  This is really a bugger.

0 Kudos
Message 18 of 20
(1,450 Views)

I don't know what else could be wrong. Can you ping it?

0 Kudos
Message 19 of 20
(1,446 Views)

Yep! I can ping it at 169.254.71.200, just fine.  And I just verified I can still reach it with the web browser on my PC, via that IP.

 

This is the one thing I'm wondering about.  The interface over this ethernet.  It's a PC on both ends.  It's not like it's a PC on my labview end and a typical scope on the other end.  The Agilent is the MSO 9104A.  In the current configuration, it's running a web server to communicate with other PCs, via the ethernet.  I tried turning off the web server but it made no difference.  

 

The driver specifically says it's for this scope, so I'd presume that's all taken into consideration.

 

 I've looked around for some Setup info I might be missing on the scope.  Under Utilities there are for Remote operation:

 

GPIB Interface

USB Interface

LAN Interface

Web Interface (tested and works)

 

For the LAN interface, it has SICL Address: lan[169.254.71.200]:inst0

 

There is another setup that says, "LXI LAN Setup" but there isn't much to change there that seems relevant.

 

BTW, I appreciate you taking the time to try and help on this.

0 Kudos
Message 20 of 20
(1,443 Views)