Hi all,
Been wondering if it I have a problem, or there's a bug in the ESC calibration mode.
Been running a pixfalcon for a while since 3.3.0 and recently came to do a rebuild / update to tidy some wiring and software updates to arducopter, OSD and crossfire. Went all ok, upgraded the BEC to a 20A CC PRO (set to 5.1v), and decided to do all the calibrations again, just for maintenance. Everything went ok...except for ESC calibration.
My normal process is the "all at once, two power cycles at full throttle" method, and indeed, all 4 Flame 80's signalled the end points had been set. Now normally, I blip the throttle a few times, just to make sure the ESC"s are indeed firing up at the same time. Worked before after all.
But not this time. Powered up, and all motors started at the same time...then after a split second, refused to respond to throttle commands. Worse still - after about 10 seconds, all motors wind up to what looks like full power. Only way to break in is the safety switch or the batter unplug.
Thinking this was a fault or an issue with the ESC's (the pixfalcon only has signal on the motor out ports, and since the Flame 80's need 5V & GND I needed to plug these into the 5V BEC), I plugged in a spare Pixhawk, since there would be 5V on the servo rail. Same issue - enter ESC calibration mode, do the end points successfully, spools the motors, and...locked out again. The motors seem to be working normally in normal mode though?
Just to be doubly sure, I connected the 4 ESC"s direct to the Crossfire cutting out the pixhawk completely, and did the end point calibrations...and it worked perfectly.
Did the ESC calibration mode get changed in 3.3.2? Why am I lose motor control in ESC calibration mode I'm kinda scared to put it back in the air, in case there's a sudden full throttle lock out incident.
Replies