Internal Error Code 0x1000400 Rover 4.1.5

Autonomost · April 29, 2022, 2:53am

Hi all,

I recently saw this error on ArduRover V4.1.5 (3ef2b3f4). Latest stable build.

Viewing the code I see in:

ArduPilot/ardupilot/blob/master/libraries/AP_InternalError/AP_InternalError.h

/*
  AP_InternalError holds information about "should not happen" errors
  that have occured within ArduPilot.  This covers things like code
  paths that should not be crossed or pointers being null when they
  really, really shouldn't be.  It does NOT cover things like losing
  GPS lock at inopportune times - that's just bad luck, not bad
  programming.

  This program is free software: you can redistribute it and/or modify
  it under the terms of the GNU General Public License as published by
  the Free Software Foundation, either version 3 of the License, or
  (at your option) any later version.

  This program is distributed in the hope that it will be useful,
  but WITHOUT ANY WARRANTY; without even the implied warranty of
  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  GNU General Public License for more details.

  You should have received a copy of the GNU General Public License
  along with this program.  If not, see <http://www.gnu.org/licenses/>.

This file has been truncated. show original

This is printed when ardupilot detects an imu reset and a “constraining nan”. @rmackay9 do you have any insight on the constraining nan internal error printout? Or know who would? Any info would be much appreciated.

Also if anyone can point to common causes of the imu reset internal error i’d very much appreciate that information too.

BrunoBagarini · April 30, 2022, 6:48pm

Hello Evan,

Are you experiencing this internal error during vehicle operation?

I always see this constraining nan internal error being triggered after compasses calibration, but have never persisted from reboot so never took care of it. If this error is being triggered after compass calibration for you also, I think it is perfectly fine to operate with it. Maybe some kind of minor bug regarding the sensors calibration.

Autonomost · May 1, 2022, 1:15am

Figured out it was low Vcc to the autopilot.