These notes contain important information for the installation and use of SINAMICS S110 V4.1 software. The document lists various issues that may occur and possible workarounds to address them. It is recommended to carefully read these notes before configuring or operating the software.

1. General conditions and function limitations, notes for configuration and operation
These notes take precedence over statements contained in other documents.
Because these notes contain important information for the installation and use of the software, please read them carefully.
SINAMICS S110 V4.1 incl. SSP for STARTER
SIEMENS SINAMICS S110 V4.1
incl. SSP for STARTER
ARTSPlusRQ Brief description Description Possible work-around
SINAMICS_SW - General
AP00316750 Changing the motor in the expert list Another motor may only be selected via the drive wizard. Changing the
motor code in the expert list can result in inconsistencies in the STARTER
displays.
---
AP00325763 The information for rated current and
rated power of the PM340 power
module in the drive wizard can
deviate from the catalog data in some
cases.
The information for rated current and rated power of the PM340 power
module in the drive wizard can deviate from the catalog data in some cases.
Select the power module by MLFB when using
the drive wizard for commissioning
AP00330263 The information for the power unit
duty cycles in indices 1 to 4 of
parameters r0206, r0207 und r0209
in the expert list are not displayed
correctly in some cases. The value in
index 0 is applicable.
The information for the power unit duty cycles in indices 1 to 4 of
parameters r0206, r0207 und r0209 in the expert list are not displayed
correctly in some cases. The value in index 0 is applicable.
none
AP00394976 When a PM340 power module is
inserted onto another CU305, the
runtime meter of the power unit fan
is reset to 0.
When a PM340 power module is inserted onto another CU305, the runtime
meter of the power unit fan is reset to 0.
None
AP00490745 The number of permissible places
after the decimal point is not taken
into account for scripting.
With scripts, it is possible to write a parameter with more places after the
decimal point than permitted or displayed in the screens. This can result in
an inconsistency between the actual value set in the drive and the display in
STARTER. These differences cannot be displayed through a comparison of
lists.
Take the number of permissible places after the
decimal point into account in the script. See
expert list.
AP00718943 Saving is rejected directly after
correcting warning A:1420
(Topology: Comparison: One
component different).
1) The topology error A:1420 (Topology: Comparison: One component
different) is present during ramp-up.
2) After correction of A:1420 and while the system is still ramping up (r002
<> 0), STARTER immediately attempts to save. A message appears that the
saving operation has failed.
3) The system continues to ramp up. Saving can be performed after
completion of the ramp-up (r002 = 0).
Acknowledge the message and wait until r002
= 0. Then save.
AP00729186 Alarms on the control unit that do not
result in a shutdown response, are not
visible when the first servo or vector
DO has been deactivated via p105.
Alarms on the control unit that do not result in a shutdown response, are not
visible when the first servo or vector DO has been deactivated via p105.
The alarms can be viewed in the alarm history
r945 to r949.
AP00748695 When using a SafeBrake relay, and in
the case of automatic configuration
and reset to factory setting, the motor
holding brake may not be detected
from time to time.
When using a SafeBrake relay, and in the case of automatic configuration
and reset to factory setting, the motor holding brake may not be detected
from time to time. This means that, when switching on the drive, the brake
remains locked. For this reason, parameter p1215 = 0 "Motor Holding Brake
Configuration" remains and error message F7935 "Drive: Motor Holding
Brake Detected" is not triggered.
The motor holding brake must be manually
configured via parameter p1215 = 1.
SINAMICS_SW - EPOS
AP00517160 Modulo rotary axis in MDI
operation, absolute, edge-triggered
positioning with direction
specification: If several starting
edges are specified during the
braking phase, the axis turns an extra
modulo revolution after reaching the
target position.
Modulo rotary axis in MDI operation, absolute, edge-triggered positioning
with direction specification: If several starting edges are specified during the
braking phase, the axis turns an extra modulo revolution after reaching the
target position.
Only specify a new starting edge after the
feedback message "Target position reached"
r2684.10 = 1.
AP00734501 If the "Basic positioner" function
module is used on the S110, the
number of blocks that can be used is
restricted when using the "Free
function blocks" function module.
If the "Basic positioner" function module is used on the S110, the number of
blocks that can be used is restricted when using the "Free function blocks"
function module. The reason is that there is less residual computation time.
During simultaneous use of the "Basic
positioner" and the "Free function blocks"
function modules, 23 blocks (one of each block
type) can be calculated in 16 ms. 23 blocks can
be calculated in 4 ms when the "Basic
positioner" function module is not activated. If
a shorter sampling time is set, this reduces the
remaining computation time, so that, e.g. only
3 blocks can be calculated in 2 ms with "Basic
positioner". When the remaining computation
time is not sufficient, F1205 is triggered.
SINAMICS_SW - General communication
AP00524709 For a BICO interconnection with
p2050 to drive object 1, there is no
normalizing of the received process
data to 4000h.
For a BICO interconnection with p2050 "CO: IF1 PROFIdrive PZD received
word" to DO 1 (CU), there is no normalizing of the received process data to
4000h. This occurs, for example, for an interconnection to the torque limits
p1522 and p1523:
If p1522 or p1523 of the drive is interconnected to p2050 of the drive, there
is a normalizing to 4000h during the determination of the torque.
If p1522 or p1523 of the drive is interconnected to p2050 of the CU, there is
no normalizing to 4000h during the determination of the torque
(normalizing: 1 corresponds to 100% torque).
There is no explicit information about this varying behavior in the
STARTER dialog boxes.
Do not transfer process data via drive object 1.
17.12.2008SINAMICS_S110_V41_Restrictions.pdf

2. SIEMENS SINAMICS S110 V4.1
incl. SSP for STARTER
ARTSPlusRQ Brief description Description Possible work-around
SINAMICS_SW - CAN communication
AP00326015 CAN command "Restore" does not
conform with CANopen.
In contrast to the CANopen specification, the "Restore all parameters" or
"Restore communication parameters" command is executed as follows for
the SINAMICS: After writing object 0x1011, subindex 1 or 2, the
corresponding objects are set to their default values directly in the RAM. If
the "Reset node" or "Reset communication parameters" is transmitted, the
values of the objects still saved on the CF card are loaded to the RAM again.
The SINAMICS is now configured again as it was before the Restore
commands.
If the SINAMICS is to ramp up with its default
values after Power OFF/ON or "Reset", the
default values must be saved to the CF card via
object 0x1011 after writing object 0x1010. If it
is sufficient to have the default values only in
the RAM, only object 0x1011 has to be
written. After a reconfiguration has been
performed, the values can be written to the CF
card with object 0x1010.
AP00703561 The CANopen status word displays
error F8701 shortly after the NMT
command "Reset communication"
although it has been automatically
acknowledged.
The CU305CAN is in the CANopen drive state "Operation enable". The
motor turns. The NMT command "Reset communication" is issued. After the
boot-up message, there is an immediate change to the NMT status
"OPERATIONAL". The error bit of the CANopen status word still displays
error F8701 for one cycle although this has been automatically
acknowledged.
Delay the "OPERATIONAL" command after
the "Reset communication" command for three
CAN cycles or ignore the error bit in the first
cycle after switching to OPERATIONAL.
SINAMICS_SW - PROFIBUS communication
AP00334540 Diagnostics display for message
frame 110 incomplete.
PZD MDI_vel and MDI_decc are missing in the diagnostics display for
PROFIBUS message frame 110.
---
AP00744750 During an interruption of the
PROFIBUS connection between the
control unit (PROFIBUS master) and
the drive unit (unplug DP plug from
control unit) and simultaneous
(online) link with the STARTER,
error message F30662 (error with
internal communications) is
sporadiacally output.
During an interruption of the PROFIBUS connection between the control
unit (PROFIBUS master) and the drive unit (unplug DP plug from control
unit) and simultaneous (online) link with the STARTER, error message
F30662 (error with internal communications) is sporadiacally output.
Error message F30662 (error with internal
communications) can be acknowledged only
through a power ON of the control unit.
AP00744833 STARTER (online) link hardly
possible if configured PROFIsafe
address not correct.
STARTER (online) link hardly possible if the configured PROFIsafe
addresses of PROFIsafe master and drive unit do not match.
Switch off or disconnect PROFIsafe master
until PROFIsafe addresses have been corrected
in the drive. The PROFIsafe addresses
(p9610/9810) in the drive must match the
address parametrized in the PROFIsafe master.
AP00745858 The functionality "Differentiating
encoder errors via PROFIBUS" is not
supported.
In the case of integrated encoder evaluation for the control unit CU305 and
SMC30 (MLFB: 6SL3055-0AA00-5CA2), the functionality "Differentiating
encoder errors via PROFIBUS" is not supported. In parameter r483 "CO:
The actual encoder position value Gn_XIST2 / Geb Gn_XIST2" is,
therefore, always shown as an error code with value 1 = encoder error if an
error message is reported.
None.
SINAMICS_SW - Closed-loop control
AP00522164 When using a synchronous motor
with selected pole position
identification and incremental
encoder with zero mark, but without
absolute position (without C/D track,
not EnDat encoder), the
'commutation with zero mark' (fine
synchronization) is not automatically
activated via p404.15.
When using a synchronous motor with selected pole position identification
and incremental encoder with zero mark, but without absolute position
(without C/D track, not EnDat encoder), the 'commutation with zero mark'
(fine synchronization) is not automatically activated via p404.15.
The fine synchronization must be manually
configured with the following sequence: p0010
= 4 (encoder commissioning) p0400 = 9999
(user-defined) p0404.15 = 1 (commutation
with zero mark)
AP00660609 No track monitoring with listed TTL
encoders
In the selection of a TTL encoder from the encoder list (e.g. p0400 = 3002),
the track monitoring (p0405 bit 2) is switched off.
The track monitoring can be subsequently
switched on with
p0010 = 4
p0400 = 9999
p0405.2 = 1
p0010 = 0
AP00719118 The configuration of the motor
holding brake p1215 is changed after
the parameter download for drives
with SMI components.
If during the STARTER commissioning, the brake of a drive with SMI
components is set to "Motor holding brake always open" (see p1215), the
value is reset to "Motor holding brake acc. to sequential control" in the drive
after the parameter download.
p1215 can be set directly to the desired value
after the download.
AP00748394 When using asynchronous motors,
current controller gain may be too
large considering the existing motor
data identification.
When using asynchronous motors, current controller gain may be too large
considering the existing motor data identification.
Considering the existing motor data
identification of asynchronous motors, the
current controller gain (p1715) must be
checked and corrected if need be. For
checking, the reference frequency response
must be taken over for the current controller.
SINAMICS_SW - Safety Integrated
AP00731197 Very sporadically alarm
F1711/30711 when selecting SS1
Very sporadically alarms F1711 and F30711 with fault value 58 occur when
selecting the extended safety function SS1. The error occurs at the time
when, because of a time condition (p9556) or the speed/velocity attained
(p9560), the STO response is triggered. The error can be acknowledged via
the safe acknowledgement (PROFIsafe: Internal event acknowledge,
TM54F: p10006). In SW V02.50.xx.xx this acknowledgement must be
performed before the deselection of SS1.
The error can be completely avoided with the
following measures: 1.) Trigger an STO in
good time before the transition time from SS1
to STO expires (p9556, p9356) 2.) Use SS2
and switch to STO after the feedback message
SOS active 3.) Use the SS1 function of the
basic safety functions
AP00737515 Re-parameterization of parameters in
the range 10100 - 10199 is not
permitted via the expert list.
Re-parameterization of parameters in the range 10100 - 10199 is not
permitted via the expert list. This results in alarm 30680 (SI motion MM:
Checksum error, safety monitoring functions).
Perform the parameterization exclusively via
the STARTER screens.
AP00744909 After error parameterization p9500
unequal to p9300 and after parameter
reset on the CU (p972 = 1) or after a
power OFF/ON, error message
F30711 is output together with the
invalid error message F30665. The
same also applies to other parameters
(p9511/p9311..) of the Safety screen
form?Configuration?
If p9500 (SI Motion Monitoring Cycle Control Unit) unequal p9300 (SI
Motion Monitoring Cycle Motor Module) is set due to incorrect
parameterization, then error message F30711 as well as the incorrect error
message F30665 (SI MM: System Defect) will be ouput after a parameter
reset on the control unit with p972 = 1 or after a power OFF/ON. The same
also applies to other parameters (p9511/p9311..) of the Safety screen
form?Configuration?
If error message F30665 is output with error
message F30711 (cross-checking error) and if
parameterization p9500 is unequal to p9300 or
(p9511/p9311..), then the parameterization in
p9500 and p9300 or (p9511/p9311..) must be
corrected in such a way that the monitoring
cycle settings match the cycle settings. Error
message F30665 can be ignored in this case.
17.12.2008SINAMICS_S110_V41_Restrictions.pdf

3. SIEMENS SINAMICS S110 V4.1
incl. SSP for STARTER
ARTSPlusRQ Brief description Description Possible work-around
SINAMICS_SW - Safety Integrated
AP00745163 After changing P10106 (SI
Acknowledgement Internal Event
Input Terminal (2nd channel)) a
present discrepancy error C30770
cannot be acknowledged any longer
with safe acknowledgement. After
power ON the new parameterization
becomes effective and is functioning.
In the event of an error, the
respective FDI remains in a safe
state.
After first commissioning or after changing P10106 (SI Acknowledgement
Internal Event Input Terminal (2nd channel)) a present discrepancy error
C30770 cannot be acknowledged any longer with safe acknowledgement.
After power ON the new parameterization becomes effective and is
functioning. In the event of an error, the respective FDI remains in a safe
state.
Switch OFF/ON.
AP00747957 Error messages C01712 and C30712
are not output with a fault value 10
and, as from fault value 11, output
with a value one less than output.
If error messages C01770 SI "Motion CU: Discrepency error of the failsafe
inputs or outputs" C30770 "SI Motion MM: Discrepency error of the failsafe
inputs or outputs" are reported, then bugfixing may show that different
settings of the parameters p10039 "SI Safe State Signal Selection / SI Safe
State Selection" and p10139 "SI Safe State Signal Selection (2nd channel) /
SI Safe State Selection" are responsible. The error messages C01712 and
C30712 with fault value 10, as expected, are, however, not output.
In the case of error messages C01712 SI "Motion CU: Defect in F-IO
processing" or C30712 "SI Motion MM: Defect in F-IO processing", the
fault value is output with a value one less than output as from fault value 11.
Fault output requires corresponding
interpretation.
SINAMICS_SW - Topology
AP00486766 After replacement of the SMI motor,
fault F1840 (SMI: Component with
changed data found) occurs.
After replacement of the SMI motor, fault F1840 (SMI: Component with
changed data found) occurs.
Open expert list of drive object 1 (device) and
change the value of parameter p9906 to 2.
Then save and switch off and on again.
AP00667805 Some errors cannot be acknowledged
after the deactivation or parking of
some SMI/SME components.
Some errors cannot be acknowledged after the deactivation or parking of
some SMI/SME components. This only applies when the errors have not
been acknowledged before the deactivation or parking.
Acknowledge errors before the deactivation or
parking. Perform restart after activation or
termination of parking.
17.12.2008SINAMICS_S110_V41_Restrictions.pdf