Mac Standalone LabVIEW App - Include Visa & LabvIEW Run-time

Hello All,
I've used LabVIEW for over a decade but only for Windows, just getting into LabVIEW for mac, so please pardon any ignorant questions.
I am developing a very simple project to be deployed stand-alone that needs LV Run-time and NI Visa. My project uses a simple USB-Serial device that I talk to using Visa. I used this link to package LabVIEW run-time with my app. I think I need to package NI Visa drivers as well. I am not sure how to do that. Anybody have any experience packaging drivers with stand alone apps for LabVIEW in mac? Thanks for your help.
Kudos always welcome for helpful posts
Solved!
Go to Solution.

Thanks, Silvia. This is a limitation and there are more and more developers on Mac OS. Can you provide answers for couple questions:
Any plans to include Installer App like how we have for Windows OS?
If [1] is not anytime soon, can NI provide a KB to deploy a stand-alone Mac app packaging drivers? I think this will be very valuable.
Kudos always welcome for helpful posts

Similar Messages

Install labview 6.1 (or compatible) run-time engine with labview 2011

I have installed a trial period version of Labveiw 2011 in order to check for possible upgrade issues I may have if I decide to upgrade from labveiw 6.1. Well, needless to say there have been alot. That is as expected since I have not updated labview in many years. I am still not under any pressure to update; however, I would like to in order to get support and make sure I do not have any compatibility issues with new equipment purchases. I have been able to resolve most of my compatibility issues with simple code fixes and such. However, twice now I have run into an error when launching labview executeables compiled by two different equipment manufacturers. The equipment I am using is not even old...maybe a year or so. When I launch the labview executables to control this equipment on a PC that has the trial period labview 2011 installed, I get an error message stating something like " This requires a Labview 6.1 (or compatible) run time engine." I have tried to download and install the 6.1 labivew engine but I can't install this engine on a PC which has labview 2011 installed. Can someone explain how I am to run these executables under labview 2011. I can't imagine these executables were developed using 6.1 since this equipment is not even a year old now.
Solved!
Go to Solution.

Im not for sure I am on the same page with you here. Im not trying to develop any code myself. I have some labview executables that came with hardware we purchased in order to control it. We used to have labview 6.1 installed; so everything was working ok. But now that I have installed 2011, I get an error message when trying to run these executables. The error message states that this executable requires a labview 6.1 or compatible run-time engine. I have seen this error on both XP and Windows 7 machines. I did not develop the executable, it was developed by the hardware manufacturer. But since this hardware is only about 1 year old, I an assuming they used a newer version of Labview to develop this code. Certianly newer than 6.1.
So I guess my question is..is there a way for me to get this executable to work on a PC that has labview 2011 installed. I have tried to install a labview 6.1 run time engine but it will not install. Any other options?

Problem with Assemble Test VIs for Run-Time Distribution

I get an error that a file is already in memory and that I will have to remove it before I can build the application. The file in question is Get File System Seperator.vi. It lives in vi.lib\Utility\sysinfo.llb. If it is not a stock vi from national and was placed there by some other add on tools (perhaps an OpenG toolkit), how can I disable it? Labview itself will not boot without this sysinfo.llb.
I am using TestStand Engine 2.01 on the XP system and 2.01f1 on win2000 with the same results. I am not using numerical limits so the fix (patch) for multiple numerical limits does not seem to be needed.

Hi Paul,
In the description of your problem you state that "I will have to remove it before I can build the application". I was wondering if you could elaborate on the scenario you are describing because this is a little bit confusing to me as it is. The "Assemble Test VIs for Run-Time Distribution" tool in the Sequence Editor does not involve "building an application" as part of the process of using it. When you select the menu option for this tool, a TestStand sequence is invoked that has a few LV VI steps in it which perform the VI Assembly process, with no application building involved (just searching through sequences for top-level vis, their sub-vis, and copying them all into a directory you choose). I hope this describes what it is I'm not understanding about your statement, but to explain why it is that I feel this is important is in order to reproduce the problem I need to know exactly what it is you are doing at the time of encountering the problem. To go over a common set of issues people encounter when they use this tool, I would like to see if you have tried the following:
1) Have you checked to make sure that the LabVIEW Standard Prototype Adapter is configured to use the LabVIEW development environment as its Run-Time Server before running the tool. It will not work if the adapter is set to use TestStand LVRTS or TestStandGUILVRTS. The assembly tool requires features of the full LV IDE to perform the functions it carries out, and you will get an error if the adapter is configured improperly. To check this out, go to Configure >> Adapters..., select the LV Adapter in the listbox, then click the Configure button. In the second dialog, change the run-time server option to "LabVIEW".
2) Are you actually trying to build the Assemble Test VIs for Runtime Distribution tool into an application? (This is not an intended use of the tool's VIs).
3) Before running the assembly tool, have you tried using the Sequence Editor's File >> Unload All Modules option?
Let me know if you have tried the above things or if you are doing any of the "unintended" things with the tool so I can get a better grasp of when it is you are seeing the problem. Again, the goal would be for us to reproduce it.
Jason F.
Applications Engineer
National Instruments
www.ni.com/ask

Labview opens all VIS in Run mode

LV2013 PDS is opening all VIs in Run Mode. This is a global problem, not specific to one or a specific number of VIs.
If I create a new VI, save it, close it and re-open it, it's in Run Mode, not Edit mode. Nothing is set to Run When Opened, nothing is set to be locked without a password.
It's only on this installation; if I take my code to another machine, there's no issue.
I have deleted the labview.INI file, but the behavior repeats itself.
Any ideas?

Jed_Davidow wrote:
SCC is not configured; I use perforce, but it's not configued to use it or to treat read-only as locked. I have also checked out all the filed ahead of time with P4, so LV never sees them locked. The folders themselves are not read-only.
Also, I have created VIs outside of my P4 folder, and I have the same trouble.
Example:
Launch LV: Create a blank VI (comes up in Edit mode).
Save to Desktop (not within P4 control) as test.VI
Close
Open test.VI ---> It's in Run Mode
I have never seen this happen before.
Neither have I
I'll assume a reboot was attempted and did not change anything. I would attempt a repair of LabVIEW from the control panel and another restart.
Jeff

Error 1073 when building LabVIEW app which calls LabVIEW dll

I am trying to use application builder to build an application that calls a dll created in LabVIEW. I get an error referencing a vi within the dll (Parse Stored String(multibyte).vi) saying that "This property is writable or this method is available only when the VI is in edit mode." The only option is to Continue which cancels the build. I had sucessfully built this application prior to including vis that call the dll and the program runs fine in the development environment.
Do you have any idea what is causing this and what I cam do about it?

I have found a temporary workaround in which I created a dummy dll that removed all functionality from exported vis but had the same name and function signatures. I then built the application using this dummy dll. Once complete, I replaced the dummy dll with the real dll.
This is not a satisfactory work around because we have to build and maintain two dlls. Also, I'm not sure we can do the same trick when creating the installer with application builder. So, I'd still appreciate any help you can give.

Include actionscript at run time

I know I can include actionscript from a file using #include
"myScript.as", for example. But this happens at publish time, so if
I make a change to myScript.as, I still need to re-publish the
flash file to get the changes to take effect. Is there a way to
include the actionscript at run time, so I can edit the myScript.as
file and have the changes take effect without having to re-publish
the flash? Thanks for any help!
Bob

no.

Can you build an Labview app on windows and run it on the Linux Runtime Engine?

Our developers work on windows workstations but we would like to convert our test stands to linux. Can we run the apps they develop on Linux with the Linux Runtime?

No. VIs developed on Windows will run in the LabVIEW Linux development (assuming no Windows specific functions like ActiveX and DLL calls) but in order to run a built application on Linux you will need to rebuild them with the Linux application builder.

Labview- Excel template path at run time(to build .exe file)

I am new to labview and I have one doubt in it. I have one main.vi file where I use local drive path to invoke one excel template, Now I have to convert this .vi file in to .exe file. So now I cannot give the local drive path to invoke the template because the client will not have the same path as mine. So what I did is I created one project. Under this project I created one virtual folder which contains the excel templates. My doubt is how to give path for the excel-template in main.vi file. Please let me know if you guys know. thanks in advance.
Thanks & Regards
saamy

Hi again.
Here is a strategy I always use when I create a project:
Create a folder named for example "My project". In this folder I create new folders called "Bin", "Doc", "Data" and "Img". I put my main Vi in the "Bin" folder and for example the excel template in the "Data" folder.
I then create a project in LabVIEW and I add the "My project" folder into this project as an autopopulating folder. This means if I add a file in i.e the "Bin" folder it will automatically come up in the project.
When I create my Main.vi and want to use the excel template, I simply add a folder path constant to the "Data" folder on my computer. I don't care about the LabVIEW project file.
After I'm done programming and I'm happy with the result I need to prepare the VI for being converted into an .exe file. This means I have to remove all the path constants and add the application folder node mentioned above. I have to know what folder hiearchy I want the installer to create. In this example we can use the folder where the .exe file will be and then a sub-folder named "Data" where the excel template will be. The path will be like "the_folder_where_the_exe_is\data\exceltemplate.xlsx."
When I create the .exe file I can add which files that will always be included. Here I add the Data folder containing the excel template. After that I create an installer where I add the folder where the exe file is, which I just created.
Regards,
Even
Certified LabVIEW Associate Developer
Automated Test Developer
Topro AS
Norway

LabVIEW 8.6 Tree Control Run-time Shortcut Menu in Executable

Has anybody else noticed that the options Open/Close All Items have disappeared from the shortcut runtime menu of a tree control when the application is built? I recently upgraded from 8.5 and those two options have disappeared from all of the tree controls in my application. I tried customizing the menu and adding the options to the menu. Now they appear but on some controls they are disabled and on the others where they don't appear disabled, they simply don't work. Everything works great in the development environment.
I built an executable of one of the LabVIEW tree control examples and the same thing happens. Is this a bug that has already been reported somewhere?
Thanks,
Erin
Attachments:
TestTree.zip ‏79 KB

Dear Erin,
I have been able to reproduce the issues you are reporting. I have opened a Corrective Action Request so our R&D Engineers can fix this issue in future versions of LabView. Thank you very much for your feedback. It will be of great help to enhance National Instruments products.
Greetings,
David
National Instruments
Message Edited by Support on 01-29-2009 11:54 AM

Labview Executable with VISA functions in Run Time Engine

Hi Everybody
I designed a gui to communicate using VISA GPIB. I created an executable for the gui. I also installed LabView Run Time Engine on the desired machine. I recieved couple of errors, for which I copied the files visa32.dll, NIVISV32.dll and serpdrv to the folder with the executable.
I recieved the following error, ' Initialization of NIVISV32.dll failed. The process interminating abnormally.'
Are there any drivers I should install in addition to the Run Time Engine? If so, where can I find these drivers?
Thank you
Jackie

I installed NI-VISA with similar version as my development installation, and LV runtime engine. Labview still crashed.
I noticed certain library functions in full labview that is not present in the NI-VISA + LV run time directory, such as _visa.llb etc.
Do I need to copy these additional library functions too? Will Run Time Engine read these library functions?

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

Can I run two separate versions of the LabVIEW Run-Time Engine on one PC?

Hello, I am curious if anyone knew if it is possibly to install and use two separate versions of the LabVIEW Run-Time Engine on one PC? I currently have the 2009 Run-Time Engine installed on one machine and wanted to install the 2011 Run-Time Engine as well. I know that you can run two separate versions of the LabVIEW program on one machine, but what about the Run-Time Engine?
Thanks!
Solved!
Go to Solution.

I'm guessing this is a bug that NI needs to fix. I see no reason you shouldn't be able to install the run-time engine of an older version. I'd be interesed in if it allows you to install the older development environment, which also includes the older run-time engine. There are some command line switches for NI installers as mentioned here:
http://digital.ni.com/public.nsf/allkb/C361087EE9F20810862577850073128E
I wonder if there is a force install option.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Upgraded from LabVIEW 8 to 2013 and now VI asks to find the installation package for Run-Time Engine 7.0

I recently installed LabVIEW 2013 on a computer (running Windows XP 32-bit). The machine also has LabVIEW 8 installed, which is what I was using prior to upgrading. I opened a VI that was created in LV8 and then saved it and all its subVIs in LV2013. Now when I open the VI in LV2013 and try to run it, a window pops up asking me to find the "lvruntimeeng.msi" installation package for LabVIEW Run-Time Engine 7.0. If I cancel that dialog box and the subsequent message stating that the installion files were not found, the VI appears (at least from intial inspection) to run normally.
I closed LabVIEW, downloaded Run-Time Engine 7.0 from the NI website, and tried to install it, but I received a message saying that it is already installed (as I had suspected). How can I determine what part of the VI and/or its subVIs is trying to make use of Run-Time Engine 7.0? Alternatively, how can I get LabVIEW to instead use the Run-Time Engine 2013 that was installed when I upgraded to LabVIEW 2013?
Solved!
Go to Solution.

Bob_Schor wrote:
Are you running your VI from a Project? If so, you can look at Dependencies and get an idea what "dependent" VIs you might have. There may be "something old" in your LabVIEW 8 code that has been superceded in 2013, but still "hangs around" -- if you can identify it, you can probably replace it with its "more modern" equivalent.
If you do not have the VI in a Project, you can simply open LabVIEW, create a new blank project, and add your top level VI to it. If all of your relevant VIs are in a single folder, add the entire folder. Now look in Dependencies.
BS
Yes I am running the VI from within a LV Project. After some more searching in the NI Knowledgebase I was able to fix the problem by using the following procedure:
1. Use the Measurement and Automation Explorer to uninstall Run-Time Engine 7.0
2. Restart the PC
3. Open the project, close the project choosing to "save all"
4. Restart the PC
5. Re-install Run-Time Engine 7.0 using a file downloaded from ni.com
6. Restart the PC
7. Open the project, close the project choosing to "save all"
8. Open the project and run the VI. No more messages about LabVIEW trying to find Run-Time Engine 7.0.

LabVIEW 8.2 -- "unable to locate LabView run-time" error message

I am trying to run a LabVIEW version 8 exe file and keep getting the
"Unable to locate" error. I downloaded LabVIEW_8.2_Runtime_Engine.exe
from the NI website and installed the entire contents of the
distribution. After getting the error, I have tried uninstalling and
reinstalling several times, with the same result.
Is there some way I can troubleshoot this? Is there a configuration
file or a registry entry I can check to see where LabVIEW is looking
for the run-time?

Michael,
As Dennis said you need to make sure the version of the Runtime Engine matches the version of LabVIEW the executable was created with.
You can find different versions of the Runtime Engine on our webpage here.
Regards,
Simon H
Applications Engineer
National Instruments

Custom Run-Time Menu error when named "FileMenu.rtm"

Discovered an interesting "feature" (error?) in LabVIEW 2009 when using custom run-time file menus.
If you create a custom run-time menu (.rtm) and name it "FileMenu.rtm" the menu will not function correctly in executable format.
In my LabVIEW Project, any VIs which called this custom file menu worked correctly in the project, but when I built an executable, the VIs defaulted to the default file menu. This was not due to a corrupted .rtm file or the file not being included in the executable. Instead after extensive debugging I determined that the name "FileMenu.rtm" is somehow reserved in LabVIEW and any executables that are built have the custom run-time menu overwritten by the default. The tricky part of this error is that it goes unnoticed while the code is still in development and only presents itself after being built into an executable.
Simply changing the name of the file fixed the executable run-time menu.

Chris,
Thanks for trying it out. It seems that my forum post may have been a bit rushed.
I tried to duplicate the problem in a new project from scratch and similarly was unable to reproduce it. I will try more soon, and in doing so perhaps reveal the true underlying problem. I would post the original code but it is proprietary.
I was running LabVIEW 2009 and Windows XP when the problem first presented itself. I updated to LabVIEW 2009 SP1 as part of my debugging and the problem still presented itself.
V/R,
~David

Mac Standalone LabVIEW App - Include Visa & LabvIEW Run-time

Similar Messages

Maybe you are looking for