Error code 412 MPG1 ENCODER ERROR

[repauli1]

Win 10, M400 Ser#A900863


I finished this retrofit a few months ago, customer pickd up router about 3 months ago.

I went out to start it up yesterday. When I press cycle start it throw this fault.

I tried a second Wireless MPG, no difference

I checked USB hub and connection inside console.

Attached is a report. I would like to go back there in the morning so hopefully you can look and advise today yet.

If need be I can get Teamviewer up with a phone call.

Thanks

Bob

[cncsnw]

Does the MPG actually work just fine?

If so, there is nothing that needs to be done about it. While a "412 ... differential error" is a fault if it affects a servo axis or spindle encoder, it is not a fault -- just informational -- if it affects an MPG handwheel.

As far as I can tell, systems with wireless MPGs often display a 412 message on startup, even if the MPG is present, connected, turned on, and working.

[repauli1]

It stops, and will not allow a reset and cycle start

[cncsnw]

Then there is some other fault present, not related to the MPG encoder error.

Post a complete report (the .zip file, not just the .txt file) so we can see what changes were made to the PLC programming, and what messages are in the message log.

Use the Alt-i display to check the status of MEM46 - MEM57 immediately after you release the emergency stop button.

[repauli1]

I did attach a report, I also emailed it, and the issue. I really need to get this resolved asap.
Thanks
BOB

[repauli1]

Attached, didn't realize it was a .txt sorry

[cncsnw]

Can you post a picture of the Alt-i display, immediately after you release the Emergency Stop button?

If you are certain that the only issue is related to the wireless MPG and its 412 encoder error, you can simply change Parameter 218 to zero and restart the control, then verify that everything (else) works correctly again.

[cncsnw]

You seem to have a lot of outputs forced on and off. You should review each forced output, then correct the PLC logic so that output forcing is not required.

Other than as a brief test of your contact coil circuit, forcing OUT1 on is never the solution to a cannot-clear-faults problem. The control still won't run, because the PLC will still be reporting a fault condition.

If you do not have a lube system with a float switch connected, it is better to invert INP9 than to force it. In your particular case, assuming there is no lube system at all and never will be, it probably doesn't matter. In general though, inversion is less error-prone than forcing.

If your machine has no spindle orientation requirement or capability, it would be better to delete the orientation logic from the PLC program and the M6 macro, than to hope to get around it by forcing INP17.

Other than the attempt to force OUT1 on, none of the forced outputs seem to have any immediate bearing on your current issue, if indeed that issue is that you cannot clear faults by pressing and releasing emergency stop; and cannot jog axes or run any auto cycle because there is still a fault condition present.

For that, the next step would be to look at MEM46 - MEM57 on the Alt-i display.

[martyscncgarage]

Did you follow Tech Bulletin 313 in setting up your wireless MPG?
WHICH Cenroid wireless MPG do you have, the newest one? WMPG?

Your parameters do not look correct for a Centroid Wireless MPG
TB313 is attached for reference
Also, it appears you are using version 4.14 software, which I believe requires a software unlock for Wireless MPG
Any reason why you are not on the latest version of software?

Just some suggestions
Marty