File conversion of LabView 2012 to 2011

Hello ,
I am new to Lab View. I am stuck with conversion of this file from LabView 2012 to 2011 .Help is very much appreciated
Thank you ,
With Regards,
Jagadish
Solved!
Go to Solution.
Attachments:
kiran_prob2.vi ‏7 KB

duplicate post

Similar Messages

Conversion from LabVIEW 2012 to 8.2

Dear All
Can any body help me to convert the attached file from LabVIEW 2012 to LabVIEW 8.2. Please send the file in doc or pdf as well.
Kind Regards
Muhammad Irfan
Solved!
Go to Solution.
Attachments:
PVT - Mathscript Node.vi ‏83 KB

Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
PVT - Mathscript Node.vi ‏90 KB

Labview 2012 to 2011

Hi,
Could anyone convert this labview 2012 driver to labview 2011?
Thank you in advance.
Attachments:
hp4195.zip ‏263 KB

Saved for 2011.
Adam
CLD & CTD
Attachments:
hp4195_2011.zip ‏177 KB

Conversion from labview 2012 to 2010

Hi there. Could someone convert this vi's to 2010 compatible?
Thanks
Attachments:
heart_rate_monitor_example.zip ‏182 KB

HI, Here you go.
You can verify that it works correctly.
Jonathan Cruz
CHALLENGER
K U D O S __ B I E N V E N I D O S
Attachments:
Heart Rate Monitor Project Folder.zip ‏144 KB

Missing vi.lib files in Run-Time LabVIEW 2012

Hi
I've got a problem executing VI's under RT in LabVIEW 2012.
Our system consist of multiple independent modules which are opened and run from a Manager VI. VI paths to the modules are read from an .ini file by the Manager VI.
We have build a single executable (RT Launcher) that takes the path of the Manager VI as argument (Attachment : RT Launcher.png).
The RT Launcher is placed in the ..\National Instruments\LabVIEW 2012 folder as the LabVIEW.exe.
The RT Launcher is called from the CLI.
"C:\Program Files\National Instruments\LabVIEW 2012\RT Launcher.exe" "C:\Workspace\Labview\Manager.vi"
This will run the Manager.vi in the RunTime Environment and the Manager.vi will open the .ini file and execute the Module VI's one by one.
By calling the RT Launcher.exe from the same folder as the LabVIEW.exe, the search paths should be the same.
The system worked fine in LabVIEW 2010.
The Manager VI is opened with broken arrow and the errors indicate that vi.lib sub VIs are missing (attachment : Manager VI errors.png)
I know there are issues regarding object cache and separated compiled code from LV2010 -> LV2011 -> LV2012, but simply can't figure out how to come around this problem.
Can anyone explain the difference and how to solve the problem ?
Thanks
Regards Kahr
Certified LabVIEW Architect
CIM A/S
Solved!
Go to Solution.
Attachments:
RT Launcher.png ‏68 KB
Manager VI errors.png ‏35 KB

Hi Kahr.
It sounds like you are making some dynamic calls to VI's, eg. by using 'Open VI Reference'. My answer is based on that assumption.
You are absolutely right. In LabVIEW2010 we introduced a function called 'Separating Compiled Code from VI'. At that time none of the VIs from VI.lib had that option enabled. In LabVIEW2011, many VI's in VI.lib have, by default, a separation of compiled code and VI. This option cannot be changed (greyed out) for these VI's as well. This feature was introduced in order to simplify source code control.
Separating Compiled Code from VIs and Other File Types
The drawback is, that it is no longer possible to call VI's dynamically from an application (executable), when this option in enabled, since the compiled code no longer exists. The method of calling a VI dynamically from an application has been (and still is) used to make some kind of a plug-and-play architecture, meaning we have one EXE-file that only gets distributed once and a set of subVI's that gets redistributed according to new versions (new features added to the subVI), meaning we can make changes in the subVI without having to redistribute the EXE-file.
With the release of LabVIEW2011 and LabVIEW2012 we can no longer distribute VI's that uses functions from vi.lib, this also include DAQmx calls even though the DAQmx driver is installed.
The simple explaining is, that it has never been intended that VI's got distributed. Eg, when Microsoft is making a new software update for Windows7, they don't send out the source code to all the users.
The solution is therefore to wrap up the source code into 'something' that includes all the compiled files. In LabVIEW we do that in a couple of different ways.
1) Include the VI's in the EXE-file.
When building the application, we have the option to include files, that normally is not included in builds. If we call a SubVI dynamically this will not automatically be included! However, the drawback of this method is, that if you need to change something in one of your SubVI's, you would need to build and distribute the entire application. Thereby, we are not making use of the plug-and-play architecture that we originally wanted. However, this method will fix the error.
Error 1003 When Using VI Server in a LabVIEW Application
2) Now, if we still want the plug-and-play architecture in LabVIEW2011+2012 (and this will properly be the same for the next many released of LabVIEW), this can still easily be achieved by making a Source Distribution. When we make a Source Distribution, we can include the VI's from VI.lib and thereby the compiled code. When using this method, two important things should be remembered:
a) Make the files into a LLB file. This will pack all the VI's into one single file, that is easy to distribute.
Go to Destinations ==> Destination Type ==> LLB.
b) Make sure not to 'Exclude files from vi.lib', as this method will then simply not work.
Go to Additional Exclusions ==> Remove checker mark in 'Exclude files from vi.lib'.
How Can I Call a VI Dynamically from an Executable Without Including Those VIs in the Build?
I have made a small example to demonstrate this:
Example: Using vi.lib
This example has two mainVIs and two EXE-applications. Build the two EXE-files, but do NOT build the source distribution yet.
1) Main(IncludeSubInExE). This version has included the subVI in the build distribution for the EXE-file. When running this EXE everything works fine, even when calling the subVI dynamically. However, since the subVI is build into the exe, we would have to redistribute the exe for every new version of the subVI. This breaks the hole idea.
2) Main. The subVI is no longer included in the build. When running and trying to call the subVI, you will get this error (on both your developer and run-time machine):
Now, build the Source Distribution and run this EXE again. The exe is running perfectly with no errors.
I hope this answers your question.
Best Regards
Alex E. Petersen
Certified LabVIEW Developer (CLD)
Application Engineer
Image House PantoInspect
Attachments:
Using vi.lib.zip ‏83 KB

Bind FPGA host reference to type definition in labVIEW 2012 crashes labVIEW

Hi,
I am using FPGA target device 5641R and labview FPGA 2012 with 5640R ver 1.7.
On the configure window of open FPGA VI reference function, choosing the dynmaic mode shows broken arrow when wired to the 5640R configuration VIs (i.e. Configure timebase, Configure ADC default, Configure ADC NCO functions). So i tried the other option which is binding the FPGA host reference to type definition and choose the control from path C:\Program Files\National Instruments\LabVIEW 2012\instr.lib\ni5640R\Configuration\NI-5640R VIs\ni5640R FPGA VI Reference.ctl. But after that when i try to save the VI on which open FPGA VI reference function is placed, labVIEW crashes. I am unable to figure out the reason. Earlier I was working with labVIEW 2011 and it was working fine there. Any suggestions would be highly appretiated.
Please see the attached images for more details.
Thanks
Attachments:
1.png ‏33 KB
2.png ‏71 KB
3.png ‏40 KB

Check out this thread. It looks like someone else ran into a similar issue and made changes that fixed their application.
http://forums.ni.com/t5/IF-RIO/correct-5640r-template-use-recommendation/td-p/1331918
Jeff B.
Applications Engineer
National Instruments

Open vi file with specific Labview version using batch file (Windows)

I want to open certain vi with using Windows batch file and to use specific version of Labview development system. I tried
"C:\Program Files (x86)\National Instruments\LabVIEW 2012\LabVIEW.exe" "path_to_vi"
"C:\Program Files\National Instruments\LabVIEW 2012\LabVIEW.exe" "path_to_vi"
to use 32-bit and 64-bit development systems respectively. However Labview opens file with version which was last used before. Are there any ways to force it use specified version?

No, it's a VI I wrote so that when I open any VI from Windows Explorer it will open it in correct version of LabVIEW according to it's source version (rather than the latest/last version of LabVIEW I opened). All it does to launch the right version of LabVIEW is to call System Exec with the path to the correct version of the LabVIEW.exe and the path to the VI - which is essentially the same as what your batch file is doing.
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

What files do I send to be upgraded from LabVIEW 5.1.1 to LabVIEW 2012?

OK. Just to be clear. I am a complete newb to ANYTHING LabVIEW or LabWindows related. I am a programmer, but I have never used any version ever. That said, I am responsible for the upgrade process of getting our old LabVIEW 5.1.1 system up to date. The old system (still running and doing it's job everyday), is an old Windows NT v4.0 SP6 system running LabVIEW 5.1.1. You can just imagine how ancient this is by today's standard.
Have I set the stage properly? I hope so. Newb, Ancient LabVIEW version 5.1.1, Windows NT 4.0, upgrading from 5.1.1 to 2012.
Now here is what I "think" I know about what is required. Because LabVIEW 2012 will not directly read in, process and /or compile LabVIEW 5.1.1 files, I must first open and save the files using an intermediate version of LabVIEW (specifically 8.2.1) to bring the files up to a version that 2012 can handle. I have noticed in reading the Version Conversion forum, that I can attach a zip file of my LabVIEW files and one of the resident Gurus will convert it for me and give them back - quite nice I think.
Now, I have what I think are all of the required LabVIEW vi and llb files that make up this system we have in place, but I want to be sure before I just post a bunch of stuff.
What exactly do I need to zip up and what can I leave out?
Are there LabVIEW vi and llb files in a "project" that are not needed?
Are there any setup/configuration/project specific files I need to include?
Are there any limitatations to this conversion process that I need to be concerned with - such as various toolkits/suites/modules that may have been used but are no longer supported?
Secondly, I am not really comfortable with posting my vi and llb files for the world to see (and possibly use) as I am not the owner of said modules, just the user/future developer who will be responsible for insuring they stay up to date. Is there any way I can send my files to a specific NI guru via email instead of just posting them?
Solved!
Go to Solution.

So if I understand you correctly, all I really need to do is to get LabVIEW 8.2.1, and update my .vi, .lib, and any .ctl files to that version.
Is it a simple matter of just opening the files and hitting something like SAVE AS, or just SAVE and it will do this? Once done, LabVIEW 2012 will then allow me to open them and do what I need to do? Do I have to save them into LabVIEW 2012 first, or is that automatic when I try to recompile them?
When I get a copy of LabVIEW 8.2.1 (eval version), do I have to get all of the pieces (modules, toolkits, etc.) in order to update the 5.1.1 files? Based on what is installed on that NT v4.0 system, we have the following items installed:
NI VISA
NI ComponentWorks 3D Graph
NI DataSocket
NI LabVIEW 5.1.1 Advanced Analysis Library
NI LabVIEW RTE 5.1.1
NI LabVIEW v5.1.1
NI Measurement and Auto Explorer 1.1
NI-488 2.1.60
NI-DAQ 6.6
NI-PAL 1.3.110
NI-Reports
NI-VXI/VISA
You mention DAQ. Our program uses NI DAQ v6.6 now. I have LabVIEW Developer 2012, so I just download the DAQ files for it and it will replace the NI DAQ v6.6 library files we use now?
Thanks for your help so far. If we had a support contract in place, this wouldn't be an issue. However, as I stated, I am not the owner of the files, just the currently assigned caretaker, and part of my task is to get from where we are now on this ancient hardware/software platform, to the latest and greatest. However, I am specifically not allowed to just place the files on a public forum for all to see. It just isn't done. We can send them to a known location and a known entity, but not to just anyone/anywhere as a public forum is by its very nature.
I know there is nothing you guys can do if I cannot give you the files, but thanks for helping me to do it myself. Getting an eval copy of 8.2.1, et. al is probably what I have to do here.

LabVIEW 2012 LLB for VBAI 2011

Hi
I'm trying to build some labview vi's in LabVIEW 2012, to be compatible with Vision Builder AI 2011. I want to include some shared variables. I have the library file containing a string shared variable and a labview VI with just a string control into the shared variable. This is to read text from the vision build inspection. Both the library and the vi is saved under version 2010 but when I try to make a LLB file, the versions change to 2012 again. Do you have any inpute into why this could be?
Cheers.

You need to use the LV project to create a source distribution that includes all the dependencies (including vi.lib). Then close out LV 2012 to make sure you don't accidentally get any cross linking. Open the main VI of your built LLB with LV 2012 and then go to File>>Save for Previous. If there are any licensed VIs from vi.lib included, those may not save for previous, but I think this is what you should try to do.
I'm not sure exactly what you are trying to do, but if you want to use shared variables, VBAI (2010 or later) can update a shared variable with it's results (or read the variable if you want to pass data to VBAI), and then any version of LV can read/write that shared variable because shared variables are not LV version specific so you don't have to have the same version of LV to read/write shared variables. If this is all you want to do, you could just keep your LV code in LV 2012 and read/write the variable that is used by VBAI 2011. You can also use the VBAI API to control the inspection from any version of LV 2010 or higher regardless of the version of VBAI. You can see an example here:
C:\Program Files (x86)\National Instruments\Vision Builder AI XXXX\API Examples\LabVIEW Examples
Let us know if this still does not address your question and provide more details if this doesn't help.
Thanks,
Brad

Convert TCPIP_Nagle_algorithm.zip from LabVIEW 2012 to LabVIEW 2011

Hello,
can somebody convert the VIs in the zip file from LabVIEW 2012 to LabVIEW 2011 please. I need them to study.
Thank you very much for your support.
Solved!
Go to Solution.
Attachments:
TCPIP_Nagle_algorithm.zip ‏63 KB

Additionally I am sorry that I have put my post in LabVIEW and not under Version Conversion

Conversion of VIs from LabView 2013 to 2011

Hi,
I would be grateful for conversion of zipped VIs from LabView 2013 to 2011.
Thank You,
Michal
Solved!
Go to Solution.
Attachments:
main VIs.zip ‏38 KB

Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Attachments:
main VIs 2011.zip ‏27 KB

Only have LabVIEW 2012. Why am I asked to download LabVIEW 2011 SP1 f2 RTE Patch?

Hello,
I recently got a new machine (clean install of Windows 8), and installed LabVIEW 2012, with no other previous versions. However, when I ran the NI Update Service, it listed "LabVIEW 2011 SP1 f2 R(32-bit) Run-Time Engine Patch" as a critical update.
I'm confused; did I accidentally install LV 2011 too?
Thanks
Solved!
Go to Solution.

Also, some addons use older RunTime Engines. It is not suprising that you need the 2011 RTE patch.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Where does LabVIEW 2012 keep Recently-opened Files?

When you open LabVIEW 2012, the right-hand side of the Welcome Screen shows an Open Existing list. In my case, "bad" VIs and Projects (some of which no longer exist) show up. I'd like to edit this list to clear out the junk. However, it no longer is in the LabVIEW.ini file, nor does it seem to be (though I may have missed it) in my LabVIEW Data folder.
Who knows where it is?
Solved!
Go to Solution.

Found it! It was the LabVIEW.ini file -- either I was looking at the "wrong" one before, or somebody put something weird in my tea when I wasn't looking. Cleaning it out now ...

Upconversion the TestStand file from V5.1 to LabVIEW 2012

Hi, please convert all the VI V5.1 files in the ZIP file to LabVIEW 2012, many thanks.
Attachments:
Teststand1582.zip ‏149 KB

Mass compiled in 8.2.1, which you can open with 2012.
I think you are missing your second attachment.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
Teststand1582_mass compiled.zip ‏136 KB

LabView 2012 hangs when opening a file from LabView 8.5

I have a program originally built in LabView 8.5. I am attempting to migrate it to a new machine running LabView 2012. I can open the program for the first time and make the adjustments needed to clear a few errors having to do with updated VI's and controls. I can then run the VI but after this I close out of LabView and when I attempt to reopen the file LabView hangs on the splash screen while loading the VI.
Any help would be appriciated. Thank you.
-Sam

Please post your original VI and the converted one so we can take a look.
This account is no longer active. Contact ShadesOfGray for current posts and information.

File conversion of LabView 2012 to 2011

Similar Messages

Maybe you are looking for