Error -1074118631 after driver update "the resource name is not assigned..." PXI-6562

[Artybear]

I just updated my niHSDIO driver from version 1.5.3 to 1.7.4, and now the device, a PXI-6562 will not initialize. I get the following error. The VI hangs for 30~60s trying to initialize before the error occurs.

Code: -1074118631

Message: niHSDIO Init Generation Session.vi<ERR>The resource name is not assigned to an instrument supported by NI-HSDIO.

The device worked fine with the old driver.

The windows device manager says everything is installed and working.

I have tried writing a simple VI using new versions of the HSDIO VIs and re-creating the I/O resource pull-down.

The resource pull-down menu lists the name as "PXI1Slot2"

I can see the device in MAX with its location listed as "Chassis: 1; Slot: 2"

The PXI-6562 has 2 LEDs on the front panel for "access" an "active." Neither lights up during an attempt to initialize.

I tried uninstalling the driver in Windows, reinstalling, and rebooting: same problem.

I tried using the device in Signal Express, and it produced the same error.

I am using LabVIEW version 8.5 and Signal Express 2.5.

Does anyone know how to fix this?

Thanks,

Arthur

[DJ_L.]

Hey Arthur,

In the Device Manager, can you right click on the device and select "Update Driver...". Then if you don't get any issues doing that, can you go back into MAX, and take a screenshot of how the device is showing up under the Devices and Interfaces? Also, can you do a Reset on the device, or a Self Test on the device in MAX, and what happens when you do that? Finally, can you let us know what PXI controller (or MXI) you are using in your system? Hopefully with this information, we will be able to help you toubleshoot and eventually solve this issue. Thanks.

Regards,

DJ L.

[Artybear]

Hi DJ,

I did the "Update Driver" in the Windows manager. It said it couldn't find a better version. I get the same response if I let Windows search automatically as when I point it to the latest NIHSDIO folder 1.7.4).

The PXI controller I'm using is a PXI-8105.

I took screenshots of each of the tabs for the 6562 in MAX:

I don't see a Reset or Self-Test button in MAX. The VISA Test Panel has the following tabs:

Currently I have NI-DAQnx 9.1.7 installed. I don't know if that's related to the NI-HSDIO driver. I am currently downloading NI-DAQmx 9.2.3.

-Arthur

[Artybear]

Also, in the MAX VISA Test Panel, if I click the "Execute" button for a viGetAttribute value, neither of the device's front-panel LEDs lights up. I assume that they should, but I'm unsure.

[Artybear]

After updating NI-DAQmx, the device problem persists. But new buttons showed up in MAX for device Self-Test and Reset. Both actions produce an "Internal Error" with code -88302.

-Arthur

[Artybear]

I get the same intenal error code (-88302) from the self-test of my PXI-4461 in the same chassis. That leads me to believe that it's a problem with the controller.

Looking in the Windows device manager, the driver for the SMBus Controller had a driver version 2.0.0.49152.

[DJ_L.]

Hey Arthur,

It seems like a specific installation file that might have gotten corrupted when installing one of the two drivers you installed. So for the first issue, where you saw the devices show up differently than normal, that seems like it was fixed when you upgraded the DAQ driver, but then that might have caused another file to get corrupted. I am looking into this to see what you should do to clean it all up.

In the meantime, can you try doing a Repair of the HSDIO driver. Go into Add or Remove Programs and then find the NI drivers, and do a Repair on the driver. I am looking into whether or not you will have to do this for the other board you have in the system, and also looking into whether or not you'll have to uninstall some software and/or repair other software. But for now, please try the repair on just the HSDIO driver and let us know what happens. Thanks.

Regards,

DJ L.

[DJ_L. · Accepted solution]

Hey Arthur,

You should also do a Repair on the NI-DAQmx driver as well, after you have repaired HSDIO. Let us know how this goes. Thanks.

Regards,

DJ L.

[Artybear]

Hark! That worked! I did need to do both repairs: HSDIO, then DAQmx. Now both cards are back online.

For anyone who runs into this in the future, you'll need your install discs, or you'll need to hunt for code repositories to download. They're required for the installer to fix the files.

Thank you for your swift help DJ L.!

Best,

Arthur