Capture a portion of FP image

[Kousy]

Attaching data files..

[altenbach]

---

Kousy wrote:
I am attaching the vi and data file to read in. I too thought of using waveform graph.

---

You need to also write the X.offset on the proprty node. See if this helps.

(BTW, the "Show" button should be latch action and the terminal should be inside its event case. I don't understand the reasoning for all your sequence frames.)

Message Edited by altenbach on 09-26-2008 11:45 AM

[Kousy]

---

 Altenbach wrote:

BTW, the "Show" button should be latch action and the terminal should be inside its event case.

---

Yes I can  use latch action button ok. But I don’t understand why the terminal should be inside its event case? & Is there any specific reason? – I should use latch action only. Is this the order (specific) should I use Xscale.offset, Multiplier, Min & then Max.

[altenbach]

I would use the properties in the order given in my example. Have you tried?

Latch action will reset the boolean once it is read by the code as dataflow allows. Placing the terminal inside it's event case ensures that the terminal resets every time the event fires. If you would place the terminal totally outside on the diagram, it will get read once at program start and then never again. If you ever press the button, it will get stuck on the down position for the duration of the program. It does not matter if an event gets fired by it or not.

[Kousy]

I tried with the order you specified, now it is working ok every time, but yet to deploy it in on machine and check out.

This order is more crucial it seems, it is plotting ok even with the chart now.

 Yeah I understand the function of Boolean latching action.  

---

If you ever press the button, it will get stuck on the down position for the duration of the program. It does not matter if an event gets fired by it or not.

---

 If I have used switching operation for the Boolean, then this button position only will get stuck on the down position or it will not fire the value change event at all when its On/Off position is changed. 

Thanks.

[parthabe]

If you use Switching action for a boolean, it ll retain that position even after the code has read its value. We have to reset it by writing False to it.Thats the basic dofference between the Switching & Latching actions for a boolean.

Moreover a Value Change event will get fired for each of the state changes.