how to do every 600 seconds to execute For loop?

[crossrulz]

Luis_AM3C, please tell me the Rube Goldberg is on purpose...

[多多]

HI,

this is my vi

i want to delay 45s to execute for loop at first

then when it finished done

every 600s to execute this for loop

i try some methods,but can't solve 😞

[Luis_AM3C]

Hi crossrulz,

¿Para qué hacerlo fácil si lo podemos hacer difícil?

Google Translator: Why do it easy if you can make it difficult?

Try adding a stop button without abort VI, and tell me which one is the Rube Goldberg Machine? or wanna wait 10 min for stop?

600 = 2*2*2*3*5*5

45 = 3*3*9

GCD = 3*5 = 15 sec

3 cycles = 45 sec

40 cycles = 600 sec

I added the feedback node because I just learn to use them, after reading that work as a delay z ^ -1. And is the correct method instead of a shift register.

Best Regards,

[crossrulz]

---

Luis_AM3C wrote:

Try adding a stop button without abort VI, and tell me which one is the Rube Goldberg Machine? or wanna wait 10 min for stop?

---

Still yours.  Since you are already using an event structure, set the event wait to 600 seconds and add an event for the stop button.  No waiting for the stop at all!

[P@Anand]

---

Luis_AM3C wrote:

I added the feedback node because I just learn to use them, after reading that work as a delay z ^ -1. And is the correct method instead of a shift register.

---

I know there are Pros and Cons between the Shift register and the feedback node but where is given feedback node is correct compared to shift register. You can share the link that would be helpful.

[vt92]

Is this the sequence?

1.) Wait 45 seconds

2.) Start the FOR loop

3.) Iterate the FOR loop every 600 seconds?

or...

1.) Start the FOR loop

2.) i=0, iterate after 45 seconds

3.) i>0, iterate after 600 seconds

[crossrulz]

---

@P Anand wrote:

I know there are Pros and Cons between the Shift register and the feedback node but where is given feedback node is correct compared to shift register. You can share the link that would be helpful.

---

They work the same.  There really is no difference except for the fact that feedback nodes do not have to be on structure edges.  That could clean up some wiring as long as the value of the saved data is not needed outside of the loop.

[Luis_AM3C]

Hi,

---

---

Luis_AM3C wrote:

I added the feedback node because I just learn to use them, after reading that work as a delay z ^ -1. And is the correct method instead of a shift register.

---

I know there are Pros and Cons between the Shift register and the feedback node but where is given feedback node is correct compared to shift register. You can share the link that would be helpful.

---

Before understand feedback node (until yesterday), i always used shift register for use the previous value iteration, wiring the shift register trougth all my cases, today i see that if i only use the previous value at one case i should use feedback node instance of shift register, because is less wire and the diagram is more clear. Because feedback node keep more clear the diagram i call it correct, i dont sure about performace, but is easy to test (i test it, shift register is more fast :S). Thank you for write, i am learning all days a little.

Best Regards,

[P@Anand]

---

@crossrulz wrote:

---

@P Anand wrote:

I know there are Pros and Cons between the Shift register and the feedback node but where is given feedback node is correct compared to shift register. You can share the link that would be helpful.

---

They work the same.  There really is no difference except for the fact that feedback nodes do not have to be on structure edges.  That could clean up some wiring as long as the value of the saved data is not needed outside of the loop.

---

Thanks crossrulz, I already worked with feedback node but he said feedback node is correct thats why asked is there any benchmarks done to prove that. But actually when the number of feedback nodes increases it really messup compared to shift registers.

[altenbach]

There are quite a few difference between feedback nodes and shift registers.

Shift registers:

always need a loop structure

right left side can be resized to get sucessively older history values.

Feedback nodes:

Allow global initialization

have an optional "enable" terminal

Don't need a loop structure (great for action engines)

Allow only one history value (selectable delay, check properties...configuration)