by PedroR » Sun Jan 18, 2009 2:15 am
by PedroR
Sun Jan 18, 2009 2:15 am
Hi
First I wanted to say thank you to Novaone and iBot for all their advice and information that we discussed during BETT, specially with regards to Robobuilder.
I really enjoyed meeting you!
I got to demo the software I've written and also found some bugs that I will need to address.
The plan is now to hack the full protocol on the Robobuilder and have the PC talk to the servo bus through the serial port.
1)
iBot has explained to me that there is a special, undocumented packet that, when sent to Robobuilder, puts it into PC control mode (an orange light appears on the RBC controller).
We can see this happening when we connect Motionbuilder to the robot for example. Once you open the COM the orange light appears on the RBC and Motionbuilder talks directly to servos when you rotate the wheels on the screen.
According to iBot there is then a second undocumented packet that exits PC control mode and returns the RBC into normal mode.
I propose documenting as the next step to take.
2) After that's done, I really wanted to extend the DLL library so we can start talking to the servos directly. This shouldn't be too hard since we have the protocol for the servos (it's documented and posted on the forum).
3) The third challenge is actually find out how to connect sensors to the IO ports on each wCK and interface with them.
Each wCK has 1 analogue and one digital IO port (I think it's one of each) but the native software doesn't seem to have a way to use them.
Again, I would like to add support for these in the DLL library.
4) Finally I wanted to be able to have the library interface with the acceleration sensor.
According to iBot this may not be trivial so let's see.
I'm really enjoying this "hacking" of the robobuilder. I've always liked robotics and these low level communications but i've never actually done anything until I started working on robobuilder.
I hope I have "company" in this journey towards hacking the RB

Hi
First I wanted to say thank you to Novaone and iBot for all their advice and information that we discussed during BETT, specially with regards to Robobuilder.
I really enjoyed meeting you!
I got to demo the software I've written and also found some bugs that I will need to address.
The plan is now to hack the full protocol on the Robobuilder and have the PC talk to the servo bus through the serial port.
1)
iBot has explained to me that there is a special, undocumented packet that, when sent to Robobuilder, puts it into PC control mode (an orange light appears on the RBC controller).
We can see this happening when we connect Motionbuilder to the robot for example. Once you open the COM the orange light appears on the RBC and Motionbuilder talks directly to servos when you rotate the wheels on the screen.
According to iBot there is then a second undocumented packet that exits PC control mode and returns the RBC into normal mode.
I propose documenting as the next step to take.
2) After that's done, I really wanted to extend the DLL library so we can start talking to the servos directly. This shouldn't be too hard since we have the protocol for the servos (it's documented and posted on the forum).
3) The third challenge is actually find out how to connect sensors to the IO ports on each wCK and interface with them.
Each wCK has 1 analogue and one digital IO port (I think it's one of each) but the native software doesn't seem to have a way to use them.
Again, I would like to add support for these in the DLL library.
4) Finally I wanted to be able to have the library interface with the acceleration sensor.
According to iBot this may not be trivial so let's see.
I'm really enjoying this "hacking" of the robobuilder. I've always liked robotics and these low level communications but i've never actually done anything until I started working on robobuilder.
I hope I have "company" in this journey towards hacking the RB
