Rainbowduino IDs about pixelcontroller HOT 3 CLOSED

hey markus

I was asking myself some days ago, if the rainbowduino port still works - but that must be a yes.

Well I had a similar issue like you in the beginning - but I think there is no issue here. in the neorainbowduino i defined the i2c address as hexadecimal, while in the pixelcontroller config file the regular decimal address is requested.

So the easiest solution in this case would be, adding a comment like

#=========================
#settings for rainbowduino
#=========================
#i2c destination address + layout definition
#Hint: the rainbowduino define its i2c address in HEX while we need a DECIMAL address

what do you think`?

cheers and thanks

from pixelcontroller.

Hi,

With that hint it should be pretty clear that you have to configure the Rainbowduino IDs in decimal. I was just wondering if it was intendend to log the IDs in decimal instead on hex. For my example I would have expected that it would also print the hex value for e.g. my 0x11 id instead of the decimal value:

Sep 07, 2011 12:52:53 AM com.neophob.lib.rainbowduino.Rainbowduino sendFrame
INFO: Send data to device 17

Nevertheless I'd suggest to change the two occurrences of Integer.parseInt() in the parseI2cAddress() method to Integer.decode(s) which simply accepts both ways of defining the I2C IDs:

layout.row1.i2c.addr=0x11,0x12,0x13,0x14
layout.row2.i2c.addr=0x15,0x16,0x17,0x18
layout.row1.i2c.addr=17,18,19,20
layout.row2.i2c.addr=21,22,23,24

Greetings,
Markus

from pixelcontroller.

Thanks for the hint about Integer.decode(s) - I included it in the refactored properties code, thanks!

from pixelcontroller.