A Mazak T32 controller can successfully send or display programs through a PC connection yet fail when receiving a program. In the reported case, loading from CIMCO software produced CMT misconnected alarm 515. The controller alarm description identifies two possible fault domains: an incorrectly connected cable or an incorrect communication parameter.
Interpret Error 515 Correctly
Successful saving and viewing confirm that part of the connection works, but they do not prove that the controller's receive path, handshake arrangement, and receive-related parameters are correct. Treat alarm 515 as a direction-specific communication fault until both the cable and controller configuration have been checked.
| Observed operation | Result | What it establishes |
|---|---|---|
| Save programs to the PC | Works | The controller can transfer data in that direction. |
| View stored programs through the connection | Works | Some cable conductors and communication settings are functional. |
| Load programs into the T32 | Alarm 515 | The receive transaction still has a cable, handshake, or parameter mismatch. |
Check the Cable and Handshake
The evidence identifies a fully populated cable as a possible source of the fault and recommends testing a three-conductor cable with the handshake signals jumpered. Do not assume the existing cable is correct merely because outbound transfers work; a conductor or handshake path used only during loading can still be wrong.
- Record the current cable connections before changing them.
- Verify the cable against the required T32-to-PC connection at both ends.
- If the present cable is fully populated, test the supported three-conductor arrangement with handshake jumpered.
- Retry a controller receive operation and note whether alarm 515 returns.
Verify Communication Parameters
Compare the T32 communication parameters with the matching settings in CIMCO. The evidence does not provide parameter identifiers or required values, so do not enter guessed values. Document the existing settings first, then use the controller documentation for the installed configuration to identify and correct only confirmed mismatches.
Verify the repair by loading a known saved program into the controller. Confirm that alarm 515 does not occur and that the received program can be opened and reviewed on the T32. If the alarm remains, separate the diagnosis by testing the cable arrangement and parameter configuration independently.
FAQ
What does Mazak T32 error 515 mean?
Error 515 is the CMT misconnected alarm. The cited alarm description points to either a misconnected cable or an incorrectly set communication parameter.
Why can my Mazak T32 save programs but not load them?
Working outbound transfers prove only part of the connection. Loading can still fail because the receive wiring, handshake arrangement, or matching communication parameters are incorrect.
What cable change can help diagnose T32 alarm 515?
If the current cable is fully populated, test the documented three-conductor arrangement with handshake signals jumpered. Record the original wiring and verify the required pin connections before making changes.