Labview version problem?

Hello guys,
I have made a subVI that controls the rpm % of a wind tunnel vane. This consists in adquiring 2 values of data within 30 seconds and compare both to see the uniformity of the flux. I use a Labview 2011 version. The problem occurs when i use this subvi in a 2012 version. The 30 seconds turn to 1 minute... I want to ask if its possible for this to be a version problem.

I'm concerned that you are reading a file and then reading it again 3 seconds later. This tells me you are looking for when the other process stops writing data. File IO is a terrible way to share data. Use a Notifier or Queue instead. Much more efficient.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Similar Messages

What are developers' opinions on how best to handle upgrading large code libraries with multiple apps to new a labview version?

I have a large set of code that I've painstakingly migrated from one labview version to another over the years. I have lots of deployed applications that I need to continue to support. From experience and interaction with other developers, I don't think I can continue to migrate every application to a new labview version when I upgrade going forward. Every application seems to break in one way or another, the builds don't work right and need to be re-done, and its too much time to get all my applications working and tested again. That opinion is solidified by NI's policies that make it impossible to install old toolkit versions on new labview versions, for example. Compatibility is often being sacrificed so NI can develop labview in the direction they choose. So I have to take the position that whatever version I write an application in will probably need to be maintained in that labview version throughout it's life.
In light of this, how are other developers managing older applicatiosn written in older versions of labview. Right now I have a virtual PC on my system with 7.1, 8.0, 8.2, and 8.5 all running on different virtual PC's so I can keep each installation separate. I strongly recommend this approach. But keeping my large libraries of code separate is tough. They are many GB, they all link to each other, and I always get worried even when I separate them in different directories that somehow labview will search in the wrong place and find the wrong version of a sub-vi. Are other people also trying to maintain separate copies of all their code in different labview versions? How are other people managing this problem?
-Devin
I got 99 problems but 8.6 ain't one.
Solved!
Go to Solution.

Hi,
The following directory hierarchy, coupled with a "hierarchical" VI naming strategy, have been effective (for me) at preventing "cross-linking" across projects and LV versions. The storage hierarchy was designed for use within an SCC environment, but works fine independently. Hierarchical-naming insures unique names for application-specific files. Use of Project Libraries (in LabVIEW 8.x) addresses the problem of having different VIs with the same name, still, it gives me warm-fuzzies to have app-specific files named uniquely, and I can't imagine not using Hierarchical-naming anymore - it's described at-length in section 2.1 of attached .doc..
Note: It's been my experience that companies identify resources as supporting specific "Programs", where a Program is related to a product or "family" of products, so, under <Programs> (below) each "Program" subdirectory encapsulates product-specific (or product-family-specific) applications. Also, assuming no SCC tool is being employed the <Production> directory (below) exists as a repository for distributables. All distributables required to reproduce a test-station should be located under <Production>.
<Software_Root>
<Development>
| <Common>
| | <LabVIEW_61>
| | | <Drivers>
| | | | <DMM>
| | | | <OS>
| | | | <PS>
| | | <Utilities>
| | | <File>
| | | <Error>
| | | <String>
| | <LabVIEW_711>
| | <LabVIEW_82>
| | <LabVIEW_851>
<Programs>
* Program-specific applications that (probably) have distributables
| <Program_#1>
| | <Application_#1>
| | <Docs>
| | <Source>
*       Individual, application-specific, VIs go here
| | <Application_#2>
| | <Application_#3>
| <Program_2>
| | <Program_3>
| <Tools>
* Tools are NOT "program"-specific, and, may have distributables
| <SomeTool>
| <SomeOtherTool>
<Production>
| <COTS&Freeware>
| <Programs>
| | <Program_1>
| | | <Application_#1>
| | | | <Application_#1_Rev#1>
| | | | Application_#1.bld>
| | | | <EXE>
| | | | <Installer>
| | | | <Source>
| | | |    Application_#1.llb>
*           Distributable is created from LLB "snapshot", not directly from development tree
| | | <Application_#2>
| | | | <Application_#2_Rev#1>
| | | | Application_#2.lvproj>
| | | | <EXE>
| | | | <Installer>
| | | | <Source>
| | | |    Application_#2.llb>
| <Tools>
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
Attachments:
StyleGuide.doc ‏941 KB

Labview version 6.1 failure:"linker.cpp", line 2302

I have the labview version 6.1 failure:"linker.cpp", line 2302 fault.
Does any one can help me please ?
Solved!
Go to Solution.

Actually HeapPeak existed as far back as LabVIEW 4 or maybe even 3. However it is not usually helpful for linker errors as that is something in the LabVIEW compiler itself. HeapPeak can be sort of useful for Insane errors to locate the element that the compiler considers insane (and consequently delete and/or rewire it).
If this is a recent error on a VI that used to work before, it is most likely related to a corruption to the VI and the best course of action is to replace the VI from a backup (source code revision control would be a great advantage here). If it is something where no previous (working) state is known about, then it is going to be a tough cookie. This version is 14 years old and eventhough I still have some installation of that version somewhere it is several years ago that I started that up for more than some accidential reasons. I'm pretty sure NI would need to do some archeological work nowadays to come up with a system they could use to replicate such an error and the OP would need to be a pretty high profile customer that they would go through that sort of effort.
Maybe it is related to this error. It is the closest available in the publically accessible list of errors. A complete recompile of the entire source code tree is definitely one of the first actions to try. It may fix the problem or run into even more errors that could maybe point into a more specific location. Upgrading to a more recent LabVIEW version is another possibility although hampererd by the fact that the currently shipping version isn't officially supporting XP anymore and that the Vision software is one piece of software that underwent serious changes in the course of time and an update from 6.1 to the most recent version is most likely not a seamless operation.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Get Project LabVIEW Version

Lets say I have a random LabVIEW file. I can use the Get File Type.vi found in the VI.lib to figure out what the file type is. It could be an Instrument, Control, Project, Library, XControl or a bunch of others. If it is a VI I can use the Get VI Version invoke node to find what version of LabVIEW it was made with. If it is a Library I can use the Library.Get File LabVIEW Version to get the version, or if it is a project I can use the Project.Get File LabVIEW Version.
What I find strange, is if I have a VI saved in 2013, and I run the invoke node for reading the LabVIEW version but my development environment is 2011, it will say the VI was made with 2013. But if I have a project saved in 2013, and use the invoke node to read the version, and my development machine is 2011, I get an error saying File version is later than the current LabVIEW version error 1125.
Is this a bug? I mean I can read the project file as text and parse it with a XML parser to find the version. So why does this function choke and die when trying to read newer file versions, but a VI and Library can be read no problem?
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.
Solved!
Go to Solution.

This was a bug in the "Project.Get File LabVIEW Version" method. It was fixed in LabVIEW 2012.
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

How to convert llb from LabVIEW version 8 to 7.1

Can someone tell how to convert the llb from LabVIEW version 8 to version 7.1?
I hope to sent the program to the others, but the other side are using LabVIEW version 7.1 but not version 8.0.
I know I can save to VI file as previous version, but it contains severals of VI in the library, it is quite time consuming.
Can everyone sugguest any method or solution to solve my problem.
Thanks.

Hi anson,
it will run also in LV7.1 - but you should check those warnings (probably things not/differently supported by LV7.1...) anyway!
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Labview 7 crashes when opening an earlier Labview version VI

Hello guys. I am using Labview 7 professional edition. The labview crashes when opening an earlier labview version VI. The error message I'm getting is just "Labview has encounted a problem and eneds to close. We are sorry for the inconvenience." The VI contains a few Tag SubVIs, and It is written with an earlier version of Labview(BridgeView is what it was called).
Do anyone have any ideas that how I can fix this bug? It's going to be a great help. Thank you very much.

Hello,
LabVIEW should not be crashing in this situation. Now, does this happen for other similar VIs too? It could be possible that a particular VI is corrupt. Also could you post your VI here so that I can try and reproduce the problem at my end.
Regards,
Chetan K
Application Engineering
National Instruments

Lvwutil32 version too early to covert to current LabVIEW version?

Hi all,
I am looking to control the windows panel with some of the useful vis stored inside the lvwutil32 lib. However when I tried to open the vis inside the library, an error message saying that the vi version (4.0) is too early to be converted to my current LabVIEW version (8.5.1).
Is there anyway to reconvert the vi that my current LabVIEW can use? It is a great shame as from the readme that comes with the lvwutil32, it seems that there are a lot of useful vis that I would find very useful for my projects.
Hope someone could provide some help on this. Thanks!
Solved!
Go to Solution.

                       Hello,
                       I am having the same problem as YuanGe(the topic owner). I wanna open a file from the 5.1.1 LABview version on my LABview 8.6 and occurs the same error message.
                      I would be very grateful, if anybody could help me.
                      Thanks.
                      ps: The file is just down here.
Attachments:
ag8614x.zip ‏2795 KB

Labview Merge Problems

I have LVMerge setup to integrate changes with my version control package and it works fine, if slow ... most of the time.
For some reason, with some VI's (especially larger ones), it refuses to "resolve" conflicts.
I click on Choose Theirs, windows flash around, the hourglass comes up, I get focus back, and nothing seems to have happened. The conflict is still marked as unresolved. Same for choose base or choose yours. Even on conflicts that were auto-resolved, I can't go back and choose a different resolution.
I don't think it's a setup problem because this works fine on other VI's. This doesn't seem to be a commonly used feature, there aren't a lot of forum posts on it, but I thought I'd throw it out there ...
Regards,
Mike
Attachments:
MergeProblem.png ‏38 KB

This can be a version-dependent issue. What LabVIEW version and operating system are you running?
Ravi A.
National Instruments | Applications Engineer

Open labview versions till 7.x with 8.5

I've update my labview version for 8.5. Uninstalling the previous version in other to avoid some complications in the future that can be caused by the mix of versions (that's what I think).
But the first problem that I've found it's that I can open vi's made on versions till 7.x.
In this specific case. i can't open the labview_win_util32.zip.
How can I turn around this problem without installing old versions of labview?
Software developer
www.mcm-electronics.com
PS: Don't forget to rate a good anwser ; )
Currently using Labview 2011
PORTUGAL

Jorge Amaral wrote:
Uninstalling the previous version in other to avoid some complications in the future that can be caused by the mix of versions (that's what I think).
Hi Jorge,
That's an interesting problem that you posted... Glad you found a solution.
As for multiple LV installations, I have on one PC LV7.0, LV7.1, LV8.2 and LV8.5. Furthermore, you can open different releases at the same time (ie: work on both LV7.1 & 8.2 at the same time). They do not seem to interfere with one another and I think that it's rather common to have multiple installs. So theres really no need to remove a past installation when upgrading to a new (major) release..
RayR

A solution for Secure Static Versioning problem in 1.5.0_10

Hi,
I have JRE 1.3.1_09 and 1.5.0_10 on my computer and I think I have solved static versioning problem.
My test computer:
- Windows XP sp2
- Internet Explorer 7 (on another computer also IE 6)
- Firefox 2.0.0.1
- JRE 1.3.1_09
- JRE 1.5.0_10
I. Solution for Internet Explorer 6 and Internet Explorer 7
1. Edit registry and add:
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Deployment\Policy
DWORD: EnableSecureStaticVersioning = 0 (Hex)
2. Restart browser if started.
3. Start web page with java applet.
II. Solution for Firefox 2.0.0.1:
1. Install 1.3 JRE in the same parent directory as 1.5 JRE.
Because default default installation path for 1.5 JRE is C:\Program Files\Java\jre1.5.0_10 you need to modify
1.3 installation path from default C:\Program Files\JavaSoft\JRE\1.3.1_09 to C:\Program Files\Java\jre1.3.1_09
After installation check out that "bin" directory is in the following path:
C:\Program Files\Java\jre1.3.1_09\bin
2. Install 1.5 JRE in default installation directory: C:\Program Files\Java\jre1.5.0_10.
After installation check out that "bin" directory is in the following path:
C:\Program Files\Java\jre1.3.1_09\bin
3. Restart browser if started.
4. Start web page with java applet.
Note: HTML page must use <object> tabs for Internet Explorer or <embed> tabs for any other browser (e.g. Firefox). You need to specify correct classid in object and/or embed tag.
P.S. If anyone would like to discuss with me send me an e-mail to [email protected], but please post question to forum and just mail me a link to forum. I will write my answer to forum.
Hope this helps,
Grofaty

I have been trying to find a solution for this issue at our organization for over 6 months. Finally, we have a work around to run multiple java versions for newer and aging java apps.
Thanks,
Adunlow

How to upgrade labview version 7 to version 8

Hi,
1. I wish to know how to upgrade labview version 7 to version 8?
2. If I save my VI under labview 7, how can I run in labview 8 and back to labview 7. What are the steps needed?
Ridwan

Yes, the option that Mike is speaking of is called File » Save for Previous Version ....
LabVIEW 7 files will automatically open with LabVIEW 8, you don't need to do anything special.
Kameralina
Ask NI (ni.com/ask)
Search The KnowledgeBase
NI Developer Zone
Measure It. Fix It. ni.com/greenengineering/
NI Vision ni.com/vision/

Version problem in DMS

Hi All,
In DMS
When i create a document with bapi_document_create2 it is creating the document with what i have given the inputs
documentnumber
documenttype
documentpart
documentversion
but version problem is there . Ex: if i give version as 03 but is creating the docuemnt with version from 01 . next if i give 10 as a version it is creating the document with version 02...like that..
Please advice me .. i want to create the document with the version what iam giving.
Regards,
RSK

Hi,
Transaction Code: SE18
Selecting the radio button "BADI name" and enter "DOCUMENT_NUMBER01" in the text box to right to see the definition.
The method is: DOCVERSION_CHECK
Hope this helps.
Regards,
Benu

Sypris Teslameter Driver_too early to convert to 8.5 labview version

I am new to labview (8.5) programme and trying to use it to run my setup. I connected the Gaussmeter/Teslameter (FW Bell Sypris 6010) to the computer using serial port and RS-232 cable and used the driver (from the company) for this type of devices in order to allow labview to communicate with this device but there is always an error when I try to access the device through labview. This error says:
"VI version is too early to convert the current LabView version"
I would really appreciate any help in getting this solved.
Many thanks
Hadiq
Islam means peace
Solved!
Go to Solution.
Attachments:
FWB6010.zip ‏412 KB

Thanks for your suggestion. I did it and hope to get it sorted.
Many thanks,
hadiq
Islam means peace

OCCI version problem

Hi,
I am having a version problem with 9i.
How can i compile OCCI with 9i database installetion?
Which library would i need?
my server is a SOL-Sparc-64 machine
and oracle database server is installed there versiion oracle 9i 32bit.
I tried to compile but it gives me error like....
Undefined first referenced
symbol in file
main /usr/local/lib/gcc/sparc-sun-solaris2.9/3.4.2/crt1.o
__1cG__CrunKpure_error6F_v_ /data/Indranil/prasenjit/clientlib/libocci.so
__1cDstdbC__RTTI__1nDstdMlength_error__ /data/Indranil/prasenjit/clientlib/libocci.so
__1cDstdMout_of_range2T6M_v_ /data/Indranil/prasenjit/clientlib/libocci.so
__1cDstdMbasic_string4Ccn0ALchar_traits4Cc__n0AJallocator4Cc___2G6Mpkc_r1_ /data/Indranil/prasenjit/clientlib/libocci.so
__1cG__CrunIex_alloc6FI_pv_ /data/Indranil/prasenjit/clientlib/libocci.so
__1cG__CrunIex_throw6Fpvpkn0AQstatic_type_info_pF1_v_v_ /data/Indranil/prasenjit/clientlib/libocci.so
__1cDstdMbasic_string4Ccn0ALchar_traits4Cc__n0AJallocator4Cc___2G6Mrk1_r1_ /data/Indranil/prasenjit/clientlib/libocci.so
__1cDstdMbasic_string4Ccn0ALchar_traits4Cc__n0AJallocator4Cc___2t6MpkcIrkn0C__v_ /data/Indranil/prasenjit/clientlib/libocci.so
__1cH__rwstdRexcept_msg_string2t6MIE_v_ /data/Indranil/prasenjit/clientlib/libocci.so
Please tell me how to do it.
Edited by: user652233 on Oct 16, 2008 1:18 AM

Hello,
I am trying to compile my C++ code (using OCCI) on Sun Solaris 5.9 (SPARC64PLUS) environment.
We have compiled and tested it on RHEL 5 Linux.
The Oracle (10g R3) database is on RHEL 5 server while OCCI/C++ application would be running on Sun Solaris 5.9 server.
Since we have no Oracle installation on the Sun Solaris 5.9 server, there are no OCCI related libraries on this server and hence we are not able to compile our C++ code on Sun Solaris 5.9
Can someone help me on how/where to download OCCI libraries (compile time as well as run time) for Solaris 5.9 ? I could find only Windows and RHEL versions of OCCI libraries on the Oracle website.
Also, how stable is OCCI on Solaris 5.9 ?
Regards,

Eye Diagram using Labview version 8.6 and Digitizer 5922

I am trying to implement an eye diagram for some analysis. I have Labview version 8.6 and NI PXI Digitizer 5922. Is it possible to do some eye diagram analysis using this hardware/software. Do I need a specific toolkit for this?

To answer your questions in order:
Yes, you can and No you don't.
Remember that an eye diagram is basically just an XY plot of one input channel against another. For example, amplitude vs phase.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Labview version problem?

Similar Messages

Maybe you are looking for