Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LED Strip Non-Functional 2.0.0 #619

Closed
teckel12 opened this issue Dec 22, 2018 · 4 comments
Closed

LED Strip Non-Functional 2.0.0 #619

teckel12 opened this issue Dec 22, 2018 · 4 comments

Comments

@teckel12
Copy link
Contributor

When I go into the LED Strip page, it shows "0 remaining" even though I haven't programmed any LEDs (new FC). Also, there doesn't seem to be any LED config data when I do a dump (2.1 pre-release).

Has LED functionality been totally removed? I know it never really worked well, but at least I could get the LEDs to light and change to red when the battery was low.

@shellixyz
Copy link
Collaborator

It seems to be working fine for me (master branch + OMNIBUS). Maybe the target you're using doesn't have the LED_STRIP feature enabled.

capture d ecran de 2018-12-22 16-07-25

@teckel12
Copy link
Contributor Author

@shellixyz How would the configurator know if my target supports LED strip? My target is new, so 2.0.0 doesn't know it even exists.

I haven't messed with the configurator source, so I really don't know how it operates. But it allows me to activate LED strip and LED strip is on the menu. Maybe this is what happens with a target that the configurator doesn't know about?

I'll close this and take it to Telegram as a question instead of an issue.

@teckel12 teckel12 reopened this Dec 22, 2018
@teckel12
Copy link
Contributor Author

teckel12 commented Dec 22, 2018

The target MATEKF722SE has LED and buzzer enabled, but it seems the configurator doesn't know about them. Not sure what I'm missing here, if it's a configurator issue, target issue, or I'm totally missing something on my end.

@teckel12
Copy link
Contributor Author

Closing this as it's got to be an issue with the target

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants