I got a problem in which our fanuc robot (a M-170 with an RJ3 controller) got its jogging "disabled". The problem started suddenly after a boot, in which the pendant works fine for everything except when I turn on the pendant. The day before it was working fine and was able to edit some points in a program.
So the symptoms are as follow:
Before turning on the TP:
-Everything works perfectly with the pendant, I can run loaded programs. Has motion, the programs run correctly.
After turning on the TP (to jog):
-For some reason it always sends me to the macro menu after turning the pendant (no exceptions).
-Many keys become disabled (some numbers, some direction keys, some function keys).
-When I try to jog (with deadman, shift and an axis pressed) it simply sends one motion warning after another with no motion (JOG-007 and JOG-010)
Do you know if it could be software related? Or a global variable which causes this kind of "glitch"? Or do you know of a place which could check the TP or a trusty reseller?
The steps I already took where:
-Boot in cold start.
-Check if TP motion was enabled.
-Check if a program which disables motion was running.
-Tried to switch the pendant of a non-working robot, but they were unfortunetaly not compatible (A05B-2301-C301 HM1 vs A05B-2301-C371 HM2)
-Check if the TP switch was working