Flowcode Support Board

Hi Steven

I wrote a small App to check delay time and Interrupt time.
The delay is really nice. For 1 Sec I get 1000mSec. Not so good is the Interrupt. I get a lot of different times so I checked 5 times the value.
Each value should be 1000mSec and all together 5000mSec.


regards

Stefan

Hi, Stefan.
I would defiantly not use an interrupt with App Developer.
There is a much more accurate way to obtain time delays.
Take a look at this topic

Hi Martin

Thank you for your info
I just tested both command icon, how exactly these work in the App developer. When I tested the delay, I wanted to know how many milliseconds of deviation it has. When I tested the interrupt, I wanted to know what frequency deviation it has. Since I noticed that the frequency very strongly wobbled with +-20%. This does not make it possible to determine the frequency. This interrupt works well on my computer and otherwise and I need it for the DSP components. These DSP components don't care if the interrupt wobbles . The DSP components still deliver the correct values and filter works correctly (maybe). Only if I control the recording duration and sample rate I get strange result. I hope there is a way to make the interrupt in the App developer stable

regards

Stefan

Hi Stefan,

I've made a note to investigate this, but I have a few other priorities at the moment and so I don't expect this to be fixed soon. So for now you may need to find an alternative way of timing if the interrupt method is not suitable for you.

Hi Steve, Hi Martin

I suspect there is no other way to trigger an interrupt in the App Developer
At the moment I can work with the timer interrupt with a tolerance of + -20%. Thank you that this little problem is on the to do list

regards

Stefan

Hi, Stefan.
Is the Timed Event trigger not suitable for you?
That acts the same as an interrupt as at the pre-set time of 1 second for example, it keeps trigging a call macro, regardless.
Depending if Auto Reset is enabled or not.

Currently the minimum time duration is 1 second.

Hi Martin

I like your idea.

So I included the time event trigger in my test. But that acts the same as an interrupt!
Varible result and instead of 1000 milliseconds sometimes only 578 milliseconds

I am not sure if I did all this test correct. But it cannot be compared with a Swiss watch

regards
Stefan

Hi Stefan,
Try the attached.
The time will count every second from -5
Use a stopwatch and start it as soon as seconds reach 0.
Leave for a period of time, e.g half an hour.
Then compare stop watch with the time elapsed on the display.

Hi Martin

With your program everything works fine, I let it run about 94 minuten (still running) and less than 1 second difference
So I will check whats wrong on my stuff.

regards and thank you

Stefan

Hi, Stefan.
I'm glad my example is working for you.
Accuracy for Timed event component is on the nose.
Thanks for the update.
Do you believe a higher resolution than 1 second would be required?