LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Mystery "USB Firmware Updater"

Solved!
Go to solution

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:

cDAQ3.PNG

 

The real device turns up missing: 

cDAQ2.PNG

Windows shows the device as an "updater".  But the driver date is 2013.

cDAQ1.PNG

 

This post links to a "solution", but the link to NI is bad.

 

Any ideas?

Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

Message 1 of 25
(5,313 Views)

Here is a working link to the page.  Maybe that will help?  Looks like it's a services issue, maybe.

0 Kudos
Message 2 of 25
(5,277 Views)

Well, the NI DEVICE LOADER was started and set to AUTOMATIC.

Stopping it and starting again had no effect.

 

Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 3 of 25
(5,260 Views)

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.

0 Kudos
Message 4 of 25
(5,251 Views)

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:

USB.PNG

How am I supposed to know which one of those my device is plugged into?

 

Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 5 of 25
(5,242 Views)

Switch to viewing devices by connection

 

Devices by connection.png

 

Message 6 of 25
(5,235 Views)

Well, that's no help - my list looks nothing like yours:

USB2.PNG

Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 7 of 25
(5,228 Views)

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.

0 Kudos
Message 8 of 25
(5,224 Views)

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:

USB3.PNG

 

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.

 

Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 9 of 25
(5,217 Views)

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.

USB4.PNG

Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 10 of 25
(5,199 Views)