Keysight N6701A Insufficient Location Information

[Will_S.]

Are you referring to the Display > Wake on I/O? I will try playing around with it more but my understanding was that simply turned on the display when the device received a command.

Will let you know. Thanks,

[Will_S.]

I spoke with two Keysight applications engineers, neither of which was very helpful, or easy to work with.  Regardless, they did at least confirm that the Wake on I/O setting is simply for the screen saver. 

To be honest I am becoming more suspicious of the network card configuration than the hardware itself. If anyone has ever seen intermittent network connectivity I'd be interested in hearing what they did to fix it. I'm using a secondary network card, directly connected to the power supplies. Steps I will take moving forward when I next have access to the system:

http://www.sevenforums.com/hardware-devices/304958-realtek-pcie-gbe-family-controller-keeps-disconne...

http://www.sevenforums.com/network-sharing/363165-lan-keeps-disconnecting-connecting-constantly.html

The odd thing is that using the ports never throws an error, I simply can't get the power supplies to communicate after a couple minutes of no use.

[Will_S.]

In the end, this was in fact a networking issue. Windows (or the driver) would only look at the primary ethernet port when attempting to locate the VISA Resource, and therefore only find one. By repeatedly calling VISA Open, it would eventually find the resource. By bridging the 4 network adapters the system treats them as one and I can open a reference to my various power supplies on the network on the first try. 

Briding the network is done in the Network and Sharing control panel by selecting the desired network adapters, right-clicking and choose Bridge.

Hope that helps someone.

[nyc_(is_out_of_here)]

---

@Will_S. wrote:

In the end, this was in fact a networking issue. Windows (or the driver) would only look at the primary ethernet port when attempting to locate the VISA Resource, and therefore only find one. By repeatedly calling VISA Open, it would eventually find the resource. By bridging the 4 network adapters the system treats them as one and I can open a reference to my various power supplies on the network on the first try. 

Briding the network is done in the Network and Sharing control panel by selecting the desired network adapters, right-clicking and choose Bridge.

Hope that helps someone.

---

Four network adapters?!?!

We had four test equipment along with the DUT and they were plugged into one 5-port D-link switch. The PC itself had one network adapter.

[Will_S.]

I didn't design that part, got to work with what I'm given 🙂

[nyc_(is_out_of_here)]

---

@Will_S. wrote:

I didn't design that part, got to work with what I'm given 🙂

---

And the fact that they were using FOUR network adapters is highly unusual and should have been mentioned in your first post.

[Will_S.]

You're right - I should have mentioned the 4 network adapters. But I wouldn't say it's unusual. In my area industrial PCs frequently come with multiple network adapters. Just haven't encountered this issue before.

[nyc_(is_out_of_here)]

---

@Will_S. wrote:

You're right - I should have mentioned the 4 network adapters. But I wouldn't say it's unusual. In my area industrial PCs frequently come with multiple network adapters. Just haven't encountered this issue before.

---

I haven't seen it at companies I have worked at. Generally they buy a business-grade PC such as Dell Optiplex or Precision with one network card and then use a Ethernet switch to connect to various instruments. Cheaper.

[crossrulz]

Most of my test systems have 2 ethernet ports: one for instruments (rack network, using a switch) and a second for a system network (many test systems on a local network using a router for central storage, SVN repository, etc).  But an ethernet port on the computer for each instrument is next to useless.

[nyc_(is_out_of_here)]

---

@crossrulz wrote:

Most of my test systems have 2 ethernet ports: one for instruments (rack network, using a switch) and a second for a system network (many test systems on a local network using a router for central storage, SVN repository, etc).  But an ethernet port on the computer for each instrument is next to useless.

---

Ah you are right. 1 ethernet port for the instruments and 1 ethernet port for the connection to the corporate network.

Though when working in an secured area, the test PC would not be connected to the corporate network. Not allowed.