ArduPilot / ArduPilot/ardupilot
PreArm: Gyros inconsistent + 4.5.x
- Dominant language
- C++
- Stars
- 15.9k
- Forks
- 21.4k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 119
Description
## Bug report
**Issue details**
_Please describe the problem_
PreArm: Gyros inconsistent + 4.5.x
Seems like when BRD_BOOT_DELAY is not zero, users will get a PreArm: Gyros inconsistent message during Preflight_Reboot_Shutdown action or Hardware power cycle.
https://discuss.ardupilot.org/t/prearm-gyros-inconsistent-4-5-x/118977
when BRD_BOOT_DELAY,0, it will produce the Gyros inconsistent message immediately after arming the copter. (log - 2024-09-13 15-34-48.zip)
**Version**
_What version was the issue encountered with_
Arducopter 4.5.x, logs logged with 4.5.6
**Platform**
[ ] All
[ ] AntennaTracker
[ x ] Copter
[ ] Plane
[ ] Rover
[ ] Submarine
**Airframe type**
_What type of airframe (flying wing, glider, hex, Y6, octa etc)_
FRAME_CLASS,2
FRAME_TYPE,1
Hexa/X
**Hardware type**
_What autopilot hardware was used? (Pixhawk, Cube, Pixracer, Navio2, etc)_
CubeOrange 00420019 3239510C 38363839, Here3, Herelink RC
**Logs**
_Please provide a link to any relevant logs that show the issue_
https://drive.google.com/file/d/1wvSXEC2BY8dfJfs7YDBRjiktyOkskFmV/view?usp=sharing
https://drive.google.com/file/d/15nJ6LtHEnR49G1Oekl4JzEniEnQwRQ70/view?usp=sharing
Contributor guide
Research direction
Start with the two linked logs and the linked forum discussion, comparing the reported behavior with BRD_BOOT_DELAY enabled and set to zero on the stated CubeOrange Copter setup. Done means the erroneous “PreArm: Gyros inconsistent” message no longer appears after reboot, power cycling, or arming under the reported conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot, robotics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100