Technical data

56 OM 1191
Embedded Fieldbus
Diagnostics – EFB
Fault Queue for Drive Diagnostics
For general MD5 diagnostics information, see Diagnostics on
page 74. The three most recent MD5 faults are reported to
theeldbusasdenedbelow.ForspecicMD5faultcodes,
see Table 53: Fault Listing on page 75.
Table 33: MD5 Faults
Drive Parameter
Protocol Reference
Modbus N2 FLN BACnet
0401 Last Fault 40401 17 90 AV18
0412 Previous Fault 1 40402 18 91 AV19
0413 Previous Fault 2 40403 19 92 AV20
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Completeparameterdescriptions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 EFB OK MESSAGES advances (advances for each
application message properly received and addressed to
this drive).
• 5307 EFB CRC ERRORS does not advance at all
(advances when an invalid message CRC is received).
• 5308 EFB UART ERRORS does not advance at all
(advances when character format errors are detected,
such as parity or framing errors).
• 5309EFBstatusvaluevariesdependingonnetwork
trafc.
• BACnet protocol: 5316 EFB PAR 16 (MS/TP token
counter) advances for each token passed to this drive.
(Does not apply for other protocols.)
Loss of Communication
The action taken by the MD5, if communication is lost, is
conguredinCommunicationfault.Theparametersare3018
COMMFAULTFUNCand3019COMMFAULTTIME.
The Complete parameter descriptions section on page 1-80
describes these parameters.
No Master Station On Line
If no master station is on line: Neither the EFB OK
MESSAGES nor the errors (5307 EFB CRC ERRORS and
5308 EFB UART ERRORS) increase on any of the stations.
To correct:
• Check that a network master is connected and properly
programmed on the network.
• Verify that the cable is connected, and is not cut or short
circuited.