LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Is it possible to run a LabVIEW LLB from Version 8.6.1 on a Version 8.6 platform?

We need to move a Version 8.6.1 LLB to a Version 8.6 platform. Assuming our 8.6.1 LLB does not use any 8.6.1 specific features, can I convert it to run under LabVIEW 8.6? Thanks!

0 Kudos
Message 1 of 4
(2,803 Views)

As you said you dont use 8.6.1 features, it is possible to use.

 

Even otherwise, it should be possible to use as such because in LV, always a X.Y.z is a minor version/revision of/over X.Y, so it should integrate/work seamlessly both ways.

 

Only thing we need to keep in mind is code in LV X.Z cant be opened in LV X.Y, where Y<Z (like 8.6 & 8.5).

 

Also, code in LV A.B wont open in LV X.Y, where A>X (like 8.0 & 7.1).

- Partha ( CLD until Oct 2027 🙂 )
0 Kudos
Message 2 of 4
(2,789 Views)

One thing as a tip, don't usean LLB as a way to develop VIs in. Only use them for distributing code. If one of your VIs become broken, your whole LLB will be broken.

 

Ton

Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 3 of 4
(2,785 Views)

TCPlomp wrote:

One thing as a tip, don't usean LLB as a way to develop VIs in. Only use them for distributing code. If one of your VIs become broken, your whole LLB will be broken.

 

Ton


Actually this is not entirely true. The VIs itself are independant entitities in an LLB, so the brokeness of one of the VIs does not automatically have any influence on other VIs inside that LLB.

 

That said, the VIs do get written to the LLB individually, and although writing changes to an LLB is always done on a shadow copy of the LLB, which only replaces the original LLB AFTER the writing has been finished without any errors, there is of course always a chance that writing of a VI itself goes havoc in some ways. This could in principle destroy the integrity of the LLB data structure, and in such a way make the LLB as whole inaccessible. But because of the shadow copy technique it is a rather seldom event.

 

Rolf Kalbermatter

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 4 of 4
(2,769 Views)