LLB in labview 2011

Hi,
i would like to create a .llb file including some VIs (i'm using LV2011). In older versions it was easy to create a library selecting file--->save with options--->development distribution and i was able to hide block diagrams by clicking on "hide diagrams".
How can i do the same thing in LV 2011?
Tnx!

Dennis_Knutson wrote:
An llb is really an obsolete file format and I would recomend you start using a lib, packed lib, for distribution and never use an llb for development.
Fully agree, Dennis, but one small feature is missing in packed libraries.
With distribution into llb I can define which VIs should be excluded from distribution:
But I can't do the same with packed libraries:
In some rare cases (complex PlugIn architecture, for example) this might be necessary.
Andrey.

Similar Messages

\National Instruments\LabVIEW 2011\vi.lib\addons\_office\excel.llb\Excel Set Cel

\National Instruments\LabVIEW 2011\vi.lib\addons\_office\excel.llb\Excel Set Cel with a broken arrow
Attachments:
error pic.png ‏27 KB

version of Excel is 2010, but i have this problem with Excel 2007, Excel 2003. This property also has a problem in old versions of labview (8.6; 9; 10).
Attachments:
excel1.png ‏86 KB
pic2.png ‏4 KB
excel version.png ‏38 KB

Labview 2011 32-bit, Tescom ER3000, Windows 7 64-bit

I currently have Labview 2011 32-bit installed on a Windows 7- 64-bit machine. I am trying to run the VIs found in the attachment below, but I get the error that function called in the DLL has failed and that TESCOM.DLL may be in use. Any thoughts as to why this is happening? I've already checked to make sure the path referenced in the VIs' function call nodes is correct... any and all help is appreciated!!
~Avi
Solved!
Go to Solution.
Attachments:
ER3000.llb ‏139 KB

Greetings;
I have been reading up a bit on the company and the DLL itself, and are we sure it is supposed to work well with Win7? Would it be possible to try booting up LabVIEW in compatibility mode (XP) to try it out?
http://www.documentation.emersonprocess.com/groups/public/documents/data_sheets/der301767x012.pdf
Only mentions up to XP, hence the question.
National Instruments
Applications Engineer

Vision builder AI 2011 incompatible with Vis created by Labview 2011 ?

Hi,
I have some issues to drive some motor by a Vi created under Labview 2011 using an inspection built under vision builder AI 2011
The step for running a Labview Vi said me that it only support 2010 VIs or earlier ? How two NI softwares 2011 can be incompatible ?
So I try to save under a old version but this vi is part of a huge LLB...Is it possible to save this LLB as a 2010 version without saving all subvis .ctl etc.. ? I am a little confused...
Thank you for your help

You should be able to save the top level VI for previous to LV 2010, and all VIs from that LLB will also be saved to a LV 2010 version LLB that can be used by VBAI. There is a restriction that any VIs from a toolkit that you have to pay for (i.e. Vision), even if they are in your LLB will not be saved for previous, but driver VIs (i.e. Motion, DAQ, NI-IMAQ) if they are in your LLB will be saved in the resulting LV 2010 LLB.
I realize this isn't ideal and VBAI will be supporting LV 2011 or a future version later. Another option will be to use the VBAI API in LV 2011 to have VBAI do just the image processing portion of your control system and do Motion, or other functionality in LV environment and control VBAI from LV using the VBAI API (this allows you to load inspections, run them, get images, and results, etc.), which does support LV 2011.
Hope this helps,
Brad

Conner LabVIEW 3.1 to LabVIEW 2011

Hi, I am a senior student in UT Arlington. I get a LabVIEW file from my professor. When I try to open it with LabVIEW 2011, it says VI version is too early to convert to the current version. LabVIEW load error code 10: VI version (3.1) is too old to convert to the current LabVIEW version (11.0.1 f2). I attach the VI with this message. I wonder if anyone can help me convert the VI from version 3.1 to the current version. I will be greatly appreciate it.
Attachments:
HP8510A.LLB ‏2811 KB

Hi everyone, im newest of this.
I have one problem with version 3.1 to version 7.1
Anyone can help me to convert an library of 3.1 to 7.1 or 8.5 or 2013?
Thats error said:
"An error ocurred loading VI verifiy information.vi.
LabVIEW load error code 10: VI version (3.1) is too old to convert to the current LabVIEW version (7.1)
Thanks to all.
Attachments:
ADVCLASS.LLB ‏1075 KB

Labview 2011 NI Report and error 7

I know this topic has been cover in this forum many times, but I just can’t get it working.
Recently, we have updated our labview from 8.2 (Window XP) to 2011 sp1 (Window 7), and of course, NI report stops working.
In our software, we have a project that eventually gets compile into a DLL (Not AN .EXE, THIS IS NOT AN EXECUTABLE). In this DLL, we modify an excel spread sheet. As a result, we need the NI report tool kit.
Now I know that you would have to manually include the two folders (NIReport and LVclass)in your project in order for this to work in labview 2011, which I did by following the link below.
http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402?OpenDocument
I made sure that the two folders were “Always Included”, and not using the labview 8.x file layout. After the compiling has been complete, one DLL was created (with 4 other files, which is good because I only want one DLL). I assumed that the NI report tool kit is included in the build since I selected “Always included”.
After that I ran my main top level vi. The main top level vi tried to access the DLL, and I got error 7,
Get LV Class Default Value.vi<APPEND>
<b>Complete call chain:</b>
Get LV Class Default Value.vi
Test.vi
<b>LabVIEW attempted to load the class at this path:</b>
C:\BUILD PATH\DLL NAME.dll\1abvi3w\vi.lib\Utility\NIReport.llb\Excel\NI_Excel.lvclass
Now I assume this might be caused by two reasons. The path is incorrect or the tool kit wasn’t included.
I have been working on and off with this problem for weeks and still can’t get it working. I am guessing the path is incorrect, but I have manually changed the path to something different but got no luck. Any suggestions?
Solved!
Go to Solution.

Hi,
Thanks for the reply.
The reason I didn't select "use Labview 8.x file layout" is because it will also create 10 extra support folders (I think this is due to name conflicts in the DLL directory) after compiling the project. This is not an acceptable solution for my customer since no one would want a DLL that comes with so many extra files.
And yes, I am aware of the file layout after Labview 2009. However, the path to NI_Excel.lvclass (C:\BUILD PATH\DLL NAME.dll\1abvi3w\vi.lib\Utility\NIReport.llb\Excel\NI_Excel.lvclass) was provided by “Excel class path.vi” (vi.lib\Utility\NIReport.llb\Excel class path.vi). In “excel class path.vi” it checks to see if the application is using the 8.x layout or not.
I switched to “use Labview 8.x file layout” just for testing reasons but it still doesn’t work. The file path for NI_Excel.lvclass is now C:\BUILD PATH\DLL NAME.dll\Excel\NI_Excel.lvclass (provided by “Excel class path.vi”). I also hard coded the path to C:\BUILD PATH\DLL NAME.dll\NI_Excel.lvclass and that doesn’t work too.
I have created a simple project to demonstrate my problem. Copy the attached folder to your desktop and you will see a folder named “Excel”. Open the “excel Test” project and build the DLL, check the build path and make sure it’s building to “Desktop\excel\Exceltest”. After that go to the DLL TEST folder (\Desktop\excel\DLL TEST) and run DLL test.vi. Make sure the path to the DLL (on the block diagram) is correct and run the vi. You should see the error I am talking about.
Thanks,
Attachments:
excel.zip ‏19 KB

Labview 2011 on Win7, OS causing serial loopback message corruption when clicking on top of windows?

I'm wondering if anyone else has seen problems like this.
I've been tearing my hair out over debugging some code. I have a ftont panel, I'm using some LEDs to send messages through the NI RS232 cable I bought, and have connected with a connector in a loopback fashion.
I've been trying to read the incoming messages from loopback...and based on those, changing indicators and controls on the front panel.
I could not figure why values were changing at strange times....like T's were turning to F's (I'm working with the serial data as boolean arrays).
Well, I was simplifying code, and mostly running right...but every once in awhile, it appeared that my front panel indictors, especially the values I'm changing based on the loopback serial messages would *BLINK*.
I happened to be looking at the Probe Watch window...and I saw where my probes were correctly showing on a couple spots (a left and right indicator) TTTTTTTF and TTTTTTTF......these appear at times to change T's to F's and vice versa.
I then started clicking around...and found this is almost always caused, when I click the mouse on the top of the window...the part that you usually click and drag to move a window around the Windows desktop!!!!!!!!!!!!
I can see this happen when I click on ANY window on the Windows OS desktop!!!!!!
It appears that the OS is messing with me..............?
I'm using Labview 2011, 32-bit on Win7....I believe the OS is 64 bit.
Has anyone seen behavior like this before?
Thanks in advance,
cayenne

Matthew Kelton wrote:
When you are probing, are you looking at the actual spot where you are getting your serial data, or are you looking at it after you've done some processing? I would look at the actual raw data and use a serial port capture utility (there are several free ones on the internet) which will confirm your data is coming in correctly.
What is your CPU running at? If it is pegged at 100%, something has to give.
Is your entire VI running in the UI execution system? If you post your test code, it sounds like it would be easy enough for someone to do a loopback test of their own to confirm similar behavior.
Thanks for the reply. No, CPU isn't being hardly used at all...this is a new lenovo laptop.....high end Dell U2711 monitor...
Task Mgr while Front Panel running:
I'm looking after I've done some processing....
I'm new to working with serial port stuff....I don't have a serial port capture device...?
Thing is...when I run this in debug with breakpoints and stepping through...I don't see this happening. But when running at full speed, and especially when I click on any of the open windows on my desktop, along the top margin where you would click and drag a window around...I can see the serial data in the probe jump...and all data going through the serial port and being displayed on the front panel changing values...
On my VI, I'm actually constructing the byte string...sending it through the serial loopback, and receiving it and acting on it. I can see the data going in is the same as is coming out...it just seems to quickly corrupt and then come back again...like maybe it is getting interrupted by the Win7 OS....?
I can't really post the whole code here...proprietary stuff...that's why in the past, I was posting a separate, simpler vi with only the parts I was having problems with....
I think I have full support with NI...I wonder if I could send them the code to look at, with more confidentiality...?
But again, I can make the problems happen, when it and the probe window is open, in real time...by clicking on windows.
Also, this tends to explain problems I saw earlier...when running slow, all was well , when debugging with break points and stepping through. But at full speed, unexplained...things would start resetting without explanation...and without regularity.
C
I"m not sure what you are asking with "Is your entire VI running in the UI execution system?"....I have the one vi running, and only that vi is running.....

Error -1074397038 occurred at IMAQ Start.vi for 64bit Labview 2011 SP1, Win7

Hello,
I am using a MC1362 camera from Mikrotron with a PCIe1433 framegrabber. I was using it with windows XP, 32 bit, labview 2010 SP1 32 bit, it was working perfectly fine. I just switch to windows 7 with labview 2011 SP1 64bit, and it is not working anymore with my custom routine in labview, though it works with MAX and camera file generator and I use the same camera file.
When I run my routine, I have this error message:
Error -1074397038 occurred at IMAQ Start.vi
Possible reason(s):
NI-IMAQ: The requested serial termination string was not found in the returned buffer.
Then, If I try to run the camera with MAX, it doesn't work anymore, I have to reboot the camera, and put it in the right mode with the Mikrotron control tool to obtain an image.
I have seen similar issue on a Basler camera on the forum, and it has been solved by using a camera file to set the different parameters. There is no camera file complete to set all the parameters of the camera, so I had to program them in serial to drive the camera with my Labview routine.
Could you help me to solve this issue please?
Thanks
Bests
David Dulin

This forum post is already handled --> SR 1154262.
Kind regards,
Corné Westeneng
Applications Engineer
NI-Netherlands

Process Failure when communicating over MODBUS using LabVIEW 2011 and DSC

I'm currently trying to read from a PLC's holding registers using MODBUS/TCP. I've confirmed that the PLC is updating the values and responding to MODBUS communication correctly using a third party program called Modbus Poll. However, when I try to poll the PLC using LabVIEW's shared variable engine, I am unable to read any values from the same addresses that I'm viewing with Modbus Poll.
My setup simply consists of a PC connected directly to the PLC over Ethernet, with no router in between. I am using LabVIEW 2011 SP1 with the DSC module.
I opened the NI Distributed Systems Manager to view the status of all shared variables in the Modbus library that I created and I've noticed that the CommFail bit is permanently set to "true". All other variables with a "read" access mode report "Process Failure". I've tried restarting the process as well as stopping and starting the local variable engine with no success. I've also restarted my computer several times to see if any services were failing, but this does not seem to have fixed the problem.
I finally resorted to monitoring communications over the network card that I have the PLC plugged into via Ethernet using Wireshark and I've found that while Modbus Poll is communicating with the PLC, many MODBUS and TCP packets are sent and received. However, when solely using LabVIEW or the NI DSM to communicate with the PLC, there does not appear to be any communication over the network card.
Something that may be worth noting is that I was able to communicate with the PLC and read values from it with the DSM on just one occasion, when I first figured out which addresses I should be reading from. It all stopped working shortly thereafter. Prior to this, "CommFail" was not usually set to "true" with my current configuration. Thinking that it was my firewall, I have since turned my firewall off, but this seems to have had no effect on the problem either.
Any help on this matter would be appreciated.
Solved!
Go to Solution.

Just a thought but I think the register addresses used by LabVIEW are one off of the actual register #. I was using a CRIO as a modbus IO Server and had to shift the register addresses by 1 to get things to work correctly (can;t recall if it was +1 or -1). This is documented somewhere on ni.com but can;t seem to find it now. But here is another link that may help:
http://zone.ni.com/reference/en-XX/help/371618E-01/lvmve/dsc_modbus_using/
Dan

Getting "setup.exe has stopped working" message when trying to install labview 2011 or 2012 on a windows 7 machine

I am getting a "setup.exe has stopped working" message when trying to install labview 2011 or 2012 on a windows 7 machine. I already tried running setup.exe as an administrator with the same results. I have Microsoft .NET Framework 4.5.1 installed on the affected machine. Could this be the cause of this issue? Or does someone know the root cause of such error?
Solved!
Go to Solution.

Hi - are you getting it at the start of installation, during or after 100% progress has finished?
Is it just LabVIEW you're installing, or is it drivers too, in which case, what was the last large package that was installing at the time?
This could be caused by the NVIDIA chipset driver :
https://decibel.ni.com/content/message/46299?tstart=-130
Thanks
Sacha
// it takes almost no time to rate an answer

How to start an 8.2 app in LabVIEW 2011

This has been a problem that I've been trying to deal with for the past week to no avail.
In short:
The 8.2s which worked on an XP machine were openned on a Windows 8 with LabVIEW 2011, made into an executable, put back on to the Windows XP to see if it will still all worked, and it does not.
In detail:
I had a ready made, working application made in LabVIEW 8.2. The goal is to update all old software to the new LabVIEW 2011, but to still make it work. The problem is, after making it run in edit mode for at least a little bit (after debugging common errors with openning in a newer version), after making an executable and putting it on the machine it used to run on, it won't run. The program will not communicate with the machine and will give the following errors which are, my eyes, things that should not be happening after working in edit mode.
Two error codes received:
1) One or more Configuration File(s) are not available. Please Check the Hardware configuration!
2) {
Error 7 occured at Openfile+.vi: Open file
Possible reason(s):
LabVIEW: File not found. The file might have been mover or deleted, or the file path might be incorrectly formatted for the operating system.
For example, use\ as path separators on Windows, : on Mac OS X, and / on Linus. Verify tht the path is correct using the command prompt or file explorer.
=========================================
NI-488: Non-existent board.
Please, if anyone has had the same or a similar issue and can give any sort of feedback or thoughts, I would greatly appreciate it. Thank you!
-Hub25

Bob_Schor wrote:
There are a number of issues here. First, LabVIEW 8.2 cannot be installed on Windows 7 (to say nothing of Windows 8), and LabVIEW 2011 cannot be installed on Windows XP. I'm not sure whether executables can be built across Windows 7/XP boundaries, but I'm pretty sure that, at a minimum, you'd need to install the LabVIEW 2011 Run Time Engine on the Windows XP system (and I don't know if this is possible).
After next April, Windows XP "turns into a pumpkin" as Microsoft drops support for it. A good time to migrate to Windows 7!
You can install LabVIEW 8.2 on a Windows 7 computer. I have that right now specifically for converting old code. And I am sure LabVIEW 2011 can go on XP as well.
I'm guessing the main issue is the lack of the 2011 Run-Time Engine on the XP machine. But I would also advise moving away from the OpenFile+.vi since that is a really old VI and the newer LabVIEW file I/O primitives are so much better anyways.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Install labview 6.1 (or compatible) run-time engine with labview 2011

I have installed a trial period version of Labveiw 2011 in order to check for possible upgrade issues I may have if I decide to upgrade from labveiw 6.1. Well, needless to say there have been alot. That is as expected since I have not updated labview in many years. I am still not under any pressure to update; however, I would like to in order to get support and make sure I do not have any compatibility issues with new equipment purchases. I have been able to resolve most of my compatibility issues with simple code fixes and such. However, twice now I have run into an error when launching labview executeables compiled by two different equipment manufacturers. The equipment I am using is not even old...maybe a year or so. When I launch the labview executables to control this equipment on a PC that has the trial period labview 2011 installed, I get an error message stating something like " This requires a Labview 6.1 (or compatible) run time engine." I have tried to download and install the 6.1 labivew engine but I can't install this engine on a PC which has labview 2011 installed. Can someone explain how I am to run these executables under labview 2011. I can't imagine these executables were developed using 6.1 since this equipment is not even a year old now.
Solved!
Go to Solution.

Im not for sure I am on the same page with you here. Im not trying to develop any code myself. I have some labview executables that came with hardware we purchased in order to control it. We used to have labview 6.1 installed; so everything was working ok. But now that I have installed 2011, I get an error message when trying to run these executables. The error message states that this executable requires a labview 6.1 or compatible run-time engine. I have seen this error on both XP and Windows 7 machines. I did not develop the executable, it was developed by the hardware manufacturer. But since this hardware is only about 1 year old, I an assuming they used a newer version of Labview to develop this code. Certianly newer than 6.1.
So I guess my question is..is there a way for me to get this executable to work on a PC that has labview 2011 installed. I have tried to install a labview 6.1 run time engine but it will not install. Any other options?

Is it possible to create a schedule in Labview . Example: i want to off the lights at 7pm and want it on at 8am. If there is can anyone teach, its for a school project. Im using labview 2011

Is it possible to create a schedule in Labview . Example: i want to off the lights at 7pm and want it on at 8am. If there is can anyone teach, its for a school project. Im using labview 2011...thx

Since this is a school project I recommend you do the work yourself. You will not learn asking others to do it for you. In addition, folks here will not do your homework for you. We are however more than wiling to answer specific questions for you. Post what you have done or tried and ask specific questions. I am confident you will get assistance.
And to answer your question, yes LabVIEW can be used to implement a scheduling program.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Application crashes when calling DLL built with LabVIEW 2011

Hello everybody,
Our application calls DLLs built with LabVIEW 2010 SP1. We installed LabVIEW 2011 and built some DLLs. So far so good. If we start our application and run 2010 DLLs it still works fine. If we run a 2011 DLL just once no error happens, but if we try to run the same 2011 DLL our application crashes reporting the error below. I saved the code for 2010 version and built a DLL and it works fine. Does anyone know why?
Thank you in advance.
#Date: Fr, 16. Sep 2011 16:25:25
#OSName: Microsoft Windows XP Service Pack 3
#OSVers: 5.1
#OSBuild: 2600
#AppName: PasTA
#Version: 11.0f2 32-bit
#AppKind: AppLib
#LabVIEW Base Address: 0x30000000
16.09.2011 16:25:26.181
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash: Crash caught by NIER
minidump id: 8a779b3f-51d7-4864-8e4d-6ab0195cd158
ExceptionCode: 0xC0000005
N
0x3072C804 - lvrt <unknown> + 0
0x3072CBB8 - lvrt <unknown> + 0
0x7C864191 - KERNEL32 <unknown> + 0
0x7C83AB50 - KERNEL32 <unknown> + 0
0x00000000 - PasTA <unknown> + 0
Attachments:
error.PNG ‏11 KB

On that note, you should be able to create DLLs in 2010 and run them with 2011, correct?? In my case, I have a 2010 built DLL (talking to sbRIO), most of the functions work when run in 2011, but a couple of them lock up LabVIEW on the desktop (but not the sbRIO), no lock ups happen with 2010 on the desktop.

Labview 2011 save for previous version crashes

Hello,
I am trying to save an existing Labview 2011 project to any previous version. I have tried 2010 all the way down to 8.0. I have a clean project, all files are LV 2011, it builds and runs correctly. I have mass compiled. It did call 2 dynamic vi's but I have removed those. The project did contain conditional compilation, but that is removed. It did contain disabled diagrams, but they are removed. I did a save hierarchy to a seperate folder, just to make sure the standard save works. It does. There are 1196 vi's and controls in the project.
If I save to LV 2010, quite a number of sub vi's are saved (909 including controls), but none of the top level ones. The crash is manifested by Labview leaving memory (task manager doesn't see it any more) and the Labview window dissapearing.
Attached is the save dialog at the instance before crashing.
I have not been able to locate a log to let me know the last loaded vi. If you know of such a log, please let me know.
Has anyone experienced similar problems? If so, any clues on how to fix this?
Thanks,
Bart Schroder
Attachments:
LV2011 save crash.jpg ‏17 KB

BartSchroder wrote:
I have not been able to locate a log to let me know the last loaded vi. If you know of such a log, please let me know.
In the advanced build configuration, check "generate build log file". See if you get more information. Good luck.
Quote from the help:
Generate build log file—Specifies whether to create a log file for the build. The build log file lists all files contained in the build, including subVIs you do not specify as Startup VIs or Always Included. The log file also contains general build information such as build start and end time, the build specification and project name, and any errors that occurred during the build.
LabVIEW Champion . Do more with less code and in less time .

LLB in labview 2011

Similar Messages

Maybe you are looking for