0813

Common Causes

• MCS channel cable or connector damaged, loose, or wired to the wrong station
• An inverter/MCS unit on the reported channel is not active or does not show the normal LED indication
• Network address/controller number conflict, address 0 traffic, or the NC seeing its own transmitted frame
• FCP board, inverter unit, or MCS software/protocol fault

Troubleshooting Steps

1. 1Read the code number shown with the alarm: code 1 = NC received a frame it had broadcast itself; YYYY is the received-frame information.; code 2 = A reply arrived from a station other than the slave that broadcast; YYYY is frame information.; code 3 = Received data length was two bytes or less; YYYY is always 0.; code 4 = Data came from a station other than the slave that sent it; YYYY is frame information.; code 5 = NC received its own non-broadcast transmission; YYYY is frame information.; code 6 = Data was received from network address 0; YYYY is frame information.; code 7 = No reception response within the allowed 1 s or 0.1 s, or SI was issued before any MCS on the link was active/powered; YYYY is 0.; code 8 = Transmission did not finish within 0.1 s; YYYY is 0.
2. 2Record the full XXXXYYYY code plus the character-string command name, channel number and network address before cycling power; also note any servo-link information shown at screen center.
3. 3Isolate power and let the drive DC bus discharge before touching hardware; if LED checks must be done live, have qualified personnel open the box and verify every MCS unit on the failed channel, with normal units indicating 22.
4. 4Inspect and reseat the MCS connection cable and connectors on the reported channel; look for bent pins, oil ingress, chafing, poor shield termination and routing beside motor/power cables.
5. 5Branch by XXXX: codes 1 or 5 mean the NC saw its own broadcast/transmission, so check for looped wiring or duplicated addressing; codes 2, 4 or 6 mean traffic came from the wrong slave or address 0, so verify controller numbers/network addresses; code 7 means no response after transmission or SI was issued before an MCS was ready, so check power sequence and that the station is online.
6. 6For codes 8, 9, A, B, C or D, treat it as a timing/protocol or error-status problem: confirm cable integrity first, then suspect FCP board, inverter unit or software; for code E decode YYYY high digits as 45 exception, 41 alarm, 57 warning or 54 error and use the low digits as the number.
7. 7Codes 100 through 106 point to a bad response format or attached data item for the SI/AS/ID command, and 200 means the data size did not match the ID definition; after wiring and station checks are clean, capture the alarm data and escalate as a software/MCS specification issue.