search

sylvandb / gruvin9x

Automatically exported from code.google.com/p/gruvin9x
0 stars 0 forks source link

Add tmain average to compliment tmain (max) on STAT2 #11

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Knowing the maximum main loop execution time is handy, but knowing a running 
average would be arguably more useful. Let's add that to STAT2.

Original issue reported on code.google.com by gru...@gmail.com on 22 Dec 2010 at 1:04

GoogleCodeExporter commented 8 years ago 
This has been added as at branches/frsky r418. 

Whilst it does show that main loop time is usually well under 10ms (just 
sitting on the STAT2 page), when the 'tmain max' figure is often sitting static 
at 25+ ms, its usefulness as a constant running average is questionable. 
Perhaps it could/should replace that throttle position graph, which I 
personally have no idea of a use for?

Or ... this average figure could be changed to a 'peak hold 10 second then 
rapid decay' style of thing. In other words, shoe the tmain max figure from the 
last 10 seconds. Of course, tmain (max) could also be made to do that.

Original comment by gru...@gmail.com on 22 Dec 2010 at 1:32

GoogleCodeExporter commented 8 years ago 
LOL -- I just discovered that pressing [MENU] on the STAT2 page reset and 
updates the figures! Well, what the heck. The running average isn't doing any 
harm, so far.

Original comment by gru...@gmail.com on 22 Dec 2010 at 1:34

GoogleCodeExporter commented 8 years ago 
Nah ... the average has no use. I'm going to get rid of it. GONE.

Original comment by gru...@gmail.com on 22 Dec 2010 at 1:36