by PaulP » Sat Mar 24, 2007 1:13 pm
by PaulP
Sat Mar 24, 2007 1:13 pm
For those who haven't seen this on Lynxmotion..
KHR-1HV after some heavy mods
http://www.youtube.com/watch?v=sf1QcBSvKUA
http://www.youtube.com/watch?v=S4Wq-m4ZrvU
http://www.youtube.com/watch?v=RFQU1QrZEPA
The first one is a slower, more useable walk.
Second is some stock moves ported across to the new processor.
The third is roborealm. A camera is connected to the KHR-1HV head and as the ball is moved, a small VB6 / VB.NET app using the roborealm API, moves the robots head to track the ball.
The RCB has been dumped and in its place in the backpack is a LynxMotion SSC-32. The Battery has been moved to the inner void and in the chestplate is an MR162 (Atmega 162).
This combination allows complete control via Sparkfun Bluesmirf while still retaining the ability to run the SSC-32 from SEQ (equivalent of H2H).
Currently, the Atmega is programmed for pass-thru comms (UARTA is connected to UARTB) so all comms get relayed. A subset of commands with a unique prefix will allow commands to be redirected to the Atmega for alternate commands.
Next is a 5 DOF Gyro/Accelerometer that (if my skills are good enough) will modify the pass-thru data to incorporate the sensor data into the moves. It will also allow the bot to auto-execute recovery routines should it fall over.
For those who haven't seen this on Lynxmotion..
KHR-1HV after some heavy mods
http://www.youtube.com/watch?v=sf1QcBSvKUA
http://www.youtube.com/watch?v=S4Wq-m4ZrvU
http://www.youtube.com/watch?v=RFQU1QrZEPA
The first one is a slower, more useable walk.
Second is some stock moves ported across to the new processor.
The third is roborealm. A camera is connected to the KHR-1HV head and as the ball is moved, a small VB6 / VB.NET app using the roborealm API, moves the robots head to track the ball.
The RCB has been dumped and in its place in the backpack is a LynxMotion SSC-32. The Battery has been moved to the inner void and in the chestplate is an MR162 (Atmega 162).
This combination allows complete control via Sparkfun Bluesmirf while still retaining the ability to run the SSC-32 from SEQ (equivalent of H2H).
Currently, the Atmega is programmed for pass-thru comms (UARTA is connected to UARTB) so all comms get relayed. A subset of commands with a unique prefix will allow commands to be redirected to the Atmega for alternate commands.
Next is a 5 DOF Gyro/Accelerometer that (if my skills are good enough) will modify the pass-thru data to incorporate the sensor data into the moves. It will also allow the bot to auto-execute recovery routines should it fall over.