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

Similar Messages

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

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 vi

When using the statistics express vi in LV7.1, I get wrong results for standard deviation. I particular, the VI outputs the mean value instead, but only for certain data sets. Most of the times it works fine. I can not see any problem in this very simple VI. Any ideas?
Thanks
Dirk
Attachments:
statistics_problem.vi ‏565 KB

Hello Dirk,
I think you found a bug on the LabVIEW's statistical functions...
I removed that set of data from the array and tried the normal (not express) statistical functions and they return NaN and for the others it's ok!
See attached code.
Paulo
Attachments:
statistics_problem[1].vi ‏600 KB

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.

How do I get the statistics express to read more than 10 segments when reading from a .lvm

I have tried 2 ways of doing this. I had an for loop set up with a "Read labVIEW Measurement FIle" then a xy chart to plot the 2 measurements vs. each other. The chart works and will plot everything great but the "Statistics" express will only take 10 samples at a time and will keep redoing the statistics for each subsequent segment of 10 samples. I tried to change this to a while loop but then the same thing happens with the stats and the xy chart does not graph. How do I get the stats calculate for the entire file?

Richard,
Thank you for contacting National Instruments. I think I understand what you are looking to do here, but it might be easiest for myself and others to help you more specifically if you post a screenshot of your code, or your actual VI. However, I looked into trying to achieve something similar, and used a loop structure to bring the information in from a file. Then, outside the loop, I used the Statistics Express VI from the Mathematics palette to obtain some statistical values. What type of statistics are you looking to receive from this program?
Jason W.
National Instruments
Applications Engineer

Statistics Express VI - help

Under the help option in the statistica express VI this is given to explain the time between samples (dt)
Time between samples (dt)
—Bases the calculation on the time between samples in
Signals
My design is two micophones and one sound and finding the time delay between the two.
Now does this mean it takes the difference from when one signal starts and the other starts
(say when microphone 1 first picks up a signal and then microphone 2)
Or does it show the time difference between the two signals ?
(as in the delay between the samples)
I'll attach the VI's below to see it that helps makes sense
Solved!
Go to Solution.
Attachments:
VI.zip ‏980 KB

dt is the time spacing between sampled points. In your case, dt=0.001.
If you convert to plain 1D arrays, the sampling information is lost, meaning the cross correlation in in units of the array indices. Given dt, you can calculate the the spacing in seconds from the spacing in index units.
You can also set the dt of the x-axes of the graphs so the display is in seconds.
LabVIEW Champion . Do more with less code and in less time .

I found Error in Statistics Express about the algorithm for mode

LabVIEW 7.1 was used. today I acquired a lot of data and analyzed using Statistics Express in LabVIEW 7.1, whereas the results of mode were not correct because I analyzed the data using both Excel and SPSS. so I think there must be something wrong with Statistics Express in LabVIEW 7.1. Attached is the data which mode is 57.24 by SPSS, but the result of Statistics Express showed the result of 32.608.
will someone please help me?
thanks
Attachments:
data.xls ‏29 KB

Hi,
I agree the 2 places of decimals is a cosmetic property and I have no issue with that....
I have my vi setup such that at one call it gets the mode of distances between points on lines. The second time I call the mode it is to get the mode of distances between another set of points. Two separate arrays in a fairly large program. I've attached a shortened sample hopefully the error still appears. Also I was wrong about wiring the intervals wire, this did not change anything.
If I run the 2nd mode operation on it's own without the previous call it works fine, only when there is a previous mode operation does it fail to "re-initialise" and returns the result of the first mode operation.
The only thing I can think of is that the first set of data has many different distances and gives a clear mode, whereas the second set has values approximately the same, with the odd multiple (ie 20,22,19,41,62,20,21,23). However, going against this is the Express Statistics vi which calculates the correct values in the Express Window (double clicking on it and selecting the statistics) but when wiring these to an indicator the result from the first mode operation is returned.
Any suggestions welcomed.
Kind regards,
Leeser
Attachments:
mode_error_example.vi ‏143 KB

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

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

Print text file with labview 2011 and windows 7

I am having some strange problem, hope someone out there knows the solution.
We have a labview program running under windows xp, the program runs some test and print label from a local label printer. Last week, I have to upgrade the computer to windows 7 and all the sudden the printer will not print any more.
The print vi is very simple. I am using the report function and I am attaching the diagram of that vi below.
If I use windows notepad to open that small text file, I can print fine. This means the printer driver itself is OK. However, if I print the same text file through Labview printing vi, from the printer's task list, I can see it does not recognize the char. From the attached png file, the top one is the task from notepad, it shows 2 pages and the bottom one is from the labview, it becomes 33 pages.
For the printer part, I use Generic / Text Only printer driver which comes from windows itself. And I am aslo attaching a sample of the text file, there are quite a lot of special char, it is for print bar code. When I tried to use labview print text vi to print general text from my computer to a regular printer, the vi works. So it seems Labview print can not handle the special char? Although it worked many years under windows XP in the past.
Welcome to any suggestions!
Thanks
Attachments:
print vi.gif ‏9 KB
labview print bug.png ‏26 KB
SerialLabel.txt ‏1 KB

DGU wrote:
where to check RAW or TEXT? the print report vi only asks for file name and printer name.
When I print from notepad, everything just goes by default. This is a label printer, so I never need to specify printing parameter such as size, orientation, etc in the past
Famous last words go something like this: "...never had to do that before." Maybe you have to do that now. It's worth at least comparing the defaults settings for bothe generic drivers. It could save you a lot of headache if you notice something different.
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.

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

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

Statistics Express Kurtosis inconistency Labview 2011 (Bug 215683)

Similar Messages

Maybe you are looking for