Diagnostics - Efb - ABB Johnson Controls AYK550-UH User Manual

1-202
Diagnostics – EFB
Fault queue for drive diagnostics
For general AYK550 diagnostics information, see
three most recent AYK550 faults are reported to the fieldbus as defined below. For
specific AYK550 fault codes, see
0401 Last Fault
0412 Previous Fault 1
0413 Previous Fault 2
Serial communication diagnostics
Network problems can be caused by multiple sources. Some of these sources are:
• Loose connections
• Incorrect wiring (including swapped wires)
• Bad grounding
• Duplicate station numbers
• Incorrect setup of drives or other devices on the network
The major diagnostic features for fault tracing on an EFB network include Group 53
EFB Protocol parameters 5306...5309. The
section describes these parameters in detail.
Diagnostic situations
The sub-sections below describe various diagnostic situations – the problem
symptoms and corrective actions.
Normal operation
During normal network operation, 5306...5309 parameter values act as follows at
each drive:
• 5306
properly received and addressed to this drive).
• 5307
message CRC is received).
• 5308
errors are detected, such as parity or framing errors).
• 5309
• BACnet protocol: 5316
token passed to this drive. (Does not apply for other protocols.)
Embedded fieldbus
Drive Parameter
advances (advances for each application message
EFB OK MESSAGES
does not advance at all (advances when an invalid
EFB CRC ERRORS
does not advance at all (advances when character format
EFB UART ERRORS
status value varies depending on network traffic.
EFB
EFB PAR
Diagnostics
Fault listing on page 1-282.
Protocol Reference
Modbus N2
40401 17
40402 18
40403 19
Complete parameter descriptions
16 (MS/TP token counter) advances for each
A 550-UH User's Manual
on page 1-281. The
FLN BACnet
90 AV18
91 AV19
92 AV20