This is definitely an old-timer's sort of question
We're having difficulty with a servo that:
1) Sometimes it runs right.
2) Sometimes it goes nuts in the homing cycle and bottoms out.
3) And sometimes just runs for the hell of it.
The symptoms are:
1) When it runs ok, all three LEDs are on.
2) Bottoming out (overtravel) results in the loss of the "Drive Enabled" LED (as one would expect).
3) When it takes off unexpectedly, it actually turns ALL of the LEDs off, including the "Board OK" LED. When this happens, it requires cycling power to the rack to clear the fault.
The fault codes coming back from the APM are:
1) 02h (when it runs right). Meaning everything's okay.
2) 15h (when it goes into overtravel). Meaning that somebody requested a move while the servo was homing (which we did not do).
3) 52h (when it takes off by itself). Meaning that the system RAM is corrupt.
We've done the obvious, changing the card and the rack to no avail. Any suggestions?
Thanks!
We're having difficulty with a servo that:
1) Sometimes it runs right.
2) Sometimes it goes nuts in the homing cycle and bottoms out.
3) And sometimes just runs for the hell of it.
The symptoms are:
1) When it runs ok, all three LEDs are on.
2) Bottoming out (overtravel) results in the loss of the "Drive Enabled" LED (as one would expect).
3) When it takes off unexpectedly, it actually turns ALL of the LEDs off, including the "Board OK" LED. When this happens, it requires cycling power to the rack to clear the fault.
The fault codes coming back from the APM are:
1) 02h (when it runs right). Meaning everything's okay.
2) 15h (when it goes into overtravel). Meaning that somebody requested a move while the servo was homing (which we did not do).
3) 52h (when it takes off by itself). Meaning that the system RAM is corrupt.
We've done the obvious, changing the card and the rack to no avail. Any suggestions?
Thanks!