I received a RGB cube (link) from SeeedStudio and I have loved staring at it. It’s so mesmerizing. I even got one for my friend. We quickly realized that we wanted to tinker with the lighting scheme. Well, to do so, you would (will) have to remove the whole case to get to the USB. This made me sad, and hopefully with the help a few new friends, we can implement the MIST standard.
MIST is a standard that uses the hardware serial port to talk in a loop with one controller talking to the first cube. The first cube will then send the data to the next one, and so forth until it gets back to the controller. The controller would send out the next chunk of data to the cubes.
This breakout of controller/slaves means that you can be up and running quickly on a multi-cube setup. This also means that the controller can be anything from a standard Arduino to a computer, to a Xadow or Trinket module. The other thing that will be nice with this format, is we hope to have an area that showcases different programs, and to load the program, you just run the flat file through your controller. Very dynamic and with the price of storage, it makes it super easy to store hundreds of plans.
The only things that are needed are the Rainbowduino’s Rx and Tx pins cleverly exposed on the outside of the case. I am proposing to use the Grove 4 pin connectors for daisy chaining together, as this should also pass power. The end cube would have to have a Grove jumper to loop the serial line back to the controller.
Just a serial out is all that is needed, and the encoded lighting patterns to match what the cubes are looking for. A screen or internet connection is not necessary, although it would make it easier to navigate through your library.
Here’s the proposed string to be sent over serial in the loop of Arduinos:
p1 p2 p3
P1: Part 1 addresses the cubes. Index of 99 affects all cubes, while 00 is the “I’m done, pass the message on” message. All other numbers decrement by one per cube. Only values of 01 are processed by the current cube.
P2: Part 2 is the XYZ of the axis of LEDs. The address starts at (0,0,0) for indexes. I will go over some customizations later to allow for calling patterns.
P3: Part 3 is just calling the color in RRRGGGBBB format. Put each value in the right place in your sting, and you’re good.
Customizations to allow for multi-LED calling
I know it’s going to be annoying to have multiple standards, but here’s the one that I’m going to propose for the 4x4x4 cube. I propose a library be loaded to convert the custom string to put adjust the LED values to their updated value.
Here is my proposed mapping for single axis decoding:
4: Unused at current time
Where the values cross is where the LEDs are being adjusted. This also allows a value of 9,9,9 to clear or fill the whole cube with one command. A  signal would instantly black out all cubes.
I have included an Excel file that is interactive with these “shortcuts” to show you how they will look when sent to the cube. (Rainbow Cube Data Feed Tester) The left table is a decoding of the axis value to LED, the middle table is where you put in your values to try it out, and the right tables are the output. Only the cells that are lit up in red would be on. I am a visual person, so this was very helpful in helping me understand the power of this standard.
- I am going to try and do a proof of concept of daisy’ing multiple ‘duinos together to try out this concept
- Work on the code and library to convert the 14 char string quickly into the format needed to update the LEDs
- Build two different controllers, one Arduino, one LinkIt (and maybe a Xadow if you’re lucky)
- Try to get Seeed to supply me with Grove female adapters to build into the cube to make it look nice
- Convince Seeed to try out 10+ units with one controller