Hi. My numeric servos where a little noisy and introduced some micro vibration when using super simple gimbal system. http://www.rcgroups.com/forums/showthread.php?t=1793759 tried this to solve it by updating output.ino. seems working pretty well on my configuration. if someone try this, please let me know if it's working too.
#define MMSERVOGIMBAL // Active Output Moving Average Function for Servos Gimbal #define MMSERVOGIMBALVECTORLENGHT 32 // Lenght of Moving Average Vector
PatrikE wrote:I'm not shure but this already exist in config.
Yes _ I think the name is confusing and may not realise.... ... what is mediamobile? perhaps translation issue
I think the tab should be develop d/ included. Is Alex going to add - can you ask him. There are a whole munch of tunable parameters that would make life so much easier. It should be as timecop does it where we can for the good old tarduino 328. lol
Perhaps on small suggestion to improve a little more....?
Consider a two stage filter - first very short or no filter. if the delta from last measure > a value, use new value and reset average to that. Otherwise use the longer term average. This will help with the downside of a filter being slow to react to big change.
So you get to fix the jitter whilst retaining the ability to respond to fast changes. May start to see small step changes in fast movements, but I think that would be better than current jitter.
take current average of last 2-3 readings. Or even just the last one if abs (current average-last average) > a value that works best (maybe 2x higher than average median noise?)
If its higher, then probability is its not jitter and its a fast change so use this reading as the new servo value
That is first stage
If it is lower, then it is probability of little / small movement only, so use second "filter" as you describe - or how MMgimbalsmoothing works. MM method is probably a little.
The only thing to note is if the first stage triggers, you will usually have to reset new average for the second part. or change one of the array values if using MMgimbal method
I loaded 2.2 last night and setup config.h like I have before... and my gimbal went crazy. I could not get it to react to frame movement at all. Eventually, the gimbal stopped working all together and now the servo's don't even budge when I power the board.
Sure hope I didn't fry my servo's I am about to re-load the last working DEV code I had, and see if i can revive the gimbal. Then I'll go back to messing with 2.2pre
subaru4wd wrote:I loaded 2.2 last night and setup config.h like I have before... and my gimbal went crazy. I could not get it to react to frame movement at all. Eventually, the gimbal stopped working all together and now the servo's don't even budge when I power the board.
Sure hope I didn't fry my servo's I am about to re-load the last working DEV code I had, and see if i can revive the gimbal. Then I'll go back to messing with 2.2pre
Hi, I loaded V2.2 pre into my craft and when I powered up the servo's just both moved to one end and jammed (I am using the super simple gimbal, Very cool!) To get over this problem I patched it with the code at the top of the first post on this thread, now it all works again.