LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW Lode Error code 3

I have installed the LabVIEW runtime engine on a machine that does not have LabVIEW installed.  I then exported my program to a .exe using the project manager.  When I went to run the .exe, I get an error message that says "Application failed to start because instrsup.dll was not found" and it suggests re-installing the application (though they don't specify what "the application is," the run-time or the .exe?) may solve the problem.  When I click "OK" a second error message pops up that says "An error occurred loading VI 'dat4700outputvalue.vi'  LabVIEW load error 3: could not load front panel.  "When I click OK on the 2nd error message, the 1st message comes up (with one ofthe other Datron driver .vis), and it cycles between the two until I have said "OK" to each error message about 10 times.  After clicking "ok" on the 2 error messages enough, the front panel finally shows up, along with a 3rd error message that says "missing sub.vi dat4700 initialize in VI TVC Cal warmup" along with all of my other drivers for my Datron 4700. 

 

error.JPG

It looks like all of my drivers for my Datron 4700 don't make it into the program for some reason.  I have tried re-compiling the program through the project manager and it still doesn't work.

Any ideas?  The only other thing I can think to try is just re-installing the run time engine...

0 Kudos
Message 1 of 13
(3,290 Views)

Did you move the .dll over to the PC?

-----------------------------------------------------------------------------------------
Reese, (former CLAD, future CLD)

Some people call me the Space Cowboy!
Some call me the gangster of love.
Some people call me MoReese!
...I'm right here baby, right here, right here, right here at home
0 Kudos
Message 2 of 13
(3,283 Views)

The dat4700_32.dll file is in the "data" folder that is created with the executable, and was moved onto the cpu in question.

0 Kudos
Message 3 of 13
(3,280 Views)

Hardware drivers are never included in an exe (LabVIEW or otherwise). For example, if you were using an NI DAQ card, you would need to include DAQmx as an additional installer when you create the installer for the exe and run-time engine. If you are using NI-VISA, you would also have to include that as a separate installer. I have no idea what your datron uses but if it requires a windows driver, then you must run the installer for it.

0 Kudos
Message 4 of 13
(3,279 Views)

And if I run the .exe file on the computer I originally created it on, even if I run it off of the travel USB drive that I am using to move the program across computers, I do not get an error message.

0 Kudos
Message 5 of 13
(3,278 Views)

The datron "driver" I am using is one I downloaded from the NI driver database, it is a labview driver that does not need a seperate install (except for, you know, putting it in the correct labview folder).

0 Kudos
Message 6 of 13
(3,277 Views)

You will need to provide the link. The only Datron 4700 in the NI Instrument Driver Network is a LabWindows driver - not LabVIEW at all and your mention of a dll shows that it is not a native LabVIEW driver. Do you know for a fact that the driver does not require anything additional such as the CVI run-time or the IVI Compliance Package?

Message 7 of 13
(3,274 Views)

Oh, I remember now, it WAS a CVI/Labwindows driver that I converted to LabVIEW using the conversion tool

0 Kudos
Message 8 of 13
(3,271 Views)

And the instrsup.dll that is mentioned in the error would need to be installed. See if including that fixes the problem. It will be in the windows/system32 folder.

Message 9 of 13
(3,268 Views)

I copy/pasted the instrsup.dll from ym cpu over to the other one, and that got rid of all of the error messages.

 

However, when I run it, none of my GPIB devices show up in the drop-down lists, even if I click "refresh," though they are visable in MAX.  I am currently downloading the VISA installer, so it will go up on the CPU next.

0 Kudos
Message 10 of 13
(3,265 Views)