There have been several threads about issues with the BlueESCs initializing properly when started up. Most of these cases have shown the following:
1. No initialization or unpredictable initialization 2. Flashing red LED, usually 1 flash, then 2 flashes, then 3 flashes
I’ve been looking into this issue. We’ve seen this during our own QC testing a few times but those units are never shipped. We test every ESC several times before it leaves our facility, but this issue seems to be appearing in some units in the field.
My best guess at the cause is an overly sensitive “hardware check” procedure that is run in the firmware at boot. It’s possible that the hardware check could fail under certain conditions.
I found a BlueESC here demonstrating this issue and I uploaded firmware with the “hardware check” disabled. The BlueESC then worked!
I’m including the firmware files with the “hardware check” disabled here for anyone who may be having this issue and would like to try these. I’d recommend testing these with caution! This is not the best long-term solution but will work until we can identify exactly what is causing this issue.
Current solution: Flash with firmware that has “hardware check” disabled.
Here are detailed instructions on how to reflash a BlueESC: http://docs.bluerobotics.com/bluesc/#assigning-isup2supc-addresses (just reflash with blueesc_id0.hex if you are using PWM control)
Please post your feedback here!