Rainbowduino v3.0

[wsarles]

Hello. First, thanks for the awesome looking project. Do you know if the project will work using Rainbowduino v3.0 hardware boards (specifically, I have a 3.0b, model ARD127D2P). I'm fairly sure I followed the Rainbowduino Readme perfectly, but it seems that I'm getting some errors finding my Rainbowduino when I run the shell script (PixelController.sh):

I see this hundreds of times: Jan 15, 2012 11:17:54 PM com.neophob.sematrix.output.neorainbowduino.Rainbowduino waitForAck INFO: No serial reply, duration: 51ms

Any ideas?

[neophob]

Hey Chiggers

It looks like the guys from Seeedstudio made a new major version of the rainbowduino device, old hardware is not compatible anymore...

I do not exactly know what they changed, but I would compare their firmware with the neorainbowduino firmware. Can you check this?

Cheers

[wsarles]

Michael,

Thanks for the quick reply. I posted on the Seedstudio forums as well:

http://www.seeedstudio.com/forum/viewtopic.php?f=4&t=2759

It seems that there were some big changes in the hardware and the 2.0 boards are no longer sold. Thanks for the tip on comparing firmwares. I'm a novice with all this, so I'll see what I can find out.

-Chad

On Jan 16, 2012, at 5:04 AM, Michael Vogt wrote:

Hey Chiggers

It looks like the guys from Seeedstudio made a new major version of the rainbowduino device, old hardware is not compatible anymore...

I do not exactly know what they changed, but I would compare their firmware with the neorainbowduino firmware. Can you check this?

Cheers

---

Reply to this email directly or view it on GitHub: https://github.com/neophob/PixelController/issues/15#issuecomment-3508501

[markuslang79]

I'm currently finalizing my Rainbowduino V3 code which is able to stream close to 25fps from a Java application to the controller via a simple USB connection. Gimme some weeks to polish everything up but Raindowduino V3 support in the PixelController isn't far away..

[neophob]

Sounds great, thanks!

[neophob]

fixed

[julio333]

I appreciate your work. I bought 2 Ranbowduino v3.0b and was able to work only with RainbowStudio. I wanted to use streaming firmware, ranbowduinoino v3.0b in pixelinvaders but it does not connect with the program. I wrote the firmware ...... in ranbowduino v3.0b with Arduino 1.0.3 IDE (rv3sf.ino). I copied the file from, PI/data/config.examples/Rainbowduino- (CFG file extension) on data, and I renamed (config.properties). I opened Pixelinvaders but it is not connected. In RainbowStudio now connects but no image appears (red control LED flash) that because neither firmware is not suitable for the program. Maybe I missed something but I followed all your instructions, and if anyone can tell me where to find the original firmware, Ranbowduino v3.0b? And what could I omit because I tried to connect and Teensy2 + +, and teensy 3 and also not connecting.

[markuslang79]

Hi Julio,

So flashing the rv3sf.ino into the Rainbowduino V3 controllers is the
correct firmware to use them within the PixelController. If flashed
successfully the controllers should show nothing on the LEDs and print
nothing on the serial port.

I've just had a look at the Rainbowduino.cfg configuration in the
config.examples directory and I have the slight feeling that it's
outdated. If you look at the
https://github.com/neophob/PixelController/blob/master/data/config.properties
file you'll find a Rainbowduino V3 section in it (search for
'rainbowduinov3') where you have to specify the individual serial
ports of the connected controllers.

I believe that your problem is a PixelController output devices
configuration problem.

Greetings, Markus

Quoting julio333 notifications@github.com:

I appreciate your work. I bought 2 Ranbowduino v3.0b and was able to
work only with RainbowStudio. I wanted to use streaming firmware,
ranbowduinoino v3.0b in pixelinvaders but it does not connect with
the program. I wrote the firmware ...... in ranbowduino v3.0b with
Arduino 1.0.3 IDE (rv3sf.ino). I copied the file from,
PI/data/config.examples/Rainbowduino- (CFG file extension) on data,
and I renamed (config.properties). I opened Pixelinvaders but it is
not connected. In RainbowStudio now connects but no image appears
(red control LED flash) that because neither firmware is not
suitable for the program. Maybe I missed something but I followed
all your instructions, and if anyone can tell me where to find the
original firmware, Ranbowduino v3.0b? And what could I omit because
I tried to connect and Teensy2 + +, and teensy 3 and also not
connecting.

---

Reply to this email directly or view it on GitHub: https://github.com/neophob/PixelController/issues/15#issuecomment-13389379

[neophob]

thanks markus

yes I plan to remove the example config files, they scream for "outdateness"!

[julio333]

 Hello ,

I downloaded the latest version Pixellinvaders1.3.1 but I could not open the 2 modules Rainbowduino-v3b (connected to USB).I selected the ports for them (COM1 & COM2) but I think the problem is config.propriertes where I did not know if the changes are correct . I would ask if you can send me a file (config.propriertes) modified my configuration, and if the original should be removed? The two modules are installed (rainbowduino-v3-streaming-firmware-ino). Thanks and I have a question. You thought a firmware Rainbowduino-v3b, Madrix software to work with. I have tried firmware rainbowdash who managed to run my modules but not correct (normal). Once again thank you for your understanding and support. With respect Julian H.

[neophob]

check out https://gist.github.com/neophob/5021637

all you need to do is replace layout.row1.serial.devices=/dev/ttyUSB0,/dev/ttyUSB1

with COM1 and COM2

try that and let me know if it works

[fredolivas]

This is making me CRAZY! This darn thing won't work. I have no idea how to config.properties this thing. Have a Rainbowduino v3 and v1 connected to COM port 6, currently and followed advice above but to no avail. Firmware IS installed. Isn't there an easier way for config? Why hasn't anyone just posted a Rainbowduino config file so that the frustration factor gets reduced?

[neophob]

Why don't you read the config file?

#=========================
#settings for rainbowduinoV3
#=========================
#serial device names + layout definition
#  on Linux/OSX use names like "/dev/ttyUSB1"
#  on Windows use names like "COM1"                             <<<<<<<< LOOK HERE
layout.row1.serial.devices=/dev/ttyUSB0,/dev/ttyUSB1
#layout.row2.serial.devices=/dev/ttyUSB2,/dev/ttyUSB3

[fredolivas]

Hi, I've read the config file but I don't understand a few things such as: on Windows use names like "COM1". My case would be COM4. Just a second here, "#serial device names"; is this where I would just write COM4? Replace 'serial device names' with COM4? Is it really that simple? What does "layout definition" mean? Is it the X,Y pixel configuration size? Thank you for my ignorance and misunderstanding but some obvious things are as "clear as mud" to me. With gratitude, Fred Olivas

On Nov 24, 2014, at 6:24 AM, Michael Vogt notifications@github.com wrote:

Why don't you read the config file?

=========================

settings for rainbowduinoV3

=========================

serial device names + layout definition

on Linux/OSX use names like "/dev/ttyUSB1"

on Windows use names like "COM1"

layout.row1.serial.devices=/dev/ttyUSB0,/dev/ttyUSB1

layout.row2.serial.devices=/dev/ttyUSB2,/dev/ttyUSB3

— Reply to this email directly or view it on GitHub.

[sdawans]

You ought to show a bit more respect and patience when asking for help.

Lines starting with "#" are not taken into account, they are comments. In your case you'll want to do something like:

layout.row1.serial.devices=COM4

Is it that simple? Sure, why make it harder than it should be? All this is doing is pointing the system to the correct serial device rather than trying to blindly test each one. Besides, if you have multiple devices it can't guess their layout.