Rename LVLIB containing LLB

Please can someone correct me if I am trying to use the LabVIEW file structures incorrectly.
I have built a self contained instrument driver - contained in an LVLIB
It references some code written by the H/W manufacturer that was supplied in an LLB.
Problem:
The whole point of going the LVLIB rout is that when I get a different variant of the H/W which requires different setup parameters or talks on a different protocol speed (but uses the same command set defined but the manufacturer in the LLB) I want  to create a new LVLIB for the new project I'm working on so that my S/W modules match the H/W modules.
When I do this all the LLB references fall apart and require resorting with LLB manager.
If I save the LVLIB as... the save corrupts.
Is there a solution to this - other than remove the code from the LLB?
James
Solved!
Go to Solution.

The "Fancy container" is just that -  a problem.
the reason for including the LLB code in the LVLIB is that if I have driver code for Instr 1 and Instr 2 which are both variants of the same instr using the same LLB code but configured a level above totally differently, then when I add them to a project I don't get conflicts.
If I move around the folder containing the LVLIB driver code the LLB code always goes with it. (a small overhead but one that so rarely happens that the disk overhead is worth the hassle of not resolving project conflicts).
I guess I'll have to take the code out of the LLB.
There isn't a programatic way to do this is there (in case the manufacturer updates the LLB code?)

Similar Messages

  • Lightroom doesn't allow me to rename folders containing pictures and videos.

    I'm using lightroom version 5.7 on a Windows 8 machine. in the library page Lightroom won't allow me to rename folders that contain video files. Works fine on folders that only contain pictures.
    any thoughts on how i solve this?

    Edward Chatlos wrote:
    IMHO you are using the wrong tool/program for renaming folders on your drive. You should use a File Manager program for that. Something like Windows File Explorer. LR is not a File Manager although it does allow you to do certain tasks.
    You should set up your image and video folder structure/system long before you import images and videos into LR's Catalog Database.
    It may be your humble opinion but is certainly not even close to being on the button. Why do you think it is allowed in Lightroom along with the creation and deletion of folders and files off the HD with Lightroom. Maybe try offering an answer.
    OP, do these folders that won't rename also contain images as well as videos? Where are the folders located?? I can't see how Lightroom could cause this as it calls the OS to do this but sometimes weird things happen.
    It may pay to remove the Lightroom Preference file as well. A corruption there can result unexpected problems: https://helpx.adobe.com/lightroom/kb/preference-file-locations-lightroom-41.html

  • Renaming function contained @  in the DLL

    Hello every one.I have a bunch of code . THis code connect t othe exteral library:
      public interface TransToQuik  extends Library{
    public int  _TRANS2QUIK_CONNECT@16(String lpcstrConnectionParamsString, LongByReference pnExtendedErrorCode, String lpstrErrorMessage, int dwErrorMessageSize);
      LongByReference pnExtendedErrorCode= new LongByReference();
        String Error;
        int len;
        int FunctionResult=0;
        String lpstrErrorMessage="";
        int dwErrorMessageSize=0;
        TransToQuik lib = (TransToQuik) Native.loadLibrary ("D://java project//Robot//TRANS2QUIK.dll",TransToQuik.class);
       FunctionResult=lib._TRANS2QUIK_CONNECT@16("D://QUIK5.15//",pnExtendedErrorCode,lpstrErrorMessage,dwErrorMessageSize);
        System.out.println(lib);But it is do not work cause the JAVA do not understand function contained @ in the name. In iinteret i find no examples. Please help me.

    For the future it would be useful to mention which libraries you use. In your case it seems to be JNA.
    Since that function hasn't got a name that's a valid Java name, I doubt that you can easily call it like that.
    But from the documentation it seems that there is at least one other way to call native functions with JNA:
    [Create a Function object|https://jna.dev.java.net/javadoc/com/sun/jna/Function.html#Function(com.sun.jna.NativeLibrary,%20java.lang.String,%20int)] and call that objects invoke() method.
    Edit: By the way, the name of the language and platform is "Java". It's not "JAVA", because it's not an acronym.

  • Loosing weight - creating LLB plug-ins, using lvlibs, minimizing LLB size

    Greetings,
          Is there a way to build LLBs which include specific VIs from VI-lib, without including all VIs from VI lib?
    I added a function from AALPro.vilib to hierarchy and, as expected, it didn't show-up in the LLB after the build.  In the past I've re-written VIs from VI-lib but I'm getting lazy, so I un-checked "Exclude Files from VI lib" in [LV8.5] project-properties - and the size of the plug-in jumped from 13M to ~50M.  I'm hoping there's a way to minimize this weight-gain - an easier way than re-writing the function/hierarchy from AALPro.
    Any help is appreciated.
    Cheers!
    Message Edited by tbd on 04-16-2009 04:04 PM
    "Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
    Solved!
    Go to Solution.

    The original Interpolation-Spline function was called from one location and with Start/End conditions wired from constants.
    Since there didn't seem to be a simple way to avoid adding hundreds of VIs to the hierarchy, I went ahead and re-wrote the Interpolation-Spline hierarchy for the "not-a-knot" case.
    This LLB is about 0.2M, saving about 40M and allowing LLBs to be created from the File\Save-As dialog (a time-saver during debug.)
    In this case, about 40M of code was unreachable - a fact known or knowable at compile-time IF only static-linking is assumed.  How about a compiler-optimization/switch called "assume static links" so the compiler can drop unreachable code?  Is the LV8.6(.1) compiler any better about this?
    Thanks/Cheers!
    "Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
    Attachments:
    Util.Math.IS_InterpolationSpline.NotAKnot.llb ‏205 KB

  • Make VI or LLB Writable

    Hello, I have an LLB with VI's from an equipment vendor. I just upgraded to LV2012 and when I open the LLB or the VI's inside they are recompiled for the new LV version. When I exit labview it asks if I would like to save changes, i.e. the recompile, which I would. If I click "Save" I get a "you don't have permission to write to the containing LLB" message. I've also tried to mass compile the LLB but get a "CompileFolderCore: error 8" which is a permissions problem I believe. If I right click on the LLB in Windows 7 the "Attributes: Read Only" box is NOT checked. How can I change the permissions on this LLB or recompile?
    Thanks,
    Ed

    edward_01 wrote:
    Hello, I have an LLB with VI's from an equipment vendor. I just upgraded to LV2012 and when I open the LLB or the VI's inside they are recompiled for the new LV version. When I exit labview it asks if I would like to save changes, i.e. the recompile, which I would. If I click "Save" I get a "you don't have permission to write to the containing LLB" message. I've also tried to mass compile the LLB but get a "CompileFolderCore: error 8" which is a permissions problem I believe. If I right click on the LLB in Windows 7 the "Attributes: Read Only" box is NOT checked. How can I change the permissions on this LLB or recompile?
    Thanks,
    Ed
    I have seen third party library files locked by default and they release it for the different version so when you upgrade your whole library some of the vi's at the top level gets compiled but the low levels vi's are not. So check about the library file and also check your third party whether they have any release for the latest version.
    The best solution is the one you find it by yourself

  • .llb file Lower Version Conversion

    Hi,
    Looking for some guidelines to convert the .llb file into lower versions of LabVIEW. The thing is we have an instrument driver project created using LabVIEW 8.6, containing public and private folders and some .mnu files as well. I can save the whole project into the lower version, for say 8.0, using "Save for Previous Version" that again compiles and saves the whole project into another folder. The newly 8.0 project I opened and found that the private folders (containing .llb files) and .mnu file in public folders are still pointing to the older location i.e. 8.6 location. I removed the 8.6 code from its location and manually added private files to point to the 8.0 location. After I create installer for 8.0 codes using project file, I installed on new machine and found that private and .mnu files are missing and therefore could not proceed further. I can understand that .mnu files won't require any conversion but wondering why my 8.0 project are considering 8.6 location at all even after manually adding all the missing files back into the 8.0 code from 8.0 location. 
    Please do suggest me if anyone has any idea for the same. Looking Forward.
    Thanks in Advance,
    Vivek

    Hi,
        The problem seems to be with the way the project folders are saved. There are two types of folders viz Virtual and Autopopulating. By default when you create new instrument drivers project , Virtual folders are created. You need to convert them to Auto populating folder as shown in the figure below. Autopopulating folder refrences and updates as and when you make any changes to the actual file. Whereas A virtual folder is a folder in the project that organizes project items and does not represent files on disk.
    Hope that solves your querry. 
    Shreyas Hebbare
    Shreyas Technologies
    India

  • VI Name conflicts with "Open VI reference"

    I am using LabView RT, where an application loads LLBs at runtime:
    1- The user creates/compiles a LLB containg a VI that is loaded at runtime later
    2- The user renames the contained VI to an enumerated name so that all names are always unique
    3- The user uploads the LLB (containg the VIs with a unique name) to a LabView RT system
    4- The LabView RT application openes all available VIs contained by the uploaded LLBs at runtime (the filename hints at the VI's unique name)
    5- The LabView RT application executes the now opened VIs
    My problem is step 2 where the user needs to rename the VI. This is because the RT application will not be able to distinguish between the opened VIs if their names are equal. I want to eliminate step 2 because it's error prone as the user always forgets to do the renaming or the user does the renaming in a wrong way (e. g. non-unique, typo).
    A dirty hack would be to automatically replace all VI name strings (which are alidentical and like a placeholder) inside the LLB binary with unique ones at RT application's runtime. So the application takes over the renaming task.
    Any other solution?

    Hi Salim,
    This CORBA support being moved from SP2 to next release.
    Honghsi
    Salim Djaffar wrote:
    Andy Piper <[email protected]> wrote:
    "Eric Green" <[email protected]> writes:
    Andy Piper <[email protected]> wrote:
    For what it's worth, except for the error message WTC appears to
    be functioning fine in a clustered environment.Right. It will mostly work, but there are some issues with the CORBA
    support.
    When is the ballpark release date for SP2? Is WTC at SP1
    now, or is this two updates away?I mean WLS 6.1 SP2. I do not know what the timeline is for these
    things.
    andy
    --I also experienced the same problem, and I planned to go production within a month
    or two.
    Do you have any estimate when SP2 will be GA for public ?
    salim

  • Error 10 occurred at New VI Library.vi when building .exe

    This is driving me crazy!  What is causing this.  The program worked fine in 8.5.1 and before.  The only thing that has changed is that I had to create directories for each class in the Microsoft Report Generation Toolkit which was a huge pain itself.  See Building an EXE in LabVIEW 8.6 using the Report Generation Toolkit application note for more information.  Anyway, any suggestions would be much appreciated.

    After a lot more testing I think I have identified the problem.  Our executable uses the Microsoft Report Generation toolkit.  Due to how LabVIEW 8.6 has implemented the toolkit, it creates directories for each class of the toolkit to prevent name collisions.  Maybe LabVIEW should start using namespaces.  Anyway, we did not want the code to be visible to out customers.  We wanted it to be in a single executable.  So I found a knowledge base article that addresses the issue.  It's called "Managing the Resulting Files from a Build Containing LabVIEW Classes" and it's document id is 4OKDCDES.  Anyway this article says to add .llb destinations into the build so that instead of 5 directories with exposed VIs, you get 5 .llb.  This worked ok with no build issues, but then the article said to rename the .llb to .dll so the extra directories would appear to look like dlls.  The first time you build this it works, but if you build it again, it fails and you get error code 10.  You can then build it again and it will work.  So the problem has to do with renaming the extra .llb to .dll. 

  • Best Practices - Distributi​ng Dynamic VI's with LV2011

    I'm distributing code which consists of a main program which calls existing (and future) vi's dynamically, but one at a time. The dynamically called vi's do not have input or output terminals. They run, one at a time, in a sub-panel in the main program. The main program needs to maintain a reference to the dynamically loaded vi so it can be sure the dyn. loaded vi has fully stopped before unloading calling a replacement vi. These vi's do not used Shared Variables or Globals, but may have a few vi's in common with the main program (it would be OK to duplicate these vi's in the release).
    With that background, what are the best practices these days for releasing dynamically loaded vi's (and their dependents)?
    If I use a Project Library (.lvlib), it would seem that I need to first build a .exe containing the top-level vi's (the one's to be dynamically loaded), so that a separate .lvlib can be generated which includes their dependencies. The contents of this .lvlib and a .lvlib containing the top-level vi's can then be merged to create a single .lvlib, and then a packed library can be generated for distribution with the main .exe.
    This seems way too involved (but necessary?)
    My goal is to simply have a .exe for the main program, and some other structure containing the dynamically called vi's and their dependents. This seemed so straighforward when a .exe was really a .llb a few years ago
    Thanks in advance for your feedback.
    Solved!
    Go to Solution.

    A great source of information I've found since posting is here:
    http://zone.ni.com/devzone/cda/pub/p/id/1261
    regarding packed libraries. Bottom line - they automatically include dependencies to the top-level dynamically linked vi's placed in a .lvlib from which the .lvlibp is built..
    I cannot seem to find an example of dynamically calling a vi within a packed library. If I use the old .exe as llb method, I get an Error 7.

  • Replacing programmatically VI's

    Until now we supplied a library called AqDx.llb which contains a lot of VI's with AqDx prefix in the VI's name, like AqDx Init.vi, AqDx Close.vi etc.
    Now we want to supply a new generation of the library who was renamed to AqD1.llb and with AqD1 as prefix of VI's name, AqD1 Init.vi, AqD1 Close.vi etc.
    It is possible under LabVIEW to replace programmatically in a VI all sub-VI's of the AqDx.llb library by the corresponding VI's of the AqD1.llb library ?
    (AqDx::AqDx Close.vi --> AqD1::AqD1 Close.vi)
    Briefly, we want to supply a migration tool to our custumer.
    Thanks a lot in advance !
    levent

    In the past this was a pain to do, you had to do it manualy.
    Now checkout the undocumented LabVIEW VI Scripting.I made an simple experiment:
    If you stick to documented LabVIEW, you can rename all old vi's to the new name ( using save instrument invoke node).
    Then unload all callers and old from memory.
    file copy then new vi's over the renamed old vi's.
    Reload everything, now with the new vi's, and save.
    Attachments:
    replacer.vi ‏49 KB
    test.llb ‏18 KB

  • Why can't I open, update, uninstall or install itunes?

    I can't open my itunes, I have gone through the support on Apple website, but when I try to uninstall itunes (as it says to do) it gives me an error message. I can't figure it out.
    An error occured while trying to create the directory c:\Program Files\iTunes.Resousces\fi.lproj\CDPlaylistPlacard.nib
    Then it tells me
    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2330.

    That error is consistent with a damaged file: c:\Program Files\iTunes.Resousces\fi.lproj\CDPlaylistPlacard.nib
    First run a disk check:
    http://support.microsoft.com/?kbid=315265
    If that fixes errors, try installing again.
    If not or the problem remains, try renaming CDPlaylistPlacard.nib
    As something else.
    If Windows will not allow you to do it, then rename then containing folder. This will prevent the iTunes installer seeing the damaged file.

  • Warning message on log off when application is running

    How can I make a warning message when a user is trying to logoff windows while an application made with labview is still running ?
    I want to pop something that ask the user if he's sure he wants to quit.
    thanks

    I was working on just this issue today. Here is a vi (in 7.1.1) and an exe showing it. The exe has been renamed to a .llb to get around some attachment restrictions, so rename it (after scanning with you antivirus of choice!).  I can make it in 8.0 if needed (don't currently have 8.2 installed)
    Putnam
    Certified LabVIEW Developer
    Senior Test Engineer
    Currently using LV 6.1-LabVIEW 2012, RT8.5
    LabVIEW Champion
    Attachments:
    shutdown.vi ‏31 KB
    shutdown.llb ‏62 KB

  • 9.0.4 install fails due to listener.....HELP !!!

    HI ALL
    I am trying to install 9.0.4 AS on Sun OS 5.8 with 9.0.2.3 already installed in separate home. I receive error - shutdown listener in 9.0.2.3 home or use same listener for 9.0.4 install as well.
    I don't want to use same listener for new install. Now how can i change the listener port for new install. Is there any config file like port.ini, which i can change during install.
    Thanks
    Amit

    Sometimes this type of error is caused by a corrupt file if you are sure permissions are OK.
    Try running a disk check to see if that fixes anything.
    If it doesn't try deleting the problem file. If that doesn't work try renaming it.
    If Windows will not even let you rename it, try renaming the containing folder.
    After that, try installing again, the installer should not see the bad file and hopefully it will go through OK.

  • How do I really(!!) change the default ringtone?

    I have a ringtone on my IPhone 3GS which appears correctly amongst the other tones. When I click upon it, a check mark appears and the sound plays successfully. It is 29 seconds long. But when my phone rings, a different tone (which is marked 'default') is used for the ring instead of the checked one. That different one is marked 'default'. I had thought that clicking upon the ringtine sets it as the default. How can I change the default so that this tone is used instead of the one marked default. Online web instructions say that clicking ought to be enough to select the ringtone used.  When I click upon other tones listed, the 'default' designation does not change to them as well.
    Although I do not believe that it is relavant, the following additional information is supplied:  Please note that this ringtone was made by me from a downloaded piece of music. Once before, I had made this into a ringtone, and that time successfuly. But I lost it when I inadvertently reset the phone. Since then, ITunes has changed four times, and this time it would not load the ringtone, even though the ITunes itself had made it. That is why I resorted to an external program. (Yes, I did follow the renaming instructions contained in some of them to verify it ended in 'R'.) An external program, IFunBox was used. It found the file, recognized it as a ringtone, and copied it into the IPhone, where it shows up as a ringtone within Settings.
    I believe if I could find a way to make it the 'default', the phone would use it..
    Thank you

    Jon:
    Dragging the thumbnails to the desktop and exporting are essentially the same process, producing copies of the full sized image file. Exporting gives you other options, however. Once you get the photos out of iPhoto you can run PhotoInfo on them and then import as new files. iPhoto will see those new files with the correct date. If you try running PhotoInfo on files already in iPhoto, you can change the EXIF Capture Date in the file but iPhoto won't recognize the changes.
    Do you Twango?
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've written an Automator workflow application (requires Tiger), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.

  • CRIO: Unflatten from string into lvclass not working in deployment

    Hello,
    I am working on a problem for some hours now and I need some help.
    I am using a cRIO-9022. I need to do some tasks, and I created a couple of classes which contain the parameters and the methods. They contain using dynamic dispatch VIs. I have an array of these classes (all derived from a parent class) which is my "configuration". I am using "flatten to string" and saving those file on disk. "Unflatten from string" is working fine. These file is created on a LV WIndows Application.
    I need to use this file on my cRIO: Unflatten from string, and then work with the array of my classes. When running the cRIO Main VI it's working fine. But when building the application and deploying it as startup, it's not working. I am getting:
    Error 1403 occurred at Unflatten From String in Gantry CommEngine.vi->RT Main.vi
    Possible reason(s):
    LabVIEW:  Attempted to read flattened data of a LabVIEW class. The data is corrupt. LabVIEW could not interpret the data as any valid flattened LabVIEW class.
    What I tried so far:
    - Added the whole lvlib containing the classes and also every single class to "Source files / always included".
    - Created constants of the array (containing the classes) to the VI (forcing LV to include the classes?)
    - Loaded the file from cRIOs flash and also by shared variable
    What else can I do?
    Thanks a lot for support!

    I tried to reproduce the matter, but couldn't. 
    I attached my example to the post. 
    What it does:
    It creates a class with only a string a bool and a number. This class oblect is saved to C:/somename.xml. The number is a random number.
    In the second case the same file is read and the number broadcasted to a variable.
    It worked quite fine building it as a startupexe.
    Nothing else was necessary. Does it work for you?
    Attachments:
    class exe.zip ‏45 KB

Maybe you are looking for