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

WS2812B (NeoPixel) Notify Sync loss #13563

Closed
IamPete1 opened this issue Feb 13, 2020 · 3 comments · Fixed by #13606
Closed

WS2812B (NeoPixel) Notify Sync loss #13563

IamPete1 opened this issue Feb 13, 2020 · 3 comments · Fixed by #13606

Comments

@IamPete1
Copy link
Member

IamPete1 commented Feb 13, 2020

NeoPixels sometimes get out of sync with other notify LED's. They look to sometimes not get the correct command but will re-sync later. This seems to be related to IO load, it is reported to get worse when more serial ports are used. More info here:

https://discuss.ardupilot.org/t/ws2812b-neopixel-integration/48580/56?u=iampete
https://drive.google.com/file/d/18cYoKydri3AWCNSzsWD8SwTqXV0C41gy/view?usp=drivesdk
https://discuss.ardupilot.org/t/ws2812b-neopixel-integration/48580/74?u=iampete

@MallikarjunSE
Copy link
Contributor

Hey @IamPete1
I'm using Pixhawk 1 with fmuv2 firmware. My board is 1MB flash one. If you insist, I can try on CubeBlack or CubeOrange.
https://drive.google.com/open?id=12DvWVjWsykdbETWoXRXrgslGnfiLS377

@MallikarjunSE
Copy link
Contributor

If possible we should add NTF_NEO_LEN to upcoming version of Arducopter. This is only available in AC4.0.3dev

@Another-Taipan
Copy link

I am using AP ver 4.0.3-dev on a Pixhawk 1 with fmuv3 firmware (a Pixhawk 2.4.8 with 2MB flash) and experience this same issue.

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

Successfully merging a pull request may close this issue.

3 participants