Watchdog Reset Reporting Page #15915
Comments
|
Copter 1fe1e53 WDG: T-2 SL0 FL0 FT0 FA0 FTP0 FLR0 FICSR0 MM0 MC0 I think it watchdogged moments later I've switched to auto Can share logs with EKF_REPLAY enabled. |
|
WD issues from Initialization on 4.1beta, Copter fell out of the sky on board reset after 5 min flight. WD errors are obviously detected ok so is there any way to start making the Quad "YAW KICK" every 2 seconds or something to get the Pilots attention? |
|
@Redshifft what flight controller is this? |
|
Little custom Nano F405 own design. First time it's done this in 60 test flight on 4.1 beta - Fault could be anything from a connection splash to HW/SW |
|
I'm just curious because its the infamous "all zeros" watchdog. Still not got to the bottom of what causes this. H7 flash corruption can, but not on an F405. |
|
I reported it for the reason that it may be possible to add something like I suggested above if detected mid flight. |
|
@andyp1per I got this wrong, somehow after 5min into flight all this watchdog stuff kicked off, not at bootup. I was quite happy until revisited the evidence. |
|
Custom build FC, close to clone of omnibusf4pro with latest arducopter beta release, this same issue happening with older stable releases as well, just hwdef.dat file has been changed and attached below Firmware - ArduCopter v4.1.0-beta3(609a65e) |
|
@rmackay9 don't think it is related to the latest firmware release, I'm getting this issue on stable arducopter-4.0.4 and 4.0.7 releases as well, just wanted a little help to decode what's the source |
|
@Notorious811 is the issue consistently repeatable? |
yes, it is consistently repeatable with both 4.0 and latest 4.1 arducopter versions of firmware |
|
@Notorious811 do you have a real omnibusf4pro you can reproduce it on? If so, please give me info to reproduce, all connected devices, how powered, procedure |
|
@Notorious811 can you provide a log - or just run that |
|
@tridge this issue is not happening on real omnibusf4pro, it is a custom build FC, close to omnibusf4pro clone just with different sensors, this issue is happening every time after few seconds since powering on the board, it is most probably some design fault from our end but we finding it very difficult to debug, this issue keeps arising even with a minimum hwdef.dat configurations attached below which suggest something we must be doing wrong with setting up components around the MCU. |
|
@peterbarker i have multiple logs but as mentioned here https://ardupilot.org/copter/docs/common-watchdog.html#determining-that-a-watchdog-reset-occurred, in my case none of the logs have this info within MSG messages about watchdog reset event, still i'm attaching some of the recent logs-
i also tried that but i don't have all the info in proper format about FA, ICSR etc, that's why this is all the data i able to decode using the WDG message in image |
|
I've got a bunch of watchdog messages right after landing, all of them were the same: board: omnibusf4pro arm switch was still on and dataflash log was being recorded |
can you please post the bin logs? There should be 2 logs, one from while it was flying, and a 2nd after the watchdog |
attached are 2 log files from that event |
|
Matek H743-WING v2, brand new. Set up the board, works fine until I arm the plane. Board immediately reboots when I arm. Used STMcube programmer to completely wipe the board several times, same issue. Can someone help me with this issue? 10/22/2021 1:30:11 PM : u-blox 1 HW: 00070000 SW: 1.00 (59842) InternalError 0x800 |
|
I use ArduPlane v 4.1.5 with pixhawk (fmuv3) and I add a serial external AHRS. if I connect the RX pin after awhile, the sensor works correctly https://drive.google.com/file/d/156dnTcbp-Tm21fdm_h0vccJo0xr5-keB/view?usp=sharing |
|
I have a Aurelia X8 Standard. After it's first flight, I get the following messages: I don't have any logs. |
|
I have resolved it. Kindly share your query to [email protected] |
This page is for anyone to report a WatchDog reset ("WDG:" in GCS or DataFlash messages). This allows the Dev team to be alerted, and to investigate as soon as possible.
Please enter the firmware used, vehicle type, and the WDG message. If you have a log, please retain it for 30 days in case a Developer would like to examine it.
Note: follow up timing on a new issue will depend on many factors, so some may not be addressed immediately.
The text was updated successfully, but these errors were encountered: