Labview 5.0 to 14 LLB

Hello -
Can someone convert this set of Version 5.0 VI drivers so that they're compatible with LabView 2014?
Thanks!
Jimcars

Mass compiled in 8.2.1, which you can open with 2014.

Similar Messages

Opening LabView VI's from a LLB

Hello,
I am currently trying to connect my newton Andor Shamrock camera and access the VI's so that I can use them in my LabVIEW program.
The readme software directed me to the LLB directory, in which I found all the applicable VI's for the camera. However, when I try to open them, a dialogue box appears directing me to find various files in the "Shared Library". Canceling this dialoge box allows the VI to still open, however the block diagram show ? and blanks where the icons of the camera's VIs should be.
Is there a way for me to access the VIs in the LLB Manager list or do I need to secure them from a separate source?
Thanks,
Justin
Solved!
Go to Solution.

Just a few names would be sufficient to give us a better idea. You can do a ctrl+h and hover over one of the missing subVI with the mouse and the missing filename will show in the context help.
LabVIEW Champion . Do more with less code and in less time .

LLB file problem (Labview 2013)

I have made labview project that builds a LLB file.
It contains my "test VIs"(auto-populating dir) and all Dependencies(user.lib, vi.lib....)
Building the LLB file goes fine.
But when i try to run the "test VIs" in the LLB file using an .Exe that uses "open VI reference -> invoke node "Run VI" i get a broken arrow and error 2002200....
Opening the "test VIs" in the LLB with Labview, the path for some of the sub VIs do not point to the LLB. It still points to the original VI (in user.lib, vi.lib....) causing the "test VI" to not be executable . ("test VIs" where all sub VIs points to LLB woks)
what am i doing wrong/how do i fix this?
/J

After some investigation.
Using Projec Explorer building a "Source Distribution" LLB Then calling my "test VIs" in the LLB file using an .Exe that uses
"open VI reference -> invoke node "Run VI" i get a broken arrow and message "VI has an error of type 2002200. The full development version of LabVIEW is required to fix problem"
The functions are in "Programming->File I/O-> Configuration file VIs" menu
(Directory C:\Program Files (x86)\National Instruments\LabVIEW 2013\vi.lib\Utility\config.llb\)
Below VIs generates the error
Get Key Names.vi
write key.vi
Remove Key.vi
Remove section.vi
Read key.vi (boolean)
Read key.vi (Double)
Read key.vi (I32)
Read key.vi (path)
But these works in llb
Open config data.vi
Get section names.vi
Read Key.vi (string)
Close config data.vi
I cant find any reason why some works and some dont.
is there someone how knows how to fix this?
/J

LV crashes while loading my llb, but the built app. functions correctly???

I�m hoping someone may understand the cause of the LabVIEW crash I�m experiencing.
LabVIEW 6.1 crashes and Windows 2000 says, "LabVIEW.exe has generated errors and will be closed by Windows" when I try to load an llb by clicking on the top-level vi from within LabVIEW or when opening the llb from outside LabVIEW. It crashes while loading particular sub-vi�s of the llb. If I try to load the offending subvi�s directly, I also get the same crash. If I build the llb into an application, the build goes smoothly and the resulting application functions correctly. If I use a �splash screen� approach and do not load the offending sub-vi�s (by not opening vi references to them), they load-up fi
ne when the top-level vi loads and then I am able to edit and re-save any vi of the llb including the offending sub-vi�s. I�ve tried re-saving the llb as a separate development distribution and still get the same crash behavior. I�ve also tried saving the offending sub-vi�s to separate files outside the mother llb (after getting them open with the splash screen approach) and I get the same crash when I open these files. If I save one of the offending sub-vi�s as a separate llb, I can�t get it open even with the splash screen approach. I�ve loaded the latest video driver for my Dell Inspiron 8100 laptop and I get the same behavior on a Dell Dimension 8200 desktop that is also running Windows 2000 (Version 5 SP4). There are 110 objects in my llb that includes *.vi�s, *.rtm�s, and *.ctl�s.. Any ideas as to why/how this is occurring and how I can fix it? Is this a known 6.1 bug that is fixed in 7? Any info would be greatly appreciated. I�ve included my splash screen like loader, f
or what it�s worth. Thanks.
Attachments:
__loadVIs.vi ‏88 KB

Thanks for responding. Your understanding is correct. Mass compiling was one of the first things I tried (although I failed to mention it). I also un-installed and re-installed LabVIEW. It crashes during mass compiling of the full llb, although the vi that it appears to be working on when it crashes is not an �offender�, i.e. I can open that vi fine. The crash during mass compiling is the same crash, i.e. Windows says it had to close LabVIEW because it generated errors.
I�ve attached one of the offenders. It is missing many of it�s sub-vi�s so you�ll have to hit �ignore vi� a bunch when opening it. (The llb of it is ~2.6 MB. I thought that might be too big/rude to post.) This vi crashes LabVIEW upon mass compile or upon opening it (after hit
ting �ignore subvi� a bunch).
I was going to attach an llb of another smaller offender, but in the process of editing it to be a little prettier and better documented, the problem kind of vanished for that vi. The main routine still crashes when I mass compile the full llb, but now I can open some of the old offenders without incident. I still can�t open the main routine directly as it crashes LabVIEW. Thanks for your time.
Attachments:
aveParam.vi ‏769 KB

How can I change the daq setting to differential mode in my labview program (example)?

I would appreciate if I could get an example in Labview 5.1. I realized that I need to create a cluster but for some reason it would not work

Examples for data acquisition are in the LabVIEW >> Examples >> Daq >> anlogin >> anlogin.llb directory. You will still have to do the following to programmatically set the measurement mode to differential.
You can set your data acquisition with the AI Config.vi in LabVIEW. There is an input for "coupling and input config". A good trick to make sure that you create the cluster correctly is to use your mouse as the wiring tool and right-click over that input. Then, choose Create Control or Create Constant. The cluster will pop up, and you can use your operating tool to choose differential mode for the second pull-down ring in the cluster.
Geneva L.
Applications Engineering
National Instruments
http://www.ni.com/ask

Link labview data with excel sheets

I would like to save the output of a cluster(containing strings and numeric data) in a specific format(each data in respective columns)
in an excel sheet.
how do I do it in labview??
I tried mathscript, is there any other way? If there isnt can u suggest how can I use it to solve the above mentioned issue.
similarly, can I recieve data in real time from excel sheets??
pls suggest.
Solved!
Go to Solution.

I think you should use the ActiveX to fullfill your requirements.
You can refer to this example
<LabVIEW Folder>\examples\comm\ExcelExamples.llb\Excel Macro Example.vi
Use activeX to write and read data.
Best Regards
Hu Yu

Fully utilizing all CPU's for a LabVIEW application

Hi All,
Have any of you figured out how to harness all of the CPU's in modern machines?
Backgroud:
I have an application that does a lot of signal processing and it was pegging the CPU of the machine it was originally deployed on for many minutes.
As a quick first step we suggested the customer try the application on a new high-end machine. THey did and the preformance improved ...
BUT...
When we look at the
Task Manager >>> Perfomance tab
it appears we are not not utilizing all of the available CPU's.
This observation is based on the 8 CPU graphs displayed in the Task Manager.
The first 4 graphs show very heavy CPU useage but the reamining four graphs show little or no loads.
I am guessing that this may be due to LV (8.X) using a default of 4 threads for each execution system.
Since the last time we were on-site, I have looked at
...\LabVIEW\vi.lib\utility\sysinfo.llb\threadconfig.vi
and it appears all I have to do is run that utility one time and save the config as 8 threads for each execution system.
Now before I send someone back to site, I'd like to find out if someone has traveled this road before me and would like to share their wisdom.
Thank you,
Ben
"Mommy, I want to go FAST!" (Daughter of one of my old girl friends)
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction
Solved!
Go to Solution.

I received a couple of questions concerning this post, so a bit more information to clear things up.
LabVIEW's Logic
LabVIEW's default thread creation logic is to create the max of (number of cores, 4). The bug we had is that we inadvertently limited this to four (no humorous comments please ).
What does the utility do?
The utility writes some settings to your ini file if different than default. When you run the utility, it displays the number of processors you have in a field at the top. It displays the number of threads being used for each priority in a section below. For a machine with 1-4 cores, the default thread count will be four. For a machine with 8 cores, the default thread count "should" be 8 (and, as of LabVIEW 8.5, it is).
Roy

Labview communicate with ABB robot through dll Dot Net

Hi all,
Currently  I need to use labview to do the communicate with dot net, for example to read and write RAPID data, Get execute status from robot. I'm able to read from RAPID but can't manage to write. Does anyone have an idea how to do? Please advice. Thanks

Hi,
     The NI OPC Server supporting device and drivers are here. Labview and third party device communication through OPC Server web cast avalable on here.
     Datasocket/OPC Server Example avalable on following link. \Program Files\National Instruments\LabVIEW 2009\examples\comm\datasktx.llb
Siva
Sivaraj M.S
CLD

LabVIEW 8.0.1 RTE Red Hat Linux

Hello,
I am trying to install the OpenG package manager 1.0, which requires the labview 8.0.1 RTE to install. I have a red hat / centos 5 system and labview 8.5. I have installed the labview 8.0.1 RTE according to http://digital.ni.com/Softlib.nsf/webPreview/7CE20CDA28E51AD08625711C006276B3?OpenDocument
Clicking on the vipm installer directley opens it up in labview 8.5 LLB manager, and I can't open any of the vi's in there. I think I need to open it with the 8.0.1 RTE. I see the only executable in the package is lvdark, which installs to /usr/local/lib/LabVIEW-8.0/ I presume this is what I need to use to run the vipm installer. However when I try to run this I get the error
/usr/local/lib/liblvrtdark.so.8.0: cannot restore segment prot after reloc: Permission denied
even when running as root.
Any ideas?
Solved!
Go to Solution.

Hi Claire,
I'm one of the VIPM support engineers, so I'm following this thread...
Forgetting VIPM for a minute, here is the fundamental problem:
An executable application for Linux was built in LabVIEW 8.0.1.
The user has the LabVIEW 8.0.1 run-time engine installed
The user has LabVIEW 8.5 development environment installed, too
When the user tries to run the build executable application, it opens in the LabVIEW 8.5 development environment (LLB manager, specifically)
Now, that executable application for Linux that was build in LabVIEW 8.0.1 just happens to be VIPM. And, our documentation doesn't cover this issue, as it's likely a bug in the LabVIEW installers or in the user's OS configuration.
Thanks,
-Jim Kring

Le changement de version de labview de 6.1 à 7

I go on a project engineer. This engineer worked on labview 6.1 and I work on version 7.
When i launch the programm, VIs aren't known by version 7.
I want to know news VIs for this old VIs:
- dio port config
- dio port write
- dio port read
- calculate finite pulse specs
- counter group config
- conuter control
- counter set attribute
- counter get attribute
- set pulse specs
- normalize pulse specs
- finite pulse train.ctl
- generate delayed pulse
thanks

jumarion wrote:
> Les VIs que vous cherchez sont probablement dans les librairies
> LabVIEW \vi.lib\daq\digital.llb pour les E/S numériques et ctr.llb
> pour les compteurs.
Those VIs sit in vi.lib so they should be found automatically. If not
they are probably not installed. Install the correct NI-DAQ software
drivers and make sure it installs the NI-DAQ support VIs for your
installed LabVIEW version.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

TestStand - Default Values 82.llb missing

I've recently upgraded to Labview 8.2 (I already had TestStand 3.5), and when I try to call a VI using some default parameters and some defined parameters, I get an error saying that "C:\Program Files\National Instruments\TestStand 3.5\AdapterSupport\LabVIEW\TestStand - Default Values 80.llb" is missing. Where do I get this file from? In the directory I see versions of this file for 8.0, 7.1 and 7.0 only. I've tried reinstalling TestStand and LabVIEW, but the installation options say everything is already defined, and i don't see an install component for anything like TestStand 3.5 LabVIEW Support.

Copy the 80 version, rename it 82. Mass compile this LLB in 8.2. This should fix your problem.
Allen P.
NI

Configuration string keys in LabVIEW 2009 changes

I am trying to write a configuration file to be used by other (non-labview) software.
However the LabVIEW 2009 'write sting key' function adds quotes around string keys, even if the 'raw string' mode is used, this makes this tool USELESS, and I could only finde a little note in the online help
When VIs write to a configuration file, they place
quotation marks around any string or path data. LabVIEW also supports
single quotes around values in .ini
files.
I could not find it in the Upgrade notes.
Could we get an option to remove the quotes?
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!

Dear Ton,
thank you so much for your post. This problem was brought to the attention from our R&D department, hopefully they will add this soon to the writekey.vi . There is a work arroud for now; you can add the attached VI to the library;
Download the attached VI and place in the following path: <Program Files>\National Instruments\LabVIEW\vi.lib\Utility\config.llb
In the same folder, double-click NI_LVConfig.lvlib
Right-click the Write folder and add the above-mentioned VI.
Hopefully this will bring you further,
Best regards,
Martijn S
Applications Engineer
NI Netherlands
Attachments:
WriteKey(String)workaround[1].vi ‏14 KB

HELP! suddenly .llb won't open anymore?!

I can't access the .llb file I was working with anymore.  I get the message: 'Error occured while listing contenst of c:\......\filename.llb.'
I've used this file a lot during the last week. No problems at all.    It's an instrument driver, now located in the instr.lib folder.   The last thing I did, was making a pallette for it.    After restarting Labview, I noticed that on the pallette, all icons changed to questions marks.   So I tried to open the corresponding llb file, and it won't open anymore.     What's going on?
Any way I can still open the llb file? There's a few days work in it.   (Not backupped... .Yeah, I know..... )
It's on Labview 8.     Attached the llb file, for anyone that wants to have a go at it.
More importantly, how did this happen?    I can't remember that I ever had this problem in the past....
Attachments:
SR5113LV8 extended.llb ‏693 KB

Hi Anthony, it seems NI can recover your file. There was an older post about this...
http://forums.ni.com/ni/board/message?board.id=170&message.id=99730

Labview generates an exe file but cannot close it properly

Hi all, I have used source code to generate an exe file. And I also load dynamic vi using this exe file. However, right now it cannot be closed properly by clicking "X" on top right corner. I think it is caused by loading dynamic vi but do not know how to solve it. Could you help me about this? Thank you!

Its here:
C:\Program Files\National Instruments\LabVIEW 2011\examples\viserver\dynload.llb\Dynamic Load Example.vi
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.
Attachments:
dynload.llb ‏118 KB

I can't find a TestStand tool that assembles all VIs into a llb file.

I used to use a teststand tool to assemble all LabView VI modules into a .llb file with an option to save only the panel view. This tool existed in TS2.0 but not in TS3.0. Where can I find this tool?

Unfortunately, the TestStand Deployment Utility does not currently provide the functionality to remove VI Block Diagrams. We are looking into providing this functionality in a future version. The TestStand Deployment Utility also does not currently provide the functionality to store all VIs including top-level code module VIs in a single LLB.
That being said, you do have the ability to Lock your VI Block Diagrams using the TestStand Deployment Utility by password protecting them. This can be done in the LabVIEW VI Options window (to get to the LabVIEW VI Options window, go to the Distributed Files tab and click the LabVIEW Options button). Additionally, in the LabVIEW VI Options window, you can specify that all of your SubVI Dependencies be placed in an LLB as opposed to a normal folder. To do this, you simply need to add a .llb to the end of the SubVI Location name:
Hope this helps.
Manooch H.
National Instruments

Labview 5.0 to 14 LLB

Similar Messages

Maybe you are looking for