Howto fix Labview 2010 delays

My Labview 2010 causes huge delays ~30-40s when compiling and when using its restore function.
It is blocking the pc (unusable) for that time.
I tried several times now but development work with that pauses is not possible.
The System: MS XP32, Athlon64 3800+ with 2GB RAM is not recent, but clearly within the min. Requirements: Pentium 4 and 1GB
The app is first written under LV 6.4/8.0 and its using very less express vi stuff.
Howto solve the delay problems coming with LV 2010?
1. Do I need to rewrite my whole program using express Vis...
2. Can I deactivate some features to reach LV 8.0 performance....
3. Do I need faster cpu and more RAM...
4. Can I give this program back to NI because of a) missing compatibility and b) wrong minimum requirements
btw...can  Labview be completely deinstalled at all...?
sorry for asking a bit agressive but this "NI program" cost me several days now for nothing
Hints esp. to Question 2 would be very appreciated...
Solved!
Go to Solution.

mwo wrote:
is that much...?
Yes, 1MB for code and 3MB for diagram objects for a single VI seems a lot. How complicated is that VI? I would recommend to modularize it a bit.
In any case, you might want to submit the code to NI, maybe there is a bottleneck in the compiler that could be improved. The 2010 compiler is much better, and I never have speed issues, even with large projects.
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

  • How can I fix the long delay (15 min  ) between the time I select a song to the time it begins playing?

    How can I fix the lond delay (15 min.) between the time I select a song to the time it begins playing?

    Hi Ben,
    This is a common issue that NI LabVIEW does not address.
    The good news is that OpenG provides a function to do just what you need.
    See this article: Resize Front Panel to largest decoration
    The way to get the OpenG functions is to use the JKI VI Package Manager (VIPM).
    In addition to the OpenG functions there are several other community provided tools avaliable through VIPM.
    For a quick test, I'm attaching these files (LV version 2010 sp1):
    Fit VI window to Largest Dec__ogtk.vi and the required sub vi Current VIs Parents Ref__ogtk.vi.
    You should really use VIPM to get the full OpenG library - there are many gems in there.
    steve
    Help the forum when you get help. Click the "Solution?" icon on the reply that answers your
    question. Give "Kudos" to replies that help.
    Attachments:
    Fit VI window to Largest Dec__ogtk.vi ‏29 KB
    Current VIs Parents Ref__ogtk.vi ‏9 KB

  • Building App Gives Error 6 about 50 - 80 - 99% of the time. Windows7, LabVIEW 2010 SP1

    Hi
    First off here is a link to a discussion of the problem.  http://forums.ni.com/t5/LabVIEW/Error-6-occurred-when-building-an-Executable-in-Labview-2009/m-p/997...
    I have tried all the suggestions on this link with no luck.
    Background:   have been using LabVIEW 2010 without problems since Sept, then I started getting the error 6 with the following message.
    " Error 6 occurred at Delete in AB_Engine_Delete_Internal_Files.vi->AB_EXE.lvclass:Build.vi
    ->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller "
    This started on one project and is now occurring on another project.  Sometimes it builds 50% of the time, other times I can't get it to build at all.  I have upgraded to SP1, no change.
    Here are some things I have tried.
    Moved build directory to c:\a
    Renamed project, moved project right under c:\
    Disabled Google , disabled Win indexing, disabled Win7 user acct. Control, run LabVIEW as Admit all the time, win explorer closed
    mass compiling, closing the project, closing LabVIEW, re-booting
    Unistalled LabVIEW 2010 SP1 and re-install, twice.
    I believe I rebuilt my project in a new project.
    I moved my projects to a WinXP system laptop I have, and they never get Error 6 !  Short term fix, but I have to use Win7.  So I hope this means it is not my code.
    The funny thing is that this is totally random.  The unfunny thing is having to explain to a client I can't get my code to compile during a frustrating 95% of the time failure episode, yikes!
    Any help and suggestions would be welcome.
    BTW, the next step is to totally uninstall LabVIEW with a 'special' procedure and piece of code sent to me.  Don't want to, but am really at wits end.  Also waiting to hear back from my service ticket, but am desperate to have parallel solutions to try.
    Thanks
    Mark Ramsdale

    Thanks for the clarify.
    I also meant to post this link.  It has a lot of info, this is the link I tried most if not all of the suggestions for.
    http://forums.ni.com/t5/LabVIEW/Get-Error-6-about-50-of-time-when-building-Application/td-p/1242634
    By the way, I was told that uninstalling LabVIEW will not resolve the issue, dodged a time killer :-)
    It seems the error is caused by Win7 and file reserving.  Waiting to hear back on that.  Have an SR.
    Again, any suggestions welcomed, maybe some Win7 ideas from those who know more about it.
    mr
    Mark Ramsdale

  • LabVIEW 2010 local variable behavior

    Hi -
    I upgraded to LabVIEW 2010 from 2009SP1 and the attached sub VI no longer works correctly.  This is a state machine case structure that gets called inside a loop.  I'm setting a Boolean local variable true, then on the next call when the case changes the variable has been reset to false. It did not do this in LV2009.
    Someone will immediately tell me I have a race condition, but these local variables are not being written anyplace else, just within these separate cases.
    See the attached code, specifically, the local variable "Enable" is getting reset when going from case "Enable" to case "Turn on".
    Anyone else seen this issue, or can shed any light?
    I fixed the VI by writing the value in each case, but this different behavior makes me wonder what other issues are lurking in LV2010?
    Thanks
    Solved!
    Go to Solution.
    Attachments:
    eq99_cycling.vi ‏42 KB

    This code looks more like some sort of an Action Engine than a state machine, but not quite.  It gets called repeatedly from a state machine, and it decides what the next state will be depending upon the inputs.  Instead of using all those local variables, I would use uninitialized shift registers (nothing wired to the left side).  They hold their value from one call to the next.  One more case needs to be added in this case.  An unnamed, default case that would set the initial values of all the shift registers.  Make it the default case and don't even name it.  It will be called first automatically because the shift register is uninitialized so the default will be called.  Inside the default case, set all the shift registers to desired values.  Next time this subvi is called, those values will still be there.  That is as long as nothing is wired on the left side,  Whatever is wired to the state shift register will be the next case called.
    See attached vi.  It is broken because I did not wire anything to the indicators.
    - tbob
    Inventor of the WORM Global
    Attachments:
    eq99_cycling-4[2].vi ‏33 KB

  • LabVIEW 2010 will not install on Win XP SP3

    I have made several attempts to install LabVIEW 2010 on Win XP SP3. I already have LabVIEW 2009 installed and working.
    For each attempt I accept the default install options and do not put in a serial number. The first attempt got stuck at 2% complete and did not change for 30 minutes. No error messages. I cancelled the install and tried the install again from setup.exe.
    The next two attempts stall at 0% blinking forever. The 4th attempt made it to 18% before it stalled for more than 30 minutes. The next two attempts stalled at 0% repeating and would not cancel. I had to terminate them with Task Manager.
    Why won't LabVIEW 2010 install without stalling before than 30 minutes? Why does it not spit out an error message instead of just stalling? How do I know why it won't install?  How do I fix it?
    Solved!
    Go to Solution.

    I had the same problem. The 2010 install was very slow on my XP SP3  PC. I do not why, but it took very very long time to get past 2% of the setup. But then the install process speeded up. So just let the computer take the time that is needed. It will eventually install. I used the trail version download from NI
    Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
    (Sorry no Labview "brag list" so far)

  • NI Developer Suite 2010 is not LabVIEW 2010

    Received new disks that read "NI Developer Suite 2010", which is misleading because this is not LabVIEW 2010, it is LabVIEW 2009 SP1. So now we have mismatched Developer Suite / LabVIEW.
    Richard
    Solved!
    Go to Solution.

    fix...
    Message Edited by Broken Arrow on 04-27-2010 02:33 PM
    Richard
    Attachments:
    blacksharpie.gif ‏12 KB

  • Wire mode bug in LabVIEW 2010?

    I had an application written in LabVIEW 2009 for a CFP-2220 that stopped working when it was converted to LabVIEW 2010, and I have tracked down the problem to one thing: the software sets the wire mode of the serial port. Calling this method simply disables the whole program. It works when run from LabVIEW...but if you build a startup application it will not even start. Remove the wire mode call - and voila, the application runs as it should.
    So - I can fix the problem easily by not calling the wire mode method, however this is no solution due to the fact that I need to use the RS-422/485 port in 2-wire RS485 mode.
    MTO
    Solved!
    Go to Solution.

    It turns out that this is an even stranger problem; the serial port init function will ONLY work in the built application if it originates from the vi.lib\Intsr\serial.llb file.  If you do a save as and substitute with original...then you would expect it to still work, it's the same VI, it has just moved...but no (!). Again - there are no warnings, no errors, and everything runs fine in the development environment, but if you deploy and run this application on the cFP-2220 it will only run if the serial port init VI came from that location. Save it to another location (no conflicts caused by this)..build it again, and the application will not start. You can even move the whole serial.llb file to somewhere else and call the serial init file from there - and that's enough to stop it from working.
    The reason why I though that I had linked this to the wire mode was the fact that I got everything to run when I used the standard serial port init VI...but if I saved a copy of this to another location and added the wire mode to it it stopped working...so I assumed it was the wire mode, because that was the only thing that had been changed that would logically produce any change...the fact that it was moved should not have any effect....it turns out that was wrong.
    I have a few other variations to test (what if I edit the file directly in vi.lib\Instr, will it work then e.g.? That will not be a good solution, but a good thing to test anyway)...
    MTO

  • Using FTC module with LabView 2010

    Hello
    I use a LabView 2010 Student edition I have purchased to learn FTC , when I tried to install the FTC toolkit I got an error message requesting that Labview 2009 must be installed before installation can proceed (see picture)
    Why can't I use FTC on Labview latest version ? can I overide this error? is something that you can fix?
    Thanks
    Moshe Epshtain
    Attachments:
    FTC install page.PNG ‏168 KB
    FTC error.PNG ‏64 KB

    Hi Moshe,
    I would recommend posting this question on the FTC Forums.
    Thanks!
    Aaron P
    National Instruments
    Applications Engineer
    http://www.ni.com/support

  • I do not have the daq assistant vi on my labview 2010 and have found no drivers for it what should i do

    I do not have the daq assistant vi on my labview 2010 and have found no drivers for it. I downloaded the service pack but  that did not have it either what should i do.

    Hi Youzhang He, 
    Did you install LabVIEW first on your PXIe 8102 before the drivers?  Most likely, you're missing LabVIEW support for your DAQmx drivers. Fortunately, this is an easy fix. What you should do is open Add/Remove Programs, select National Instruments Software, select Uninstall/Repair. In the window that pops up listing NI software, select NI-DAQmx 9.x and select Modify. In the window that appears, expand Application Development Support and select to install LabVIEW support.  From here complete the install process and restart your system.  LabVIEW support should be installed and DAQ Assistant should appear in your palette.
    Allie

  • Application crashes in Windows 7 64bit made in Labview 2010 sp1 f2 with Fault module name%3A lvrt.dll%2C version 10.0.0.4033 and exception code c0000005

    I build an application exe and then its installer along with run time environment.
    The installers instals the application correctly but when I try to execute the application, I get an error that application has crashed and Windows must close it down or search for solutions online with this additional information for the crash. 
    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: AGMS.exe
    Application Version: 1.3.0.0
    Application Timestamp: 4c24e8f5
    Fault Module Name: lvrt.dll
    Fault Module Version: 10.0.0.4033
    Fault Module Timestamp: 4c9273f4
    Exception Code: c0000005
    Exception Offset: 00005310
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 1033
    Additional Information 1: 0a9e
    Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
    Additional Information 3: 0a9e
    Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt
    I am using labview 2010 sp1 32 bit on a 64-bit machine, with the following specs
    Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
    Language: English (Regional Setting: English)
    System Manufacturer: Dell Inc.
    System Model: Dell System XPS L502X
    BIOS: Default System BIOS
    Processor: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (8 CPUs), ~2.0GHz
    Memory: 8192MB RAM
    Available OS Memory: 8106MB RAM
    Page File: 3457MB used, 12753MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7601.17514 32bit Unicode
    The exe /application runs fine on my PC but when I try to run it on another PC it crashes. The other PC has similar specs as given below
    Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)
    Language: English (Regional Setting: English)
    System Manufacturer: LENOVO
    System Model: HuronRiver Platform
    BIOS: Default System BIOS
    Processor: Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz (4 CPUs), ~2.2GHz
    Memory: 4096MB RAM
    Available OS Memory: 4010MB RAM
    Page File: 1359MB used, 6658MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7601.17514 32bit Unicode
    I tried another machine, 64 bit of course, as I want to deploy my application on a 64bit PC, but still got the same problem.
    This other machine was from HP, iCore 3 (4 CPUs) 2.2GHz, 4GB RAM and running Windows Professional 64 bit.
    Now as I see it, it could be a Run-time environment mis-match error.
    For this I tried installing a 64 bit LVRTE from NI, but still no sucess.
    I checked DEP, for all 3 PCs and it was set to the following
    Turn on DEP for essential Windows programs and services only (first option).
    I am confused. I can not find a solution for this and it is really frustrating.

    But I am assuming that when I make the installer, the 32-bit Run Time Engine is appened with the installer, as show below
    Since from the picture you can see its including the support installers from '\Program Files (x86)\'
    The application runs queries to fetch data from database in SQL server 2008, and for that I am using a Microsoft SQL Native Client 2008 R2 64 bit ( this is the only version that installs on either PC, even the one on which I developed my LV Application).
    I am not using any driver, only toolkits for reports - and for that I un-checked the "Remove unused polymorphic VI instances" when making the executable, otherwise LV throws up an exception that share variable are not being included.
    Yes I did reboot every time after I ran the installation.
    Still getting the same error.

  • Run-time engine problem in Labview 2009 and Labview 2010

    I have a problem with Labview 2009 and Labview 2010. I updated my Labview 2009 into 2010. But it turned out to be a trial one, because i did not have the serial number. So I uninstalled the Labview 2010. however, the funny stuff came over. I cannot use my Labview 2009. So i uninstalled Labview 2009 again. But eventually, I could not reinstall Labview 2009. Every time i had a runtime error and i could not proceed with the installation. in addition, any installation  related to Labview is not permitted and the same error came up every time. it is very annoying.
    So, What is the deal?
    I attached the error here. Any comments or advice are welcomed and appreciated.
    Attachments:
    error.docx ‏2305 KB

    By chance is this machine's language set to any non-English locale?  You would check the locale setting by:
    Opening Control Panel.
    Opening "Regional and Language Options".
    Looking Under "Regional Options" >> "Standards and Formats"
    If it is set to something besides English, trying setting it to English and please report back what locale it was set to (or if this even solves the problem).
    Regards,
    - WesW

  • Report Generation toolkit for labview 2010

    H All.
    I'm looking to download the report generation toolkit for labview 2010. When I proceed to download the toolkit from the national instrumnets website, it says that i need to labview 2011 or later in order to install it.
    Is there a version of this report generation toollkit for labview 2010 and can someone provide a link maybe??.
    Thanks for reading.
    Solved!
    Go to Solution.

    Try this: [Link removed, NI software downloads can be found on ni.com/downloads, the LabVIEW 2010 Report Generation Toolkit is available to customers with Standard Service Program here: http://joule.ni.com/nidu/cds/view/p/id/3247/lang/en, other customers may contact NI directly]
    Beginner? Try LabVIEW Basics
    Sharing bits of code? Try Snippets or LAVA Code Capture Tool
    Have you tried Quick Drop?, Visit QD Community.

  • How to configure LabVIEW 2010 to communicat​e with GE Speedtroni​c Mark VI ethernet global data (EGD)

    We want to use LabVIEW 2010 to send/receive floating points from LabVIEW 2010 to/from a network (192.168.101.xxx) that utilizes GE ethernet global data protocol (EGD).
    The network has several HMI's running Cimplicity Plant Edition 4.01.
    We can configure Cimplicity to read modbus points from LabVIEW using LabVIEW's multi-variable editor and a modbus slave library.
    However, we cannot get the points from LabVIEW to read/write to the EGD protocol.  Anyone ever run into this?

    EGD is a UDP message (port 4746h) with a special header.See below for header structure (32 Bytes). Send UDP at constant rate. Limit user data to 1400 bytes. If you want to receive EGD data don't forget to increase the MaxSize connector on UDP receive to 1500. Are you using the a csv file or SDB Server to get tag names? Or manually entering tag names in cimplicity? This works much better than OPC because all parameters are contained in your labview executable. If you have a redundant cimplicity HMi Server send as Broadcast to the local subnet. All consumers will get the EGD telegram.  Example IPA of 192.168.0.255.  Server 1 IPA 192.168.0.1 and Server 2 IPA 192.168.0.2
    Maybe to late for this project but would be a good upgrade or the next project.

  • Integral blocks from labview 7.1 where is in labview 2010

    Hi I must integrate sampled signal. In labview 7.1 is good checked blocks for it. But where is equivalent in labview 2010?? I cant find it.
    Solved!
    Go to Solution.
    Attachments:
    calkowanie.png ‏2 KB

    http://zone.ni.com/reference/en-XX/help/371361G-01/gmath/integral_xt/
    Did you try the search capability for the functions palette?
    Attachments:
    functions search.png ‏17 KB

  • No longer able to import CVI Instrument Driver in LabView 2010

    Hello,
      I used to be able to download the Import CVI Instrument Driver Wizard in LabView 2009, but there is no wizard for 2010?
    I also tried importing the driver with the shared library import, but then Binary, Slides and Rings do not come up with their values i.e. if my slide in CVI has 3 positions :
    Description      Value
    Item 1                 1
    Item 2                 2
    Item 3                 3
    or if my Binary has
    Description      Value
    On                        1
    Off                        0
    they do not import the description into LabView 2010?
    I tried copying the directories created by the 2009-wizard to the directories of 2010 i.e.:
    from     C:\Program Files\National Instruments\LabVIEW 2009\resource\CVIFpConv
    to          C:\Program Files\National Instruments\LabVIEW 2010\resource\CVIFpConv
    and
    from     C:\Program Files\National Instruments\LabVIEW 2009\project\_DriverCtoLV
    to         C:\Program Files\National Instruments\LabVIEW 2010\project\_DriverCtoLV
    and the wizard loads and runs until I specify a .fp file and then I get the error in the jpeg attached. When I try to open the block diagram (FC_RFL_Initialize.vi), it says you need a password to view it, so that stops my debugging.
    Attachments:
    Error using Instrument Driver Import Wizard in LabView 2010.JPG ‏88 KB

    HI,
      I downloaded the wizard and when I tried to import a driver I got this message shown below...(labview 2010)
    Thanks...Ness
    Attachments:
    Error message.JPG ‏140 KB

Maybe you are looking for