LabVIEW hangs building packed library

Hi,
I have migrated most of my object libraries to PPLs (suffering the common pitfalls). But yesterday I encountered a (what I think) Biuld process specific issue:
after updating / changing som dependencies I tried to re-build, but LabVIEW locks up in the build process: the dialog says "Building packed library"
and LabVIEW can only be stopped using the Task Manager.
What I see in the target directory is, that all the dependencies are generated corretly (PPLs themselves) as well as a ZIP File with the name of the target PPL.Using 2013SP1f5
Any hints anyone?
Cheers
Oli
Programming languages don't create bad code, programmers create bad code....

So... finally tried on a different computer (f2 though)
Worked from scratch five times in a row until I dared to disable debugging. Reenabling debugging after restart did not solve the problem. Tried a Clean before the next try. This worked for the next build. But a subsequent build without doing any changes failed again.
On this computer, the NI Error Report did not always occur; if it didn't LV came up with the following eror message:
Might be related to f2, but maybe it might be a hint.
Programming languages don't create bad code, programmers create bad code....

Similar Messages

Error 56003 building packed library

Hi
I am trying to build a packed library from my project. I keep getting an error both with Labview 10 and 2014:
Error 56003 occurred at Invoke Node in AB_Source_VI.lvclass:Copy_SourceItem.vi->AB_Build.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_PackedLibrary.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: Adding this item would cause a conflict with another item.
Unfortunately, no information is provided on which "item" is causing the problems.
Any ideas how to identfy the "item"?
Thanks
Solved!
Go to Solution.

wsilh, try to create a new project with only this library in it. See what dependencies are pulled with it , maybe a different lvlib/lvlibp is pulled in. Also, be careful where you use the lvlib (uncompiled) and the lvlibp (compiled) because they can clash with each other.
Is this library using another library?
Thanks,
Danielle
"Wisdom comes from experience. Experience is often a result of lack of wisdom.”
― Terry Pratchett

Using LabVIEW Packed Library within TestStand Deployment Tool

I am wondering what could be the interest of generating Packed Library within the TestStand Deployment Tool since the sequences using these VIs will not be able to find the dependant VIs included into the build Packed Library on the deployment target.
Any experience using Packed Library within TestStand Deployment Tool ?
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 & 2010 & 2014)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)

Jiggawax,
Sorry for the confusion,
My question concerns the developement of Custom Step Types.
For example, within a project or as an independant product.
The best practices is to avoid using main module when developing CST in order to preserve evolutivity (main module calling paramters are copied within CST instances and could need prototype updating). I prefer using PostStep (as NI does for its own CST).
Thus, when creating the CST palette, I have to configure the EditStep and the PostStep and define each VI call.
If I want to distribute these VIs through a .lvlibp, then I need to build a .lvlibp very early and use it within my CST palette.
This .lvlibp will be used on deployed benches and may not contain VI diagrams and debug options (best performance).
But during the development of my CSTs, if I need to debug the VIs called when using CST whitin a sequence, and if I don't want to change the called VIs defined in my CST palette, then I need to regenerate this .lvlibp with debug option (different from the deployment .lvlibp) in order to allow debug.
May be it could be interesting that the TestStand deployment tool take into account SubSteps when selecting the Packed Library option. This tool is able to modify sequences, it could be able to change also palette configuration file.
This will allow to have only two levels :
> Source and Debug (VIs)
> Deployment (.lvlibp)
instead of three :
> Source (VIs)
> Debug (.lvlibp with debug option)
> Deployment (.lvlibp)
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 & 2010 & 2014)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)

How to use outside Class in packed library plugins

I have found the very useful article from Michael Lacasse (https://decibel.ni.com/content/docs/DOC-19176) on how to use packed library as plugins. This approach makes the most sense when you try to distribute additional code after your executable has already been installed.
My problem is that when I try to use a class from the main code in a plugin, the plugins won't work anymore. Ideally, I would have liked the parent plugin-interface to inherit from a class used in the main code, or using the class as an input parameter of the plugin would be the next best thing.
I got several errors, some at execution time (#1448) or at edit time ("This VI does not match other VIs in the method: connector pane terminal(s)"). I have settled to use clusters to pass data to the plugins.
My question is: Is it possible to use a class defined in the main code in a packed-project-library, either inherited or as a parameter? If yes, do you have any example?
Marc Dubois
HaroTek LLC
www.harotek.com
Solved!
Go to Solution.

I should point out that it's important to use the copy THAT'S IN THE PPL, *-NOT-* the copy from your source.
It will compile if you mix them together, but they aren't the same object, and won't share data.
You should never refer to your source code for the class, except to build the PPL.
(Consider using a separate project, to avoid temptation).
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

Calling a DLL(with vi.lib) from a lvclass within a Packed library

Basically, I am having problem calling a DLL (which uses the vi.lib) from a packed library.
The error code I got is error code 1003. “Error 1003 occurred at Call Library Function Node in XXXXX.lvlibp”, “Labview: The VI is not excutable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it.   Create Summary Log.vi”
The VI that was mentioned above (Create Summary Log.vi) is one of the functions in the DLL that I am trying to call from the packed library. This VI modifies an Excel spreadsheet so it needs the vi.lib. In my DLL project, vi.lib is in my dependencies. When I compile my DLL, Labview will create four folders (NI_Excel, NI_HTML, NI_report, NI_Standard Report) at the build destination.
To problem happens when I run a Top level VI, which calls-> the lvlibp -> lvclass (within the packed library) -> DLL (uses the vi.lib Excel functions).
This problem doesn’t happen when I am not running the packed library (Only with the lvclass). So I think the problem is that DLL can’t access or find the vi.lib when it’s being called by the packed library. It seems like the packed library changes the way the DLL access the vi.lib.
Any suggestions?

Hi,
Thank you for your reply. Unfortunately, I think I might have provided wrong information. I thought the problem didn’t exist when I wasn’t running the packed library, but the truth is, the problem always exist regardless.
I would get an “error 7” when I created a simple VI that would utilize “Call Library Function Node” to call the DLL.
Error 7 occurred at Get LV Class Default Value.vi
Possible reason(s):
LabVIEW: File not found. The file might have been moved 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 Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488: Nonexistent GPIB interface.
Complete call chain:
     Get LV Class Default Value.vi
     NI_report.lvclass:New Report.vi
     Create Summary Log.vi
     Create Summary Log.vi.ProxyCaller
LabVIEW attempted to load the class at this path:
C:\XXX\XXX.dll\Excel\NI_Excel.lvclass
So the problem is, I don’t know how to include the NI_Excel.lvclass in my DLL. I didn’t have this problem back in 8.2, as I would just include a VI (with the excel VIs in the block diagram) in the project when I build it. This doesn’t work anymore as I am using 2011.

Labview hangs when accessing dll

Im accessing an active x dll using labview 8.21. When we query the dll all parallel loops in labview hang until the dll returns. Is there a way to get around this behaivour?

HI,
I do not know if this will help, but there is an issue with the Call Function Library node in LabVIEW 8.2.1 and is posted in the LabVIEW 8.2.1 Readme help here:
If you configure a Call Library Function Node to call a LabVIEW DLL, place a checkmark in the Specify path on diagram checkbox on the Function page of the Call Library Function dialog box, and select Run in UI thread in the Thread control, LabVIEW hangs when executing the Call Library Function Node. To correct this problem, select Reentrant instead of Run in UI thread in the Thread
control. If you configure the Call Library Function Node to call a DLL
written in C with these same settings, LabVIEW works correctly.
I hope this helps,
Regards,
Nadim
Applications Engineering
National Instruments

Object loaded and saved with Read and Write Datalog are not compatible with packed library

Hi all,
I often use packed libraries to distribute my software.
My problem is the following:
I save a LabVIEW object of a class (MyClass) that is not included in a packed library using "Write datalog" (for example saved file is MyObject.dat).
If I load MyObject.dat using "Read Datalog" but using "MyCLass" saved in packed library as "Record type", Read Datalog generates an error or anyway loaded data is inconsistent.
In other word, if I save an object using as "Record Type" MyClass not included in a packed library and then I load saved file using the MyClass included in a packed library, file cannot be loaded.
Can you help me?
Thank all

I think you are running into an issue created by namespacing.
Point is, that lvlib as well as lvlibp create a level of namespacing:
I would expect that level of namespaces being part of the datalog file.
So essentially, if the class is not encapsulated in the very same namespace when reading in which it was written, it should fail with exactly the error you are describing.
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

How to add packed library on palette set

Hi,
I am unable to add packed library to pallete set. Can someone provide information on how to do that?
Thanks,
Andrej
Solved!
Go to Solution.

Andrej,
starting with LV 2010, you can use packed libraries to encapsulate functions and supply them on the palettes. The way to get there is somehow a little tricky, so here a short description on how to do that:
1. Build your LV library (lvlib) as used, please remember to set prudent item settings (private vs. public). Public items will be "exported" in the packed library whereas private are not.
2. Open the palette edit tool via Tools >> Advanced >> Edit Palette Set
3. Go to the subpalette you want to include your custom palette (exported items) and right click on the parent palette. Select Insert >> Subpalette.
4. In the dialog, select Create a new palette file (.mnu). Select a path contained in your lvlib.
5. Customize your subpalette as desired. Please place only public items on the palette.
6. Save the changes and add the new .mnu file to your lvlib.
7. Build the packed library. Make sure, that the .mnu file is part of the lvlibp (by default it is already selected).
8. Copy the lvlibp to the target system.
9. Select Tools >> Advanced >> Edit Palette Set in the target. Browse to the palette you want to have as parent for your lvlibp.
10. Right click and select Insert >> Subpalette. On the dialog, select Link to a palette file in a project library. Select your lvlibp file and acknowledge the following dialog.
11. Save changes and use your lvlibp on the target.
That should be a comprehensive step-by-step list for this request.
Hope this helps,
Norbert
[EDIT] Corrected some typos.
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Packed library and SQL Toolkit

Hi
I have labview development studio and I have made some test software that runs a test and posts the results to a database.
I have built the functions of the test in to a packed library
Another company will be using the packed library to test some pcb's for us. The problem is that they do not have the database module in their labview and so the database section of the code does not work.
Is there a run time program for the SQL toolkit I can give them?
Solved!
Go to Solution.

No, but you can replace them with these drivers and not have to worry about toolkits. Be sure to read the discussion too - it will give you other reasons why you are better off without the DCT. The download link for a current version of LV is on the last page of the discussion.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Having difficulty creating MNU for packed library

Hello All,
I am using a packed library and I am attempting to create a .mnu for it.
I want to be able to drop my packed library into the user.lib or vi.lib folder so my coworkers and I can use common VI's.
Every time I create the .mnu and add it to my packed library, my links get broken.
I can create a .mnu using the Edit Palette Set.
I can add the .mnu to my packed library.
I can import the packed library .mnu using the Edit Pallete Set. But at this time, any VI's inside that menu are now just broken links.
I have tried multiple processes. What I have observed is I cannot import VI's from the library. I have to import them prior to being packed. So I copy all my VI's to my user.lib folder.
However, the path does not match the packed library.
How do I make a .mnu for a Packed Library with subdirectories and no broken links?
I need to be able to put it in any folder with the links of the packed library not being broken.
I would like to use subdirectories for easy navigation.
Do I need to put the VI's into a folder named the same file name as my packed library to preserve the relative paths?
I have searched the forums and the help and I am missing something. Perhaps I am doing things out of order.
Any advice would be helpful.

I sort of answered my own question. Here is what I did, for those who have similar issues.
1.) Opened my packed library project.
2.) Selected the top level project item.
3.) When to tools -> advanced -> edit palette set. (This is why I selected the top level item. for me, this option does nothing unless I select a VI or some sort of project in the file tree first. I can also do it inside a VI with no problems.)
4.) Under the user libraries, I created a new subpalette.
5.) Under new subpalette, I selected the fourth option (link directly to directory)
6.) I browse to the directory where I stored my VI's in the packed library. I DID Not move them to the user.lib folder.
7.) Once the import was completed, the VI's appeared in my control panel under user libraries. I also customized my Icons and directory names at this point.
8.) A dir.mnu file is created as part of the import inside the folder my VI's are contained in.
9.) I right click on the top level library in the project viewer, and select properties. I set the dir.mnu file as the default .mnu
10.) I build the library
11.) I copy my packed library into the user.lib folder.
12.) I once again go to edit palette set, I remove the palette created in step 5.
13.) I create a new palette, this time choosing option 5 (link to palette file in a project library). The packed library is now part of my control panel. My Icons and directories are preserved.
My project structure is to create a folder with the packed library project. I then have a subfolder called VI. Inside that volder I store all of my VI's that are part of the packed library project.
This seems to work. But I need to do more testing. I used basic structures. I have not done one yet with a more elaborate scheme such as sub palettes.

How to deploy a single PBL (Build Runtime Library) in 64Bit

Hello There,
I am testing PB15 and create
two Project Files within the application. One Projectfile to compile a 32Bit Version and the other one to deploy a 64Bit version in P-Code. We are delivering today Patches in a Patch Library at the top of the library list (we are aware for the dependencies and know how to avoid the “Wrong Function Call” issue).
How can I create a Patch Library for 64Bit?
Today we just recompile the Patch.PBL two times and rename Patch.PBL -> Patch.PBD. But that did not work with 64Bit Project because I can’t choose the desired Platform (I am guessing it is always compiles in 32Bit).
There is an additional menu point “Build Runtime Library” which seems to have the settings / option similar to the Project settings. But there is the Platform the missing link either (see attached Picture).
So how can I get a single PBL compiled in 64Bit without deploying the whole Project?
BTW:
Compilation of the Whole app takes about 6 hours and results in full XCOPY deployment
of 730MB (in 64Bit), so we want wait that time or deliver so much files if a single
Patch.pbd of 500KB would be sufficient.
Regards
Marco

Hi Marco,
You should try orcascript to build your patches. It is much cleaner and faster.
I setup a .dat file with the orcascript and then run it using a .bat file.
this is my batch file command: OrcaScr125 build.dat >buildlog.txt
Note that the orcascr command is version specific. I have NOT tried this yet with PB 15 32 or 64 bit.
this is what the build.dat would have in it. The liblist has to be your lib list, same with the main applicaiton info.
NOTE: i regen a function in the script in order to set a patch date that users can see. Also, note that i copy the patch.pbl to a build directory, build it, then copy the .pbd to various locations.
start session
file copy "patch.pbl" "build\patch.pbl"
set liblist "build\patch.pbl; ...."
set application "C:\main.pbl" "app"
regenerate "build\patch.pbl" "f_get_patch_date" "function"
build library "build\patch.pbl" "" pbd
file copy "build\patch.pbd" "patch.pbd"
file copy "patch.pbd" "..\patch.pbd"
end session
regards
-mike

[svn:fx-trunk] 12087: Dev only. Checking in Flash Builder 4 " Library Projects" for building Flex SDK SWCs in trunk.

Revision: 12087
Revision: 12087
Author:   [email protected]
Date:     2009-11-21 20:56:09 -0800 (Sat, 21 Nov 2009)
Log Message:
Dev only. Checking in Flash Builder 4 "Library Projects" for building Flex SDK SWCs in trunk. These projects are easier to import and do not require linked resource variables to be specified.
Note: although the trunk does not build textLayout.swc, there appears to be a legitimate compiler error in FlowGroupElement.as as a cast is missing. I'll follow up with TLF.
QE notes: N/A
Doc notes: N/A
Bugs: N/A
Reviewer: N/A
Tests run: N/A
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/build.xml
Added Paths:
    flex/sdk/trunk/frameworks/projects/airframework/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/airframework/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/airframework/.project
    flex/sdk/trunk/frameworks/projects/airframework/.settings/
    flex/sdk/trunk/frameworks/projects/airframework/.settings/org.eclipse.core.resources.pref s
    flex/sdk/trunk/frameworks/projects/airspark/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/airspark/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/airspark/.project
    flex/sdk/trunk/frameworks/projects/airspark/.settings/
    flex/sdk/trunk/frameworks/projects/airspark/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/flex/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/flex/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/flex/.project
    flex/sdk/trunk/frameworks/projects/flex/.settings/
    flex/sdk/trunk/frameworks/projects/flex/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/framework/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/framework/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/framework/.project
    flex/sdk/trunk/frameworks/projects/framework/.settings/
    flex/sdk/trunk/frameworks/projects/framework/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/halo/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/halo/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/halo/.project
    flex/sdk/trunk/frameworks/projects/halo/.settings/
    flex/sdk/trunk/frameworks/projects/halo/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/osmf/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/osmf/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/osmf/.project
    flex/sdk/trunk/frameworks/projects/osmf/.settings/
    flex/sdk/trunk/frameworks/projects/osmf/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/rpc/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/rpc/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/rpc/.project
    flex/sdk/trunk/frameworks/projects/rpc/.settings/
    flex/sdk/trunk/frameworks/projects/rpc/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/spark/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/spark/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/spark/.project
    flex/sdk/trunk/frameworks/projects/spark/.settings/
    flex/sdk/trunk/frameworks/projects/spark/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/sparkskins/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/sparkskins/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/sparkskins/.project
    flex/sdk/trunk/frameworks/projects/sparkskins/.settings/
    flex/sdk/trunk/frameworks/projects/sparkskins/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/textLayout/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/textLayout/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/textLayout/.project
    flex/sdk/trunk/frameworks/projects/textLayout/.settings/
    flex/sdk/trunk/frameworks/projects/textLayout/.settings/org.eclipse.core.resources.prefs
    flex/sdk/trunk/frameworks/projects/wireframe/.actionScriptProperties
    flex/sdk/trunk/frameworks/projects/wireframe/.flexLibProperties
    flex/sdk/trunk/frameworks/projects/wireframe/.project
    flex/sdk/trunk/frameworks/projects/wireframe/.settings/
    flex/sdk/trunk/frameworks/projects/wireframe/.settings/org.eclipse.core.resources.prefs

Status Update - don't know if this is a bug, design flaw, install problem or my misunderstanding.
I got it to work by first changing my Flex library to 4.5.0 - still didn't work with current
app and update mxml files using "2.6" for their namespace versions. But I did at least
get the popup error number 16815 - indicating an error in the update version namespace.
By leaving my application namespace version at "2.6" and changing the update version to "2.5" ... bingo!
I got my new update installed autiomatically.
Is this how it's supposed to work - or are my runtimes mixed up?
Will this work the same using the Flex 4.5.1 SDK? I'll find out shortly
Hope this helps others.

Best Practice Building Block Library not accessible in Firefox

Hello SAP Documentation Team,
I've just get aware of the <a href="http://help.sap.com/bp_bblibrary/500/BBlibrary_start.htm">Best Practice Building Block Library</a>. Unfortunately it can't be used with Firefox 1.5.0.4 because of a script error. I see the dropdown lists but when I select for example Country "Germany" nothing happens. In IE it works perfect.
Regards
Gregor

Hope that this will change with later Best Practice releases.

HT3986 i purchased windows 7 from amazon and i just received it. they sent me windows 7 home premium "OEM System Builder Pack". the instructions say "Intended for system builders only". also says " must be per installed on the hard drive of a fully assemb

i purchased windows 7 from amazon and i just received it. they sent me windows 7 home premium "OEM System Builder Pack". the instructions say "Intended for system builders only". also says " must be per installed on the hard drive of a fully assembled computer system, using the OEM Preinstallation kit (OPK)."

System Builder - just be sure to get 64-bit version, no one needs or wants 32-bit today, and only comes with one, while retail ships with both 32/64-bit media.
you can't install it and activate on different hardware later is all, and by then for what you saved, so what, Windows 8 or SP2 will be out.
A few people had trouble with Windows 7 SP1 for some reason and not sure exactly why, changes to the boot loader on the DVD I presume.

Syncing issues, iPhoto won't build new library

I have two macs - an eMac and an iBook G$. Both are running iPhoto 5.0.4. but I wanted to sync the photo libraries. I made a folder on the desktop of the eMac called "iPhoto Library - New" and dragged the contents of the iBook library over to it. Once it was complete, I dragged this folder into the pictures album next to the original iPhoto Library. Since I couldn't remember the short cut for choosing a new library, I renamed the old one knowing that iPhoto would prompt me to select a library when I opened it. I launched iPhoto and went to select the new library but it won't select it. I read through the old posts and wanted to rebuild the library but it won't allow me to do that - it asks me to select one first. Since it won't let me select neither the new library nor the old library, I thought I would build a new library then import the photos into it as on http://discussions.apple.com/thread.jspa?threadID=550004&tstart=0
but now it won't let me build a new library either. When I click build new library, the window disappears like it is going to do something but nothing happens, the program stalls with most of the menu selections grayed out.
What I really want to do is get my laptop pics into the desktop comp. I don't care about the keywords but I do want to keep the dates and both the original and edited versions of the photos intact (so I can still revert to original if necessary). Any suggestions on what I need to do from this point? Thanks in advance for any assistance.

I knew there was no reason why it shouldn't have worked the first time! I restarted my mac, opened iPhoto, and was able to select the imported Library as my default. Thanks anyhow!

LabVIEW hangs building packed library

Similar Messages

Maybe you are looking for