SINAMICS DCP
List Manual (LH21), 05/2016
429
4 Faults and alarms
4.2 List of faults and alarms
A01945 PROFIBUS: Connection to the Publisher failed
Drive object: All objects
Cause: For PROFIBUS peer-to-peer data transfer, the connection to at least one Publisher has failed.
Alarm value (r2124, interpret binary):
Bit 0 = 1: Publisher with address in r2077[0], connection failed.
...
Bit 15 = 1: Publisher with address in r2077[15], connection failed.
Remedy: - check the PROFIBUS cables.
- carry out a first commissioning of the Publisher that has the failed connection.
See also: r2077 (PROFIBUS diagnostics peer-to-peer data transfer addresses)
F01946 (A) PROFIBUS: Connection to the Publisher aborted
Drive object: All objects
Cause: At this drive object, the connection to at least one Publisher for PROFIBUS peer-to-peer data transfer in cyclic
operation has been aborted.
Fault value (r0949, interpret binary):
Bit 0 = 1: Publisher with address in r2077[0], connection aborted.
...
Bit 15 = 1: Publisher with address in r2077[15], connection aborted.
Remedy: - check the PROFIBUS cables.
- check the state of the Publisher that has the aborted connection.
See also: r2077 (PROFIBUS diagnostics peer-to-peer data transfer addresses)
F01950 (N, A) PB/PN clock cycle synchronous operation synchronization unsuccessful
Drive object: All objects
Cause: Synchronization of the internal clock cycle to the global control telegram has failed. The internal clock cycle exhibits
an unexpected shift.
Remedy: Only for internal Siemens troubleshooting.
Note:
PB: PROFIBUS
PN: PROFINET
F01951 CU SYNC: Synchronization application clock cycle missing
Drive object: All objects
Cause: If DRIVE-CLiQ components with different application clock cycle are operated on a DRIVE-CLiQ port, this requires
synchronization with the Control Unit. This synchronization routine was unsuccessful.
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
Remedy: - carry out a POWER ON (power off/on) for all components.
- upgrade the software of the DRIVE-CLiQ components.
- upgrade the Control Unit software.
Note:
If a Controller Extension is being used (e.g. CX32, NX10), then the following applies:
Check whether the Controller Extension is issuing error messages, and if required, remove these.
F01952 CU DRIVE-CLiQ: Synchronization of component not supported
Drive object: All objects
Cause: The existing system configuration requires that the connected DRIVE-CLiQ components support the synchronization
between the basic clock cycle, DRIVE-CLiQ clock cycle and the application clock cycle.
However, not all DRIVE-CLiQ components have this functionality.
Fault value (r0949, interpret decimal):
Component number of the first faulty DRIVE-CLiQ component.
Remedy: Upgrade the firmware of the component specified in the fault value.
Note:
If required, also upgrade additional components in the DRIVE-CLiQ line.
Siemens Parts
To Next Page
Loading...
