10-18-2017 09:41 AM
Using LV2013, and two cDAQ-9172 chassis, my system has worked OK for years.
I need to move a program that uses those cDAQs to LV2017.
I have a VM with LV2017 on it.
At first it didn't work, no cDAQ found. When I told the VM to connect the devices to the VM instead of the host, I got "USB Firmware Updater" that showed up instead of the devices.
There's nothing I can do with this alleged device - no settings, nothing. The real devices show up as missing.
I quit VMWare, reboot the whole machine, and now the original setup is gorched as well.
No settings:
The real device turns up missing:
Windows shows the device as an "updater". But the driver date is 2013.
This post links to a "solution", but the link to NI is bad.
Any ideas?
Blog for (mostly LabVIEW) programmers: Tips And Tricks
Solved! Go to Solution.
10-18-2017 11:18 AM
Here is a working link to the page. Maybe that will help? Looks like it's a services issue, maybe.
10-18-2017 12:20 PM
Well, the NI DEVICE LOADER was started and set to AUTOMATIC.
Stopping it and starting again had no effect.
Blog for (mostly LabVIEW) programmers: Tips And Tricks
10-18-2017 12:55 PM
You can maybe update your USB host controller on both your VM and your real PC? Maybe tell the VM to connect the host controller to it directly if that's an option?
If it doesn't help, it could be that whatever virtual USB controller the VM uses suffers from the same issue that assorted host controllers suffer from.
10-18-2017 01:28 PM
Well for the moment, let's leave the VM out of it, since the host PC now has the problem as well.
I don't follow those instructions: "Look for the controller that your device is plugged into".
Here's my list of controllers:
How am I supposed to know which one of those my device is plugged into?
Blog for (mostly LabVIEW) programmers: Tips And Tricks
10-18-2017 01:38 PM
Switch to viewing devices by connection
10-18-2017 01:46 PM
Well, that's no help - my list looks nothing like yours:
Blog for (mostly LabVIEW) programmers: Tips And Tricks
10-18-2017 01:49 PM
Nearly all devices on your PC are going to be under "ACPI x64-based PC → Microsoft ACPI-compliant System → PCI Bus", then looking for USB hubs or controllers under that.
10-18-2017 01:56 PM - edited 10-18-2017 02:02 PM
OK, that helps, I guess. I don't know how I am supposed to know this, or why I should have to, but I did find the updaters masquerading as devices:
I just now noticed that the USB INPUT DEVICE listings are further expandable. One of them is mouse and the other is keyboard.
I don't see the cDAQ chassis.
Blog for (mostly LabVIEW) programmers: Tips And Tricks
10-18-2017 02:43 PM
It is cute that after stopping, starting the NI DEVICE LOADER service, that MAX will do this:
If those stripes mean something, I don't know what.
Blog for (mostly LabVIEW) programmers: Tips And Tricks