Basic Communication API Framework (multiple ways in / multiple ways out)

[GoogleCodeExporter]

Hi, 

I think that we could generarate a elemental communication API for Serial
and Bluetooth Connection.

The first layer, allow to stablish the connection. For the moment if you
use Serial Port with Python, a good idea could be define a standard to
connect with an Arduino board. With Bluetooth, we could create the same API
to reach that goal.

In a second layer, we could stablish a protocol to manage actuators, for
example RC Servos.

Original issue reported on code.google.com by archivo...@gmail.com on 9 Mar 2010 at 8:57

[GoogleCodeExporter]

I agree. We want to break out the robot logic from the inbound commands, and 
the outbound calls 
to the robot hardware. Three layers would be great and some examples might 
include:

1. Inbound commands
- BlueTooth
- Terminal
- Web / HTTP page hosted from phone
- Web socket through another server
- XMPP

2. Robot logic that makes decisions, does some error checking, and handles 
communications 
between the hardware and controlling user.

3. Outbound signals
- BlueTooth
- Serial
- DTMF audio
- On screen signal for photoresistors
- Wi-Fi

Original comment by rhickman on 26 Mar 2010 at 4:14

• Added labels: Priority-High, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

As of 3/27/2010 we now have support for accepting telnet or voice commands by 
default. 
Would like to see the loops threaded so a user could enable both options, or 
easily 
turn one or the other on and off.

Original comment by rhickman on 28 Mar 2010 at 11:31

[GoogleCodeExporter]

Original comment by rhickman on 28 Mar 2010 at 11:47

• Changed title: Basic Communication API Framework (multiple ways in / multiple ways out)

[GoogleCodeExporter]

This is in place now so I'm closing this. While we don't support all of the 
above 
methods, we have a nice framework to give users options.

Original comment by rhickman on 2 Jun 2010 at 3:15

• Changed state: Fixed