Open LabView VI to a LLB

Hello

Currently, I'm trying to connect my camera Andor Shamrock of newton and access the VI so that I can use in my LabVIEW program.
The software readme directed me to the LLB directory, in which I found all VI applicable to the camera. However, when I try to open, a dialog box if poster direct me to find the files in the "shared library". The cancellation of this dialoge box allows the opening, however, VI block diagram see the? as well as whites where the icons of screws of the camera should be.

Is there a way for me to access the screws in the LLB Manager list or I have to fix from a separate source?

Thank you

Justin

Fortunately, after the conversation with the company, its seems to have been a fault of their own. After redownloading software, the VI became available. Thanks to everyone for their assistance; hope this is useful to others.

Tags: NI Software

Similar Questions

  • Cannot open labview 11 after installation

    I received the last mydaq at school. I have loaded all of the software and was able to use the mydaq, but does not open labview. I have an acer aspire v3-551-8664. There the A8 of AMD Quad core processor. I saw in another place that the AMD FX "bulldozer" has a problem with labview. Any ideas?

    So, I finally realized what I was missing that was the patch needed to go in two different folders. He has got to work! Thanks for your help and sorry for the confusion.

  • Just openning LabVIEW and causing 99% CPU usuage

    Hi people,

    I just opened LabVIEW 8.2.1 and later, he finishes its initialization, while on the start-up screen LabVIEW uses 99% of CPU.

    I tried to restart and repair the installation, but nothing helped. Someone has experienced this problem?

    Thanks in advance!

    One thing to try: start in safe mode. I think that LabVIEW should always run in safe mode, although no service will operate. I would be very interested to know if the CPU usage is still attached.

  • 9.30 NIDAQ drivers not install LabVIEW 2011 - example. Microsoft .com's in LabVIEW 2010 under vi.llb

    I just upgraded to LabVIEW 2011 without uninstalling LabVIEW 2010.  I downloaded the last set of drivers DAQmx 9.30.  I find that these drivers are installed in a DAQmx folder under the vi.llb of theLabVIEW 2010 and NOT in the vi.llb of LabVIEW 2011.  The DAQmx features do not appear on the menus and the existing instances are reported as 'cannot be compiled. How can I get the DAQmx functions to properly install LabVIEW 2011?

    You must DAQmx 9.4.

    9.4 DAQmx

  • Open LabVIEW VI reference executable.

    Hello

    I did do that for a while and there does not as expected.  I'm trying to 'Open VI Reference' of executable A.exe to B.exe.  I try to get a control value of B.exe in A.exe.  Can anyone send me an example?

    Right now I'm at this point: I'm running as an executable of LabVIEW A.exe.  I'm trying to 'Open VI référence' to A.exe of LabVIEW Development without success.  Don't know what I'm doing wrong.

    Feel free to ask for more information if you need.

    LabVIEW 2012, Windows 8.1.

    Thank you

    Michel


  • Open Server LLB VI

    Is there a way to open a LAW degree, in LLB Manager, programmatically using VI Server?

    Opening a VI library, project, etc. all can be done relatively easily by using VI server but I do not see a method for opening a LAW degree.  Research into the LLB Manager in the \project\llbedit.llb\LLBMgr to Interface.vi I see that I can provide the path to a Bachelor's degree in LAW on control of path (not on the side of the connector) and run the VI and it will work, but using this method has a problem when you try to open a second Bachelor's degree in LAW , because this VI is not reentrant, and it will not open a second window.

    A method that works is in command line with the full path to the LabVIEW.exe and the path being the first argument LLB.  The problem with this method, is that still does not work with several versions of open LabVIEW.  It is often open in the wrong version.  But using VI Server I can specify the port to open an instance of the application on and make sure that the version I want open, is the version

    Well, this can greatly simplify things, through Server VI methods I found an open > LabVIEW Document which seems to do exactly what I want, all supported types of LabVIEW files.

  • LabVIEW 8.6.1 project causes the slow open VI reference

    I have a strange problem with 'Open VI Reference.vi'.

    Case 1.

    • Open a project in LabVIEW that contains "Main.vi".
    • Open 'Main.vi '.
    • Run "Main.vi".
    • Execution of "Open VI Reference.vi" take about 2, 000ms

    Case 2.

    • Open "Main.vi" - open LabVIEW No. project
    • Run "Main.vi".
    • Execution of "Open VI Reference.vi" take about 100ms

    I converted the project to 8.5 and the problem goes away. I have not all machines with 8.6.0 to test if there is a problem with 8.6.1 only.

    Has anyone else seen anything like this?


  • Problem in opening and running LabVIEW in separate user account

    Hello

    I would like to create a 2nd user account on my computer in the laboratory that has LabVIEW 2011 installed on it. However, when I try to open LabVIEW in the 2nd user account there is an error code 1 and another message complaining about some dialogue 3 button VI.

    I found that I can still continue by clicking OK, except that now I can't start my VI, where I copied over my 1 user account. I get attached errors, including one that seems to be complaining of Simple error handler in my VI which runs at the end of my program error messages. Does anyone have an idea on how to fix the errors?

    Help, please!

    Thank you!!!

    Hi Vrinkle,

    LabVIEW is usually installed in "C:\Program files (x 86) \National Instruments\LabVIEW xxx ', where"(x 86) "is the version of LabVIEW application for a 32-bit version of LabVIEW on a Windows 64-bit and"xxx"brand (year)." In this folder you will find subfolders "vi.lib", "instr.lib" and "user.lib" - all the rights granted to your new user account need to access these files (like all the others those of LabVIEW file)!

    BTW. display your serial number on a public forum is not the best idea...

  • LabVIEW 2012 do not open

    My LabVIEW 2012 opens with a message that says operation side by side is not configured correctly.  I tried to open LabVIEW 2011 and he opened and I don't see the message, but it was very slow, as it opened.

    Before seeing the error, I did a repair on my Package redistributable Microsoft Visual C++ 2010 (x 86) and on my 4.5 .NET.  What is the best way to solve this problem?

    Thank you!

    I did a lot of installation and uninstall of Microsoft Visual C++ distributable, and which does not solve the problem.  I also did a repair for the 2012 of LabVIEW.  Later, I look at the event log, and who told me the LabVIEW.exe.config file.  I made the following change below, and that fixed the problem.  I don't know why but.

    LabVIEW.exe.config that caused the error






    LabVIEW.exe.config as the error correction





  • VI blocks labVIEW on opening

    Whenever I open my first level vi, labview crashes with the error message "LabVIEW 10.0 development system has stopped working" and he invites me to close labVIEW.

    My first level vi contains a machine structure and the event State and several under vi. It was working fine until a crash suddenly after I was wiring a local variable... and now it will not open at all.

    Is there anyway to restore a vi like this or will I have to start from scratch?

    Vascular cerebral accidents says:

    I'm still new to labVIEW (where the lack of backup vi).

    Being new to LabVIEW and have a good backup strategy are mutually exclusive.  Consider using a source code control system.

    How can I open labVIEW 2011 vi in labVIEW 10.0 (which is the version I use), I thought about the opening of vi it would convert it automatically... ?

    You can not. Screw saved in a newer version of LabVIEW can not be opened in a previous version. That's why we have to Downconvert requests Thread. A new version of LabVIEW open screw written in an earlier version (up to a certain point) and convert them. If the VI is too old, then we have the Upconvert requests Thread.

    In fact, I downloaded the wrong version. Joined the LV 10.0 version. Sorry about that.

  • Where LabVIEW 2012 keeps the files recently opened?

    When you open LabVIEW 2012, the right side of the home screen displays a list of existing open.  In my case, 'bad' screws and projects (some no longer exist) appear.  I would like to change this list to clear the junk.  However, it is more in the file LabVIEW.ini, there doesn't seem to be (although I may have missed it) in my LabVIEW data folder.

    Who knows where it is?

    Found!  This is the file LabVIEW.ini - either I was watching 'bad' that precedes it, or someone put something weird in my tea when I wasn't looking.  Cleaning now...

  • NOR-845 x driver Labview 2011 SP1

    Hi all

    I faced problem,

    I have a LabView program that is used to communicate with devices SPI-NOR-8451. Program worked perfectly, on PC with LabView 2010. After that, I moved the program to new PC where f1 LabView 2011 SP1 has been installed. And now, I am not able even open - LabView program stuck on the white block diagram (not responding).

    Program is complex and includes 10 ~ SubVis, which is packaged in the .llb file. I tried different things - to decompress from .llb, or run subVis themselves - for all the subVis, which include a part any communication NOR-8451, I've got stuck LabView. In addition, after the removal of NOR-845 x pilot, I can't ignore everything and load the program successfully, with '? ' instead of screws of NOR-845 x pallete.

    In addition, when I'am tring from white VI and set NEITHER-845 x ref Device link (see attachment for details Link_on_ref_.jpg) on the block diagram, I'm LabView stuck - see the attached Stuck_.jpg.

    I use NEITHER-845 x driver 2.0, I tried to reinstall several times.

    So, it's my suspicious that NEITHER-845 x driver 2.0 does not work for LabView f1 2011 SP1 - is it possible? Or maybe I'm doing something wrong?

    Hi RangerOne,

    Thanks for the trace, as LabVIEW is suspended, it is what I expected but hoped a different error code. If you could go to MAX and reset Configuration data, and then create a MAX Technical report and attach it.

    If you open the test Panel, you run a query, it works or hang? Try to run a trace when you try to query.

    I see the same error with the camera on my machine under interrupt in Pipe status is not abnormal.

    I also noticed that your computer input for findlist, retcount and SrcName parameters have not the & on the non-working paper. I will continue to examine the reason why the & is not there and if it has an effect on the shot.

    DylanC

  • How to access COM in Labview objects?

    How can we accessCOM objects in labview? Also if it I sany .dll file, then how can we read this file in Labview?

    Take a look at the Automation open on the block diagram function to access objects COM/tool and then use the nodes property and invoke nodes to access the properties and methods. See the slide show VI in labview\examples\comm\actxpp.llb for examples of using the function of opening automation.

    You can read a DLL using the call library function node.

  • DAQ Assistant is not in LabView

    Hi all

    I use NEITHER cDAQ-9174 and NI 9203.  I have already installed the driver for the NI 9174 cDAQ, which is NEITHER-DAQmx 9.8.0.  I can see the device when I opened NI MAX. However, when I open LabView 2015, I can't find DAQ Assistant in the function Palette. I noticed on the chassis, 'ACTIVE' light is not on while two other "POWER" and "READY" light is on.  I look in the forums OR but I can not find the solution.

    Any suggestion, please help!

    Thank you!

    DAQmx 9.8 is not compatible with LabVIEW 2015.  You must use at least DAQmx 15.0.  See here for more details: NOR-DAQmx and LabVIEW compatibility

  • Ethernet I / P Communication between Fanuc LR Mate 200iC and LabVIEW

    How can I read the outputs and write entries of a device, Ethernet/IP, using the NI Ethernet/IP drivers?

    I recently get the NI Ethernet/IP driver OR to communicate with a robot of 200iC Fanuc LR Mate using this communication protocol. In fact, I set up the robot as a parameter to map digital 1 to 64 and output digital from 1 to 64 and through the Ethernet/IP configuration.

    What I do is for example, a specific moment in my logic to the status of an output of the Fanuc Robot to take measures, or give some input to the Fanuc Robot so do some operations. Now, as I noted above, I get this drivers recently and apparently they are new or regular technical support do not support for this product. Basically there is no apartment of the LabVIEW help on this driver documentation, and this help doesn't help too much.

    So, if someone can help me to make this work I really appreciate it a lot. I'm in the middle of a project we showld integrate via Ethernet/IP. Here is a screenshot of the the inputs and outputs in the configuration of Fanuc Robot are on Slot 1. Attached is a table with a summary of the Fanuc Robot of the configuration settings that should be used to set up the scanner (in this case, LabVIEW):

    I'm using LabVIEW 2011 with Ethernet/IP v1.2 drivers on a Windows 7 Professional

    Once again, any help on this will be really appreciated. Thank you.

    Hi Ferdinand,.

    Please refer to the help as documentation below:

    1. open LabVIEW, go to the Help Menu-> NOR-Industrial Communications for Ethernet/IP. This is documentation of EIP support for all applications.

    2. in him getting started window of LabVIEW, please go to find examples. And check the directory:

    Input and output hardware-> NOR-Industrial Communications-> EtherNet/IP

    In this directory, there are several examples of use of the PPC.

    And for your case, read the example in ".vi AccessAssablyInstanceData (Explicit)", which should be very similar.

    For any question below, please do not hesitate to contact me.

    Thank you.

    Chris

Maybe you are looking for