LabVIEW 2012 runs processor up

When LabVIEW 2012 is open but idle it runs the processor up over 25%.  This happens if getting started screen is up, just a project window or if a VI or exe are in event structure wait mode.

Is your IT trying to run a scan on the LabVIEW application because they don't know what LabVIEW is?  I have that problem sometimes.  I usually don't see my CPU going at 25% with just the welcome screen.  But I often have to wait 30 seconds when I save my VIs due to our IT running scans.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Similar Messages

  • Is Labview 2012 run-time on TPC-2206?

    When I go to Uninstall programs on my TPC-2206 I see Labview Run-Time 2009, 2010 and 2011. Labview 2012 Run-Time does not show up in the list. When I download and install it, I still only see the above plus a generic National Instruments program. The new TPC-2206 touch panels we have show a generic National Instruments program in the program list, but I don't know how to find out if that is Labview 2012 Run-Time. I can't find anywhere on the NI website that lists what Run-Time software is already loaded on the Touch Panels.

    I did try running a Labview 2012 executable after I had put up the post. It did not work, so I knew that Labview 2012 Run-Time was not on it. I put Labview 2012 Run-Time on it, but afterwards when I looked in the Remove/Change programs list in the Control Panel, Labview 2012 Run-Time was not in the list of installed programs. There was a generic National Instruments program, but there was nothing identifying what NI program it was. This was the real problem, because all of the earlier versions of Labview Run-Time were clearly identified in the installed programs list and Labview 2012 Run-Time was not. There is no way to know if Labview 2012 Run-Time is installed except to try to run a Labview 2012 executable.

  • Labview 2012 32bit running in 64 bit windows

    Hello Sir/MAdam,
    I have recently installed LabView 2012 on 64-bit windows 7. It seems LabView is 32-bit. When I run a simple code for reading digital inputs, it does not response while when I run this code on LabView 2010 running on a 32-bit PC it works!
     Could this problem be because of 32-bit LabView 2012 running on my 64-bit windows. I also installed drivers which support 64-bit. 
    I attached the simple code I am using for reading digital inputs.
    I appreciate in advance your kind help.
    Thanks,
    soroush.
    Attachments:
    read digital inputs.vi ‏44 KB

    Soroush,
    At this point it's still a little hard to say what may be causing this problem. Have you tried running any other I/O examples included with LabVIEW? Are these also unresponsive on the 64-bit machine running LabVIEW 2012? 
    Are you able to see any values using the Test Panels for the simulated cards in the Measurement & Automation Explorer (MAX)?
    I don't think this is related to the 32- or 64-bit architecture of the computer, but hopefully we can help you figure something out.
    Best regards,
    Andy C.
    Applications Engineering
    National Instruments 

  • Missing vi.lib files in Run-Time LabVIEW 2012

    Hi
    I've got a problem executing VI's under RT in LabVIEW 2012.
    Our system consist of multiple independent modules which are opened and run from a Manager VI. VI paths to the modules are read from an .ini file by the Manager VI.
    We have build a single executable (RT Launcher) that takes the path of the Manager VI as argument (Attachment : RT Launcher.png).
    The RT Launcher is placed in the ..\National Instruments\LabVIEW 2012 folder as the LabVIEW.exe.
    The RT Launcher is called from the CLI.
    "C:\Program Files\National Instruments\LabVIEW 2012\RT Launcher.exe" "C:\Workspace\Labview\Manager.vi"
    This will run the Manager.vi in the RunTime Environment and the Manager.vi will open the .ini file and execute the Module VI's one by one.
    By calling the RT Launcher.exe from the same folder as the LabVIEW.exe, the search paths should be the same.
    The system worked fine in LabVIEW 2010.
    The Manager VI is opened with broken arrow and the errors indicate that vi.lib sub VIs are missing (attachment : Manager VI errors.png)
    I know there are issues regarding object cache and separated compiled code from LV2010 -> LV2011 -> LV2012, but simply can't figure out how to come around this problem.
    Can anyone explain the difference and how to solve the problem ?
    Thanks
    Regards Kahr
    Certified LabVIEW Architect
    CIM A/S
    Solved!
    Go to Solution.
    Attachments:
    RT Launcher.png ‏68 KB
    Manager VI errors.png ‏35 KB

    Hi Kahr.
    It sounds like you are making some dynamic calls to VI's, eg. by using 'Open VI Reference'. My answer is based on that assumption. 
    You are absolutely right. In LabVIEW2010 we introduced a function called 'Separating Compiled Code from VI'. At that time none of the VIs from VI.lib had that option enabled. In LabVIEW2011, many VI's in VI.lib have, by default, a separation of compiled code and VI. This option cannot be changed (greyed out) for these VI's as well. This feature was introduced in order to simplify source code control.
    Separating Compiled Code from VIs and Other File Types
    The drawback is, that it is no longer possible to call VI's dynamically from an application (executable), when this option in enabled, since the compiled code no longer exists. The method of calling a VI dynamically from an application has been (and still is) used to make some kind of a plug-and-play architecture, meaning we have one EXE-file that only gets distributed once and a set of subVI's that gets redistributed according to new versions (new features added to the subVI), meaning we can make changes in the subVI without having to redistribute the EXE-file.
    With the release of LabVIEW2011 and LabVIEW2012 we can no longer distribute VI's that uses functions from vi.lib, this also include DAQmx calls even though the DAQmx driver is installed.
    The simple explaining is, that it has never been intended that VI's got distributed. Eg, when Microsoft is making a new software update for Windows7, they don't send out the source code to all the users.
    The solution is therefore to wrap up the source code into 'something' that includes all the compiled files. In LabVIEW we do that in a couple of different ways.
    1) Include the VI's in the EXE-file.
    When building the application, we have the option to include files, that normally is not included in builds. If we call a SubVI dynamically this will not automatically be included! However, the drawback of this method is, that if you need to change  something in one of your SubVI's, you would need to build and distribute the entire application. Thereby, we are not making use of the plug-and-play architecture that we originally wanted. However, this method will fix the error.
    Error 1003 When Using VI Server in a LabVIEW Application
    2) Now, if we still want the plug-and-play architecture in LabVIEW2011+2012 (and this will properly be the same for the next many released of LabVIEW), this can still easily be achieved by making a Source Distribution. When we make a Source Distribution, we can include the VI's from VI.lib and thereby the compiled code. When using this method, two important things should be remembered:
    a) Make the files into a LLB file. This will pack all the VI's into one single file, that is easy to distribute.
    Go to Destinations ==> Destination Type ==> LLB.
    b) Make sure not to 'Exclude files from vi.lib', as this method will then simply not work.
    Go to Additional Exclusions ==> Remove checker mark in 'Exclude files from vi.lib'.
    How Can I Call a VI Dynamically from an Executable Without Including Those VIs in the Build?
    I have made a small example to demonstrate this:
    Example: Using vi.lib
    This example has two mainVIs and two EXE-applications. Build the two EXE-files, but do NOT build the source distribution yet.
    1) Main(IncludeSubInExE). This version has included the subVI in the build distribution for the EXE-file. When running this EXE everything works fine, even when calling the subVI dynamically. However, since the subVI is build into the exe, we would have to redistribute the exe for every new version of the subVI. This breaks the hole idea.
    2) Main. The subVI is no longer included in the build. When running and trying to call the subVI, you will get this error (on both your developer and run-time machine):
    Now, build the Source Distribution and run this EXE again. The exe is running perfectly with no errors.
    I hope this answers your question.
    Best Regards
    Alex E. Petersen
    Certified LabVIEW Developer (CLD)
    Application Engineer
    Image House PantoInspect
    Attachments:
    Using vi.lib.zip ‏83 KB

  • Exe created with labview 2012 won't run using LVRTE2013

    I created an exe using Labview 2012.  I had the user install the latest rte (lvrte2013).  The exe would not run and told the user it needed 2012 rte.  Do users have to have the same rte for each exe?
    Solved!
    Go to Solution.

    Yes.  But the various RTEs can coexist on the same PC.

  • Issues with windows 7 after Labview 2012 installation

    Hi
    I am having some issues after installing Labview 2012 on machines running Windows 7. Firstly, after installing a program on a user's machine, the machine sometimes takes 20 minutes to boot up before the user can log on. The 'Please Wait' message appears during this time. This is also the case on the development machine.
    Secondly, on the development machine, I am having an issue when trying to run compiled programs created in Labview. When installing, everything works fine but when I go to open the program, it appears on the task bar for a brief period before closing. It does not appear in the task manager either. I have tried this on 2 other machines with windows 7 and Labview installed and still get the same issue.
    Any help on these matters would be much appreciated. Thank you

    Hi
    Firstly, looking at the issue with the slow Windows 7 boot up time, as Norbert_B suggested the Windows Event Log is a good starting point to find the root of the problem. The following link describes how to launch “Event Viewer” and some common problems:
    http://itexpertvoice.com/home/what%E2%80%99s-taking-so-long-how-to-fight-slow-startup-times-in-windo...
    Aside from that, if your computer is part of a domain, the problem may be connected with certain Windows Services that start automatically on boot up. I recommend trying the following steps:
    Open up “Control Panel” go to “System and Security” then “Administrative Tools” from here launch “Services”.
    Sort the list by name and scroll down to “Network Store Interface Service” right click and select “Properties”. Under the startup type dropdown select “Automatic (Delayed Start)”.
    Next scroll down to the “WebClient” service again under “Properties” this time select “Disabled” under the startup type.
    As for the problem with running LabVIEW executables, I have a few questions:
    Do you get any error codes when it closes automatically?
     Does this occur for multiple executables or just one in particular?
     Does the code run without a problem within LabVIEW?
     Have you tried to update LabVIEW?
    What hardware are you running?
    Without this information I can only think it may be caused by the Windows Data Execution Prevention (DEP) security feature. So you can try the following steps:
    Right click on “Computer” and select “Properties”.
    Click on “Advanced System Settings” and select the “Advanced tab, then under the performance section click “Settings”.
    Click the “Data Execution Prevention” tab.
    Make sure it is activated for essential Windows programs and services only, or you have an exception for your EXE.
    You may also find the following link helpful on debugging applications:
    http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/debug_apps_dlls/
    Let me know if these solve the problems.
    Andrew.N
    Applications Engineer
    National Instruments

  • LabView 2012 Security System Main vi's have error 200559

    The vi's give errors of 200559 in my LabView 2012 and NI application engineer "John Staskal" told me as "Another good step 
    is to recreate the VI in your current version of LabVIEW so that you know the error is not caused by upgrading the VI to a newer version of LabVIEW." I did all that, but not resolved.
    Their application engineer John Staskal also told me as "In addition to working to resolve the error you may want to pursue is posting on our upgrade forum and asking the community to convert the VI to a current 
    version of LabVIEW.  http://forums.ni.com/t5/Version-Conversion/bd-p/VersionConversion".
     I did all trouble shooting steps such as highlight execution, probes, etc as what their application engineer told me and still having error of 200559 in LabView 2012.
    I  appreciate help from any one.
    Ali Tariq Bhatti
    Ali Tariq Bhatti
    Advice: Some people talk on different issues and abusive against your post because they do not want to help and arguing with you on some other topic. You all will observe and I also observed, so also do not want to mention their name and best way is complaint them to the moderator. If anyone still wants to talk on different issues against the post, other way is to do private message.
    ~~~Be nice, have faith in ALLAH(God)~~~
    Attachments:
    NI ELVIS II Security System VIs (2).zip ‏313 KB
    Error 200559.docx ‏500 KB

    RavensFan,
    I) Yes, I open up the front panel of the Express VI's and probe into them.
    2) I use the express vi's, but if you see my attached vi's file. You will see Security System Main vi is the main vi where the program is running and where I am getting the error of 200559.
    3) I also attached the word document file, so I am getting error of 200559 in probes 3, 4, and 5 using Export Key Press and Voltage vi's in this post.
    4)Do you know, how to convert these my attached vi's to 2011, 2010, 2009, or LabVIEW8.5 version. May be, it fix the problem, or if you know some one to get help from or get chance to use ELVIS II board, so let me know .Your help or any one's help is appreciated.
    Advice: Some people talk on different issues and abusive against your post because they do not want to help and arguing with you on some other topic. You all will observe and I also observed, so also do not want to mention their name and best way is complaint them to the moderator. If anyone still wants to talk on different issues against the post, other way is to do private message.
    ~~~Be nice, have faith in ALLAH(God)~~~
    Attachments:
    did probes for Export Press and Key vi's file.docx ‏340 KB

  • Only have LabVIEW 2012. Why am I asked to download LabVIEW 2011 SP1 f2 RTE Patch?

    Hello,
    I recently got a new machine (clean install of Windows 8), and installed LabVIEW 2012, with no other previous versions. However, when I ran the NI Update Service, it listed "LabVIEW 2011 SP1 f2 R(32-bit) Run-Time Engine Patch" as a critical update.
    I'm confused; did I accidentally install LV 2011 too?
    Thanks
    Solved!
    Go to Solution.

    Also, some addons use older RunTime Engines.  It is not suprising that you need the 2011 RTE patch.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • What files do I send to be upgraded from LabVIEW 5.1.1 to LabVIEW 2012?

    OK.  Just to be clear.  I am a complete newb to ANYTHING LabVIEW or LabWindows related.  I am a programmer, but I have never used any version ever.  That said, I am responsible for the upgrade process of getting our old LabVIEW 5.1.1 system up to date.  The old system (still running and doing it's job everyday), is an old Windows NT v4.0 SP6 system running LabVIEW 5.1.1.  You can just imagine how ancient this is by today's standard.
    Have I set the stage properly?  I hope so.  Newb, Ancient LabVIEW version 5.1.1, Windows NT 4.0, upgrading from 5.1.1 to 2012.
    Now here is what I "think" I know about what is required.  Because LabVIEW 2012 will not directly read in, process and /or compile LabVIEW 5.1.1 files, I must first open and save the files using an intermediate version of LabVIEW (specifically 8.2.1) to bring the files up to a version that 2012 can handle.  I have noticed in reading the Version Conversion forum, that I can attach a zip file of my LabVIEW files and one of the resident Gurus will convert it for me and give them back - quite nice I think.
    Now, I have what I think are all of the required LabVIEW vi and llb files that make up this system we have in place, but I want to be sure before I just post a bunch of stuff.  
    What exactly do I need to zip up and what can I leave out? 
    Are there LabVIEW vi and llb files in a "project" that are not needed? 
    Are there any setup/configuration/project specific files I need to include? 
    Are there any limitatations to this conversion process that I need to be concerned with - such as various toolkits/suites/modules that may have been used but are no longer supported?
    Secondly, I am not really comfortable with posting my vi and llb files for the world to see (and possibly use) as I am not the owner of said modules, just the user/future developer who will be responsible for insuring they stay up to date.  Is there any way I can send my files to a specific NI guru via email instead of just posting them?
    Solved!
    Go to Solution.

    So if I understand you correctly,  all I really need to do is to get LabVIEW 8.2.1, and update my .vi, .lib, and any .ctl files to that version.
    Is it a simple matter of just opening the files and hitting something like SAVE AS, or just SAVE and it will do this?  Once done, LabVIEW 2012 will then allow me to open them and do what I need to do?  Do I have to save them into LabVIEW 2012 first, or is that automatic when I try to recompile them?
    When I get a copy of LabVIEW 8.2.1 (eval version), do I have to get all of the pieces (modules, toolkits, etc.) in order to update the 5.1.1 files?  Based on what is installed on that NT v4.0 system, we have the following items installed:
    NI VISA
    NI ComponentWorks 3D Graph
    NI DataSocket
    NI LabVIEW 5.1.1 Advanced Analysis Library
    NI LabVIEW RTE 5.1.1
    NI LabVIEW v5.1.1
    NI Measurement and Auto Explorer 1.1
    NI-488 2.1.60
    NI-DAQ 6.6
    NI-PAL 1.3.110
    NI-Reports
    NI-VXI/VISA
    You mention DAQ.  Our program uses NI DAQ v6.6 now.  I have LabVIEW Developer 2012, so I just download the DAQ files for it and it will replace the NI DAQ v6.6 library files we use now? 
    Thanks for your help so far.  If we had a support contract in place, this wouldn't be an issue.  However, as I stated, I am not the owner of the files, just the currently assigned caretaker, and part of my task is to get from where we are now on this ancient hardware/software platform, to the latest and greatest.  However, I am specifically not allowed to just place the files on a public forum for all to see.  It just isn't done.  We can send them to a known location and a known entity, but not to just anyone/anywhere as a public forum is by its very nature.   
    I know there is nothing you guys can do if I cannot give you the files, but thanks for helping me to do it myself.    Getting an eval copy of 8.2.1, et. al is probably what I have to do here.

  • XYGraph Cursor legend bug instantly crashes LabView 2012

    Hi!
    I am just facing a very annoying bug.
    Please find my example VI attached, I would like to know wheather you can confirm the bug? Run the VI if you wish to see some curve (actually the bug appears even if you do not put any data on the graph, if you do, just the same) and after that try to click on the cursor legend vertical scrollbar to scroll up or down to see the cursor names.
    It instantly crashes my LabView 2012 Full version:  12.0.1f2 (32-bit). This XYGraph always crashes LabView... I cannot go on with my project, now I will just try to bypass the error, I will try to delete the cursors, and add them again...
    Anyhow, very strange and annoying behaviour...
    Anyone could repeat the same bug?
    Thanks for support!
    Solved!
    Go to Solution.
    Attachments:
    XYGraph_bug_test1.vi ‏149 KB

    hello,
    please find attached my example VI, where I would like to programmatically set the label position of a cursor. Why my code does create at every run a new cursor with the same name?
    thanks!
    Attachments:
    cursor_offset_label_via_propertynode.vi ‏12 KB

  • Installing both Vision Builder 2012 and LabView 2012 on same Computer

    am new to NI Vision Builder Automation Inspection 2012 (Which I am supposed to learn and use for part inspection) as well as LabView (Which I need not know at this time)
    When I was presented (to work with) a 1722 Camera and the computer, Labview 2012 was already installed but not Vision Builder.
    The IT folks installed the Vision builder without uninstalling LabView.
    I have my problems getting upto speed with my inspection work, but is any of it attributed to both systems being on the computer?
    Can I (Must I) uninstall LaView??
    Thanks

    LabVIEW and Vision Builder run fine on the same computer.  I have several versions of each on mine with no problems.
    Bruce
    Bruce Ammons
    Ammons Engineering

  • Labview 2012 Runtime Application Crash: Access Violation Error

    hi All,
    my rather large app that I been develping over teh last few years has recently been crashing.
    I do not know if it is since I began compiling it in LV2012 SP1 that the problem occurred or I have some programming error
    that I cannot track down.
    It use to run with uptimes over months, even with some memory leaks.
    If I monitor using Task Manager there is no decernable increase in memory usage.
    It crashes on two different systems - both running Windows XP.
    The developer version running in LabVIEW 2012 f5 ( Windows XP ) does not crash. Only the runtime version crashes.
    It also crashes either if the program sits idle for a few days - 5 or so ( memeory footprint stable ), or if it is used extensively to actively gather and control several instruements ( memory increase matches data size increase )
    It does call several external API via ActiveX to spawn off processes, however from the lvlog.txt it seems the crashing is a simple open file that uses the NI supplied String to Config.vi.
    I have double/triple check my code and I close any refernces open by the calling vi.
    I am sure how to read teh mini-dump files so if someone can look at these it would be apreciated
    thanks
    Michael
    Here are two crash logs:
    Attachments:
    fde86f7f-a024-417d-ac1c-d38b2e9a41e3.zip ‏61 KB
    4f75c413-793d-46db-b66c-889a2f2daf69.zip ‏59 KB
    00660fb7-749d-4af5-bcb1-ac5cad73a5cb.zip ‏56 KB

    Hi Michael,
    It's tough to tell what's going on, especially since it seems like you've really covered your bases!  I'm curious about the fact that you don't see the crashes in LabVIEW (LV), just in the Run-Time Engine (RTE).  Have you ever tried running it in LV for an extended period of time?
    Also, do you have any loops in your program?  Perhaps shrinking any waits that might be present and allowing your program to run faster would decrease the amount of time to see these errors from days to shorter.  
    In the future, when you get a dump file, submit it to our R&D department.  It then pops up on a website that allows me to read them.  I can also use win debug but that will take me a bit, so I'll have to get back to you on that.  
    Also, if you could take a picture of the error, that would help as well.
    Julian R.
    Applications Engineer
    National Instruments

  • Labview 2012 Runtime Ubuntu

    Hello. I am trying to distribute a compiled labview program on Ubuntu linux machines. However, I can't seem to get the Labview Run Time Enviroment to install on Ubuntu in order to run the executable. Has anyone managed to do this? I have tried using Alien to convert the .rpm into a .deb. However, whenever I do this I get a weird Alien error that I can't seem to debug:
    Error executing "rpm -qpi 'labview-2012-rte-12.0.0-1.i386.rpm'": at /usr/share/perl5/Alien/Package.pm line 489.
    I would appreciate any help.

    This configuration is not officially supported by NI, but this forum post may be helpful to you:
    http://forums.ni.com/t5/LabVIEW/LbVIEW2012-Linux-Ubuntu-12-Installation/m-p/2304470
    Applications Engineer
    National Instruments

  • Why wont Turbo Tax 2012 run on my mac?

    Why wont Turbo Tax 2012 run on my Intel Mac running OS10.6.8?
    My Mac:
       Intel Core Duo
       OS 10.6.8
       2GHz processor
    Box and online specs indicate it should work but it does not...
    Can Anyone help...

    Hi eston,
    well, the bad news for you is that the specs do indicate that it will not run on your computer.
    Why, you ask.
    If you look at the TurboTax 2012 specs for Mac, it states that for Mac OS X 10.6.8, one needs to run 64-bit.
    from Intuit site, TurboTax Deluxe 2012 computer requirements  (http://turbotax.intuit.com/personal-taxes/cd-download/deluxe.jsp):
    Processor:Intel-based Processor
    Operating System:
    Mac OS X v10.6.8 or later
    Mac OS X v10.7.5 or later
    Mac OS X v10.8.0 or later
    Note: 64-bit required for Mac OS 10.6.8
    the "64-bit required" link takes one to the Apple kb page....
    My Mac:
       Intel Core Duo
       OS 10.6.8
       2GHz processor
    your spec list above states that you have an Intel Core Duo.  The Apple kb article (http://support.apple.com/kb/HT3696)  shows a list of which processors are 64-bit and which are 32-bit.  Unfortunately for you, the Intel Core Duo is 32-bit.  This is why TurboTax 2012 will not run on this computer.
    The next processor, Intel Core 2 Duo, is 64-bit, as are the later Xeon and "i" series.
    cheers, and good luck,
    Roy

  • LabVIEW 2012 f1 Patch crashes

    I've just installed LabVIEW 2012 and unfortunately I've already run into some troubles.
    I received a "Setup has stopped working" when I installed the device drivers.  But the installation appeared to be fine.  LabVIEW started and MAX would open.  I did not try connecting to any hardware yet.
    When attempting to install the f1 patch, LabVIEW crashed again.  Subsequent retries net the same thing. 
    Has anyone else had this trouble with the patch?   
    This is on a Win7 machine with LV 8.6, and 2011 previously installed. 
    Patrick Allen
    Solved!
    Go to Solution.

    Why do you have LabVIEW open when you are trying to install a patch?  Are you running other versions of LabVIEW when performing the install?  It is highly recommended you are not running anything NI when running installers from NI.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

Maybe you are looking for