-
Notifications
You must be signed in to change notification settings - Fork 3
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
feat (driver) implement our own LED driver #141
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, really good :-) Thank you for your extraordinary efforts!
…asumi/TesLight into feat/140-own-led-driver
Tested the current code for 24h now. I assume its stable. So I would say we can merge it after you approved. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. I could not test it atm, I need to get another power supply first...
If this happens in the near future we can also wait😋. Having a second tester would be great. |
!= I get ... :-) |
Alright, then I am going for the merge now😜. The new driver is there🥳. Get ready for crashes and bugs. |
* Add from internal repo * Remove c-style casts * Fix stale LEDs * Minor stuff like comments * Update TesLight.cpp * Small fix
closes #140
closes #98
partially closes #134
Its finally here, our own driver for WS2812(B) LEDs. With that we remove the FastLED dependency and potentially a lot of problems which startet when we included it. The performance with the new driver has roughly doubled while the memory consumption was also slightly reduced. The CPU load also reduced drastically since we are using DMA with the I2S hardware. So far it seems perfectly stable but I am still in the process of testing. There might be smaller improvements to the way how pixels are accessed but this is more about... "making it look nicer" while not changing anything functional.
Also note that this potentially seems to close #66. So if we don't encounter this again I would guess we close it in the future. Alright, I guess all this is pretty good news.