by PedroR » Tue Jul 31, 2012 2:47 pm
by PedroR
Tue Jul 31, 2012 2:47 pm
Hi Chienkai
Robobuilder does not supply a Gyro for the 57xx Robots.
There is a way to "hack" the robot to add a gyro using the I2C bus of the Accelerometer.
However, to do this, you need to program the micro controller in WinAVR (C).
If you're familiar with doing this, you may want o reffer to the following posts:
- Sample C code to get you started:
http://robosavvy.com/forum/viewtopic.php?t=3379
- You will need to design your board (or prototype) and add any I2C Gyro and eventually the Accelerometer.
You will then need to write the code to read the sensors and also to make use of them.
When using custom C programs written in WinAVR, the Robobuilder Graphical tools (MotionBuilder, ActionBuilder) and RBC Protocol will not work though.
There are also some alternative firmwares for Robobuilder that _might_ let you access the I2C bus without having to get down to WinAVR (maybe the BASIC firmware by l3v3rz but I'm not sure).
If you're familiar with these topics, the explanation above should be good enough; if you're not familiar with I2C and WinAVR, I would sincerely recommend sticking to the default configuration and firmware.
Regards
Pedro.
Hi Chienkai
Robobuilder does not supply a Gyro for the 57xx Robots.
There is a way to "hack" the robot to add a gyro using the I2C bus of the Accelerometer.
However, to do this, you need to program the micro controller in WinAVR (C).
If you're familiar with doing this, you may want o reffer to the following posts:
- Sample C code to get you started:
http://robosavvy.com/forum/viewtopic.php?t=3379
- You will need to design your board (or prototype) and add any I2C Gyro and eventually the Accelerometer.
You will then need to write the code to read the sensors and also to make use of them.
When using custom C programs written in WinAVR, the Robobuilder Graphical tools (MotionBuilder, ActionBuilder) and RBC Protocol will not work though.
There are also some alternative firmwares for Robobuilder that _might_ let you access the I2C bus without having to get down to WinAVR (maybe the BASIC firmware by l3v3rz but I'm not sure).
If you're familiar with these topics, the explanation above should be good enough; if you're not familiar with I2C and WinAVR, I would sincerely recommend sticking to the default configuration and firmware.
Regards
Pedro.