Pages: [1]   Go Down
Author Topic: A charlieplexing library  (Read 1426 times)
0 Members and 1 Guest are viewing this topic.
Offline Offline
Newbie
*
Karma: 0
Posts: 4
View Profile
 Bigger Bigger  Smaller Smaller  Reset Reset

Hi, all!
When I went looking for a library to help with charlieplexing an array of LEDs, I couldn't find one that supported larger numbers of LEDs, while making it simple to address each LED. So I wrote one. smiley-grin I'm calling it ChuckPlex, and I hope others will find it as useful as I do.

It can help you configure your array: telling you how many pins you will need for a particular number of nodes and how to wire them. It addresses nodes by index, hiding the HIGHs, LOWs, INPUTs and OUTPUTs. It supports using as many pins as you can spare, allowing over a hundred LEDs on most boards, or thousands on the Mega. If the chosen pins are PWM pins, it supports writing analog values in addition to digital ones.

Some example code:
Code:
#include <ChuckPlex.h>

int pins[] = {2,3,4,5};
ChuckPlex plex = ChuckPlex(pins,4);

void setup(){
  // no setup!
}

// blink the fourth led in the array
void loop(){
  // light the fourth led
  plex.enable(4);
  delay(1000);
  // turn off all leds
  plex.clear();
  delay(1000);
}

Please try it out if you are inclined, and I would love to hear feedback!
latest version: ChuckPlex v1.0.1
« Last Edit: October 03, 2012, 01:29:18 am by marcuserronius » Logged

Offline Offline
Edison Member
*
Karma: 19
Posts: 1041
Arduino rocks
View Profile
 Bigger Bigger  Smaller Smaller  Reset Reset

0) Put all of those strings into flash memory!

1) It seems like there's a lot of bloat. You pull in the floating point library and a ton of strings, which is unnecessary. Although I'm not sure if gcc is smart enough to ignore all of those if the user doesn't end up using the displayConnections function.

2) You need to use memcpy for getting the pins array, because you don't know what the user will do with it after they've passed you the pointer.

4) Add some documentation. You should at least say which methods are "you should use this" and which ones are "you probably won't need this" --- I'm guessing that write is the "main" method.

5) write's value argument should have a default value, because it's pretty frequent that you just want it on full power.
Logged

Offline Offline
Newbie
*
Karma: 0
Posts: 4
View Profile
 Bigger Bigger  Smaller Smaller  Reset Reset

Thanks for the feedback smiley This is my first project working with Arduino, so I don't know a lot of the tricks that may seem obvious to others.

Regarding the strings, I was originally going to use an external utility to display the connections, but decided to pull it into the project. Probably it would be better to conditionally compile that in only if it's in develop mode…

memcpy: thanks for the pointer, didn't think of that.

documentation: since it was simple, I was just letting the examples do the documenting smiley But that's pretty lazy, so I'll get something proper in there.

Again, thanks for the feedback!
Logged

Offline Offline
Newbie
*
Karma: 0
Posts: 4
View Profile
 Bigger Bigger  Smaller Smaller  Reset Reset

So it appears that gcc will leave out the the strings and floating point library if the user doesn't call the displayConnections() method. If the method is only used the one time for setup, is there a cause for concern about it? Or would it be a more elegant solution to move it back to an external utility after all? Thanks for all your help smiley
Logged

Pages: [1]   Go Up
Jump to: