-
Notifications
You must be signed in to change notification settings - Fork 17k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal Error Reporting Page #15916
Comments
I receive Internal Error 0x1000. Pixhawk1 4.0.5 Stable Firmware Build. HexaCopter. |
When did this happen? Close to boot time? After doing something with the device (e.g. flashing a bootloader)? Just after upgrading to 4.0.5? |
Internal Error message: PREARM: INTERNAL ERRORS (0x4000) Prearm error log: https://www.dropbox.com/s/qnyhvh19c59f4rf/2020-12-09%2009-16-03.bin?dl=0 After I cycled the power I was able to arm, but the plane crashed during takeoff. It banked to the left and crashed. Not sure if it is related to the error but it would be great to find out what caused the crash. Crash log: https://www.dropbox.com/s/i862unbg7bw45bi/2020-12-09%2009-21-51.bin?dl=0 Thanks |
Attempting to re-arm after landing a TVBS using MatekH743 arming was prevented by an internal error.....it has IMU0 disabled since the ICM20602 drifts over time...only IMU1 is used.... PreArm:INTERNAL ERRORS 0X1000000 L:160 IMU_RESET |
@peterbarker @rmackay9 @tridge User reported that he had flown master on this particular setup with no issues prior to loading 4.0.6. User setup details: Log files after the watchdog reset are here. ELF and object dump for latest log is in the same link. The previous log used the same branch built on an older compiler version and I didn't keep the elf or object dump. Here is the decoded WDOG msg and here is the portion of code the Fault address points to For the second watchdog reset, here is the WDOG message decoded The HEX value is 0x810ba5f and the section of code is below if (port_irq_enabled(sts)) { |
I reported a internalerror 0x800 incident at https://discuss.ardupilot.org/t/arduplane-4-0-9-froze-in-the-middle-of-flight/69140/2 firmware used: arduplane 4.0.9 stable, Could you investigate this? logs and videos in the forum |
Hi, I (seems randomly but I'm not sure) often got Internal Error 0x1000000 (IMU_RESET). I use a Matek H743 FC in a Tricopter Frame. This started to happen in Arducopter 4.1. Never got this before in 4.0.6 (I migrated to 4.1 based on Matek Support advice as I got lot of ACCELS Inconsistent and Gyro Health problems...).
|
The combination of ArduPlane 4.1 DEV on a H743-Wing is definitely not ok ... I am currently building a plane with this combination. There are the following problems: The setup goes corrupt after a reboot. There are currently 98 backup files (STRG0.bak - STR98.bak) in the APM/STRG_BAK directory of the SD card. Here probably a copy was inserted, in order to find the problem. When trying to arm via MP (Data / Actions / Arm/Disarm) there is immediately an error: "PreArm: Internal errors 0x800000I:57 stack_ovrflw". You can force arming here, but not disarming anymore ... I have attached the last 5 backup files. |
Rover 4.1.0-dev "latest" on Matek H743
|
FIX IS IN MASTER Copter master 1fe1e53 STABILIZE> log list STABILIZE> log erase looks like storage thread stack overflow when deleting the logs on sdcard: ThreadsV2 |
Hi guys, I updated a qplane with ArduPlane V4.1.0dev (31c889f) - I was with 4.0.8 and after that - I'm running on a bbbmini - beaglebone green + bbbmini cape - I got my linux with more than 16.8 of load average and with 100% of cpu and memory usage. I don't know if the load is caused by this imu_reset error or the error is caused by the high consuption. |
Its not the storage thread its the log_io thread |
thanks Andy, I've opened a PR to fix it |
@tridge did you have a callpath in mind when you thought increasing the stack size might be the solution to this problem? |
We believe this is failure to honour the sd-card-slowdown parameter. A patch is being tested. |
This was fixed with: |
PreArm: Internal errors 0x800000 l:57 stack_ovrflw if set VTX_ENABLE 1
VTX settings (TBS Unify Pro 5.8G HV - Race V2): |
using an early pixhawk 1, delta wing, latest pixhawk 1M firmware, I also get: Pre|Arm: internal error 0x3000 and can't arm. |
Matek f405wse (MATEK F405 WING firmware), arducopter v4.1.0-dev. After arming and disarming quadcopter will not arm again, mission planner shows 0x100000 l:868 (flow_of_control) error. After rebooting quad will fly again one time, and fall back to that error again after disarming. Update: after reading some posts here, I tried removing SD card and disabled logging completely: and it worked! I am now able to disarm and re-arm my quad, and get no error messages. But what to do with logging? |
Mamba f405 mk2 ARDU 4.1 beta 3
This is after i'm run save all logs from spi flash |
I have had a constraining nan internal error on Copter 4.1.beta3 line number 234. During log download over USB, whole system seems to lock up for 1 second in every five and you end up with lots of empty log files on the SD. Sounds the same as #15916 (comment) . Some greping for constrains on that line suggest the internal error is a symptom of the system locking up and not the root cause. |
Matek H743-Wing Git HEAD detached at 3582b69 The flight controller restarted in the air, the aircraft landed in an emergency, and the flight controller restarted repeatedly after landing. After the power is off, the flight control cannot be started, and it stops at calibrating the barometer. It can only be started by refreshing the firmware with BL using STM32CubeProgrammer, help, please! |
Hi The error happend after 131min in the air, while performing AUTO mission. Attached is a screenshot of the error in MP and a Tlog file (incident at 91%) note: Internal error and Failsafe could not be found on the Internal SD log file |
@geoffreybainathsah, this is most likely a hardware error because we have seen quite a few reports recently about this board and this error. We've reported it to Mateksys but it is really up to them whether they do about it. Here is a topic in the discuss forums about this: https://discuss.ardupilot.org/t/prearm-internal-errors-0x1000000-l-168-imu-reset/71658 |
18.07.2021 13:12:55 : PreArm: Internal errors 0x400 l:234 cnstring_nan After compas/mot calibration.. 4.1 have many problems with ineternal errors - any fixes? Maybe in 4.1 we have very bad optimisations when many threads cant working good with proper latency and maybe some irq's lost or have bad priority - i'm think this is main problem in 4.1 with many internal errors. |
Pixhawk 4 running Copter V4.1.1 (01d1aa1), got error Additionally, during the second autonomous flight of the day (log 58) the tracking started going very poorly, ended up needing to recover in STAB mode (never had this issue before). Vehicle has over 100 flights (about 24 h flight time) with no previous issue. Logs for today (*.BIN and tlogs), plus some quick flight notes and a photo of the UAV (12" props) can be found here. I have all the *.BIN logs from previous flights so can provide those as required. Thanks! |
@AndersonRayner, the "256" means that it must be this line that is producing the error. Is it possible that one of the COMPASS_ORIENT or AHRS_ORIENT parameters has been set to CUSTOM? I'm not sure of the exact issue but I think it is related to this. |
@rmackay9 - Yes - I have COMPASS_ORIENT set to CUSTOM (100) and COMPASS_CUS_YAW set to -4 (in degrees, as per the parameter description field in Mission Planner). I have just (as a sanity check) converted my value over to radians and the error persists (even through a full power cycle). Setting the COMPASS_ORIENT back to 0 appears to have fixed the problem, however I can't flight test it (to be sure) for a couple of days. |
@AndersonRayner Looks like you have a UAVCAN compass, custom rotations do not work for UAVCAN if I recall correctly. Something that #19164 will fix. |
@IamPete1 - You are correct, I have a mag in the Here+ puck which is connected via CAN. I'll re-mount my compass a little more carefully so I don't need the custom corrections for now, then do the fine tuning once the PR goes through. Thanks for the quick responses! |
I'm getting an "Internal Errors 0x8000" on my Zealot H743 running ArduPlane 4.2.3 stable. This is happening on the bench (disarmed no GPS fix), so I'm not sure I have a log. I guess this means "Main loop stuck". |
@timtuxworth you can get a log by setting LOG_DISARMED = 1 |
Thanks Henry - ok enabled. Of course it doesn't happen on the next reboot. But I'll leave it on for a while and hope it pops up again. |
Recieved the following on a 3dr solo: 9/2/2022 2:26:45 PM : PreArm: Internal errors (0x800) |
Currently having an issue with an internal error message on a Arduplane 4.2.2 ( 693c9d9 ) system running on a Cube orange on a ADS-B standard Carrier Board from cubepilot. Anybody else having a similar issue at the moment ? Or having an idea how to track the cause of it ? One more thing we saw is that the raw_temp output of this cube does not show 0.0 all the time, but not sure if it is related tot this error message. |
Please provide a log if possible. Regarding |
First of all thanks for the fast reply and your time. Log of the same error: https://www.dropbox.com/s/1izax4zvzdlh4ev/Upload_00000113.BIN?dl=0 Regarding Mission Planner, we will update it good to know the reason for the raw_temp. |
I continue to see Internal Errors 8000 while downloading logs on the QioTek Zealot H743. Because I am not armed I don't have a log. I tried turning on log while disarmed and I don't think I have seen the error when I do that. |
I built an X8 Quad with Arducopter 4.2.3 |
Matek F743 Slim.
These lasst messages (on top) are constantly repeated. Looking at this:
So it could be |
Hi, I experienced an inflight error upon transiting from FBWA to QLOITER which gave an “internal error 400” message and let to loss of control of the plane with minimal damage. After disarming, the warning “Prearm : Internal errors 0x400” continued showing until power cycling the aircraft which seemed to fix the issue. Any help would be greatly appreciated |
Just got this with a 4.5.0 test build - as usual while downloading logs. Luckily I had log_disarm on for something else. |
Another one - happened multiple (many, many) times, again while downloading some larger logs. This is the log of the download. https://www.dropbox.com/s/hbi55d3n1pfhel3/log_193_2023-6-17-17-12-56.bin?dl=0 |
After a flight of about 3 minutes I get this message 'Internal error 0x1000000' After receiving the message, the drone enters FAIL SAFE and I use a cube blue but there is a version of an cube orange on it Platform [ ] Copter Airframe type Hardware type |
This page is for anyone to report an Internal Error ("Internal Error:" 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 Internal Error 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 list of internal error numbers and meaning can be found here.
The text was updated successfully, but these errors were encountered: