LabView crash when intensity graph is in P6 of tab control

Any available fixes for LabView crash when intensity graph is put on page 6 of tab control and right-clicked??

Michael,
This has been fixed in LabVIEW 6.1.
Regards,
Cyril Bouton
Applications Engineer
National Instruments
Cyril Bouton
Active LabVIEW Developper

Similar Messages

  • LabVIEW crashes when you run a VI that contains a mixed signal graph with a multi-plot cursor.

    Hello, LV 8.2.1 notes indicates the following bug fix:
    43SAIR2A  Fixed an issue where LabVIEW crashes when you run a VI that contains a mixed signal graph with a multi-plot cursor.
    I am running this version, and still have this behavior.  Is there anything I may be missing, and/or certain circumstances that may still be causing this?
    thanks in advance,
    Darren

    Darren:
    I looked at the CAR ID that you mentioned and the issue has been resolved in LabVIEW 8.2.1. To verify something similar, I ran the attached VI and things worked just fine. Please feel free to send me the steps to follow to reproduce the issue you are running into in 8.2.1.
    Regards,
    Rudi N.
    Attachments:
    MixedGraphs.vi ‏15 KB

  • LabVIEW Crashes when Opening Project

    Hey Guys,
    I'm running into an interesting issue where LabVIEW crashes when opening a project. This is the second time I've run into this issue, on the same project. To get around it the first time I simply deleted and re-made my project, but since it's happened again, I need to figure out how to debug it. The symptom is that LabVIEW will crash when opening the project (sometimes I can see the "vi loading" screen) without any indication that crash has occured. It doesn't even launch the error reporter, the process just dies. Anyone know how I can go about debugging this?
    Solved!
    Go to Solution.

    xkenneth86,
    What version of LabVIEW? Have you ever had previous versions of LabVIEW on your computer? Can you attach a screenshot of the crash?
    David H.
    National Instruments

  • Labview crashes when creating large image files

    I have a problem with Labview 6.0.2( I've tested evaluation version 7.0 too).
    I'm constructing a very large image, for example: 4500x4500 pixels. Labview crashes when converting the pixture to a pixmap. The image is fully constructed on my screen (in a picture control), but when converting it to a pixmap (for saving the image in a known format (bmp, jpg, tiff)), Labview crashes.
    I did some testing and when the number of pixels exceeded the limit of 2^24(16777216), the file 'image.cpp' crashes on line 1570. The vi to convert it to a pixmap is: P'icture to pixmap.vi'
    Does someone know a workaround for this problem? Or is there a fix for it?
    Thank you!

    I've tested the 6i version of my VI in Labview 7.0 evalutation version. It raised an error but not the same error:
    d:\lvworm\src\lvsource\compatexport.cpp(37) : DAbort: Called a routine not in the compatibility LVRT table
    $Id: //labview/branches/Wormhole/dev/lvsource/compatexport.cpp#11 $
    0x004BD4CB - LabVIEW_Eval + 0
    0x0EB710D9 - lvs248 + 0
    0x094C87A0 - + 0
    So i replaced the picture VI's with the 7.0 evalutation version VI's, and it worked. It is now possible for me to construct very large image files!
    I see no attached VI to test. But i guess it is also solved in Labview 7.0
    I used this file to convert the picture to image data:
    C:\Program Files\National Instruments\LabVIEW 7.0 Evaluation\vi.lib
    \picture\pictutil.llb\Picture to Pixmap.vi
    And this file to convert image data to bmp:
    C:\Program Files\National Instruments\LabVIEW 7.0 Evaluation\vi.lib\picture\bmp.llb\Write BMP File.vi
    I guess i have to write a workaround for this problem:
    divide the picture in blocks of 4096 x 4096 and then merge the image data arrays of the bloks together.

  • LabVIEW crashes when I save changes to a particular VI.

    LabVIEW crashes when it tries to compile a particular VI. I have managed to get it to work a couple of times by changing a few things and making some subVIs, but the problem keeps returning.
    Is there some way to fix this or clean the VI of whatever corruption keeps occurring?
    Thank you,
    David R. Asher

    I can think of address/hardware conflicts or something that LabVIEW cannot provide an error message. I would go with hardware/address conflicts.
    Try renaming the file and executing it stand-alone. also try making it as a subvi and run the toplevel code.
    Kudos always welcome for helpful posts

  • Why does LabView crash when unloading my DLL (reentrant calls)?

    I have written a DLL in Borland Delphi using multiple threads that exports several functions (stdcall). I am using LabVIEW 6i on a WinXP machine.  All functions in the DLL work as expected and return correct values. Everything works fine if I set all Call Library Function Nodes to 'UI-Thread', but as soon as I set one Function Node to 'Reentrant', LabView crashes when I close the VI after it has been executed. I assume the error is caused by the DLL unloading mechanism of LabView. Other C++/Delphi programs using the DLL reentrantly work fine, this only occurs in LabView. In which thread does LabView call FreeLibrary/DLL_PROCESS_DETACH? Has anyone experienced similar problems?

    I have never run into this situation myself, but I do know that calling a multi-threaded DLL or CIN from LabVIEW does depend upon the following criteria:
    If your CIN/DLL doesn't have any global data storage (global variables, files on disk, etc.), AND it doesn't access any hardware (register-level programming) AND it doesn't call any functions/DLLs/Drivers that are thread-unsafe.
    OR
    Your CIN/DLL protects (with semaphores or mutex's) access to those global resources.
    OR
    Your DLL is only called from one, non-reentrant VI
    OR
    Your CIN is only called from one, non-reentrant VI AND you don't access any global resources from CINInit, CINAbort, CINDispose, etc. procedures.
    Hopefully this information can help you out in some way.
    J.R. Allen

  • Firefox crashing when i wanna open or close a tab or a window, also while wanna open any page, now what to do for solving the problem?

    Firefox crashing when i wanna open or close a tab or a window, also while wanna open any page, now what to do for solving the problem?

    Disable McAfee siteadvisor and check the problem still persist or not?

  • Labview crashes when trying to use bar graph

    Hi all; I am trying to make a 3D Bar or 3D Pie chart but LabVIEW crashes and shut down. When I try to pick up 3D Bar graph from controls to the front panel, LabVIEW shuts down without giving any error. I was using LabVIEW 2011 and now using LabVIEW 2012 evaluation version but the problem is same on both versions. I am using windows XP. 
    Any suggestions? 

    There has been reports about crashes like this in the past. There is already a CAR filed on this with LV 2009 which seems still to be "unaddressed". It is listed in e.g. the LV 2010 known issues.
    Since the source of the crash is a result of an incompatibility between OS, graphic driver (device) and OpenGL, i doubt that there is much NI as company can do about it.
    So i ask you to follow the suggested updates/test and see if the crash persists.
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • Why does LabView crash when I run it in parallel with a temp/ RH logging probe?

    I am running LabView 6.1 on windows 95. Up till now I have had no problems. However, we recently acquired a Temperature / Humidity probe which plugs into the Com1 port of the computer and logs the data using it's own software. Since then, when the two programs are used together, eventually LabView crashes with the following error message: Failure, 'image.cpp, line 5793.
    Can you tell me why this occurs and what the solution is?

    Taking a shot at this. It could be because the two programs are trying to access the same type of logging program(excel??). Only one link can be active at a time or they crash. Try running it without saving the data and see if it crashes.

  • Labview crashing when building application (exe)

    Hi,
    I am trying to build an application from a simple labview (2011) vi. All the vi does is sets (boolean = TRUE) a line on the digital output card (NI 9472) when I start running the vi. The program works fine after I have coded it. But when I try to build an exe file (application) of that project, then labview crashes in the build process. Is this a known issue? please help. I am attaching my vi alongwith this email
    Thanks
    Solved!
    Go to Solution.
    Attachments:
    relayProject.lvproj ‏34 KB
    relay.vi ‏21 KB

    I'm sorry to hear that gascars.  I have downloaded your project and VI and have succesfully built an executable in both LabVIEW 2011 and LabVIEW 2012.  Can you please send me a screenshot of the error you are receiving?  Also, can you make a simple VI that just adds two numbers and see if that can be made into an .exe.  
    Thanks
    Chris
    Chris
    National Instruments
    Applications Engineer

  • LabVIEW crash when saving from LV2012 to LV2011 with express VI and reopen in LV2012

    Hi all,
    Preconditions:
    Save the "Meas Angular Position-Buffered-Cont-Sync AI Sample Clk.vi" for a previous version of LabVIEW, in this case from LV2012 to LV2011
    Reopen the LV2011 VI in LV2012 according to the steps below.
    Steps to get it to crash:
    Unzip Crash.zip
    Open the "Meas Angular Position-Buffered-Cont-Sync AI Sample Clk.vi" and from there double-click (open) the "PulsedDerivative.vi" and from there double click the "Derivative dX/dt" express VI.
    LabVIEW crashes!!
    Alternatively when LabVIEW does not crash:
    Unzip Crash.zip
    Open "PulsedDerivative.vi"
    Inside the VI double click the "Derivative dX/dt" express VI.
    LabVIEW does not crash?
    Some compiler bug?
    Br,
    /Roger
    Solved!
    Go to Solution.
    Attachments:
    445b4df5-fd64-49a2-8302-f8ddf06af2d3.zip ‏62 KB
    Crash.zip ‏166 KB

    Hi Roger,
    Thank you for reporting this. I have filed CAR 390673 to our developers.
    Regards,
    Jeff Peacock 
    Product Support Engineer | LabVIEW R&D | National Instruments 

  • LabVIEW crashing when running NI-DSP VI on Windows XP

    I am in the process of upgrading a software application from LabVIEW 3.1 on Windows 3.11 to LabVIEW 7.0 on Windows XP with NI-DAQ 7.2. The hardware has been replaced, the relevant hardware change here is from the AT-DSP2200 to the NI-4551.
    The source code uses the NI-DSP libraries to control the DSP2200. I can't find any equivalent in the new LabVIEW (and have assumed that there is none, this is all covered in the MAXX now). The source code has been convereted to LabVIEW 7.
    When the source code is opened on the Windows XP machine LabVIEW crashes. I've traced to cause of this crash to the NI-DSP code. Whenever I try to open any VI that contains the DSP code it crashes LabVIEW. I think the problem is the CNI call
    inside the DSP library. When I try opening the source code on a computer that doesn't have the NI-4551 installed there are no problems.
    What is the upgrade from NI-DSP to? Is there a direct mapping of NI-DSP functions to equivalent NI-DAQ ones? How is it that having the hardware plugged in causes a crash even though it shouldn't be accesssed until I run the VI?
    Any help would be appreciated.
    Thanks.

    Hello EborLance,
    The NI-4551 can use either NI-DAQ or NI-DSA as the driver. If you only have NI-DAQ installed, any program that uses the NI-DSA functions may be crashing.
    There is no direct mapping of NI-DAQ functions to NI-DSA functions but you can download and install the NI-DSA driver from the website. Current DSA Drivers
    Once you have installed the NI-DSA driver, you should see the functionality you were previously used to and your program should run.
    Thanks,
    C. Flip
    National Instruments

  • Labview crash when saving

    Hi Forum
    When trying to save the attached file in 8.6 (the file is created in 7.1)  LabVIEW crashes with a Windows error telling me that the system has encountered a problem and needs to close.
    All the SubVIs save without problems and I don't see what should cause this specific VI to cause trouble.
    I have searched the forum and tried the different tricks mentioned in other threads about this issue, but none of them seems to help on my VI.
    I hope that somebody has a good suggestion as to what I can do.
    B.R.
    Martin
    Solved!
    Go to Solution.
    Attachments:
    Crash when save.vi ‏87 KB

    The problem appears to be with the typedefs. Specifically, it looks like it's the text ring. Disconnecting the typedefs in 7.1 and resaving it allows it to be opened in newer version. Attached is in 8.2
    Attachments:
    Crash when save 8.2.vi ‏27 KB

  • Labview crashes when building exe

    Hi all,
    I have created a Project and have a main vi which works fine in the development environment. When I try to build exe for the same, LabVIEW crashes. I dont get it why. If anyone could help on this, you are welcome.
    LabVIEW version:2013, 64 bit
    Thanks,
    Prabhu
    Solved!
    Go to Solution.

    Hi Prabhu,
    either provide full error descriptions - or your complete project so somebody else can try to build your EXE…
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • Labview crashed when saving vi and now cannot open VI libray

    Hi
    I am using LabVIEW 7.1.
    I am developing a moderately large application.  I Just saved my main VI and LabVIEW crashed for some reason.
    My vi library will now not open.  When I try to open the library I get the error message: "an error occured when listing the contents of (my directory/myvi.library)".
    Has anybody ever had this problem and if so does anybody know how I can recover my vi library?
    I have just lost about 2 days work so if anybody has any ideas I would be most grateful.
    I hope it is not a fatal problem - I cannot even show the vi's in the vi libray using windows explorer.
    Many thanks
    Ashley

    It looks like you've learned the hard way why you should not use .llb's
    during development. If a single VI in the library get's corrupted, the
    entire library is bad. This is why during development, you're much
    better off keeping everything in an organized directory structure. This
    way, a crash like you had would only affect those VI's that had not yet
    ben saved.
    I've heard rumors that NI has an internal untility that might be able to recover the library. I'd try contacting support directly to see if they can help.
    Good Luck
    Ed
    Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
    Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

Maybe you are looking for