Rainbowduino: Extra Technical Information

[michu]

@miso

Hello michu and thanks for the new info.

The garden.seedstudio page is definitely the best source of information regarding rainbowduinos right now. I did not realise that anyone could edit it.
I can see that it got where it is through iterative improvements and what I was suggesting was for people to ask/answer questions here and then collect/use that information in order to make the page even more complete. There is important information on it now that I needed and was not there a couple of days ago.

Jep - I just started some days ago… fee free to add more information!

1. What is the normal I2C communication speed between an arduino and an array of rainbowduinos?
   what do you mean with “communication speed”??? the bottleneck is definitve NOT the i2c bus.

I meant how many bytes per second can be send from the arduino to the rainbowduino? And if you have more than one connected is that speed shared?

As i2c is a bus protocol, the speed is shared yes. but to be honest, I dont have a clue whats the theoretical troughput is when using i2c bus at 400khz…

4. the best way to dynamically update a frame … best IDEs, best firmware/libraries and hardware
   “the best” is not very specific - read the wiki about the different firmwares

Yes you are right. I wanted to leave this generic so that the answers would not be specific. Things that I was interested to hear about were things like: Is the default arduino IDE the easiest to use? Is it the most advanced one? Are there any other IDEs worth looking into and why. Regarding dynamically updating full frames, I wanted to know what experiences people had with wired/wireless solutions and different IDEs that they have used. Regarding firmwares I wanted to know if there are any significant optimisation differences between existing firmwares (memory/comunications) or whether they all pretty much use the same code which is adapted to do slightly different things in logic.

M

The arduino IDE works fine for me, but I guess there are other for the more advanced users (AVR stuff). My plan with the neorainbowduino was, flash the firmware once and then just your code using the processing ide - you could also use the eclipse ide for that.