hegoak

  • *
  • 2
problem with EVO CC3D
« on: January 11, 2016, 11:04:59 am »
I have a problem, the alarm window out these messages:

RC INPUT:CRITICAL

One of the following conditions may be present:

-One or more of the r/c input channel types is not set.

 On the CGS configuration page,make sure all inputs have a type set


- One or more of the r/c input channel types mappings are invalid
- The driver unintialized for one or more of the r/c input channel
- Current flight mode is undefined: this indicates a bug in the code
- Current flight mode set to guidance but flight status flight mode is reported a something
  other than altitude hold
- During update of desired stabilization mode,flight status is reported reported a something
  other than altitude stabilized 1,2,3,4,5 or 6



BOOT FAULT : CRITICAL


- System has failed to boot more than three times: system defaults have been set


SYSTEM CONFIGURATION: CRITICAL

 One of the following conditions may be present:

- you have set up a GPS mode (poshold,RTB) to thr flight mode switch,and you may have
  selected "basic (complementary)" fusion algorithm.

- Select "GPS Navigation (INS13)" in config / attitude tab / paremeters / attitude / estimation algorithim



f5soh

  • *****
  • 4572
    • LibrePilot
Re: problem with EVO CC3D
« Reply #1 on: January 11, 2016, 11:33:19 am »
Hi Hegoak, welcome :)

Double check the flight mode tab, you may remove all Gps modes.
CruizeControl is only allowed with attitude/rattitude, not rate
Rcinput looks normal is your receiver is not powered or inputs not configured.

I remove the duplicate post.

Laurent

Re: problem with EVO CC3D
« Reply #2 on: December 15, 2019, 10:22:00 pm »
BOOT FAULT : CRITICAL


- System has failed to boot more than three times: system defaults have been set

Cómo se corrige eso

Re: problem with EVO CC3D
« Reply #3 on: December 16, 2019, 05:40:04 am »
Where I usually see this is if I make a bad setting that keeps it from booting.

Easy fix is to Erase Settings and start over.

OR - If you know that you changed something and it broke it, then once it boots like this, go and change that setting back to default, and next time it should boot normally.