3152

Common Causes

• Faulty MCS controller
• Faulty or corrupted NC/MCS software
• Noise or wiring problem on the NC-to-MCS communication path
• Corrupted servo data such as backlash, scale values or positioning data

Troubleshooting Steps

1. 1Read the code number shown with the alarm: code XX=04 = Self-diagnostic data has an error; ZZ is the received data.; code XX=06 = Software sync bit or format code of buffer A is wrong.; code XX=07 = Software sync bit or format code of buffer B is wrong.; code XX=08 = An error occurred in data communication.; code ZZ = Data kind: 1=speed command, 2=laser linear scale value, 3=backlash, 6=full-closed loop encoder value, 7=semi-closed loop encoder value, 8=ODIFF, 10=APA in divided stroke, etc.
2. 2Record the XXZZAAAA code: XX shows the error kind (04 self-diagnostic data error, 06 buffer A sync/format wrong, 07 buffer B sync/format wrong, 08 data communication error) and ZZ shows the data kind, such as 1 speed command, 3 backlash, 6 full-closed encoder value or 8 ODIFF.
3. 3Cycle power and note whether the same XX/ZZ combination returns on the same axis; a repeatable code points to one specific corrupted data item.
4. 4Check the servo link cables and connectors between the NC and the MCS/inverter units for looseness or noise-inducing routing near power cables.
5. 5Reload or verify the servo data file and NC software if a particular data kind (ZZ) is repeatedly flagged as wrong.
6. 6If the error survives cable and software checks, the MCS controller itself is faulty and must be exchanged; then re-initialize and home the affected axis.