Faults and alarms
List of faults and alarms
3-1234
© Siemens AG 2012 All Rights Reserved
SINAMICS S110 List Manual (LH7), 06/2012, 6SL3097-4AP10-0BP3
Alarm value (r2124, interpret decimal):
Alarm number.
Note:
If required, the significance of this new alarm can be read about in a more recent description of the Control Unit.
Remedy: - replace the firmware on the Sensor Module by an older firmware version (r0148).
- upgrade the firmware on the Control Unit (r0018).
Reaction upon F: NONE (IASC/DCBRAKE, OFF1, OFF2, OFF3, STOP1, STOP2)
Acknowl. upon F: IMMEDIATELY (POWER ON)
Reaction upon N: NONE
Acknowl. upon N: NONE
A50001 (F) PROFINET configuration error
Message value: %1
Drive object: CU_S110-CAN, CU_S110-DP, CU_S110-PN
Reaction: NONE
Acknowledge: NONE
Cause: A PROFINET controller attempts to establish a connection using an incorrect configuring telegram. The "Shared
Device" function has been activated (p8929 = 2).
Alarm value (r2124, interpret decimal):
10: A CPU sends a PROFIsafe telegram.
11: F CPU sends a PZD telegram.
12: F CPU without an A CPU.
13: F CPU with more PROFIsafe subslots than activated with p9601.3.
14: F CPU with fewer PROFIsafe subslots than activated with p9601.3.
See also: p8929 (PN remote controller number), p9601 (SI enable, functions integrated in the drive (processor 1))
Remedy: Check the configuration of the PROFINET controllers as well as the p8929 and p9601.3 setting.
Reaction upon F: NONE
Acknowl. upon F: IMMEDIATELY
A50020 (F) PROFINET: Second controller missing
Message value: -
Drive object: CU_S110-CAN, CU_S110-DP, CU_S110-PN
Reaction: NONE
Acknowledge: NONE
Cause: The PROFINET function "Shared Device" has been activated (p8929 = 2). However, only the connection to a PRO-
FINET controller is present.
See also: p8929 (PN remote controller number)
Remedy: Check the configuration of the PROFINET controllers as well as the p8929 setting.
Reaction upon F: NONE
Acknowl. upon F: IMMEDIATELY
F50510 FBLOCKS: Logon of the run-time group rejected
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: When the run-time groups of the free function blocks attempted to log on with the sampling time management, the
logon of at least one run-time group was rejected.
Too many different hardware sampling times may have been assigned to the free function blocks.
See also: r20008 (Hardware sampling times available)
Remedy: - check number of different hardware sampling times (r20008, r7903).
- if necessary, deactivate again the drive object on which the function module "free function blocks" was last activated
(p0108[0...15].18 = 0). Then carry out a POWER ON.
Note:
The assignment of drive object numbers to the index numbers of p0108[0...15] can be read out in p0101[0...15]; the
assignment to the drive object types can be read out in p0107[0...15] on the drive object of the CU or CX (only with
SM150).
To Next Page
Loading...
