LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview 7.1 to labview 2015

Hello,

I hope you can help me with my following problem. I have a project in university, in which I have a test bench with electrical motors. The test bench runs with an old computer with labview 7.1. Now I need to get the whole project on a new computer with labview 2015. I'm new to Labview and it shows a lot of errors but just on the new computer. Most often the errors appear, because I relink the Sub VI and then the wires are not connected anymore or the data type is not correct.

The question is, does anyone knows how I can get my project from labview 7.1 to labview 2015? If I just copy paste it, it shows the error.
Thank you for your help.

(I'm not that good in english and I really don't understand labview, so i hope you can understand my problem and maybe help me)

0 Kudos
Message 1 of 17
(5,937 Views)

Hi Student,

 

Most often the errors appear, because I relink the Sub VI and then the wires are not connected anymore or the data type is not correct.

Which errors do appear?

Why do you need to relink subVIs? Which subVIs?

 

The question is, does anyone knows how I can get my project from labview 7.1 to labview 2015? If I just copy paste it, it shows the error.

Usually you create abackup of this old LV7.1 VIs. Then you open them with LV2015 and it should be ok…

"Should" means: there are ~10 years between both LabVIEW versions and a lot changed in LabVIEW and the compiler. So depending on those old VIs APIs could have been changed and you need to relink/rewire/recreate some subVIs…

 

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 17
(5,929 Views)

Hello GerdW,

following errors appear:

- SubVI '...': Recursive reference in non-reentrant VI ( the solutions google showed me didn't help )

-Bad linkage to SubVI ( the I try to relink but i can't rewire, because the data type is not correct anymore and I don't get why )

- Errors about data types, like : You have connected a scalar type to and array of that type and I don't know why it runs in the older version but not now anymore

 

Thank you a lot for your help

Best regardings

Student

0 Kudos
Message 3 of 17
(5,925 Views)

Hi Student,

 

when you need more help you need to supply more information…

 

Can you upload the old VI(s)? (ZIP them when there are more than just two.)

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 17
(5,920 Views)

There were major changes to LabVIEW between Versions 7 and 8, with further significant improvements coming as Version 8 "matured" (things like the LabVIEW Project).  One of the most significant changes, and a source of great pain until you realize you should really "just start over and recode this from scratch" is the change from Traditional DAQ (very complex, hard to program, harder to understand) and DAQmx (easy to learn, flexible, powerful).

 

I agree with GerdW that to get any meaningful help (who knows, one of us might just do most of the hard work for you) you have to put all of the relevant VIs in the Version 7.1 source in a folder (if you have sub-folders that help organize the original code, keep them intact, but get everything into a "Version 7-1" folder), compress this folder, and attach the Zip file.  We can then take a look and provide relevant help.

 

Bob Schor

 

P.S. -- there is also a Version Conversion Forum on this site, which I think of as asking to create "older" Versions from "Modern" LabVIEW, but it seems that it may also function to convert from "old" to "Modern".  If you submit your code there, then I presume someone knowledgeable will convert it for you ...

0 Kudos
Message 5 of 17
(5,877 Views)

@Bob_Schor wrote:

P.S. -- there is also a Version Conversion Forum on this site, which I think of as asking to create "older" Versions from "Modern" LabVIEW, but it seems that it may also function to convert from "old" to "Modern".  If you submit your code there, then I presume someone knowledgeable will convert it for you ...


Correction.  That forum is for converting newer versions to older, or really old versions that can't be opened in newer LabVIEW.  Since you can open LV 7.1 code in 2015, your code doesn't qualify.  That forum is NOT meant for fixing people's code problems as a result of the conversions.

0 Kudos
Message 6 of 17
(5,871 Views)

If you have a version of Labview that is somewhere in-between 7.1 and 15 (i.e. 2010 or 2012), you might try a stepped upgrade of the code.  Open it up in 2010, save it and then open it in 2015.  Baby steps.

aputman
0 Kudos
Message 7 of 17
(5,856 Views)

Hello,

thank you for your answers! Here is my project, I hope you can help me.

If you open it, the "main programm" is called "Hauptprogramm" (German). The other VI's are in the folder "VIs_Prüfstand".

I don't really know if there are other VI's because there were like 10 projects on the computer and it was not organized well. Thank you for your help! If you need more information or if you get a solution please let me know i would be so thankful.

 

Best Regards

Student

0 Kudos
Message 8 of 17
(5,825 Views)

Hi Student,

 

as recommended before: those old VIs are using this very old "traditional DAQ" functions.

You need to replace all of them with now-standard DAQmx functions.

 

When/before you start that work I strongly recommend to create the whole program from scratch. It's far from "nice"/scalable…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 9 of 17
(5,820 Views)

I opened your VI in LabVIEW 2017.  The only errors I'm seeing are related to missing subVI's particularly NICAN and DAQ vi's in an EASYIO library.

 

Nothing about reentrancy or wrong wire data types.  So perhaps those errors are occurring in the libraries you are using that I don't have.

 

I do see lots of weird code constructs in there that could be fixed.  A scalar that gets built into a 1-D array, auto-indexed to a 2-D array. built into a 3-D array, then the sum of the array taken.  Meaning you are really only taking the sum of a 1-D array and the creation of other array dimensions was a waste of time.  Also, many 1-iteration For Loops.

0 Kudos
Message 10 of 17
(5,818 Views)