LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Is Labview 2009 Supposed to be backwards Compatible?

Solved!
Go to solution
We developed a set of VI's in Labview 6.1, and they've been compatible and functional with all versions of Labview up to 2009.  Is 2009 not backwards compatible?
0 Kudos
Message 1 of 13
(6,222 Views)
I would suggets opening your VIs in a previous version of LabVIEW, say 8.0, and save them. You should be able to open them in 2009 then. As for backward compatibility NI has a fixed number of versions back that they will support. I believe that number is 2 major versions back. I would have to confirm the actual number though.


Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
0 Kudos
Message 2 of 13
(6,217 Views)

 

In the first sentence, you say that your VIs are compatible with LabVIEW 2009? Does that not answer your question? 😉

 

 

More details here.

Message 3 of 13
(6,215 Views)

Christian, I think what was meant was that they were compatible upto 2009, but that the "In Range and Coerce", but that "include upper limit" hadn't been selected.

 

As to backwards compatible, if it has worked for the versions up to 8.6 there shouldn't be any problems of compatibility other than actually loading, which would be fixed by opening the older vi in 8.2+ and saving at that version.

Putnam
Certified LabVIEW Developer

Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5


LabVIEW Champion



Message 4 of 13
(6,200 Views)

Saving in 8.2, and then re-opening in Labview 2009 helped some of the vi's, but the Writing vi's are still give errors:


 Output Buffer iIs Full Value Not Sent!.   

 

Should I try opening the drivers in 8.6 (If yes, do you have a link to an eval. version of 8.6)?

 

I've added the files if anyone would like to take a look.  They are intended to be unzipped under the

 

C:\Program Files\National Instruments\LabVIEW???\instr.lib

 

directory.  If you run the file "WriteDemo.vi", you'll see the error message "Output Buffer Is Full.." which is not supposed to happen. 

 

Thanks for your help so far. Unfortunately I have almost no experience developing with Labview.

Download All
0 Kudos
Message 5 of 13
(6,162 Views)

The drivers are used to talk to Qlarity which is a free download here:

http://www.qsicorp.com/engfiles/Qlarity%20Foundry/QlarityFoundry2_60_setup.exe

0 Kudos
Message 6 of 13
(6,158 Views)
I tried opening up the vi's in Labview 8.6, and re-saving them all.  Then opening them in Labview 2009.  I'm still having the problem with the Write.vi.  It looks like the codes going to need to be changed to make it compatible.
0 Kudos
Message 7 of 13
(6,114 Views)

QlarityEng wrote:
I'm still having the problem with the Write.vi.

There are about 16 different write_____.vi. Can you narrow it down a bit?

0 Kudos
Message 8 of 13
(6,108 Views)
To reproduce the problem, run the Write Demo.vi, under the Demo directory and press play.  If it's working correctly something will be sent out the comport.  When it's not working (in 2009), it displays the output buffer full error.
0 Kudos
Message 9 of 13
(6,104 Views)

Is the two versions back compatibility applicable if I open my .vi in 8.6, it works, I save it, and then re-open in Labview 2009?

 

I have a customer who is planning to upgrade there system to Labview 2009 using these vi's, so any help would much appreciated.  They had upgraded to 2009 which broke compatibility so they downgraded  back to 8.6.

0 Kudos
Message 10 of 13
(6,042 Views)