James Jackson

which error?

also, what is the CPU on px4pilot?

Yeah, mixing up F1(NAZE) and F4(REVO) firmware definitely won't work. It'll say the flash was successful, but it won't run.

Another quick diagnostic is to watch `dmesg` while plugging in the flight controller. You should see messages as the device registers itself with the usb drivers. `dmesg -w`

We have two ideas for fixing this: 1. Don't allow more than 10% deviation from desired command (saturate `scale_factor` to 0.9) 2. Don't allow throttle input higher than 0.9 and...

@korken89 That's awesome! Thanks for sharing that. That video spoke mainly about the low-throttle situation. We've typically had issues at high throttle (because we are typically carrying way too much...

Check your email

Hey @cmcquinn, we typically don't "close" an issue until we merge the commit into a release branch (like `rc1.0`. Thanks for putting this together. When we get around to merging...

Multi-i2c just failed after about 2 hours. :( The new driver needs a better recovery scheme. The `unstick` method doesn't seem to be working. I'm open to any ideas. @plusk01...

Cool! You're right, as it currently stands, I don't think we support multiple update rates. We're somewhat limited by the hardware in this respect. Check https://github.com/rosflight/airbourne_f4/blob/master/docs/Revolution%20Schematic.pdf. You'll see things like...