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

Similar Messages

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

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

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

  • Labview 2013 report generation toolkit word 2010 insert table problem

    Hi,
    I am currently evaluating LV2013 with respect to the report generation toolkit for use with word 2010. My Vi/program won't insert the correct table and gives me an error message. see below:-
    Exception occured in Microsoft Word: The requested member of the collection does not exist.Help Path is wdmain11.chm and context 25421 in NI_ReportGenerationToolkit.lvlib:Word_Insert_Table​.vi->NI_Word.lvclass:Append Text Table to Report.vi->Word Table save.vi
    I have since run the following word example.vi provided by NI within LV2013 office examples:- Growable table.vi. this gives me the same error!
    Exception occured in Microsoft Word: The requested member of the collection does not exist.Help Path is wdmain11.chm and context 25421 in NI_ReportGenerationToolkit.lvlib:Word_Insert_Table​.vi->NI_Word.lvclass:Append Text Table to Report.vi->Growable table.vi
    It would seem that regardless of my own Vi there is a fundamental problem in the office example vi.
    I have found examples of a similar problem in LV2011/2012 but the work around code doesn't seem to match the LV2013 vi's code for a direct replacement.
    Can anyone help/shed some light on this? 
    Thanks in advance,
    Dan.

    Because the upgrade of Word from 2007 to 2010 I needed to upgrade an existing application from LabVIEW 2009 to 2013. This didn't work because of the insert table error. I discovered that the problem is the vi called "Word_Insert_Table.vi" located in the ..Program Files (x86)\National Instruments\LabVIEW 2013\vi.lib\addons\_office\_wordsub.llb. There is a "Cut" command implemented, this command removes the created cell instead of clearing it. Therefore the table will be filled half and then returnes with an error. I have removed this command. I have posted the changed vi (LV 2013).
    Attachments:
    Word_Insert_Table.vi ‏30 KB

  • FPGA FlexRIO SCTL LabVIEW 2013 Compilation Problems

    Hi,
    I have an FPGA FlexRIO (7962R) VI that interfaces to a 6585 LVDS board that consists of a SCTL running at 200MHz and using a Xilinx Coregen FIFO.
    In LabVIEW 2012 using Xilinx 13.4 I have had no problems compiling this at 200Mhz, but in LabVIEW 2013 using Xilinx 14.4 I am unable to get it to compile reliably about about 170MHz with absolutely no modifications to the code.
    The Xilinx FIFO is probably irrelevant as I have tried cloning the VI and removing the FIFO and still get the same problem.
    Any ideas, things to try or solutions? 
    Thanks,
    Dave
    David Clark
    CLA | CTA
    CLA Design Ltd
    Hampshire, England

    Have you tried optimising the Xilinx compiler for Timing?
    You can't modify the Xilinx compile options of a FlexRIO target.
    In LabVIEW 2012 using Xilinx 13.4 I have had no problems compiling this at 200Mhz, but in LabVIEW 2013 using Xilinx 14.4 I am unable to get it to compile reliably about about 170MHz with absolutely no modifications to the code.
    What compile error are you getting? Does not reliably mean that sometimes it does compile correctly? Can you upload a simple example of a piece of code that works in 2012 but not 2013?
    National Instruments
    FlexRIO Product Support Engineer

  • DAQMX vi files missing in Labview 2013

    I try to open this file slinger-logger.vi [see attachment], but I can't open it, because it is missing files such as DAQmx Clear task.vi
    I already tried to install several versions of DAQmx (14.1, 9.9, 9.4):
    http://digital.ni.com/public.nsf/allkb/B0D5630C0A5​0D5C6862578E800459248
    But I couldn't get the file working without those missing vi errors. Can anyone get this file working in Labview 2013? Or Labview 2012?
    Attachments:
    Slinger-logger.vi ‏70 KB

    kihans wrote:
    I already tried to install several versions of DAQmx (14.1, 9.9, 9.4):
    http://digital.ni.com/public.nsf/allkb/B0D5630C0A5​0D5C6862578E800459248
    But I couldn't get the file working without those missing vi errors. Can anyone get this file working in Labview 2013? Or Labview 2012?
    Why do you install random version of DAQmx, especially since 9.4 does not even support the LabVIEW 2013 or 2012 versions you mentioned. You even show the link outlining that! Pick the neswest one only!
    Tell us exactly what you did:
    Did you install DAQmx after installing LabVIEW and did you select support for the installed LabVIEW version?
    Did you reboot after installation?
    LabVIEW Champion . Do more with less code and in less time .

  • Read access mdb file in labview via ADO/DAO problem

    Hi guys,
    I am now facing one problem that I want to import ACCESS database (ver2000) files into labview and turn it into tables.
    but if I use ADO(actually using LABSQL) I have to create the ODBC in control panel, if I use DAO, I don't know how to call the activeX method.
    I would like to realize like this:
    choose in a directory which mdb file I would like to open, and then open it and show it in a labview table, but using AD0 I have to create connection for each file, does it stand a chance to open it without specify the connection in control panel?
    He Liang

    You can use a Connection String defined by you like this
    You can get the basic connection string by creating a UDL file and editing that file in Wordpad.
    Hope this helps
    David
    Message Edited by David Crawford on 11-27-2006 01:04 PM
    Attachments:
    Connection String.jpg ‏13 KB

  • How can I enable Windows Explorer (Windows 7 64 bit) to open LabView 8.2.1 LLB files?

    How can I enable Windows Explorer to open LabView LLB files? I am running LabView 8.2.1 on Windows 7 64 bit. The option “Enable Windows Explorer for LLB Files” in Tools/Options/Environment is unchecked and grayed out.

    LabVIEW until 7.1 came with a shell extension that could display the content of an LLB in an explorer window.
    That was removed in LabVIEW 8.x for  a number of reasons.
    - Shell extensions are pretty badly documented, tricky to implement right, and of very limited use since only Windows Explorer and a few explorer replacements can use them. It doesn't add any functionality for most other programs in Windows, since the shell extension are a Windows Explorer thing, and not a Windows core technology.
    - With 8.x NI decided that LLBs were pretty old fashioned and their main feature of supporting file names longer than the DOS 8.3 naming was pretty much obsoleted by then, while they didn't allow for more than one level of directory hierarchy. So they decided to depreciate LLBs and declared them a legacy technology that should not be used for new development anymore.
    - For the uupcoming 64 bit version of Windows a new shell extension would have been required to allow Explorer to use it.
    For all these reasons the LLB shell extension was removed from the LabVIEW installation to further discourage the use of LLBs.
    If you have a LabVIEW 7.0 or 7.1 installation on your computer and run 32 Bit Windows you can enable the shell extension in the LabVIEW Options dialog.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • LabVIEW 2013 Patch f2 update problem

    I have installed LV 2013 (13.0.1f1) Patch f1 (32-bit). I tried to install NI LabVIEW 2013 f2 Update but I got error message: "NI LabVIEW 2013 must be installed before you can install this update."
    So, why it doesn't recognize installed app?
    BR,
    Jick

    There is a difference between
    LabVIEW 2013 f2-Patch and
    LabVIEW 2013 SP1 f2-Patch
    Choose the right one.

  • Report Generation Toolkit failure with Win 7 and Labview 2013

    I recently had my computer updated to Windows 7 and am now seeing a problem with the Report Generation toolkit (version 2013) when working with Excel files.  If I try to run the New Report.vi with report type Excel selected I get  error -2146777998.  Doing the same thing with Word selected eventually opens Word, although this takes about ten seconds, but it does not generate an error.  Selecting Standard Report or HTML also run without errors.
    I've researched this error on line but I keep ending up .NET and C# forums where everything goes over my head. Has anybody got any suggestions?
    Solved!
    Go to Solution.

    I found the solution to this particular source of error code -2146777998. There are two template files that reside in C:\Program Files (x86)\National Instruments\LabVIEW 2013\templates\Report  by the name of MSOffice_RGT_Template.dot and MSOffice_RGT_Template.xlt.  The problem came down to that these templates got corrupted somehow during the fresh install. As soon as I replaced them with versions from another machine the problem disappeared.
    Just as a side note, I discovered the problem by kicking off the MS Office Report Express vi and out came a much clearer message that aimed me at the templates. Not quite sure why that message isn't echoed into the individual subvi's on the pallette, but life is a mystery.

  • How can I read pdf files from LabVIEW with different versions of Acrobat reader?

    How can I read pdf files from LabVIEW with different versions of Acrobat reader?
    I have made a LabVIEW program where I have possibility to read a PDF document.  When I made this LabVIEW program it was Acrobat Reader 5.0.5 that was installed on the PC. Lather when the Acrobat Reader was upgraded to version 6.0, there was an error when VI tries to launch the LabVIEW program. And Later again when we upgraded to Acrobat Reader 7.0.5 I must again do some changes and rebuild the EXE files again
    It isn't so very big job to do the changes in one single LabVIEW program, but we have built a lot of LabVIEW programs so this take time to due changes every time vi update Acrobat Reader. (We have build EXE files.)
    The job is to right click the ActiveX container and Click "Insert ActiveX Object", then I can brows the computer for the new version of acrobat Reader. After this I must rebuild all the "methods" in the Activex call to make the VI executable again.
    Is there a way to build LabVIEW program so I don't have to do this job every time we update Acrobat Reader?
    This LabVIEW program is written in LabVIEW 6.1, but I se the problem is the same in LabVIEW 8.2.
    Jan Inge Gustavsen
    Attachments:
    Show PDF-file - Adobe Reader 7-0-5 - LV61.vi ‏43 KB
    Read PDF file.jpg ‏201 KB
    Show PDF-file - Adobe Reader 5-0-5 - LV61.vi ‏42 KB

    hi there
    try the vi
    ..vi.lib\platform\browser.llb\Open Acrobat Document.vi
    it uses DDE or the command line to run an external application (e.g. Adobe Acrobat)
    Best regards
    chris
    CL(A)Dly bending G-Force with LabVIEW
    famous last words: "oh my god, it is full of stars!"

  • Slow LabView 2013

    Hi
    I have Labview 2013 Professional Dev Sys SP1 ver 13.0.1f2 (32-Bit) and it is slow when I develop any aplication.
    For example, if I have a tab control and I change to another tab, it takes about 2 seconds to change tab after I click it.
    If i wire a new line, it takes 2 seconds to appear that line in block diagram, and so on.
    I have a new computer Dell Optiplex 7010, i7 Processor 3.40Ghz, 64-Bit, 4Gb RAM, WIndows 7 enterprice SP1
    If i run Windows task manager it shows 17% CPU usage and 2.14 GB Memory.
    If I run for example, excel 2013 it does not seems slow.
    Do you have any suggestions ?
    Regards
    Solved!
    Go to Solution.

    EDGAR_PLATRONICS wrote:
    Hi Yamaeda:
    I am not sure about mass compile. You mean rewrite code ? Or create exe file and test?
    A this moment I have checked with only one Vi but it is very large. Many sub VIs and code.
    Actually it worked correctly in labview 8.5 but i converted to LV 2013.
    I will research about transparent borders overlapping.
    Hi Altenbach:
    17% is overall. 3 cores are high % than others.
    The problem is at edit mode and also when I run program.
    Yes I have many front panel indicators, but I do not think they have tons of data but I will double check.
    When I open my VI in labview it shows 118 MB memory when running and 124MB at edit mode
    By the way, last week when by mistake I moved a part of code to some centimeters below, block diagram was frozen and was been updated to new position but line by line until complete full screen. I took about 5 minutes to work normally.
    I am using 2 monitors in my PC. One to display LV panel and one for LV code.
    I meant Tools -> Advanced -> Mass compile and recompile your upgraded code. In the same manner a ctrl+run array will force recompile your program. It can help. Else you're down to e.g. using VI analyzer tool to find the culprit, it might be some VI that's corrupted and needs to be moved to a new VI.
    /Y
    LabVIEW 8.2 - 2014
    "Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
    G# - Free award winning reference based OOP for LV

  • .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

  • Bug in LabVIEW 2013 RTETT Download

    I've called this in to NI, but am posting it here in case you've downloaded LabVIEW 2013 before they fix the problem.
    Downloading the toolkits from ni.com/trylabview usually is a three-step process.  First, you download a "downloader", a small program (154 KB) that manages the download of the Installer.  When you run the Downloader, it downloads the Installer, usually as an executable ZIP file.  The final step is to run the Installer, which first unzips itself into a folder (by default, C:\National Instruments Downloads), then executes the unzipped Setup.exe contained therein.
    There is a (usually) consistent naming convention to these various files.  For example, the files for LabVIEW Real Time are 2013RealTime-Eng_Downloader, 2013RealTime-Eng (the Installer), and LabVIEW RT (the name of the folder that the Installer "unzips" into).  I've downloaded 8 modules, and (with the exception below) they all follow a similar pattern.
    The "bug" is in the Real Time Execution Trace Toolkit (RTETT).  The Downloader is 2013RTETT_downloader, and it brings in 2013RTETT as the Installer.  However, the Installer is set to unzip into LabVIEW RT, the same folder that is used for LabVIEW Real Time.  The "fix" is to change the name of the UnZip folder to LabVIEW Real Time Trace Execution Toolkit (this name is analogous to the LabVIEW Desktop Execution Trace Toolkit name for 2013DETT).  Alternatively, you can run one installer, rename the folder, run the other, and adjust the folder names to your liking.
    Bob Schor

    I am using Windows 7 (x64), fully patched.  As I understand it, the purpose of the Installers is two-fold -- to extract themselves to individual folders (by default in C:\National Instruments Downloads) and then to run their respective Setup executable to actually install themselves.
    I have not (yet) installed RTETT, but I have installed LabVIEW RealTime.  However, in the interest of time-efficiency, I first did downloads of all of the elements I wanted to install (which included both RealTime and RTETT), ran the Installer, but only the "extractor", then planned to run the actual installations from the folders in the Downloads folder.  That's when I discovered that the folder labelled LabVIEW RT did not contain LabVIEW Real Time, but LabVIEW Real Time Execution Trace Toolkit.  Thinking I'd forgotten to extract Real-Time, I tried extracting it again, and discovered that it and RTETT "shared" the same folder in NI Downloads.  I fixed the problem for myself by manually relabelling the folders so one was LabVIEW RT (for LabVIEW Real Time) and one was LabVIEW Real Time Execution Trace Toolkit.  With these distinctive names, I'm much less likely to install "the wrong thing".
    I consider this a "bug", as NI clearly (and logically) intended for the different Toolkits to be downloaded into their own folders.  I mentioned it here in case others faced a similar confusion of "Where did my download folder go?".  Note that if you only download Real Time or only download RTETT, the "reuse" of the folder name won't matter to you.
    BS

  • Labview 2013 missing smtp VIs from Labview 2011

    We are upgrading to LabView 2013 and any VI that we open that uses SMTP is broken. It seems that NI updated the SMTP functionality but do we have to rewrite every VI that was using SMTP to mail emails from our applications? Are the old 2011 VIs avalable in 2013? Two that we use a lot are "SMTP Send Message.vi" and "SMTP Send File.vi". Where can we find these and any others for LabView 2013?

    0utlaw wrote:
    It appears that they've been replaced with the SMTP Email VIs available in Data Communication>>Protocols>>SMTP Email - there's .......  The old functions are still present at <root>\National Instruments\LabVIEW 2013\vi.lib\Utility\SMTP, but don't appear in the palettes.   
    That's actually where I went to look for my SMTP e-mails in LV 2012.  The VI hierarchy path for these VI's is LabVIEW 2012\vi.lib\Utility\SMTP\smtpeml.llb  I thought those were the VI's the original poster was looking for and not finding.
    0utlaw wrote:
    - there's even a nifty-looking Send Email express VI I wasn't aware of.   
    I haven't seen that in 2012.  Maybe that is a new addition to LV2013.

  • Windows explorer doesn't open LLB files.

    was running LV6, 6.1, now 7.0 on win98 machine.
    recently ran microsoft regclean and now I have no more support for
    viewing inside .LLB files through windows explorer. Attempting to
    re-enable this through LabVIEW/tools/options does not help.
    Any hints?
    thanks
    paul

    It appears that running regclean has busted this function by
    removing 7 entries from the system registry.
    Running ADD/REMOVE PROGRAMS/National Instruments/LabVIEW/repair,
    repaired the problem, and returned Windows Explorer support for LLB
    files, unfortunately it also removes the LabVIEW registration name and
    Ser#, but this can be easily found (and repaired) in ...
    HKEY_LOCAL_MACHINE
    SOFTWARE
    NATIONAL INSTRUMENTS
    LABVIEW
    7.0
    in the system registry and values typed in for Registered Owner & Serial
    Number fixes the 'unregistered' on the splash screen.
    back to the LLB Explorer support problem,
    What I actually did was to,
    1) run regclean to make sure there wasn't any crap in the registry.
    2) fix the LLB Explorer support
    problem by 'repairing' LabVIEW from the
    ADD/REMOVE PROGRAMS system function.
    3) run regclean
    4) rename the 'UNDOwhatever.REG' file (in regclean directory) to 'Fix
    LabVIEW LLB Support.reg'
    5) Finally, double click 'Fix LabVIEW LLB Support.reg' to put the data
    back into the system registry.
    In this way, if I ever run regclean again and it removes the LLB
    file support in Windows Explorer, all I have to do is run 'Fix LabVIEW
    LLB Support.reg' instead of repairing (re-installing) LabVIEW.
    I did this in on a Windows 98 system with LabVIEW 7.0. Your milage may
    vary with other platforms or applications.
    Paul wrote:
    > was running LV6, 6.1, now 7.0 on win98 machine.
    > recently ran microsoft regclean and now I have no more support for
    > viewing inside .LLB files through windows explorer. Attempting to
    > re-enable this through LabVIEW/tools/options does not help.
    > Any hints?
    > thanks
    > paul
    >

Maybe you are looking for

  • How to distinguish built-in SQL functions of PL/SQL?

    I m having a hard time to figure out which functions are used ONLY in SQL statements and which are used in regular expr(ie, variable assignment,). Can anyone show me a list of each or perhaps a URL to look for? I have searched through either the deve

  • Where can I get a sample pdf to test digital signature?

    I am trying to test my digital signatures in Adobe Reader X on Windows. However, I can't find a PDF file that has the correct "rights" to allow me to sign it. Is there somewhere I can get a sample PDF that will allow me to try my digital signature?

  • Call RFC_READ_TABLE via VBA.

    I try to get data from table LFBK (bank data for vendor). Here is my VBA code to get data, it's not works.  Anyone can suggest me what's wrong?  Thank you very much. Anek Public Sub RFC_Read_Table()     Dim Functions As Object     Dim RfcCallTransact

  • HDMI No Signal !

    Hi guys ,  my Computer  Hp G62 253tu is not conecting to my TV , the problem in not on the  HDMI Cable ... , On the Tv says no Signal ... How can i make it work ??  IM using windows 7 King regards

  • Using external scsi for internal drive.

    Hi people. I have a beige g3 desktop and recently bought a sound card (pro tools project pci) that has a scsi port for external drives. The card wont work without a drive atached, and I was wondering if I could use a 50 pin centronics to 50 pin inter