I recently had to replace my computer. Now when I try to connect my 34461A to the new Dell I get a beep indicating the device is present but it doesn't show up on the device manager's list. If I connect the same cable to my laptop, it works. If I connect an iPhone to the new Dell on the same usb outlet it works.
I am running BenchVue 3.5 with IO Suite 17.2, and the latest NI release.
How do I proceed to diagnose and fix the problem?
Gordon
What does the instrument look like in Device Manager? Does it show up in Connection Expert? Screenshots of both tools would be uber useful!
hognala, and Brian,
I responded via email, but some how the replies go kicked back. This is a repeat. Hope it gets thru.
Thanks for the suggestions.
I am using the DDM with USB. I also have a scope connected. I found the two devices in the Device Manager list in the "Other" category. Here are some screen shots:
I am still stuck.
Gordon
PDF 1 indicates that the IVI USB-TMC driver is not installed. This can happen especially when some other installation is "stuck" in the Windows Plug & Play system. This is not obvious to the user, unfortunately. In order to fix this, try this workaround from an Administrator command prompt:
dpinst /S /SE /SW /PATH "c:\Program Files\IVI Foundation\VISA\IVI USB Staging"
Post any error messages / screenshots if it doesn't work.
No joy in Mudville. I have attached three screenshots:
1. Device manager - the DDM doesn't currently appear at all. This has happened sometimes in the past.
2. NI VISA Wizard for one device
3. NI VISA Wizard for another device
I ran dpinst and assume it went ok.
Gordon
Awwww, but assumptions don't help anyone... Is this 64-bit Windows? if so, try this from an Administrator command prompt:
C:\Program Files\IVI Foundation\VISA\IVI USB Staging\b841aa80\Windows
Then unplug and replug the USB cable.
The 2022A is now recognized correctly, while the 34461A is identified as “Other”. However, the 2022A will not start with BenchVue.
A pdf is attached with the following pages
Please let me know if any of the above are superfluous to cut down on my work and your reading.
Thanks for sticking with me on this.
Gordon
Cool, making progress!
For the 34461A, unplug the cable, plug it back in. Then, if it still doesn't get a driver correctly, force the driver manually using the attached document.
Way big progress! After power recycling everything, the 34461A now works in BenchVue. The 2022A is stuck "waiting for a trigger..."
What next?
I'll ping w0dz and see if he can get more info on DSO-X 2022A "Waiting for acquisition to complete..."
OK, here are the questions from R&D:
1. What is the state of the scope when you launch the BV Scope app? Is it in Stopped mode, or waiting for trigger or running?
2. Can we get the log files at the point that its waiting? To do that: In BenchVue, click the Settings cog, then click Report an Issue... and send that in to us (put a comment in the defect description with your forum username, and tell them to contact hognala/Alan and it will get routed to me)
Thanks for your persistence!
I power cycled everything a couple of times and now all works. Thanks for the help.
Gordon
Is the connection via native USB or via a GPIB adapter? If there are no adapters in use, and if file IO is disabled to the DMM, there wouldn't necessarily be anything showing up in the Windows Device Manager.
A clue might be that NI IO Libs are also installed. If using a Keysight USB-GPIB adapter, you'd need to enable the Passport for Tulip in NIMAX. Also make sure that Keysight IO Libs are correctly showing up as secondary, not primary VISA. Finally, in side-by-side installations like this, often the VISA Shared Components library gets corrupted, so you might try uninstalling it and then re-installing Keysight IO Libs to fix it. A reboot wouldn't be a bad idea either.
Brian
OK, here are the questions from R&D:
1. What is the state of the scope when you launch the BV Scope app? Is it in Stopped mode, or waiting for trigger or running?
2. Can we get the log files at the point that its waiting? To do that: In BenchVue, click the Settings cog, then click Report an Issue... and send that in to us (put a comment in the defect description with your forum username, and tell them to contact hognala/Alan and it will get routed to me)
Thanks for your persistence!