Internal errors 0x100000 l:917 flow_of_ctr

ArduCopter Copter 4.2
, , ,
12

I think @rmackay9 and the developers are looking into this at the moment!

13

Thanks guys. I will stay tuned. If additional info/logs etc is necessary I can help

14

I tracked the “SubSys:30 ECode:1”

According to AP_Logger.h subsystem 30 is internal error and 1 means failed to initialize … so not super helpful

enum class LogErrorSubsystem : uint8_t {
MAIN = 1,
RADIO = 2,
COMPASS = 3,
OPTFLOW = 4, // not used
FAILSAFE_RADIO = 5,
FAILSAFE_BATT = 6,
FAILSAFE_GPS = 7, // not used
FAILSAFE_GCS = 8,
FAILSAFE_FENCE = 9,
FLIGHT_MODE = 10,
GPS = 11,
CRASH_CHECK = 12,
FLIP = 13,
AUTOTUNE = 14, // not used
PARACHUTES = 15,
EKFCHECK = 16,
FAILSAFE_EKFINAV = 17,
BARO = 18,
CPU = 19,
FAILSAFE_ADSB = 20,
TERRAIN = 21,
NAVIGATION = 22,
FAILSAFE_TERRAIN = 23,
EKF_PRIMARY = 24,
THRUST_LOSS_CHECK = 25,
FAILSAFE_SENSORS = 26,
FAILSAFE_LEAK = 27,
PILOT_INPUT = 28,
FAILSAFE_VIBE = 29,
INTERNAL_ERROR = 30,
};

// bizarrely this enumeration has lots of duplicate values, offering
// very little in the way of typesafety
enum class LogErrorCode : uint8_t {
// general error codes
ERROR_RESOLVED = 0,
FAILED_TO_INITIALISE = 1,
UNHEALTHY = 4,
// subsystem specific error codes – radio
RADIO_LATE_FRAME = 2,
// subsystem specific error codes – failsafe_thr, batt, gps
FAILSAFE_RESOLVED = 0,
FAILSAFE_OCCURRED = 1,
// subsystem specific error codes – main
MAIN_INS_DELAY = 1,
// subsystem specific error codes – crash checker
CRASH_CHECK_CRASH = 1,
CRASH_CHECK_LOSS_OF_CONTROL = 2,
// subsystem specific error codes – flip
FLIP_ABANDONED = 2,
// subsystem specific error codes – terrain
MISSING_TERRAIN_DATA = 2,
// subsystem specific error codes – navigation
FAILED_TO_SET_DESTINATION = 2,
RESTARTED_RTL = 3,
FAILED_CIRCLE_INIT = 4,
DEST_OUTSIDE_FENCE = 5,
RTL_MISSING_RNGFND = 6,
// subsystem specific error codes – internal_error
INTERNAL_ERRORS_DETECTED = 1,

// parachute failed to deploy because of low altitude or landed
PARACHUTE_TOO_LOW = 2,
PARACHUTE_LANDED = 3,
// EKF check definitions
EKFCHECK_BAD_VARIANCE = 2,
EKFCHECK_VARIANCE_CLEARED = 0,
// Baro specific error codes
BARO_GLITCH = 2,
BAD_DEPTH = 3, // sub-only
// GPS specific error coces
GPS_GLITCH = 2,
};

15

Out of curiosity what does the PM>NLon graph show in the log?

16

Yes but it is 0 the entire time. Also the rest of the PM values don’t seem to change much compared to before or after the error is announced

17

Sorry if I missed it but was there a log attached somewhere?

18

Dear Leanard, sorry for the late reply, I was away for a while.
I worked on this yesterday. I use a modified version of Copter 4.2.3 and some of my code that was running essentially AltHold’s run() was an issue. I was running the althold run from a few versions before and the order in which the functions were called was different.

I updated with the current AltHold code and the error no longer appears. So in my case I was the source of the problem.

19

Thanks for letting us know.

20

I’ve placed links to some alpha testing binaries in this thread that may help resolve these issues.

No pressure of course but if people are happy to help us test these binaries that would be a great help!

21

After testing, version 4.3.3 fixes this problem.

22

Which Parameter you change the rate from 800 to 400?

I have a Matek H743-Slim V3 and I got also:

Arm: Internal errors 0x100000 l:125 flow_of_ctrl

btw can this happen during flight, and if it does it goes to Failsafe or recovers or crashes?

I have built, learning Ardupilot and configuring my X500 quad for a while now and today it showed this error for the 1st time!

I have done a few hovers about 2 ft from the ground been very stable and no visible vibrations so I was planning for tomorrow to be the maiden flight/test/tuning…

Any suggestions?

23

Are you running the latest release?

1 Like
24

SCHED_LOOP_RATE is what I changed.

1 Like
25

You should not have this issue with an H7 processor. At least not with limitef processor power as the main cause.

If it happens during flight it will go into EKF failsafe I beleive. I’ve set my copter to use alt.hold in case of that. Yours will probably land right away.

1 Like
26

I believe so:

ArduCopter V4.3.5 (02ff7ea3)

27

Thank you for the Param.

I just checked it and it is set at 400 already.

28

Doing some investigation on why I show this error only yesterday for the first time after many successful low hovers and never seeing it before and have not changed the firmware of any device lately, I think could be related with the following 2 changes:

The only parameters I had changed the last few days was:
FS_GCS_ENABLE from 0 to 4 (SmartRTL)
FS_THR_ENABLE from 1 to 4 (SmartRTL)

and also assigned Pos_Hold and Smart_RTL to switches Flight modes. During “testing” the switches with the new modes and before arming is when I received the errors on MP. Interesting enough, I just tried it and I could not get the errors today.

Anyway, thank you all for responding and helping with this.

29

Are you able to send a log?

1 Like
30

Sorry for the delay. I will get the log in a couple of days.

31

Sorry I cannot find the log. Maybe I am looking for it the wrong way. I do “Review a Log” then I filter for ERR on the table and look for the Message. I went through all the Dloaded logs and could not find anyone with this error.