Labview runtime broken 5.1.1

I created a 'development' library file with labview development that includes ALL sub vi's. When I try to run it with runtime it says a sub-vi is not executable. I open it back up with development just fine and re-save it. It is still broken with runtime. I have labview development 5.1 and runtime 5.1.1. Any ideas?

Hi Stee1hed,
You can use runtime to run executables. They aren't used to run development VIs or .llb files. In your case, i think you are creating a llb file with all the sub vi's by saving with options, you are not creating a executable. To be able to use the runtime you could create a executable and include all the subvi's or the llb as support files.
Hope this helps,
pravin

Similar Messages

LabView TestStand interoperability with LabView runtime adapter

I would like to get some background information on how the interoperability of LabView and TestStand works.
We are using LabView steps mainly for some minor tasks in TestStand projects.
We do not use the regular deployment way as proposed by NI, but simply use one or more VI folders from which we reference LabView steps.
Deployment is done by copying the whole TestStand/LabView folder structure to the target machine.
We use the LabView runtime adapter within on our deployed systems.
We never mix LabView versions within one project.
Now, we frequently face the situation that the exact same project structure on two different machines has problems with the LabView steps.
So one changed VI runs on one target machine while the other after copy deployment is broken. Due to the same project structure and the virtual drives the paths must be the same.
A mass compile usually solves the situation.
So this is mystery number 1.
Today, I had the same problem, however I did not mass compile the full VI folder but simply some folders which I assumed had changed.
One VI which was referenced by TestStand was not mass compiled and was declared as broken by TestStand.
All I did was opening the broken VI in LabView Development System and nothing was obviously changed by LabView.
I closed the VI and pressed the Reload VI button on the TestStand step and the VI was working again, however the sequence file now had changed somehow (* at file name).
Another phenomenon:
An existing project on a machine was running with a certain user.
After switching the user, the VI steps of the project were suddenly broken.
My questions?
1) Why do VIs which run in the development system flawlessly become broken in the runtime?
2) Does the runtime use different search paths than the development system?
3) What kind of information does the mass compilation produce and where is it stored.
4) What kind of information does TestStand store along with the VI?
5) Is there a way to diagnose the problem with the runtime adapter ? With the runtime adapter I cannot open the VI to see what is the problem and in the developer mode it works.

First, to clarify a few points:
1) It is not necessary to use a workspace for TestStand deployments. You can specify a directory of source files for a TestStand deployment.
2) TestStand licensing should not be affecting this issue in any way. TestStand licenses do not have any impact on LabVIEW VI execution in TestStand.
Thorsten,
The issues you are describing are likely being caused by the LabVIEW VIs needing to be recompiled. The runtime engine is not able to recompile VIs, but the LabVIEW Dev System can, so this explains why you are able to execute again after opening the VIs in LabVIEW Dev. it also explains why a mass compile fixes the issue.
There are a variety of reasons why this could be happening. One scenario that could cause this to happen is that you make a change in one VI, but the change causes a second VI to need to be recompiled. This could cause a problem if you redeploy only the VI that you changed, because it will not be able to work properly unless the second VI is recompiled, which cannot be done by the LabVIEW RTE alone. This can happen because the LabVIEW compiler will optimize certain operations in the compiled code depending on where data is used--for example, the compiler will try to avoid allocating a copy of an array if it does not need to be accessed by multiple pieces of code at the same time. As you can imagine, this type of optimization might be appropriate for one version of your code, but might not be appropriate if a subVI changes such that it needs access to the array in parallel with the rest of the code.
The specific example I mentioned is called the Inplaceness Algorithm, and is described along with much more information about the LabVIEW compiler in this whitepaper. This might help explain the reasons a LabVIEW VI would need to be recompiled.
One potential solution to your problem that would allow you to keep your current deployment method would be to use packed project libraries (PPLs). You could have multiple PPLs for different parts of your code that you want to be able to update individually, which would allow you to make small changes to your codebase without having to deploy the entire set of code at once. A PPL is a self-contained set of compiled code that does not change, which should avoid the recompile issue from occurring.

Not found error message from LabVIEW runtime when called from VC++ with statically linked MFC

I have a dll built using LabVIEW 6i. I am calling the dll from a VC++ application. When the application loads I get an error pop-up 'cannot find LabVIEW runtime'. If I change the VC++ code to dynamically load MFC (using the loadlibrary function) or dynamically load the LabVIEW dll I created then the problem goes away. Only when both are loaded statically do I get the error message.
The target machine is running Win2K pro and has the LabVIEW runtime installed.
I do not want do dynamic loads as I need to call the dll from a legacy application. Are there any options to change the way LV links to MFC or to force the dll to find the LV runtime?
Alan Widmer

Ben,
I have attached a ZIP of the files required to test a DLL from an MFC application. Or you can build the same application by following the instructions below. I used the numtest dll that you previously sent to me so there is no 'magic' in the LabVIEW or dll.
In VC++ select NEW. Pick the MFC AppWizard (MFC) to build an MFC application. In the wizard select
Project Name: MFCNumtest
Single Document
No database support
No Compound document support
Support for ActiveX
Default settings on the Features page
MFC Standard
MFC as a shared DLL
From the ResourceView of the project explorer, add an item Test to the IDR_MAINFRAME menu then add an item Go as a submenu item (with an ID of ID_TEST_GO)
Right click the new menu item and run the Class
Wizard. Click Add Function.. button to make a function OnTestGo()
Open MainFrm.cpp and scroll to the end of the file to see the skeleton for the OnTestGo function. In this function add a call to the LabVIEW dll. You will also need to add a reference to the .lib file and the usual extcode.h.
When you run the app you will see a window with the Test menu item. Select it and click Go to run the call to LabVIEW.
This all works great. If you now go to Project | Settings and on the general tab change the Microsoft Foundation Classes: item from 'Use MFC in a shared DLL' to 'Use MFC in a static library' rebuild ALL files in the project and run the app you get the error message:
System error 998 while loading the LabVIEW Run-Time Engine (C:\Program Files\National Instruments\shared\LabVIEW Run-Time\6.0\\lvrt.dll).
numtest requires a version 6.0 (or compatible) LabVIEW Run-Time Engine. Please contact the vendor of numtest to correct this problem.
I apologies for my slow response, g
ot distracted by some other issues.
Thanks for your help,
Alan Widmer.
Attachments:
mfcnumtest.zip ‏44 KB

LabVIEW Runtime engine on Windows Embedded Standard 7 P 32/64 bit?

Did anyone ever try to install and run LabVIEW Runtime engine (2011 or later) on Windows Embedded Standard 7 P 32/64 bit?
I am trying to figure out if this will work, for example on a Beckhoff CX5120 embedded PC. I will need to have some simple TCP/IP communication in order to exchange information with another PC, but nothing else, i.e. drivers, etc...
I hope someone tried to do this already. I just don't have the right hardware right now to check it out.
Solved!
Go to Solution.

As NI sells touch panels with WES7 installed here: http://sine.ni.com/nips/cds/view/p/lang/en/nid/210551 it's pretty safe to assume they've used the RTE on WES7.
But yes, it's been done.

How To Handle Labview Runtime Error in Teststand

Hi,
I am working NI-CAN device to transfer CAN frames through the VI's using TestStand. Before transmission took place, we need to choose for the port, in case if the port is selected wrong, Labview take it as a runtime error and handles accordingly while teststand keeps on running i.e. if I have 7 steps that are calling that VI, the runtime error from the labview will appear that many times also. Is there any way to handle labview runtime errors directly through TestStand. I have a sequence that will take care of the Runtime Errors in my sequence file.
Please help me soon.
Thanks in Advance,
Vivek

Hi Vivek,
If the LabVIEW VI is handling the error, then what you probably want to do is make the VI have an Error Out output terminal. You'd have to wire the appropriate error out wires to the terminal of course.
This way, when you call the VI from TestStand, you can check the value of the Error Out and decide in TestStand how to handle it (skip the remaining steps, popup a message, etc).
Jervin Justin
NI TestStand Product Manager

Windows error 998 by installing labview runtime 8.2.1 on windows xp

Hello,
I got Windows Error 998 during installation of the labview runtime engine 8.2.1 on windows xp system. The installation with the same package worked on serveral other systems with the same os.
Any ideas?
Thanks a lot and best regards,
Michael
Attachments:
Error_998.png ‏14 KB

Based on the message it appears it's having problems reading the file. Did you copy the files from a CD? From a network? The file itself may be corrupt. Try recopying the files to your hard drive. You may also want to check your hard drive for errors.

Unable to determine the install root path for the LabVIEW Runtime Engine

Hi,
i have an issue with using a LabVIEW interop assembly in a .NET application. I get an exception "Unable to determine the install root path for the LabVIEW Runtime Engine" when calling the assembly.
The little test program is attached below. It's called dotNETHost.exe. If you excecute the programm a dialog with an button appears. Clicking the button shall open another dialog (the LabVIEW Interop component). But the only thing I get is the exception message. The ZIP folder also contains the complete exception meassage (ExceptionMessange.jpg & ExceptionDetails.txt).
The Interop Assembly was built with LabVIEW 2011. We use Visual Studio 2010 and .NET 4.0.. The dotNETHost.exe.config file is prepared as mentioned in Knowledge base - Loading .NET 4.0 assemblies.
The Interop assembly contains only one simple dialog (loop is finished by clicking OK) without calling any other VIs or other DLL's. In case of this there's also no support directory generated by the build process.
I have no idea why it doesn' work. I hope anyone can help me.
Thanks in advance
Kay
Attachments:
Debug.zip ‏75 KB

This may be unrelated, but Labview and .Net4.0 dont work well together. Not yet anyway. I had to compile my assembly in 3.5 to get it to work.
Please read the following:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configuring_clr_version/
http://digital.ni.com/public.nsf/allkb/32B0BA28A72AA87D8625782600737DE9
http://digital.ni.com/public.nsf/allkb/2030D78CFB2F0ADA86257718006362A3?OpenDocument
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

Profibus-Connection with NI LabVIEW Runtime-engine

Hi,
I have a Profibus network running in our porduction lane.
Now we want to report several states of this production continously.
Therefore I want to connect a desktop-pc via profibus to the PLC. But I want to run the VI on the PC as an application(exe) with the NI LabVIEW runtime engine because I won´t install LabVIEW on this PC. (on my development computer I have LabVIEW 2011)
My question is:
Does the Profibus communication work if I run the VI that way if I add the needed "additional installer" to my installer file?
I´m quite sure that it will work but I want to check this point before ordering a Profibus-Board.
I hope you understand my question and give me a positive answer so I can order an new Profibus-PCI-Board
best regards
Martin

Hi Martin,
the scenario you are describing sounds reasonable and that should work.
But in general, if you buy something at NI you can always call and describe your situation. Either the sales person can help you with your decision or in more complicated cases the sales person redirects you to a support engineer.
Best regards,
Christoph

Running Datasocket in labview 2013 open labview runtime engine 7.0

Hello All,
I am trying to communicate with a COGNEX camera using Labview 2013. I am using Datasocket to read tags from cognex OPC server.
but when I open labview and run the code for the first time. An installer will automatically pop up trying to install labview runtime engine 7.0.
When i cancel the installation datasocket throws an error. Again if i run second time, datasocket works fine and communicate with cognex camera using OPC.
This problem comes everytime I open labview and run the datasocket. I cancel the installer. second time onwards when i run the code everything works fine.
This is actually annoying and i doubt how things will work when i make an executable.
Need help.
Is this due to datasocket version installed... how to resolve this.

Hi phil,
That is interesting that you were unable to find the offending key that the installation is having trouble with. Do you have Administrator privileges on your computer? You may even want to try to log in as the actual Administrator itself to make sure that you have access to all of the proper registry keys. Also, I was going to say that I do think you're right with Windows XP not having the Scanreg/fix function, but there are several free programs that you can download as registry checkers. You may want to try one of those to see if you can find the key and give it the proper permission.
As far as the other part of your question, the Run-Time Engines are very important for LabVIEW to be able to run, but the 7.1.1 Run-Time Engine should not be affecting a LabVIEW 8.2 installation as it will use the 8.2 Run-Time Engine. One thing that you can do is go into your Control Panel under Add or Remove Programs>>National Instruments Software and you can try and repair/modify your Run-Time Engine there. If you already have the 7.1.1 Run-Time Engine on your computer, this is where it will show up so you can make any changes you want. Also, if you go to www.ni.com and click on "Drivers and Updates" on the right, you will be able to find the Run-Time Engine there that you will need, but I would definitely try using a downloadable registry checker first before attempting to change any of the software that is currently on your computer. As stated in the Knowledgebase article, this is actually an error from Windows saying that the registry key does not have the proper permission settings, so I am reluctant to say that downloading the new Run-Time Engine from our website will help much. Please try some of these suggestions out and let me know how they work out for you. Thanks!
Regards
Noah R
Applications Engineering
National Instruments

Labview runtime engine plugin problem in Mac OS X

Hi:
We have just recently acquired a macBook Pro and am trying to test some instrumentation modules we have previously developed online for Circuit Theory courses on the MAc platform.
These VI's are installed on lab view server and we have no difficulty accessing them in Windows XP or Vista from a browser either Firefox or IE. Of course the latest version of runtime engine is installed on the pc prior to accessing the vi using remote panel and secondly we have to disable any virus protection software.
I have also installed the 8.5 version of LV runtime engine on the macbook with Leopard 10.5.x OS. I can see the LV plugin with the proper version in the Installed plug in check for the Safari browser. But every time the Remote panel is accessed I get a missing plugin message.
Here is the message:
Safari cannot find the Internet plug-in.
The page “Blackboard Academic Suite” has content of MIME type “application/x-labviewrpvi82”, but you don’t have a plug-in installed for this MIME type. A plug-in should be available on this page:
http://digital.ni.com/express.nsf/express?openagent&code=exck2m&
Do you want to open the page?
The page it suggests is the NI site for the plugin download?
I am really in a corner and donot know what I am doing is wrong? Any help will be appreciated?
Vishnu

I'm not a Mac expert, but it sounds like you are missing the LabVIEW Browser Plugin which is necessary to view remote front panels. That plugin installs with the LabVIEW runtime engine which you can find here. I don't think Safari requires any extra configuration to work with the plugin but it might... let us know if installing the runtime engine doesn't resolve the problem.
Travis M
LabVIEW R&D
National Instruments

Is there a .sld file for LabView runtime engine when creating Embedded XP image

I'm looking for a .sld file to aid inclusion of LabView runtime engine in my embedded XP image. Has anyone already written one?

Hi,
unfortunately, National Instruments doesn't have any sld files for embedded OS'es, however, please checkout the links from the Lookout discussion forum, where someone was trying to do something similar.
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=506500000008000000AD5C0000&ECategory=Lookout
Although there's no definitive resolution to this thread, the person who answered has said he could be contacted.
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

CIN (Code interface node) LabVIEW runtime engine dependency

Hello:
Am I correct that the old style CIN (code interface node) is not dependent on what version of LabVIEW runtime engine is being used?
However if I create a dll from say LabVIEW 8.2 I must then alway have LabVIEW runtime 8.2 installed on any newer machine with newer version of LabVIEW?
Thank You!

GE Osmonics wrote:
Hello:
What I have are old CIN (no source) that work in LabVIEW7.1 but will not work in LabVIEW 2010 (link error, object code not loaded).
What I thought I could do is generate dll from the vi's that contain the CIN using LabVIEW 7.1 with application builder.
I could use the Call Library Function from LabVIEW 2010 to load the 7.1 generated dll to effectively do what the old CIN accomplished
provided I installed the LabVIEW 7.1 runtime engine on my LabVIEW 2010 machine
Thanks for the input
If the CIN resource doesn't load you most likely changed the LabVIEW platform. LabVIEW for Windows 32 Bit and LabVIEW for Windows 64 Bit are different platforms. Just as LabVIEW for Windows and LabVIEW for Macintosh or Linux. A 32 Bit DLL, which a CIN is internally can't be executed in a 64 Bit environment at all.
Your solution fails for more than one reason here. LabVIEW will try to load and link a LabVIEW DLL into its actual runtime environment to avoid interprocess communication latency which would be inavoidable if the DLL is started in a seperate runtime engine, which is in fact a new process. If your issue is 32 bit to 64 Bit you won't be able to link the 7.1 32 Bit DLL into your LabVIEW 64 Bit application through the Call Library Node at all.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Install MAX with only LabVIEW runtime engine

Hi,
I want to know if it is possible to install MAX from the Device Driver CD, when only LabVIEW RunTime engine is installed. There is no full installation of LabVIEW on that PC. That's MAX 3.1.1.3004 with LabVIEW RunTime Engine 7.1.
Patrick.

Dear Patrick,
The device driver CD usually does not have a single installation of MAX, but you can install MAX by installing most of the other drivers such as NI-DAQ, NI-488.2, NI-Serial, etc. MAX does not require LabVIEW, so you can have MAX and LabVIEW Run-Time without LabVIEW. Have a great day!
Sincerely,
Marni S.

Installing Labview runtime engine 2011

Hi,
Is it mandatory to uninstall any previous version of the Labview runtime engine before installing the 2011 verstion ?
Thanks.

No, you should actutally keep the older runtime engine installed in case you still have applications that depend on it. The 2011 run time will only support applications built with LabVIEW 2011.
LabVIEW Champion . Do more with less code and in less time .

Load Labview runtime engine with matlab platform

When I use labview DLL on matlab platform it loads labview runtime engine.
Once I use "close all" command of matlab, labview runtime engine is not available any more so I want to reload it.
How can I do this?
If I run the DLL again an error is occurred.
Best regards,
Nir

Hello Nir,
I recommend contacting MathWorks for assistance with the exact functionality and results of close all. Based on online documentation for calling DLLs in MATLAB, you should use unloadlibrary to remove the LabVIEW DLL from memory instead of close all. If you use this method, are you able to load the LabVIEW DLL (using the loadlibrary function) and call it successfully from MATLAB?
MATLAB® is a registered trademark of The MathWorks, Inc.
Regards,
Andrew Brown
Applications Engineer
National Instruments

Labview runtime broken 5.1.1

Similar Messages

Maybe you are looking for