SK6822

A WS2813 Clone With Some Shortcomings

The SK6822 is a WS2813 clone with almost the same technical specifications.

Differences

Its input voltage range seems wider (3.3-7.5V) than the original, allowing 3.3 microcontrollers to safely operate them.

Then again, the original WS2813 tolerates 3.3V as well when the distance between first LED and microcontroller is less than 30cm.

When To Use

SK6822 may be an alternative when price matters.

When To Not Use

This is a clone trying to mimick the original WS2813.

While some of the specs seem improved over the original, you pay the price elsewhere:

There are reports about strange timing issues and smaller LED die.

Clones can be perfectly ok but do not always come with the same quality (i.e. smaller LED die = less brightness or issues with the data protocol)

If you don’t want to be a test pilot, choose the WS2813 (if you need redundant data wires) or the cheaper and well proven WS2812B. Both are not much more expensive than the clones anyway.

Datasheet

WS2813 datasheet

Slow Website?

This website is very fast, and pages should appear instantly. If this site is slow for you, then your routing may be messed up, and this issue does not only affect done.land, but potentially a few other websites and downloads as well. Here are simple steps to speed up your Internet experience and fix issues with slow websites and downloads..

Comments

Please do leave comments below. I am using utteran.ce, an open-source and ad-free light-weight commenting system.

Here is how your comments are stored

Whenever you leave a comment, a new github issue is created on your behalf.

  • All comments become trackable issues in the Github Issues section, and I (and you) can follow up on them.

  • There is no third-party provider, no disrupting ads, and everything remains transparent inside github.

Github Users Yes, Spammers No

To keep spammers out and comments attributable, all you do is log in using your (free) github account and grant utteranc.es the permission to submit issues on your behalf.

If you don’t have a github account yet, go get yourself one - it’s free and simple.

If for any reason you do not feel comfortable with letting the commenting system submit issues for you, then visit Github Issues directly, i.e. by clicking the red button Submit Issue at the bottom of each page, and submit your issue manually. You control everything.

Discussions

For chit-chat and quick questions, feel free to visit and participate in Discussions. They work much like classic forums or bulletin boards. Just keep in mind: your valued input isn’t equally well trackable there.

  Show on Github    Submit Issue

(content created Mar 09, 2024 - last updated Mar 19, 2024)