Error 8100 after CM5 Update
Error 8100 after CM5 Update
by Merlin
Mon Apr 27, 2009 2:57 am
Dear folks
Today I have updated my CM5 to 115 version hex file, using the Behavior Control Program, as the User guide indicates.
Just after the update process, which end without problem reported (CM5 Updated succefully was the final message....) the CM5 gives an 8100 error message when I try to run any program. All of this programs runs perfectly before the upgrade...even the example programs don't work, I the CM5 gives the same 8100 error.
Do you have any idea how to solve this? Pls help me, I have the robot for almost 4 years and this is my very serious problem (also my very first upgrade process....)
Any advice could help, thanks
merlin
Today I have updated my CM5 to 115 version hex file, using the Behavior Control Program, as the User guide indicates.
Just after the update process, which end without problem reported (CM5 Updated succefully was the final message....) the CM5 gives an 8100 error message when I try to run any program. All of this programs runs perfectly before the upgrade...even the example programs don't work, I the CM5 gives the same 8100 error.
Do you have any idea how to solve this? Pls help me, I have the robot for almost 4 years and this is my very serious problem (also my very first upgrade process....)
Any advice could help, thanks
merlin
by Merlin
Mon Apr 27, 2009 4:30 am
A few hours ago I posted this message here. In the meantime I was debugging the issue and I have found the response for this case in particular.
As I said, the problem begins after an Upgrade process to CM5. Unfortunately, during the uograde process it was connected one of my AX-12 to the CM5 unit...after a debug with Robot terminal I was realized that during the upgrade the AX-12 auto-changed the ID number from 5 to 000.
This 000 number was the cause of the rest of the problems after the upgrade and also it cause the 8100 error message.
I replaced this wrong ID number to the original ID and the things appears to be normal at this time.
I am posting again because can help another guy with the same problem.
Thanks
merlin
As I said, the problem begins after an Upgrade process to CM5. Unfortunately, during the uograde process it was connected one of my AX-12 to the CM5 unit...after a debug with Robot terminal I was realized that during the upgrade the AX-12 auto-changed the ID number from 5 to 000.
This 000 number was the cause of the rest of the problems after the upgrade and also it cause the 8100 error message.
I replaced this wrong ID number to the original ID and the things appears to be normal at this time.
I am posting again because can help another guy with the same problem.
Thanks
merlin