Cannot build executable with niHSDIO Close.vi error

[DJ_L.]

Hey Martin,

So it looks like you can't even run your VI because you have a broken arrow, much less build an executable. So now we need to figure out why that one VI is giving you issues. You said that you opened one of the examples, but I am curious as to where you got the example? Did you open it using the Example Finder or did you browse to the directory where the examples are? Have you tried to delete the niHSDIO Close.VI and put down one in the palette?

Actually, an easy test would be to start with a blank VI, and then just place an HSDIO Init.VI (Acquisition or Generation), and then right after it place the HSDIO Close.VI from the palette. Create a constant for the Resource and see if your Run arrow is broken. See the image below. Try this out and let us know how that goes. Thanks, and have a great day.

Regards,

DJ L.

[Marty_H]

Hi DJ L,

I have tried both the ways you have explained.  The first was using the example in the example finder and the other was just using the one from the palette.  Both did not work, but they do now!

What I did was delete the refnum from the Get Session Reference.Vi and re-create it by right-clicking on the register session vi and creating a constant refnum.  Now saved it does not error.

Was this a specific problem I am having?  Are you using LabVIEW 8.6?  The Get Session Reference.vi works in 8.5.1, but not in 8.6. (That is on my machine)

Regards

Martin

[Andrew McL]

Hi Marty H,

Have you been able to use these example VIs to build an executable? It may be worth removing LabVIEW and re-installing it as this may help clear up this problem.

Thanks,

[Marty_H]

Hi,

From my previous posts, I removed all the NI software and just installed 8.6 from the downloaded file on the NI website.  Then I installed the NISDIO driver version 1.5.4 from the download link.  This did not solve the problem.

Regards

Martin

[Andrew McL]

Hi Marty,

Have you tried  deleting the Refnum and replacing it, like you mentioned for the examples, in your own code?

Have you tried turning the example programs into an executable?

Thanks,

[Marty_H]

Hi Andrew,

If you read my post to DJ  L I deleted the refum that caused the problem and re-created it with a new one.  I then re-saved it and I can now build my application.  I was interested if this has been a problem for anyone else.  Have you looked at the nisDIO Close.vi using 8.6?

Martin

[DJ_L.]

Hey Martin,

First, I'm glad to hear that you were able to pinpoint the problem down to that refnum in the Get Session Reference VI, and are now up and running. We would like to help you determine what was the cause of the VI getting into the state that it did. It sounds like the refnum was not pointing to the correct session, possibly to an older version of the DAQmx driver (which HSDIO depends on).

So we have not been able to reproduce this issue using LabVIEW 8.6 and the HSDIO 1.5.4 driver, which brings me to some questions about the way that you installed the driver and LabVIEW. If you can explain the exact steps that you took when installing everything, that would help us possibly reproduce this issue. Some related troubleshooting type of questions would be:

- Did you install the HSDIO driver before or after you installed LabVIEW 8.6?

    - If you installed it before, how did you go about adding support for LV 8.6, by modifying the driver or copying files to the LV directory?

- Did you deselect any of the options in the beginning of the installer?

    - If you deselected anything, did you maybe deselect DAQmx support for LV?

- When you uninstalled and reinstalled HSDIO and LV 8.6, did you also uninstall DAQmx or just the HSDIO driver?

- Did you install any other drivers before or after you installed the HSDIO driver (if so, which ones and in what order)?

Somehow that refnum got corrupted, and when you deleted it and recreated the constant, it knew where to point to. So the reason for all the insallation questions is because if something got corrupted then most likely it was during installation. One other thing that you can try is to put LabVIEW 8.6 and HSDIO 1.5.4 on a clean machine that does not have any previous versions on it and see if you have the same issues, but this of course is if you have the extra time to try that out, and is not necessary if you do not cuz I am sure you are busy enough. Let us know if you have any further questions or concerns. Thanks, and have a great day.

Regards,

DJ L.

[Marty_H]

Hi DJ L,

Thanks for your support.

To answer your questions, I started with the LabVIEW 8.5.1 development suite.  I installed all the default options, plus the drivers.  The disk set is from the second quarter 2008.  I then installed Version 8.6 from the NI website shortly after using 8.5.1.  I hadn't used the HSDIO driver before this so I don't know whether the VI worked.  As I was developing software for the PXI HSDIO card, I started looking at the examples that came with LabVIEW, and discovered this problem with the Get Session Reference.  When I copied my files from my PC to the PXI Controller that had just only version 8.6 Trial version, the Get Session Refnum was fine!  Anyway, I unistalled everything from my machine and re-installed 8.6 only and the latest version of HSDIO  commented in my previous posts.  Still, this didn't solve the problem.  I think many of the Windows Registry entries are still there even after uninstalling LabVIEW.

Cheers

Martin