Adding NI VISA RunTime to a LabVIEW app on Mac using PackageMaker

I would like to create a Mac installer that installs NI VISA Run-time in addition to my application. Actually, it would also include a 3rd party USB/UART bridge driver. I'm trying to figure out how to get the NI VISA RT and the bridge driver included in my installer package. I'm close--I can create a package that throws up 3 installer wizards. The problem is that both the NI VISA RT installer and the bridge driver installer wizards end with "Reboot" buttons. If a user clicks either of those reboot button too early, not everything will be installed.
Has anyone come up against this kind of issue?
Thanks

Yup. Install VISA after your program. If you set your own installer to NOT require a reboot, then you'll only have the requirement after VISA installs. This is how I did it I think.
Either that or I took out part of the VISA installer and re-incorporated it into my own installer. I'm not in the office now so I can't check.
I so wish NI would offer an installer package for LV on the Mac. Having to do this stuff manually is really not worthy of a $$$ product.
Shane.
Ps i should read better. I see you have two packages requiring a reboot. I think you can extract at least part of the installer package and re-incorporate it into your own installer. I haven't done an installer on Mac for a while so my memory may be rusty.
Message Edited by Intaris on 11-11-2009 04:22 PM
Say hello to my little friend.
RFC 2323 FHE-Compliant

Similar Messages

Running a LabVIEW app on a MAC yosemite without LabVIEW

Hello all !
When you compile LabVIEW codes on a Mac, you create a ".app" instead of a ".exe". I would like to run my ".app" on another Mac running with Yosemite (OSX 10.10) and without LabVIEW on it.
I downloaded the latest RunTime Engine for LabVIEW on that Mac in order to make the application run but it does not seem to work ...
Has anyone already done such a thing and would have a method to follow ? :-)
Thank you in advance !
Solved!
Go to Solution.

gvanhoeke wrote:
When you compile LabVIEW codes on a Mac....
LabVIEW VIs are always compiled. You are probably talking about building a standalone executable.
gvanhoeke wrote:
I downloaded the latest RunTime Engine for LabVIEW on that Mac in order to make the application run but it does not seem to work
Instead of the "latest", you need the runtime engine that matches the LabVIEW version used to develop the program.
(Sorry, I have no direct experience with Macs)
LabVIEW Champion . Do more with less code and in less time .

Do I need "NI-VISA Runtime 5.1" visa in the install package?

I have applications that use the serial port communications. The install package has grown from 109mb with v8.0 to 150mb with v2011. Do I have to install the NI-VISA runtime 5.1 if I am only using the serial communications?
Solved!
Go to Solution.

Yes.

Unable to load LabVIEW VI into TestStand using LV Run Time only

I'm unable to load some of my VIs into TestStand from LabVIEW. I am using:
TestStand 4.2.1
LabVIEW 2010
I have the appropriate patches installed for both TestStand and LabVIEW, and I still get the error.
Attached is a message that I get when I hover over the "!" to explain my error. The VI has the "Simple Error Handler.vi" as part of the build, and when I eliminate this VI from my VI, TestStand then loads correctly.
Thanks,
Eric
Solved!
Go to Solution.
Attachments:
TestStand_LoadError_Hover.png ‏16 KB

This fixed my issue as well. Thank you for posting this. I have repaired LabVIEW 2010 sp1, LabVIEW FPGA, LabVIEW RT, DAQmx, and VISA 5.0. These are not small programs to do repairs on. Even after doing all of these repairs I still had issues with just labview coming up.
Just by clicking on my lv shortcut to run the labview.exe I would get a loading screen for gws_int.vi This was before opening any projects or VI's. Labview was having many issues. Once the loading vi screen went away the standard labview 2010 startup page was present. But this page was dysfunctional. For example if you clicked tools and then options it would just totally crash LabVIEW, no error message or warning.
Many people are suggesting to mass compile to fix this, but that is not an option. If you went to tools>advance>mass compile the same loading vi screen would come up (pic A), but then the mass compile program would have a broken arrow (pic b) I included a image to show people this.
The error list will always pop up, but there are no errors.
I called NI tech support and they suggested that I repair all of my programs starting with the largest programs first. During the repairs I found this forum. I have over 30 different NI modules installed on this machine, I would have been at this for the next two days.
Thank you very much for this.
A good question is why didn't the repairs of these large programs find this, and would any repair of any module have fixed this?
Attachments:
b.png ‏116 KB
a.png ‏46 KB

Labview 8 Application Builder and VISA Runtime Engine

Hi,
I am using Labview 8 Application Builder and everything is working fine except for 1 small thing. My program makes use of some of the VISA functions and when I build the application I'm having to include the VISA Runtime Engine Installer as a separate item on the CD to make the .exe file work.
What I would ideally like is for people who want to use the application to run the installer and that all necessary components (including the VISA Runtime Engine) are also installed in the one installation. At the moment they're having to do 2 installations and I would like to streamline this.
Is this possible?
Ken

Hi,
this How-To explains about making those selections and including the different drivers :
http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/add_installers_to_build/
and this tutorial covers the screenshots a little more step by step.
http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

Runtime Error building Installer with NI-VISA Runtime

Greetings, I'm getting this error whenever I check the "NI-VISA Runtime" option in the installer app builder.
Everything builds fine when I check only the Runtime Engine. Shown below is what causes the RUNTIME ERROR and closes Labview Unexpectedly.
Any help you could provide would be very much appreciated.
Regards,
JD

Hi JD,
This is a relatively common error with the Application Builder that can happen for several different reasons, namely registry keys pointing to installations that no longer exist. The easiest way to identify the problem is to get detailed information about the installer build. Here are directions:
LabVIEW has the
ability to create a very detailed log of the events that occur when
building an application or installer. To enable this feature, open up
the LabVIEW.ini file and copy "CDK.EnableLog=true" to the bottom
of the file. Save the changes and close the ini file. The LabVIEW.ini
file is usually located in C:\Program Files\National
Instruments\LabVIEW X.X
Enabling this feature will create a log file in the %temp% directory of your computer (%...% means a computer variable) .
To
find out where this temp directory is located, go to Start>>Run.
Type in "cmd". Then type "set". This will return all of your computer's
variable names.
Look for TEMP in the list of variable names. You should see something like "TEMP=C:\DOCUME~1\user\LOCALS~1\Temp".
Navigate to this directory using Windows Explorer.
You
should see a file named "Name.log" where "name" is the name of your
build specification. For example, you might see "My Installer.log" if
the name of your build specification is "My Installer".
This will give you a more detailed log of the attempted build and, if I'm correct about why this particular build failed, show you which installer is expected at that registry. If the registry points to a directory without the necessary installer (i.e. VISA), simply delete the registry and allow the App Builder to prompt you to to point to the correct location.
Michael K.
| Michael K | Project Manager | LabVIEW R&D | National Instruments |

Labview app wont run on fresh reboot unless MAX is started.

I am a Labview NOOB. I am the only IT here and started about a year ago and basically got thrown into the "labview" with 0 labview experience.I had to take an xp machine and turn it into a win 7 machine.
Here's some specs: labview 8.2 32bit running on windows 7 32 bit with IO libraries 16. Driving a gpip to usb 34970A data aquisition unit and a temperature compensation oven. Heres the situation. When i restart the PC my "temp_comp.exe"(application that labview consultant wrote) will not run. I get a few errors One as soon as i start the app: "oven Communication Fault" and one when i try to run the oven with shortened testing times and temp:
error 107387202 occurred at visa close in HP34970A close.vi-
34970A_read.vi>measure oven temp.vi->wait for oven to reach temp vi-
a comp loop.vi - a test loop sequence.vi>main temp comp.vi
Possible reasons VISA: hex 0xbfff009e a code library required by VISA could not be located or loaded.
I have reformatted a machine with xp and was able to get this running fine.
So here's the kicker. If i open up MAX and expand the devices and interfaces tree the program works fine and dandy. no errors. I have ran 3 batches in the oven over night with no problems. I figured i would just do an easy work around and have the max program start during startup but i have to manually expand the devices and interfaces tree before it will work.
Any ideas will be super helpfull Cheers!
Solved!
Go to Solution.

It never ceases to amaze me what managers think is possible. It would be difficult for even an experienced LabVIEW programmer to port a LabVIEW app from XP to Windows 7 using a version of LabVIEW not supported on the operating system. Tell them you'll see them in a few months.
I ran into an issue once where a vendor's Win7 dll had different default settings than the priginal and we couldn't figure out why we couldn't communicate with the I/O card. Seems that they inverted the address bits as default. Of course, there was no documantation on the change - unless you count the source code itself.
It was an intentional change which would make sense if you were someone who bought a new card and never used the old dll before. But guess what? The card was already obsolte/unsupported, so there AREN'T GOING TO BE ANY NEW USERS!
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

NI VISA Runtime engine

When "Building" a LabVIEW program containing NI-VISA sub VI's (e.g. to communicate with USB), I have had problems getting the "Built code" to find my NI VISA devices, even though the NI VISA USB Drivers are correctly installed on the "target machine".
(The "built" code WILL run if the target machine has a LabVIEW installation on it, including NI VISA)
So - will the NI VISA runtime engine be automatically included in the "Build" (Because of the NI VISA sub VI's), or do I have to specify this myself - And how?
Thanks. Peter.
Solved!
Go to Solution.

You specify installing the NI VISA Runtime Engine when you build and installer for your built executable. Look on the Additional Installers tab of the Installer Properties Dialog Box. The NI VISA Runtime Engine should be selected automatically but if it's not you can uncheck the Automatically select recomended installers checkbox and select any other installers you want to include in your install.
If you're not using an installer then no runtime engines are installed and you'll have to do that manually on each machine you copy the executable to.
This all assumes LabVIEW 2013. The selection process is slightly different in earlier versions but all the options are still available.
Kelly Bersch
Certified LabVIEW Developer
Kudos are always welcome

NI-VISA Runtime 4.3 Additional Installer problem

Hello,
I am using Project Explorer and I'm trying to include NI-VISA Runtime 4.3, but during the build I get a message that says:
Locate the "Activate" distribution. LabVIEW needs to copy a component installed or updated by the distribution to continue building the installer.
I don't know what the "Activate" distribution is or where to find it! Please help.
See attachments.
Message Edited by Sidd on 10-09-2008 02:02 PM
Solved!
Go to Solution.
Attachments:
additional_installers.JPG ‏87 KB
activate.jpg ‏25 KB

Thanks for the suggestion but I solved the problem a different way. I downloaded NI-VISA Run-time 4.3 from http://joule.ni.com/nidu/cds/view/p/id/989/lang/en then extracted it to a folder. I pointed Project Explorer to this folder and it found it properly.
I was then able to build the project successfully.
Sidd

Can Labview apps be ported to CVI/Labwindows?

I use Labview as an interface to my devices but I am not an expert
programmer in C/Labwindows. I would like to know if Labview-apps
("graphical" code) can be migrated to C/C++ code on a Labwindows
environment.
Can I implement and "export" a subVI to Labwindows?
Thanks

jon wrote:
I use Labview as an interface to my devices but I am not an expert
programmer in C/Labwindows. I would like to know if Labview-apps
("graphical" code) can be migrated to C/C++ code on a Labwindows
environment.
Can I implement and "export" a subVI to Labwindows?
Thanks
The
only thing you can do is using the LabVIEW application builder to turn
your VI(s) into a DLL and call that from LabWindows CVI. There is no
way currently that LabVIEW can convert its VIs into C code for
LabWindows CVI or other compilers targetting Desktop OSes. The only
LabVIEW that can do something in this direction is LabVIEW Embedded
Development Module but that costs lots of $$$$$ and targets 32bit
embedded plattforms for embedded applications (eg. no local UI,
specific LabVIEW embedded environment and interface libraries, and a
few other not so trivial details).
Rolf Kalbermatter
Message Edited by rolfk on 11-22-2006 10:47 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Code signing labview.app in OsX

I'm trying to sign a built labview.app in OsX and get the error "unsealed contents present in the bundle root".
I believe this is due to locating "AppContents_x64.llb" outside of the "Contents" folder.
From the apple website,since Mavericks :
..." In addition, there may not be any content in the top level of a bundle. In other words, if a bundle has a Contents or Versions directory at its top level, there may be no other files or directories alongside them. The one exception is that alongside Versions, there may be symlinks to files in Versions/Current."...
https://developer.apple.com/library/mac/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919...
One of our programmers sniffed the lvruntime framework; the runtime will load the AppContents.llb if it is reolcated to the Contents/Resources folder. So, the default location seems incorrect, and the project explorer does not seem to have an option to changed the destination. Does anyone know of a workaround (other than copying the file)?

Correction_
The AppContents_x64.llb is NOT found when placed into the Resources folder. On a clean system ( no LV development environment), the app wil run only when that .llb file is in its original location- which invaildates the codesign. So I'm still unable to sign my app.
Any suggestions?
Thanks
Kevin M

Looking for a VISA Runtime Merge Module

I am building an installer with install shield. I have been able to find a LabVIEW Runtime Merge Module and that seems to work great. But, I need one for the VISA RunTime.

You can download the VISA RunTime Engine from NI's website ( click here ) and have your installer also install the RunTime engine. This link will take you to an NI Knowledge Base which describes how to do this.
J.R. Allen

Which is better for usb camera between VISA and imaqdx in labview 2010?

i have done a program for usb camera to acquire images with imaqdx.
now i want to know which is better between VISA and imaqdx in labview 2010?
i didn't study visa before
thans for help.

VISA is primarily used to communicate with instruments via GPIB/TCP-IP/Serial/USB. In order to use easily VISA with an instrument over USB the instrument must adhere to the USBTMC spec. A camera is not likely to have this. Otherwise you have to use USB RAW, and that requires detailed knowledge of the data that is transmitted by the instrument. Manufacturers rarely give this information out. Normally they will provide a DLL to communicate with the instrument.
Thus, in your case, VISA is not going to be an appropriate API to use for a USB camera.
Out of curiosity, what prompted this question?

Multiple concurrent LabVIEW apps sharing card resources in one cDAQ chassis

I'm looking for help, reallly a yes/no answer and/or pointers/suggestions as to the feasability of as well as how to have multiple LabVIEW apps run concurrently and share resources (cards) from a single cDAQ module. The background is that I have an array identical of LabVIEW test systems that are used to perform testing in environmental chambers, and there are many different standardized tests that they run, ideally some (that use different resources) at the same time. The problem is that different tests use different subsets of the cDAQ resouces, but the goal is to be able to run multiple tests/apps (for example, for multiple pieces of equipment in the environmental chamber) at the same time). Can LabVIEW apps be structured such that they can share a module in a cDAQ chassis? For example, if I have 20 thermocouples connected to the chassis that can all be scanned/read at the same rate (around once/second), can one app read some of them and another app read others of them virtually concurrently, perhaps by sharing a common task?
Any advice as to how something like this could/should be done would be appreciated.
Thanks.

I would also make a separate application to handle the DAQ stuff. Depending on what you need, I would likely use a combination of TCP/IP, UDP, and shared variables to send commands, stream data, and get latest data.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

How to run Labview apps in tablet with android os

How to run Labview application in tablet with android operating system?
Can we use Labview mobile module or we must use google play data dashboard for labVIEW? how to install it in PC?
Solved!
Go to Solution.

If you had looked at data dashboard and some of the other links on Android, you would see that you cannot run a LabVIEW app on Android. Nor can you use a serial port. With Data Dashboard, you have a pc running LabVIEW and it publishes to network shared variables. Data Dashboard on the Android allows you to view those variables.

Adding NI VISA RunTime to a LabVIEW app on Mac using PackageMaker

Similar Messages

Maybe you are looking for