With a little imagination – a lot! Here’s a quick start to get you and your ROBO up-and-running.

Step 1: Software / Driver InstallationIMG_8565 You can communicate with ROBO using a RADiuS dongle, you’ll need to install FTDI’s Virtual COM Port Driver first – before plugging the dongle in. Versions of the driver are available for Mac OS X, Windows, and Linux.






[clear]Step 2: Plug-in the DongleIMG_8572 Insert the RADiuS dongle into an available USB port. You should probably say ‘pew pew’ or ‘swoosh’ really loud when doing this.







[clear]Step 3: Arduino IDEIMG_7749 Open the Arduino IDE, and from the main menu ( tools -> serial port ) select the dongle as your target device. When you’re ready – open the serial monitor and set the BAUD to 19200 and line-endings to ‘newline.’ You’re ready to communicate with your ROBO!







[clear]What to do… what to do? If your ROBO has servos, you can control them with the following command. Just copy and paste this into the text-box in the Arduino serial monitor and click ‘send.’ That’s it!

{ robo:a1a1, cmd:servo, data:1|100|30 }

How does all this work?

Each ROBO has a unique and case-sensitive ID… in the example above it’s a1a1. When a ROBO hears a command with their ID – they will respond accordingly. If you want to issue the same command to multiple ROBOs, use the ID 0000.

The cmd, or ‘command’ should be easy to read. We want to control a servo, and ‘data’ is what we want the servo to do. The first number is the servo you want to control, the second number is the position or destination you want it to seek to, and the last – is the number of frames or time to take moving from its current position to the destination.

With ROBO facing you…

servo 1: left hand (range from 0 – 240)
servo 2: left shoulder (range from 0 – 240)
servo 3: neck/head (range from 0 – 180)
servo 4: right shoulder (range from 240 – 0)
servo 5: right hand (range from 0 – 240 )

Did you know that ROBOs with an EMIC 2 Text to Speech Module installed can talk? Switch over to the ‘say‘ command… and give it something to say in the data.

{ robo:a1a1, cmd:say, data:whatever you want me to say }

If your ROBO seems stubborn and won’t respond to commands – try unplugging it for a second or two. ROBOs can get confused from time to time… a power-cycle can help clear their brainz.

Upgrades? Firmware? Yes… and yes. I’ll be releasing the firmware along with instructions on how to upgrade and/or add functionality to your ROBO on June 10th. Stay tuned!