so there is a boot led on the pixhawk1 (2.4.8) board. on boot, it blinks and then eventually pixhawk boots. However, I have seen some pixhawks boot much faster, and run same ardupilot, like within seconds. Why is there this delay? Can it be reduced?
Also, sometimes if replug very quickly, it doesnt boot and led stops blinking midway. Why does this happen?
Maybe fake pixhawk, fake chip, incorrect chip, old hardware, etc
Define which led do you mean and what is “replug very quickly”?
I first plug lipo
It boots normally and Ardupilot is running
I remove lipo and plug back within 1-2 seconds
The boot error led becomes solid and then I need to repeat this cycle sometimes and then it will boot
My Pixhawk is new and is 2mb and has generic stm chip (have checked by opening)
On other boards, how much time does it take from power up to the Ardupilot boot tone
This a probably a brown-out or smth like this. The Caps kept some charge left and the STM didn’t switch off completely and now hangs somewhere with an error.
I don’t know why you are that much in a hurry? I’ve extra added 3sec additional boot delay to have all peripheral devices booted up before Ardupilot does and have any movement of the vehicle settled.
Ardupilot will not do its initial gyro calibration as long as its moving - maybe this is your problem?
Is it just the FC or the complete drone with ESC which you “reset” by this batterie disconnect - reconnect? As @YupsUAV also said this is an expected behaviour especially in last case.
Happens with usb too.
The resetting is not a big issue as it is very rarely done but the boot tone of Ardupilot and the led color come after 5-6 second with 0 as the value of the boot delay param
You can reboot via software so you won’t have the error described above.
In MissionPlanner you press CTRL+F
Yeah I know this and already said that that process was rare, only needed in mp firmware flashing so now I have shifted to qgc for this and mp never worke
