From 6bc890ea66d4404b685f30fc6090cebbc700cccb Mon Sep 17 00:00:00 2001 From: Rich Lander Date: Fri, 9 Apr 2021 18:28:29 -0700 Subject: [PATCH] Update README.md --- src/devices/Charlieplex/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/devices/Charlieplex/README.md b/src/devices/Charlieplex/README.md index 6e227ce8e6..3a2c9847d2 100644 --- a/src/devices/Charlieplex/README.md +++ b/src/devices/Charlieplex/README.md @@ -4,6 +4,8 @@ An even bigger challenge is that the scheme (at least in its basic form) only allows for lighting a single LED at once. On the face of it, that would seem to be a big problem. Don't worry. The LEDs change very quickly such that the eye is tricked into thinking multiple LEDs are lit at the same time. This means that your code that cannot be doing something else while the LEDs are lit. This is why the API accepts timing information. This is not what you'd expect if you are used to lighting LEDs directly from GPIO pins or via a shift register. +[Show dotnet: Animating 40 LEDs with charlieplexing](https://devblogs.microsoft.com/dotnet/show-dotnet-animating-40-leds-with-charlieplexing/) demonstrates using this binding. + ## Usage The following code sample demonstrates addressing 6 LEDs with 3 pins.