need help with ESD200
by l3v3rz
Fri Mar 20, 2009 7:44 pm
Got mine from Robosavvy today . 30 mins later - all working !!! The longest part was installing the BT drivers on Vista (BlueSolei)
For the soldering there aren't any instructions with the module - fortunately I found Joypad_Remote_Controller_KIT(RBX-BTCONT-01).pdf has all the details. With good pictures.
And as Joe says if you then a running the homebrew firmware its then pops up to tell you its 'idle' - (lazy robot).
cheers
For the soldering there aren't any instructions with the module - fortunately I found Joypad_Remote_Controller_KIT(RBX-BTCONT-01).pdf has all the details. With good pictures.
And as Joe says if you then a running the homebrew firmware its then pops up to tell you its 'idle' - (lazy robot).
cheers
by PedroR
Mon Mar 23, 2009 1:18 am
Replying to Joe, indeed if we happen to be sending a command to the BT module that has a meaning to the RBC that could pose a problem.
Maybe we could write some sort of "empty" firmware, that does nothing, to load into the RBC whenever we want to configure the Bluetooth module.
This way we can talk to the BT module without any interference for sure.
Once configuration is complete we can then upload the native firmware once again.
This is the extrema solution but I hope I will find the time to try and test all of this out.
I should be getting my BT module in the next days.
Maybe we could write some sort of "empty" firmware, that does nothing, to load into the RBC whenever we want to configure the Bluetooth module.
This way we can talk to the BT module without any interference for sure.
Once configuration is complete we can then upload the native firmware once again.
This is the extrema solution but I hope I will find the time to try and test all of this out.
I should be getting my BT module in the next days.
by PedroR
Tue Mar 24, 2009 1:50 am
Today was my turn to receive my Robobuilder bluetooth module 
I already soldered it in place. I'm definetelly not a guy that's into soldering but the whole process went much smoothly than I anticipated. Just inserted the headers, soldered (which went very well to my surprise!) and plugged the module in.
I am now in the process of running some tests and will post the process on the forum (with pictures!)
Needless to say the first test will be controlling the Robobuilder using the PS2 controller/software I wrote
In the process I took some pictures of the RBC board for all those who are curious
I already soldered it in place. I'm definetelly not a guy that's into soldering but the whole process went much smoothly than I anticipated. Just inserted the headers, soldered (which went very well to my surprise!) and plugged the module in.
I am now in the process of running some tests and will post the process on the forum (with pictures!)
Needless to say the first test will be controlling the Robobuilder using the PS2 controller/software I wrote
In the process I took some pictures of the RBC board for all those who are curious
by Joe
Tue Mar 24, 2009 4:47 am
I've found something very odd today.
When I have both the serial cable plugged in, and the ESD200 installed, and try to communicate with my robot over the serial cable, Strange Things happen. It appears that, under some circumstances (which I haven't fully pinned down), data sent out the serial port is being somehow looped back and seen by the RBC as input.
This quickly causes things to go haywire, and the message ERROR appears over and over again (probably reacting to the appearance of the word ERROR), even though no such string is found anywhere in my source code or the terminal app on my Mac.
If I disconnect the serial cable and communicate over BlueTooth instead, then this does not happen. So it's some weird interaction of the two.
EDIT: Yes, actually, sometimes it does. I just connected again, over BT with the serial disconnected, with the bot already in a mode that reports what inputs it sees. And I got "CONNECT 001F5BE0C349" surrounded by CRLF's.
It's late, and I'm tired and confused, but thought I'd mention it anyway — if anyone has any insight, please share. At the moment my hypothesis is that I failed to configure something properly on the ESD200, and I'll be opening my RBC up again (unless Pedro's idea of configuring it onboard works out!).
Best,
— Joe
When I have both the serial cable plugged in, and the ESD200 installed, and try to communicate with my robot over the serial cable, Strange Things happen. It appears that, under some circumstances (which I haven't fully pinned down), data sent out the serial port is being somehow looped back and seen by the RBC as input.
This quickly causes things to go haywire, and the message ERROR appears over and over again (probably reacting to the appearance of the word ERROR), even though no such string is found anywhere in my source code or the terminal app on my Mac.
If I disconnect the serial cable and communicate over BlueTooth instead, then this does not happen. So it's some weird interaction of the two.
EDIT: Yes, actually, sometimes it does. I just connected again, over BT with the serial disconnected, with the bot already in a mode that reports what inputs it sees. And I got "CONNECT 001F5BE0C349" surrounded by CRLF's.
It's late, and I'm tired and confused, but thought I'd mention it anyway — if anyone has any insight, please share. At the moment my hypothesis is that I failed to configure something properly on the ESD200, and I'll be opening my RBC up again (unless Pedro's idea of configuring it onboard works out!).
Best,
— Joe
by i-Bot
Tue Mar 24, 2009 10:47 am
Hi Joe,
Are you sure you are in mode 3 ? It looks like the BT is responding to AT commands, which should only be in mode 0.
On the idea of Pedro. Because the serial cable and BT and connected in parallel, then for the serial to talk direct to the BT module, then a cross over would be required on tx and rx. You could download special code to the RBC, run it to talk to configure the BT, then reload normal RBC code. It would not have the PC connection while configuring, so have to rely on buttons and LED.
Are you sure you are in mode 3 ? It looks like the BT is responding to AT commands, which should only be in mode 0.
On the idea of Pedro. Because the serial cable and BT and connected in parallel, then for the serial to talk direct to the BT module, then a cross over would be required on tx and rx. You could download special code to the RBC, run it to talk to configure the BT, then reload normal RBC code. It would not have the PC connection while configuring, so have to rely on buttons and LED.
by Joe
Tue Mar 24, 2009 4:55 pm
i-Bot wrote:Are you sure you are in mode 3 ? It looks like the BT is responding to AT commands, which should only be in mode 0.
Absolutely sure — I wouldn't be able to connect to it in mode 0 (it's only discoverable in mode 3). And I certainly am able to connect.
Also, I tried saying "AT" to it, and it did not respond (I had the same thought as you). But I agree that it does seem to be responding to some inputs, and its responses are being seen as additional inputs.
Best,
— Joe
by PedroR
Tue Mar 24, 2009 6:39 pm
Just FYI these are the instructions I received from the Robobuilder guys with regards to configuring the Parani ESD200.
They are for the graphical config tool but I'm sure you will be able tos ort out the equivalent AT commands.
To iBot: with regards to the use of a cross overcable, I don't really think you need this.
The PC RX -> RBC TX
PC TX -> RBC RX
Since the BT module is ORed with the RBC RX and TX I believe that, by default, (using the normal cable) you can talk to the BT module.
Am I correct?
They are for the graphical config tool but I'm sure you will be able tos ort out the equivalent AT commands.
To iBot: with regards to the use of a cross overcable, I don't really think you need this.
The PC RX -> RBC TX
PC TX -> RBC RX
Since the BT module is ORed with the RBC RX and TX I believe that, by default, (using the normal cable) you can talk to the BT module.
Am I correct?
by PedroR
Tue Mar 24, 2009 7:12 pm
SUCESS
My Robobuilder works like a charm over bluetooth using my COM library.
I just tested it using the little script I made available here:
http://robosavvy.com/forum/viewtopic.php?t=3269#19287
The robot is currently assembled as Doggy and I had my share of excitement!
The current version of my library relies on MSCOMM32.OCX to handle the COM port. It has a hard coded limit of 16 com ports (you can only open up to port 16). There is a hack to increase this limit that is available here: http://www.tek-tips.com/viewthread.cfm? ... 924&page=1
My Robobuilder works like a charm over bluetooth using my COM library.
I just tested it using the little script I made available here:
http://robosavvy.com/forum/viewtopic.php?t=3269#19287
The robot is currently assembled as Doggy and I had my share of excitement!
The current version of my library relies on MSCOMM32.OCX to handle the COM port. It has a hard coded limit of 16 com ports (you can only open up to port 16). There is a hack to increase this limit that is available here: http://www.tek-tips.com/viewthread.cfm? ... 924&page=1