Rainbowduinos and i2c communication

[zapgadget]

Hello,

I have 3x Rainbowduinos V2 and 3x Rainbowduinos V3

I have a project where I want three of the Rainbowduinos to work together as a simple 8x24 RGB matrix.

On the wiki pages for both V2 & V3, it says “can be easily cascaded to use i2c”.

My question is how to use 2-3 boards with i2c? Physically is easy - just chain them together.

Is there any example working code (an arduino sketch) anywhere in the world for this?

All I see so far is rumors about i2c being hard because you don’t have interrupts available - that doesn’t sound like easy.

Thanks,

Paul

[ffoppel2]

Hi Paul,
a full answer to your question is hard, since you did not describe you ful setup. But cascading rainduinos in general is very easy. I2C is a single Master bus topology, so I see 2 options for your scenario.

1. (I2C-Master)<->1stRainduino)<->2ndRainduino)<->3rdRainduino
   The master could be an arduindo or anything else that can send the messages. all 3 rainduinos will use the same code, but must have different I2C addresses.
   In this case the master must be aware of the fast that there are 3 recievers and where to send which messages.
   This is also what I have used in my project. The master arduino has a network shield and offers interfaces for both global control e.g. set color xyz will be translated into 3 identical messages send to the 3 different IDs as well as some specific interfaces like DrawPixelABCRGB where A is the ID of the receiver B and C the coordinates inside the rainduino and RGB the color.
2. external interface e.g.serial->1stRainduino)<->2ndRainduino)<->3rdRainduino
   In this case you need 2 different firmware vesions, one for the first rainduino, which is capable of spliting the incoming commands to the ones used hinself and the one to be resend via i2c to the other rainduinos. The other to rainduinos will just have a simple slave SW like in example 1.

HTH
Fritz

[zapgadget]

Hi Fritz,

Thanks for the reply.

@ffoppel2

Hi Paul,

1. (I2C-Master)<->1stRainduino)<->2ndRainduino)<->3rdRainduino
   The master could be an arduindo or anything else that can send the messages. all 3 rainduinos will use the same code, but must have different I2C addresses.
   In this case the master must be aware of the fast that there are 3 recievers and where to send which messages.
   This is also what I have used in my project. The master arduino has a network shield and offers interfaces for both global control e.g. set color xyz will be translated into 3 identical messages send to the 3 different IDs as well as some specific interfaces like DrawPixelABCRGB where A is the ID of the receiver B and C the coordinates inside the rainduino and RGB the color.
   Fritz

secnario 1 is more what I was thinking. I’m familiar with the i2c bus. When I tried using neorainbowduino firmware, I got a problem where the i2c slaves simply didn’t respond at all.

I’d be happy with some sample code that I knew worked. Otherwise it’s easy to get tied up with bus timing and irq servicing. What upsets me is the blithe remark “i2c is easy” with no code to back that up.

The wiki even says for the RainbowDash firmware (which seems to be working great) that “Can easily be changed to use I2C; only one file (RainbowDash.pde) needs to be changed.” I wondered if anyone had actually done it.

Thanks,

Paul