PROFIBUS/PROFINET: Fault on drive

What does 380500 mean?

This alarm signals that a fault has been detected on a drive connected via PROFIBUS or PROFINET, and its fault memory contents have been reported. The alarm includes specific parameters: the drive identifier (%1), the fault code of the drive (%2), the fault value (%3), and the fault time (%4). This is a general indication of a drive-specific issue; the underlying fault must be diagnosed using the drive's own documentation to prevent process interruptions or damage to the drive.

• Internal fault within the connected drive itself (e.g., overcurrent, overvoltage, motor overload) causing it to report an error via PROFIBUS/PROFINET.
• Loss of control power (e.g., 24VDC) to the drive, resulting in a communication timeout or internal fault reported via the fieldbus.
• Incorrect PROFIBUS GSD file or PROFINET GSDML file used for the specific drive, leading to incompatible data exchange.
• Watchdog timeout on the drive's communication module due to excessive bus load or delayed responses from the PLC.
• Firmware issue within the drive's PROFIBUS/PROFINET communication interface.

Click steps to track your progress.

1. 1

   1. Identify the specific drive causing the fault using the drive identifier provided with the alarm, and then check its local display for detailed fault codes.

2. 2

   2. Use the engineering software (e.g., TIA Portal, Step 7) to read the fault buffer of the specified drive for a detailed explanation of its internal fault.

3. 3

   3. Verify the 24VDC control power supply at the drive's control terminals (e.g., X9, X10) using a multimeter.

4. 4

   4. Cross-reference the GSD/GSDML file version in the PLC project with the actual firmware version of the faulty drive's communication module.

5. 5

   5. Monitor the PROFIBUS/PROFINET communication status indicators (e.g., SF, BF LEDs) on the drive to confirm bus activity and data exchange.

6. 6

   6. Perform a drive reset via the engineering software or by cycling the drive's control power after addressing the underlying drive fault.