Building an Application in Windows to be used in Linux (with the Run-Time Engine)

Hi All,
I have an LabVIEW project I have developed in a Windows environment.  I can create an Application (.exe) using the Build Specification -> Application Builder which works fine on the development platform.
I now want to distribute the application to a Linux Environment.  The OS is openSUSE v10.3 (with GNOME).  I have downloaded the two rpm files needed for the run-time engine and installed them, as per here:http://digital.ni.com/softlib.nsf/websearch/97E14BA3E0C14A89862572C300567733?opendocument&node=13207...
Now, the question is; how do I create an Application in Windows which can be used on the Linux Box?  According to the Application Builder instructions, it's simply a case of removing the .exe extension in the Target File Name options, however, this gives an error "Invalid Extension."
If I do create an exe and manually remove the extention is doesn't work on the Linux enviroment (typing ./application).
Has anyone had experiance of this?
Many Thanks for Any Help,
Oliver
Windows XP SP 2
Labview 8.2.1
openSUSE v10.3 (with GNOME)
LabVIEW Run-time Engine Version 8.2.1 for Linux

The cross-platform nature of LabVIEW refers more to the code than to the executable.
LV (given the appropriate development version) can compile the same source code into a Windows (using LV for Windows), Linux (using LV for Linux) or Mac (using LV for Mac) program.
This means you will still have three versions of your program, one for each platform.
If you want to distribute VIs (without block diagrams), you will also need different versions of these as without the block diagram, they cannot be re-compiled for a new platform.
Shane.
Say hello to my little friend.
RFC 2323 FHE-Compliant

Similar Messages

  • Getting LabVIEW load error code 59 using LabVIEW 2010 with a Run Time Engine.

    I use a vi compiled with a run time engine to run separate vi’s in my application directory. Once a file association is made with this exe file any Vi in my application directory is available to be loaded as needed. This is a process that has been very successful for me over the years and would prefer to continue using this process. Most of my applications are running in LabVIEW 8.6 and have moved them to 2009. First indications are in 2009 this process is still working. However, I plan to go on to 2010 before upgrading my test stations.
    In 2010 I get the error 59: “The source file’s compiled code has been separated, and this version of LabVIEW does not have access to separated compiled code.”
    The same dialog box also presents, (Hex 0x626)  “Cannot open a VI with separated compiled code in a Run Time Engine that has no access to the VIObjCache.”
    What can I do in the build that will get around this error?
    Thank you

    Thank you for the solution. I am sure this works until the next vi in the vi library gets this option selected.
     The bigger issue is I was doing something that National Instruments did not support. When I started in the days of LV 4.0 it was recommended to me that I use this method as virtually all my applications were for in house projects. This is still my preference because it gives the most versatility and allows modifications of single files rather than compiling the entire application.
    The final solution I ended up with for those who may be having the same issues. My recommendation for what it is worth, is to compile the application as an executable. This is from what I can tell the only acceptable and supported method. Using this method the problem is solved.
    I have accepted this as the solution. I still don't like it. I could list the reasons why but it is a mute point.
    Thanks again for taking the time to respond to this issue and offer the solution you found.

  • Calling a VI which uses "system exec.vi" with LabVIEW run-time engine as adapter

    Hi,
    My TestStand sequence calls a VI which includes a call to "system exec.vi". When I try to load it in TestStand and if LabVIEW adapter is set to run-time engine, I get an error message "Unable to load Vi...". If I switch the adapter to "Development system", then it works fine.
    Is there any way to use "system exec.vi" in a VI which is called in TestStand with LabVIEW run-time ?
    Thanks,
    Alex
    Solved!
    Go to Solution.

    Hi Alex,
    In you case, you are getting a -18002 error.
    The reason is explained in the following link:
    -18002 Errors in TestStand
    http://digital.ni.com/public.nsf/allkb/D82FEAF0B4BA293A862575710053E252?OpenDocument
    Please have a look at the 2nd reason. This is your case.
    Hope it helps,
    Regrads
    Julien De Freitas / Applications Engineer / Certified LabVIEW Developer (CLD)
    National Instruments Switzerland

  • NI 5660 Driver DLL Errors when using Teststand 2010 and LabVIEW Run-Time Engine 2010

    This problem seems similar to the post "Resource not found error in executable on developmen​t machine." but I didn't want to repost under that thread because I only happened upon it by chance and none of my searches brought me there... so I made a more descriptive Subject.
    I am working on a system that uses a PXI Chassis with a NI 5600 Downconverter and a NI 5620 high speed digitizer, among other PXI Cards. 
    I inherited working code written in LabVIEW 2010, running with the LabVIEW Run-Time Engine 2010.  The code was using a custom executive and my task was to rewrite the test using TestStand 2010.  I reused the majority of the old code.  The old code used NI-5660 to control the 5600 and 5620.  When I run my sequence using the LV Development System and TestStand, it runs without any issues.  When I change the adapter over to LabVIEW Run-Time Engine 2010, all of my NI5660 VIs become broken due to DLL issues.  It warns that the nipxi5600u​.dll was not initialized correctly.  Many of the errors are associated with the NI Tuner and NI Scope. After this LabVIEW will crash randomly, and the seqeunce will not work in TestStand even when back with the LV Development Adapter.  The only way to recover after this is to restart the computer - TestStand automatically reverts back to the development system, the VIs are no longer broken and the sequence works again. 
    I have all of my VIs associated with a project. After reading a little bit about DLLs and TestStand, I found all of the DLLs in the dependencies section of my project and added them to my TestStand workspace.  I also used Dependency Walker to track down the problems with the nipxi5600u​.dll, the 2 DLL files that it said were not found already existed in the same folder as the original DLL (C:\Windows\System32).  I have also performed a Mass Compile to make sure everything was running in LV 2010.  If I skip the steps involving the 5660, my entire sequence runs fine. 
    The previous code was running with the LabVIEW Run-Time Engine without any issues.  Is there just a step I am missing?  Has anyone seen anything like this before?  I can send screenshots of errors to provide more detail if necessary. 

    I have tried some more things and still can't get it to work.  I have added the VIs mentioned in the Notes On Creating Modulation Executables KB both to the TestStand workspace and the LabVIEW project holding all of my VIs.  This did not change the results. 
    When I try to run my sequence, The first error I get is shown in Error 1445.bmp.  This happens when I try to use the NI 5660 initialize.vi.  If I click ignore, the next error I see is shown in Error -20551.bmp.  When I try to open the VI to look at it, I get the 2 DLL errors shown in Error loading nipxi5600u.bmp and Error loading nidaq32.bmp.  When I close TestStand, I get the error LabVIEW Fatal Error.bmp. 
    Attachments:
    Error1445.JPG ‏164 KB
    Error -20551.JPG ‏174 KB
    Error loading nipxi5600u.JPG ‏9 KB

  • Problem to install the Run-Time Engine 6.0.2 on a Windows XP

    Hi,
    A client tried to install our application on a new computer with Windows XP Pro. The application was developped on LabVIEW 6i, so he has to install the RTE 6.0.2, like it was on the old Windows 2000 computer.
    The installation of this RTE is OK, but it disturbs completely the "Add/Remove Application" windows of the Control Panel (See attachment).
    And then our application is very very slow !!!
    Our client installed then the Service Pack 2 for XP, that didn't change anything.
    Is there a possibility to use correctly a LabVIEW 6i-application on a Windows XP SP1 or SP2 ?
    Now the client is thinking to transfer directly this application on a Windows 2003 server, is it possible ? Is there a already known problem to do it ?
    The application is used to do the monitoring of geological movements and is therefore very sensitive and should run fine, without any trouble !!! We can't be unsure !
    Many thanks in advance for any help.
    Best regards,
    Gerald Monin
    Attachments:
    RTE_XP_prob.gif ‏26 KB

    Hi,
    Regarding the blank space in the add/remove programs list, please look at the following link
    http://digital.ni.com/public.nsf/websearch/9D43413​E0F8289B586256DD50072EDFB?OpenDocument
    Regarding the slow execution, I would suggest to upgrade the LV environment to 6.0.2 as well and create an installer with the RTE included to be sure to have the right version installed on the target machine. If not, then please give more info's about what is executing slower (the hole application, acessing HW,ports...).
    Porting the application to windows server 2003 is not the best idea, because LV in general is not supporting it and lv 6i is released a long time before windows 2003 server was. But i know a lot of people which are using lv 7.1 on windows server 2003 successfuly.
    I hope it helps!
    Regards,
    Evrem  

  • Hello, my Macbook Pro 13.5'', version 10.9.2, was recently invaded by what I believe is a virus, and when I open a new tab or window on chrome it would open with the Trovi search engine.

    I read online to reset the default settings on chrome and when i did that the problem seemed to all but go away. But then, not even an hour later, i notice that there are random ads that popup and sometimes ads will just open in new tabs. I know that this is a virus and i really want to get rid of it. Any help would be greatly appreciated.

    Remove V search/Downlite.
    http://www.thesafemac.com/arg-downlite/

  • Distribute application without labview run-time engine

    I read a lot of post saying if the target machine has the same run-time engine installed, then I don't need to distribute the application with labview run-time engine. Somehow this rules doesn't work for me. I have a PC installed labview 2010 development system and has run-time engine 2011 SP1. I also download the same version of run-time engine and installed it in a target PC. When I distribute my labview application, if I select to include the run-time engine in build properties, the application will be able to install and run properly in the target machine; If I don't include the run-time engine, then I wouldn't be able to run the application.
    Does anyone help me on this? I don't want to always build the application with the run-time engine since it's quite big
    Solved!
    Go to Solution.

    Could you take a look at my NI software list and let me know what labview run-time engine is really in use?
    And in build properties, it actually list addition installer include labview run time engine SP1. If I includes this version of run-time engine and run the installer in target machine, it will still install the run-time engines just like there is no run-time engine installed in the target machine before.
    Attachments:
    NI software.jpg ‏98 KB
    Installer.jpg ‏216 KB

  • When opening PT Assembler, Windows tries & fails to open NI Run-Time engine

    I am using PT Assembler, a front-end for the Panorama Tools software bundle, to stitch microscope images taken by LabVIEW using the QCam Suite.  Whenever I attempt to open PT Assembler, Windows informs me that it needs to configure the NI LabVIEW Run-Time Engine 7.1.1, which it cannot as it is not installed.  After cancelling the configuration 4-5 times, my program opens and runs without errors.
    PT Assembler has absolutely nothing to do with with NI or Labview as far as I can determine, so why does Windows try to open it with the run-time engine?   I attempted to install the 7.1.1 engine from ni.com but was informed that it was unavailable.  Is there any way I can keep Windows from attempting to use the engine?  I could install a later version of the engine and hope it works, but I am a bit leery about how it might affect my program.

    Hi rhazelton,
    If this program hasn't been created in LabVIEW, then I'm not sure why it would be doing this..  However, you should be able to download the 7.1.1 run-time here.  Give it a try and see what happens!
    Regards, 
    Brian A.
    National Instruments
    Applications Engineer

  • Is Labview Run-Time engine 2009 SP1 compatible with Windows 8

    I potentially need to install a Labview executable and Run-time engine 2009 on a Windows 8 OS.  From looking at the run-time engine support, it only looks like it only shows windows 7 down to XP.  Does anyone have any experience using Runtime 2009 on Windows 8?

    Hi Awhite144,
    The first version of LabVIEW to officially support Windows 8 is LabVIEW 2012 SP1. That being said, I would expect LabVIEW 2009 to work fine on Windows 8, and if you run into any trouble, feel free to post it here. LabVIEW 2012 SP1 installs a number of older LabVIEW run-time engines (including LabVIEW 2009), so it will install on Windows 8.
    I have not personally used LabVIEW 2009 on Windows 8, maybe if someone else has experience with it they can weigh in, but I expect it to work.
    As an important consideration, I assume you are talking about the full version of Windows 8, not Windows 8 RT. 
    Regards,
    Jeff Peacock 
    Product Support Engineer | LabVIEW R&D | National Instruments 

  • Labview using Report generation toolkit in 2011 run time engine

    is that possiblity to run the  word in labview using Report generation toolkit in 2011 run time engine

    It is possible to use the Report generaion toolkit with the run time engine.  But you will have to include a lot of VIs from User lib since the report generation toolkit uses a lot of dynamically called VIs and classses.
    Certified LabVIEW Architect
    Certified Professional Instructor

  • Can't install LabVIEW Run-Time Engine 6.1 on Windows Terminal Server

    With my system admin, we tried to install the LabVIEW Run-Time Engine 6.1 on our Windows Terminal Server NT4. And we get an error all the time:
    -install using the plugin
    -install using LVRTE.exe
    -install after rebooting the server
    But I remember that we could install the Run-Time Engine 6.0 on another Windows Terminal Server NT4.
    Is there any compatibility issues with the new Run-Time Engine 6.1 ??
    Thanks for your help
    Cyrille

    Cyrille,
    What is the error that you get when trying to install the run-time engine?
    Are you installing it from the LabVIEW CD, or did you download it from the web site?
    To further troubleshoot this problem, it would be best if you send us an email to [email protected] and send the above information.
    Also, try running the installer from the command prompt window, and use the following syntax:
    setup.exe/l*v
    This will save the error log to the file you specify. Send us also this file to help us troubleshoot.
    Thanks
    Zvezdana S.
    National Instruments

  • Why is VI not executable using Labview 7.1 Run-Time Engine?

    Hi,
    In our Teststand sequence, we have a Labview Action step which is returning an error: "The VI is not executable", along with the error code: -18002.
    This error occurs on a Production PC using the L.V. 7.1 Run-Time Engine.
    I'm aware of Mass Compiling to ensure all the VI's are the correct version, but this has not resolved the problem.
    The software was installed on the production PC using a Teststand created installer, with the Labview Adapter set
    correctly to the Run-Time Engine, i.e. not trying to open the Labview Developer Server to execute the step at run time.
    Because it's the 1st Labview module to be executed, I added another similar step to run beforehand, i.e. the new simple
    Labview code ran first. This executed correctly, but then the next step caused the error above.
    The small number of associated sub-vi's are on the target PC, and have been mass compiled.
    I've had -18002 errors before, but this is one I cannot cure.
    All suggestions gratefully received.
    Gary.

    Hi Guys,
    Regarding this -18002 error when using the Run Time Engine instead of the Development Environment, what is the VI within the step that is failing (in any of the cases you've mentioned) trying to do? Are they built around any toolkits?
    In my experiments with a simple VI (with just a user dialogue) using the LabVIEW 7.1 RTE in both TestStand 3.1 and 3.5 this morning, I haven't found any issues
    There is a possibility if any of the sub-VIs or toolkits you use contain a Merge Errors.vi, that the Run Time Engine picks up a copy of the VI built for previous versions of the RunTime Engine (due to the order in which the sub-VI directories are scanned), and it cannot convert it.
    There are a few solutions for this, the easiest one looks to be to copy the error.llb\Merge Errors.vi for LabVIEW 7.1 into the same directory as the VI you're calling (so TestStand can pick it up easily).
    Can you let me know if this solution helps at all? If not, would it be possible to post up any of the code or sequence you're having problems with?
    Best wishes,
    Mark
    Applications Engineer
    National Instruments

  • Visa Control grayed out when executable used with Run-time Engine

    When I run an executable on a machine with only the Run-time Engine the Visa Control for Com Ports is grayed out. I'm guessing that I am missing a library, but do not know which one.

    You need to install the VISA run-time. If you are just using VISA for serial communication, then there is an option on the app builder (Installer Settings>Advanced) for Serial Port Support. This will add a much smaller version of the VISA run-time engine to the installer you create. If you are using GPIB, etc., you have to install the hardware driver (i.e. NI-GPIB) and the full VISA run-time engine.

  • Can I use the labview run-time engine 2010 with my LV 2012 program?

    Hi all,
    I will receive the new Labview Developer Suite 2012 DS2 in a few days and
    I am wondering if it is possible to run LV2012 programs on the LV run-time engine 2010 or is it necessary to update all my clients from run-time engine 2010 to 2012?
    Stay Hungry, Stay Foolish
    Solved!
    Go to Solution.

    Hi Benjamin,
    You will not be able to use the LabVIEW 2010 run-time engine with LabVIEW 2012 applications.  Versions of run-time engines need to correspond with the version of LabVIEW that you have installed.
    The following links direct you to our download pages for the run-time engine:
    The 32-Bit Run-Time Engine can be downloaded from our website as can the 64-Bit Run-Time Engine, depending on which version of operating system you, use by clicking the link under "Standard Download".
    Hope this helps.
    Marshall B
    Applications Engineer
    National Instruments UK & Ireland

  • Why does "NI LabVIEW Run-Time Engine 6.1" window appear when I start LabVIEW?

    it also prompts "insert the 'NI LabVIEW Run-Time Engine 6.1' disk.
    Attachments:
    windows.jpg ‏26 KB

    Hi,
    There can be many reasons why this error would appear. Most probably, you have a broken installation of the Run-Time engine.
    Just reinstall the run-time engine from the LabVIEW 6.1 CD. You can also download it from our web site:
    LabVIEW Run-time Engine Version 6.1 for Windows 95/98/NT/2000/ME/XP
    Zvezdana S.
    NAtional Instruments

Maybe you are looking for