Loading my VI in LabVIEW 8.2.1 causes LabVIEW to hang.

Loading my VI in LabVIEW 8.2.1 causes LabVIEW to hang. I have an older version that sometimes loads, but it causes LabVIEW to hang many of the times as well. I think the older version of my VI only hangs when you try to scroll around by clicking in the scroll bar area instead of clicking the scroll arrow. I am not getting any error messages. I have to close LabVIEW using the task manager. I've tried this on multiple computers with the exact same results. The VI has sensitive information, so I would rather not post the VI publicly. If you have the capability of debugging a hung LabVIEW .VI, then please send me your email information.
Thanks,
Matt

Hi Matt,
nice to hear that trick helped. Usually LV informs you about any "insane objects" before saving, in this case you should perform this procedure immediatly... When the vi "kills" LV while loading it's too late.
To rate messages you should click on those "kudos" buttons right to the message. Once should be fine, but it's Christmas time and nice to give away presents Maybe you're too new to the forum and this option isn't enabled yet?
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Similar Messages

Error 404 causes Labview 2010 to crash but only occasionally

Hello,
I am requesting help to solve a problem with LabVIEW 2010 crashing. I am new to this company and the last Labview developer left without providing
background on this problem. Labview crashes after running project VIs. Labview closes without warning or error messages. The project acquires data from pressure transducers, dP transducers, thermocouples, IEPE, load cells, and voltages through NI real-time system and has digital I/O. NI hardware includes PXI-1050 with modules 6221, 6280, 6224, 6220 and NI PXI-1052, SCXI-1306, SCXI-1112, SCXI-1520, and SCXI-1102. I've reviewed the labview program and the software relies heavily on shared variables, references, and local variables but I cannot find anything that stands out as a problem in the software .
The program crashed again today after running for only 1/2 hour and was not recording data. No error message occurred before the crash and the only error after restarting LabVIEW was the standard message that LabVIEW did not close properly. I went to the Event Viewer and at the time of the crash I received the following information:
Event ID = 3299
Source = LabVIEW
Log = Application
Level = Error
LabVIEW Information: Error 404 "Not found" for "/national instruments/ real-time execution trace toolkit/ 2.0/ trace receiveport", file "Crogram files (x86)/ national instruments /shared/ ni webserver/ www/ national instruments/ real-time execution trace toolkit/ 2.0/ trace receiveport": Can't access URL
According to Event Viewer, this error 3299 occurred 15 times in the last 3 days. LabVIEW crashed today at 10:19 am at the same time this error 3299 occurred but LabVIEW did not crash the other times this error occurred in the last 3 days. I believe this error is related to the crash but does not usually cause the crash. It appears to me from reading the error message that the error is the result of occasional lose of communication with the real-time system (Can't find URL). Any suggestions how to resolve this would be greatly appreciated.
Bill

1. Have you had this code working before on this or another machine?
2. Which operating system and version of LabVIEW are you running? (This can be found in Control Panel >> All Control Panel Items >> System)
3. Which National Instruments Drivers are you using? (This can be found in the measurement an automation explorer under the software tab [a screenshot would be good])
I would look into removing afsetup.exe which is a data collection tool provided by Microsoft which could a) not be installed correctly and/or b) trying to pull data from LabVIEW. I think this may help you out, as even though your programs aren't explicitly calling it, the service is running in the background.
Secondly, I would look into stopping the NI Web Server application that could be polling a web page that's not needed.

How can I call a LabVIEW executable from within another LabVIEW executable?

I have a customer requirement for two LabVIEW executables. Based on their current setup, they need to run executable "A" or "B", both of which are under independent revision control. I have created a third "selection" executable that allows the operator to choose between one of the two, but I am receiving errors when I attempt to call a LabVIEW executable from within a LabVIEW executable using either the "System exec" VI or the "Run Application" VI. If I call a non-LabVIEW executable (such as Windows Explorer) everything works fine.

> I have a customer requirement for two LabVIEW executables. Based on
> their current setup, they need to run executable "A" or "B", both of
> which are under independent revision control. I have created a third
> "selection" executable that allows the operator to choose between one
> of the two, but I am receiving errors when I attempt to call a LabVIEW
> executable from within a LabVIEW executable using either the "System
> exec" VI or the "Run Application" VI. If I call a non-LabVIEW
> executable (such as Windows Explorer) everything works fine.
As with the other poster, I suspect a path problem. You might try the
path out in a shell window, and if it works, copy the complete absolute
path to LV to see if that works. LV is basically passing the comma
nd to
the OS and doesn't even know what is in it, so you should be able to get
it to work.
The other poster commented on subpanels, which is a good suggestion, but
without going to LV7, an EXE can have open more than one VI. You can
use the VI Server and the Run method to fire up another top-level VI.
The decision is whether you want both to be in unique processes.
Greg McKaskle

How can i use labview.tlb to control Labview from an external application?

Hi,
I've been told by a labview engineer that i could use the file
labview.tlb located in the labview install folder to control labview
from an external application (in my case, a C# app). I'm using Labview
6.1 under Windows 2000. This article confirms that:
"ActiveX and LabVIEW"
http://zone.ni.com/devzone/conceptd.nsf/webmain/5401BE584FBAEECE862567C2006D36C7?opendocument
But i've not been able to find out how to use this file to achieve
what i want. I just want to be able to open/close labview, open/close
a vi, start/stop a vi, hide/show a vi from a C# application. The above
web page talks about activex but i really don't see the realtion
between activex and that labview.tlb file.
Is there so
mebody around who knows how to use that file? Why does NI
tell us that it's possible to do what i want to do but doesn't explain
how (or hides this info very well)?
Thanks

Hi,
> Hi I am fighting a similar problem and so far I found this: Calling
> LabVIEW from C++ Using ActiveX
>
> http://sine.ni.com/apps/we/niepd_web_display.DISPLAY_EPD4?>p_guid=B45EACE3E21356A4E034080020E74861&p_node=DZ52051&p_submitted=N&p_rank=&p>_answer=&p_source=External
Thanks for the link, i actually already found this link before. I've
found yesterday how to use Labview.tlb, just add it to the references
of the project, it was probably too easy for me at that time:-) But
now, i'm still stuck as there is no doc about using the interfaces and
classes of this activex to control labview.
The example given on your link is made is C++ and for some reasons,
the wrapper generated for Labview.tlb when i added it to my c# project
doesn't seem to expose the same
interfaces and classes as the one used
in the C++ example. I therefore can't use the C++ example in C#.
I've tried to do something like:
LabVIEW.ApplicationClass a = new LabVIEW.ApplicationClass();
Just this line causes labview to launch but then immediately throws an
exception: "Query interface for interface LabVIEW._IApplication
failed".
Does somebody knows how to use that control in C#/VB.NET ?

Problems with project when switched from Labview 8.2.1 to Labview 10

Hi everyone,
I recently switched from Labview 8.2.1 to Labview 10.
Before I can run the project I get the error which you can see in the attachment.
(The project is running well in Labview 8.2.1)
I did already check if variables end with a space, but none of them are.
The variables are also without any slashes, so that couldn't be the problem either.
Does anybody has any idea what the problem can be, please let me know.
I hope to hear from some of you soon.
Regards,
Kenny
Attachments:
Error Labview 10.JPG ‏19 KB

Your other post in the other thread indicates you've looked at that thread. Based on that have you checked your variable names to see if any of them are multi-line? The error message is basically telling you that you have illegal characters. A carriage return (\r) or a new line (\n) is an illegal character.

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

Running the VI causes LabVIEW to crash

Hello
While debugging a SW, I found that a particular VI, when run, causes LabVIEW to crash. This happens whether this VI is called while executing an exe or called by higher VI or even when it is run separately.
The VI to be run is NLD_Test_PP_Plot.vi present in the folder "Generic VI's".
The input for this VI is .csv file, which is attached. The csv file needs to be placed in a separate location and that path needs to be entered in the string constant in the VI.
Note: This VI is developed and run in LV v2009.
Thanks
Sharath
Attachments:
SpecimenCW_20150407_193059.csv ‏67 KB
NLD_Test_PP_Plot Folder.zip ‏208 KB

LabVIEW did not crash for me (nor did it throw an error). It made a bmp of your data and then exited. I am using LV 2013.
Did it actually crash or did it throw an error? If it crashed, do you have the crash zip file?
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Deny Access function with invalid file refnum causes LabVIEW to crash

Hi folks,
I have LabVIEW 8.5, and today encountered something interesting that consistently causes LabVIEW to crash. Essentially, if you find the "Deny Access" function under the advanced file IO palette and wire up an invalid refnum, Windows (XP in my case) reports that LabVIEW has to close. I checked in task manager, and the LabVIEW process is still active and using a disproportionate amount of the CPU.
To reproduce the issue, simply drop the function on your block diagram, create a constant from the refnum input terminal, and run the VI. Has anyone else seen this behavior?
Thanks,
Jim

Hi Carla,
I'm glad to help, and thanks for looking into it. The way I ran into the bug was while I was working on an action engine VI to log certain text values (see attached picture). While logging, I didn't want other programs to access the file. When a new file had to be generated, I wanted to stop denying access and close the reference. However, if the value on the shift register was invalid, LabVIEW crashed instead of throwing an error (I guess a crash qualifies as an error).
If you look at the attached picture, my workaround was to use the "Not A Number/Path/Refnum?" function. If the reference is bad, I don't try to use the "Deny Access" funtion or close the file. That worked just fine and seems like a good solution for now.
Jim
Attachments:
Logger.png ‏6 KB

Build a DLL in LabVIEW & Use the DLL in LabVIEW

I am trying to build a DLL for the simple vi with LabVIEW and want to use the DLL in LabVIEW. is it impossible?
I wrote a vi and it have 2 terminals. one is the input for numeric dbl data type and one another is the output for numeric dbl 1D array data type.
It was built with the Application builder for LabVIEW 8.0 and DLL was created successfully.
I want to use this DLL in new vi with LabVIEW.
Call library function used. I wrote a new vi to use that DLL.
In config dialog I config each parameter for dll and connected terminals. but it doesn't work
pleas refer to the attatched file and let me know what I missed.
Attachments:
Array1D.zip ‏60 KB

At first I kept scratching my head wondering why someone would want to do this. Create a DLL in LabVIEW to call it from LabVIEW. Seems redundant. But, perhaps it's an exercise or perhaps it's for testing the DLL...
In any event, calling the DLL worked for me in 8.2. How are you configuring your Call LIbrary Function node? I have it set up as follows:
return type: void
iteration: Numeric, Signed 32-bit Integer, pass by value
array1D2: array type, Signed 32-bit Integer, 1 dimension, "Array Data Pointer" format
len: Numeric, Signed 32-bit Integer, pass by value
Then I called the DLL like this:
Message Edited by smercurio_fc on 03-16-2007 12:57 PM
Attachments:
Example_BD.png ‏2 KB

Convert VI llb from LabVIEW 5 for use in LabVIEW 8.6

Hi Everybody!
Firstly, I'd like to say how much I have enjoyed working for NI and especially supporting the online community in my spare work time. I have to say it is a great place for NI, long term users, new users and everything else LabVIEW - and you guys have fun! Excellent.
I am now back at university and I am looking to use LabVIEW for some robotic work. During my research I have found some manufacturer's VIs for the hardware: however their 'latest' version appears to be in LabVIEW 5.
Would someone be so kind to convert my VIs into at least LabVIEW 6, or up to LabVIEW 8.2.1 (Last version that can open LabVIEW 5 VIs) that would be great. My LabVIEW 8.6 should be able to open VIs saved in LabVIEW 6 or greater. (Obviously not LabVIEW 2009!)
Reference: How to Upgrade or Revert a VI to a Different Version of LabVIEW
Thanks ever so much in advance (I miss the day I had every version of LabVIEW - and NI software on my machine!)
Regards,
James Hillman
Message Edited by Hillman on 10-04-2009 10:16 AM
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!
Solved!
Go to Solution.
Attachments:
Koala_PC.zip ‏328 KB

Mass compile in 7.1
Felix
www.aescusoft.de
My latest community nugget on producer/consumer design
My current blog: A journey through uml
Attachments:
Koala_PC.zip ‏274 KB

Agilent Driver Causes LabVIEW to Blow Up and Stop

I have started to use the AG6000A driver for LabVIEW. It seems to work fine until I do a "Text" search and only on specific drivers. When I search on the "Acquire Multiple Waveforms Example"for any text, the LabVIEW application ends suddenly causing a loss in any work that is being performed. Anyone else have this problem?
I am using LV 8.5 on a 32 bit Windows XP OS.
Thanks.
Michael
Solved!
Go to Solution.

The driver I found at http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=0D3F5F0998FE61CAE0440003BA7CCD... and I selected version 8.0. However, I also found this driver:
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=1E5E6D70FCA569A3E0440003BA7CCD... and I selected version 8.2.
I downloaded the 2nd driver and had no problems and them I download the original driver and again had no problems. All is well now. Something must have happened when I added the driver to the LabVIEW instr.lib folder. Anyway, sorry to bother.
Michael

Some of the c function are not directly wrapped in to labview how can wrapping to labview

hi here shambhu
i have problem that some c call i.e. MTL.dll can wrapped in to labview directly, some of the c function MTL.dll are not directly wrapped in to labview .How can wrapping to labview.Please suggest me how to over come.Those global data sharing calls will be woking in labwindow cvi.
Attachments:
Template.vi ‏12 KB
Template.uir ‏13 KB
Template.c ‏8 KB

After I posted this, this showed up as a suggestion:
https://discussions.apple.com/message/17723048
The "killall Dock" works, have to try the
~/Library/Preferences/com.apple.dock.plist
Drag that plist file to the desktop.
Reboot, and your problem should be fixed.
later on

Convert these VIs ZLibInflate,ZLibDeflate of LabVIEW version 5.0 into LabVIEW 2009

Convert these VIs ZLibInflate.vi,ZLibDeflate.vi of LabVIEW version 5.0 into LabVIEW 2009

Hi priyash,
you should be able to download them with the VIPM.
Mike

External lib call exits on error, which causes Labviews Solaris to exit completely.

I have an external lib which VI's make calls to.
When my function follows the error path, it makes a
call to another lib which does an exit(11).
This in turn causes Labviews 6.0.2 (Solaris 8).
I have the same libs on NT, and Labviews gives a popup
dialog with an error string.
Anyone know how to prevent Labviews from exiting???
I cannot change the 3rd library.
Thanks!

> When my function follows the error path, it makes a
> call to another lib which does an exit(11).
> This in turn causes Labviews 6.0.2 (Solaris 8).
> I have the same libs on NT, and Labviews gives a popup
> dialog with an error string.
> Anyone know how to prevent Labviews from exiting???
You might try to install a signal handler. I don't remember the syntax,
but you have to have a C style function pointer, and you call something
like InstallSignalHandler.
You might want to install it, call the faulty function, then set it back
to its initial setting.
Greg McKaskle

Sendmail plug-in not loaded at installation of Reader 10.1.3 - reader goes in hang mode

HI, Installed Reader 10.1.3 and the sendmail plug-in does not load. When trying to attach an email, reader goes in hang mode and I have to force quit. How can I load the plug-in? Thanks!

wankel wrote:
I would see an Adobe exe in the list of running programs
That is rather strange; the Adobe Reader executable is AcroRd32.exe
If that is what you actually saw, can you check the Event Viewer (applications) for the time when that happened, if you can see any reasons why this happened?

Loading my VI in LabVIEW 8.2.1 causes LabVIEW to hang.

Similar Messages

Maybe you are looking for