RGB Ring V3 will not respond to commands

[Ricky]

We've just updated the V3 documents. Here is the structure of the command

5.3 Rainbow Ring interaction
The following are the commands used to control your Rainbow ring. Included are the parameters needed and the terminal command to execute each command.

               //Term command
#set_led_rgb(LED, INT, INT, INT);    //b     The first parameter is the LED number from 0-11, INT = intensity 0-64
#set_led_unicolor(LED, RGB, Int);    //u    RGB = 0, 1, OR 2.
#set_all_rgb(R, G, B);         //r    int = intensity  i.e.:RED 00, GREEN 25, BLUE 34: set_all_rgb(00, 25, 34);
#set_all_unicolor(RGB, Int);      //a
#rotate(color, dir);         //o    Color, direction, color is set from 0-7 and rotation from 0-2
#clearCommand();         //-   No parameters needed
#random_leds ();         //x   indicate how many LEDs to light and the delay between each
#fader ();            //f   how many times to repeat
#fader_hue ();            //h   how many times to repeat
#sequence();            //S   how many times to repeat   *NOTE: CAPITAL S
#color_wave (0) ;         //w   amount to increase ,delay
Each terminal command should be preceeded by a "c" and ended with an "s". These commands are case sensitve.

EXAMPLE:co029901s

This will send the command (c) rotate(o) the color Blue (02) times (99) clockwise (01) send (s)

[Scottish Dave]

Hi Ricky,

Thanks for getting back to me, but have you read my posts ? You have directed me to the files for the V2 ring, when I have a V3. And you are telling me to use the same command that I listed in my first post as not working....

Dave

[Hector]

Hi Dave,


I really apologize for the poor documentation provided for V3. I will try to talk to the developer and ask him for a more user friendly sample code, it might take some time, please be patient.


We are committed to delivering complete functioning products. Along with sample code, occasionally we slip up and don't provide proper documentation. Please understand we have lots of products with new ones being added every week, which makes it difficult for our small team to keep up with.


Also, we service the DIY community, which means we rely on users to provide better codes and project guides for our products. We normally only provide connection diagrams, and a simple sample code to prove to the user that the device is in fact working. The rest is left to the user to figure out. Never the less we strive to provide customer satisfaction, and we have in the past delivered better sample code for this product, I'm sure we can do so again. At the moment I am very busy preparing for the San Francisco Maker Faire, so please understand if this takes a little longer.


Also, if you are a newbie this is a good way to learn 

[Ricky]

Hi Ricky,

Thanks for getting back to me, but have you read my posts ? You have directed me to the files for the V2 ring, when I have a V3. And you are telling me to use the same command that I listed in my first post as not working....

Dave

Hi Dave:

The V3 has exactly the same commands as V2.  It may be other issues that these commands are not working. Please check the baud rate, connection etc. 

Sorry for the poor documentation. We are doing some tests and will get back to you ASAP.

[Hector]

Hi Dave,


I have updated the wiki, please take a look at the new section. I have updated the code to comply with the old instructions. Please let me know if it is working well.




Wiki doc

[caseyd]

Hey Dave, how did this go?

I just fired up a V3 and am experiencing oddness in the behavior of the library - or my use of it!

Roboteros - if we come up with patches etc where do we place them?

[caseyd]

self-follow up, sorry.

let me see if I'm getting this right:

the 'new' RAR has 2 sketches, ReceiverV3 and SenderV3. These are intended to be used in the IC2 'test' configuration.

ReceiverV3 is quite a bit like RGB_Ring_V3. The code which reads the on-board switches looks to be the same, while the code which handles the IC2 communications is a bit different.

The most exciting parts of the ReceiverV3 code are the comments // BROKEN adjacent to a number of the handlers.