Stand alone .exe GPIB communication issue

[Dennis_Knutson]

Why don't you want to provide the path? You probably have two instances of the dll. There would be one in the ivi foundation folder that was the original install. If you have another in the build folder, that could be the cause of the error. For ivi, you just can't make things up as you go.

[mxmxm]

Ok, so when I went to get the path, I realized that the software must had set it by default because it wouldn't let me access it. So I've set it to the following path "C:\CSP2\chr62000p_LV_20120309\chr62000.dll" which corresponds to the one I use in my VI. What's the next step?

[Dennis_Knutson]

Run the VI to see if you get the error. I suspect that you will. I suspect that the issue is the duplicate dll. An IVI dll should be installed in the appropriate IVI folder - the one that it was originally installed to because it also needs the IVI Compliance functions. Your VI is probably referencing the dll in the correct location. If you still get the error as I suspect, delete it and try running the exe.

[mxmxm]

Well, my VI was still working but my .exe wasn't.

But I'm starting to figure out there may be something wrong about the .dll. It seems I was using both a IVI installer and a package that contained a VI library and another .dll. Am I supposed to do that or does the IVI package (.msi installer with a NI interface) is supposed to be enough???

[Dennis_Knutson]

I've always used the original instrument driver installer. As I said, this will place the dll in the correct ivi foundation folder - exactly where the VI is calling it.

[mxmxm]

How can I modify the .dll that is called by the VI and how can I make sure that the right one is included in the support files of the .exe?

So far I've uninstalled the IVI package and tried to rely on the .zip containing the VI library and the .dll. I've rerouted all the VIs to the correct .dll and it still works only when I'm running the VI in LabVIEW.

Also, it seems the .vi from the library are pointing towards a different .dll than the one the IVI was pointing to.

Driver sessions path was : C:\Program Files (x86)\IVI Foundation\IVI\Bin\chr62000_32.dll
While VI was : C:\CSP2\chr62000p_LV_20120309\chr62000.dll

[Dennis_Knutson]

I keep saying that I do not use the dll included as a support file, I did not mark the dll as always include and you should not remove the ivi compliance package.

I'm mostly going from memory on this since I don't have an instrument/driver to test.

[mxmxm]

Does the IVI package come with its own VIs?? Because the VIs in the .zip won't work with the IVI .dll. If so, how can I access those VIs??

[Dennis_Knutson]

At this point, I don't what you mean. What zip file? Are you still just trying to run the exe from the development pc?

[mxmxm]

Yes, I'm trying to run from the development PC.

What I mean is that I have used two packages from Chroma.

The first one was a .zip containing a chr26000.dll and a library of VIs which I used in my project. I also had installed another pack, the IVI package.

I've looked into it and it says the IVI package is for LabWindows.. so I guess it wasn't necessary to install that. Anyways, using the LabVIEW package from Chroma I still get the error when I'm running the .exe.