Convert 8.5 llb to 8.2 llb

Can anyone convert those 8.5 LLB to version 8.2 or older. I cannot access them with LabView 8.2
m.s.m.
Solved!
Go to Solution.
Attachments:
LC100.llb ‏818 KB
LC1_Drv.llb ‏504 KB
LC1.llb ‏413 KB

We have a thread for this: Downconvert Requests Thread. The link for it is right on the front page of the forums in the Announcements section.
In the future please post your requests there.
Attachments:
LC1 8.2.zip ‏184 KB
LC1_Drv 8.2.zip ‏198 KB
LC100 8.2.zip ‏388 KB

Similar Messages

Can't convert llb to directory

I have a pop-up keyboard llb someone shared. When I open it, the convert to directory button is disabled, as are the cut and copy buttons. I need to extract this.
Why is it doing this?
Thanks,
Jim
Solved!
Go to Solution.
Attachments:
HMI_PopUp_KB.llb ‏206 KB

In the llb manager, go up one folder, then select the llb file. Now you can convert it to a folder.
LabVIEW Champion . Do more with less code and in less time .

Convert labview 5 llb to 8.6

Could someone please convert this library (apparently from Labview 5) into a format compatible with Labview 8.6? Also, if it is possible to download labview version 8.2 (so I can do these conversions myself without bothering anyone) that would be great too. I've tried accessing some links but get am denied access. From reading prior posts, this is not uncommon.
Many thanks for any help you can provide!
Solved!
Go to Solution.
Attachments:
NetCDF_LV_5_0_x.llb ‏712 KB

Hi Samoth,
here you go (LV7.1, missing dll...)
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome
Attachments:
VLabLib.llb ‏348 KB
VLabSample.llb ‏79 KB

LV 2009 project LLB as startup vi in .exe build?

I hope I can explain my problem correctly.
I started a new project and wanted to build an .LLB and have subvi's called under these in the project as this is what I was used to doing minus the project in LV 8.2.1.
The problem is I built my GUI under the LLB but did not put any of the other vi's underneath it. So my project has 1 LLB and several vi's attached to it. The problem is when I tried making an executable it wants a startup vi(which is my LLB) and it will not allow me to put it in the startup vi column so I cannot build an executable.
I tried converting the LLB but got an error and almost lost my whole project because it deleted the LLB and did not convert it. Luckily I had a backup.
How do I make an executable when my front panel is in an LLB format?

An LLB is not a LabVIEW code-file like a VI, it is more a container file like a .zip file.
I advise you not to develop code in an LLB, just stay in a VI. The problem with developing in an LLB is that if the file structure is corrupt all the code is damaged. Since you only have one file in the LLB I see no reason to maintain the LLB.
However you should be able to select the VI inside the LLB as your startup VI.
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!

Error 1003: Running a VI inside LLB from EXE

HELP!
I have a Labview Executable which is using some "plugin drivers" provided as LLB. The drivers are loaded dynamically with "Invoke Method: Run VI". My Exe does not contain any dependency to those driver LLB's. The LLB build projects are build with vi.lib. "Disconnect type def" and "Remove unused polymorphic ...." are both unchecked. Everything worked for a while without any problems. I had one driver which is using GMath:Interpolate 1D. Now I have a second driver which is using "Interpolate 2D". Those 2 driver VI's won't load at same time. It is really strange but if I disable one, the other will load. If both are active I get error 1003 indicating that some VI is not able to run mostly because of missing dependencies. I faced that message a lot in the past but this time I don't know what else to do. I tried several combinations of building the LLB's and the exe, even included those dynamic VI's into exe but all time same. I have less hope that someone here can help me but I give it a try.
BTW, is there any chance to debug and see the exact reason why my VI won't load. When I breakpoint at "Invoke Method: Run VI" i will see that it returns 1003 but can I find out more?

I have seen this happen as well in my application's plug-in architecture. It happened with a pair of different DAQmx Read VIs in our case. I filed CAR 285388 against it. It is currently under investigation. I will put the information about your issue in the existing bug report.
Right now I don't know of any workaround.
Jarrod S.
National Instruments

In saving a viWhat's the difference as a .vi verses .llb?

Most of the .llb programs I pull up have .vi's attached or they are shelled within the .llb. I am trying to make a copy of a program I've written that includes multiple sub-vi's. I would like the copy of the program to include all sub-vi's without having to save a copy of each individual vi seperately. Any help will be greatly appreciated. Thanks in advance!

Select With Options and choose Development Distribution to create an llb with all subVIs except vi.lib files. You can then use the Edit VI Library option under the Tools menu and make your main VI Top Level. If you plan on making this distribution the master, you should be aware that source code control programs don't really handle llb files.
The llb was originally created as a means to get around the old limitation of DOS file name lengths.

How do I specify the Startup VI for a LLB in LV 8.5.1 Full?

Hi,
I recently upgraded to LabVIEW 8.5.1 from LabVIEW 7.1.1. I entered the project Build Specifications and compiled my code into a LV .llb file called "my_program.llb". I also specified the top level vi (called "main.vi") inside my_program.llb. Now I want to make "main.vi" automatically open and execute whenever the user double clicks on my_program.llb from within Windows Explorer. How can I do this in LV 8.5.1 Full?
Right now when the user double clicks on my_program.llb, the LLB Manager window opens, but "main.vi" doesn't automatically launch like it used to do back when I was using LabVIEW 7.1.1 Full.
I know it is possible to specify the Startup VI using the Professional version, but is this possible to do in the Full version?
Thanks,
Richard
Solved!
Go to Solution.

Check out this KB
Managing LabVIEW Library Files in Windows Explorer & the LLB Manager
LabVIEW 8.5 and beyond
In LabVIEW 8.5, the
option to open LLB files in Windows Explorer has been removed. However,
if you have a previous version of LabVIEW installed along with 8.5,
LLBs can still be opened through Windows Explorer if you follow the
procedure below. If you are not using another version of Labview along
with 8.5, you can change the default behavior so that an LLB that is
opened from Windows will open the top-level VI instead of the LLB in
the LLB Manager.

Call library function not finding DLL in directory where my LLBs are

I am using LabVIEW 8.6. I have a set of VIs in several LLBs. All the LLBs are in one directory. Most of my VIs are wrappers for the functions in one DLL. I was told to put my DLL in the directory where the LLBs are, and supposedly this is how the previous programmer worked (using an earlier version of LabView).
In the Call Library configuration, I have specified <dllname>.dll without a path. (This is how we want it as our VIs are an API which other programmers will integrate, so I don't know where they will put things and I can't use any absolute paths).
When I load the VIs in LabVIEW, LabVIEW can't find the DLL and asks me to located it. It is right there in the directory with the LLBs and when I double click on it everything works fine. However my absolute path to the DLL now appears in the Call library configuration, and we don't want that.
Does anyone know how to make this work? I would assume that the location of the VIs (or LLBs, in this case) would be the current directory and thus Windows would look there for the DLL. However, it seems that this is not the case (at least, in the current version of LabVIEW).
Thank you.
Batya
Solved!
Go to Solution.

rolfk wrote:
Well somebody using your library should not have to dig into your VIs and do all this on his own. Instead your library should wrap that and hide the troubles of this entirely.
That is EXACTLY what I want to do.
The error cluster was added when the dynamic path option was added. It is not useful to hide that error output so it is always there. Together with the dynamic path there was improved error handling added to the CLN. One of them is that the level of error checking during the function call (exception handling) can be specified. I would assume that some of those options can generate an error code instead of popping up a dialog as they did before and for that the error code output can be useful even in the static call case.
As to what you want to do, I would long ago
I would long ago have done a lot of things differently on this project -- but no one asked me then :-) (Good thing it wasn't me, or maybe I'd have taken offense ;-) )
have handled that with a wrapper DLL that has basically the same functions as your other DLLs and some initiliasation function that returns a pointer to a function dispatch structure based on the actual DLL you want to call.
OK, I am getting the feeling that this will be a brilliant and elegant solution when I fully understand it. I understand what a wrapper DLL is. But do you mean that each version of my product would include a different wrapper DLL (with the same name so that CLN would always work), or the same one and it would somehow be told which actual DLL I want to call? Who would decide which DLL, the VI or the wrapper DLL?
By a function dispatch structure do you mean a table of function pointers gotten by GetProcAddress, one such entry for each function?
Quite like what an object oriented function dispatch table is. Then when initilising your interface you call that initialise function and specify the interface/device type you want to use and after that all the other functions take one additional function dispatch pointer parameter as first parameter in addition to the parameters the actual function has. This function dispatch pointer would be just a pointer to a structure containing the table of function pointers for that interface and for the sake of LabVIEW would be simply a pointer sized integer.
The wrapper function then verifies the function dispatch structure pointer for validity and calls the actual function with the remaining parameters.
I think I understand what the wrapper functions need to do. But I am missing some pieces for the initialize function. It would have to do LoadLibrary and lots of GetProcAddresses -- that much I get. But I still don't understand who decides which DLL. Maybe you mean that the wrapper DLL's initialize function will get the DLL name and path from the registry, load it, try a different path if the load fails, etc. Is that what you mean? That could work very nicely. But from where would it get the registry key? From the VI? This is the part that would clearly be different for each product. I suppose that you had something in mind when you described your solution.
This is some C programming
Great! That's what I do for a living. At least I know how to do that! Hey, I should have thought of this idea!
and might require some planning and desigining of the different interfaces to facilitate this kind of dispatch technique but it will for sure pay of in the long run, and make your library even usable in earlier LabVIEW versions, as well as VB etc. without tricky dynamic loading in the high level programming environment.
Ah, see how much I don't know in LabVIEW? I didn't know this was a new feature...
Thank you for the great idea.
Batya Perlman

Labview 2013 + Windows7, can't add file to llb

Very simple, I am trying to add VI file to LLB but instead of that Labview is trying to save VI file as LLB.
New feature of LV2013? LLB's are not displaying as folders anymore? Bug?

Hi,
Could you possibly add the LLB file and the VI to a project? Then drag the VI in the project into the LLB and save the LLB.
Kind Regards,
Laurence C.
Senior Test Development Engineer
Dyson Ltd

LLB for LV8.61 to work with sample VI PXI-4351

I use LV8.61 and installed driver for PXI-4351, NI435X v252.
While I try to use sample vi came with v252 (Measure Thermocouple (with Accessory).vi), I get error for
missing LLB, vilib\DAQ\MISC.LLB\Get DAQ Device Information.vi
Indeed I can not see \LabVIEW8.6\vi.lib\DAQ folder. How I get this LLB and needed update?

Sorry for my misunderstanding. Traditional DAQ was not installed.
In my control pannel, installed software list, within NI software, it showed TDAQ744 installed.
However, it was not. I installed TDAQ744 and sample vi worked.
Thanks for help.

Convert 5.1 files to 2012 in Labview

Hello all,
Could someone please convert the attached file's that are in labview 5.1 into a file's that I can open in labview 2012.
Thank you in advance for the help.
Cheers,
Rich
Solved!
Go to Solution.
Attachments:
Dynamic Vave Train Testing (Filter).zip ‏78 KB
Valve Train Durability Testing_mag (Filter)2.zip ‏52 KB

Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
AI.LLB ‏682 KB
CUSTOM.LLB ‏369 KB

Convert Stanford DG353 DS345 VI drivers V7.1

Hi!
I downloaded VI drivers for Stanford DG535 (delay generator) and DS345 (function generator) from NI driver network.
However, it is for LabView 8.0 and above. Please help me to convert them to LabView 7.1. Two .LLB are attached.
Thank you.
Shelby Kuo
Attachments:
SRDG535.LLB ‏279 KB
srds345.llb ‏561 KB

Sure, here you go
Misha
Attachments:
SRDG535.LLB ‏368 KB
srds345.llb ‏795 KB

Convert Labview 5.0 to Labview 8.5

Can someone help me too and convert these Vi´s in a newer version. They are written in 5.1 and here we have only 8.2.
So it would be nice if someone can convert it for me.
Thanks
Nota: Proirity given to VIs
- DH RPM4 Read Pressure.vi and
- DH RPM4 Pressure Status.vi
Attachments:
DHRPM4.LLB ‏1287 KB
DHRPM4U.LLB ‏65 KB

Attached are the llb's converted to version 7.1. Version 8.5 should be able to read them
Attachments:
DHRPM4.LLB ‏1114 KB
DHRPM4U.LLB ‏56 KB

What is the eaisest way to convert an LLB to new labview version?

I have an insturment driver LLB that is a total mess now.
It started out as a LV 5.11 LLB
I am working in LV 8.5 now and LV 8.5 will not open code written in LV 5.11 (Too old)
I have tried to mass compile it in LV 8.2 but I still am running in to VI's in the LLB that are too old for LV 8.5 to open.
That means they are still in LV 5.11.
Do I really have to open each and save every single VI in the LLB in LV 8.2 to be able to use it in LV 8.5?

Dennis Knutson wrote:
I was able to mass compile it. I did notice that you did not include the hp34970u.llb. Did you point to this during the mass compile. Also, this llb is long obsolete. There is a nice, modern 8.5 project style driver available as well as a plug and play driver. Why do you even need to convert this?
I have mass compiled it with out errors too, but it seems like it was not really compiled as I still keep running into vi's in it that were still in 5.11.
I have a decade (or more) of 5.11 code that I am maintaining and upgrading when I have a chance.
Production test is still coding and deploying LV 5.11
I have tried the newer version of the 34970A driver but it is missing some of the vi's that many of our 5.11 codebase uses so is is not a drop in replacement for upgrading code.
Here is the "u" llb too, I forgot to attach last time
Message Edited by RTSLVU on 03-10-2009 01:12 PM
Attachments:
hp34970u.llb ‏21 KB

Help needed to convert 4.0 version llb to 6.0 or above

Can some help me convert the attached old llb (written in LV 4.0) to 6.0 or higher version so I can open it in LV 2012? Thx
Solved!
Go to Solution.
Attachments:
igorbin4.llb ‏315 KB

Try posting here: http://forums.ni.com/t5/Version-Conversion/bd-p/VersionConversion
Just for reference, here is a chart to help you know the minimum versions required. Version 6.0+ is correct.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If someone helped you out, please select their post as the solution and/or give them Kudos!

Convert 8.5 llb to 8.2 llb

Similar Messages

Maybe you are looking for