04-24-2007 06:33 PM
04-24-2007 09:16 PM
Sorry, I have no idea about which indocator you're talking about, but try the following:
Go to "VI properties...execution" and select "clear indicators when called".
(Overall, you have way too many unnecessary sequences and local variables.)
04-25-2007 09:43 AM
04-25-2007 09:53 AM
04-25-2007 09:59 AM
04-25-2007 11:40 AM
@UofH wrote:
but once it starts running, it starts averaging using the previous value as well.
None of the code you show does any "averaging", thus the problem must be withing the qmeasure.dll. Do you know who made it? Is it LabVIEW based?
Attached is a quick try at code cleanup. (LabVIEW 8.2.1) with a few comments. Basically, you seem to use hidden controls for the sole purpose of using local variables. None of these are needed. Let me know if you have any questions.
The way you programmed it leads to "tunnel vision coding": it is impossible to see the big picture because you can only see 5% of the code at any given time.
You should always use the error cluster to determine execution order. You probably als want to stop the loop if an error occurs (not implemented).
04-25-2007 09:45 PM
04-26-2007 12:52 AM
OK, two simple things:
You should initialize your feedback node. Right-click on the initializer terminal on the left and "create constant" ( switched to a shift register for better code clarity, but it's the same thing)
Also the input to clear the chart history needs to be a cluster since you changed the datatype.
The attached should point you in the right direction. I made a few other minor changes, e.g. the "sum" indicator should probably come after the adition of the new element, not before.
04-26-2007 12:56 AM