ArduPilot / ArduPilot/ardupilot
Problem in Copter 4.3.0 with the subsytem led preventing the drone from booting . (luminousbee)
- Dominant language
- C++
- Stars
- 15.9k
- Forks
- 21.4k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 119
Description
## Bug report
**Issue details**
Hello all ardupilot developers 😄 , I would like to report a bug that I found while testing the stock Copter-4.3.0 .
First of all I worked together with @ntamas , which will be useful to explain the problem from a second point of view .
**This bug seems to involve the subsytem led which prevents the drone from booting correctly and preventing us from connecting to it with Mission Planner (both USB and UDP), making any other operation impossible.**
Just today I tested this problem with the stock _Copter 4.3.0-rc1_ .
To recreate the problem , what I did was to use a **lua script that turns on a number of leds set in the script** ( [lua_led_testing.zip](https://github.com/ArduPilot/ardupilot/files/10067883/lua_led_testing.zip)) .
By setting a number of leds to turn on , in the lua script , **equal to or greater than 44** , turning on the drone the script will start correctly , but **it will be impossible to connect to the drone either from USB or UDP** , and also it seems that the drone does not boot correctly . We have tried several times , **but even from the system led rgb , we can see that the drone did not start correctly** .
By setting a number of leds to be turned on in the lua script , **less or equal than 44** , turning on the drone the script will start correctly , and **it will be possible to connect to the drone from USB or UDP** ! And the drone will also pass the boot phase correctly .
**Whatever problem there is, it seems to be triggered when trying to operate with a number of LEDs equal to or greater than 44**
I want to specify that the hwdefs of the drone , have been tested with Copter 4.2.3 and work correctly with all the led subsystem .
It therefore seems that there is sometype of bug or problem with Copter 4.3.0 .
I ask for help from the developers to solve this problem as quickly as possible @andyp1per , @rmackay9 . Thank you all :)
**Version**
Copter-4.3.0-rc1
**Platform**
[ ] All
[ ] AntennaTracker
[X] Copter
[ ] Plane
[ ] Rover
[ ] Submarine
Contributor guide
Research direction
Start by reproducing Copter 4.3.0-rc1 with lua_led_testing.zip, comparing scripts that set 44 LEDs with scripts that set fewer. Read the LED subsystem and the affected hwdefs while checking USB and UDP boot behavior. Done means the drone boots and accepts Mission Planner connections when the script controls 44 or more LEDs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, lua
- Domain
- embedded-iot, robotics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100