Whoa ?R, are those 2pin rgb fade leds or are those 4 pin rgb terminated leds? They look to only have 2 pins.

they are RGB LEDs with common anode, 4 pins, they are controlled by 3 TLC's

about the tiny84, i'm trying it, but i think there is a problem with the port mapping, because in the tiny85 you set the pin PB0, PB1 and and PB2 but in attiny84 should be PA6 PA5 and PA4, do you agree with me? or am i wrong?

#if defined (__AVR_ATtiny85__) || (__AVR_ATtiny84__)/*------------------------------------------------------------------------ Configuration------------------------------------------------------------------------*/// How many TLC chips are attached. Each chip needs 32 bytes of RAM.// The ATtiny85 only has 512 bytes of RAM and you need some left over// for the rest of your program. Do the math...#ifndef NUM_TLC5940s#define NUM_TLC5940s 3#endif

/*------------------------------------------------------------------------ Pin assignments------------------------------------------------------------------------*/// You could move the BLANK_XLAT_PIN if you wanted to// but the USI pins are fixed.#if defined (__AVR_ATtiny85__)#define BLANK_XLAT_PIN PB0#define USI_OUT_PIN PB1#define USI_CLK_PIN PB2#else#define BLANK_XLAT_PIN PA6#define USI_OUT_PIN PA5#define USI_CLK_PIN PA4#endifafter i'll try the hardware, but i think that with those modifications that library can be called "Tiny_TLC5940" what do you think about? am i wrong?

Whoa ?R, are those 2pin rgb fade leds or are those 4 pin rgb terminated leds? They look to only have 2 pins.

they are RGB LEDs with common anode, 4 pins, they are controlled by 3 TLC's

about the tiny84, i'm trying it, but i think there is a problem with the port mapping, because in the tiny85 you set the pin PB0, PB1 and and PB2 but in attiny84 should be PA6 PA5 and PA4, do you agree with me? or am i wrong?

Oh, yes, those pins need to change, too.

PA6 PA5 and PA4 is correct but you'll also have to change all references to PORTB, DDRB and PINB into PORTA, DDRA and PINA.

/*------------------------------------------------------------------------ Bitbang driver for ATtiny85+TLC5940 using only three pins------------------------------------------------------------------------*/#ifndef _TEENY5940_H#define _TEENY5940_H

#if defined (__AVR_ATtiny85__) || (__AVR_ATtiny84__)/*------------------------------------------------------------------------ Configuration------------------------------------------------------------------------*/// How many TLC chips are attached. Each chip needs 32 bytes of RAM.// The ATtiny85 only has 512 bytes of RAM and you need some left over// for the rest of your program. Do the math...#ifndef NUM_TLC5940s#define NUM_TLC5940s 1#endif

/*------------------------------------------------------------------------ Pin assignments------------------------------------------------------------------------*/// You could move the BLANK_XLAT_PIN if you wanted to// but the USI pins are fixed.#if defined (__AVR_ATtiny85__)

This is going to sound really newbish but how do you guys program your ATtinys? I have tried the High Low Tech tutorial numerous times and it doesn't work. Also I have a hard time finding ATtiny85 cores. Any help?

I have tried the High Low Tech tutorial numerous times and it doesn't work. Also I have a hard time finding ATtiny85 cores. Any help?

I think that was the page I used when I started out but I admit I never did "Arduino as ISP", I bought an ISP programmer.

I usually don't bother with cores any more. The chips are very easy to program directly and writing the code is part of the fun!

The real problem would be in using other libraries that rely on having SPI, etc. Adapting code that needs those things would be a challenge. I don't use other code much though (it rarely fits exactly) and I can always use a Mega328 if I really need to...

And i recommend using Coding Badly's TinyISP. It gives you all the debug benefits you are used to from the Arduino

Serial comms? The problem with that is the Tiny85 has very limited pins. Dedicating some of them to debug output is difficult.

PS: This is why I do most of my Tiny85 coding on a Tiny84... they're similar enough that the code can run on both chips without much effort and the Tiny84 has enough pins left over to use for debugging.

( I use LEDs and a little screen for debug output...you can see my development environment here: http://arduino.cc/forum/index.php/topic,139345.0.html )

No, I don't answer questions sent in private messages (but I do accept thank-you notes...)

Anyway it is a nice little programming board you have made.Any link to the display ?

This is the one I bought: http://www.ebay.com/itm/170842973484

(also available from other sellers...)http://www.ebay.com/itm/170929165280http://www.ebay.com/itm/160889283903http://www.ebay.com/itm/250986036479http://www.ebay.com/itm/180945872898...

nb. There's some cheaper OLED screens on eBay but those ones run off 5V and have an extra controller chip that can draw text, etc. all by itself - no need for font data or bitmap manipulation code on the Arduino. I definitely think it's worth the extra $5 for that feature (nb. I didn't know this when I bought mine, I got lucky...)

No, I don't answer questions sent in private messages (but I do accept thank-you notes...)

i'm using fungus's library and i want to try to consume less energy.is there any way to say to the TLC "go to sleep" as we do with atmel microcontrollers?do you think that just stopping the communication with it could be enough? or usign the method init?