Odd CM-5 issue. Please assist.
Odd CM-5 issue. Please assist.
by AlphA
Fri Mar 07, 2008 8:54 am
As of yesterday, I am the proud owner of a Bioloid. I attempted to create the crossing gate as my first Bioloid project when I ran into an issue. After building the gate and downloading the CheckAssembly(Crossing Gate).bpg program to the CM-5, I played the program with the following output in the Behavior Control Programmer (version 1.32 from the Bioloid CD Version: 1.10 downloaded from Robotis.com).
[CM-5 Version 1.15]
<->PC:57142 BPS, <->Dynamixel:1000000 BPS
ID:<16>
001(0X01) Dynamixels Found.
ERROR:8100[0008:02]001 002 003 001
I updated the CM-5 with Bioloid_Ver115.hex, but doing so did not resolve the issue.
After checking the forum, I tried some of the remedies I found. I checked the cables, swapped cables and AX-12’s etc. Then, I read something about setting the baud rate. So, I fired up the Robot Terminal, connected to the CM-5 and when I put the CM-5 in to Manage Mode, Robot Terminal outputted the following:
#0sa835\,@;9{‘b0
At this point, I knew I was having a real issue. I tried a few different things in Robot Terminal and have yet to see it output anything intelligible. And, nothing I type shows up on the screen. However, the CM-5 does blink the TXD and RXD when I type. So, I know something’s going on in there. I thought it could be my USB to Serial interface, but when I tried everything again on another computer with an actual Serial port, the results were nearly identical.
If anyone can help me thought this issue, I would GREATLY appreciate it, as it looks as though I’ll be snowed in this weekend and I am looking forward to spending the bulk of my time getting acquainted with my Bioloid.
Thanks in advance.
[CM-5 Version 1.15]
<->PC:57142 BPS, <->Dynamixel:1000000 BPS
ID:<16>
001(0X01) Dynamixels Found.
ERROR:8100[0008:02]001 002 003 001
I updated the CM-5 with Bioloid_Ver115.hex, but doing so did not resolve the issue.
After checking the forum, I tried some of the remedies I found. I checked the cables, swapped cables and AX-12’s etc. Then, I read something about setting the baud rate. So, I fired up the Robot Terminal, connected to the CM-5 and when I put the CM-5 in to Manage Mode, Robot Terminal outputted the following:
#0sa835\,@;9{‘b0
At this point, I knew I was having a real issue. I tried a few different things in Robot Terminal and have yet to see it output anything intelligible. And, nothing I type shows up on the screen. However, the CM-5 does blink the TXD and RXD when I type. So, I know something’s going on in there. I thought it could be my USB to Serial interface, but when I tried everything again on another computer with an actual Serial port, the results were nearly identical.
If anyone can help me thought this issue, I would GREATLY appreciate it, as it looks as though I’ll be snowed in this weekend and I am looking forward to spending the bulk of my time getting acquainted with my Bioloid.
Thanks in advance.
by siempre.aprendiendo
Fri Mar 07, 2008 11:31 am
It's very odd... Do you have test it with other cables? Other serial cable and other AX+12+ to CM-5 cable... ¿with other AX12+ in the Manage mode?
If there is a damaged element, changing elements is usually a very effective method.
May be you should contact Robotis ...
If there is a damaged element, changing elements is usually a very effective method.
May be you should contact Robotis ...
by alzb92
Fri Mar 07, 2008 1:03 pm
Hi,
If you use USBDynamixel feasible and comes from a malfunction at this level. To ensure worry uses RS232 cable directly to the serial port and see if it works.
If you can not connect directly and that you use WinXP SP2, it is important that you do your testing on a WIN2000.
And if it works it will simply get left to return to the store Converter
Sorry for the English but it is a google translation ^ ^
If you use USBDynamixel feasible and comes from a malfunction at this level. To ensure worry uses RS232 cable directly to the serial port and see if it works.
If you can not connect directly and that you use WinXP SP2, it is important that you do your testing on a WIN2000.
And if it works it will simply get left to return to the store Converter
Sorry for the English but it is a google translation ^ ^
by AlphA
Fri Mar 07, 2008 4:09 pm
Do you have test it with other cables?
Yes, I have tried with different cables.
Other serial cable and other AX+12+ to CM-5 cable...
I have tried other AX-12+ to CM-5 cables.
The only serial cable I have is the one included with the kit.
¿with other AX12+ in the Manage mode?
Yes, I have tried many AX-12+ in manage mode.
May be you should contact Robotis ...
What is the best way to contact Robotis? I can not find an email.
To ensure worry uses RS232 cable directly to the serial port and see if it works.
Yes, I have tried connecting the CM-5 directly to the serial port on my PC via the Bioloid serial cable.
If you can not connect directly and that you use WinXP SP2, it is important that you do your testing on a WIN2000.
I do not have a WIN2000 computer. I tried running the Behavioral Control Programmer in compatibility mod for 2000, but it didn't help.
by alzb92
Fri Mar 07, 2008 4:20 pm
Quote:
To ensure worry uses RS232 cable directly to the serial port and see if it works.
Yes, I have tried connecting the CM-5 directly to the serial port on my PC via the Bioloid serial cable.
And ?
Do you use USBDynamixel ?
With Xp, port com meet problem...It's for this reason that purpose win2000 .
by AlphA
Fri Mar 07, 2008 5:01 pm
Do you use USBDynamixel ?
No. I do not own a USB2Dynamixel.
Have you contacted your vendor?
Yes. I am waiting to hear back from Alex at CrustCrawler Inc. Is CrustCrawler very responsive?
P.S. I've sent you a PM with a Robotis support email address
Thank you. I have sent an email regarding my issue.
by AlphA
Fri Mar 07, 2008 6:25 pm
I noticed that the serial COM port (in windows XP) would change when I physically plugged my USB to Serial adapter into a different USB port on my laptop. I noticed that the COM port is the first entry in the Robot Terminal v1.06.cfg file, which did not update after I had changed ports. So, I relocated the cfg file, thus forcing RobotTerminal to create a new one with the proper COM port. I assume it creates this config file once RobotTerminal successfully connects to the CM-5.
With the new config file created, I am able to use Robot Terminal to scan, search, dump... and I am even able to move the servo as desired via the GO command.
I don't believe this was the cause for my 8100 errors, but I have somehow made them stop also and everything seems to be functioning fine now. thanks for the help guys.
With the new config file created, I am able to use Robot Terminal to scan, search, dump... and I am even able to move the servo as desired via the GO command.
I don't believe this was the cause for my 8100 errors, but I have somehow made them stop also and everything seems to be functioning fine now. thanks for the help guys.