Create a subVI with fgv

[Blokk]

it would be easier to help if you share the actual VI and not a monster pdf screenshot...

[eecharlesbr]

hi Blokk

actually,  I would like  to reduce the maximum time possible, I would like to optimize.

If I get a loop team of 70 or 80 ms I will be very pleased

[Blokk]

Hmm, I do not really see why it will help you, but try the following:

delete the "wait until next ms multiple", and set the timeout value at the Event Structure for 70 msec. What is now your iteration time?

edit: I would not call optimization to run a wreck a little bit faster. What is your actual goal with this?

edit2: what is in the Timeout case of the Event Structure?

[eecharlesbr]

Blokk

it's for you

[Blokk]

Yep, nothing time consuming in the Event Structure timeout case. So what happens, if you delete the "wait until next ms multiple", and set the timeout value of the Event Structure to 70 msec?

But do not forget that, the two other loops have timing too! The next loop below (something with Modbus functions) has a timing 500 msec or above.

The DAQmx loop at the bottom has a timing 100 msec.

So the question is: what do you hope to get by increasing the speed of the top loop??

[eecharlesbr]

yes, I already deleted the 3 "wait until next ms multiple" but the time was the same.
What I hope is that the program solves this boucle de quickest way, and thus can be more useful  for my results.

[Blokk]

"What I hope is that the program solves this boucle de quickest way, and thus can be more useful  for my results."

I guess boucle means loop in French? But I still do not understand: why the results are more useful for you, if the top loop iterates a little bit faster?? What difference it makes?

[eecharlesbr]

Yes that's right. I'm a little confused today, sorry.

if I can reduce this time, the treatment of post test will be more accurate.

but this will is no longer  my job

[Blokk]

Have a look at the "Speed (encoder)" Indicator, its value is updated inside the Modbus loop. If you right click on it, and choose: "Find local variables", LabVIEW will show you 6 items! All these local variables are inside the top loop. So even if you speed up your top loop, it will just read the same value faster, nothing else...

To be honest, I would not base any serious work or experiment on this piece of software...

edit: "if I can reduce this time, the treatment of post test will be more accurate."

It is not really clear, but I think this is not correct. You have 3 loops with different rates, and lots of local variables...

[eecharlesbr]

I'm trying to reduce the amount of local variables in the "code".

but I think it will not change much the time loop