If i have a labview .vi file(and labview) but i want to open it in a computer that doesn't have labview, how would i do it??
Okay, i have a made a labview program and save it as.vi.
Let's say that it is a program that when opened and you hit run it shows a sine wave.
Now if i wanted to open up the program without Labview, ( i don't need to modify it) on a computer that doesn't have labview. How would i go about doing this??
...Converting LabView 4 vi. to LabView 7 vi.
I have a collection of programs written in LabView 4. I upgraded to
LabView 7 recently. I am now trying to open my old 4 vi's with no
luck. No block diagram is the error that I'm getting. Any ideas on
converting would be greatly appreciated.
Without a block diagram, you cannot open a VI in a newer version
because the block diagram is required for the recompile. The only way
to upgrade is to find the original VIs with the source code. No one,
NI included, can recover a block diagram once it has been deleted.
Chris Merriman wrote:
> I have a collection of programs written...Labview error code 10:vi version is too old to convert to the current labview version (8.0)
when I'm running a squence from example for computer main board test in the operator interface, the error occur
Labview error code 10:vi version is too old to convert to the current labview version (8.0)
my teststand version is 3.1
I'm confuse how is the current labview version (8.0),actually I don't have installation the labview yet .
...How to open Labview 8.5 VI in Labview 8.2
Hi I am using LabVIEW 8.2.I found one ook modulation example project(http://decibel.ni.com/content/docs/DOC-1394),it was developed in Labview 8.5.I have to oepn this one in My system mean in Labview 8.2.Please tell procedure.Is it possible or not.?Thnaking you sir.
It is not possible directly. Somebody with access to version 8.5 needs to save it for version 8.2.
Could you attach that particular vi in your post so that somebody can save it for 8.2
Or you can install Labview 8.5 demo. Works for 30 days....
Hi Mathan,Thanks for your reply.i need OOK Modulation (FPGA).VI and OOK Modulation (HOST).VI in version 8.2Here i am attaching this two vi please save it in version 8.2 and send to me.Thanking you Sreenivasulu.O
i�m not sure if they are enough, but here they are. :smileyhappy:
OOK Modulation (FPGA).vi:
http://forums.ni.com/attachments/ni/170/324624/1/OOK Modulation (FPGA).vi
OOK Modulation (HOST).vi:
http://forums.ni.com/attachments/ni/170/324624/2/OOK Modulation (HOST).vi
Hi Mike,i got error like this.Here i am attaching two error image what i got.please check nad correct me.One more "OOK_Pack Bits for transmission.VI" and "OOK_Configuration IF RIO for Transmission.VI" was not found.Thanking you sirSreenivasulu.O
ook_error2...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
...Strange crash with Intel FFT in Windows XP x64: only when first starting LabVIEW and opening VI, not when opening VI by double-clicking
When I use the Intel FFT libraries(MKL), I seem to have a strange crash whenever I start allocating the Intel DFTI descriptors. I call a DLL from LabVIEW 8.2.1, in which these functions are used. I am working on Windows XP x64. This seems like a bug which was present in these libraries, but I got the libraries where the bug was resolved.The strange things is that, when I open LabVIEW and then open the VI, LabVIEW crashes from the moment I allocate an Intel Dfti descriptor. But when I just double-click the VI and open it this way, I can run the VI without a crash! I already removed the DLLs in \Program Files (x86)\National Instruments\Shared\MKL\MKL70 to see if they were the cause. But even without them, I still get the crash.I know there was a strange crash in the previous version of Intel MKL when calling a DLL and allocating this type of descriptor, so it seems like somewhere LabVIEW still uses old versions of some of these DLLs. But even then, can this explain the difference in behaviour between opening the VI through LabVIEW or directly? And if so, were could I find these DLLs? I've already searched from them everywhere.
Interesting effect... I guess, may be something wrong with entry point of the DLL. In the DLL you may have DllMain function, which will be called with DLL_PROCESS_ATTACH (or DLL_THREAD_ATTACH) parameter when you open the VI, which contains DLL call.
I will suggest to try do not call MKL DLL directly, but create your own wrapper DLL,...Calling a LabView DLL from a Labview VI
Hi, I have a vi that is calling a Labview DLL and they both have a same
subVI. If I drop that SubVI into the block diagram first then drop in the
Call Library Function Node, when I run the VI, the DLL would not work and
it did not give me any error. Does anyone know how fix this problem with
Labview? or is there some configuration that I can force the all of that
SubVI points into the DLL.
Thanks for your help,
...No 64-bit long ints in LabVIEW 7? [Also: beta version of 64-bit LabVIEW?]
Is there no primitive data type in LabVIEW 7 that corresponds to a
64-bit long int? [I guess LabVIEW would call it either I64 or U64...]
Please, please tell me I'm wrong - if I'm right, this is an
unacceptable state of affairs.
And, if I'm right - when will LabVIEW be upgraded to 64-bit-ness? Is
there a beta version of 64-bit LabVIEW out there that I could get
involved with? [I'd really, really like a 'for' loop that could take
64-bit ints as its counters.]
Anyone know anything about this?
There is no native support for 64 bit ints. I don't expect to se...Is LabVIEW 7.1 Aug2005 identical to LabView 7.1 May2005?
I am attempting to have a coworker at a remote site set up their PC with the exact same software as one that I have here. I used the August 2005 CDs from Developer Suite. My coworker tells me that he has the TestStand 3.1, and the Device Driver CDs from the Aug2005 Dev Suite shipment, but he can only find LabView 7.1 from the May2005 delivery.
I would like to safely assume that LabView 7.1 is LabView 7.1, regardless of whether it was shipped in May or August, but it is really important to me to make absolutely sure that we end up with the same software v...Why cannot a VI be run in LabView version 7.1, if it ran in version 6.1?
I developed a VI in LabView 6.1 and try to open it in version 7.1. The
error was as follows "Compile Error - Report this error to NI Tech
Support: nmx unbundler bad sea/eea or edisp-sdisp = 0x1"
It was suggested to me that I should mass compile all my 6.1 files,
before opening them in version 7.1.
I did so and then the error became "Code could not be generated
correctly for this VI / An error occurred in compiling this VI"
Please advise of a potential solution.
A couple things you might try.
Open the offending VI in 6.1 and do a "Save As" a...change a LabVIEW array outside LabVIEW and keep updated in LabVIEW
change a LabVIEW array outside LabVIEW and keep updated in LabVIEW
I am Interfacing a FrameGrabber with LabVIEW using a frame grabber
The memory managment of this FG allow you to allocate your own Array
and to give a pointer to this Array to the memory manager.
Then when you acquire with the frame grabber, the acquired image will
be directly accessible in your array.
1.I give to the FG memory manager a pointer to the Labview array
through a SDK Dll function.
2. I run the acquisition
3. I display the array
My problem is that the Array is allways displayed with it initial
val...LabVIEW 8.0 changed a constant that was wired to a Case structure to a hidden control to maintain compatibility with LabVIEW 7.1 and earlier.
Y am i getting this msg?
This happened because "...LabVIEW does not compile code on the block diagram that does not execute. For example, LabVIEW does not compile any code that exists within the inactive subdiagrams of the Conditional Disable structure. In addition, LabVIEW does not compile code within a Case structure that has a constant wired to it that would not execute the case with the code..."In the other words, if you have case structure, which is wired to T/F constant, then prior to version 8.x both cases will be compiled. From version 8.x the only "executed" case will be compiled. So, LabVIEW replaces constant with control for ensure that both cases will be compiled as before.
refer to <a href="http://zone.ni.com/reference/en-XX/help/371361A-01/lvupgrade/labview_8_0_features/" target="_blank">this document</a>
Got it andrey thanx
...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
...Compatability from Labview 5 to labview 7 express?
I am having a problem where I may have to write a VI on labview 5 on
one computer, then move it to a second computer running labview 7
express. Are there any compatability issues I may have to deal with in
there is not supposed to any compatibility issues with version 5. You
would have a problem going backwards from 7 to 5 but not from going
from 5 to 7.At least that is the way it is supposed to work.
LabVIEW 7.0 will open and convert LabVIEW 5 VI=92s. There are
occasionally conversion issues, just depending on what is involved in
the VI (the bulk of which bein...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=&...upgrading cRIO from Labview 7 to Labview 8
Hi again :)
I have a cRIO system that is running Labview 7. It runs fine. No problems. We've upgraded to LV8 and I'm wondering if I should convert the LV7 system to LV8. The only reason I would do this is because for me LV8 is much easier to work with regarding cRIO (using DMA, setting up the project etc.).
Now, if I attempt to upgrade the LV7 cRIO system, what kinds of problems will I run in to? I assume it means formatting the cRIO, installing LV8, converting the program from LV7 to LV8...
Is there an FAQ regarding this, specifically about the cRIO?
Jeff...labview crashing when calling labview-built dll
Hello I need some help with regard to calling a LabVIEW-built DLL in
LabVIEW.I have created a vi in LabVIEW. I made the DLL for this vi. I
called this VI as a re-entrant in another vi.This vi(calling DLL) has
been working fine till yesterday. Since yesterday, it started crashing
LV.I need some help in this regard.I am attaching the
screenshots of the Application Builder configuration window, the B.D of the vi
using DLL and that of the configuration window which pops up when i call the
DLL.I made a vi which performs FRA. I built its DLL.I have around 10
inputs. I output 3 one-dimensional arrays, and a string from the DLL.When i
build the DLL, the builder defines the outputs 'gain', 'phase' and 'frequency'
as arrays of 8-byte double.When i call this DLL in my vi, the configuration
window sets them as 'numeric' outputs.Why does this happen? What is the
solution to this?When i try to set them as 'array' in this configuration
window, i get a warning that i am trying to change the data types which do not
match with the data type found in the DLL. Is this the problem with my
code or with the Application Builder?Now, after i change the 3 output
datatypes to Arrays, and set their minimum length(i assumed that this value
means the size of the array ), the vi runs and crashes LV. I am nto sure when it
crashes, why it crashes. It runs fine at one time. It crashes at another time. I
am nto sure if these arrays are teh reason why L...How to convert LabVIEW 3.0 version source code to LabVIEW 6.1 Version?
How to convert LabVIEW 3.0 version source code to LabVIEW 6.1 Version?
Follow this link to see how to get the free VI Conversion package from
...LabView 7.1 crashing on exit of VI
LabView 7.1 has been crashing on me recently when I go to quit out of running my main VI. I really hope that someone will be able to give me a hint as to what I'm doing or not doing that might be causing this crash, so that I can make it stop happening (I have a communications VI running in its own thread on the side, for instance, but I cause it to quit by checking a global variable that gets set by my program during cleanup).
I can't post the VI as it's company property, but I get the following error description:
AppName: labview.exe AppV...DSC module 7.1 labview 7.1, new controls and functions not showing up in labview
I have installed labview 7.10 (also tried update to 7.11)
and DSC module 7.1
I thought I would get additional functions and controls in labview due
to installation of this module, but I do not see addtional controls or
functions, althought I have searched for them and set the controls to
Anyone any idea what I have to do.
thanks and regards.
...LabVIEW 8.5 crashes when I try to open this VI
A few days ago i was making changes to this VI for programmatically fitting the waveform graph to a pane on front panel. I was able to make some changes to the code successfully, saved the file and closed LabVIEW. But today i am not able to open the VI and LabVIEW crashes without giving any error codes. There is too much work put into this main vi and it will take a long time to reproduce it. Please HELP!!!
Yup, it crashes. I would recommend that you go back to your last backup and work from there... What's that? You don't have a recent backup? Hmmmm.... Consider this a lesson learned... Yet another good reason for source code control - daily backups.Mike...
Crashes for me as well I am afraid, But it is a pretty sad state of affairs that we have become so accustomed to corrupted VIs/projects. When was the last time you came across C code which brought down the IDE when loaded?I have to say, 6.0, 7.0 and 7.1 (the other versions I have worked with), were far less prone to random shutdowns and corrupted code.
Does NI have a way to salvage these corrupt VIs? There were only a few changes made towrds the end of the editing cycle and we should be able to discard those changes and retrieve the rest.
I hope someone says yes :smileysad:
Maybe someone with Labview 8.6 beta can open it....
In general there is no way to recover a corrupt VI. Even if a later version c...labview 8.2 crashes on opening a specific VI
Hi all - I really hope you can help me on this, because this problem is rather bizarre.
I have a VI that opens fine and runs fine. It's a rather massive VI, with upward of 30 subVIs.
If I open the VI, save it (even without making any changes!), close it, and then repeat that process a few times, on average about the 4th time I try to open it, LabView cannot display it; my CPU usage jumps to 50% (corresponding, I think, to maxing out one of the two CPUs), and Labview becomes unresponsive (and the front panel never shows up, and I can't ctrl-E into the block diagram).
This, of course, makes it rather difficult for me to edit the VI.
It seems like the file is corrupt, or something of the sort, so what I really need is some kind of workaround on making a not-corrupt copy, because re-writing it would be a huge pain.
P.S I'm not sure if posting the VI would do any good, since so much of it is various subVIs. I am also quite certain that there is not anything wrong with the code.
Are you able to open the VI?
If so, select the entire Block Diagram and copy everything into a blank, new VI. See if that helps...
Strange things do happen. In the past, there were bizzare "insane objects" which were resolved by copying the block diagram into a new blan vi. Saving it, and everything was fine afterwards..
Let us know ...Labview 7 crashes when a vi containing a dll is closed
I've written a dll in C language to use a USB dongle. Before making my C code into a dll, I throughly tested it as a console application, using Borland C++.
In Labview, I call my dll, using the call library function node. The first time I run my program, it does what I expect with the dll. If I try to run it again, it doesn't work. I found a program on the internet, called listdll, which displays the dlls that are currently loaded in memory. The dll that I wrote as well as the other dlls that this function uses (loaded statically), appear in the list.
&a...how to open 8.0 vi with Labview 7.0
i'm using LabVIEW 7.0
how can i open a vi that was create with Labview 8.0?