Convert VI Labview 5.1 to Labview 2011

Hi.
I've attached three VIs (within a zip file) I can no longer access due to version conflicts.
I would really appreciate a conversion given I do not have the intermediate software.
-Matt
Solved!
Go to Solution.
Attachments:
connectionstoolkitvis.zip ‏53 KB

There's a library missing, but here's the VIs converted to 2011.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
connectionstoolkitvis.zip ‏53 KB

Similar Messages

I want to convert my source code in Labview 5.1 to labview 2011

HI
I want to convert a labview program which is in labview 5.1 to labview 2011 version
i am not able to open the program in the 5.1 version.
if there is no way to convert it ,then can you tell me if 5.1 version is avialable online that is compatible with the windows7 .?
thanks
Attachments:
plant.vi ‏31 KB
PID.vi ‏104 KB
integration3.vi ‏18 KB

Post your request in this Version conversion Board
The best solution is the one you find it by yourself

Conner LabVIEW 3.1 to LabVIEW 2011

Hi, I am a senior student in UT Arlington. I get a LabVIEW file from my professor. When I try to open it with LabVIEW 2011, it says VI version is too early to convert to the current version. LabVIEW load error code 10: VI version (3.1) is too old to convert to the current LabVIEW version (11.0.1 f2). I attach the VI with this message. I wonder if anyone can help me convert the VI from version 3.1 to the current version. I will be greatly appreciate it.
Attachments:
HP8510A.LLB ‏2811 KB

Hi everyone, im newest of this.
I have one problem with version 3.1 to version 7.1
Anyone can help me to convert an library of 3.1 to 7.1 or 8.5 or 2013?
Thats error said:
"An error ocurred loading VI verifiy information.vi.
LabVIEW load error code 10: VI version (3.1) is too old to convert to the current LabVIEW version (7.1)
Thanks to all.
Attachments:
ADVCLASS.LLB ‏1075 KB

CIN: Converting a C String to a LabVIEW String

Hi all,
I have been developing CINs in Microsoft Visual C++ 6.0 for LabVIEW as
project needs. However, I am having a problem with converting a C String
to a LabVIEW String in CIN.
I used two ways to try to make the conversion work that were LStrPrintf
and MoveBlock as stated as following:
1. LStrPrintf
#include "extcode.h"
#include "hosttype.h"
#include "windows.h"
struct teststrct{
const char* test;
struct teststrct testinstance;
typedef struct {
LStrHandle test
} TD1;
CIN MgErr CINRun(TD1 *testcluster, LVBoolean *Error) {
char *tempCStr = NULL;
strcpy(tempCStr, testinstance.test); // this would cause LabVIEW crash!
LStrPrintf(testcluster->test, (CStr) "%s", tempCSt
r);
// but if I assigned tempCStr as tempCStr = "test", the string value
"test" could be passed to LabVIEW without any problems.
2. MoveBlock
#include "extcode.h"
#include "hosttype.h"
#include "windows.h"
struct teststrct{
const char* test;
struct teststrct testinstance;
typedef struct {
LStrHandle test
} TD1;
CIN MgErr CINRun(TD1 *testcluster, LVBoolean *Error) {
char *tempCStr = NULL;
int32 len;
tempCStr = (char *)&testinstance.test; //since strcpy didn't work, I
used this way to try to copy the const char* to char*.
len = StrLen(tempCStr);
if (err = NumericArrayResize(uB, 1L, (UHandle*)&testcluster->test,
len))
*Error = LVFALSE;
goto out;
MoveBlock(&tempCStr, LStrBuf(*testcluster->test), len); // the string
was able to passed to LabVIEE, but it was unreadable.
out:
Did I do anything wrong? Any thougths or suggestions would be very
appreciated!

Thank you so much for your response, Greg. However, I still have problem after making
corresponding modification for LStrPrintf approach:
int32 len;
char tempCStr[255] = "";
strcpy(temCStr, testinstance.test);
len = StrLen(tempCStr);
LStrPrintf(testcluster->test, (CStr) "%s", tempCStr);
LStrLen(*testcluster->test) = len;
LabVIEW crashes. Any ideas?
Greg McKaskle wrote:
> The LStrPrintf example works correctly with the "test" string literal because
> tempCStr= "test"; assigns the pointer tempCStr to point to the buffer containing
> "text". Calling strcpy to move any string to tempStr will cause
> problems because it is copying the string to an uninitialized pointer,
> not to a string buffer. There isn't anything wrong with the LStrPrintf
> call, the damage is already done.
>
> In the moveblock case, the code:
> tempCStr = (char *)&testinstance.test; //since strcpy didn't work, I
> used this way to try to copy the const char* to char*.
>
> doesn't copy the buffer, it just changes a pointer, tempCStr to point to
> the testinstance string buffer. This is not completely necessary, but
> does no harm and is very different from a call to strcpy.
>
> I believe the reason that LV cannot see the returned string is that the
> string size hasn't been set.
> Again, I'm not looking at any documentation, but I believe that you may
> want to look at LStrLen(*testcluster->test). I think it will be size of
> the string passed into the CIN, and it should be set to len before returning.
>
> Greg McKaskle
>
> > struct teststrct{
> > ...
> > const char* test;
> > ...
> > };
> >
> > struct teststrct testinstance;
> >
> > typedef struct {
> > ...
> > LStrHandle test
> > ...
> > } TD1;
> >
> > CIN MgErr CINRun(TD1 *testcluster, LVBoolean *Error) {
> >
> > char *tempCStr = NULL;
> >
> > ...
> >
> > strcpy(tempCStr, testinstance.test); // this would cause LabVIEW crash!
> > LStrPrintf(testcluster->test, (CStr) "%s", tempCStr);
> > // but if I assigned tempCStr as tempCStr = "test", the string value
> > "test" could be passed to LabVIEW without any problems.
> >
> > ...
> > }
> >
> > 2. MoveBlock
> >
> > #include "extcode.h"
> > #include "hosttype.h"
> > #include "windows.h"
> >
> > struct teststrct{
> > ...
> > const char* test;
> > ...
> > };
> >
> > struct teststrct testinstance;
> >
> > typedef struct {
> > ...
> > LStrHandle test
> > ...
> > } TD1;
> >
> > CIN MgErr CINRun(TD1 *testcluster, LVBoolean *Error) {
> >
> > char *tempCStr = NULL;
> > int32 len;
> > ...
> >
> > tempCStr = (char *)&testinstance.test; //since strcpy didn't work, I
> > used this way to try to copy the const char* to char*.
> > len = StrLen(tempCStr);
> >
> > if (err = NumericArrayResize(uB, 1L, (UHandle*)&testcluster->test,
> > len))
> > {
> > *Error = LVFALSE;
> > goto out;
> > }
> >
> > MoveBlock(&tempCStr, LStrBuf(*testcluster->test), len); // the string
> > was able to passed to LabVIEE, but it was unreadable.
> > ...
> >
> > out:
> > ...
> >
> > }
> >
> > Did I do anything wrong? Any thougths or suggestions would be very
> > appreciated!

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

Seamlessly migrating Labview 6.1 to Labview 10

Hi,
My company have several legacy projects that were written in Labview 6.1.
We recently bought Labview 2010 and tried to convert the projects over and found several issues:
1) Report Toolkit changes
    Write PNG (word). vi
    Write JPEG (word) . vi
    were missing
2) Received the following warnings:
   Labview changed a constant that was wired to a Case Structure to a hidden control to maintain compatability with Labview 7.1 and earlier
Is there an easy way to port from Labview 6.1 to Labview 2010?
I am not a Labview developer myself so pardon me for any silly questions.
Thanks & Best Regards

Generally upgrading over 4 versions will result in some warnings and some things broken, as you have observed. First thing is to save the warnings to a file so you can go back through it as often as necessary.
Use the dialog which comes up when you try to run the broken (upgraded) VI. That will take you with one click to places where something is broken. Systematically work through those. Often replacing an obsolete subVI with one from the current palette takes care of most of the problem. You may need to reconnect wires if the connector pane is different. For some replacements you may need to change datatypes on inputs. Examples include arrays to waveform or numerics to enums. As you do this check the functionality of the replacements to see if anything has changed which will affect the performance of your program.
Then work through the warnings list. Verify that the warning does not cause undesired behavior in your program. If it does, then you need to change something. If it does not, make a note to consider modifications to get rid of whatever the warning was about after everything is fully functional.
Although it does not sound like this has occurred in your case, consider whether it would be better to use the old program as a guide to establish a test or performance specification. Use that to write a new program, probably with a better architecture and taking advantage of new features. For example the old program might use lost of sequence structures and local variables, making it difficult to modify or even to understand. The new one might be written using a Producer/Consumer architecture and LVOOP techniques. Rewriting may not take much longer than trying to "fix" the old program and results in a program which takes full advantage of new features and techniques.
I am planning a rewrite this summer or fall in LV 2010 or LV 2011, depending on timing, of a program whose ancestor was written in LV 1.2 in 1988-89. The kind of rewrite I described above has already been done twice on this program.
Lynn

Upconvert VI to Labview 8.5 or labview 10.

Please help me upconvert the following VIs to Labview 8.5 or Labview 10. I tried posting in the upconvert VIs thread but did not get any result. Please help me for the same
Jay
Solved!
Go to Solution.
Attachments:
curve_tracers.zip ‏354 KB

You did not start a new thread for your problem in the conversion board, but added to an existing thread that was already solved. This makes it difficult to find. As has been mentioned, you should start a new thread for each conversion.
No, I cannot help. To convert from 5.1.1, we need somebody that still has LabVIEW 8.2 installed.
You originally posted on Friday afternoon where most people get ready for the weekend.
There is typically not much traffic here over the weekend.
Today is a federal holiday in the US so there might also be less activity overall.
I think you just need to be patient. Good luck!
LabVIEW Champion . Do more with less code and in less time .

Upconvert from Labview 5.1 to Labview 2010

Please convert these VIs (in zip) from labview 5.1 to Labview 2010
Solved!
Go to Solution.
Attachments:
c3d_reader_labview_b.zip ‏864 KB

Attached as 8.2, which you can open.
Note: The VIs in the "Files IO" folder have been deprecated. You should replace them with the single Read from Binary File function.
Attachments:
C3D Reader.zip ‏706 KB

Downconverter for labview 11.0 to labview 8.6 vi file

Please help me convert the vi file below from labview 11.0 to labview 8.6 version.
Thank you
Attachments:
dbltomatrix.vi ‏17 KB

Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
dbltomatrix.vi ‏14 KB

How to open labview program with Quit Labview function inside?

Hi Any idea how to open labview program with Quit Labview function inside?
I forgot to add and set the condition of the type for this program.
If the program is an application, it would close straight away.
If it is still labview work, it will go straight to editing program without closing.
So I need to recover, open it and make some changes.
Clement
Solved!
Go to Solution.

Put the VI in a project and open it from there, then it shouldn't autorun. You can use App.kind property of application to decide whether to close or not.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

From Labview 9.0 to Labview 8.2.

I need a conversion, if possible, from Labview 9.0 to Labview 8.2.
Thank you for the support
Attachments:
Write Std Out with Redirection.vi ‏24 KB

attached
WARNING: There is a bug in LabVIEW 8.2 where you cannot use the error cluster to chain together the Call Library Function Nodes. You will need to either create wrapper VIs for each CLFN or you will need to use case structures around each call.
Attachments:
Write Std Out with Redirection.vi ‏28 KB

UDP Error when upgrading from Labview 8.6 to Labview 2009

I recently updgraded from Labview 8.6 to Labview 2009. I am writing an application to stream data to disk from UDP. My VIs run just fine in Labview 8.6, but when I try to run them in Labview 2009 my UDP read times out despite being able to monitor UDP traffic and see that the data is being sent and nothing in the file is changed from 8.6 to 2009. Is there a known issue related to this?

How are you moniting the UDP traffic? Have you verified that the port you are trying to use is actually available? When you installed 2009 there may have been an additional service installed that may have used the port you're trying to use. If you're running on Windows you can use the command "netstat -n -o -a" to see all the ports that are currently in use, as well as the process ID that has that port open.

Can I run 64 bit LabVIEW and 32 bit LabVIEW on the same machine?

If I have a 64 bit OS (Windows 7 64 bit or Server 2008 64 bit) can I install and run 32 and 64 bit LabVIEW on the same machine?
John

LabVIEW 64-Bit vs. 32-Bit Applications FAQ
Q. Can I have both LabVIEW 32-bit and LabVIEW 64-bit installed on the same 64-bit machine?
A. Yes.
The FAQ will likely answer other questions you have regarding the restrictions and issues you will have with having both versions and compiling in one vs the other.

I have written a binary file with a specific header format in LABVIEW 8.6 and tried to Read the same Data File, Using LABVIEW 7.1.Here i Found some difficulty.Is there any way to Read the Data File(of LABVIEW 8.6), Using LABVIEW 7.1?

I have written a binary file with a specific header format in LABVIEW 8.6 and tried to Read the same Data File, Using LABVIEW 7.1.Here i Found some difficulty.Is there any way to Read the Data File(of LABVIEW 8.6), Using LABVIEW 7.1?

I can think of two possible stumbling blocks:
What are your 8.6 options for "byte order" and "prepend array or string size"?
Overall, many file IO functions have changed with LabVIEW 8.0, so there might not be an exact 1:1 code conversion. You might need to make some modifications. For example, in 7.1, you should use "write file", the "binary file VIs" are special purpose (I16 or SGL). What is your data type?
LabVIEW Champion . Do more with less code and in less time .

How to open labVIEW 8 file in LabVIEW 7.1

Hi
I want to open a LabVIEW 8 file into LabVIEW 7.1 version? when i tried to open there is an error appiers and I couldnt open it so please give suggestion how to open it..
Thank you

If you open the vi with a higher version of LV and save it, you can't open it with the earlier version, as I said before, because the vi is no backward compatible.
What you could do is open the vi with LV8.0 and browse the menu to File >> Save for Previous Version. Then just follow the instructions given on the dialogs.
Using LV8.0
Don't be afraid to rate a good answer...

How to open program developed using labview 8.2 in labview 7.1?

Dear friends,
I need to open program developed by using labview 8.2 in labview 7.1.help me in this regard?

In order to open it up, you have to backsave it to 7.1. You would need to first save it to 8.0 and 8.0 can save it as a 7.1 file. Attach your VI and ask if someone can do it for you if you don't have the intermediate version.

Convert VI Labview 5.1 to Labview 2011

Similar Messages

Maybe you are looking for