Thanks for your help everyone!
It ended up being related to the PRIO-801 fault. We finally recieved the EtherCat manual from Fanuc, which showed that by enabling the "Error one shot" option under Menu > Setup > EtherCAT, would allow us to bypass the EtherCAT issue, and would subsequently stop the MCTL-003 error from appearing when runing in normal operation.
Yeah this is my first fanuc, so operator error is definitely possible. The only other active faults are the Deadman released fault, and PRIO 801 ethercat offline error, which is only a yellow fault. We are going to be using ethercat for a future integration, and from what Ive read it shouldn't be pulling up this fault.
That's normal. Set $DMAURST (deadman auto-reset) to true if you want the fault to reset when you pull in the deadman instead of requiring a push of the "reset" button.
Hey Titus,
From what I can tell, normal operation requires holding the deadman switch, then pressing reset, then holding shift, then jogging. If you release the shift button while jogging, you can press it in and continue moving as long as the deadman is still pressed. it appears $DMAURST allows you to skip pressing reset.
The issue that I am having is that if the reset and shift are not pressed at the same time every time, the MCTL-003 fault will appear. When I changed the $DMAURST variable, there was no change clearing the faults.
I may still be misunderstanding the documentation that I'm reading, but I don't think so.
Hey guys, I am trying to get a new M1000ia set up, and am encountering an issue. When trying to jog the robot, I always get a MCTL-003 system is in error status fault. I can press reset+shift and hold shift to bypass this, but the alarm always comes back. I am not at any limit switch, and DCS is not enabled. Does anyone know how to make sure this fault doesn't arise while running the robot?
