LabView 2010 Lockup on opening VI

I am running LabView 2010 SP1 with about 15 X-Controls on the front panel. When I open the main GUI VI, I get about 750 - 800 VI's in during the Loading phase and then the LabView program locks with one of hte processor cores fully consumed. It seems that if I Clear the compiled cache or sometimes do a Mass compile I can get it open, but this needs to be done even after closing the VI and then re-opening.
Any ideas are appreciated as to what could be causing this or any way to get further debug information.
Thanks,
Anthony

Hi Yeager,
Thanks for your question. Since you have so many subVIs, and although it will be tedious, you might want to choose to inline some of them which would make loading them and running them faster. Inlining is for subVIs that do not contain recursion or automatic error handling, and it automatically compiles the code and places it into the calling VI. You can inline by going into the subVI and press on File>>VI Properties. Then click on execution and place a checkmark in the Inline subVI into calling VI checkbox. You must also place a check mark on the Reentrant execution checkbox on that page.
Another option would be to load subVIs as subroutines, once again by going into the VI properties and selecting subroutine from the priority pull down menu. Here is a link with more information on this. http://zone.ni.com/reference/en-XX/help/371361H-01/lvconcepts/vi_execution_speed/
You can also right click on the subVI in the main VI (if you can hopefully get it loaded at least once) and choose call set up, then choose reload for each call or load and retain on first call. This loads the subVI into memory when the first call to it is made rather than loading it into memory as soon as you open up the main VI. See this link for more information http://digital.ni.com/public.nsf/allkb/387EF1BC4762A96C8625713B007E0032?OpenDocument.
Regards,
Basil
Applications Engineering
National Instruments

Similar Messages

Can not Open exe file that is created by Labview 2010 SP1

Hi Everyone,
My Operating system is XP .. I installed .net latest version but I can not open exe file. I try to open exe file, then crashes , quits without seeing any interface.
I tried with another computer whose o.s is xp too. I can open exe file. I saw it is created by Labview 2010 Sp1
I dont know what the difference is. I attached config file.
Attachments:
TPS65175 C (Vcom only).ini ‏1 KB

burak35 wrote:
[..]Do I need any other components besides .Net?
That's a question only the provider of the application can answer.
You could also take a look into the system event log if there is an indication for the reason of the application failing to start properly. It is possible that certain services are required for the application, but they do not run on the machine.
Another point is possibly missing rights. So you might want to test the application once with the option "Run as Admin" (right click menu item on the application shortcut or the exe itself).
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Error 7 when opening file running LabVIEW 2010 executable

I am using Open/Create/Replace File in LabVIEW 2010 to open a text file. This works fine until I compile the code. I then get Error 7. I have tried paths that look like the following but none work.
c:\<directory name>\file.txt
c:\<application name.exe>\file.txt
c:\<application.exe>\<directory name>\file.txt
Thanks
Solved!
Go to Solution.
Attachments:
read.vi ‏17 KB

You have to get the path to the folder of the .exe. Then strip off the .vi name and the .exe name. Then Build onto the path from there to get to your .txt file. The way you have it, you are treating the .exe as a folder rather than a file. The text file is not part of the .exe, so you can't create a path that includes the .exe name.
Why Does My Executable Not Work When Using the Current VI's Path Constant?

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

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

3D graphs cause LabVIEW 2010 to hang

I've been using LabVIEW 2010 for several weeks without any problems, but today I noticed that it doesn't work at all with anything related to the 3D picture control. Today was the first time that I tried doing anything with the 3D picture tool since installing LV 2010. Dropping any of the 3D Graphs on the front panel of a new VI causes LV2010 to hang. (By hang, I mean the VI window remains open but most UI things no longer work. Right-clicking on the window does not show a context menu. The main menu doesn't work. The X button does not close the VI front panel window nor the diagram window. Control-Q does not cause LabVIEW to quit. I have to kill the process in Task Manager.) It is the same story with just a plaing 3D picture indicator. Also, the solarsystem.vi example does not work either. The problems start as soon as I open the solarsystem.vi. After killing LV with Task Manager and relaunching LV10, I do not get the LV message about a previous crash.
The problem I am talking about is for LabVIEW 2010 with the f2 patch running in Win7. I am actually running it using VMware Fusion 3.1.3 on a 2009 Mac Pro running Lion. The Mac drivers are all updated. Since it is VMware Fusion machine, the video driver on the Windows side is part of the VMware Tools installation, which is up to date.
After searching the forums, I've tried all the other potential solutions I could find: 1) repaired LV2010 using add/remove programs and 2) tried using the compatibilty mode settings to turn off Aero.
Interestingly, 3D graphs work fine on the Mac side for LV2010 for Mac.
Even more insterestingly, 3D graphs work fine on Win7 for LV 8.5, which I still have installed. The fact that it works fine for LV 8.5 would seem to indicate that Lion did not introduce the problem and that the video driver is working fine.
Solved!
Go to Solution.

Yep, it's the same virtual machine. I set it up almost 2 years ago and it has been extremely stable. Both LabVIEW 8.5 and 2010 have been perfectly happy on it. It's a great way to do LabVIEW on Win7. I didn't notice any changes at all to the VM when I upgraded from Snow Leopard to Lion. I installed LabVIEW 2010 before upgrading to Lion, but I didn't have occasion to work with 3D controls before the upgrade to Lion so I don't know if it would have worked on Snow Leopard. The Mac versions of both LabVIEW 8.5 and LabVIEW 2010 also work great on the both Snow Leopard and Lion.
I happen to have an XP virtual machine too, but I haven't installed LabVIEW there. Let me know if that would be a worthwhile test.
You might check with Marc Page--unless he has already upgraded again I think he has a similar machine to mine.
The video card is the original stock:
NVIDIA GeForce GT 120:
Chipset Model: NVIDIA GeForce GT 120
Type: GPU
Bus: PCIe
Slot: Slot-1
PCIe Lane Width: x16
VRAM (Total): 512 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0640
Revision ID: 0x00a1
ROM Revision: 3386
Displays:
Cinema HD Display:
Resolution: 2560 x 1600
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Display Connector:
Status: No Display Connected

LabVIEW 2010 SP1: "Controls" pop-up palette "Select a control..." bug?

I'm using LabVIEW 2010 SP1 (32-bit) and I noticed today that I cannot place my custom controls on a VI's front panel when I use the "Select a Control..." option on the "Controls" pop-up palette. I'm wondering if anyone else is having this same problem?
Steps to reproduce the problem:
1) Create a custom control, or download/save the attached custom control "Machine State.ctl" (< a strictly-typed enum control).
2) Open a VI (new or existing).
2.1) If the "Controls" palette is visible (pinned open), close it.
3) Right-click with the mouse on the VI's front panel window to display the "Controls" pop-up palette.
Note: DO NOT use the "Controls" option in the "View" menu here.
Note: DO NOT pin open the Controls pop-up palette at this point.
See my comments below in the "Notes" section.
4) "Controls" palette > "Select a Control..." option
5) Using the "Select the Control to Open" dialog, browse to, select and open the custom control file (e.g., "Machine State.ctl").
At this point the on-screen cursor should show the outline of an instance of the custom control I just opened, but for me that doesn't happen; all I see is the "+" crosshair cursor, and left-clicking with the mouse on the front panel does not place an instance of the custom control on the front panel.
Notes:
* In step 3) above, if I open the VI's "View" menu and select the "Controls" option, or if I pop-up the "Controls" palette and pin the palette to keep it open, I can successfully use the "Select a Control..." option to browse to, select, open, and place an instance of my custom control on the VI's front panel. The failure only occurs when I use the "Select a Control..." option on the pop-up (unpinned) version of the Controls palette.
* I can successfully drag-and-drop an instance of a custom control onto a VI's front panel from a Windows Explorer window, or from the LabVIEW project explorer window.
* The host computer is running Windows 7 Enterprise x64 w/ SP1.
Jim
Attachments:
MachineState.ctl ‏5 KB

Just now I tried creating and using controls on five different computers, each running Windows 7 Enterprise x64 w/ SP1.
On three of the systems the problem did not occur; I was able to place a user-defined control on the front panel using the "Select a control..." option on the controls palette.
On two of the systems the problem still occurs. Upon further investigation, however, I learned that the hard drives in these two systems were cloned from a "master" hard drive image the IT department created. So I'm guessing there's some bad mojo on the master hard drive image, and that's what's caused this problem to show up on these two systems (and others).
So for now, I'm just going to put up with having to use the old "drag-and-drop" method for placing user-defined controls on the VIs. Thanks for your feedback and assistance with this.
Jim

LabVIEW 2010 SP1 may not cleanly shut down

Occasionally LabVIEW 2010 SP1 (32-bit, running on Windows 7) will appear to "hang" when the "Getting Started" window is closed. The window disappears but the shortcut icon still appears in the Windows toolbar in the bottom of the screen. Right-clicking and selecting "Close Program" does not work and Windows seems to think any VIs that have been recently closed are still open. The program is still in the list in Task Manager and it can successfully be shut down all the way from there.
This is more of an annoyance than an operational issue (I think) - is there something I am doing (or failing to do) that causes this problem?
Thanks in advance.

Hello Unplugnow,
Deleting the .ini file will not cause any issues in terms of being able to reload Labview it will simply restore the default settings for Labview which will insure that there were be no data corruption issues. I have tried this procedure on my side with no issue although I would recommend copying the .ini file to another directory in case you need to recover this information at a later time.
To another note, does this issue arise when you are opening a particular VI, or does it occur when you are simply opening and closing Labview?
Best,
Blayne Kettlewell

Bug? LabVIEW 2009 Enum in Datalog Refnum Loses Data in LabVIEW 2010+

Hi
Can I please get support from an AE?
Attached is a LabVIEW 2009 VI with a Control of an Enum in a Datalog Refnum.
Whereby the Enum's FP Object is represented as an image.
In LabVIEW 2009 this works fine however, in any higher version (I have definitely tested with LabVIEW 2011, but have been told LabVIEW 2010 is the same) the image is blank.
Is this a bug - is data being lost?
Interestingly enough, if I remove the LabVIEW 2009 Enum from the Datalog Refnum then load in LabVIEW 2011 this image displays correctly.
Is there anything I can do (setting? etc...) in LabVIEW 2009 that will correct this problem so it displays correctly in later versions?
This issue originated in this LAVA thread.
Cheers
-JG
Certified LabVIEW Architect * LabVIEW Champion
Attachments:
Datalog Refnum Enum_LV2009.vi ‏10 KB

This was reported to R&D (# 311354) for further investigation.
As a possible workaround, if you move the enum control out of the datalog refnum before saving in LV 2009, when you open your VI in LV 2011 the image will still show up for the enum control. You can then move the enum control back into the datalog refnum and it should work fine.
Thanks for the feedback,
Daniel H.
Customer Education Product Support Engineer
National Instruments
Certified LabVIEW Developer

Labview 2010 crashes XP while looking for webserver

Hi,
I am using a Windows 7 laptop with LV 2010 to compile my 32-bit executable. I've copied it to my target Windows XP, SP3 computer and after running it for a short while it rebooted the computer automatically (I believe the reboot was caused by a BSOD).
I've gone into the Windows Event Viewer and there is an event that says "Labview information: Error: 404 "Not Found" for "national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc", file "c:/program files/national instruments/shared/ni webserver/www/national instruments/ni-rpc/interface/eadfc80d-1e6f-425b-8986-12ccef98f646/ncalrpc": Can't access URL ."
I'm attaching a jpg of the Event in case I typed it incorrectly. There is another post that mentions this error but there is no resolution and the discussion went in a different direction: http://forums.ni.com/t5/LabVIEW/LabVIEW-2010-unstable-on-Windows-7/m-p/1247366/highlight/true
Neither my Win 7 development laptop or my target Win XP system have this www folder.
Has anyone seen this before or know the cause? Thanks.
Steve
Attachments:
Event Viewer small.jpg ‏69 KB

Altenbach,
Thanks for the quick reply.
Yes, the time stamp of this error coincides with the crash. I guess I assumed that it caused the crash because I see about 20-25 instances of it in the Event Viewer. Immediately before these errors appear there are two instances of the NI Configuration Manager with the Description saying "Opening configuration database".
This only happened on time and I have not been able to reproduce it again.
I'll need to explain to my customer why this Error has appeared so many times in the Event Viewer, and also how I can get it to not happen again. Do you have any suggestions? Once I isolate this error and prevent it from happening again then I can monitor the computer for future crashes.
Thanks.
Steve

LabVIEW 2010 unstable on Windows 7

I am finding that LabVIEW 2010 is fairly unstable on Windows 7 Ultimate system.
LV stopped working several times, LV tells me that it stopped working, looks for a solution and then shuts down. Like just a few minutes ago, shortly after system power up.
Several times it just closes all of the Windows and terminates without any message or error displayed. Didn't even say goodbye.
I have even had one BSOD (which is hard to do on Win 7) almost immediately after an application was built and run. Didn't happen again when app was run again and built again.
I have only observed these problems with LV. All other applications have been running fine over the last month without unusual errors or misbehaver.
The system is only 1 month old. It is fairly clean with minimal software installed.
I don't know how much data on these problems that NI is capturing automatically. I haven't seen my system request permission to send problem reports to NI.
Has anyone else seen similar behavior with LV and Win 7 Ultimate?

I too am extremely (that's a total understatement) displeased with the behavior of Labview 2010 under Windows 7.
I get frequent crashes, some with recovery/log/.error message, some where Labview just exits. One minute I'm editing my code with 7 windows up; the next I'm staring at an empty desktop.
I too have started saving my work every few seconds. It's a royal pain in the ass.
I have turned in NUMEROUS bug reports, including samples of code that cause Labview to crash. MANY of them are related to typedefs. I just found another one and will be turning in that bug report within minutes. In this case I have a typedef (NOT strict) that contains only a combo listbox. If I right-click on the combo listbox, Labview silently exits and does no recovery or logging when started back up.
I have lost SOOOOOO much time trying to create code while fighting numerous Labview 2010 issues. The most egregious (to me) is that I have a control (I *want* it to be a strict typdef) that when I drop it on the Labview block diagram, Labview crashes. Yes this has been reported. I had to change the control from 'strict typedef' to 'control' to use it. The result is that every time I have to modify it (it's a work in progress) I heve to go thru my code and change over 60 occurrences of that control. By hand. If it was a typedef, I would change it ONCE.
I have a customer I'm developing Labview code for; I find it both personally and professionally embarassing to be missing deadlines for delivery, and blaming Labview instead of myself. But I have 3 pages of bug reports online with NI; each one cost me between an hour and 3-4 days of time. Many of them required me to redesign code I'd alrady written to avoid using constructs in Labview that simply don't work.
I'm glad to know I'm not alone - but absolutely dismayed that the code base for Labview 2010 is so buggy under Windows 7; it may be buggy on every platform, but that's all I'm using.
NI tech support has been helpful; but only to a point. They routinely generate correction requests based on my bug reports; not one has resulted in a patch from engineering to date.
I've been a software engineer for over 35 years. This is probably the 2nd worst experience with an IDE that I've had. The first was with a Sun product that was supposed to generate user interfaces; it simply was crap. Labview is dismayingly similar. If I'd elected to write this application in C I'd not only be finished, but it would have taken 6 months less on the calendar. Some of that is due simply to the way you have to construct and enter code in Labview; but in my case, most is due to failures of Labview to work as documentd, or to failures in the Labview documentation to explain what Labview is really doing (yes, I've turned those in too).
Here's an example of a Labview crash: open this VI and right-click on the listbox on the front panel. Make sure you do NOT have any other Labview code open at the time...!
Gary Sloane
SB/US Engineering Inc.
Attachments:
HL2_CAL_DISPLAY.ctl ‏5 KB

I'm getting a cwinstr error after upgrading from labview 7.0 to labview 2010

Hello
recently upgraged a PC from Labview 7.0 pro to Labview 2010 pro. Now I can not open a calibration executable we been using for a xantrex xfr power supply (unfortunately I don't have source code). The only error I get is "cwinstr-can't load program" pop-up when trying to run the executable. The calibration SW will run on multiple platfroms, Win 95, Win 200 0 and XP and this is the first time getting this error. The calibration SW ran fine until the Labview 2010 install. My question is does LV 2010 change the registry files when loaded? Visa and MAX still run fine on this PC and were loaded when LV 7.0 was installled. I know the calibration SW uses the VISA drivers so this is what's confusing. i don't want to downgrade back to LV 7.0 unless I have to.
Thanks

Hello Tanya,
I'm a little confused here. i only started having issues with the executable (it ran previously with the visa drivers from 7.0) after I loaded LV2010. After the install, the exectuable started giving me the cwinstr error. As best I can tell, this may be an activex issue, but since I only have the executable it hard to tell.
My question id do i have to install both labview 7.0 in addition to labview 2010 on the pc. Fom the the readme file, it looks like Labview 2010 won't support certain vi's older than 8.0. But since I'm dealing with an exectuable only here, I thought I should be able to open it at least.
So instead of updating the visa drivers, should i re-install the old visa drivers (Ni-Max) for 7.0 instead? would this even work without removing LV2010.
Thanks Again

Upconvert from Labview 5.1 to Labview 2010

Please convert these VIs (in zip) from labview 5.1 to Labview 2010
Solved!
Go to Solution.
Attachments:
c3d_reader_labview_b.zip ‏864 KB

Attached as 8.2, which you can open.
Note: The VIs in the "Files IO" folder have been deprecated. You should replace them with the single Read from Binary File function.
Attachments:
C3D Reader.zip ‏706 KB

Labview 2010 Student Edition, will it work with the Labview FPGA module and Xilinx Spartan 3E??

Just as the title states.
I did a search here on compatibility, but I am coming up short with not much to show for it.
I have Labview 2010 student edition, 32bit and 64 bit. I am trying to do a Senior Design project for my undergrad, and I am having some issues.
I was able to download the Support for the Xilinx Spartan 3E and Labview FPGA.
I install it, it runs through the unzipping process, installs, and then mysteriously I cannot find it. I have looked through my programs list and it is not listed. I open both editions of LabView and I find ABSOLUTELY NOTHING indicating that either one has ANYTHING to do with FPGA.
Did I install it wrong? Or is it just not supported in the studend version of Labview???
Can someone help me, please?

M Boat wrote:
What about the trial version? Any chance of it being on there?
I think everything is available for download, and without activation it will be in trial mode and you have about a month (?) before the trial expires.
A trial version of the FPGA module is available for download here. I have no idea if it would work with the student version.
I would recommend to talk to your local NI sales representative for advice. Good luck.
LabVIEW Champion . Do more with less code and in less time .

LabVIEW 2010 F2 - Crash - Localization issue ?

Hi fellows !
I am using LabVIEW 2010 F2 (French localized version) and I am facing this strange behavior. Can you confirm that this is a bug and / or this is because I am using a localized version of LabVIEW ?
When using the Modifications:VI property node (CTRL+SHIFT+B) and connecting its output to a case structure everything works fine (it looks like that).
But now if I change the Modifications:VI property to Modifications:Front Panel and let the output of the property node connected to the case structure, LabVIEW crashes or the broken arrow appears.
If I click on the broken arrow or try to save the VI (CTRL+S), I get the following error message :
Fpsane.cpp line 442
Thanks for your help.
Regards,
Da Helmut
Attachments:
err.PNG ‏11 KB
test.png ‏14 KB
test.vi ‏7 KB

Hi,
Thanks for the answer.
There is another bug with LabVIEW 2010 (F4 this time).
To reproduce it you have to create a (strict) type definition that consists of a cluster and put a constant which is linked to this typedef on the BD (just select the .ctl file in the BD) and then delete the type definition from the hard drive.
Close the VI that has the constant in the BD.
Re-open the VI, and in the BD, right click on the cluster constant and select "View as Icon". Now you get LabVIEW crashed. (ok it is useless doing that on a non existing typedef but this is crashing LabVIEW, so I thought this should be reported).
Keep me informed if you have any further informations about that.
Regards,
Da Helmut

LabView 2010 Lockup on opening VI

Similar Messages

Maybe you are looking for