labview 8.0 to labview 7.0
Can somebody save the below VIs in LV 8.0 for LV 7.0, please... ?!
Find Power Interrupt Time.vi:
http://forums.ni.com/attachments/ni/170/335061/1/Find Power Interrupt Time.vi
Remove Element(s) from Array.vi:
http://forums.ni.com/attachments/ni/170/335061/2/Remove Element(s) from Array.vi
Hi Partha,Here are the VIs in LV7.0.Have a nice day
Find Power Interrupt Time.vi:
http://forums.ni.com/attachments/ni/170/335070/1/Find Power Interrupt Time.vi
Remove Element(s) from Array.vi:
http://forums.ni.com/attachments/ni/170/335070/2/Remove Element(s) from Array.vi
...Installing the 8.2.1 run time engine on a system with LabVIEW 8.2 installed
Note: This is a <a href="http://forums.lavag.org/index.php?showtopic=7942" target="_blank">cross-post to LAVA</a>. If I have a system with LabVIEW 8.2 installed and I upgrade only the
RTE to 8.2.1 (leaving LabVIEW 8.2 installed) will I run into any
problems?- Will applications that I build in LabVIEW 8.2 still run correctly?
RTE will applications that I build in 8.2 require? (I'm presuming that
the 8.2.1 RTE upgrade will not touch the lvapp.lib stub used by the app
builder and that apps built in 8.2 will run in the 8.2 RTE)
Here is what I (think I) know: - The
8.2.1 run time engine (RTE) is an upgrade to the 8.2 RTE, meaning that
the 8.2 and 8.2.1 RTEs cannot be installed at the same time.
built using LabVIEW 8.2 will run in the 8.2.1 RTE, however apps built
using LabVIEW 8.2.1 require the 8.2.1 RTE and will not run in the 8.2
Has anyone attempted this?Thanks,
Anything that we product that is X.X.X is mostly a bug fix release, and so you are correct in that it installs over X.X (your example 8.2.1 installs over 8.2 and so it is not possible to have them installed at the same time separately). It also means that there is a good chance that you can interchange VIs and projects without a problem, but it is not guaranteed.
This means that applications built in LV 8.2 can run using 8.2.1 RTE, and LV 8.2.1 applications can probably run with 8.2 RTE, but it is highly recommended to have the same ve...Does Labview run-time engine 6.0 application created by Windows NT/2000 can install & run on UNIX
LabVIEW exe created in Windows and running in UNIX
LabVIEW source code from one OS can be ported to another OS (except
for OS specific things like ActiveX) but executables cannot. You would
need the unix version of LabVIEW and it's app builder to create an new
...Installing LabVIEW Run-Time Engine 8.5.1
I want to run saved VI's from one computer with LabVIEW 8.5 Professional Development (8.5) on another computer using the Run-Time Software.
After installing LabVIEW Run-Time Engine 8.5 (<a href="http://ftp.ni.com/support/softlib/labview/labview_runtime/8.5/windows/LabVIEW85RuntimeEngineFull.exe" target="_blank">LabVIEW85RuntimeEngineFull.exe</a> from <a href="http://joule.ni.com/nidu/cds/view/p/id/861/lang/en" target="_blank">http://joule.ni.com/nidu/cds/view/p/id/861/lang/en</a>), do I need to do anything else before running a saved VI created in LabVIEW 8.5 from another computer? I install the program, but the only options under programs-national instruments are:
When I installed LabVIEW DSC Run-Time System 7.1 on the same computer there was an shortcut under "programs-national instruments-" to LabVIEW DSC Run-Time System 7.1, which is what I need but for the Run-Time Engine 8.5 instead.
I believe you can not do this. The runtime I believe requires the executable version of the VI.
You will need to build an application from your saved VI. In the application builder, you can include the run-time libraries and progras. This will help ease the installation process. Once you have completed this operation, you can just run the executable with your VI.
Joseph is correct. The run-time engine is only for "stand-alone" execu...labview 8.2 llb run with labview 8.5
On the PC I have delete labview 8.2, but I dont find the CD for reinstall. I have a .llb file made with labview 8.2, Can i run it with labview 8.5 or download labview 8.2, I muss install ii rapidelly.
Costello, you can update the VIs within the LLB to LV 8.5 if they do not have their blockdiagram removed.....hope this helps,Norbert
How can I update ? When I start the .vi in the lbb he dont found somme .vi located in DAQmx (wrtie.lbb, start task.lbb,...) How can i install this lbb?
Costello, if you get loading errors when opening one VI from the LLB like you the ones you get, you have missing components.Since you spoke of DAQmx, i asume that you didn't install NI DAQmx on your machine. You should catch that up.hope this helps,Norbert
...Open LabVIEW 8.0 files in LabVIEW 7.0
I have developed an application in LabVIEW 8.0 and built a standalone executable just to realize that I have to deploy it in a Windows NT computer that is not compatible with LV Run Time Engine 8.0 that only supports Windows 2000 and XP. I have tried to open the labView files (*.vi) using LabVIEW 7.0 but it gives me an error. Is there any easy and clean solution to import these files in LV 7.0 in order to build a new excutable and make it compatible with Windows NT?
...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?
...Re: LABVIEW 8.0 DATALOGGING RUN-TIME SYSTEM installation failure
Thank you for contacting National Instruments. Does the error give any more information about why the installation failed? Does it say the instance name is invalid or another version is already installed? There are several reasons this could happen. This error means that DSC could not install the Microsoft SQL Server Desktop Engine. Please take a look at this <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;317268" target="_blank">Microsoft Knowledge Base article</a> that describes several symptoms and workarounds to see if this is useful. Any more information you can provide about the specific error message would be helpful in troubleshooting this issue.
...labview 8.5 to labview 7.0
i am on my labview working with 8.5but at work, we only have labview 7.0.what would be my best way to get my vi to be 7.0?thank you so muchMessage Edited by krispiekream on 06-19-2008 03:59 PM
In order to go from LV 8.5 to LV 7, you will need to have LV 8.5 (save it back to 8.0), LV 8.0 (save it back to 7.1) and LV 7.1 (to save back to 7.0).
If it's only a few small VI's, you can post them on the forum and ask someone to do the saves for you. (Best if you do the save back to 8.0 and post that in order to eliminate 1 of the 3 steps for whoever will do the rest of the conversions for you.)
yeah. great.. i did all those steps.i went from 8.0 to 7.1i dont have labview 7.1 so i can't go to 7.0.can someone please help me.
Please try the attached to see if it works with LV7.0
Hopefully it does!!
thank you so much. i'll try it right now.
hi there,i somewhat got it to work.but i am having this error everytime i try to save it.does anyone know how i can get rid of it?<img src="http://forums.ni.com/attachments/ni/170/334653/1/untitled5.PNG"> Message Edited by krispiekream on 06-24-2008 06:02 PM
You might want to look into <a href=&...You must install LabVIEW run-time engine on the computer you run the application
When I build an executable application, I get a warning message
says,'You must install LabVIEW run-time engine on the computer you run
How can I solve this problem? Thanks.
It is not a problem. It is a requirement that you install the run-time
engine so the app builder is just reminding you of that fact. When you
create the installer for your app, you can optionally choose to have
the run-time engine as part of the install.
Install LabVIEW run-time version (1 CD) on your computer before you
run the .exe.
...LabVIEW 8 run time
Am upgrading from 7.0 to 8. Is Run Time compiled with the .exe during
the build? Does Run Time install with the .exe on the target machine?
Are there any hoops to jump through during the build, or target
Instructions for 8 Run Time seem to be slim.
The run-time engine isn't really compiled with your built application since it's a separate program. You can, however, include the installer as part of your build so that when you deploy your application you will also distribute the run-time engine with it. From the LabVIEW documentation:
If you use the Applicati...labview 7.1 to Labview 8.0 upgrade
My company has recently aquired labview 8.0 licences and is intending to use it as its development platform instead of labview 7.1. the problem is that all of our customers are currently running executables generated in a labview 7.1 environment and any updated versions of our software that we will send them in the future will most likely be developed in labview 8.0. The question is , other than sending them the executables generated by LV8 along with LV8 RTE are there any problems. did any one see a problem with a conversion like this. i have done alot of reasearch about this and have been testing the converted code from 7.1 to 8 and the executalbes generated by 8.0 and i havent seen any major problems. any feedback on a related probelm would be greatly appreciated.
I am using
PCI I/O boards
talking to remote and local data bases (Micorsoft and Oracle)
all on a Windows Xp pro operating system
...Labview 7.0 Vs Labview 8.2 Issue?
Hello, For a independent study Labview class I'm taking, I am trying to create a program that will input two different wav files and combine parts of them together for audio output. The first file I am trying to cut out the bass lines and replace them with the bass lines from the second file. Kind of like turning the second file into a karaoke version and filling in the vocals with the vocal line from the first file. A second option is simply taking the instrumentals from a song (a wav file containing only the bass line) and adding them to the first file after cutting out the original bass line of the first if this isn't possible. I found the attached file while searching for information/examples as to how to do this - it was originally posted at:http://forums.ni.com/ni/board/message?board.id=170&message.id=74618&requireLogin=FalseI tried running the file in Labview 8.20 and it came back with the error that "Build Screen.vi not found." I have searched for this file to download but have come up with nothing.Also, any tips/pointers/comments (or "there is no way this is possible") are much appreciated and very welcome. I have been searching to see if there is anything like this that has been done before and as of yet haven't been able to find anything. I am pretty new to Labview but I am a quick learner and I have a professor working with me on the project that is very familiar with Labview. However, it's spring break right no...Labview run time 8.5
Where can I download labview run time 8.5?
Does LabVIEW run-time engine 8.5 support earlier version of LabVIEW compiled files and how far back does it support?
Hello Simon, The
Run-Time Engines are not backwards compatible. I.e. LabVIEW Run-Time
Engine 8.5 cannot run executables made in LabVIEW 8.2.1.So, you need to install the Run-time engine for the version of LabVIEW that
the code was written in. E.g. If your VI was written in LabVIEW 8.5,
you need to have the LabVIEW 8.5 RTE (Run Time Engine) installed in
order to run it after it is compiled into an executable. In order to check which Run-Time Engines you already have installed to your PC, browse to the following directory.C:\Program Files\National Instruments\Shared\LabVIEW Run-TimeIn
that directory, you will find a different folder for every version of
Run-Time Engine that you currently have installed onto your system.Hope this helps!
...How can I run a labview 7.2 vi in labview 8.2
We have several versions of labview running different test and control functions in our facility. There are labview 7.2 VIs in a production setting I wish to reproduce in the test lab. Can I convert them to run on 8.2 or do I have to recreate them in 8.2. I tried to open one in 8.2 and got multiple SubVI's that were not in my program library.. most dealing with AI manipulation.
And make sure you have backup copies of your 7.x code. Once you load and save in 8.2, it is a lot of work to get them back to 7.x.
Note I used 7.x because I am unaware of LabVIEW version 7.2 even existing. 7.1.1 was the last release prior to 8.0
...Send sms from Labview without LabVIEW 8.0 PDA module
Does anyone can send sms from Labview without LabVIEW 8.0 PDA module?
...ALL 8.0 LABVIEWers!! Convert 8.0 VIs to 7.1
This is another "Can somebody help me cause I'm desperate?" kind of post.
I am using the brand new 8.2.1 version and I have to submit the prog by the 8th of January.
After using 'Save for previous version' I have only managed to "degrade" it to 8.0
Thus - Could somebody convert the attached zipped VIs to version 7.1 or any other that would work with Labview 7 ?
I have not used any new modules/functions e.g. instead of using the new x^2 (squared) triangle I have used the old 'to the power of x' function with a two etc.
The sigma.vi is the key one - if u dont manage to convert all of them just pack the converted ones, preferably checked.
Thanks a whole lot!
I have suffered this recently where I opened a 7.1 project in 8.2 went to a client site with the code and could not do anything since I only have 7.1 and 8.2 on the PC I am working on. Very frustrating. I can help you possibly later when I get my laptop back in the office with 8.0. NI is not considering us who have subscriptions but skipped 8.0 but use 8.2 and 7.1 extensively. NI should automate a server with a FTP that can take a project in any version and batch process it and down grade to previous version online. Could be very useful, especially for this discussion forum w...LabView 6.1 Run-time engine
Hello, all. I installed the LabView 6.1 run-time engine on a Win2k
platform with no trouble. My question is that when one is building an
executable LabView application to use the run-time engine is it possible
at build time to know the subroutines and dlls that a particular VISA VI
(a component of the top-level VI) will call? These subroutines/dlls
either have to be included in the build or on the run-time platform.
Although LabView 6.1 Professional identifies the sub-VIs of the top-level
VI, I see no tool(s) that identifies the needed subroutines/dlls (e.g.
VISA.dll in the \Windows\Syste...I need convert LabVIEW 4.0 files to LabVIEW 8.5. Can it be done?
I am running LV8.5. I am upgrading and/or converting an old legacy system. All I have is the disk with the VIs from the old system. I do not have an older version of LV installed.
I can install all the way back to version 5.1. But I am concerned, can LV8.5 convert 5.1? The real question is what is the earliest version of LV that 8.5 will convert and will that version convert 4.0.1?
I have to imagine this has been done. With all the legacy systems going obsolete. This should be a common need.
Thanks for all of the responses. I have about 500+ VIs to convert. I would not be able to post them because of the nature of the projet but thanks for the suggestion. I have to imagine that someone in the office has 8.2 still floating around. I do not want to go back to 6 or 7. I will hunt for an older machine in the AM. Maybe a good job for an intern.
...pdfcreator invokes LabVIEW run-time engine installer!
Okay, so I'm a desktop tech, know little about LabView, but can at least install it. We also use pdfcreator on our desktops. For some reason, however, whenever pdfcreator is used (for ANYTHING, not just LabView stuff), a windows installer fires up, "please wait while windows configures NI LabVIEW Run-Time Engine 7.0." The installer proceeds, then gets stuck while trying to find the msi. Well I don't HAVE the proper MSI apparently, because my version is 7.1.1! When I put in the 7.1.1 Run-Time CD (the only one I have) and point ...UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71
UNABLE TO LOCATE THE THE LABVIEW RUN-TIME ENGINE.LVBROKERAUX71 REQUIRES A VERSION 7.1 (OR COMPATIBLE) LABVIEW RUN-TIME ENGINE?PLEASE CONTACT THE VENDOR OF LVBROKERAUX71 TO CORRECT THIS PROBLEM
Uninstalled DAQ and reinstalled. MAX still throws an error.
Any Isead besides uninstalling 3/4 of my software?
...LabVIEW Run Time Engine and ActiveX Automation Server
I have a question related to LabVIEW Run Time Engine and ActiveX Automation Server:
We have a tool developed in LabVIEW and TestStand. End user interface is a LabVIEW GUI (it's an executable) which executes TestStand sequences. Some TestStand sequences call lower level LabVIEW VIs.
Everything works fine with LabVIEW installed, but I was wondering if I could run this tool on deployment machine with only LabVIEW run time engine installed. We are using LabVIEW 6.1 and with only the run time engine installed, I get the error message: "Unable to launch the 'LabVIEW.Application' ActiveX automation server ".
BTW, we are planning to upgrade the versions soon.
Is it possible to make things work only with the run time engine?
Thanks for the response, Brian.
I did upgrade to LabVIEW 8.0 and TestStand 3.5. Everything works fine on the development computer where LabVIEW and TestStand is installed. On the target computer in the lab, I installed LV RTE 8.0 and TestStand 3.5, and now when a VI is called in a sequence file, I get the following:
RunState.PreviousStep.Result.Error.Msg "LabVIEW: The VI is not executable"
So, the executable opens and works fine (which means that the LV ...NI Labview Run-time Engine installation fail
I am attempting to install my USB-6008 data aquisition device for use with Labview. I get an error:
The NI LabVIEW Run-Time Engine 7.1.1 installation has failed with the following error.
Error 1402. Could not open key: UNKNOWN\OPC.ServerList.1\CLSID. Verify that you have sufficient access to that key, or contact your support personnel.
I've been having trouble with the installation in general - is the above error critical? What can I do to correct it?
Thank you for contacting National Instruments. After checking to see if you have administrative priviledges on the computer, you may want to look at these articles from <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;303089" target="_blank">Microsoft</a> and <a href="http://www.adobe.com/support/techdocs/329137.html" target="_blank">Adobe</a>. Try the steps highlighted there and let me know what you find.
ajs_olnpvt: Thank you again for the prompt reply. You should be able to install the driver for for USB 6008 device with the student version of LabVIEW, so I do not think that it is an issue. I did some further research and I found that this is a Windows
installer error and not a National Instruments error. Even though you
are logged in as the administrator and have access to the key, the
L...Running LabView run time from Excel
I need to run a labview runtime from Excel, the problem is I do not
have LabView installed on my computer so I do not see the LabView
object library in Excel VB interface, I assumed that installing a
runtime version should install that too.
Am i missing something, or is there a way to run a labview runtime VI
using ActiveX without actually intstalling labview.
Check out this post on <a href="http://forums.ni.com/ni/board/message?board.id=170&message.id=45099&requireLogin=False" target="_blank">Accessing compiled VI`s via VBA </a>. I think will shed some light on the subject. Also, consider making a dll instead of an exe. That may also solve the problem. Post to let us know your results. Thanks!
I'm hoping that this thread isn't TOO old... In any case, I am also trying to call an ActiveX server I have built with LV from Excel. If I change the reference to "Labview.application" to something like "myapp.application", the routine actually runs once and Excel stops with a "runtime error '13' type mismatch". Anybody have any ideas as to what is mismatching what?
Two things to verify,
1. The LabVIEW run time engine is installed.
2. You've enabled ActiveX for your executable. See the picture below.