You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the oreoLEDS are off by default. we need them set by maybe adding a BRD_SOLO option.
there are more things that are specifically solo related, AHRS_Orient to 12 for example... and the solo tunes... some gimbal stuff etc... that may all benefit from this parameter.
Can we also bring these commits from Hugh Eaves into master? He made these modifications to allow custom control of the LEDs. These commits allow the cube to accept the custom commands. He had some nice Python scripts that run on the solo (or maybe APsync) that can change the LEDs to do many other cool things. This doesn't appear to be something that would adversely affect other things. It's a pretty popular mod among the solo users today. https://github.com/hugheaves/ardupilot-solo/commits/solo-led-control
Issue details
ardupilot/libraries/AP_Notify/AP_Notify.h
Line 25 in d170396
the oreoLEDS are off by default. we need them set by maybe adding a BRD_SOLO option.
there are more things that are specifically solo related, AHRS_Orient to 12 for example... and the solo tunes... some gimbal stuff etc... that may all benefit from this parameter.
Version
copter 3.5 / Master (3.6)
Platform
[ ] All
[ ] AntennaTracker
[ X] Copter
[ ] Plane
[ ] Rover
Airframe type
What type of airframe (flying wing, glider, hex, Y6, octa etc)
SOLO
Hardware type
What autopilot hardware was used? (pixhawk, pixracer, PX4FMU etc)
Pixhawk 2.0, 2.1, 2.1 Solo
@Pedals2Paddles @tridge
The text was updated successfully, but these errors were encountered: