Closed gaitskell closed 9 years ago
Ok - so we figured it out by trial and error. I2C requires a write THROTTLE 0 for safety before a write THROTTLE 50 (finite speed). And you have to write <= 0.5 secs to avoid safety shutdown (which is a good feature). We filmed a video of the basic logic of operation and will post it on YouTube. Obviously, it would be great to get the online docs to include these aspects of I2C operation.
The manual doesn't explain what the red and blue LED's indicate on the integrated BlueESC. Also what does it mean when it beeps every few seconds?
I am able to read I2C data from the BlueESC but am unable to get prop spinning when writing I2C. Do you have any debug suggestions? Do you have to use PWM stop signal to activate motor, prior to being able to use I2C? I assume not? Do you have some I2C Python SBUS examples you could post to make sure I'm using your desired conventions? Thanks Rickg@gaitskell.com