LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

mixing libraries

Solved!
Go to solution

Hello everybody!!

 

I am looking for some good practise advices. I am doing a Labview Project using the 8.6 version. I can develop the new vi just using two old libraries done in the 7.1 version, then I think the solution is not difficult to perform so I would like to pay attention to the good practises to get a tidy project. The problems are that I am not really used to libraries and the change of versions.

 

First at all, I was thinking on create a project. I want to keep the main vi of one of the libraries and modified it using the other library. So I create the project, I add the main vi and all the subvis that it involves "appear" in the project that dependencies (without adding them directly). Is that a good idea or maybe is it better to add them to the project?Or just adding the libary?

 

Basically the modifications I have to do are to substitude some of the subvis of the main library for others of the "secondary" library. The old and the new subvis have different types of inputs and outputs, and also they are located in very low in the hierarchy, so some changes have to be done in other subvis and in the main vi.

 

Then, should I add the "secondary" library in the project?Even if I am not using the main subvi of the other library, should I add it?Should I replace the subvis directly in the upper level of the hierarchy or just adapt the front pannel and the block diagram of the old subvi, keeping them in hierarchy?

 

Wow, I am starting to think that try to follow good practises is not such a good idea 🙂

 

Thank you

0 Kudos
Message 1 of 6
(3,683 Views)
Solution
Accepted by topic author 1000a

Hi 1000a,

 

I've been reading your post. At first I would like to make one big remark:

Please use the VI's in your Project Explorer, and not LLB's.

LLB's are perfectly suited for distributing your application, but not for storage.

 

My advice for your application: get the VI's you need from the LLB, safe them on your harddisk and add them to your project. For development it is much easier to use the VI's seperated from the LLB's. Once you have finished your project, you can consider building an LLB for distribution.

 

Next to this, the use of LLB's can cause additional errors, since they can get corrupt (which means you cannot get the data from it).

 

Hope this will provide you with some additional information on how to setup your new project.

 

Regards,

 

Peter S.

0 Kudos
Message 2 of 6
(3,663 Views)

Hello Peter.

 

First at all, thank you for your answer. Now, I know what is the propuse of the LLB's

 

I would like to ask you a question, maybe it's very basic...anyway. In your post, you said that I should save the VI's on the harddisk, then, is there any function to take the VI's from the LLB and save them (like the unzip function in winrar) or  do i have to open the LLB, select the VI's and copy them in a folder? Because trying to do the last opcion, there is a pop-up window with a fatal mistake from a cpp file.

 

Thanks

0 Kudos
Message 3 of 6
(3,647 Views)

More info about the mistake I was talking about: It is a fatal internal mistake in the memory.cpp. And it says Labview 7.1.1 (in which it was develop but I modified them a little using the 8.6)

 

Thanks

0 Kudos
Message 4 of 6
(3,645 Views)

Hi 1000a,

 

Sorry for the delay in answering.

 

If you want to get the VI's from your LLB, you have to start the LLB Manager from LabVIEW and browse to the LLB file(s).

 

Than you right click on the LLB file and select convert (see "Select File.PNG").

Select File.PNG

An Conversion Options window will appear like the one in the file "Conversion Options.PNG".

Conversion Options.PNG

 

Here you can make some adjustmens, and after clicking on the "Convert" button, the LLB will be converted to a folder with the VI's.

 

I hope this will help you with your application!

 

Regards,

Peter S

Message Edited by Peter S on 06-05-2009 11:02 AM
Message 5 of 6
(3,596 Views)
Thank you Peter S. That was exactly the solution!
0 Kudos
Message 6 of 6
(3,579 Views)