Quantcast
Channel: Instrument Control (GPIB, Serial, VISA, IVI) topics
Viewing all articles
Browse latest Browse all 5565

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

$
0
0

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?


Viewing all articles
Browse latest Browse all 5565

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>