Siemens SINUMERIK 840D Diagnostics Manual page 643

10.04
Reactions:
Remedy:
Program Continuation:
380005
Parameters:
Definitions:
Reactions:
 Siemens AG, 2004. All rights reserved
SINUMERIK 840D/840Di/810D Diagnostics Guide (DA), 10.04 Edition
• 03 = DPM cycle status, DPM actual value status, DPM setpoint value status, DPM error
code
• 04 = DPM cycle error, DPM actual value status, DPM setpoint value status, DPM error
code
• 05 = client not registered, client number, max. number of clients, --
• 06 = synchronisation error, number of sync violation, --, --
• 07 = spinlock timeout, PLC spinlock, NCK spinlock
• Digit 1000 of the error cause = number of the affected bus
Alarm class: (see alarm 380 060)
The following can be primary causes:
• For error cause 01: Data transfer error on PROFIBUS DP
• For error cause 02, 03, 04: Error in contents of SDB1000
• For error cause 02, 03, 04, 05, 07: Corruption of parts of system program
• For error cause 06: The PCI bus cycle does not match the expected rate and synchroni-
zation is not possible for this reason. The correct PCI bus cycle must be entered.
The error can also be caused by a hardware problem on the MCI module.
- Channel not ready.
- NC Start disable in this channel.
- Interface signals are set.
- Alarm display.
• For error cause 01:
• Check the electrical and fault-related specifications for PROFIBUS DP, assess the cable
installation
• Check the terminating resistors of the PROFIBUS connectors (ON setting at end of
cable, otherwise OFF setting required)
• Check slave
• For error cause 02, 03, 04:
• Check SDB1000
• For error cause 02, 03, 04, 05:
• Follow the procedure described for troubleshooting alarm 380 001
• For error cause 06:
• The correct PCI bus cycle must be entered.
If the error cannot be eliminated by this procedure, please make a note of the error text
and contact the control system manufacturer.
Clear alarm with the RESET key. Restart part program
Profibus-DP: bus %3 access conflict, type %1, counter %2
%1 = Conflict type
%2 = Serial number within a conflict sequence
%3 = Number of the affected bus
An access conflict occurred on the PROFIBUS DP in cyclic mode: The NCK attempted to
write data to the bus or to read from the bus while cyclic data transfer was active. This can
lead to data integrity problems.
Type 1: Cyclic transfer has not finished on the PROFIBUS when the NCK attempts to
read data.
Type 2: The NCK has not finished writing data when cyclic transfer begins again. Counter
%2 contains a serial number starting at 1. A maximum of 10 alarms are output in succes-
sion. If no conflicts occur in a DP cycle, the counter is reset and new alarms are output
again on the next conflict.
- Alarm display.
1 Alarms
1-643