Closed ManicMiner-Es closed 3 years ago
This bug is probably fixed in 4.0.5-rc2. Can you please test if it fixes this issue for you?
WDOG.FT (fault type) = 3, which is a hardfault. Noting that the watchdog was added specifically due to the MiniPix, I wouldn't be at all surprised if this is a legitimate board hardware error.
This bug is probably fixed in 4.0.5-rc2. Can you please test if it fixes this issue for you?
I'm on the way .... DEVEL 4.0.5 firmware flashed to several boards; watchdog disabled to be sure about hangs .... up to now, 10h continous running (not flying) with no hungs ... let's wait 20 or 30 more hours ....
WDOG.FT (fault type) = 3
auturgy, please, where did you find this info ?
Sounds like this was resolved.
Issue details Watchdog reset controler during flight condition; disabling watchdog and tested without arming motors, ends in a hanged controller.
When at enough altitude, two logs appear : first one ended at top flight height, and second one starts five second later, and several meters down, until 0m crash
Version Arducopter 4.0.4 & 4.0.3
Platform [ ] All [ ] AntennaTracker [X] Copter [ ] Plane [ ] Rover [ ] Submarine
Airframe type Quad
Hardware type Radiolink Minipix v1.2
Logs first flight, first part first flight, last part
second flight, first part second flight, last part