Mystery "USB Firmware Updater"

[CoastalMaineBird]

If I use DEVICE MANAGER to disable the mystery FIRMWARE UPDATERs, then delete the real cDAQs from the MAX config, I get this:

The names show up as "present", but I can't do anything with them.

[protocoled]

At this point, I would recommend uninstalling and reinstalling our DAQmx drivers as a first step. If that doesn't help, you'll maybe want to update the drivers for all of your USB ports as well.

[JÞB]

Steve,  Open the Task Manager, 

Select the "Services" Tab Click the "Services..." Button

In the services Config set the NI Device Loader and NI Configuration Manager to "Automatic (Delayed Start)"

Don't ask me "why" I only remember What and How 

[CoastalMaineBird]

In the services Config set the NI Device Loader and NI Configuration Manager to "Automatic (Delayed Start)"

Weird that after a couple of years of working OK it would need that.

In any case, that doesn't change anything.

I did a system restore to the point before this started, and I did get back to the FIRMWARE UPDATER point.  that reverted the deletion of drivers that I did.

In case it's not obvious, I don't know squat about USB drivers.  But it's weird that an "updater", presumably a piece of software, shows up in a list of hardware.

I'm on the verge of moving to LV2017, but can't quite yet, so maybe it's time to reinstall LV2013 to fix this, and the other places it has crapped itself.

[CoastalMaineBird]

Well, repairing NIDAQ did nothing except waste an hour's time.

It still claims that where I plug in a cable, I plugged in a "Firmware updater".

Words cannot express my loathing of this crap.  The system will not tell me what's really wrong, just mystery labels where my device ought to be.

I especially love when, after repairing NIDAQmx 9.8, the NI updater service it tells me that there's an urgent patch for 9.8.0.f1.  So when I try to install that, it tells me that the patch is already installed, you silly human.

Arrrgh.

I guess I have to uninstall the whole LabVIEW suite and start over.

[CoastalMaineBird]

Found this post and followed those instructions.

I removed the cDAQ cables, and reset the MAX configuration, requiring a reboot.

i opened MAX and the DEVICE MANAGER.

Plugging in the cDAQs caused nothing, except the Windows banjo sound.

No change, except it's now invented an LPT port

It says he waited quite a while and then it magically fixed itself.   Yeah, I have a lot of confidence THAT will happen.

[CoastalMaineBird]

It turns out that the DEVICE MANAGER had a section called DATA ACQ DEVICES.  After DELETING the firmware updater from there, and then resetting the MAX config again, rebooting again, I get Windows to recognize that plugging in a cDAQ is something new.  it says it doesn't know what driver to use.

I try to tell it, but the list of available drivers on my machine includes practically everything EXCEPT the one I need.

< sigh >

[CoastalMaineBird]

So, if I delete the firmware updaters, kill the MAX config and install from a DOWNLOADED copy of NIDAQ 9.8.0, I get a new mystery device:

I've no idea what a 6009 is, but I don't think I have one.  And now the cDAQ choices in the driver list are missing altogether.   You can't get there from here.  It's just making up stuff to complain about.

[RavensFan]

According to http://www.ni.com/download/ni-daqmx-15.5/5901/en/

support for the cDAQ-9172 wasn't added until DAQmx 15.5

[JensG69]

That's wrong, support started with DAQmx 8.8:

See download page of DAQmx 8.8: http://www.ni.com/download/ni-daqmx-8.8/1085/en/

and documention of cDAQ-9172 (page 6): http://www.ni.com/pdf/manuals/371747f.pdf

--

A USB-6009 was a low cost multifunction DAQcard by NI, now replaced by the USB-6000 to 6003 cards.

Regards, Jens

Regards, Jens