connection to CM-5 issue
connection to CM-5 issue
by darwinn
Mon Apr 18, 2011 2:36 pm
Hi there,
I started using bioloid robots for univ. classes in robotics some time ago. Students have 4 Bioloid Comprehensive Robot Kit in the lab. It worked quite well, but one CM-5 recently broke and I cannot make it work.
It powers on, I can run a program that is downloaded in it, I can charge it, but I cannot have it connected to the PC. Whenever I try to connect (on correct COM) I receive message: "Unable to connect to CM-5". If I try to connect in terminal having pressed "#" on the screen it shows nothing. But it connects somehow - I can download a new firmware without any problem, whenever I hit something on the keyboard, RXD led lights up. I'm not receiving any feedback from CM5 though. In bioloid BehaviorControl software I cannot connect at all.
Can someone tell me how to verify what happened and what can I do with it? I already thought of exchanging AVR (someone told me, there is only some number of times programs can be written into it, after that - dead...), but I would not like to do that anyway.
Thx,
Darwin
I started using bioloid robots for univ. classes in robotics some time ago. Students have 4 Bioloid Comprehensive Robot Kit in the lab. It worked quite well, but one CM-5 recently broke and I cannot make it work.
It powers on, I can run a program that is downloaded in it, I can charge it, but I cannot have it connected to the PC. Whenever I try to connect (on correct COM) I receive message: "Unable to connect to CM-5". If I try to connect in terminal having pressed "#" on the screen it shows nothing. But it connects somehow - I can download a new firmware without any problem, whenever I hit something on the keyboard, RXD led lights up. I'm not receiving any feedback from CM5 though. In bioloid BehaviorControl software I cannot connect at all.
Can someone tell me how to verify what happened and what can I do with it? I already thought of exchanging AVR (someone told me, there is only some number of times programs can be written into it, after that - dead...), but I would not like to do that anyway.
Thx,
Darwin
by Fritzoid
Mon Apr 18, 2011 3:37 pm
Sounds like a communications problem on USART1!
darwinn said
If that is the case, then the hardware is OK and you can talk to the bootloader at 56Kbs. The problem is probably related to how the firmware you are downloading is configuring USART1.
Where did you get this "firmware?"
darwinn said
I can download a new firmware without any problem
If that is the case, then the hardware is OK and you can talk to the bootloader at 56Kbs. The problem is probably related to how the firmware you are downloading is configuring USART1.
Where did you get this "firmware?"
by PedroR
Mon Apr 18, 2011 5:33 pm
Hi
To add to Fritzoid's excelent reply I would like to enphasize the following:
1) If you can download a firmware then the Bootloader is fine and it means the whole set of USART, cable/communication is physically OK and working.
2) To use Behaviour Control Program you need to install the standard firmware from Robotis. Otherwise you will always get those communication errors.
Also for the Terminal to work and respond as documented on the manual you need to be using the standard firmware from Robotis.
For the CM5 you can use the Behaviour Control program (with the correct firmware) - OR - you can use the new Roboplus.
Instructions on how to use Roboplus with your Bioloid can be found here http://support.robotis.com/en/product/b ... e.htm#bc-1
Following those instructions will automatically install the correct firmware on the Robot to work with Roboplus.
To add to Fritzoid's excelent reply I would like to enphasize the following:
1) If you can download a firmware then the Bootloader is fine and it means the whole set of USART, cable/communication is physically OK and working.
2) To use Behaviour Control Program you need to install the standard firmware from Robotis. Otherwise you will always get those communication errors.
Also for the Terminal to work and respond as documented on the manual you need to be using the standard firmware from Robotis.
For the CM5 you can use the Behaviour Control program (with the correct firmware) - OR - you can use the new Roboplus.
Instructions on how to use Roboplus with your Bioloid can be found here http://support.robotis.com/en/product/b ... e.htm#bc-1
Following those instructions will automatically install the correct firmware on the Robot to work with Roboplus.
Bioloid on one feet.
by MOHIT JINDAL
Wed Apr 20, 2011 6:14 am
Hi;
Can any have the motion code to stand the Bioloid on One Feet
Thanks.
Can any have the motion code to stand the Bioloid on One Feet
Thanks.
by darwinn
Wed Apr 20, 2011 10:52 am
I downloaded the firmware from Robotis website (Bioloid v115.hex). It is also the same which is at http://www.tribotix.info/Downloads/Robo ... m#Firmware . This software is downloded also on the other three bioloids and it works.
I work also with original software given with robots, so Robotis Behavior Control. I would not like to shift to Roboplus yet - it is a lot of work to prepare classes and changing the software can be made only during the sumer break.
If FW is OK, and hardware is OK, then what...? nothing?:P
Ok, let me think from the beginning - what is an indicator, that the firmware has been SUCCESSFULLY downloaded into CM5? Because this is the reason for stating, that the hardware is OK... I made a test and in robot terminal launched transmitting the file (firmware) without CM5 connected at all - it showed progress and 100% transmitted... So my stating that the firmware was downloaded correctly is not necessarily correct:)
How to verify this then?
I work also with original software given with robots, so Robotis Behavior Control. I would not like to shift to Roboplus yet - it is a lot of work to prepare classes and changing the software can be made only during the sumer break.
If FW is OK, and hardware is OK, then what...? nothing?:P
Ok, let me think from the beginning - what is an indicator, that the firmware has been SUCCESSFULLY downloaded into CM5? Because this is the reason for stating, that the hardware is OK... I made a test and in robot terminal launched transmitting the file (firmware) without CM5 connected at all - it showed progress and 100% transmitted... So my stating that the firmware was downloaded correctly is not necessarily correct:)
How to verify this then?
by Fritzoid
Wed Apr 20, 2011 11:35 am
Hi darwinn,
The key question here is whether you can communicate to the boot loader in the CM-5 or not. You can determine this using a terminal program like RoboPlus Terminal or HyperTerminal in Windows.
First configure the COMM port in your terminal program using a speed of 56Kb and parity at 8N1.
Next connect to the CM-5. You won't get any response but it will open the COMM port on your computer.
If the CM-5 isn't turned off already turn if OFF now.
Next, hold down the shift and the # keys while you turn on the CM-5 (with your other hand).
You should get the boot loader message displayed at this point. If so, your hardware is OK. If you are using RoboPlus Terminal you can use the LD command to download the new firmware (.hex file).
If you don't see the boot loader message after a second or two then there is a hardware problem. You might want to open the thing up and have a look at the connections around the serial jack.
Good luck!
The key question here is whether you can communicate to the boot loader in the CM-5 or not. You can determine this using a terminal program like RoboPlus Terminal or HyperTerminal in Windows.
First configure the COMM port in your terminal program using a speed of 56Kb and parity at 8N1.
Next connect to the CM-5. You won't get any response but it will open the COMM port on your computer.
If the CM-5 isn't turned off already turn if OFF now.
Next, hold down the shift and the # keys while you turn on the CM-5 (with your other hand).
You should get the boot loader message displayed at this point. If so, your hardware is OK. If you are using RoboPlus Terminal you can use the LD command to download the new firmware (.hex file).
If you don't see the boot loader message after a second or two then there is a hardware problem. You might want to open the thing up and have a look at the connections around the serial jack.
Good luck!