Comments on: 64pixels are enough

By: Alex

Alex — Tue, 08 May 2012 06:10:49 +0000

Hi G’duino,
take a look at the Makefile, included in the zip, at the end of the howto article.

By: G'Duino

G'Duino — Mon, 07 May 2012 17:51:11 +0000

Hi Alex, this is an awesome project. I want to build this project myself but before that, can you please give some detail about fuse bit’s setting of Attiny2313 for this project. Thanks!

By: Alex

Alex — Tue, 24 Apr 2012 10:30:17 +0000

Hi Dani,
all characters in font.h are at max 3 pixels wide. Every byte stands for a single column, the last byte stands for the length of the character, e.g. if you want to light up the up most 2 pixels, that would be 0×03, or binary “0000 0011″. That way you can design you own font. Making the font wider would be a bit more complex.

By: dani

dani — Tue, 24 Apr 2012 08:18:06 +0000

Hi Alex,
great idea and look nice, uuummm how can I get full text size? (using all 8 row instead of 5), i’ve try to edit font.h but without luck, can you help me. i just want to displaying 2 words, but at full sized font. it is possible?

By: Charlieplexed animated heart hoodie « RobotSkirts

Charlieplexed animated heart hoodie « RobotSkirts — Sun, 09 Oct 2011 22:06:43 +0000

[...] The heart uses a technique called Charlieplexing to drive the 27 LEDs using just 6 pins. To finally get the device working, I just soldered wires directly to the heart. My favorite feature of this project was the simple Flash based animation tool Jimmie included to generate the Arduino sketch. It really made what could have been an arduous process of generating animation frame arrays very very easy. You can see the final few animations I programmed embedded below. I liked this badge idea so much, I ordered 2 of Alex’ 64 pixel kits. [...]

By: Lo and Behold, 64 Pixels are Enough! | Coffeebot Labs

Lo and Behold, 64 Pixels are Enough! | Coffeebot Labs — Sat, 13 Nov 2010 04:58:56 +0000

[...] enamoured with Alex Weber’s 64 Pixels project from the moment I saw it. When I happened across it (via Make:blog, I think), I was just [...]

By: tgfuellner

tgfuellner — Sun, 12 Sep 2010 17:40:05 +0000

Simplicity rules!

I like this small thing. You can compile with current AVR-GCC instalations by using the compiler option
-fno-inline-small-functions

In the Makefile:

COMPILE = avr-gcc -Wall -Os -fno-inline-small-functions -DF_CPU=$(CLOCK) -mmcu=$(DEVICE)

By: saw0

saw0 — Mon, 28 Sep 2009 00:40:05 +0000

Thank you so much

I found a Conversion table in the net.

Greetings

saw0

By: Alex

Alex — Sat, 26 Sep 2009 14:56:58 +0000

Hi saw0,
0x## is the hex notation.
As an example: 0×18 is one byte in hex. In bits it looks like this: 0001 1000, so first 4 digits is the 1, that last 4 is the 8. So that lights up the two LEDs in the middle.
Cheers,
Alex

By: saw0

saw0 — Sat, 26 Sep 2009 14:49:46 +0000

Hey Alex!

Thanks for pointing this out, now i also see that the wiring is different.

I uncommented the part, It works flawlessly now.

Thanks for this nice Blinky, my girlfriend loves it

Just another question: I don’t quite understand how to make own animations:

0×18, // ___XX___
0×3C, // __XXXX__
0×7E, // _XXXXXX_
0xDB, // X_XXXX_X

how can i translate the “0x##” part so i know which pixel i actually lights?

Greets and thanks in advance!

saw0