Digital I/O

cancel
Showing results for 
Search instead for 
Did you mean: 

HSDIO ver 1.81 not working?

Solved!
Go to solution

Hi,

       I recemtly noticed that a more recent version of HSDIO was available for download, so in some down-time I decided it would be "no harm" to install the latest version (upgrade from ver1.74). Once installed my PXIe-1073 showed up in MAX as well as my 6541 card, however the I could not control the 6541. When I clicked on self-test it failed and also threw up an error when I tried to use the test panel.

   I tried a "repair install" just in case but there was no difference. For a finish I had to uninstall and reinstal the 1.74 version. 

   Anyone else seen similar issues?

 

 

I'm running LV 2010.0.1 (32bit) on a windows 7 x64 machine.

 

0 Kudos
Message 1 of 10
(5,686 Views)

Hello ds_1,

 

Do you by chance have a record of what error you received when performing the self-test on the 6541?  Downgrading from 1.8.1 to 1.7.4 seemed to fix your issue, correct?  There should be no difference between the operation of the two drivers, and this is the first report I've seen regarding this configuration.  

Kyle A.
National Instruments
Senior Applications Engineer
0 Kudos
Message 2 of 10
(5,676 Views)

"Failed Self Test" was about as descriptive as the error was. When I tried to RESET card or open the test panel I did get an error code but I never wrote it down. (I was in a bit of a panic to get system working again.)

The downgrade to 1.74 fixed things, I'll leave it at this version for the time being.  

0 Kudos
Message 3 of 10
(5,665 Views)

I see, thank you for the additional input, and if you can update us with a more descriptive error in the future, it would be appreciated.  I apologize for the experience you had in upgrading, and I am going to do some testing on a similar setup to try and reproduce the behavior you are seeing.  Just to verify the setup:

 

PXIe-1073 integrated MXIe connection

PXI-6541 in any slot

LV 2010.0.1

NI-HSDIO 1.8.1 up from NI-HSDIO 1.7.4

 

Can you provide any additional information on the manufacturer of your PC?  Thank you.

Kyle A.
National Instruments
Senior Applications Engineer
0 Kudos
Message 4 of 10
(5,662 Views)

Hi,

       Thanks for your reply, PC is Dell Precision T3500 Win7 x64 (build 7601 Sp1)

 

0 Kudos
Message 5 of 10
(5,660 Views)

Hello,

 

I worked with Kyle to reproduce this issue. We upgraded our HSDIO driver from 1.7.4 to 1.8.1 and ran a self-test in MAX and LabVIEW 2010. We received no error and card worked properly. We are going to look into this further and see why you are seeing this error.

 

Thank you,

Vimal Fernandez || Applications Engineer  || National Instruments || (512)683-1781 || Vimal.Fernandez@ni.com 

Applications Engineer
National Instruments
0 Kudos
Message 6 of 10
(5,630 Views)

Hi Vimal,

               Thanks for taking the time to look at this for us.Based on the fact that you haven't seen an issue with similar conditions I attempted another reinstall. 

         This time it was a success. The only difference this time I think is that I made sure that the PXI chasis was powered off befpre running the installer. Perhaps this caused the previous unsuccessful install? 

     Rgds,

        ds_1 

0 Kudos
Message 7 of 10
(5,604 Views)

I spoke too soon!!! 

After 5-10 minutes of use my LV application acquiring data from the card hung. LV completely stopped responding (the stop button wouldn't even stop my VI. I opened MAX and tried to RESET the card and that hung too.

After killing LV etc and rebooting I get the same errors again.

I've captured them here:

 

Back to 1.74 again!!

 

 

 

0 Kudos
Message 8 of 10
(5,601 Views)

System info attached.

I can also send Max settings exported as .nce. Not sure if there is serial number info etc included in this so proabably best not to post here?

 

 

 

0 Kudos
Message 9 of 10
(5,598 Views)
Solution
Accepted by topic author ds_1

Hi Again!,

                Issue has no been resolved. We had an NI engineer visiting today and managed to get some of his time. It appears that the issue is related to the NI Device Loader settings.

Looking at the NI Device Loader on my system it was listed as "Stopped"  

It seems that the default settings are "Take no Action" if the service fails to respond (perhaps other things at boot up or otherwise are causing it to fail to respond.) 

It was recommended to change this to "Restart the Service" and things appear to have improved.

Rgds,

 ds1

 

 

0 Kudos
Message 10 of 10
(5,595 Views)