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

Similar Messages

Labview 2013 slow after building application

I have Labview 2013 with the DSC module installed.
I am running on Windows -64bit with 4 GB RAM
After I build my application, Labview slows to a crawl. There are no errors when I create my application and my application runs fine
All other programs run fine.
The windows task manager shows CPU use ranging from 2 to 20%
I have to shut down the computer and restart it. Then Labview is again running fine. Until I build my application again.
My application was originally developed in Labview 2012
I have not yet tried to create a new application to see if it is specific to my application or my Labview setup. I will try that next but I wanted to see if anyone else had this issue.
Thanks

Is this Windows 8, 7, Vista, etc?
Are you running 32-bit LabVIEW or 64-bit?
I would definitely recommend seeing if this problem happens when you try to build any application, or just your specific application?
Assuming the problem only occurs with your specific application, I would recommend that you try to build it on a different machine (assuming you have access to one) and see if LabVIEW behaves the same way on that other machine.
When you originally built your application in LabVIEW 2012, did you encounter this problem?
You could also try repairing both LabVIEW and the DSC Module to see if that makes a difference.
Regards,
Ryan K.

Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop).

Hi all. Since upgrading to LabVIEW 2013, every VI compiles every time I open it (including quick-drop). This really slows things down! Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini. Has anyone seen similar, and/or any hints towards a solution?

Jeff-P wrote:
As a side note, LabVIEW.ini is a file that gets generated by LabVIEW when it is launched if the file does not exist. So if you are missing the 32-bit ini file, launch 32-bit LabVIEW and that file should be created.
I thought that the message: "Perhaps related, my system tells me I don't have permission/access to modify my LabVIEW ini" might indicate that the labview.ini file cannot even be created... strange...
LabVIEW Champion . Do more with less code and in less time .

VI with Several XControls on nested tabs takes minutes to load in LabVIEW 2013

Hello all,
I have a VI in LabVIEW 8.2 that includes more than 400 Xcontrols in nested tabs, which opens in seconds (very fast). The code was upgraded to LabVIEW 2013 and now the VI takes minutes to open and in the meantime LabVIEW is unusable with the CPU at 100%.
I am wondering if anybody has experienced this behavior with Xcontrols.
Thanks.

Please note that I am working with jarcTek on this project where we inherite that UI with so many XControls instances.
It is not like there are a lot of different XControls (there are a total of about 10 different type of XControls), but there are a lot of instances of these XControls (several 100) in 3 levels of nested tabs.
Yes, we both had the time to re-recompile the source code between the two posts that jarcTek made. The various XControls are stored in 4 different llbs. Most of the XControls that have a lot of instances are actually pretty simple (very little code there). Finally, yes the VI property (or the XControl library property general settings) indicate that the code is in LabVIEW 2013 [see image below].
You are correct, the delay occurs after the VI is loaded from disk. The loading time is fine (we see the loading progress/dialog since there are a few 100s vis to load with that main UI), but after that everything hangs for several minutes (cpu peg at 100%). We run the Desktop execution toolkit, and we can see a lot of XControl events (1000s) that are fired during this time.
FYI: Unloading (closing) the VI is also very slow.
To put this in perspective, In LabVIEW 8.2 the same code is ready to run immediately after the UI opens.
Thanks
PJM

Report Generation Toolkit labview 2013 64bits?

Muy buenas tardes.
Estoy buscando el Report Generation Toolkit para labview 2013 64bits, lo he buscado pero no logro encontrarlo y con este mismo pero de 32 bits me marca error al instalarlo.

Hola Antonio,
Intenta con esta liga : http://www.ni.com/gate/gb/GB_EVALTLKTREPGEN/US
Espero que por aqui lo puedas descargar,
saludos
Erwin Franz R.

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.

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

How can I build a LabView application that uses the 2012 runtime, on a development system with LabView 2013 or 2014 installed?

I need to build a LabView application .exe to run with the 2012 Runtime, for legacy support. I currently have LabView 2013 installed on my development system, and have 2014 available. How can I build an application that uses the 2012 runtime on this development system? Do I have to downgrade to 2012? Thank you.

We have existing customers that have installed our application that was originally built with 2012 (provided by a contractor that is no longer available). Due to IT regulations, it is far easier to update these customers by simply replacing the .exe file, than creating an install that their IT department must run.
If I have to downgrade to LabView 2012, where can I get the installation for this?

LabVIEW 2013: An error occured trying to load the assembly

Hey all,
I'm trying to load a .NET 4.5 dll into LabVIEW 2013.
When I place any of the .NET VIs and try to select the one I'm after it says "An error occured trying to load the assembly" and won't let me load it.
I also tried importing the dll, but that gave errors too.
It's defintely a .NET 4.5 dll as the .NET reflector gives me
[assembly: ComVisible(false)] [assembly: TargetFramework(".NETFramework,Version=v4.5", FrameworkDisplayName=".NET Framework 4.5")] [assembly: SecurityRules(SecurityRuleSet.Level1)] [assembly: SecurityPermission(SecurityAction.RequestMinimum, SkipVerification=true)]
To try and get around the import issue, I added the following to my LabVIEW.exe.config file
<?xml version ="1.0"?>
<configuration>
<runtime>
<loadFromRemoteSources enabled="true" />
</runtime>
</configuration>
but it made no difference.
Any suggestions? All the things I've read so far are for 2010.
Solved!
Go to Solution.

Hornless.Rhino wrote:
Wart wrote:
I had the same issue a while back. Unfortunately mine magically resolved itself, but I made a post with what I'd been reading and got a reply with another suggested link. It sounds like you've gone down the same road, but I figure every little bit helps:
http://forums.ni.com/t5/LabVIEW/Error-Loading-NET-Assembly-in-2013/m-p/2521098
Thanks.
Hopefully mine will resolve itself too. LV2013 is meant to support the newer stuff without me having to mess about.
We shall see...
So far no dice.
It's really bizarre. It works with sample c# code in visual studio (see link below), but for some reason LabVIEW doesn't like the dll (tried both LV 2012 and 2013).
Sample code (not mine) is available at http://elbruno.com/2013/12/01/kinectone-hello-world-with-kinectsdk-v2-body-count/

Conversion of VIs from LabView 2013 to 2011

Hi,
I would be grateful for conversion of zipped VIs from LabView 2013 to 2011.
Thank You,
Michal
Solved!
Go to Solution.
Attachments:
main VIs.zip ‏38 KB

Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Attachments:
main VIs 2011.zip ‏27 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/B0D5630C0A50D5C6862578E800459248
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/B0D5630C0A50D5C6862578E800459248
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 .

Labview 2013 executable works only on develoment machine?

Hi all
I created an executable so as to distribute my test software but it only runs on the development machine. I have successfully distributed my executables before with labview 2012 on target machines by simply creating the .exe in project explorer and then installing the nessary labview drivers and run time engine without problems. Now I created a new test programme with Labview 2013 and I can't get my new .exe test software application to run on the target machine. Has anyone seen this type of problem before? Any assistance will be appreciated.
Thanks
Solved!
Go to Solution.

In addition to the run-time engine you are likely missing some other installers. Lets say you used RS-232 code in your EXE well now you need to install VISA run-time on the new machine. Did you use DAQ? Now you need DAQmx. Did you use NI-Scope? NI-DMM? NI-Power? NI-Switch? You'll need to install those as well.
In 2013 the process of making an installer can detect what installers you need. In previous versions you just have to know which you used and select them in the Additional Installers section.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Using "panelresize.vi" in Labview 2013, in code originally written for Labview 2006.

Hello,
I'm updating code written in Labview 2006 to make it compatible with Labview 2013. My code calls a custom TDMS file viewer vi. This viewer calls a function called "panelresize.vi". This is a NI vi that has been updated since the 2006 version. The new version includes a "help - boolean refnum" in the input cluster, so that the vi now expects a cluster of 9 elements instead of the 8 that I am sending it. I am not sure what this "help refnum" is, how to use it, or how to add this to my input cluster in the calling function so that the error goes away.
Any suggestions?
Thanks!
Attachments:
Untitled.png ‏392 KB

Hi,
it is a help button. You can add a help button to your customized File Viewer. If you don't want this button, you can make it invisible.
What requirements drive you to make your own customized File Viewer?
FYI. In LabVIEW 2013, we made changes to improve the performance of the file viewer. For the compatibility, we kept the panelresize.vi and added a specific panelresize_tdms.vi for this improvement. panelresize_tdms.vi requires more than 9 elements.

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

Slow LabView 2013

Similar Messages

Maybe you are looking for