Windows 10 "creating" multiple addresses for GPIB-USB instruments

[HRSmith]

Our LV programs stops working after a few days. GPIB-USB connecton to the instruments is lost. KeySight Connections shows multiple GPIB addresses for each instrument (e.g., main address is "GPIB::23::INSTR", and several sub-addresses are shown as "GPIB::23::0::INSTR", "GPIB::23::1::INSTR, "GPIB::23::2::INSTR, etc.). It appears that a unique sub-address is being created for every user that logs onto the PC, which has Windows 10 OS. This does not occur on the earlier versions of Windows OS, so it may be something new for Windows 10. However, this does not explain why the program loses connection after some time. I thought it may be because the programs are addressing a specific GPIB string (i.e. "GPIB::23::INSTR"), which may become invalid for next user that logs on (i.e., sub-address created as "GPIB::23::8::INSTR"). To test this theory, we tried assigning an alias for each main address. First, we disconnected the GPIB-USB cable, removed all of the GPIB addresses and sub-address in KeySight Connections, refreshed, and then reconnected the GPIB-USB cable. After refreshing KeySight again and waiting for the main GPIB addresses to reappear, we then assigned a unique alias to each of the main GPIB addresses, and replaced the GPIB address strings with the alias strings in the LV programs. The programs worked as usual, no problem. Next, another user logged onto the PC, and the sub-addresses were created as expected, but the alias strings did not get carried forward to the new sub-addresses (e.g., alias "blue" was assigned to main address "GPIB::23::INSTR", but it did not automatically get assigned to the sub-address "GPIB::23::8::INSTR" created by the OS). However, the programs continued to work ok. Next, we asked several other employees to log onto the PC. And, as expected, new sub-address was created for every user the logged onto the PC, and the programs continued to work ok for every user. Seems like problem solved, but I am uncertain that we actually "fixed" the underlying issue. Has anyone else seen a problem like this? Does anyone know why Windows 10 is "creating" sub-addresses for every user?

[Just_Amber]

I want to add some new details to our problem, as of this morning: We've now noticed this behavior on one of our Windows 7 machines.

We are unsure if this is an issue with LabView, our Keysight GPIB to USB talker, our Windows Machine, or what.

Additionally, all LV code that we're using is packaged as an executable. And we have not released any new executables. So absolutely nothing has changed code wise...

[Andrea.W]

Hi Just_Amber,

Thank you for detailing your issue. Are all of your devices on the same sub-address? And does this issue seem to happen only on Windows 7 machines?

This sounds like it could be related to the IP address configuration settings. Do you know if you have your devices configured with a static address or dynamic address?

Regards,

[Just_Amber]

Hi Andrea,

At first we though that the problem was just confined to Windows 10. We then noticed it on a Windows 7 machine as well

I am confused by your reference to IP address. We do chat with other equipment (a motor) using a static IP, but this is an issue with our GPIB / Visa talker.

We'll statically set the address of our equipment (and of our talker) to say... 23. The first user will have the instrument listed as "GPIB0::23::INSTR"

After multiple users log on, we'll see the list grow to something like:

"GPIB0::23::0::INSTR"

"GPIB0::23::1::INSTR"

"GPIB0::23::2::INSTR, etc...

I think the max that HRSmith and I have seen is around 24 sub-addresses. By this point, our LV executable crashes stating that it cannot connect with the hardware.

We have not seen the program[s] crash since we've labeled "GPIB::23::INSTR" as "blue" and then have the executable talk to "blue," but we would like to figure out how / why these sub-addresses are being automatically created.

[cymrieg]

Do you have Keysight Visa installed? WE saw this same issue with Visa returning GPIB secondary addresses with our instruments. I think (don't swear by it) that in Keysight Connection expert there is a way to switch of returning secondary addresses

[HRSmith]

Hi cymrieg,

Yes, we have very latest versions of both Keysight VISA and NI VISA installed, but we are using an older Agilent GPIB-USB interface (82375B). Actually, we use this same interface on several other test stations without any issues (i.e. creating secondary GPIB addresses for each user).

I thought this problem was only to do with Windows 10 since it is a more "secure" OS. I read somewhere that the system environment is separated for every app installed so that no two apps share the same files (DLL, registry, etc.). I wondered if maybe a similar arrangement applied to users, i.e. no two users allowed to share the same GPIB address. But, Amber reported having same problem on a station with Windows 7. And, we have another test station that was just recently upgraded to Windows 10, and it does not appear to suffer the same problem.

If there is switch to turn off OS from returning secondary addresses, we have been unable to find it. We've looked in KeySight Connections Expert, NI MAX, and the OS device manager. I assume the setting is probably in a windows registry somewhere, but I have no idea where to look.

Thanks!

Hugh

[Just_Amber]

The issue popped back up again 

We think something might be happening with that particular Windows 10 laptop because I now cannot get any of my LV executables to load, in addition to the crazy amount of VISA addresses.

I am in the process of trying out a completely different computer. But this problem is just ... odd...

[mkumar172]

Did we found the core issue of this problem. I am also facing similar problem. I tried to connect my device via Keysight E5810B and as soon I connect by one device to it. It shows multiple fake GPIB add. 

Any help....

Cheers!

Manohar