Simple Math VI crashes LabVIEW 2009 SP1

Hi,
We previously filed a related issue, (ref #: 7302858). The last problem was resolved by
Andy Hertzka from NI re-compiled the VI and send it back to us. That re-compilation solved the LabVIEW crashing.
However, the interesting crash happens again.
I attached a working VI before the change and a non working VI after the change and save. All the change I applied to the VI is
1. Add the "Word bits" as a connector on the diagram
2. Save it Then the VI begin to crash LabVIEW 2009 SP1.
Before the change, the VI was functioning all right.
Any idea why this might be happening? Can you try to recompile the non_working version and send it back to me for a try?
Thanks,
Tian
Attachments:
Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB
Working_B4Change_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB

Tian,
Like Andy I was unable to see why this code is unstable on your machine. I am able to run the code fine on my computer without any problems. Looking at the code on the block diagram I do not see any major "crash worthy" issues with it.
I have resaved the VIs like Andy had in order to fix your issue. By the way what OS are you using, windows 7? It might be helpful to save the log file for the LabVIEW crash. You should get this option when LabVIEW is restarted.
<Joel Khan | Applications Engineering | National Instruments | Rice University BSEE>
Attachments:
Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB
Working_B4Change_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB

Similar Messages

Labview 2009 SP1 - Create exe option does not appear

Hello everyone,
I'm using Labview 2009 SP1 and I want to create a simple exe file (to run in the same computer that has labview or in any other computer with the appropiate labview run time engine).
I create a project with project explorer with the appropiate VI, everything OK for the moment, but when I right click on the menu "Build Specifications" of the project explorer I only have the options New and Help. If I click on New I only have "Source Distribution" and "Web Service (RESTful)" I would like to see the option Application and be able to create the EXE file.
Anyone knows how can i create simple EXE files or make the option "Application" to be visible?
Thanks for advance!
Much thanks for your time and dedication!

I guess you did not install the LabVIEW Application builder when you installed LabVIEW. When you do, it will allow you to create the exe and installer (You must be having a valid licence also).
The best solution is the one you find it by yourself

LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows - Supported Features

Hi,
Can some one please point out what features are supported by the LV RTE (Minimum ) [LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows]
1) Is there a limit on the size of the exe which can be run on it?
2) Will this support additional modules like DAQ etc.,? Or do we have to chose the regular installer ( 170 Mb ) for that purpose?
3) If a list of what it does or does not support is available, it would be extremely helpful.
Thanks In advance.
Regards,
Vijay

Anand,
I did go through both the links that you had sent earlier before posting on the forum. For eaxample refer the following link where it says,
http://joule.ni.com/nidu/cds/view/p/lang/en/id/1599
It does not contain the full run-time engine, but will allow some executables to run.
1) What do they mean by 'some' executables. Is there a list of yay's and no's available?
2) Can someone from NI reply to this and shed more knowledge?
Regards,
Vijay

LabVIEW 2009 SP1 - Incorrect icon in connector pane palette

In LabVIEW 2009 SP1 (I don't have 2010 yet to check it) there seems to be a minor bug in the connector pane palette.
One of the connector patters appears twice, but when you select the second one, it shows up as the missing pattern.
I'd post an image, but that function seems to be broken getting through my company's proxy server. So image attached (I hope).
In LabVIEW 2009 SP1 (I don't have 2010 yet to check it) there seems to be a minor bug in the connector pane palette.
One of the connector patterns appears twice, but when you select the second one, it shows up as the missing pattern.
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle
Solved!
Go to Solution.
Attachments:
Connector pane.PNG ‏4 KB

Troy K wrote:
I guess everyone else is using "proper" connector patterns instead of these crazy non-standard ones.
So you must be using crazy non-standard connector panes, or you would not have discovered this bug. Right? Actuall this is a good catch for it to go unnoticed for this long.
- tbob
Inventor of the WORM Global

Labview 2009 SP1 crashes when moving large selection with arrow key

If I select a lot (10 or 15) of Block Diagram components and try to move them some distance with the arrow key, I will frequently get a program crash. Since a smaller number of components seems to crash after a longer travel distance, it looks like some kind of buffer overflow error. I do not see this problem when using the mouse to move selections.
I have checked to be sure I have the latest video driver for my NVIDIA Quatro FX570. I have also tried working with no hardware acceleration and no combined writes. This is happening on Windows XP SP3 with all the current updates.
It has become so bad that I have to do a Save As every fifteen minutes to keep from losing data.
Why don't I use my mouse for all movements? Because it is not as accurate and not so easy to restrict to one dimension of movement. My hand is not as steady as it once was.
I hoping someone will have a suggestion that will clear up this problem.
Solved!
Go to Solution.

As I indicated, I had the same problem with 8.5 and just DID a new installation of Labview 2009.
Since it is possible my three-monitor setup, which obviously requires more video memory, may be at the root of the problem, I am satisfied with the workaround of dragging the objects near their final destination and then using the arrow keys.
Three monitors are ideal for front panel, block diagram and Help/Internet/Probe Window. When I had to work in the field with only one monitor, I felt severely handicapped.
You may consider the matter closed.
Thanks for attempting to duplicate the failure.

Labview 2009 SP1 Installer build help needed

Hello,
First time posting here. I have a rather large project that I recently converted from Labview 7.0 to 9.0. I am able to build an executable and it starts up Ok but I don't know for sure if it works. Since I couldn't build an installer, I copied the folder containing the .exe onto the targeted machine and installed Labview Run-time Engine 2009 SP1. The executable then complains that it needs the full development version to work. I am not too worry about this part at the moment, but if you have any pointers, please go ahead and post them.
Ok, I have gone through a lot of posts on building and installer but it seems the one post that has something similar to what I experienced didn't get an answer. Here's the Build Errors from the pop-up dialog:
CDK_Item_OnDoProperties.vi.ProxyCaller >> CDK_Item_OnDoProperties.vi >> CDK_InstallerConfiguration_Editor.vi >> CDK_Build_Invoke.vi >> CDK_Engine_Main.vi >> CDK_Engine_BuildDevPart.vi >> NI_MDF.lvlib:MDFBuildDevPart_SetOtherProperties.vi
Loading product deployment information
Loading product deployment information
Loading product deployment information
Loading product deployment information
Adding files to installer
*** Error: An internal tool or library returned an error. (Error code -21)
*** End Error Report
*** Error: Windows SDK function returned an error. (Error code -12)
*** End Error Report
The build log file has slightly more info:
    [LOG ON] Mon May 31 20:55:07 2010
<<<MDFConfig_SetDeveloperLanguage>>> Language id: 9
<<<MDFConfig_SetDistributionLanguage>>> Language id: 9
<<<MDFConfig_SetBuildDir>>> Build directory: C:\HardwareTest\XXX\Release\Installers\Lab Test Suite 4.2.9 Installer - XXX
<<<MDFConfig_SetBuildMode>>> Build mode: 1
    [NMDK BEGIN] Mon May 31 20:55:07 2010
     Building developer part
> Adding files to installer
<<<MDFBuildDevPart_SetFileNames>>>
<<<MDFBuildDevPart_SetDefaultInstallDir>>>
<<<MDFBuildDevPart_SetUpgradeInfo>>>
<<<MDFBuildDevPart_SetOtherProperties>>>
>
> **************
> *** Error: An internal tool or library returned an error. (Error code -21)
Error in MDF API function: _MDFBuildDevPart_SetOtherProperties
nmdkSetInformationalProperties returned error code 26024
> *** End Error Report
> **************
>
Adding product dependencies to developer part
>
> **************
> *** Error: Windows SDK function returned an error. (Error code -12)
Closing dist kit
***** About to begin MAXImportConfig:oMAXPartModifications...
No MAX import files specified - nothing to do - returning.
Error in MDF API function: _MDFBuildDevPart_Close
Error in MDF::BuildDeveloperPart::Close.
ERROR: Caught MSI Exception:
<Unable to format error record.>
MSI error code: 6
> *** End Error Report
> **************
>
    [LOG OFF] Mon May 31 20:55:07 2010
    [MDF END] Mon May 31 20:55:07 2010
     Closing MDF.
I realize that I should post my project file but I can't do that until tomorrow. From those 2 errors, can you tell me what the installer builder is looking for? I have gone through all my dependencies and they look Ok at the moment.
Thanks for you time.

Hi Celeb,
I had to help out on another project and finally only getting back to looking at this issue yesterday. As you suggested, I went ahead and created a new project and created new build specifications (exe and installer). I was able to properly build both items but won't be able to check out the executable til later this week.
I noticed one thing about the project that Labview produced after converting the old *.bld file to a project file.  With the converted project, Labview adds unexpected installer destination folders into WindowsFolder in the Installer/Source Files/Destination View. I thought I deleted them before but they seem to make it back (kinda hazy about this at this point).  My actual installer folder should only go into the WindowsVolume folder. Anyway, on the new build spec, since I don't manually add the installer folder into the WindowsFolder, nothing get populated there and the installer is able to build properly. This might have been the cause of my inability to build an installer with the converted project/build specs.
I hope NI could add in more details into the build error messages. As it is, it's really difficult to know why a build failed because there's no details in those messages.
Thanks again,
T.

BSOD with labview 2009 sp1 on windows xp on dual core intel computer stop code F4

I have 14 test stations with the Labview runtime engine installed. These stations run 24 hours a day, or are supposed to, Every week, on average, one of the computers gets a blue screen of death, with a stop code of F4. It seems fairly random which computer it is.
Some other details:
Labview version 2009 sp1, and visa 5.02 installed
The computers are brand new Intel D510MO computers, with wester digital solid state hard drives. (Fanless)
XP service pack 3.
The computers aren't overheating, The ram is good, to power is stable and filtered.
The computers seem to run fine without ni software installed.
The only other thing installed is a serial port driver for a usb serial port converted.
We've caught one blue screen with no Labview executable running.
I've run a batch to turn off all non-essential Labview services, but it still seems to happen.
I've been working this problem for months. Any ideas?

John@ge wrote:
I have 14 test stations with the Labview runtime engine installed. These stations run 24 hours a day, or are supposed to, Every week, on average, one of the computers gets a blue screen of death, with a stop code of F4. It seems fairly random which computer it is.
Some other details:
We've caught one blue screen with no Labview executable running.
I've run a batch to turn off all non-essential Labview services, but it still seems to happen.
I've been working this problem for months. Any ideas?
If I am reading this correctly you have ruled out your LabVIEW program as the cause and you think it is one of the non-essential services. Which ones are still running?
Have you looked in the Windows error logs?
Edit: I forgot to add the link I was going to give you.
=====================
LabVIEW 2012

Image ROI ID number in LabVIEW 2009 SP1?

In LV 8.5 (Vision), multiple ROIs had ID numbers displayed next to them:
Apparently not so anymore in 2009 SP1:
The only difference between the two VIs is that I was using a classic image object and I am now using the modern version;and the image tools window is replaced by the image tools palette associated with the image. There is no image property that I can find to turn the ROI "legends" on or off.
How is the user supposed to know which ROI is which?
Solved!
Go to Solution.

Ooops...: Indeed. I checked my LV 8.5 code (in fact written in LV 6 or whenever the first Image control was released) and I did overlay the ROI numbers myself at that time!
Since I had meanwhile used overlay to get ROI numbers, I just reinvented the wheel...twice.
I still think that would make sense to have this feature by default in the Vision toolkit.
X.

How to activate labview 2009 sp1 after reinstall window?

hi
my camputer was installed labview 2009 and it was activated by the academic license. Currently, i reinstalled the window and i cannot activate the labview 2009. So how can i activate it?

Hi,
In the license manager (Start » National Instruments » License Manager) you should set the correct parameters concerning your license server.
Regards,
Da Helmut

LabVIEW 2009 sp1 not responding / crash

Hi,
I seem to have developed an issue with LabVIEW whereby it freezes at a random point during execution. It is not a case of a VI freezing, rather the LabVIEW application itself ceases to work and needs to closed by task manager. What I have running at the time is a host VI that sends and receives data over a TCP connection to a real-time target on a PXI. The real-time application keeps running after the crash. The host system is also running 3D picture control showing some basic graphics. The whole system is controlled at a top level by a program written in C# over a TCP connection but can run stand alone. When running stand alone the problem does not occur.
The communication between the C# and LabVIEW works fine, yet at a random point during operation, LabVIEW freezes while the C# continues to work. This doesn't seem to correspond to a particular action by the C# program. I guess my question is, is there any likely culprit by which LabVIEW can be crashed by an exernal program where the only communication is via TCP that seems to work fine and where there doesn't appear to be excessive memory or CPU usage?
Cheers.
Solved!
Go to Solution.

Having further investigated it appears to only occur as TCP exchange is taking place and the full LabVIEW application doesn't appear to have crashed, but several VIs hang and can't be closed. There are three total TCP connections running, one that links to the PXI unit, one to the C# application and one from the C# to the visual display VI that is idle when this event occurs. Does anyone know of any reason why a TCP connection can cause LabVIEW to hang? The same connection has worked numerous times before the error occurs. Appears to only happen when the 3D picture control is running.

Startup crash LV 2009 SP1 (bug?)

This has happened a few times, but today was the worst. Frequently I'll get the "LabVIEW encountered an error ... would you like to investigate?". Frequently (at least once a week) LV won't even start up and I get the "LabVIEW encountered an error and needs to shut down". The only workaround from that - until today - was to restart the computer. Today I could not get LV to startup at all. The only way I was able to get LV to startup was, in a moment of serendipity (or dumb luck) I double-clicked my project icon on my desktop. LV started up. I exited LV and tried to restart and it came up fine.
PaulG.
"I enjoy talking to you. Your mind appeals to me. It resembles my own mind except that you happen to be insane." -- George Orwell

Hello PaulG,
What OS are you on? It appears it isn't isolated to a particular VI of yours but just in LabVIEW in general. However, if this crash occurs specifically to a VI, please post it so we can try duplicating your issue.
Also, when prompted "LabVIEW encountered an error.." I would recommend selecting the option that allows you to investigate now which should provide directions to send the error log to National Instruments in which it could be further investigated.
Regards,
Glenn

How to remove sub panel scrollbars with LabVIEW 2009-SP1?

I did a search and found this thread on the subject: http://forums.ni.com/t5/LabVIEW/subpanel-scollbars-in-labview-8-0/m-p/284503/highlight/false#M149983
I double checked that that the horizontal and vertical scrollbars were not selected in the Customize Window Appearance and they were not selected as shown in the image below. You can see the nasty scrollbars in the front panel in the image at the bottom. Of couse, since the code / sw cannot be shown, it has been painted over but you can still see the scrollbars along the frame of the sub-panel.
Customized Window Appearance settings:
Scrollbars are seen at the bottom & right of the sub panel frame
Solved!
Go to Solution.
Attachments:
WIndowAppearance.PNG ‏22 KB
scrollbars.PNG ‏33 KB

Just ran into this myself. (To complicate matters, forgot that one of my debug tools turns the scroll bars back on upon program exit.) "Off While Running" works, too. You can insert this code onto the diagram of any VI that will be called in a subpanel.
Thanks for the tip.
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs

Using RSLinx OPC with Labview 2009 SP1 and Getting Wierd Problem

I have a small test system with 4 analog inputs and 4 analog outputs. Oddly, I can use the Labview Distributed Systems Manager and read the input (level) changes and stroke the analog outputs (valves). However, when I go into a VI, I can get the level readings (only the first time I enter, after that not), but can never stroke the valves. Looking at the shared variable setup in both the project I am using and the Distributed Systems Manager, I have them both set up the same as a PSP with the same OPC reference, although formerly the project used project-attached shared variables.

Using the timed structure set at the same acquisition rate as the OPC interface corrected the problem.

Impossible de demasquer une commande Labview 2009 SP1

Des fois quand on masque une commande il est impossible de la demasquer.
Pour réaliser cette opérationil faut passer par un noeud de propriété.
Pourquoi ?
Résolu Merci

impossible ou pas pratique ?
@+
Tinnitus
CLAD / Labview 2011, Win Xp
Mission d'une semaine- à plusieurs mois laissez moi un MP...
RP et Midi-pyrénées .Km+++ si possibilité de télétravail
Kudos always accepted / Les petits clicks jaunes sont toujours appréciés
Don't forget to valid a good answer / pensez à valider une réponse correcte

Lot of bugs & Crash labview 2012 SP1 in Table control

Run applied vi.
We see lot of bugs in Table control. I fixed some on the right table, but not all.
How fix other?
Thanks in advance, Alex.
Attachments:
NI_BugReport_in_Table.vi ‏30 KB

The attached modification includes a workaround for the ctrl+z bug on the Data Mixer (Not Table). It basically keeps a history of your deleted headers and adds them back in when the user types ctrl+z. Not the most elegant solution, but gives you an example of what you can do to work around it.
You could clean it up by using functional globals instead of shift registers.
www.movimed.com - Custom Imaging Solutions
Attachments:
NI_BugReport_in_Table (Modified).vi ‏49 KB

Simple Math VI crashes LabVIEW 2009 SP1

Similar Messages

Maybe you are looking for