The problem – the KHR 2 has an umbilical cord this can make more mobile actions dependant on the umbilical cords distance limitations.
Standard Bluetooth communication on the RCB3 –J is problematic and almost on the impossible scale.
Using a BlueSmirf from SparkFun has been concluded by Shsan’s research/experiments and others that Bluetooth inherently cannot allow proper transmission of the RCB3-J packet protocol which it uses. This is because the communication from the RCB3 is timing specific. Shsan’s website explains more on the behavior of the RCB3 communication under an Oscilloscope
And as PaulP on his post Wed Feb 28, 2007 10:55 pm here
“Bluetooth has byte gaps and latency problems. This can cause data problems on those robots that have a very strict timing protocol.” (PaulP)
Which is true so Bluetooth is out as a possible solution for a wireless RCB3 communications link between RCB3 and a PC.
So another possible solution is the XBEE
The XBEE is has been in fact used on other robots such as the infamous ROBONOVA-I & Hitec
Look here
Wireless Communication with XBee Radios
Practical Example HERE in this example they used a PIC microcontroller.
Is a really good example of how simple they are to implement
Well that concludes this little summary of what information so far has been gathered of the wireless problem.
Edward Arreola
Statistics: Posted by edmen — Sat May 05, 2007 8:54 am
]]>