This is very interesting I always wanted to test I2C and the how-to you wrote is exactly what I wanted to know. If @sim- prefers the MK addressing style then there are no other changes than useful documentation, so please commit to help and tidy-up one issue ;-)
I suppose the documentation should really go in the Wiki. In theory I2C is faster than OneShot125 so people with this capability might want to use it? A new flight board with I2C only would certainly follow if this become popular, as PWM is really legacy if there's a good pure digital alternative?
Unless there are technical issues I really hope I2C development is expanded. Two way communication of any sensor data would also be useful, e.g. RPM and somebody mentioned some ESCs can detect temperature. I'm certainly going to give this a proof of concept.
This is very interesting I always wanted to test I2C and the how-to you wrote is exactly what I wanted to know. If @sim- prefers the MK addressing style then there are no other changes than useful documentation, so please commit to help and tidy-up one issue ;-)
I suppose the documentation should really go in the Wiki. In theory I2C is faster than OneShot125 so people with this capability might want to use it? A new flight board with I2C only would certainly follow if this become popular, as PWM is really legacy if there's a good pure digital alternative?
Unless there are technical issues I really hope I2C development is expanded. Two way communication of any sensor data would also be useful, e.g. RPM and somebody mentioned some ESCs can detect temperature. I'm certainly going to give this a proof of concept.