Well, at least for me it does. I’m a software guy, and I’m sure there are things that every electronics guy with at least 4 brain cells remembers in his sleep that I’ve never heard of. Things like ‘decoupling your power supply’. That one cost me a few days, and a dead chip.
It’s all better now though - I’m learning pretty quickly, and have my new chip on a new board with some support crap, including a little LED display, a button, a knob, and a place to hook servos up. I’ve got it reading my R/C receiver output with ~10 bit resolution, and I can produce the exact same output signals. I wrote code to produce servo outputs in pairs, so each servo costs a max of 1ms. This is handy when you’re controlling 14 of them, and your R/C receiver takes (worst case) 12ms to give you 6 signals.
I’m still over my 25ms budget - Just barely, granted, but enough to be worried. See, servos need to hear from you about 40 times a second to keep them happy, which is 25ms between pulses. My plan for the final version is to output all servo signals more or less at once. It’ll be a bit of work, but I think I can do it.
I also bought some crap at Home Depot and made metal frame with landing gear. I still have to make a place to put the electronics, but I’m not too worried about that. The landing gear have a little spring to them, and the whole thing is screwed together, so it should be much more sturdy than my balsa version.
I have to write a little bit more support code, and then I hook up the gyros again. Yeehaw.