Have you guys seen this problem b4 ?
Have you guys seen this problem b4 ?
by UncleBob
Thu Sep 16, 2010 7:13 am
Hi guys I am getting this problem very very often. I think the controller might be faulty. Have any of you seen this before. Appreciate your help.
phpBB [media]
by billyzelsnack
Sat Sep 18, 2010 12:55 am
If I'm understanding what's going on.. It's probably the overload protection. I'm surprised this is the first time you've run across it. Supposedly there is a way to coax the servo back alive ( maybe setting torque limit to zero or something I can't remember ) without rebooting, but I've never been able to make it happen.
s
by UncleBob
Sun Sep 19, 2010 6:03 am
Symtom
1. Servos do not have red light
2. Happens when more servos are moving
3. Once happen, it is hard to make it go away
4. Put the controller in freezer helps
5. Only the communcation with PC does not work. Robotask will run if already in robot.
Probable solution.
Put limit on all servos (maybe some of them got stuck)
a. This seems to alleviate the problem but not completely. Maybe controller already damage.
b. Does not look like a fail safe feature.
c. Problem still occurs sometimes even without using it for long time, after switch on and off several times it is ok. Once ok, problem don't usually occur.
1. Servos do not have red light
2. Happens when more servos are moving
3. Once happen, it is hard to make it go away
4. Put the controller in freezer helps
5. Only the communcation with PC does not work. Robotask will run if already in robot.
Probable solution.
Put limit on all servos (maybe some of them got stuck)
a. This seems to alleviate the problem but not completely. Maybe controller already damage.
b. Does not look like a fail safe feature.
c. Problem still occurs sometimes even without using it for long time, after switch on and off several times it is ok. Once ok, problem don't usually occur.