Serious Bugs in LabVIEW 2011

Dear Sir or Madam,
I have been working with LabVIEW for 10 years.
recently I have istalled the last version (LabVIEW 2011) and encountered some fundamental Bugs as bellow:
1-when I want to close LabVIEW 2011 Platform,it taks about 3 sec time to be closed ! while this was not in earlier version such as LabVIEW 9 sp1.
2-In a typical Front Panel,when I press Ctrl+M to chenge to Run mode,it went but after pressing Ctrl+M again,it will not exit from run mode(THIS BUG HAPPEN SOME TIMES NOT ALWAYS) or when I do right-click to view Function pallet or Control pallet,nothing happen!(THIS BUG HAPPEN SOME TIMES NOT ALWAYS).
I will be happy if you tell me what is the reasons and can I trust on LabVIEW 2011 for big projects or It is better for me to used LabVIEW 2009 as the past.
thank you for your kind attention.
Regards,
Ata Rahai,
Specialist Engineer.

Hi
I believe that 2011 is a very stable version (I was beta testing) and in my system the CtrlM works both ways, always.
Taking a few seconds to close is normal since version 8.0, depending on how many services are running. LV does clean up the system.
greetings from the Netherlands

Similar Messages

Serious bug in LabView 8.5 Formula Node

Hello,
Thought I would warn my fellow LabView programmers about a serious error in the Formula Node:
The problem may be encountered by anyone running a non-us LabView installation:
I am located in Norway, and over here we use the comma (,) as the separator in floating point numbers: So, the use 3.14 is written like 3,14.
The problem is that the Formula Node accepts both formats, but only the US Notation is interpreted correctly !
Example:
float64 x1, x2;
x1 = 3.14;    // Interpreted Correctly !
x2 = 3,14;     // Interpreted as 3: One might say this leads to problems.......
Message Edited by geirove on 06-13-2008 06:23 AM
Geir Ove

geirove wrote:
JoeLabView wrote:
Hi Geir,
It is not a bug.  ............
The node does not recognize localized decimal separators."
Of course it is a Bug: **Any** code that **any** compiler does not recognize, should be flagged with an error message ! I have written my share of compilers myself, and they all flag down code that is not accepted as an error.
Failing to do so may cause serious, expensive and very hard to trace errors.
Sorry, but I would expect that the NI team in their 20. year of LabView development is capable of better than this.
Sorry to disappoint you! It's not a bug since that statement is absolutely valid albeit useless in that context.
The Formula Node since LabVIEW 7 supports C syntax except some advanced features such as pointers. In C the comma in expressions is the sequence operator meaning it separates expressions that will be executed from left to right and the last one will actually be the result of the entire sequence expression. This is often used for the initilizer expression inside the for statement, to initilize several variables to a start value.
And the NI team really is a lot better than you think. The online help may be a bit short about the reasons why the comma is not supported as decimal point but there have been many people thinking about this before it was made like that. It was either C syntax support without localized decimal point or some homegrown syntax with localized decimal point and they went for the first.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Serious bugs in the SR400 gated photon counter LabVIEW drivers

Hi
I am developing an application with SR400 and came
across what I think is a bug in the LabVIEW driver. Essentially, none
of the VI's allow you to set the preset counters. For instance, if you
call Read VI and choose mode A, B for preset T, there is no way to
specify preset T, which means that the count period defaults to some
factory default, not a situation you want. This might also explain some
of the timeouts some people are getting to SRQs that come later.
Further,
if you look at the block diagram of Read VI, the line selector string
is set to "CM 0" for two distinct choices of the count mode. This is a
serious bug. I do not know who wrote this driver, but it does seem, at
least to me, that they did a rather shoddy job of it. How this driver even got certification to be posted at IDN is something I cannot explain.
Comments welcome from those that use LabVIEW with SR400 and have used this driver.

Hi. Dwell time of 2ms is good for me. It would be great if you can send me this file to circumvent the 2000points/measurement. Also, If i understand it right, if I set the Gate to CW, then my gate should always be open for the count period, they why do I have to set the gate parameters at all. I want to change the integration time, but for some reason I am not able to change it in your setup 2.VI at all. I made some changes in setup 2.vi. I removed the setting for channel B as I am not going to use it and I integrated the readchannel.vi into this file. I am not sure if I made a mistake in doing this. Now, I am able to write some data to a file, but I not as I want. If it helps, I am uploading my modified VI file and an example data file (Gate A width is 0.992s, Gate A delay and delay step are 0, Gate A mode is CW, Dwell time is 0.002s).
Attachments:
SR400-V.vi.vi ‏125 KB

Bug report: on LabVIEW 2011 SP1 and Windows 8 'Open URL in default browser.vi'

Dear colleagues,
Here is a bug report.
Culprit: 'Open URL in default browser.vi'.
System: Windows 8, Professional. LabVIEW 2011 SP1.
Abnormal behaviour and steps to reproduce:
Above mentioned VI doesn't work when LabVIEW was started with administrator privilegies. And it works as expected when LabVIEW running in normal (non-administrator) mode.
Looking forward to see this fixed.
Best regards,
Igor Titov.
CLD.
=========================
Igor Titov, CLA
WebPager - put LabVIEW front panels into the web page
Labicom.net

Hi Igor,
Unfortunately LabVIEW 2011 SP1 does not support Windows 8. I tested this behavior with LabVIEW 2012 SP1 on Windows 8 and everything worked correctly.
Regards,
Jeff Peacock
Product Support Engineer | LabVIEW R&D | National Instruments

Bug (LabVIEW 2011 sp1 crash)

Bug (LabVIEW 2011 sp1 crash)
1) Open LabVIEW
2) Blank VI
3) Front Panel / View / Class Browser
follow exactly this :
Class Browser / Object library ---> select "LabVIEW Classes" ---> and then clic "Search"
result : The window "Class Browser Search" opens ----> do nothing ... just "Cancel"
back to the window Class Browser ...
Class Browser / Object library ----> now select "DAQmx"
result : in the window Class Browser : Objet library = DAQmx
Class = DAQmx buffer
don't touch anything else (!)
and now clic "Search" ... LV CRASH

When you meet your colleagues, could you ask them, of course when they have time, to create this number.
This will make me happy, and this would be a small reward for this bug report.
Thank you very much in advance ThiCop

Statistics Express Kurtosis inconistency Labview 2011 (Bug 215683)

Hi All,
I am currently working with a data collection program from which I need to output the skew and kurtosis values for an array of 30 data points. As I was already using the Statistics Express VI to calculate mean, s.d. etc. I just added the skew and kurtosis outputs to that VI. I then set up a basic VI to generate a 1D array of random numbers to let me compare the Express VI to the skew and kurtosis VI on the mathematics > probability and stats. palette.
The skew and kurtosis values are inconsistent between the two VIs. If I calculate the skew and kurtosis by hand I can see that the non-express VI appears to be giving the correct answer. I did some digging and found that this has been labelled as bug no. 215683 and is described as having been fixed as part of Labview 2011. I am running Labview 2011 with SP1 so I'm not quite sure why the two VIs are still inconsistent.
I realise that I can simply use the VI which is giving the correct answer but I am curious as to why a bug which should be fixed still appears to be active in my version of Labview.
Any thoughts/ input would be greatly appreciated.
Many thanks in advance

Hi cat,
why don't you get rid of that buggy (as it seems) ExpressVI?
The remaining data (StDev, variance) are provided by just another function from math->statistics palette…
You can also opne the ExpressVI to see, how it calculates those data and why it does produce different results!
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

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

Fail to install LabVIEW 2011

When I tried to install LabVIEW 2011, it failed to install immediately. It gave me the attached message. I already have LabVIEW 2012 installed and I am using window 8 32 bits. Can someone help? Thanks!
Kudos and Accepted as Solution are welcome!
Attachments:
Untitled.png ‏8 KB

Ranjeet_Singh wrote:
Hi friend,
This is posing problem becasue 2012 is already installed in the computer. Two developement software with different versions in same computer is insane.
This is completelly false. The most development systems I've ever had installed at once was 9. Many had different toolkits installed and all worked just fine. This is not always the case but I had no problems.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

LabVIEW 2011 compiled application icon missing

Previously when I built an application the VI Icon would appear in the top right corner exactly the same in the compiled executable as it did in the VI.
Since upgrading to LabVIEW 2011SP1 all I get is a blank/question mark, icon missing indicator.
This happens for all of my compiled applications regardless of what icon I specify, even if I leave it as the default.
VI icon looks like this Application icon looks like this.
Just to be extra clear, there is no problem with how the exe icon appears in windows explorer and shortcuts.
I am ONLY talking about how the front panel icon in the top right corner appears.
The application works, it just looks ugly/unprofessional.
Is this a bug? Do I have something configured incorrectly? Is there a workaround? Has anyone else noticed this?
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.

I tried building on another computer. It works properly.
My usual development machine is running Windows XP SP3.
The other computer I just tried a build on is running Windows 7 and that works fine.
I'm trying a repair of the XP installation now (I'll get back to you in a couple of hours!).
One other possible difference is that on the XP machine I installed the LabVIEW 2011 SP1 f1 patch.
Now I can't remember if I uninstalled it again afterwards. How can you tell if the patch has been applied or not?
I can't remember if I did it on the Windows 7 machine too???
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

Sound and Vibration Spectral map not working in LabVIEW 2011

I recently installed the latest development suite with LabVIEW 2011 and sound and vibration toolkit.
Previously I have successfully used the express function "spectral map" without a speed profile for plot type "frequency-time". With the installation of LV2011 I get an error saying "OA Speed Profile attribute not found" when using the function.
The setup is pretty straight forward with express functions "Simulate Signals", "Spectral Map" and "Color Map" in series.
Is there a bug fix or workaround for this problem?
Attachments:
Spectral Map Error.png ‏30 KB
Spectral Map VI.png ‏36 KB

No, I haven't been able to make the Sound and Vibration Spectral Map express node work in LabVIEW 2011.
A workaround is to not use the express function for a spectral map. You can find the spectral map node under "Sound and Vibration"-"Order Analysis"-"Spectral Map".
I guess the speed profile should be the same for both the express and ordinary function. If so you need to input a cluster of 2 1D arrays, not a waveform. Array1 contains the time in seconds and Array2 the associated speed.

Labview 2011 on Win7, OS causing serial loopback message corruption when clicking on top of windows?

I'm wondering if anyone else has seen problems like this.
I've been tearing my hair out over debugging some code. I have a ftont panel, I'm using some LEDs to send messages through the NI RS232 cable I bought, and have connected with a connector in a loopback fashion.
I've been trying to read the incoming messages from loopback...and based on those, changing indicators and controls on the front panel.
I could not figure why values were changing at strange times....like T's were turning to F's (I'm working with the serial data as boolean arrays).
Well, I was simplifying code, and mostly running right...but every once in awhile, it appeared that my front panel indictors, especially the values I'm changing based on the loopback serial messages would *BLINK*.
I happened to be looking at the Probe Watch window...and I saw where my probes were correctly showing on a couple spots (a left and right indicator) TTTTTTTF and TTTTTTTF......these appear at times to change T's to F's and vice versa.
I then started clicking around...and found this is almost always caused, when I click the mouse on the top of the window...the part that you usually click and drag to move a window around the Windows desktop!!!!!!!!!!!!
I can see this happen when I click on ANY window on the Windows OS desktop!!!!!!
It appears that the OS is messing with me..............?
I'm using Labview 2011, 32-bit on Win7....I believe the OS is 64 bit.
Has anyone seen behavior like this before?
Thanks in advance,
cayenne

Matthew Kelton wrote:
When you are probing, are you looking at the actual spot where you are getting your serial data, or are you looking at it after you've done some processing? I would look at the actual raw data and use a serial port capture utility (there are several free ones on the internet) which will confirm your data is coming in correctly.
What is your CPU running at? If it is pegged at 100%, something has to give.
Is your entire VI running in the UI execution system? If you post your test code, it sounds like it would be easy enough for someone to do a loopback test of their own to confirm similar behavior.
Thanks for the reply. No, CPU isn't being hardly used at all...this is a new lenovo laptop.....high end Dell U2711 monitor...
Task Mgr while Front Panel running:
I'm looking after I've done some processing....
I'm new to working with serial port stuff....I don't have a serial port capture device...?
Thing is...when I run this in debug with breakpoints and stepping through...I don't see this happening. But when running at full speed, and especially when I click on any of the open windows on my desktop, along the top margin where you would click and drag a window around...I can see the serial data in the probe jump...and all data going through the serial port and being displayed on the front panel changing values...
On my VI, I'm actually constructing the byte string...sending it through the serial loopback, and receiving it and acting on it. I can see the data going in is the same as is coming out...it just seems to quickly corrupt and then come back again...like maybe it is getting interrupted by the Win7 OS....?
I can't really post the whole code here...proprietary stuff...that's why in the past, I was posting a separate, simpler vi with only the parts I was having problems with....
I think I have full support with NI...I wonder if I could send them the code to look at, with more confidentiality...?
But again, I can make the problems happen, when it and the probe window is open, in real time...by clicking on windows.
Also, this tends to explain problems I saw earlier...when running slow, all was well , when debugging with break points and stepping through. But at full speed, unexplained...things would start resetting without explanation...and without regularity.
C
I"m not sure what you are asking with "Is your entire VI running in the UI execution system?"....I have the one vi running, and only that vi is running.....

Error -1074397038 occurred at IMAQ Start.vi for 64bit Labview 2011 SP1, Win7

Hello,
I am using a MC1362 camera from Mikrotron with a PCIe1433 framegrabber. I was using it with windows XP, 32 bit, labview 2010 SP1 32 bit, it was working perfectly fine. I just switch to windows 7 with labview 2011 SP1 64bit, and it is not working anymore with my custom routine in labview, though it works with MAX and camera file generator and I use the same camera file.
When I run my routine, I have this error message:
Error -1074397038 occurred at IMAQ Start.vi
Possible reason(s):
NI-IMAQ: The requested serial termination string was not found in the returned buffer.
Then, If I try to run the camera with MAX, it doesn't work anymore, I have to reboot the camera, and put it in the right mode with the Mikrotron control tool to obtain an image.
I have seen similar issue on a Basler camera on the forum, and it has been solved by using a camera file to set the different parameters. There is no camera file complete to set all the parameters of the camera, so I had to program them in serial to drive the camera with my Labview routine.
Could you help me to solve this issue please?
Thanks
Bests
David Dulin

This forum post is already handled --> SR 1154262.
Kind regards,
Corné Westeneng
Applications Engineer
NI-Netherlands

Process Failure when communicating over MODBUS using LabVIEW 2011 and DSC

I'm currently trying to read from a PLC's holding registers using MODBUS/TCP. I've confirmed that the PLC is updating the values and responding to MODBUS communication correctly using a third party program called Modbus Poll. However, when I try to poll the PLC using LabVIEW's shared variable engine, I am unable to read any values from the same addresses that I'm viewing with Modbus Poll.
My setup simply consists of a PC connected directly to the PLC over Ethernet, with no router in between. I am using LabVIEW 2011 SP1 with the DSC module.
I opened the NI Distributed Systems Manager to view the status of all shared variables in the Modbus library that I created and I've noticed that the CommFail bit is permanently set to "true". All other variables with a "read" access mode report "Process Failure". I've tried restarting the process as well as stopping and starting the local variable engine with no success. I've also restarted my computer several times to see if any services were failing, but this does not seem to have fixed the problem.
I finally resorted to monitoring communications over the network card that I have the PLC plugged into via Ethernet using Wireshark and I've found that while Modbus Poll is communicating with the PLC, many MODBUS and TCP packets are sent and received. However, when solely using LabVIEW or the NI DSM to communicate with the PLC, there does not appear to be any communication over the network card.
Something that may be worth noting is that I was able to communicate with the PLC and read values from it with the DSM on just one occasion, when I first figured out which addresses I should be reading from. It all stopped working shortly thereafter. Prior to this, "CommFail" was not usually set to "true" with my current configuration. Thinking that it was my firewall, I have since turned my firewall off, but this seems to have had no effect on the problem either.
Any help on this matter would be appreciated.
Solved!
Go to Solution.

Just a thought but I think the register addresses used by LabVIEW are one off of the actual register #. I was using a CRIO as a modbus IO Server and had to shift the register addresses by 1 to get things to work correctly (can;t recall if it was +1 or -1). This is documented somewhere on ni.com but can;t seem to find it now. But here is another link that may help:
http://zone.ni.com/reference/en-XX/help/371618E-01/lvmve/dsc_modbus_using/
Dan

Hi, I developed a web application using HTML5-Offline Application Cache mechanism. Inspite of deleting the cache as mentioned in the above steps, Firefox still maintains a copy of the page in it's cache. Also, a serious bug is, even though we delete all

== Issue
==
I have a problem with my bookmarks, cookies, history or settings
== Description
==
Hi,
I developed a web application using HTML5-Offline Application Cache mechanism. Inspite of deleting the cache as mentioned in the above steps, Firefox still maintains a copy of the page in it's cache. Also, a serious bug is, even though we delete all temp files used by Firefox, and open the previously cached page, it displays it correctly, but upon refreshing/reloading it again shows the previous version of the page maintained in the cache.
== Troubleshooting information
==
HTML5: Application Caching
.style1 {
font-family: Consolas;
font-size: small;
text-align: left;
margin-left: 80px;
function onCacheChecking(e)
printOutput("CHECKINGContents of the manifest are being checked.", 0);
function onCacheCached(e) {
printOutput("CACHEDAll the resources mentioned in the manifest have been downloaded", 0);
function onCacheNoUpdate(e)
printOutput("NOUPDATEManifest file has not been changed. No updates took place.", 0);
function onCacheUpdateReady(e)
printOutput("UPDATEREADYChanges have been made to manifest file, and were downloaded.", 0);
function onCacheError(e) {
printOutput("ERRORAn error occured while trying to process manifest file.", 0);
function onCacheObselete(e)
printOutput("OBSOLETEEither the manifest file has been deleted or renamed at the source", 0);
function onCacheDownloading(e) {
printOutput("DOWNLOADINGDownloading resources into local cache.", 0);
function onCacheProgress(e) {
printOutput("PROGRESSDownload in process.", 0);
function printOutput(statusMessages, howToTell)
* Outputs information about an event with its description
* @param statusMessages The message string to be displayed that describes the event
* @param howToTell Specifies if the output is to be written onto document(0) or alert(1) or both(2)
try {
if (howToTell == 2) {
document.getElementById("stat").innerHTML += statusMessages;
window.alert(statusMessages);
else if (howToTell == 0) {
document.getElementById("stat").innerHTML += statusMessages;
else if (howToTell == 1) {
window.alert(statusMessages);
catch (IOExceptionOutput) {
window.alert(IOExceptionOutput);
function initiateCaching()
var ONLY_DOC = 0;
var ONLY_ALERT = 1;
var BOTH_DOC_ALERT = 2;
try
if (window.applicationCache)
var appcache = window.applicationCache;
printOutput("BROWSER COMPATIBILITYSUCCESS!! AppCache works on this browser.", 0);
appcache.addEventListener('checking', onCacheChecking, false);
appcache.addEventListener('cached', onCacheCached, false);
appcache.addEventListener('noupdate', onCacheNoUpdate, false);
appcache.addEventListener('downloading', onCacheDownloading, false);
appcache.addEventListener('progress', onCacheProgress, false);
appcache.addEventListener('updateready', onCacheUpdateReady, false);
appcache.addEventListener('error', onCacheError, false);
appcache.addEventListener('obsolete', onCacheObselete, false);
else
document.getElementById("stat").innerHTML = "Failure! I cant work.";
catch (UnknownError)
window.alert('Internet Explorer does not support Application Caching yet.\nPlease run me on Safari or Firefox browsers\n\n');
stat.innerHTML = "Failure! I cant work.";
== Firefox version
==
3.6.3
== Operating system
==
Windows XP
== User Agent
==
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 ( .NET CLR 3.5.30729; .NET4.0E)
== Plugins installed
==
*-Shockwave Flash 10.0 r45
*Default Plug-in
*Adobe PDF Plug-In For Firefox and Netscape "9.3.2"
*NPRuntime Script Plug-in Library for Java(TM) Deploy
*The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
*Google Update
*4.0.50524.0
*Office Live Update v1.4
*NPWLPG
*Windows Presentation Foundation (WPF) plug-in for Mozilla browsers
*Next Generation Java Plug-in 1.6.0_20 for Mozilla browsers
*Npdsplay dll
*DRM Store Netscape Plugin
*DRM Netscape Network Object
Thanks & Regards,
Kandarpa Chandrasekhar Omkar
Software Engineer
Wipro Technologies
Bangalore.
[email protected]
[email protected]

We have had this issue many, many times before including on the latest 3.6 rev. It appears that when the applicationCache has an update triggered by a new manifest file, the browser may still use only its local network cache to check for updates to the files in the manifest, instead of forcing an HTTP request and revalidating both the browser cache and the applicationCache versions of the cached file (seems there is more than one). I have to assume this is a browser bug, as one should not have to frig with server Cache-Control headers and such to get this to work as expected (and even then it still doesn't sometimes).
The only thing that seems to fix the problem is setting network.http.use-cache to false (default is true) in about:config . This helps my case because we only ever run offline (applicationCache driven) apps in the affected browser (our managed mobile apps platform), but it will otherwise slow down your browser experience considerably.

Getting "setup.exe has stopped working" message when trying to install labview 2011 or 2012 on a windows 7 machine

I am getting a "setup.exe has stopped working" message when trying to install labview 2011 or 2012 on a windows 7 machine. I already tried running setup.exe as an administrator with the same results. I have Microsoft .NET Framework 4.5.1 installed on the affected machine. Could this be the cause of this issue? Or does someone know the root cause of such error?
Solved!
Go to Solution.

Hi - are you getting it at the start of installation, during or after 100% progress has finished?
Is it just LabVIEW you're installing, or is it drivers too, in which case, what was the last large package that was installing at the time?
This could be caused by the NVIDIA chipset driver :
https://decibel.ni.com/content/message/46299?tstart=-130
Thanks
Sacha
// it takes almost no time to rate an answer

Serious Bugs in LabVIEW 2011

Similar Messages

Maybe you are looking for