Runtime engine difference​s

Hello all,
I've long known (improperly assumed ?) that the CVI runtime engine was free
to distribute along with apps we develop. And nothing here seems to prove me
wrong:
http://joule.ni.com/nidu/cds/view/p/id/2245/lang/e​n
Then I was surprised to see this:
http://sine.ni.com/nips/cds/view/p/lang/en/nid/203​157
So am I reading this wrong or does it cost 1100$ to redistribute my apps for
Linux ?
Note that it's not clear if this is only the runtime or the full compiler
because it says "compile and run"...
Guillaume Dargaud
http://www.gdargaud.net/

Hello Guillaume,
Your assumption is correct. The CVI runtime engine is free.
The cost of the Linux module is $1100, but this doesn't mean that you have to pay $1100 for each system where you want to install your application + the runtime. Purchasing the module (which I believe you already own) gives you the right to port your application to Linux. Once you have this license, you can distribute your application (along with the module, or simply the CVI runtime libraries if that's all you need) to as many Linux targets as you wish.
The key sentence in the page that you linked to is: "Compile and run Windows-created applications on multiple Linux distributions".
Luis

Similar Messages

  • Runtime engine can't load vi with lvdatetimerec.ctl

    Hello everybody,
    i have trouble with TS 3.5 / LV 11.0
    I programmed a small vi that calculates the time difference between now and a time stamp. To pass the timestamp from Teststand i use a Control (lvdatetimerec.ctl) and the matching VIs to do the task.
    Unfortunally i can't load the vi into Teststand using the Runtime Engine. I get the message "Unable to load VI "xx.vi" with the Run-Time Engine. It is possible that the version of the VI or one of its subVIs is not the same as the ..."
    It is certainly the same and there is no problem until i include a constant or control of that type.
    Do anybody have an idea?
    Best regards
    Thomas
    Attachments:
    TimeDiff.vi ‏7 KB

    Try to recompile your vi hierarchy in LabVIEW (hold Ctrl and click Run), then save it, then try again in TestStand with LabVIEW runtime.
    Runtime engine does not support dynamic compiling, this vi may looks fine in LabVIEW, but TestStand will complain that it is broken. 
    Sergey Kolbunov
    CLA, CTD

  • App won't install with the prerequisite SAP Crystal Reports Runtime Engine

    On installing with the following prerequisite checked:
       SAP Crystal Reports Runtime Engine for .NET Framework 4.0
    .. received this error:
    Crystal Reports for .NET Framework 4.0\CRRuntime_32bit_13_0.msi
      has changed since it was initially published.
    Should I NOT use the prerequisite, and instead, use a merge module?

    I ran a program with the exact same name, 2 weeks ago, on my VS 2010 Dev machine:
    CRforVS_13_0.exe.  (284 Meg)
    Today, I followed your link, and downloaded the file with the same name, but different size:  (1.5 Meg).  I mean, a really major difference in size!
    Because creating and testing installation packages is very time consuming, I want to verify what you have stated so that I completely understand before I change what currently works, which is for the client machine to separately install the CR runtime, to what you're proposing in including a prerequisite to my install package.
    ->  I should run this latest exe.  It will add a prerequisite to the prerequisite list in Visual Studio 2010.  The installation of this prerequisite will work, as the earlier one did not.  And it will work for both 32- and 64-bit client machines.
    Therefore, I can eliminate the need for the client machine to install the CR run time separately.
    Please confirm, and then I will make the necessary changes, and do the install tests on client machines.
    (Also, FYI the merge module did not work for me on a 32-bit client machine.  So I removed it.)
    Thanks, Peg

  • Runtime engine huge issue

    Hi,
    I have a very big issue with the labview runtime engine.
    I use the print at completion mode for a VI and it seems the runtime engine doesn't support either the PNG compression property or the Scale frontpanel property. Which one I still need to find out.
    The executable says that arg 3 of my property node is not supported.
    Now, this is killing for my application as I can not use the application without this feature.
    If someone has an idea, please let me know. I'm under high time pressure and really have no other choice than to distribute a complete development setup if I can't solve the issue.
    Regards,
    Marcel

    Remember that PNG is a lossless bitmap image. There is some compression but it is a lossless compression so there isn't a setting for level of compression. I think that there are some differences in compression algorithms but the difference is minor and only useful if you have particular images that compress better than others. There is only 1 compression type which is zlib, but there are filters that can be applied before compression:
    Compression
    Filters
    PNG can be completely implemented with opensource free software and the specification is patent and royalty free. I don't know why the "compression type" needs to be specified for PNG.
    -Scott

  • Run labview exe in other way than runtime engine?

    Hi guys
    This might be stupid question, but can I run labview's *.exe in other way than in the runtime engine? In these days in have done *exe and installer with runtime engine and give it to the end-user. It does not matter how tiny ur code is, user have to install 40 conponents and then restart computer... How annoying. Is there eny other way? Can i use other programming languages some how?
    -AA-

    If the runtime is only one out of 40 components, it should not make a big difference for you.
    I always tell my users to download and install the runtime engine directly from NI. This needs to be done only once per PC and per runtime version, at which point you can distribute a small installer.
    There is also an idea to simplify all this. Please support it.
    (It is not reasonable to be able to build an executable with embedded runtime, that would make a LabVIEW 2009 executable 100+MB in size. (We had that back in LabVIEW 4.0, where each 20kb VI turned into a 3+MB executable, which was significant in the days of 1GB drives.)
    Message Edited by altenbach on 12-16-2009 11:42 AM
    LabVIEW Champion . Do more with less code and in less time .

  • LV 6.0 runtime engine not found with labview 6.1

    I recently upgraded to LabView 6.1.
    Now when I try to run an exe built under 6.02, I get an error that the 6.0 (or compatable) runtime engine could not be found.
    I have the developers version of labview 6.1 installed, and the labview runtime engine 6.1 installed.
    Do I need to install 6.0 runtime too? (in that case do I need 5.1 ruintime instaled too for exe's built a log time ago)?
    Shouldnt the 6.1 RTE be able to run older exe's?
    I could find no solution searching this web site.
    Thanks
    Larry Junek, Certified LabVIEW Developer

    Did you install 6.1 wheer 6.0 was?
    You may have lost the 6.0 RTE you did not realize you where using.
    Yes you need the version of RTE that matches the app.
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Runtime engine 8.6.1 on Labview 11

    Hello,
    I have upgraded labview 10 to Lv 11. A program that used to work on Lv 10 is giving problems now. It asks for runtime engine 8.6 ( usually gets stucked preparing the installation ). Once i cancel this process, it loads all the vi's, and it seems to work, but I can't be sure until all the devices are connected, and it can't be done until september. My question is, do i really need to install runtime engine 8.6 to make it work properly, or it can work without it? 
    And if I downgrade to Labview 10, will i solve this issue??
    Thanks in advance!!

    This is actually strange behavior because the runtime engine 8.6.1, if it is installed on the computer, should be accesible both from LV2011 and from LV2010.
    What do you mean by "downgrade to LabVIEW 2010? You may have multiple version of LabVIEW on the same computer. Did you uninstall LV2010 first? If you did, then it may happened that you uninstalled the runtime engine 8.6 at the same time.
    Do you really need or don't need the engine depends of your application. In any case, it should not be a problem to download the runtime engine from ni.com and install it. http://joule.ni.com/nidu/cds/view/p/id/1244/lang/en
    Sergey Kolbunov
    CLA, CTD

  • How do I determine if a VI is running in the runtime engine or LabView Development Environment?

    Is there a function or VI that I can call that will tell me if the program is running in the LabVIEW Runtime Engine or if it is running in the LabVIEW developement Environment?  I am using LabView 8.5.
    I have a menu item, File/Exit,  and I would like to call the Exit LabVIEW vi if running in the runtime engine when that item is selected.  However, in development, I don't want to shut down LabVIEW when I select that menu item.
    Maybe there is a more appropriate way to exit the program.  However, I am looking for something elegant.  I'm sure I could find some other way to accomplish the same thing, but I'm looking for a clean way to do it.
    Thanks

    Here is a small VI with this exact function.
    Attachments:
    Is EXE.vi ‏9 KB

  • Several question s about runtime Engine, application builder and labview player

    I am a little confused by all the options to distribute a program.
    Please help bij answering (one of) the following questions:
    1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
    2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
    3. What is the advantage of the labview player above the runtime Engine?
    All questions refer to the latest software versions of NI software
    Thanks in advance,
    Regards,
    Ferry

    ferry1979 wrote:
    1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
    Yes, the runtime engine contains all the stuff that is common to all LabVIEW applications. This is not any different than e.g. the Visual basic runtime (VBrun...) or dforrt.dll for Fortran.
    If you built the application, you can strip it a little bit by including the runtime with the installer and leaving out unneeded modules (see image from the 7.1 builder).
    The advantage of a seperate runtime engine is that applications are very small. The runtime needs to be installed only once. On any broadband connection, 33MB is peanuts. I distribute everything without runtine, but tell people to download and install the runtime directly from NI.
    (In LabVIEW 4, no runtime was needed, with the disadvantage that even the simplest program was multiple megabytes. Not an efficient solution).
    (Maybe in a few years LabVIEW will be so prevalent that the LabVIEW runtime will be part of a standard OS install ;
    2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
    No. See above.
    3. What is the advantage of the labview player above the runtime Engine?
    The two are quite different. The labview player is more a simple educational tool, because it lets users inspect the diagram. It is not designed for any serious application deployment.
    Message Edited by altenbach on 08-21-2005 10:05 AM
    LabVIEW Champion . Do more with less code and in less time .
    Attachments:
    runtime.png ‏24 KB

  • Installing LabView 8.2 runtime engine on Windows 7 64-bit

    We have a product built on LabView 8.2
    For a couple of years, we have been distributing this product on Windows 7 64-bit systems with no trouble at all.
    Today, we received a customer complaint indicating that the LabView 8.2 runtime engine cannot be installed on Windows 7 64-bit.
    Our verification team has confirmed this to be true.
    Interestingly, we have several Windows 7 64-bit computers with the LabView 8.2 runtime engine already installed.
    How is this possible?
    Has something changed in Windows that no longer allows the LabView 8.2 runtime engine?
    We are confused by the fact that this appears to be a new problem and the runtime engine did, at some point, install correctly on multiple Windows 7 64-bti computers.
    Any thoughts would be extremely appreciated.
    Attachments:
    lv_install_error.jpg ‏22 KB

    No, i dont think the 8.2 installer is corrupt, but it uses the Windows Installer service, which according the image has some problems. Maybe it recently updated? It's incompatible with that old installer so you need to downgrade it? It's corrupted and needs some fix?
    /Y
    LabVIEW 8.2 - 2014
    "Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
    G# - Free award winning reference based OOP for LV

  • Cannot Install LV Runtime Engine 7.1

    HI,
    Some of our users are having unusual installatiion problems while
    installing the LV runtime Engine 7.1.1 on win2k. Our users have
    installed another application recently and in that process the LV
    runtime engine was removed from their computer. So, they tried to
    install the runtime engine(downloaded it from NI website) again but couldn't becuase they keep getting
    the message that they are not logged in as administrator. We logged in
    as admnistrator and  tried installing the runtime engine again,
    but the error keeps occuring and is not allowing us to install. I
    searched the NI discussion forums and the Knowledge base to find
    answers but did not see any that match our problem. From some of the
    posts I suspect it has got something to do with Microsoft hotfixes and
    windows upgrades etc.
    If anyone else had seen this kind of behavior and has found a fix,
    please share it with us. Any help will be greatly appreciated.
    Thanks Ahead
    Deepak K

    Hello!
    This is an unusual problem.  I would first go through the add/remove
    programs through control panel.  Loate the "National Instruments
    Software" item and select "change".  See if any LabVIEW
    components are there and slect to remove them. This will completely remove the
    LabVIEW components.  Then attempt a reinstall of the runtime engine. 
    If this still causes problems, you may have deleted the old LabVIEW runtime
    engine in an unusual way which is interfering with later installs.  If this
    is the case, there are some other methods that we might be able to use to
    uninstall fragments of NI software.  Removing the software does not fix
    the problem post back and let us know!
    -thanks-
    Travis M
    LabVIEW R&D
    National Instruments

  • How do CVI7.0 runtime engine and TestStand3​.0 runtime engine work in a test system?

    I developed code modules from CVI 7.0, and test sequence from TestStand 3.0. Now I want to deploy all to a test system. Should I create distribution kits for CVI and TestStand, and install to a target PC? Do each kit include the RTE? How do the runtime engine work in a system?

    hp7550,
    I saw your post earlier entitled "what is a run-time engine?". It looks like this post is addressing the same issue.
    To answer your questions, it is not necessary to create a distribution kit for your CVI code modules. You can simply install the CVI Run-time Engine, which you can find if you go to www.ni.com and click on the Drivers and Updates link on the left-hand side.
    Then you will need to deploy your TestStand system using Tools >> Deploy TestStand System in the Sequence Editor. That tool will go out and gather all the CVI code modules your sequence calls - unless you are calling a DLL or something dynamically inside of a code module; in which case, you need to add that dynamically called DLL (or code module) to your TestStand workspace.
    To install the TestStand Run-time Engine, make sure the Install TestStand Engine option is checked on the Installer Options tab of the deployment utility. You can customize what gets installed with the engine by clicking on the Engine Options.
    For more information on deployment, see Chapter 14 of the TestStand Reference manual (Help >> Search the TestStand Bookshelf...).
    To answer your last question a run-time engine simply gives you access to the compiled code that corresponds to the functions you used from the CVI or TestStand libraries during development.
    I hope that helps.
    Best Regards,
    Matt P.
    Applications Engineer
    National Instruments

  • Unable to install LV Runtime Engine 7.1.1 with LabVIEW Professional 8.5.1

    I installed LabVIEW Professional Sys. for Windows (XP) 8.5 and then the 8.5.1 update. Somewhere in the original installation, LV Run-time Engine 7.1 was installed. But I need LV RTE 7.1.1. So I attempted to install RTE 7.1.1. Problem: The LV RTE installer aborts with the following message:
    "Installation aborted. Newer version already installed." 
    Why do I need 7.1.1? I must run some commercial LV executables that were compiled with LV 7.1.1 and will not run under 7.1.

    Well, I have to correct myself. MAX indicated that LV RTE 7.1 (not 7.1.1) was installed. My complied LV app indicated that 7.1.1 was not installed. I checked Windows Add New Programs and selected "National Instruments Software" I found that LV RTE 7.1.1 was, in fact, installed. So I selected LabVIEW Runtime Engine 7.1.1 and clicked Repair. After rebooting, My app works correctly. Again, MAX incorrectly displays LV RTE 7.1 (not 7.1.1). My app works, so I don't care.

  • How to Detect LV runtime engine prior to showing Remote panel in browser?

    I work on a web server that delivers remote panels embedded in browser windows.  On new machines, the labview runtime engine needs to be downloaded and installed.
    Currently, when a new user 'hits' the remote panel, the user is prompted and then downloads the component.  However, the user experiences some errors that can be confusing.  The first time, the remote panel is not embedded properly and the user must go 'BACK' then reload the page.
    We would like to check and detect whether the LVRT engine is installed prior to posting a webpage that contains a remote panel.
    What is the best way to detect whether the LVRT engine is installed on a remote computer?
    Jim West

    Jim West wrote:
    My brain is swimming... I haven't had enough coffee this morning... There is a chicken and egg issue.  As soon as I post the page, the client knows it needs to install the Labview runtime engine.  However, my Labview process has already attempted to place the remote panel in the page.   I get an error.  I'll admit that I haven't delved into my software since there are two spawned processes involved.  One process responds to the request and another lingers in memory running the remote panel until the user finishes. 
    From my perspective my lingering process should be sufficient to get the remote panel displayed when the RTE in finished installing but here is the catch.  Installing the RTE requires a reboot, therefore the server process would need to linger in memory a long time and then would need to recoginize that a user from the same computer and login is looking for the page.  Not really the way to go.  I can't have a process on the server lingering waiting for a user to reboot his computer and then do something when they start running again.  That process needs to die right away if the RTE is not available.
    Jim
    Would it be possible for this lingering process to check to see if the web server read has timed out?  The default is 60 seconds, and you can change it by going to Tools>>Options>>Web Server: Configuration.
    Trey B
    Applications Engineering
    National Instruments

  • Runtime engine files 8.2

    Hi,
    Since most users of my written program are users with "restricted right" acounts under Windows XP I copied the Runtime engine files of LV7.11 manualy by copying the
    "Program Files\National Instruments\LabVIEW 7.1\Shared\LabVIEW Run-Time\7.1" files to the harddisk and run a build executable from that directory. Since this application looks in its own directory for support-files this worked fine for LV7.1.
    Last week I converted my program to the LV8.2 version. When I tried to copy the RTE8.2 file in the same way as I did before, the program would start-up. It asks for a NIINI32.DLL file. When I include this file it does not return any errors, but the program doesn't start. Can anyone tell me whether their is a different way to run a exe-file build by LV-application builder by copying files manual in stead of running the RTE-installer?
    Thanks in advance,

    I know that NI did the run time engine to minimize space when installing multiple application. But i'm agree with you, we should have another way to build executable without the runtime engine. Some people dont know what it the runtime engine and uninstall it. afther that they just cant use the program anymore. The other reason, it that a VI use just some Kbyte and the run time engine that include almost everything, need some Mbyte.
    If somebody know, please tell us......
    Benoit Séguin
    Software Designer

Maybe you are looking for