Searching for a minimum doesn't work

[altenbach]

Please attach the latest code (without event). Most of it is obscured in your picture.

[JÞB]

Create an indicator on the equals ouput The Probes Should show the same value most of the time while running!  

What did I Say!:

Lets look:

• The xyz data is dequeued and processed and the result placed on the SR
• a simple calc finds the value for probe 9
• The loop iterates and while waiting for new data.... which won't be there for 500 ms - the value for probe 10 is calculated

To put it simply: you proved conclusively that the passed to the output SR of one iteration it the value on the input SR of the next iteration Hey, isn't that how it is supposed to work?

[Pavel_47]

---

@JÞB wrote:

Create an indicator on the equals ouput The Probes Should show the same value most of the time while running!  

What did I Say!:

Lets look:

• The xyz data is dequeued and processed and the result placed on the SR
• a simple calc finds the value for probe 9
• The loop iterates and while waiting for new data.... which won't be there for 500 ms - the value for probe 10 is calculated

To put it simply: you proved conclusively that the passed to the output SR of one iteration it the value on the input SR of the next iteration Hey, isn't that how it is supposed to work?

---

My consideration is as follows: the data that is going to output SR (right side) is actual iteration data, the data that is processed, whereas the data coming from input (left side) SR is data from previous iteration ... so these 2 values cannot be the same, isnt it ? But they are the same.

Well it seems I've found the block that do the job: time derivative.

But in anyway - is it possible in somehow to calculate incoming slope using ordinary staff (e.g. shift register) ?

Regards.

P.S. Altenbach, here is actual VI

[JÞB]

Pavel,

In your previous post :  Lets assume i=n  Probe 10 is updated with the new data at the beginning of iteration n whereas probe 9 cannot be updated until new data becomes available (500mSec after the iterartion start) so probe 9 shows a value from i=n-1 for most of the time the loop is iterating.  As soon as probe 9 is updated the loop iterates again and probe 10 is nearly instantly updated again.  Thats why you see the same value in the probe watch window.

Turn on execution hightlighting to see what I mean or watch the Jing above

[Pavel_47]

Clear.

Thanks Jeff.

[Pavel_47]

---

@JÞB wrote:

Pavel,

In your previous post :  Lets assume i=n  Probe 10 is updated with the new data at the beginning of iteration n whereas probe 9 cannot be updated until new data becomes available (500mSec after the iterartion start) so probe 9 shows a value from i=n-1 for most of the time the loop is iterating.  As soon as probe 9 is updated the loop iterates again and probe 10 is nearly instantly updated again.  Thats why you see the same value in the probe watch window.

Turn on execution hightlighting to see what I mean or watch the Jing above

---

Jeff,

Finally I've found a solution that works ... I mean find extremum "min" and keep it until next iteration of the external loop. Here it is: