Fonction déconvolution bug labview 2010

Bonjour,
Je voulais tester la foction de déconvolution dans labview 2010. Mais je fais planter labview à chaque fois :
pas d'erreur notifiée, et impossible d'arreter le programme an appuyant sur l'arret d'urgence
=> je suis obligé d'arrêter Labview avec le gestionnaire de tâches.
Je suis sous windows XP 32 bits.
Est-ce que quelqu'un a déjà rencontré ce problème faut-il unstaller qualquechose dans labview???
Merci d'avance
ci joint le programme
Dcharala, Ingénieur en instrumentation, pratiquant de LabVIEW 2010 sur Windows XP.
Résolu !
Accéder à la solution.
Pièces jointes :
Test déconvolution.vi ‏2626 KB

Effectivement.
Cela fonctionne aussi si tu décimes les points du graphe d'origine. (j'ai décimé par 10 pour le test)
Après, les résultats ne sont pas du tout les mêmes, et je ne sais pas ce que tu attends comme résultat.
Cordialement,
Olivier L. | Certified LabVIEW Developer

Similar Messages

LabVIEW 2010 in-placeness crash bug

[cross-posted to LAVA]
I found an odd LabVIEW 2010 bug that will cause a hard crash. The bug appears to be related to how LabVIEW operates on data in-place and some interaction between clusters, arrays, and the Aum Array Elements node. It's hard to describe verbally, so I'll just draw you a picture
LabVIEW 2010 CRASH.vi (16.56K)

No crash on my system: LV2010, W7 64-bit, Pentium E5200
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}

Bug in Formula node under LabVIEW 2010

appendix is my test project.
there is a test.vi in the project. The test.vi contains only a case structure with 5 SAME subdiagrams. Each subdiagram contains a formula mode. The formula code does some calculation with an 2d array of double.
If i run the test.vi under LabVIEW 2010(or SP1), it may cause LabVIEW 2010 corrupt occasionally. If I build application form the test.vi, and run the application ,the application will definitely corrupt.
if I delete one subdiagram of the case structure , the test.vi and the application both run well.
however, the same project works well under LabVIEW 2009.
so is it a bug with LabVIEW 2010?
Attachments:
Test.zip ‏7 KB

'corrupt' means the program exit unexpectedly without any warning or error message. it just disappeared and you can't find it in the 'process' tab of windows task manager after that.
If LabVIEW corrupted, once i reopened it, there may be a error message dialog pop-uped before the LabVIEW interface appeared. The dialog said something wrong with 'undo.cpp'. I zipped the failure long to the appendix. I can't find any other error or warning message from LabVIEW or Windows ( I checked the Windows Event Viewer).
If the built exe corrupted, There isn't any message for LabVIEW or Windows neither.
I tested the project on my own laptop with Windows XP(SP3) Chinese Version and NI PXI-8810 with Windows XP(SP3) English Version which is my target machine.
Appendix also contain a exe build in my laptop. If I run the exe file, once I click the run button , it will corrupt. I wonder if it works the same on your computer.
Thanks for your concern.
Attachments:
lvlog2011-05-13-23-23-35.zip ‏150 KB

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

LabVIEW 2010 SP1: "Controls" pop-up palette "Select a control..." bug?

I'm using LabVIEW 2010 SP1 (32-bit) and I noticed today that I cannot place my custom controls on a VI's front panel when I use the "Select a Control..." option on the "Controls" pop-up palette. I'm wondering if anyone else is having this same problem?
Steps to reproduce the problem:
1) Create a custom control, or download/save the attached custom control "Machine State.ctl" (< a strictly-typed enum control).
2) Open a VI (new or existing).
2.1) If the "Controls" palette is visible (pinned open), close it.
3) Right-click with the mouse on the VI's front panel window to display the "Controls" pop-up palette.
Note: DO NOT use the "Controls" option in the "View" menu here.
Note: DO NOT pin open the Controls pop-up palette at this point.
See my comments below in the "Notes" section.
4) "Controls" palette > "Select a Control..." option
5) Using the "Select the Control to Open" dialog, browse to, select and open the custom control file (e.g., "Machine State.ctl").
At this point the on-screen cursor should show the outline of an instance of the custom control I just opened, but for me that doesn't happen; all I see is the "+" crosshair cursor, and left-clicking with the mouse on the front panel does not place an instance of the custom control on the front panel.
Notes:
* In step 3) above, if I open the VI's "View" menu and select the "Controls" option, or if I pop-up the "Controls" palette and pin the palette to keep it open, I can successfully use the "Select a Control..." option to browse to, select, open, and place an instance of my custom control on the VI's front panel. The failure only occurs when I use the "Select a Control..." option on the pop-up (unpinned) version of the Controls palette.
* I can successfully drag-and-drop an instance of a custom control onto a VI's front panel from a Windows Explorer window, or from the LabVIEW project explorer window.
* The host computer is running Windows 7 Enterprise x64 w/ SP1.
Jim
Attachments:
MachineState.ctl ‏5 KB

Just now I tried creating and using controls on five different computers, each running Windows 7 Enterprise x64 w/ SP1.
On three of the systems the problem did not occur; I was able to place a user-defined control on the front panel using the "Select a control..." option on the controls palette.
On two of the systems the problem still occurs. Upon further investigation, however, I learned that the hard drives in these two systems were cloned from a "master" hard drive image the IT department created. So I'm guessing there's some bad mojo on the master hard drive image, and that's what's caused this problem to show up on these two systems (and others).
So for now, I'm just going to put up with having to use the old "drag-and-drop" method for placing user-defined controls on the VIs. Thanks for your feedback and assistance with this.
Jim

Wire mode bug in LabVIEW 2010?

I had an application written in LabVIEW 2009 for a CFP-2220 that stopped working when it was converted to LabVIEW 2010, and I have tracked down the problem to one thing: the software sets the wire mode of the serial port. Calling this method simply disables the whole program. It works when run from LabVIEW...but if you build a startup application it will not even start. Remove the wire mode call - and voila, the application runs as it should.
So - I can fix the problem easily by not calling the wire mode method, however this is no solution due to the fact that I need to use the RS-422/485 port in 2-wire RS485 mode.
MTO
Solved!
Go to Solution.

It turns out that this is an even stranger problem; the serial port init function will ONLY work in the built application if it originates from the vi.lib\Intsr\serial.llb file. If you do a save as and substitute with original...then you would expect it to still work, it's the same VI, it has just moved...but no (!). Again - there are no warnings, no errors, and everything runs fine in the development environment, but if you deploy and run this application on the cFP-2220 it will only run if the serial port init VI came from that location. Save it to another location (no conflicts caused by this)..build it again, and the application will not start. You can even move the whole serial.llb file to somewhere else and call the serial init file from there - and that's enough to stop it from working.
The reason why I though that I had linked this to the wire mode was the fact that I got everything to run when I used the standard serial port init VI...but if I saved a copy of this to another location and added the wire mode to it it stopped working...so I assumed it was the wire mode, because that was the only thing that had been changed that would logically produce any change...the fact that it was moved should not have any effect....it turns out that was wrong.
I have a few other variations to test (what if I edit the file directly in vi.lib\Instr, will it work then e.g.? That will not be a good solution, but a good thing to test anyway)...
MTO

LabVIEW 2010 App Builder: Registry editor has issue with keys of the same name at the same level in registry tree

This is a bug report for an NI application engineer. Please file a CAR.
In a LabVIEW 2010 project, create a new installer build and go to the Registry editor.
Enter some keys like the following
Click OK to close the installer wizard.
Now reopen the build specification and go to the Registry editor. The registry editor comes up blank and non functional.
I believe the registry entries are still written when the installer executes, but you cannot edit the registry any further in LabVIEW 2010. This was not an issue in LV 2009. The issue seems to stem from having two keys with the same name at the same level in the registry tree (in this case, the two "Test" keys).

Hi sensor_daniel,
This was reported to R&D (#305026) for further investigation.
Thanks for the feedback!
Have a great day,
Chris V
Applications Engineer
National Instruments

LabVIEW 2010 unstable on Windows 7

I am finding that LabVIEW 2010 is fairly unstable on Windows 7 Ultimate system.
LV stopped working several times, LV tells me that it stopped working, looks for a solution and then shuts down. Like just a few minutes ago, shortly after system power up.
Several times it just closes all of the Windows and terminates without any message or error displayed. Didn't even say goodbye.
I have even had one BSOD (which is hard to do on Win 7) almost immediately after an application was built and run. Didn't happen again when app was run again and built again.
I have only observed these problems with LV. All other applications have been running fine over the last month without unusual errors or misbehaver.
The system is only 1 month old. It is fairly clean with minimal software installed.
I don't know how much data on these problems that NI is capturing automatically. I haven't seen my system request permission to send problem reports to NI.
Has anyone else seen similar behavior with LV and Win 7 Ultimate?

I too am extremely (that's a total understatement) displeased with the behavior of Labview 2010 under Windows 7.
I get frequent crashes, some with recovery/log/.error message, some where Labview just exits. One minute I'm editing my code with 7 windows up; the next I'm staring at an empty desktop.
I too have started saving my work every few seconds. It's a royal pain in the ass.
I have turned in NUMEROUS bug reports, including samples of code that cause Labview to crash. MANY of them are related to typedefs. I just found another one and will be turning in that bug report within minutes. In this case I have a typedef (NOT strict) that contains only a combo listbox. If I right-click on the combo listbox, Labview silently exits and does no recovery or logging when started back up.
I have lost SOOOOOO much time trying to create code while fighting numerous Labview 2010 issues. The most egregious (to me) is that I have a control (I *want* it to be a strict typdef) that when I drop it on the Labview block diagram, Labview crashes. Yes this has been reported. I had to change the control from 'strict typedef' to 'control' to use it. The result is that every time I have to modify it (it's a work in progress) I heve to go thru my code and change over 60 occurrences of that control. By hand. If it was a typedef, I would change it ONCE.
I have a customer I'm developing Labview code for; I find it both personally and professionally embarassing to be missing deadlines for delivery, and blaming Labview instead of myself. But I have 3 pages of bug reports online with NI; each one cost me between an hour and 3-4 days of time. Many of them required me to redesign code I'd alrady written to avoid using constructs in Labview that simply don't work.
I'm glad to know I'm not alone - but absolutely dismayed that the code base for Labview 2010 is so buggy under Windows 7; it may be buggy on every platform, but that's all I'm using.
NI tech support has been helpful; but only to a point. They routinely generate correction requests based on my bug reports; not one has resulted in a patch from engineering to date.
I've been a software engineer for over 35 years. This is probably the 2nd worst experience with an IDE that I've had. The first was with a Sun product that was supposed to generate user interfaces; it simply was crap. Labview is dismayingly similar. If I'd elected to write this application in C I'd not only be finished, but it would have taken 6 months less on the calendar. Some of that is due simply to the way you have to construct and enter code in Labview; but in my case, most is due to failures of Labview to work as documentd, or to failures in the Labview documentation to explain what Labview is really doing (yes, I've turned those in too).
Here's an example of a Labview crash: open this VI and right-click on the listbox on the front panel. Make sure you do NOT have any other Labview code open at the time...!
Gary Sloane
SB/US Engineering Inc.
Attachments:
HL2_CAL_DISPLAY.ctl ‏5 KB

Labview 2010 64-bit property node setting

I am trying to set the selection start and selection size for an array in LabVIEW 2010 64-bit on a Windows 7 64-bit machine.
LabVIEW 2010 64-bit crashes and is shut down by Windows.
The call works fine in LabVIEW 2010 32-bit on the same machine.
The computer is a Dell Precision 3500 with 4 GB ECC memory, an Intel Xeon 3530 2.8 GHZ CPU, and a 320GB hard drive. I have LabVIEW 2010 Service Pack 1 installed.
Here is an example of code with just one property node call.
Is this a bug or something weird with my system.
Attachments:
Array Property Node Crash Example.png ‏24 KB

I was able to reproduce the problem, also using LV2010 64-bit on Windows 7 64-bit. I tried various representations of the array data type as well as trying to not include the data type for the control reference as well as trying it via a property node in the calling VI. LabVIEW crashed each time. I'd say it's definitely a bug.

LabVIEW 2010 F2 - Crash - Localization issue ?

Hi fellows !
I am using LabVIEW 2010 F2 (French localized version) and I am facing this strange behavior. Can you confirm that this is a bug and / or this is because I am using a localized version of LabVIEW ?
When using the Modifications:VI property node (CTRL+SHIFT+B) and connecting its output to a case structure everything works fine (it looks like that).
But now if I change the Modifications:VI property to Modifications:Front Panel and let the output of the property node connected to the case structure, LabVIEW crashes or the broken arrow appears.
If I click on the broken arrow or try to save the VI (CTRL+S), I get the following error message :
Fpsane.cpp line 442
Thanks for your help.
Regards,
Da Helmut
Attachments:
err.PNG ‏11 KB
test.png ‏14 KB
test.vi ‏7 KB

Hi,
Thanks for the answer.
There is another bug with LabVIEW 2010 (F4 this time).
To reproduce it you have to create a (strict) type definition that consists of a cluster and put a constant which is linked to this typedef on the BD (just select the .ctl file in the BD) and then delete the type definition from the hard drive.
Close the VI that has the constant in the BD.
Re-open the VI, and in the BD, right click on the cluster constant and select "View as Icon". Now you get LabVIEW crashed. (ok it is useless doing that on a non existing typedef but this is crashing LabVIEW, so I thought this should be reported).
Keep me informed if you have any further informations about that.
Regards,
Da Helmut

LabVIEW 2010 crashes when changing representation of TypeDef

Hello NI,
I have to report a bug
which causes LV 2010 to crash with error in "datamgr.cpp", line 2720.
This crash is reproduceable.I use LabVIEw 2010, 32 bit on Windows 7.
To cause this crash you have to perform the
following steps (I attached a sample VI to reproduce these steps.):
Place a ring control on the FP, change
representation to I32
On the BD, create a property node “Strings
And Values[]”
The datatype of this property is Array of
Cluster with 2 Elems, “String” & “Value”, where “Value” is of type I32
Create a control of this property,
surprisingly the type of Value is “extended”
On the FP, select the cluster inside the
array, click “Customize Control…” from Edit- menu
In the Control- Editor change the DataType
of Value to I32, then exit the Control Editor without saving the control,
but replacing the original cluster
LabVIEW 2010 will crash with the error
message stated above
The problem is to change the
representation of the cluster element, where the cluster is part of a typedef. A
solution is to forbid to call the “Customize”- editor directly from the FP (not
nice) or to forbid to replace the orginal control, instead force the user to
save the altered control to a .ctl (nicer).
This shows a general problem with TypeDefs,
where the array of a not-typedefed cluster is typedefed. This was discussed
earlier with the cursor list of waveform graphs (couldn’t find it anymore, but
read it in this forum) where this problem also can occur. So this is an appeal
to National Instruments to change the TypeDef to the clusters and make arrays
of them.
And, after all, for me it is
unexpected behaviour that a constant / control / indicator, created from a
property (or any terminal / node I can find on the BD) has another datatype
than the original terminal or node.
Greets, Dave
Picture 1: Type of property node
Picture 2: Type of created control
Picture 3: Error message
Greets, Dave
Attachments:
Ring TypeDef Problem.vi ‏66 KB

Hi All,
I am also facing the same bug from the long time which causes loss of data unexpected.Please solve this bug and tell me any way to solve this.I am using Control Type Def in my project.
Thanks
Yogeshwar
Attachments:
error.jpg ‏19 KB

LabVIEW 2010 crash when calling user32.dll

Interesting LabVIEW 2010 "feature" I discovered this morning.
Attached are two identical VIs, one saved in 2010 and one saved in 2009. These VIs were specifically written to demonstrate the bug I stumbled upon this afternoon. Each VI when run should allow you to find a specific program (window) open in Microsoft Windows and bring it to the foreground. It relies on "user32.dll" to perform this operation. It also allows you to specify the calling convention for the function call.
In LV 2009, either calling convention works, without error. However, in LV 2010 the calling convention for the function must be "stdcall (WINAPI)" and not the default "C". If the calling convention is "C" then LabVIEW crashes and closes without warning.
If you happen to have both LV 2009 and LV 2010 on your computer, I would love to hear if this phenomenon is duplicated so that I can pinpoint whether the bug is LV 2010 related or is more specific to my personal setup.
Thanks,
~David
Solved!
Go to Solution.
Attachments:
LV2010 test.vi ‏13 KB
LV2009 test.vi ‏14 KB

221113
Return
CLFN with the wrong calling convention may siliently crash LabVIEW.
LabVIEW 8.5 through 2009 could adjust the calling convention at run time if the user selected the wrong option. In 2010 this no longer happens. More information is found in KnowledgeBase 59KB14WI
Workaround: Use the correct calling convention
Reported Version: 2010 32-bit
Resolved Version: N/A
Added: 07/23/2010
From 2010 release notes.
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

Problème création .exe avec des VIs Expresse (Labview 2010)

Bonjour,
Actuellement en stage j'ai été chargé de créer une interface. Tout c'est parfaitement déroulé jusqu'à ce que je doive créer l'exécutable. En effet l'erreur 1052 se produit lorsque je souhaite créer mon exécutable. D'après ce que j'ai pu lire sur les forums ceci est du au passage de Labview 2009 à Labview 2010. N'ayant que Labview 2010 comment puis-je créer mon exécutable en conservant mes VIs Express ?
Si je ne peux pas conserver mes VIs Express par quoi puis-je les remplacer ?
J'utilise les Vis Express suivant : Ecriture et lecture d'un fichier de mesure et construction d'un tableaux.
Merci d'avance,
J-R
Résolu !
Accéder à la solution.

Bonjour,
Il vaut mieux ne pas utiliser de VIs express pour faire un exécutable.
En ce qui concerne les fonction Ecriture et lecture d'un fichier, tu peux utiliser les fonctions Ecrire dans un fichier au format tableur et Lire un fichier au format tableur. En ce qui concerne la construction d'un tableau, tu peux utiliser la fonction Construire un tableau.
Cordialement.

Labview 2010 beta 3 - Where do I find a copy?

Hi,
I am trying to locate the Labview 2010 beta 3 version for me to try using the latest Licensing tool kit. I d really appreciate it if someone could point it out to me as early as possible.
Appreciate your help in advance.
Vijay.

I got this mail last month
Greetings Beta User,
The LabVIEW 2010 Platform Beta program is now closed. The LabVIEW development team wants to thank you very much for your participation in this beta. Your assistance and feedback is critical for our testing process and enhancing the quality of the LabVIEW product family. We had 198 bug reports filed during the beta program from 547 beta users.
Thank you for all your voluntary efforts in testing LabVIEW 2010! National Instruments has not yet announced the release of LabVIEW 2010 but you can watch for this announcement by going to http://www.ni.com/upgrade.

Plantage LabVIEW 2010 F4

Bonjour à tous,
Je viens ici vous rapporter un petit bug concernant LabVIEW
2010 (F4).
Lors que l’on a utilisé une définition de type stricte
comprenant un cluster (obligatoire) qui contient lui-même différents types de
données (peu importe) pour créer une constante sur un diagramme et que cette
définition a été supprimée, cette
constante est affichée en transparence sur le diagramme (jusque là tout est
normal).
Si par malheur on a l’idée d’effectuer l’opération « Visualiser
en tant qu’icône » sur cette constante de type cluster, on obtient un
plantage de LabVIEW.
Est-ce un bug connu ? A-t-il déjà été rapporté ?
Problème uniquement sur la version française ?
Cordialement,
Da Helmut

Hello,
Ca ne sert strictement à rien, c'est sur mais ce n'est pas normal que ça plante ! Au pire on pourrait obtenir un message d'erreur...
J'ai fait remonter l'info ici et sur le forum Américain. Après, c'est à voir qui veut augmenter ses stats de CAR au support
Cordialement,
Da Helmut

Fonction déconvolution bug labview 2010

Similar Messages

Maybe you are looking for