S210 1FK2 Op Instr 011217 Eng
S210 1FK2 Op Instr 011217 Eng
SINAMICS/SIMOTICS
Servo drive system
SINAMICS S210
SINAMICS S210 converter
SIMOTICS S-1FK2 servomotor
Fundamental safety
instructions 1
Description 2
SINAMICS/SIMOTICS
Configuring 3
SINAMICS S210 servo drive system Safety functions integrated in
the drive 4
Installing 5
Operating Instructions
Commissioning and
diagnostics in the Web server 6
Diagnostics 7
Technical specifications 8
Dimension drawings 9
Decommissioning and
disposal 10
Ordering data 11
Parameters 12
12/2017
A5E41702836B AA
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in
this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
Target group
These operating instructions are intended for persons who perform different tasks in the drive
environment, e.g. for:
● Planning engineers
● Project engineers
● Machine manufacturers
● Commissioning engineers
● Electricians
● Installation personnel
● Service technician
● Warehouse personnel
More information
Information on the following topics is available at:
● Ordering documentation / overview of documentation
● Additional links to download documents
● Using documentation online (find and search in manuals / information)
Additional information on drive technology (https://support.industry.siemens.com/cs/de/en/ps/
13204)
If you have any questions relating to the technical documentation (e.g. suggestions,
corrections) then please email them to the following address: Email
(mailto:docu.motioncontrol@siemens.com)
My support
The following link provides information on how to create your own individual documentation
based on Siemens content, and adapt it for your own machine documentation:
My support (https://support.industry.siemens.com/My/de/en/documentation)
Note
If you want to use this function, you must first register.
Later, you can log on with your login data.
Technical Support
Country-specific telephone numbers for technical support are provided on the Internet under
Contact:
Technical Support (https://support.industry.siemens.com)
Use of OpenSSL
This product contains software (https://www.openssl.org/) that has been developed by the
OpenSSL project for use in the OpenSSL toolkit.
This product contains cryptographic software (mailto:eay@cryptsoft.com) created by Eric
Young.
This product contains software (mailto:eay@cryptsoft.com) developed by Eric Young.
Preface.........................................................................................................................................................3
1 Fundamental safety instructions.................................................................................................................11
1.1 General safety instructions.....................................................................................................11
1.2 Equipment damage due to electric fields or electrostatic discharge......................................17
1.3 Warranty and liability for application examples......................................................................18
1.4 Industrial security...................................................................................................................19
1.5 Residual risks of power drive systems...................................................................................20
2 Description..................................................................................................................................................21
2.1 System overview....................................................................................................................22
2.2 The scope of supply for the system components...................................................................24
2.3 Motor......................................................................................................................................25
2.4 Converter...............................................................................................................................28
2.5 Connection systems...............................................................................................................31
2.6 Motor-converter combinations................................................................................................32
2.7 Optional accessories..............................................................................................................33
3 Configuring.................................................................................................................................................35
3.1 EMC-compliant installation of a machine or system..............................................................35
3.1.1 Control cabinet.......................................................................................................................35
3.1.2 Cables....................................................................................................................................36
3.1.3 Electromechanical components.............................................................................................38
3.2 Permissible line supplies and connection options..................................................................39
3.2.1 Connection options, 230 V devices........................................................................................40
3.3 Configuring the motor.............................................................................................................44
3.3.1 Configuration sequence.........................................................................................................44
3.3.1.1 Clarification of type of drive....................................................................................................45
3.3.1.2 Specification of the supplementary conditions and integration into the automation system......46
3.3.1.3 Definition of the load, calculation of the maximum load torque and determination of the
motor......................................................................................................................................46
3.4 Configuring the external braking resistor...............................................................................52
3.5 Establishing communication of the converter with the controller...........................................55
4 Safety functions integrated in the drive......................................................................................................57
4.1 Overview of Safety Integrated Functions...............................................................................57
4.2 Basic Functions......................................................................................................................58
4.2.1 Safe Torque Off (STO)...........................................................................................................58
4.2.2 Safe Brake Control (SBC)......................................................................................................61
7.4 Alarms..................................................................................................................................173
7.5 Faults...................................................................................................................................174
8 Technical specifications............................................................................................................................175
8.1 Technical data and properties of the motor..........................................................................175
8.1.1 Technical features................................................................................................................175
8.1.2 Permissible environmental conditions for the motor............................................................176
8.1.3 Cooling.................................................................................................................................178
8.1.4 Derating factors....................................................................................................................180
8.1.5 Degree of protection.............................................................................................................180
8.1.6 Balancing.............................................................................................................................181
8.1.7 Vibration response...............................................................................................................182
8.1.8 Shaft extension....................................................................................................................183
8.1.9 Radial eccentricity, concentricity and axial eccentricity........................................................184
8.1.10 Permissible radial and axial forces.......................................................................................185
8.1.11 Available encoders...............................................................................................................185
8.1.12 Brake data............................................................................................................................185
8.1.13 Technical data and characteristics 1FK2 High Dynamic......................................................187
8.1.13.1 1FK2102-0AG......................................................................................................................187
8.1.13.2 1FK2102-1AG......................................................................................................................189
8.1.13.3 1FK2103-2AG......................................................................................................................190
8.1.13.4 1FK2103-4AG......................................................................................................................191
8.1.13.5 1FK2104-4AK.......................................................................................................................192
8.1.13.6 1FK2104-5AK.......................................................................................................................193
8.1.14 Technical data and characteristics 1FK2 Compact..............................................................194
8.1.14.1 1FK2203-2AG......................................................................................................................194
8.1.14.2 1FK2203-4AG......................................................................................................................196
8.2 Technical specifications of the converter.............................................................................197
8.2.1 Electromagnetic compatibility ..............................................................................................199
8.2.2 Converter ambient conditions..............................................................................................200
8.2.3 General data, converter.......................................................................................................202
8.2.4 Specific data, converter........................................................................................................203
8.3 Technical data and properties of the connection system.....................................................204
9 Dimension drawings.................................................................................................................................207
9.1 Dimension drawings of motor...............................................................................................207
9.2 Dimension drawings of converter.........................................................................................210
10 Decommissioning and disposal................................................................................................................213
10.1 Removing and disposing of the motor..................................................................................213
10.2 Disposing of converter.........................................................................................................214
11 Ordering data............................................................................................................................................215
11.1 Ordering data of the motor...................................................................................................215
11.2 Ordering data of the converter.............................................................................................216
11.3 Connection cables between the motor and the converter....................................................217
11.4 Accessories..........................................................................................................................219
11.4.1 Memory cards......................................................................................................................219
WARNING
Electric shock and danger to life due to other energy sources
Touching live components can result in death or severe injury.
● Only work on electrical devices when you are qualified for this job.
● Always observe the country-specific safety rules.
Generally, the following six steps apply when establishing safety:
1. Prepare for disconnection. Notify all those who will be affected by the procedure.
2. Isolate the drive system from the power supply and take measures to prevent it being
switched back on again.
3. Wait until the discharge time specified on the warning labels has elapsed.
4. Check that there is no voltage between any of the power connections, and between any
of the power connections and the protective conductor connection.
5. Check whether the existing auxiliary supply circuits are de-energized.
6. Ensure that the motors cannot move.
7. Identify all other dangerous energy sources, e.g. compressed air, hydraulic systems, or
water. Switch the energy sources to a safe state.
8. Check that the correct drive system is completely locked.
After you have completed the work, restore the operational readiness in the inverse sequence.
WARNING
Electric shock due to connection to an unsuitable power supply
When equipment is connected to an unsuitable power supply, exposed components may
carry a hazardous voltage that might result in serious injury or death.
● Only use power supplies that provide SELV (Safety Extra Low Voltage) or PELV-
(Protective Extra Low Voltage) output voltages for all connections and terminals of the
electronics modules.
WARNING
Electric shock due to damaged motors or devices
Improper handling of motors or devices can damage them.
Hazardous voltages can be present at the enclosure or at exposed components on damaged
motors or devices.
● Ensure compliance with the limit values specified in the technical data during transport,
storage and operation.
● Do not use any damaged motors or devices.
WARNING
Electric shock due to unconnected cable shields
Hazardous touch voltages can occur through capacitive cross-coupling due to unconnected
cable shields.
● As a minimum, connect cable shields and the cores of cables that are not used at one end
at the grounded housing potential.
WARNING
Electric shock if there is no ground connection
For missing or incorrectly implemented protective conductor connection for devices with
protection class I, high voltages can be present at open, exposed parts, which when touched,
can result in death or severe injury.
● Ground the device in compliance with the applicable regulations.
WARNING
Arcing when a plug connection is opened during operation
Opening a plug connection when a system is operation can result in arcing that may cause
serious injury or death.
● Only open plug connections when the equipment is in a voltage-free state, unless it has
been explicitly stated that they can be opened in operation.
WARNING
Electric shock due to residual charges in power components
Because of the capacitors, a hazardous voltage is present for up to 5 minutes after the power
supply has been switched off. Contact with live parts can result in death or serious injury.
● Wait for 5 minutes before you check that the unit really is in a no-voltage condition and
start work.
WARNING
Spread of fire from built-in devices
In the event of fire outbreak, the enclosures of built-in devices cannot prevent the escape of
fire and smoke. This can result in serious personal injury or property damage.
● Install built-in units in a suitable metal cabinet in such a way that personnel are protected
against fire and smoke, or take other appropriate measures to protect personnel.
● Ensure that smoke can only escape via controlled and monitored paths.
WARNING
Failure of pacemakers or implant malfunctions due to electromagnetic fields
Electromagnetic fields (EMF) are generated by the operation of electrical power equipment,
such as transformers, converters, or motors. People with pacemakers or implants in the
immediate vicinity of this equipment are at particular risk.
● If you have a heart pacemaker or implant, maintain a minimum distance of 2 m from
electrical power equipment.
WARNING
Failure of pacemakers or implant malfunctions due to permanent magnetic fields
Even when switched off, electric motors with permanent magnets represent a potential risk
for persons with heart pacemakers or implants if they are close to converters/motors.
● If you have a heart pacemaker or implant, maintain the minimum distance specified in the
Chapter "Technical data".
● When transporting or storing permanent-magnet motors always use the original packing
materials with the warning labels attached.
● Clearly mark the storage locations with the appropriate warning labels.
● IATA regulations must be observed when transported by air.
WARNING
Unexpected movement of machines caused by radio devices or mobile phones
When radio devices or mobile phones with a transmission power > 1 W are used in the
immediate vicinity of components, they may cause the equipment to malfunction.
Malfunctions may impair the functional safety of machines and can therefore put people in
danger or lead to property damage.
● If you come closer than around 2 m to such components, switch off any radios or mobile
phones.
● Use the "SIEMENS Industry Online Support App" only on equipment that has already been
switched off.
WARNING
Motor fire in the event of insulation overload
There is higher stress on the motor insulation through a ground fault in an IT system. If the
insulation fails, it is possible that death or severe injury can occur as a result of smoke and
fire.
● Use a monitoring device that signals an insulation fault.
● Correct the fault as quickly as possible so the motor insulation is not overloaded.
WARNING
Fire due to inadequate ventilation clearances
Inadequate ventilation clearances can cause overheating of components with subsequent
fire and smoke. This can cause severe injury or even death. This can also result in increased
downtime and reduced service lives for devices/systems.
● Ensure compliance with the specified minimum clearance as ventilation clearance for the
respective component.
WARNING
Unrecognized dangers due to missing or illegible warning labels
Dangers might not be recognized if warning labels are missing or illegible. Unrecognized
dangers may cause accidents resulting in serious injury or death.
● Check that the warning labels are complete based on the documentation.
● Attach any missing warning labels to the components, where necessary in the national
language.
● Replace illegible warning labels.
NOTICE
Device damage caused by incorrect voltage/insulation tests
Incorrect voltage/insulation tests can damage the device.
● Before carrying out a voltage/insulation check of the system/machine, disconnect the
devices as all converters and motors have been subject to a high voltage test by the
manufacturer, and therefore it is not necessary to perform an additional test within the
system/machine.
WARNING
Unexpected movement of machines caused by inactive safety functions
Inactive or non-adapted safety functions can trigger unexpected machine movements that
may result in serious injury or death.
● Observe the information in the appropriate product documentation before commissioning.
● Carry out a safety inspection for functions relevant to safety on the entire system, including
all safety-related components.
● Ensure that the safety functions used in your drives and automation tasks are adjusted
and activated through appropriate parameterizing.
● Perform a function test.
● Only put your plant into live operation once you have guaranteed that the functions relevant
to safety are running correctly.
Note
Important safety notices for Safety Integrated functions
If you want to use Safety Integrated functions, you must observe the safety notices in the Safety
Integrated manuals.
WARNING
Malfunctions of the machine as a result of incorrect or changed parameter settings
As a result of incorrect or changed parameterization, machines can malfunction, which in turn
can lead to injuries or death.
● Protect the parameterization (parameter assignments) against unauthorized access.
● Handle possible malfunctions by taking suitable measures, e.g. emergency stop or
emergency off.
WARNING
Injury caused by moving or ejected parts
Contact with moving motor parts or drive output elements and the ejection of loose motor
parts (e.g. feather keys) out of the motor enclosure can result in severe injury or death.
● Remove any loose parts or secure them so that they cannot be flung out.
● Do not touch any moving parts.
● Safeguard all moving parts using the appropriate safety guards.
WARNING
Fire due to inadequate cooling
Inadequate cooling can cause the motor to overheat, resulting in death or severe injury as a
result of smoke and fire. This can also result in increased failures and reduced service lives
of motors.
● Comply with the specified cooling requirements for the motor.
WARNING
Fire due to incorrect operation of the motor
When incorrectly operated and in the case of a fault, the motor can overheat resulting in fire
and smoke. This can result in severe injury or death. Further, excessively high temperatures
destroy motor components and result in increased failures as well as shorter service lives of
motors.
● Operate the motor according to the relevant specifications.
● Only operate the motors in conjunction with effective temperature monitoring.
● Immediately switch off the motor if excessively high temperatures occur.
CAUTION
Burn injuries caused by hot surfaces
In operation, the motor can reach high temperatures, which can cause burns if touched.
● Mount the motor so that it is not accessible in operation.
Measures when maintenance is required:
● Allow the motor to cool down before starting any work.
● Use the appropriate personnel protection equipment, e.g. gloves.
NOTICE
Equipment damage due to electric fields or electrostatic discharge
Electric fields or electrostatic discharge can cause malfunctions through damaged individual
components, integrated circuits, modules or devices.
● Only pack, store, transport and send electronic components, modules or devices in their
original packaging or in other suitable materials, e.g conductive foam rubber of aluminum
foil.
● Only touch components, modules and devices when you are grounded by one of the
following methods:
– Wearing an ESD wrist strap
– Wearing ESD shoes or ESD grounding straps in ESD areas with conductive flooring
● Only place electronic components, modules or devices on conductive surfaces (table with
ESD surface, conductive ESD foam, ESD packaging, ESD transport container).
Note
Industrial security
Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, systems, machines and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is
necessary to implement – and continuously maintain – a holistic, state-of-the-art industrial
security concept. Siemens products and solutions only represent one component of such a
concept.
The customer is responsible for preventing unauthorized access to its plants, systems,
machines and networks. Systems, machines and components should only be connected to
the enterprise network or the internet if and to the extent necessary and with appropriate
security measures (e.g. use of firewalls and network segmentation) in place.
Additionally, Siemens’ guidance on appropriate security measures should be taken into
account. For more information about industrial security, please visit:
Industrial security (http://www.siemens.com/industrialsecurity).
Siemens’ products and solutions undergo continuous development to make them more secure.
Siemens strongly recommends to apply product updates as soon as available and to always
use the latest product versions. Use of product versions that are no longer supported, and
failure to apply latest updates may increase customer’s exposure to cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS
Feed at:
Industrial security (http://www.siemens.com/industrialsecurity).
WARNING
Unsafe operating states resulting from software manipulation
Software manipulations (e.g. viruses, trojans, malware or worms) can cause unsafe operating
states in your system that may lead to death, serious injury, and property damage.
● Keep the software up to date.
● Incorporate the automation and drive components into a holistic, state-of-the-art industrial
security concept for the installation or machine.
● Make sure that you include all installed products into the holistic industrial security concept.
● Protect files stored on exchangeable storage media from malicious software by with
suitable protection measures, e.g. virus scanners.
Correct usage
The components are intended for industrial and commercial use in industrial networks.
The motor is only approved for operation with a converter.
For system-specific setting options, refer to the following Chapter:
Commissioning and diagnostics in the Web server (Page 105).
Typical applications
● Robots and handling systems
● Packaging, plastics and textile machines
● Wood, glass, ceramics and stone working machines
● Printing machines
&RQWUROOHU3/&
HJ6,0$7,&6
&RPPXQLFDWLRQYLD352),1(7
(QJLQHHULQJYLD/$1ZLWKWKH
ZHEVHUYHULQWHJUDWHGLQWKH
FRQYHUWHU
6,1$0,&66FRQYHUWHU
2&&FRQQHFWLRQFDEOHIRU
SRZHUFRQQHFWLRQVPRWRUKROGLQJEUDNH
DQGHQFRGHUV
6,027,&66).PRWRUV
9$&
;
;
; ;
;3
;
;3
; 352),1(7
352),VDIH
;
3(
① Fuse or circuit breaker ⑨ OCC connection cable for motor, motor holding
brake and encoder
② Line contactor (optional) ⑩ Shield clamp
③ Line filter (optional) ⑪ Shield plate
④ External braking resistor (optional) ⑫ Ferrite core (for frame size FSB)
⑤ Shaft sealing ring for IP65 (optional) ⑬ 24 V power supply
⑥ 1FK2 servomotor ⑭ SD memory card (optional)
⑦ OCC extension cable (optional) ⑮ Commissioning device
⑧ Mounting flange for control cabinet ⑯
Controller, e.g. SIMATIC S7-1500
bushing (optional)
Figure 2-2 System components and accessories
Motor
The motor scope of delivery includes:
● A "Safety instructions" sheet
● A sheet referencing links to product information
Converter
The converter scope of delivery includes:
● The Quick Installation Guide (English)
● Shield plate
● A warning label for affixing in the control cabinet
● For FSB a ferrite core for EMC category C2
● The following connectors:
– X1: Line connection and external braking resistor (jumper for internal braking resistor is
enclosed.)
– X2: Motor connection
– X107: Motor holding brake
– X124: 24 V DC supply voltage
– X130: Connector for digital inputs
2.3 Motor
The SIMOTICS S-1FK2, called "1FK2" in the following, is a permanent-magnet compact
synchronous motor with an integrated encoder and a high degree of protection.
The 1FK2 meets the requirements of standards EN 60034 and EN 60204-1 - and complies
with the Low-Voltage Directive 2014/35/EU.
WARNING
Failure of pacemakers or implant malfunctions due to electromagnetic fields
Electromagnetic fields (EMF) are generated by the operation of electrical power equipment,
such as converters or motors. People with pacemakers or implants in the immediate vicinity
of this equipment are at particular risk.
Deviating from the notes in Section "General safety instructions (Page 11), applies to the
1FK2 motors:
● If you are affected, stay at a minimum distance of 30 cm from the motors.
Dynamic versions
● 1FK21 "High Dynamic" with low moment of inertia for a maximum acceleration capability
in applications with low load moments of inertia
● 1FK22 "Compact" with average moment of inertia and precise positioning and synchronous
operation characteristics for applications with a high and variable load moment of inertia
Power range
0.05 kW … 0.75 kW for a line supply voltage of 230 V 1 AC
Degree of protection
● IP64
● IP65 with a radial shaft sealing ring to protect against spray water
For additional information on the degree of protection, see Chapter:
"Degree of protection (Page 180)"
Cooling
The 1FK2 is a non-ventilated motor.
The motor thermal losses are dissipated by thermal conduction, thermal radiation and natural
convection.
If the ambient temperature exceeds 40 °C (104 °F) or the installation altitude 1000 meters
above sea level, you must reduce torque and power of the motor (derating).
Information on derating can be found in Chapter:
"Derating factors (Page 180)"
Bearing version
The motors have deep groove ball bearings with life-long lubrication.
The average bearing service life is designed for 25000 operating hours.
The motors have spring-loaded bearings in the NDE direction. For version with holding brake,
the NDE bearing is a locating bearing.
The permissible axial and radial forces can be found in the technical data in Chapter:
"Permissible radial and axial forces (Page 185)"
Encoder
The motor encoder resolution is 20 bit (1,048,576) per revolution (singleturn). An optional
multiturn encoder is available that is equipped with an additional 12-bit revolution counter
(traversing range of 4096 revolutions).
The names of these two encoders are as follows:
● AS20DQC: Absolute encoder, singleturn, 20 bit
● AM20DQC: Absolute encoder, 20 bit + 12 bit multiturn
For additional information, see Chapter:
"Available encoders (Page 185)"
Holding brake
The 1FK2 servomotor is available with integrated holding brake. The holding brake is used to
clamp the motor shaft when the motor is at a standstill.
The holding brake closes in the current-free state and locks the motor shaft. It opens as soon
as current is flowing.
SINAMICS S210 controls the holding brake without any additional devices.
The torsional backlash of the holding brake is less than 1°.
The holding brake is not a working brake for braking the rotating motor. However, limited
emergency stop operation is permissible.
Rating plate
The rating plate contains the Article No. and the technical information of the motor.
SIMOTICS 1P 1FK2104-4AK00-0CA0
3 ~ Mot. S YF JO662 2670 01 002
Z:
M0 1,27 Nm I0 2,4 A nmax7400 /min
MN 1,27 Nm IN 2,4 A nn 3000 /min
UiN108 V Th.Cl.155 (F)
EN60034
m: 3 kg IP 64 IC410
Encoder AS22DQ35 G95 +
Brake 24 VDC
RN 000
Siemens AG, DE-97616 Bad Neustadt Made in Germany
Figure 2-3 Rating plate
2.4 Converter
The converter is a single-axis device (complete converter with integrated infeed). It is
characterized by a compact design, side-by-side installation and high overload capability.
It is intended for use with 1FK2 motors.
● Supply voltage 200 V … 240 V 1 AC ± 10%
● Power range 100 W … 750 W
Control mode
Servo control, optimized for 1FK2 motors
s
SINAMICS S210
1P 6SL3210-5HB10-4UF0
S ZVE4Y7M000141
SNC-A5E37577127
INPUT: 1AC 200-240V 5.8A/0.3A 50/60Hz
INPUT: 24VDC 0.5A OUTPUT: 3AC 0-INPUT V 2.6A 0-550Hz
IP CLASS: IP20 MOTOR: 0.2kW/0.4kW
VERSION: 01 SCCR: 65kA
USE IN PD2 AND OVC III ENVIRONMENT ONLY
USE 75°C COPPER WIRES ONLY | REFER TO MANUAL
KCC-
REM-S49- IND.CONT.EQ.
S100 4TR2
SINAMICS S210
FS: 01
PN1 / X127
00-00-00-00-00-00
00-00-00-00-00-00
Further information
Additional information about EMC-compliant installation is available in the Internet:
EMC installation guideline (http://support.automation.siemens.com/WW/view/en/60612658)
3.1.2 Cables
Cables with a high level of interference and cables with a low level of interference are
connected to the converter.
Note
Cables with a high level of interference must be shielded.
/LQH
&RQWUROFDELQHW
0RXQWLQJSODWH
)XVHVVZLWFKHVDQG
FRQWDFWRUV
)LOWHURSWLRQDO
&RQQHFWVKLHOG (OHFWULFDOO\
FRQGXFWLYH
&RQYHUWHU FRQQHFWLRQV
WKURXJKDODUJH
VXUIDFHDUHD
&RQQHFWVKLHOG 6KLHOGVXSSRUW
&RQQHFWVKLHOG
%UDNLQJUHVLVWRU
RSWLRQDO
Figure 3-1 Routing converter cables inside and outside a control cabinet
)HUULWHFRUHUHTXLUHGIRU)6%
IRU(0&&DWHJRU\&
2&&FRQQHFWLRQFDEOHWRWKH &RQQHFWLRQFDEOHIRUIDLOVDIHGLJLWDO
PRWRU LQSXWDQGSUREH
&RQQHFWLRQFDEOHIRUH[WHUQDO
EUDNLQJUHVLVWRU
Figure 3-2 Shield support with the shield terminal from the scope of supply of the MOTION-
CONNECT OCC cable.
$&9
/
/
/
1
$&99 $&99
/ /
1 /
/
WARNING
Neutral conductor fire caused by high currents
If you connect the converter without an isolation transformer to a supply system with 400 V
3 AC between the N-conductor and a line conductor (L1, L2 or L3), the harmonic currents in
the N-conductor can add up to values that are greater than the currents in the line conductors.
This heats up the N-conductor and can cause a fire.
● Take the harmonic currents into account when dimensioning the power supply cables.
$&9
/
1
)
$&9
/
/
/
1
))
Motion control
Drives are optimized for motion control applications. They execute linear or rotary movements
within a defined movement cycle. All movements should be optimized in terms of time.
As a result, drives must meet the following requirements:
● High dynamic response, i.e. short rise times
● Capable of overload, i.e. a high reserve for accelerating
● Wide control range, i.e. high resolution for precise positioning.
The following table "Configuring procedure" is valid for synchronous and induction motors.
3.3.1.2 Specification of the supplementary conditions and integration into the automation system
Take the following into account during the confguration:
● The line system configuration when using specific motor types and/or line filters
● The utilization of the motor rated values for winding overtemperatures of 60 K or 100 K (for
synchronous motors)
● The ambient temperatures and the installation altitude of the motors and drive components
● The heat dissipation from the motors through natural ventilation, forced ventilation or water
cooling
Other conditions apply when integrating the drives into an automation environment such as
SINUMERIK or SIMOTION.
For motion control and technology functions (e.g. positioning), as well as for synchronous
operation functions, the corresponding automation system, e.g. SIMATIC S7-1500 or
SIMOTION D is used.
3.3.1.3 Definition of the load, calculation of the maximum load torque and determination of the
motor
The motors are defined bases on the motor type-specific limiting characteristic curves.
The limiting characteristic curves describe the torque or power curve over the speed.
The limiting characteristic curves take the limits of the motor into account on the basis of the
DC-link voltage. The DC-link voltage is dependent on the line voltage.
In the case of torque drive the DC-link voltage is dependent on the type of Line Module and
the type of infeed module or infeed/regenerative feedback module.
0BPD[
7RUTXHLQ1P
6
0RWRUVSHHGLQUSP
Procedure
1. Determine the load which is specified by the application.
Use different characteristics for the different loads.
The following operating scenarios have been defined:
– Duty cycle with constant ON duration
– Free duty cycle
2. Determine the characteristic torque and speed operating points of the motor for the defined
load.
3. Calculate the acceleration torque of the motor.
Add the load torque and the acceleration torque to obtain the maximum required torque.
4. Verify the maximum motor torque with the limiting characteristic curves of the motors.
The following criteria must be taken into account when selecting the motor:
– Adherence to the dynamic limits
All speed-torque points of the load event must lie below the relevant limiting
characteristic curve.
– Adherence to the thermal limits
At average motor speed, the effective motor torque must be below the S1 characteristic
(continuous operation) during the load.
You have specified a motor.
39
W
˽
˽ PD[
The drives with this load cycle typically operate at a stationary operating point.
Procedure
1. Configure a base load for the stationary operating point. The base load torque must lie
below the S1 characteristic.
2. In the event of transient overloads (e.g. during acceleration), configure an overload.
Calculate the overload current in relation to the required overload torque. The overload
torque must lie below the M_max characteristic.
In summary, the motor is configured as follows:
0BPD[
0BFRQVWBRYHU
7RUTXHLQ1P
6
0BFRQVWBEDVH
0RWRUVSHHGLQUSP
M_max Curve of the maximum torque M_const_ov Curve of the overload torque
er
S1 S1 characteristic M_const_b Curve of the base load torque
ase
Figure 3-9 Motor selection for a duty cycle with constant switch-on duration
7 W
0
WL W
Procedure
Determine the required motor torque as follows:
● Define a load torque for each time slice. Also take the average load moment of inertia and
motor moment of inertia into account for acceleration operations. If required, take a frictional
torque into account that opposes the direction of motion.
● With mounted gearbox:
Determine the load torque and the acceleration torque that must be supplied by the motor.
Take the gear ratio and gear efficiency into account.
Note
A higher gear ratio increases positioning accuracy in terms of encoder resolution. For any
given motor encoder resolution, as the gear ratio increases, so does the resolution of the
machine position to be detected.
The following formulas can be used for duty cycles outside the field weakening range.
0BPD[
7RUTXHLQ1P
6
0BHII
QBPHDQ
0RWRUVSHHGLQUSP
You have defined the characteristic motor values corresponding to the duty cycle.
Table 3-2 Braking energy and continuous braking power with the integrated braking resistor in
relation to the shaft of the servo motor
J Moment of inertia of the driven mechanical system in relation to the shaft of the servo
motor
Note
As the actual friction is not taken into account in the above formula, less energy is fed back to
the servo drive system in practice than that calculated in the formula.
Example
WARNING
Risk of fire caused by continuous overload
If the external braking resistor is continuously overloaded, for example as the result of a
defective braking chopper, this can result in an explosion or fire - or the housing could melt.
● Use only braking resistors that are intrinsically safe.
Table 3-4 Examples of suitable external braking resistors from a third party
1) For thermal reasons, it is not permissible that the continuous braking power of 240 W is exceeded.
Note
Braking resistor with temperature monitoring
Use only a braking resistor with temperature monitoring.
Standard telegrams:
● Telegram 3
● Telegram 5
● Telegram 102
● Telegram 105
Supplementary telegrams
● Telegram 700
● Telegram 701
● Telegram 750
PROFIsafe telegrams
● Telegram 30
● Telegram 901
Basic Functions
These functions are part of the standard scope of the converter and can be used without
requiring an additional license. The Basic Functions consist of the following Safety Integrated
Functions:
● Safe Torque Off (STO)
● Safe Brake Control (SBC)
● Safe Stop 1, time-controlled (SS1)
Overview
Functional features
The switching on inhibited prevents an automatic restart after deselection of STO and therefore
satisfies the requirements of EN 60204-1. Consequently, the STO function prevents an
electrically-driven machine component from restarting.
Note
There is no galvanic isolation between motor and converter.
The STO function can be selected via PROFIsafe and/or the fail-safe digital input (F-DI).
STO is a drive-specific function that must be put into operation individually for each drive.
Applications
Applications include all machines and systems with moving axes (e.g. conveyor technology,
handling).
STO is suitable for applications where the motor is already at a standstill or will come to a
standstill in a short, safe period of time as a result of friction.
STO facilitates personnel to work safely with the protective door open. A classic Emergency
Stop with electromechanical isolation is not required. The converter remains connected to the
line and can be fully diagnosed.
Note
The distinction between Emergency Off and Emergency Stop
"Emergency Off" and "Emergency Stop" are commands that minimize different risks in the
machine or plant.
The STO function is suitable for implementing an Emergency Stop - but not an Emergency Off.
Details regarding the distinction between Emergency Off and Emergency Stop are provided
in the following section:
What is the difference between the Emergency Off and Emergency Stop functions?
(Page 745)
Sequence diagram
212))
$FWLRQ
672GHVHOHFWLRQ
6SHHG W
7KHPRWRUFRDVWV
UHVSRQVH
GRZQWRDVWDQGVWLOO
0RWRU
W
&RQYHUWHU
672DFWLYH
UHVSRQVH
5HDG\WRVWDUW
W
Deselecting "Safe Torque Off" represents an internal safety acknowledgment. The following
is executed when the cause of the fault has been removed:
1. The Safety requirement "Close motor holding brake" is canceled.
2. Any pending STOP F or STOP A commands are canceled.
3. The messages in the fault memory must also be reset using the general acknowledgment
mechanism.
Overview
Functional features
In order that SBC can become active you must enable the function when commissioning the
system.
Note
SBC cannot be selected as an autonomous function; however, if it is enabled, it is activated
at the same time that STO is selected.
The holding brake is controlled using the encoder integrated in the motor.
Applications
SBC can be used wherever a safe position must be maintained even with a de-energized
motor, in order to prevent suspended or passing loads from dropping (e.g. lifting gear,
passenger elevators, winders). No external logic or switching elements required, as the
functionality is completely integrated in the drive.
Note
Condition of the motor holding brake
SBC is not able to identify as to whether a holding brake is mechanically worn or is a defective.
As a consequence, observe the maximum permissible number of emergency braking
operations for the motor holding brake being used.
Sequence diagram
212))
$FWLRQ
2SHQPRWRUKROGLQJEUDNH
672GHVHOHFWLRQ
6SHHG W
UHVSRQVH
0RWRU
0RWRUEUDNHVWR
VWDQGVWLOO
W
672DFWLYH
&RQYHUWHUUHVSRQVH
6%&UHTXHVWHG
7LPHIRUEUDNHFORVLQJRSHUDWLRQ 7LPHIRUEUDNHRSHQLQJRSHUDWLRQ
0 0 0
0RWRUKROGLQJEUDNHRSHQ
5HDG\IRUVZLWFKLQJ
W
STO is selected during operation via the control bit of the selected PROFIsafe telegram or via the
F-DI.
Safe Brake Control (SBC) is activated at the same time. Taking the brake closing time (r1217)
into account, the command to close the motor holding brake closes the brake, thus supporting the
shutdown process initiated by STO.
The mechanical brake brakes the motor down to standstill.
The converter goes into the "Ready to start" state, when STO is deselected via PROFIsafe or F-
DI. SBC is reset at the same time. The brake remains (unsafely) closed until the standard program
executes the command to open the brake.
The converter switches the motor on again with a positive signal edge at ON/OFF.
Taking the brake opening time (r1216) into account, the command to open the motor holding brake
opens the brake.
The converter carries out a check to ensure that the "Safe Brake Control" function is working
properly and ensures that - if there is a failure or fault - the brake current is interrupted and the
brake is thus applied. If a fault is detected by the converter, the brake current is
disconnected. The brake then closes and a safe state is reached.
Overview
∆t t
Functional features
There are the following variants for the Basic Function "Safe Stop 1":
● SS1 with OFF3 (SS1-t according to IEC 61800-5-2)
● SS1 with external stop (SS1E)
The setting of the SS1 response is performed during the Safety commissioning in the step
"Parameterization"
Applications
SS1 can be used wherever the load torque cannot stop the motor in a sufficiently short time
as a result of friction - or where there is a safety risk if the drive coasts down (STO).
Note
There is a single-channel monitoring of the braking process at the OFF3 ramp!
212))
$FWLRQ 'HVHOHFW66
W
6SHHG
UHVSRQVH
0RWRU
7KHPRWRUFRDVWVGRZQ
WRDVWDQGVWLOO
W
'HOD\WLPH
&RQYHUWHU
66DFWLYH
UHVSRQVH
672DFWLYH
5HDG\WRVWDUW
W
SS1 is selected during operation (selection via the control bit of the selected PROFIsafe telegram
or via F-DI).
The converter signals the status "SS1 active" via the status bit of the PROFIsafe telegram to the
PLC for further processing.
After the response time, the converter initiates braking along the OFF3 ramp. The SS1 delay time
is started at the same time.
The converter brakes the motor along the OFF3 ramp for the duration of the delay time.
STO is initiated automatically after the SS1 delay time expires (p9652).
The motor coasts down to a standstill. STO safely prevents an unwanted restart of the motor.
When SS1 is deselected (via PROFIsafe or F-DI), STO and SS1 are deactivated and the converter
goes into the "Ready for switching on" state.
The converter switches the motor on again with a positive signal edge at ON/OFF.
Note
OFF1 or OFF3 for active SS1
Switching the motor off via an OFF1 or OFF3 command while SS1 is active (e.g. by a limit
switch) does not influence the response of converter and motor.
SS1 remains active after the OFF command. After the delay time has elapsed, the converter
transitions to STO status.
212))
$FWLRQ 'HVHOHFW66
W
6SHHG
UHVSRQVH
0RWRU
7KHPRWRUFRDVWVGRZQ
WRDVWDQGVWLOO
W
'HOD\WLPH
&RQYHUWHU
66DFWLYH
UHVSRQVH
672DFWLYH
5HDG\WRVWDUW
W
SS1E is selected during operation (selection via the control bit of the selected PROFIsafe telegram
or via F-DI).
The converter signals the status "SS1 active" via the status bit of the PROFIsafe telegram to the
PLC for further processing.
The control system triggers the shutdown via the setpoint input. The SS1 delay time in the con‐
verter is started at the same time.
The motor is braked by the external setpoint input, and signals "SS1E selected" to the PLC.
STO is initiated automatically after the SS1 delay time expires (p9652).
The motor coasts down to a standstill. STO safely prevents an unwanted restart of the motor.
When SS1 is deselected (via PROFIsafe or F-DI), STO and SS1 are deactivated and the converter
goes into the "Ready for switching on" state.
The converter switches the motor on again with a positive signal edge at ON/OFF.
Note
SS1 cannot be interrupted
If SS1 is deselected again during this time, the STO function is selected and deselected again
immediately after the delay time has elapsed or the speed has dropped below the shutdown
speed. This terminates the SS1 function normally. It cannot be interrupted.
Overview
If Basic Function faults occur, the following stop responses can be triggered:
● STOP A
● STOP F
Internal event
An "internal event" is a major fault that causes the converter to bring the motor to a standstill
as quickly as possible by triggering a STOP reaction.
An "internal event" can be triggered, for example, if the converter detects a fault in the
monitoring channels during a data cross-check (e.g. F01611 "Defect in a monitoring channel").
An "internal event" can only be acknowledged using a fail-safe signal.
STOP A
For a STOP A, the converter safely switches off the torque of the connected motor immediately.
STOP A corresponds to STO.
STOP F
STOP F is triggered when a fault in the data cross-check of the monitoring channels is detected.
Consequently, STOP A is triggered and fault F01600 issued.
The transition time from STOP F to STOP A can be selected in p9658.
Note
The selected transition time from STOP F to STOP A (p9658) must be greater than or equal
to the delay time (p9652).
Drive response
The converter sets the bit "Internal event" after the discrepancy time has elapsed. You cannot
switch on the motor as long as this signal is active.
Note
Discrepancy time
To avoid incorrectly triggered fault messages, the selected discrepancy time in p9650 must
always be shorter than the shortest time between 2 switching events at these inputs (ON/OFF,
OFF/ON).
The converter indicates the discrepancy error when the RDY-LED flashes quickly red.
● The converter outputs a fault message on the numerical display. It signals the fault via the
web server and vie PROFIsafe
– "Discrepancy (fault F01611 or F30611 "Defect in a monitoring channel" with fault values
r0949 = 2000 or 2002)"
● The converter sets the error bit of the safety functions (= internal event).
Communication telegrams (Page 737) and Bit assignments of the process data
(Page 740)
Independent of the voltage levels present, the converter remains in the STO state until you
have acknowledged the "Internal event" state.
Table 4-1 Response times for control via terminals on the Control Unit and the Motor Module.
p9651 = 0 t_E = 8 ms
p9651 ≠ 0 t_E = p9651 + 5 ms
What is an acceptance?
The machine manufacturer is responsible in ensuring that the plant or machine functions
perfectly. As a consequence, after commissioning, the machine manufacturer must check
those functions or have them checked by specialist personnel, which represent an increased
risk of injury or material damage. This acceptance or validation is, for example, also specified
in the European machinery directive and essentially comprises two parts:
● Acceptance test: Checking the safety-relevant functions and machine parts after startup.
● Documentation: Generate an "Acceptance report" that describes the test results.
Supply information for the validation, e.g. the harmonized European standards
EN ISO 13849‑1 and EN ISO 13849‑2.
Documentation
The following must be documented for the converter:
● Result of the acceptance tests
● Settings of the integrated drive safety functions
This documentation must be countersigned.
Recommendations
With the acceptance test, you check whether the safety functions in the converter have been
set correctly.
● Perform the acceptance test with the maximum possible velocity and acceleration to test
the expected maximum braking distances and braking times.
● Alarm A01697:
This alarm is issued following each system startup and is not critical for acceptance.
After the acceptance test of the converter's safety functions, you must also check whether the
safety-related functions in the machine or system are functioning correctly.
Note
Examples of acceptance tests
The following acceptance tests are examples which demonstrate the basic procedure. They
are not suitable for every possible setting of the converter.
Note
When you replace the converter, an error message appears. Acknowledge this error message,
e.g. by switching off and on.
What does the acceptance test for the converter consist of?
Documentation
1. Supplement/change the hardware data
2. Supplement/change the software data (specify version)
Precondition
The converter is ready for operation.
● The converter signals neither faults nor alarms of the safety functions (r0945[0…7],
r2122[0…7]).
● STO is not active (r9734.0 = 0).
Procedure
Use the following procedure for the acceptance test of the Basic Function STO:
Switch on motor
1. Enter a speed setpoint ≠ 0.
2. Switch on the motor (ON command).
3. Check that the correct motor is running.
Select STO
1. Select STO while the motor is running.
Test each configured activation, e.g. via digital inputs and PROFIsafe.
2. Check the following:
– If a mechanical brake is not available, the motor coasts down.
A mechanical brake brakes the motor and holds it to ensure that it remains at a standstill.
– The converter signals neither faults nor alarms of the safety functions (r0945[0…7],
r2122[0…7]).
– The converter signals the following:
"STO is active" (r9734.0 = 1).
Deselect STO
1. Deselect STO.
2. Check the following:
– STO is not active (r9734.0 = 0).
– The converter signals neither faults nor alarms of the safety functions (r0945[0…7],
r2122[0…7]).
Precondition
The converter is ready for operation.
● The converter signals neither faults nor alarms of the safety functions (r0945[0…7],
r2122[0…7]).
● SBC is not active (r9734.0 = 0 and r0899.12 = 1).
Procedure
Use the following procedure for the acceptance test of the Basic Function SBC:
Switch on motor
1. Enter a speed setpoint ≠ 0.
2. Switch on the motor (ON command).
3. Check that the correct motor is running.
4. Enter the speed setpoint = 0.
Select SBC
1. Select the STO function or the SS1 function.
2. Check the following: The converter signals the following: "SBC is active" (r9734.0 = 1 and
r0899.12 = 0).
Deselect STO
1. Deselect STO.
2. Check the following:
– The converter signals the following: "SBC is not active" (r9734.0 = 0 and r0899.12 = 1).
– The converter signals neither faults nor alarms of the safety functions (r0945[0…7],
r2122[0…7]).
Precondition
The converter is ready for operation.
● The converter signals neither faults nor alarms of the safety functions (r0945[0…7],
r2122[0…7]).
● SS1 is not active (r9734.1 = 0).
Procedure
To perform the acceptance test of the SS1 Basic Function, proceed as follows:
Switch on motor
1. Enter a speed setpoint ≠ 0.
2. Switch on the motor (ON command).
3. Check that the correct motor is running.
Select SS1
1. Select SS1 while the motor is switched on.
Test each configured activation, e.g. via digital inputs and PROFIsafe.
2. In your machine, check the following:
– The motor brakes on the OFF3 ramp.
– SS1 is active (r9734.1 = 1).
– After the p9652 time has expired, the converter signals: "STO is active" (r9734.0 = 1).
Deselect SS1
1. Deselect SS1.
2. Check the following:
– SS1 is not active (r9734.1 = 0).
– The converter signals neither faults nor alarms of the safety functions (r0945[0…7],
r2122[0…7]).
NOTICE
Thermal damage to temperature-sensitive parts
Some parts of the electrical motor enclosure can reach temperatures that exceed 100 °C. If
temperature-sensitive parts, for instance electric cables or electronic components, come into
contact with hot surfaces then these parts can be damaged.
● Ensure that no temperature-sensitive parts come into contact with hot surfaces.
Note
Required checks
The checks listed below are a minimum benchmark and must be performed in any case.
Further checks before, during and after the installation of the motor depend on the system-
specific conditions and are the responsibility of the plant or system manufacturer.
● Thoroughly familiarize yourself with the safety instructions and observe the checklists below
before starting any work.
Check OK
General checks
Are the environmental conditions in the permissible range? See Chapter "Permissible
environmental conditions for the motor (Page 176)".
Checks regarding the mechanical system
Is the motor free of visible damage?
Have the mounting surfaces (e.g. flange, shaft) on the customer machine and on the
motor been cleaned?
Are the mounting surfaces free of corrosion?
Do the mounting dimensions (e.g. shaft diameter, shaft length, true run) on the customer
machine meet the specification?
NOTICE
Damage to shaft sealing rings caused by solvent
If shaft sealing rings come into contact with solvents when removing the corrosion protection,
the shaft sealing rings can be damaged.
● Avoid contact between solvents and shaft sealing rings.
NOTICE
Damage to the motor due to runout on the shaft extension
Runout and thrust on the shaft extension of the motor damage the motor.
● Mount the motor without runout and thrust on the shaft extension.
Motor Bolt DIN 7984 Washer ISO 7092 Tightening torque for bolts (not for electri‐
[mm] cal connections)
1FK2☐02 M4 4 (d2 = 8) 2.2 Nm
1FK2☐03 M5 5 (d2 = 9) 4 Nm
1FK2☐04 M6 6 (d2 = 11) 8 Nm
NOTICE
Damage to the motor due to runout on the shaft extension
Runout and thrust on the shaft extension of the motor can damage the motor.
● Mount the motor without runout and thrust on the shaft extension.
Mount or remove the power output elements (e.g. couplings, gear wheels, belt pulleys) using
suitable devices only (see figure).
● Use the threaded hole in the shaft extension.
● If required, heat up the output elements before mounting or removing.
● When removing the output elements, use an intermediate disk to protect the centering in
the shaft extension.
● If necessary, completely balance the motor together with the output elements according to
ISO 1940.
Note
Motors with feather key are half-key balanced. The motors have been balanced with half
a feather key.
Additional requirements for plants and systems in the United States / Canada (UL/cUL)
A label with the following number is provided with the device: A5E36790112.
Note the instructions on the label and attach the label in a clearly visible location close to the
converter in the control cabinet.
Installation notes
● Install the converter vertically with the flap for the LED display facing upwards.
:LGWK 'HS
WK
+HLJKW
!
ุ
! !
!
!
Permissible cable lengths for the connection of the motor to the converter.
NOTICE
Destruction of the motor if it is directly connected to the three-phase line supply
The motor will be destroyed if it is directly connected to the three-phase line supply.
● Only operate motors with the permitted converters.
The cables have a SPEED-CONNECT connector. This reduces the installation time and
costs, and increases the operational reliability of the drive.
● Check that the sealing surfaces of the connectors have not been damaged.
O
O
Motor Connec‐ Distance, point of Length of the plug Minimum bending radius, static
tor size rotation to NDE connection MC500 MC800 PLUS
l1 / mm l / mm R / mm
1FK2☐02 M12 40 61 23 29
1FK2☐03 22
1FK2☐04 M17 32.5 70 25 31
Note
A maximum of 10 twists are permitted so as not to impair the degree of protection of the motor.
˞
˞
You can also connect quick-connection cables with SPEED-CONNECT to motor connectors
as conventional cables with screw locks (fully threaded).
Note
We recommend cables equipped with SPEED-CONNECT connectors.
Connecting
1. Make sure that the SIEMENS logo on the connector enclosure is at the top or that the
arrows on both connectors are opposite to each other. This ensures that the pins and coding
keys of the connector and motor connector are aligned.
2. Push the connector into the motor connector up to the endstop.
3. Tighten the fastener or the screw cap per hand in a clockwise direction.
Disconnecting
1. Turn the fastener or the screw cap per hand in an anticlockwise direction up to the endstop.
2. Pull the connector out of the motor connector.
Note
To disconnect the plug-in connection, always pull the cable connector and not the cable.
Figure 5-9 Permissible and impermissible cable routing when connecting in a damp environment
Install the converter so that you are compliant with local regulations for erecting and installing
low-voltage systems.
Note
Safety devices
Install suitable protective equipment between the line supply and converter.
Technical specifications of the converter (Page 197)
Note
Operating displays for converter operation
If, when switching over a function from ON to OFF, an LED or other similar display is not lit or
not active; this does not indicate that the device is switched-off or in a no-current condition.
Observe the following product note about protection against indirect contact:
To protect against indirectly touching part of the motor circuit of a frequency converter and to
automatically shut down in the case of a fault according to DIN EN 60364-4-41 (VDE 0100-410)
(http://support.automation.siemens.com/WW/view/en/103474630)
then you must use additional residual current protective devices RCD (RCCB or MRCD),
type B.
● RCCB: Residual current circuit breaker
● MRCD: An MRCD comprises an RCM (differential current monitoring device), a measuring
current transducer and a circuit breaker with additional undervoltage release, listed in the
Technical data.
To prevent an RCD from unnecessarily tripping as a result of operational leakage currents,
the following preconditions must be fulfilled:
● The neutral point of the line supply is grounded.
● Use an RCCB type B with a response limit current of 300 mA. Connect the RCCB in series
with the overcurrent protective devices.
● Use a separate RCD for each converter.
● The motor cables are shorter than 50 m (164 ft) and shielded.
WARNING
Risk of electric shock and fire from a network with an excessively high impedance
Excessively low short-circuit currents can lead to the protective devices not tripping or tripping
too late, and so causing electric shock or a fire.
● In the case of a conductor-conductor or conductor-ground short-circuit, ensure that the
short-circuit current at the point where the inverter is connected to the line supply at least
meets the minimum requirements for the response of the protective device used.
● You must use an additional residual-current device (RCD) if a conductor-ground short
circuit does not reach the short-circuit current required for the protective device to respond.
The required short-circuit current can be too low, especially for TT systems.
WARNING
Risk of electric shock and fire from a network with an impedance that is too low.
Excessively high short-circuit currents can lead to the protective devices not being able to
interrupt these short-circuit currents and being destroyed, and so causing electric shock or a
fire.
● Ensure that the uninfluenced short-circuit current at the line terminal of the inverter does
not exceed the breaking capacity (SCCR or Icc) of the protective device used.
6WDWXV/('V
(UURUGLVSOD\
$FNQRZOHGJHHUURU
6ORWIRU6'FDUG
;
; 6HUYLFHLQWHUIDFH(WKHUQHW
9H[WHUQDO
GDLV\FKDLQIRUDGGLWLRQDO
FRQYHUWHUV
;
3UREHDQG
; IDLOVDIH
/LQHFRQQHFWLRQDQG GLJLWDOLQSXW
H[WHUQDOEUDNLQJUHVLVWRU
;3
352),1(7SRUW
; ;3
0RWRUFRQQHFWLRQ 352),1(7SRUW
;
(QFRGHUFRQQHFWLRQ
6KLHOGFRQQHFWLRQIRU
VKLHOGHGFDEOHV
FDEOHUHOLHIYLDFDEOHWLHIRU
RWKHUFDEOHV ;
0RWRUKROGLQJEUDNH
Note
Connection of motor holding brake, connector X107
Also connect the conductors for the motor holding brake to the connector at X107, even when
you are using a motor without holding brake.
Shielded cables
To ensure the proper functioning of the drive, use shielded cables for the connection of the
motor (OCC cable with connection of encoder and holding brake), of the external braking
resistor and of the fail-safe digital input.
Use the shield support that comes with the converter to connect the shield. Siemens
recommends connecting the shield - as shown in the figure - with the shield clamp that comes
with the prefabricated OCC cable for the motor connection.
● Connect the shield at both ends of the cable.
● Use cables with finely-stranded, braided shields.
● Do not interrupt the shield.
)HUULWHFRUHUHTXLUHGIRU)6%
IRU(0&&DWHJRU\&
2&&FRQQHFWLRQFDEOHWRWKH &RQQHFWLRQFDEOHIRUIDLOVDIHGLJLWDO
PRWRU LQSXWDQGSUREH
&RQQHFWLRQFDEOHIRUH[WHUQDO
EUDNLQJUHVLVWRU
Figure 5-11 Shield support with shield plate and shield clamps for prefabricated OCC cable
Note
Without the ferrite core, EMC Category C3 is achieved.
5.4.3.2 Connecting the line supply, motor, motor holding brake and encoder to the converter
/
1
1P
1P
Connect the shield of the motor connection cable to the shield plate over a large area. Use
commercially available clamps, the clamps supplied with the prefabricated cable or the shield
connection clamps supplied as accessories.
NOTICE
Damage to the device by connecting other motors or devices
Connecting other devices (motors, encoders) can destroy the converter or the connected
device.
● Only connect 1FK2 motors to this interface.
● Use only MOTION-CONNECT OCC cables from Siemens - or cables that you have
fabricated yourself with the correct pin assignment.
To connect the encoder, insert the Siemens IX connector as shown in the following in the X100
plug socket.
%5
%5
Note
Connection of motor holding brake, connector X107
Also connect the conductors for the motor holding brake to the connector at X107, even when
you are using a motor without holding brake.
'&3 '&3
5 5
5 5
6KLHOG
0
0
/
/
① 24 V external
② Loop-through for additional converters
Figure 5-17 X124 - 24 V external
Connecting high-speed digital inputs, temperature monitoring for external braking resistor and fail-safe
digital input
Digital inputs DI 0 and DI 1 are high-speed digital inputs and can be used as measuring inputs.
Digital inputs DI 2 and DI 3 form a fail-safe digital input.
The temperature monitoring for an external braking resistor can be connected to DI 4. When
the temperature of the external braking resistor is too high, the converter shuts down the motor.
/ ',
', ', ', )',
0 ',
/ ',
', ', /
0 ', ',
WRWKHQH[W
/LQH FRQYHUWHU 6WDWXVGLVSOD\
YLD/('
1 / 9 0 9
([WHU 0HPRU\
QDO RSWLRQDO
7 7 FDUG
9 0
;
(WKHUQHW ;
0
;
/ ,OLP 9
', 6 ,
0
9
)XVHRUFLUFXLWEUHDNHU ,
', 6
0
/LQHFRQWDFWRU
RSWLRQDO
', ;
',
/LQHILOWHU )', ', FXUUHQW
RSWLRQDO ; ', VRXUFLQJ
', FXUUHQW
/ (0& ',
1 9 VLQNLQJ
ILOWHU
'&3 ',
5 ,QWHUQDOEUDNLQJ
˽
5 UHVLVWRU
%UDNLQJUHVLVWRU
([WHUQDORSWLRQDO
352),1(7 ;3
352),1(7 ;3
;
8
9 (QFRGHU ;
:
0RWRUKROGLQJEUDNH ;
%5
%5
2QH&DEOH&RQQHFWLRQ2&&
; ;
9 9
', ',
0 0
9 9
', ',
0 0
; ;
', ',
', ',
)', )',
', ',
', ',
9 9
', ',
0 9
; ;
9 9
', ',
0 0
9 9
', ',
)'2 )'2
0 0
9
; ;
', ', 9
', ',
)', )',
', ',
', ',
9 9
', ',
0 0
Connection of the fail-safe digital input Connection of the fail-safe digital input with
with a fail-safe digital output a fail-safe digital output
Supported browsers
The web server integrated in the converter supports the following browsers:
6.1 Fundamentals
Preparations
1. Install the motor and converter according to the specifications in the following section:
Installing (Page 83)
2. Mount the motor on the mechanical system. Connect the motor to the converter.
3. Connect the converter to your commissioning device via the service interface (X127).
4. Switch the converter on.
The converter powers up and reads the motor data.
5. Start the browser for commissioning.
6. Enter the IP address of the converter in the input line of your browser.
Default IP address: 169.254.11.22.
NOTICE
Software manipulation when using non-encrypted connections (HTTP)
The HTTP protocol transfers data without encryption. This facilitates password theft, for
example, and can lead to data manipulation by unauthorized parties and thus ultimately to
damage.
● Limit access to HTTPS connections so that all data is transferred encrypted.
Note
The display also changes to the Login screen form if you do not enter a password within 10
minutes.
If you wish to assign an administrator password for the first time, switch the converter off and
on again so that the initial input screen form appears again.
Password reset
It will be no longer possible to access the converter if the administrator password is lost. In this
case, you must reset the password. To do this, use a memory card that contains a configuration
with a known password.
Procedure:
Load a configuration for a converter which has a known administrator password and reset it
to factory settings.
1. Insert an empty memory card (max. 2 GB) into the PC.
2. Copy the configuration to the memory card (as a minimum, to the USER directory).
3. Insert the memory card card into the converter and switch on the converter.
4. Open the web browser and log on as administrator with the known password.
5. Reset the converter to the factory settings.
Backup and restore (Page 153)
6. The converter starts with the factory settings. After the run-up, the input dialog for the
administrator password appears.
7. Re-assign the administrator password.
Remember the password or store the password in a safe place that cannot be accessed
by unauthorized persons.
8. Recommission the converter.
9. Save the changes.
① Device designation
② Status bar (from left to right):
Name of the converter (if entered) / Status of the converter / Fault and warning messages
③ Drop-down list for the language selection and to log out from the web server.
Displays the logged-in user and the set language
④ Active view of the web server (in the example: Start page after the user has logged in)
⑤ Action bar (from left to right):
Support information / Call control panel / Save retentively (RAM to ROM)
⑥ Navigation toolbar (see following "Navigation of the web server")
Figure 6-2 Basic structure of the web server
Navigation via the navigation bar Navigation via drop-down lists (drop-down menus)
The navigation bar of the web server has a multi- Alternatively, the screen forms can also be called in the active view of the
level structure. Example: web server via drop-down lists (drop-down menus). This also allows easy
navigation in small displays (smartphone).
0RW
You make changes to the parameter values in the table rows under the graphic display. It is
not possible to make entries in the graphics. However, the edited rows are highlighted context-
sensitive in the table and graphic.
In most cases you will be able to work with the parameters in the table directly below the
diagram.
In some cases, you must make the parameter settings which can only be found in the
parameter list of the converter.
Further information:
Adapt parameter list (Page 129)
6.4 Login/logout
Note
Configuring passwords for the users
You can configure the passwords of the two users in the system settings with administrator
rights (see Chapter "Setting or changing user accounts (Page 156)").
The following access rights apply for the users of the web server:
6.4.2 Login/logout
In order to be able to work in the web server, you must be logged in as "SINAMICS" or
"Administrator" user.
2. Enter the name of the user (Administrator or SINAMICS) in the "User name" field.
Automatic logout
If you are not using the web server, access to the web server is automatically logged out after
10 minutes. You must log in again to access the web server.
6.5 Commissioning
After being switched on, the converter starts extensive self-configuration. The most important
data is read from the electronic rating plate of the motor connected using the OCC cable and
used for the self-configuration. The following steps are required to complete the
commissioning:
● Name assignment of the converter (initialization) according to its technical application
● One Button Tuning for the optimal controller setting of the converter
Note
Rights required for commissioning
Administrator rights are essential for commissioning via the Web server:
( "Users and access rights (Page 114)")
Procedure
1. Select "Commissioning" and "Device" in the navigation.
Procedure
1. Select the "Optimization" submenu in the "Commissioning" navigation.
5. Enter the angle through which the motor and the connected machine are permitted to turn
for the required measurements (e.g. 360°) without the mechanical system being damaged.
The angle should be at least 60° in order to be able to determine useful controller
parameters. Generally, longer traversing distances result in better optimization results.
6. Click "OK".
The tuning through the One Button Tuning starts. No entries are possible during the tuning.
After the tuning has been completed, a message appears as to whether the "One Button
Tuning" was successful - or not. If the OBT was not successful, then optimization must be
repeated, possibly with modified entries.
A list in the lower part of the window shows how the settings have been changed by the
One button tuning.
Note
If the machine vibrates or whistles at certain speeds following One Button Tuning, then the
dynamic response setting is too high. In this case, select a lower dynamic response and
repeat the One Button Tuning.
7. After completing the controller tuning, you must return the master control over the converter.
Click "Return control".
8. Confirm the confirmation prompt with "Confirm".
The color bar is no longer displayed.
9. Click to save the data permanently.
Result
When One Button Tuning is completed, the basic commissioning of the converter is finished.
All other parameters are automatically preset according to the motor characteristic.
2. To close the control panel again, click the "Control panel" button again in the footer of the
web server or on the X at the top right in the header of the control panel.
6.6 Settings
Setting limits
1. Select "Parameters" and "Limits" in the navigation.
The table below the graphic shows the "Maximum speed" line of the speed limitation.
2. Enter the maximum speed in the input field of the same name.
3. Enter the two torque limit values.
– "Torque limit when motoring"
– "Torque limit when generating"
4. Click to save the data permanently.
Note
Automatic default setting
The values of the holding brake are automatically set correctly through the self-configuration
of the converter in accordance with the electronic rating plate. As a consequence, generally
the displayed values no longer have to be corrected.
The values in this screen form serve more as a check. It may only be necessary to adapt the
values for suspended axes.
Procedure
1. Select "Parameters" and "Brake control" in the navigation.
2. Select the appropriate input signal in the table for the measuring inputs and the temperature
control:
– "Digital input 0 (X130/DI 0)": Probe 1
– "Digital input 1 (X130/DI 1)": Probe 2
– "Digital input 2, 3 (X130/DI 2+, DI 2-, DI 3+, DI 3-)":
Fail-safe digital input for the Safety Integrated Basic Function "STO" or "SS1".
The configuration is performed via the Safety commissioning. By clicking "Safety", you
open the Safety commissioning and can make the appropriate settings there.
"Safety commissioning (Page 135)"
– "Digital input 4 (X130/DI 4)": Temperature monitoring of ext. braking resistor
3. Click to save the data permanently.
You can make all of the essential settings after commissioning using the setting web pages.
In certain cases, it may be necessary to make extra settings or evaluations of status and
measured value outputs.
The available parameter list in which you can view or change all the available device
parameters, is used for this purpose.
You will find a detailed description of all S210 parameters in the following Section:
Parameters (Page 225).
/RZHURUXSSHU
YDOXHOLPLW
H[FHHGHG
&RQWUROOHUWXQLQJQRLVHDPSOLWXGH
,QDFWLYH
① Adjustable parameters with this icon have several indices or bit arrays
② Name of the parameter
③ Input field for the parameter value
④ Select the parameter value via the drop-down menu
⑤ Invalid value
⑥ Unit of the parameter
Figure 6-14 Example of the representation of an adjustable parameter
● Display parameters
Display parameters are for information purposes only and cannot be changed.
6WDWRUZLQGLQJWHPSHUDWXUH r&
① Display parameters with this icon have several indices or bit arrays
Figure 6-15 Example of the representation of a display parameter
This advanced list view is only temporary. The next time the web server is called, the simple
view is displayed again.
Grouping parameters
You can combine individual parameters of the parameter list into a personal group. You can
activate the checkboxes in the "My group" column to assign the selected parameters to your
personal group.
1. In the "My group" column, activate all checkboxes of the parameters that you want to take
into your group.
2. Click to save the data permanently.
The parameter list is limited further after every further filter setting (the filters are linked via an
AND operation). The filters can be set in any order.
Note
Collapsing the filter bar
The filter bar is opened per default. To collapse the filter bar, click the arrow next to "Search
and Filters".
Resetting filters
As long as you are logged in to the Web server and the filter settings have not changed, the
parameter list is always displayed with the last filter settings. To reset all filter settings in the
parameter list, proceed as follows:
Click "Reset all filters" at the top right in the filter bar.
Note
Due to the specified supplementary torque setpoint via the controller, a switchover of the
supplementary torque is also possible. Thus, when the product is lifted, a supplementary torque
can be specified that is different from the supplementary torque for a movement without a load.
6.8.1.1 Overview
The web server provides you with a commissioning Wizard that navigates you through all of
the steps required when commissioning safety. The basic handling is shown in the following
diagram:
● The safety commissioning must have been fully completed. It is not possible to cancel
commissioning.
● A password can be defined to protect against unauthorized changes to safety settings. This
can either be done at the beginning or at the end of the safety commissioning.
The converter issues an alarm if a password has not been defined.
● The fault and alarm messages for safety are provided in the general message window.
● The set safety settings can be checked in the read mode at a later point in time. The
commissioning mode is not required for this.
2. Specify how you want to continue with the Safety commissioning. The following options are
available for selection:
– Execute commissioning step-by-step (Page 138)
– Check commissioning in read mode (Page 148)
Function selection
Select the desired functions and the control method in the "Function selection".
4. Assign a safety password. You can also define the safety password later. As long as a
safety password is not defined, the drive issues an alarm.
Configuring the safety password (Page 146)
5. If a safety password has been defined, enter the safety password in the input field.
You cannot make any further Safety settings without this entry.
6. To start the configuration of the individual Safety commissioning steps, click "Start" in the
footer of the screen form.
Parameterization
Adapt the required settings in the "Parameterization" tab.
1. Parameterize the emergency stop function with the "SI SS1 delay time".
The following settings are possible:
– SS1 delay time = 0 → STO (stop category 0 according to EN 60204-1)
– SS1 delay time ≠ 0 → SS1 (stop category 1 according to EN 60204-1)
2. If the converter is not to be autonomously braked in the event of an emergency stop ("SS1
with OFF3"), but via the higher-level controller ("SS1E external stop"), select this via the
drop-down list "SI SS1 drive-based braking response".
3. Click "Continue".
The "Control" commissioning step is activated.
If, in the HW configuration, a PROFIsafe telegram was already selected and downloaded to
the converter, then this telegram is displayed in field "PROFIsafe telegram from HW
configuration".
1. In the "PROFIsafe telegram" drop-down list, select the desired PROFIsafe telegram and
enter the PROFIsafe address. The PROFIsafe telegram and PROFIsafe address must
match the definitions in the higher-level controller.
2. Click "Continue".
The "Test stop" commissioning step is activated.
1. If you want to change the discrepancy time, click the "SI F-DI discrepancy time" field.
An input dialog with the same name opens. Adjust the set discrepancy time and confirm
with "OK".
2. If you want to change the debounce time, click the "SI STO/SS1 debounce time" field.
An input dialog with the same name opens. Set the debounce time and confirm with "OK".
3. Click "Continue".
The "Test stop" commissioning step is activated.
1. To change the time interval, click in the "Test stop timer" field. An input dialog with the same
name opens.
Set the timer interval here and confirm by clicking "OK".
The remaining time up to the test stop is determined automatically and displayed.
2. Click "Continue".
The "Completion" commissioning step is activated.
Completion
You have made all of the settings for commissioning the drive-integrated safety functions. If,
up until now a safety password has not been configured, then it can now be configured in this
step (see the following chapter).
1. Click "Finish".
The following prompt appears. Click "Finish" again to confirm the prompt.
If both checkmarks are checked, the converter imports the settings of the safety
commissioning and performs a restart when the user clicks "Finish".
After the restart, the commissioning of the drive-integrated safety functions is completed
and the browser once again shows the home page of the web server.
Note
The safety password is write protection specified in the appropriate standards to prevent
against maloperation by unauthorized users.
The password must also include the following elements to provide protection against
unauthorized access, e.g. unauthorized persons.
● At least 8 characters
● Uppercase and lowercase letters
● Numbers and special characters (e.g.: ?!%+ ...)
It is not permissible that the safety password is used elsewhere.
Checking the password
The length of the password is checked by the converter. There is no check for uppercase and
lowercase letters and special characters!
You must enter the safety password in this input field so that you can continue with the
other safety settings.
5. Click to save the data permanently.
The individual commissioning steps are displayed in the header of the "Safety
Commissioning" screen form.
2. Click the "Continue" button each time and check the settings that are required Safety
commissioning.
You receive the following individual information via separate display areas:
● "Diagnostics of the safety functions"
Shows which safety functions have been activated in the converter.
● "Status"
Information on the status of the converter. If a forced checking procedure is required, then
this is displayed. The times for the forced checking procedure of the timer and the remaining
time up to the forced checking procedure are displayed.
The display area also shows whether internal events (e.g. software errors in the converter
or a discrepancy in the monitoring channels) have taken place and whether the
communication is OK.
● "Checksums"
Uses the safety logbook to determine changes to safety parameters and to indicate if a
component has been replaced/exchanged. Shows changes in the form of functional
checksums with time stamps.
Setting filters
1. In the "Search" field, enter a search term (any number of characters) for which you want to
search in the message list.
The search term is also active in the "Alarm" column in the message list.
2. In the two "Filter by Date" fields, enter a period for which the messages are to be displayed.
The message list is limited further after every filter setting. The filters can be set in any
order.
Note
Collapsing the filter bar
The filter bar is opened per default. To collapse the filter bar, click the arrow next to "Search
and Filters".
Resetting filters
As long as you are logged in to the Web server and the filter settings have not changed, the
message list is always displayed with the last filter settings. To reset all filter settings in the
message list, proceed as follows:
Click "Reset all filters" at the top right in the filter bar.
The message list then displays the unfiltered view of the messages again.
The values are displayed in hexadecimal format in the default setting. You can switch the
display of individual values between binary and hex format by clicking on the button to the right
of the value.
You can perform backup and restoration functions in the 3 setting ranges of the view.
Note
The parameterization is saved in encrypted form during a data backup. Therefore, it is not
possible to check or edit parameters.
Password requirements
The password must fulfill the following conditions to provide protection against unauthorized
access, e.g. cyber attacks:
● At least 8 characters
● Both uppercase and lowercase letters
● Numbers and special characters (e.g.: ?!%+ ...)
● Different passwords for different types of access (administrator / user)
The length of the password is checked by the converter. There is no check for uppercase and
lowercase letters and special characters!
Remember the passwords or store the passwords in a safe place that cannot be accessed by
unauthorized persons.
Procedure
1. Select "System" and "Settings" in the navigation.
2. Select the "User Accounts" tab.
Perform the following steps to configure the user accounts for the web server:
NOTICE
Software manipulation when using non-encrypted connections (HTTP)
The HTTP protocol transfers data without encryption. This facilitates password theft, for
example, and can lead to data manipulation by unauthorized parties and thus ultimately
to damage.
● Limit access to HTTPS connections so that all data is transferred encrypted.
Note
Certificates for the secure data transfer
To secure an HTTPS connection, it requires security certificates for the encryption of the
access. Detailed information on working with these security certificates can be found in
Section "Certificates for the secure data transfer (Page 750)".
You can make the connection between the converter and the commissioning device more
secure through the settings described in the following.
Procedure
1. Select "System" and "Settings" in the navigation.
2. Select the "IP Connections and Addresses" tab.
Note
Switchover from HTTP to HTTPS
If you were logged-in via HTTP, then after activating option "Only use HTTPS connection",
you will be logged-out. To log in again, you must set a secure HTTPS connection (https://...)
to the converter.
Note
If the NTP server cannot be accessed for more than 10 minutes when NTP time
synchronization is activated, alarm A01097 "NPT server cannot be accessed" appears.
If you want to deactivate this time synchronization or activate it again, proceed as follows:
1. Select "System" and "Settings" in the navigation.
2. Select the "Drive System Time and Date" tab.
Click the links to open the desired support addresses - or to open in another browser - or
to copy at a later point in time.
2. Click "Close" to close the Support information.
OK button
You can acknowledge the faults whose cause has been corrected with the OK button.
① LED display
② Three-digit display
③ OK button
LED is ON
LED is OFF
Please contact Technical Support for LED states that are not described in the following.
RDY Explanation
The electronics power supply is missing or outside the permissible tolerance range.
Remedy: Check the power supply.
Temporary status after the supply voltage is switched on.
Converter waits until the power supply is switched off and switched on again after a firmware
update
RDY Explanation
Firmware update in progress for the connected DRIVE-CLiQ components.
or
COM Explanation
No bus fault is present.
When the RDY LED lights up green and the COM LED is off, the converter is ready for
communication.
Temporary status after the supply voltage is switched on.
No bus connection
Remedy: Make sure that the bus cables are connected and are not damaged.
Table 7-4 Explanation of the RDY and COM LEDs - firmware update
WARNING
Operation without functioning protective devices
Operation without functioning protective devices can cause death or severe injury.
● Operate the motor, even in test operation, only with functioning protective devices.
If there are deviations from normal operation or if faults occur, proceed as follows.
● Identify the fault using the "Possible faults" table.
Also observe the converter messages.
● Try to correct the fault using the "Fault causes and remedial measures" key table.
If the fault still cannot be resolved after taking the measures stated above, please contact the
manufacturer or the Siemens Service Center.
7.4 Alarms
Alarms
Alarms have the following properties:
● Alarms have no direct influence on the drive.
● Alarms disappear again when the cause is eliminated.
● Alarms cannot be acknowledged.
● Alarms are displayed as follows:
– In the PLC according to the PROFIdrive message class
– On the drive via LEDs
– At the drive using the three-digit display according to the PROFIdrive message classes
– In the Web server via the "Diagnostics - Messages" view
Alarm code or alarm value describe the cause of the alarm.
Reference
You can find additional information on alarms in Chapter "Overview of faults and alarms
(Page 291)".
7.5 Faults
Faults
Faults have the following properties:
● The fault causes the motor to be switched off.
● Faults must be acknowledged.
● Faults are displayed as follows:
– In the PLC according to the PROFIdrive message class
– On the drive via LEDs
– At the drive using the three-digit display according to the PROFIdrive message classes
– In the Web server via the "Diagnostics - Messages" view
Acknowledge fault
Before you can acknowledge a fault, you must have resolved the cause of the fault.
To acknowledge, you have the following options:
● Acknowledging via the PLC
● Acknowledging via the OK button under the front cover
● Switch off the converter power supply and switch on again
● Acknowledging via the Web server
Faults detected during the converter-internal monitoring of hardware and firmware can be
acknowledged only by switching the power supply off and on again. In the list of faults, you
will find the information on limitations when acknowledging at the corresponding fault codes.
Reference
You can find additional information on faults in Chapter "Overview of faults and alarms
(Page 291)".
Property Version
Environmental conditions for transport in the transport packaging according to Class 2K3 to EN 60721‑3‑2 except for the "air
temperature" and "condensation" environmental factors
Climatic environmental con‐ ‑ 15° C … + 70° C
ditions
Highest relative humidity < 95% at 40° C, condensation not permissible
Mechanical environmental Shock and vibration permissible according to 3M8 to EN 60721‑3‑3: Single shocks (6 ms)
conditions max. 250 m/s²
Protection against chemical Protected according to Class 2C2
substances
Biological environmental Suitable according to Class 2B2
conditions
Property Version
Environmental conditions for long-term storage in the transport packaging according to Class 1K3 to EN 60721‑3‑1 except
for the "air temperature", "highest relative humidity" and "condensation" environmental factors
Climatic environmental con‐ ‑ 15° C … + 55° C
ditions
Highest relative humidity < 60% - condensation not permissible
Mechanical environmental Vibration-free storage space, vrms< 0.2 mm/s
conditions
Protection against chemical Protected according to Class 1C2
substances
Biological environmental Suitable according to Class 1B2
conditions
Duration ● Six months for the above-mentioned conditions.
● For storage periods of six months up to a maximum of two years, special preservation
measures are required.
Further information Calling Support information (Page 162)
Property Version
Ambient conditions during operation according to 3K4 to EN 60721‑3‑3 except for the "low air temperature", "condensation"
and "low air pressure" environmental factors
Installation altitude Up to 1000 m above sea level without limitations
Derating factors (Page 180)
Property Version
Climatic environmental con‐ ● Temperature range: - 15 °C 1) … + 40 °C
ditions1) ● Relative humidity: 5 … 95%, condensation not permitted
● Absolute air humidity: 1 ...29 g/m³
● Rate of temperature change2): 0.5°/min
● Atmospheric pressure: 89 1), 3) ... 106 kPa4)
● Solar radiation: 700 W/m² 2)
● Movement of the air: 1.0 m/s
● Water (other than rain): See protection class
Mechanical environmental ● Vibration levels permissible according to Class 3M8 to EN 60721-3-3: Max. 50 m/s²
conditions ● Shock permissible according to Class 3M8 to EN 60721-3-3
Protection against chemical Protected according to 3C2 to EN 60721‑3‑3
substances
Biological environmental Suitable according to 3B2 to EN 60721‑3‑3
conditions
Pollution Suitable for environments with degree of pollution 2 according to EN 61800-5-1
Cooling air Clean and dry air
The motors are not suitable for operation
● In a vacuum5)
● In salt-laden or aggressive atmospheres
● Outdoors
1)
Increased ruggedness with regard to low temperature and low atmospheric pressure better than 3K3 according to EN
60721-3-3
2)
Averaged over a period of 5 min
3)
The limit value of 89 kPa covers applications at altitudes up to 1000 m.
4)
Conditions in mines are not considered.
5)
Operation in a vacuum is not permissible because of the low dielectric strength and poor heat dissipation.
8.1.3 Cooling
The 1FK2 is a non-ventilated motor.
To ensure sufficient heat dissipation when installed, the motor requires a minimum clearance
of 100 mm from adjacent components on three lateral surfaces.
● Maintain theses clearances irrespective of the following mounting variants.
The data in the table refers to an ambient temperature of 40 °C and an installation altitude up
to 1000 m above sea level.
If the environmental conditions are different, derating may be required. For more information,
refer to Chapter:
"Derating factors (Page 180)"
For larger mounting surfaces, the heat dissipation conditions improve.
Table 8-2 Power derating depending on the installation altitude and the ambient temperature
Calculate the derating value for ambient temperatures that are not shown here and installation altitudes
below the maximum values by interpolating. For example: 40 °C at 1500 m above sea level = derating
factor 0.975
Note
It is permissible that the radial shaft sealing ring runs dry.
With degree of protection IP65, it is not permissible for liquid to collect in the flange.
The service life of the radial shaft sealing ring is approximately 25000 operating hours.
The radial shaft seal ring shortens the usable shaft end.
For additional information, see Chapter:
"Shaft extension (Page 183)"
8.1.6 Balancing
The motors are balanced according to DIN ISO 8821.
Motors with featherkey in the shaft are half-key balanced.
A mass equalization for the protruding half key must be taken into account for the output
elements.
Y UPVSHUP >PPV@
*UDGH$
Q>USP@
Select the measuring points according to ISO 10816-1 section 3.2. The vibration values must
not exceed the specified limits at any measuring point.
Shaft Shaft dimensions Shaft dimensions with Feather key Centering thread
height Diameter x length in mm IP65 Width x height x DIN 332-DR
Diameter x length in mm length in mm
20 8 x 25 8 x 18 2 x 2 x 10 M3
14 x 30 14 x 21.5 5 x 5 x 16 M5
30 optional 11 X 23 1) - - M4
40 19 x 40 19 x 32 6 x 6 x 22 M6
1)
The optional 11 mm x 23 mm shaft extension is only available without a keyway and without
a shaft sealing ring (IP65).
Table 8-3 Radial eccentricity tolerance of the shaft to the frame axis (referred to cylindrical shaft ends)
/
① Motor
② Motor shaft
③ Dial gauge
Figure 8-2 Checking the radial eccentricity
Table 8-4 Concentricity and axial eccentricity tolerance of the flange surface to the shaft axis (referred
to the centering diameter of the mounting flange)
$ %
PP
PP
Shaft Reference type Average oper‐ Point of load Radial force Axial force, Axial force,
height without brake ating speed (distance reference dynamic 1) static 1)
M0 / Nm n / rpm from the type FA dyn / N FA stat / N
flange) FR / N
l / mm
20 0.32 3000 20 120 20 30
30 1.27 3000 25 280 40 75
40 3.18 3000 30 400 60 100
1) The specified axial forces are determined by the spring loading and therefore also apply for motors
with holding brake.
Note
Applications with an angular toothed pinion directly on the motor are not permitted with
standard bearings because the permissible axial forces are exceeded.
WARNING
Unintentional movements through inadequate braking effect
If you use the holding brake incorrectly, e.g. as a safety brake, or you ignore the number of
permissible operating cycles of the brake, the brake does not close reliably. As a
consequence, there may be no brake effect. Unintentional movements of the machine or
system can result in death or serious injury.
● Observe the permissible number of operating cycles and EMERGENCY STOP properties.
● Operate the motor only in conjunction with an intact brake.
● Avoid repeated brief acceleration of the motor against a holding brake that is still closed.
The holding brakes of the 1FK2 have a torsional backlash of less than 1°. The following table
contains additional technical data regarding the holding brakes:
Motor type Holding Dyn. brak‐ Opening Closing Maximum Maximum Total oper‐
torque ing torque time time permissi‐ EMER‐ ating ener‐
M4 at M1m ble single GENCY gy (serv‐
120 °C switching STOP ice life)
energy speed
M4 / Nm M1 / Nm t / ms t / ms W/J n / rpm Wmax / kJ
1FK2☐02 0.32 0.2 50 15 7.4 8000 0.5
1FK2☐03 1.3 1.1 90 20 62 7500 5
1FK2☐04 3.3 3 110 30 268 7500 35
Holding torque M4
The holding torque M4 is the highest permissible torque for the closed brake in steady-state
operation without slip (holding function when motor is at standstill). The data applies for the
state at operating temperature (120 °C).
Dynamic braking torque M1m
The dynamic braking torque M1m is the smallest mean dynamic braking torque that can occur
for an EMERGENCY STOP.
Opening time and closing time
The delay times that occur when switching the brake.
Maximum permissible single switching energy
The maximum permissible single switching energy of an individual EMERGENCY STOP
procedure.
After an EMERGENCY STOP with the maximum single switching energy, allow for a cooling
time of at least 5 minutes before you put the motor into operation again.
Maximum EMERGENCY STOP speed
Maximum permitted speed for a safe EMERGENCY STOP procedure.
Total operating energy (service life)
The total switching energy is the sum of the single switching energy (switching energy for each
EMERGENCY STOP procedure). If the total switching energy is exceeded, flawless
functioning of the brakes can no longer be guaranteed.
● Refurbish the motor.
J load / kgm2 Load moment of inertia of the mounting part on the motor with brake (kgm2)
182.4 Constant for calculating the circular frequency and SI units
8.1.13.1 1FK2102-0AG
The rated data applies when the converter is connected to 1AC 230V.
8.1.13.2 1FK2102-1AG
The rated data applies when the converter is connected to 230 V 1 AC.
8.1.13.3 1FK2103-2AG
The rated data applies when the converter is connected to 230 V 1 AC.
8.1.13.4 1FK2103-4AG
The rated data applies when the converter is connected to 230 V 1 AC.
8.1.13.5 1FK2104-4AK
The rated data applies when the converter is connected to 230 V 1 AC.
8.1.13.6 1FK2104-5AK
The rated data applies when the converter is connected to 230 V 1 AC.
8.1.14.1 1FK2203-2AG
The rated data applies when the converter is connected to 230 V 1 AC.
8.1.14.2 1FK2203-4AG
The rated data applies when the converter is connected to 230 V 1 AC.
W>V@
,,Q>@
>@
,UDWHG,+,V,PD[
I>+]@
Figure 8-5 Permitted output current at low frequencies
,UDWH
,K
W>V@
7V
Property Version
Interference immunity The converters are suitable for use in the first and second environments without restrictions
Interference emission Category C2 Up to a motor cable length of 10 m 1)
- second environment Up to a motor cable length of 25 m with additional external line filter
Category C3 Up to a motor cable length of 25 m
Up to a motor cable length of 50 m with additional external line filter
1)
Converters of frame size FSB require a ferrite core for the motor cable to reach category C2.
Connecting the converter (Page 93).
Note
Installation in Category C2 environments
Converters that are installed in environments of category C2 require a connection approval for
the low-voltage supply system. In this regard, contact your power system operator.
Property Version
Ambient conditions for transport in the transport packaging
Climatic ambient conditions ‑40 °C … +70 °C, according to Class 2K4 to EN 60721‑3‑2
maximum humidity 95 % at 40 °C
Mechanical ambient condi‐ Shock and vibration permissible according to 2M3 to EN 60721‑3‑2
tions
Protection against chemical Protected according to Class 2C2 to EN 60721‑3‑2
substances
Biological environmental Suitable according to Class 2B2 to EN 60721‑3‑2
conditions
Ambient conditions for long-term storage in the product packaging
Climatic ambient conditions ‑25 °C … +55 °C, according to Class 1K4 to EN 60721‑3‑1
1)
Table 8-5 Maximum permissible output current depending on the installation altitude and ambient
temperature
Ambient temperature [° C]
Installation altitude 50 45 40
[m] up to Output current [%]
1000 100
2000 90 100
3000 80 90 100
4000 70 80 90
Property Version
Line voltage 200 V … 240 V 1 AC, ±10 %
Output voltage 0 V 3 AC … input voltage
Input frequency 50 Hz … 60 Hz, ±10%
Output frequency 0 … 550 Hz
Relative supply short-circuit RSC ≥ 25
power
Power factor λ > 0.9
Overvoltage category to IEC/ ● Up to 2000 m: The converter insulation is designed for surge voltages of overvoltage
EN 61800-5-1 category III.
● More than 2000 m: The surge voltages must be limited to values of overvoltage category
II, using an isolation transformer, for example.
Pulse frequency 8 kHz
Short-circuit current rating ≤ 65 kA rms
(SCCR) and branch protection Branch protection and short-circuit strength according to UL and IEC
Protective devices (https://support.industry.siemens.com/cs/ww/en/view/
109748999)
Degree of protection according IP20 Must be installed in a control cabinet
to EN 60529
Electronics power supply 24 V DC, -15% … +20%, Imax = 1.6 A (PELV or SELV)
Control mode Servo control
Protection functions Ground fault protection, output short-circuit protection, overvoltage/undervoltage protection,
I2t detection, IGBT overtemperature protection
Type High-speed digital inputs Fail-safe input Digital input for monitoring
for probe or reference (F-DI) the temperature of an ex‐
marks ternal braking resistor
Number 2 (DI 0, DI 1) 1 (DI 2 and DI 3) 1 (DI 4)
● Low level -30 V ... +5 V -30 V ... +5 V -30 V ... +5 V
and ≤ 2 mA and ≤ 2 mA and ≤ 2 mA
● High level 15 V ... 30 V 15 V ... 30 V 15 V ... 30 V
● Current consumption 6 mA 5 mA 6 mA
● Delay time, typ. L → H 5 µs 50 μs 5 µs
● Delay time, typ. H → L 50 μs 100 µs 50 μs
● Electrical isolation No Yes No
Conductor cross section, max. 1.5 mm² 1.5 mm² 1.5 mm²
Designation and use Cable type Connector Outer diame‐ Minimum For con‐ Article number 1)
size ter bending ra‐ nection to
dius, static motor
Dmax / mm R / mm
Motor connection cable M12 9.7 23.5 1FK2☐02 6FX5002-8QN04-
MC500 OCC for predom‐ 1FK2☐03 ☐☐☐☐
inantly fixed installation
M17 10.5 25.5 1FK2☐04 6FX5002-8QN08-
☐☐☐☐
Motor connection cable M12 9.7 28.2 1FK2☐02 6FX8002-8QN04-
MC800 OCC for use in a 1FK2☐03 ☐☐☐☐
cable carrier
M17 10.5 30.6 1FK2☐04 6FX8002-8QN08-
☐☐☐☐
Extension cable M12 9.7 23.5 1FK2☐02 6FX5002-8QE04-
MC500 OCC for predom‐ 1FK2☐03 ☐☐☐☐
inantly fixed installation
M17 10.5 25.5 1FK2☐04 6FX5002-8QE08-
☐☐☐☐
Extension cable M12 9.7 28.2 1FK2☐02 6FX8002-8QE04-
MC800 OCC for use in a 1FK2☐03 ☐☐☐☐
cable carrier
M17 10.5 30.6 1FK2☐04 6FX8002-8QE08-
☐☐☐☐
1)
The last 4 positions (☐☐☐☐) define the cable length corresponding to the length code.
The length code can be found in Chapter:
Connection cables between the motor and the converter (Page 217)
Technical data and notes for cable carrier use with MC800 PLUS
Note
You require an MC800 PLUS cable to connect the motor using a cable carrier.
● The cable fixings must be attached at both Cable routed in a cable carrier
ends at an appropriate distance away from
the end points of the moving parts in a dead
zone.
When laying cables, comply with the instructions given by the cable carrier manufacturer.
PVt 027,21&211(&73/86
$FFHOHUDWLRQ
Y PPLQ
P
7UDYHOGLVWDQFH
Figure 8-7 Permissible acceleration levels for MOTION-CONNECT 800 PLUS cables
Note
Additional fixing of the cable
If between the cable strain relief on the cable carrier and the terminal at the motor, part of the
cable is hanging loose or is not routed, we recommend that the cable is additionally fixed for
vibration load and with horizontal or vertical cable entries.
● Also fix the cable where the motor is fixed so that machine vibrations are not transferred
to the connector.
).¨
0
K
M
M
K
',1'50
NN
$$
$
).¨
0
M
M
',1'50EHL
',1'50EHL O
NN
$$
$
).¨
0
N
M
N
M
',1'50
NN
$$
$
ෘ[
[
ෘ[
[
ෘ[
[
WARNING
Risk of injury through falling motors or machine components
Motors and machine components can fall when being dismantled from the machine. They
can cause serious injury or property damage.
● Secure the machine components being dismantled to prevent them falling.
The removal of the motor must be performed and/or supervised by qualified personnel with
appropriate expert knowledge.
Components
Sort the components for recycling according to whether they are:
● Electronic waste
● Scrap iron, e.g. shield plates
● Aluminum
● Insulating materials and plastics
You can find further details regarding motors and converters here:
Technical specifications (Page 175).
Designation and use Cable type For connection Connector Article number 1)
to motor size
Motor connection cable OCC 1FK2☐02 M12 6FX5002-8QN04-☐☐☐☐
MC 500 for predominantly fixed in‐ 1FK2☐03
stallation
1FK2☐04 M17 6FX5002-8QN08-☐☐☐☐
Motor connection cable OCC 1FK2☐02 M12 6FX8002-8QN04-☐☐☐☐
MC 800PLUS for use in cable carrier 1FK2☐03
1FK2☐04 M17 6FX8002-8QN08-☐☐☐☐
Extension cable OCC MC 500 for 1FK2☐02 M12 6FX5002-8QE04-☐☐☐☐
predominantly fixed installation 1FK2☐03
1FK2☐04 M17 6FX5002-8QE08-☐☐☐☐
Extension cable OCC MC 800PLUS 1FK2☐02 M12 6FX8002-8QE04-☐☐☐☐
for use in cable carriers 1FK2☐03
1FK2☐04 M17 6FX8002-8QE08-☐☐☐☐
1)
The last 4 positions (☐☐☐☐) define the cable length corresponding to the length code
O
Procedure
1. Determine the required cable length l **. Consider having cable in reserve for strain-free
routing.
2. Determine the length code for the required length l ** corresponding to the following
overview. The stretched lengths (*) are added automatically for the prefabricated cables.
3. Also select the cable type, the desired cable version, and the required connectors for the
article number
);q 4q q q q q q
2&&027,21&211(&7
&DEOHW\SH &RGH
0&
0&3/86
&DEOHYHUVLRQ &RGH
0RWRUFRQQHFWLRQFDEOH 1
&RQQHFWRUVL]H &RGH
([WHQVLRQFDEOH (
0
0
([DPSOHVIRUOHQJWKFRGH
P $% /HQJWK &RGH
P $& P
P '*
PD[P )$ /HQJWK &RGH
P $
P %
P &
P '
P (
P )
/HQJWK &RGH
P $
P %
P &
P '
P (
P )
P *
P +
P -
P .
/HQJWK &RGH
P
P
P
P
P
P
P
P
P
Figure 11-2 Structure of the article number with length code for an OCC MOTION-CONNECT cable
4. Order the required cable with the article number thus determined.
11.4 Accessories
These SD cards are also required to save licenses of functions that require a license. It is not
possible to use commercially available SD cards.
Note
Permissible memory cards
The integrated card reader supports SD cards up to a memory capacity of 2 GB.
SDHC or SDXC cards are not supported.
Article number Rated current Type of connec‐ Conductor cross- Degree of Dimensions (W x H x D)
tion section protection
6SL3203-0BB21-8VA0 18 A 200 V … 240 V 0.3 mm … 10 mm2 IP20 59 x 153 x 55
1 AC
The mounting flange is installed on the external wall of the control cabinet. It ensures the
degree of protection of the control cabinet.
● Install the mounting flange as specified in the enclosed installation instructions.
Shaft sealing ring - IP65 degree of protection kit for the motor
The shaft sealing ring can be used as spare part or for retrofitting.
Note
You can order a motor with shaft sealing ring (degree of protection IP65) directly.
Additional information about ordering degree of protection IP65 can be found in Chapter:
"Ordering data of the motor (Page 215)"
The motor satisfies degree of protection IP65 when the shaft sealing ring is installed.
Motor article number Figure of the shaft sealing ring Article number of the degree of pro‐
tection kit
1FK2☐02 1FK2902-0GC00
1FK2☐03 1FK2903-0GC00
1FK2☐04 1FK2904-0GC00
Terminal X1: Line connection and connection for external braking resistor
Also connect the conductors for the motor holding brake to the connector at X107, even when
you are using a motor without holding brake.
3DUDPHWHUQXPEHU
3DUDPHWHUQDPH 1XPEHUIRUPDWRIWKH *URXSWRZKLFKWKH
SDUDPHWHU SDUDPHWHUEHORQJV
6WDWHWKDWWKHFRQYHUWHUPXVWEHLQWR
HQVXUHWKDWWKHYDOXHRIWKHSDUDPHWHUFDQ
EHFKDQJHG
3DUDPHWHUQXPEHU
3DUDPHWHUQDPH
U 6SHHGDFWXDOYDOXHVPRRWKHG
Data type: FloatingPoint32 P group: Displays, signals Scaling: p2000
Parameter number
The parameter number is made up of a "p" or "r", followed by the parameter number and
optionally the index or bit array.
Can be changed
The "-" sign indicates that the parameter can be changed in any object state and that the
change will be effective immediately.
The information "C1(x), C2(x), T, U" ((x): optional) means that the parameter can be changed
only in this drive unit state and that the change will not take effect until switching to another
state. One or more states are possible.
The following states are possible:
● C1(x) Device commissioning C1: Commissioning 1
The device is being commissioned (p0009 > 0). The pulses cannot be enabled.
The parameter can only be changed in the following device commissioning settings (p0009
> 0):
– C1: Can be changed for all settings p0009 > 0.
– C1(x): Can only be changed for settings p0009 = x.
A changed parameter value does not take effect until the device commissioning is exited
with p0009=0.
● C2(x) Drive object commissioning C2: Commissioning 2
The drive is being commissioned (p0009 = 0 and p0010 > 0). The pulses cannot be enabled.
The parameter can only be changed in the following drive commissioning settings (p0010
> 0):
– C2: Can be changed for all settings p0010 > 0.
– C2(x): Can only be changed for settings p0010 = x.
A changed parameter value does not take effect until drive commissioning mode is exited
with p0010=0.
● U Operation U: Run
The pulses have been enabled.
● T ready T: Ready to run
The pulses have not been enabled and the state "C1(x)" or "C2(x)" is not active.
Data type
The following data types are available for the parameters:
P group
Specifies the functional group to which this parameter belongs.
Scaling
Specification of the reference variable with which a signal value is automatically converted
with a BICO interconnection.
The following reference variables are available:
● p2000 … p2003: Reference speed, reference voltage, etc.
● PERCENT: 1.0 = 100%
● 4000H: 4000 hex = 100% (word) or 4000 0000 hex = 100% (double word)
Parameter values
● Min
Minimum value of the parameter [unit]
● Max
Maximum value of the parameter [unit]
● Def
Value when delivered [unit]
NOTICE
For a display not equal to 0, the drive is either powering up or an enable signal is missing. The control sends these
enable signals.
For several missing enable signals, the corresponding value with the highest number is displayed.
Note
The drive only controls the motor speed in the "Operation" state (r0002 = 0).
OC: Operating condition
EP: Enable Pulses (pulse enable)
RFG: Ramp-function generator
COMM: Commissioning
MotID: Motor data identification
SS2: Safe Stop 2
STO: Safe Torque Off
1: Device configuration
30: Parameter reset
Note
The drive can only be switched on when in the "Ready" state (p0009 = 0).
NOTICE
For p0010 = 95:
The safety commissioning Wizard must be carried out in the web server after changing safety parameters. These
changes become effective after carry out all of the commissioning steps of the wizards.
Note
The drive can only be switched on when in the "Ready" state (p0010 = 0).
NOTICE
After the drive is switched on, the system starts to determine the motor temperature with an assumed model value.
This means that the value for the motor utilization is only valid after a stabilization time.
Note
The value of -200 indicates that there is no measuring signal.
For index [0]:
Maximum value of the inverter temperatures (r0037[5...10]).
For index [1]:
Maximum value of the depletion layer temperatures (r0037[13...18]).
The maximum value is the temperature of the hottest inverter or depletion layer.
In the case of a fault, the particular shutdown threshold depends on the power unit, and cannot be read out.
Note
For index [0]:
Difference between the energy drawn and energy that is fed back.
Note
The value r0046 = 0 indicates that all enable signals for this drive are present.
Bit 00 = 1 (enable signal missing), if:
- the signal source in p0840 is a 0 signal.
- there is a "switching-on inhibited".
Bit 01 = 1 (enable signal missing), if:
- the signal source in p0844 or p0845 is a 0 signal.
Bit 02 = 1 (enable signal missing), if:
- the signal source in p0848 or p0849 is a 0 signal.
Bit 03 = 1 (enable signal missing), if:
- the signal source in p0852 is a 0 signal.
Bit 04 =1 (armature short-circuit active), if:
- the signal source in p1230 has a 1 signal
Bit 05, Bit 06: Being prepared
Bit 08 = 1 (enable signal missing), if:
- safety functions have been enabled and STO is active.
- a safety-relevant signal is present with a STOP A response.
STO enabled via terminals:
- the pulse enable via terminal EP is missing (booksize: X21, chassis: X41), or the signal source in p9620 is for a 0
signal.
STO enabled via PROFIsafe or TM54F:
- STO is selected via PROFIsafe or TM54F.
Bit 09 = 1 (enable signal missing), if:
- the signal source in p0864 is a 0 signal.
Bit 10 = 1 (enable signal missing), if:
- the signal source in p1140 is a 0 signal.
Bit 11 = 1 (enable signal missing) if the speed setpoint is frozen, because:
- the signal source in p1141 is a 0 signal.
- the speed setpoint is entered from jogging and the two signal sources for jogging, bit 0 (p1055) and bit 1 (p1056)
have a 1 signal.
Bit 12 = 1 (enable signal missing), if:
- the signal source in p1142 is a 0 signal.
- When activating the function module "basic positioner" (r0108.4 = 1), the signal source in p1142 is set to a 0 signal.
Bit 16 = 1 (enable signal missing), if:
- there is an OFF1 fault response. The system is only enabled if the fault is removed and was acknowledged and the
"switching-on inhibited" withdrawn with OFF1 = 0.
Bit 17 = 1 (enable signal missing), if:
- commissioning mode is selected (p0009 > 0 or p0010 > 0).
- there is an OFF2 fault response.
- the drive is inactive (p0105 = 0) or is not operational (r7850[DO-Index]=0).
Bit 18 = 1 (enable signal missing), if:
- OFF3 has still not been completed or an OFF3 fault response is present.
Bit 19 = 1 (internal pulse enable missing), if:
- synchronization is running between the basic clock cycle, DRIVE-CLiQ clock cycle and application clock cycle.
Bit 20 =1 (internal armature short-circuit active), if:
- the drive is not in the state "S4: Operation" or "S5x" (refer to function diagram 2610).
- the internal pulse enable is missing (r0046.19 = 0).
Bit 21 = 1 (enable signal missing), if:
The pulses have been enabled and the speed setpoint has still not been enabled, because:
- the holding brake opening time (p1216) has still not expired.
- the motor has still not been magnetized (induction motor).
- the encoder has not been calibrated (U/f vector and synchronous motor)
Bit 22: Being prepared
Bit 26 = 1 (enable signal missing), if:
- the drive is inactive (p0105 = 0) or is not operational (r7850[DO-Index]=0).
- the function "parking axis" is selected (BI: p0897 = 1 signal)..
- all power units of a parallel connection are deactivated (p0125, p0895).
NOTICE
The value is updated with a sampling time of 1 ms.
Note
Absolute current value = sqrt(Iq^2 + Id^2)
The absolute current actual value is available smoothed (r0027) and unsmoothed (r0068).
Note
The DC link voltage is available smoothed (r0026) and unsmoothed (r0070).
Note
The value is available smoothed (r0031) and unsmoothed (r0080).
Note
The mechanical active power is available smoothed (r0032 with 100 ms, r0082[1] with p0045) and unsmoothed
(r0082[0]).
For index [3]:
Smoothing time constant = 4 ms
NOTICE
If, in the switched-off state (pulse inhibit), the supply voltage is higher than the entered value, the Vdc controller may
be automatically deactivated in some cases to prevent the motor from accelerating the next time the system is
switched on. In this case, an appropriate alarm A07401 is output.
Note
Setting ranges for p0210 as a function of the rated power unit voltage:
U_rated = 400 V:
- p0210 = 380 ... 480 V (AC/AC), 510 ... 720 V (DC/AC)
U_rated = 500 V:
- p0210 = 500 ... 600 V (AC/AC), 675 ... 900 V (DC/AC)
U_rated = 660 ... 690 V:
- p0210 = 660 ... 690 V (AC/AC), 890 ... 1035 V (DC/AC)
U_rated = 500 ... 690 V:
- p0210 = 500 ... 690 V (AC/AC), 675 ... 1035 V (DC/AC)
The precharging switch-in threshold for the DC link voltage (Vdc) is calculated from p0210:
Vdc_pre = p0210 * 0.82 * 1.35 (AC/AC)
Vdc_pre = p0210 * 0.82 (DC/AC)
The undervoltage thresholds for the DC link voltage (Vdc) are calculated from p0210 as a function of the rated power
unit voltage:
U_rated = 400 V:
- U_min = p0210 * 0.78 (AC/AC) > 330 V, p0210 * 0.60 (DC/AC) > 380 V
U_rated = 500 V:
- U_min = p0210 * 0.76 (AC/AC) > 410 V
U_rated = 660 ... 690 V:
- U_min = p0210 * 0.82 (AC/AC) > 565 V, p0210 * 0.63 (DC/AC) > 650 V
U_rated = 500 ... 690 V:
- U_min = p0210 * 0.82 (AC/AC) > 420 V, p0210 * 0.63 (DC/AC) > 480 V
CAUTION
In order to prevent incorrect measurement values, these parameters may not be written during an active
measurement.
Note
DI: Digital Input
Refer to the encoder interface for PROFIdrive.
CAUTION
In order to prevent incorrect measurement values, these parameters may not be written during an active
measurement.
Note
DI: Digital Input
Refer to the encoder interface for PROFIdrive.
Note
DI: Digital Input
The inversion has no effect on the status display of the digital inputs (r0722).
Note
DI: Digital Input
For bit 00, 01:
DI 0 and DI 1 are fast digital inputs and can be used to connect a measuring probe (p0488, p0489).
For bits 02, 03:
DI 2 and DI 3 form a fail-safe digital input.
For bit 04:
DI 4 is intended to monitor the temperature of the external brake resistor.
Note
For bits 00, 01, 02, 04, 05, 06, 09:
For PROFIdrive, these signals are used for status word 1.
For bit 13:
When the "Safe Brake Control" (SBC) is activated and selected, the brake is no longer controlled using this signal.
For bit 14, 15:
These signals are only of significance when the "extended brake control" function module is activated (r0108.14 = 1).
Note
If a value is not equal to 999, a telegram is set and the automatically set interconnections in the telegram are inhibited.
The inhibited interconnections can only be changed again after setting value 999.
Note
The sign-of-life monitoring is disabled for p0925 = 65535.
NOTICE
The properties of the fault buffer should be taken from the corresponding product documentation.
Note
The buffer parameters are cyclically updated in the background (refer to status signal in r2139).
Drive faults are signaled using parameters r0945, r0947, r0948 and r0949.
NOTICE
The time comprises r2130 (complete days) and r0948 (milliseconds, incomplete day).
Note
The buffer parameters are cyclically updated in the background (refer to status signal in r2139).
The structure of the fault buffer and the assignment of the indices is shown in r0945.
Note
Example:
r0964[0] = 42 --> SIEMENS
r0964[1] = 5410 --> SINAMICS S210 PN
r0964[2] = 409 --> first part of the firmware version V04.09 (for second part, refer to index 6)
r0964[3] = 2017 --> year 2017
r0964[4] = 1705 --> 17th of May
r0964[5] = 1 --> 1 drive object
r0964[6] = 100 --> second part, firmware version (complete version: V04.09.01.00)
Note
When the parameter is read via PROFIdrive, the Octet String 2 data type applies.
Note
Example:
r0975[0] = 42 --> SIEMENS
r0975[1] = 11 --> SERVO drive object type
r0975[2] = 102 --> first part, firmware version V01.02 (second part, refer to index 10)
r0975[3] = 2003 --> year 2003
r0975[4] = 1401 --> 14th of January
r0975[5] = 1 --> PROFIdrive drive object, type class
r0975[6] = 9 --> PROFIdrive drive object sub-type class 1
r0975[7] = 2 --> drive object number = 2
r0975[8] = 0 (reserved)
r0975[9] = 0 (reserved)
r0975[10] = 600 --> second part, firmware version (complete version: V01.02.06.00)
NOTICE
After changing the value, it is not possible to change parameters until the operation has been completed.
Note
After all of the parameters have been reset to their factory setting, the system must be commissioned for the first time
again.
Reset is realized in the non-volatile memory.
Procedure:
1. Set p0009 = 30 (parameter reset).
2. Set p0976 = 1 The system is powered up again.
p0976 is automatically set to 0 and p0009 is automatically set to 1 after this has been carried out.
NOTICE
The drive power supply may only be switched off after data has been saved (i.e. after data save has been started,
wait until the parameter again has the value 0).
Writing to parameters is inhibited while saving.
Note
Information about the individual indices can be taken from the following literature:
PROFIdrive Profile Drive Technology
Note
This time can be exceeded if the DC link voltage reaches its maximum value.
Note
DSC: Dynamic Servo Control
CAUTION
For the setting p1215 = 0, if a brake is used, it remains closed. If the motor moves, this will destroy the brake.
Setting p1215 = 2 is not permissible if the brake is used to hold loads.
Note
For p1216 = 0 ms, the monitoring and the message A07931 "Brake does not open" are deactivated.
NOTICE
If the selected closing time is too short with respect to the actual closing time of the brake, then the load can sag.
If the closing time is selected to be too long with respect to the actual closing time of the brake, the control works
against the brake and therefore reduces its lifetime.
Note
For p1217 = 0 ms, the monitoring and the message A07932 "Brake does not close" are deactivated.
Note
In order that standstill is identified, the speed threshold in p1226 must be somewhat higher than the speed actual
value noise level.
Note
The monitoring is deactivated with p1227 = maximum value.
Note
This parameter is only effective if the filter is set as a PT1 low pass.
Note
The higher the set P gain, the faster and more unstable the control.
Note
The shorter the integral time, the faster and more unstable the control.
Note
The value in p1538 may not exceed the value in p1521.
Note
The value in p1539 may not exceed the value in p1521.
NOTICE
After changing parameter p1821, the direction of rotation is not automatically adapted in the safety area. The following
parameters can be used to set the direction of rotation for safety monitoring:
-SI Motion encoder configuration safety functions - position actual value sign change (p9516.1/p9316.1, only active
for operation with encoder)
00 Bit 0 ON OFF -
01 Bit 1 ON OFF -
02 Bit 2 ON OFF -
03 Bit 3 ON OFF -
04 Bit 4 ON OFF -
05 Bit 5 ON OFF -
06 Bit 6 ON OFF -
07 Bit 7 ON OFF -
08 Bit 8 ON OFF -
09 Bit 9 ON OFF -
10 Bit 10 ON OFF -
11 Bit 11 ON OFF -
12 Bit 12 ON OFF -
13 Bit 13 ON OFF -
14 Bit 14 ON OFF -
15 Bit 15 ON OFF -
16 Bit 16 ON OFF -
17 Bit 17 ON OFF -
18 Bit 18 ON OFF -
19 Bit 19 ON OFF -
20 Bit 20 ON OFF -
21 Bit 21 ON OFF -
22 Bit 22 ON OFF -
23 Bit 23 ON OFF -
24 Bit 24 ON OFF -
25 Bit 25 ON OFF -
26 Bit 26 ON OFF -
27 Bit 27 ON OFF -
28 Bit 28 ON OFF -
29 Bit 29 ON OFF -
30 Bit 30 ON OFF -
31 Bit 31 ON OFF -
NOTICE
The time comprises r2136 (days) and r2109 (milliseconds).
Note
The buffer parameters are cyclically updated in the background (refer to status signal in r2139).
The structure of the fault buffer and the assignment of the indices is shown in r0945.
Dependency: When setting p2111 = 0, all of the alarms that have been removed from the alarm buffer [0...7] are transferred into
the alarm history [8...63] - and alarm buffer [0...7] is deleted.
See also: r2122, r2123, r2124, r2125
Note
The parameter is reset to 0 at POWER ON.
NOTICE
The properties of the alarm buffer should be taken from the corresponding product documentation.
Note
The buffer parameters are cyclically updated in the background (refer to status signal in r2139).
Alarm buffer structure (general principle):
r2122[0], r2124[0], r2123[0], r2125[0] --> alarm 1 (the oldest)
...
r2122[7], r2124[7], r2123[7], r2125[7] --> Alarm 8 (the latest)
When the alarm buffer is full, the alarms that have gone are entered into the alarm history:
r2122[8], r2124[8], r2123[8], r2125[8] --> Alarm 1 (the latest)
...
r2122[63], r2124[63], r2123[63], r2125[63] --> alarm 56 (the oldest)
NOTICE
The time comprises r2145 (days) and r2123 (milliseconds).
Note
The buffer parameters are cyclically updated in the background (refer to status signal in r2139).
The structure of the alarm buffer and the assignment of the indices is shown in r2122.
Note
The buffer parameters are cyclically updated in the background (refer to status signal in r2139).
The structure of the alarm buffer and the assignment of the indices are shown in r2122.
Description: Displays the time in milliseconds referred to the day that the alarm was resolved.
Dependency: See also: r2122, r2123, r2124, r2134, r2145, r2146
NOTICE
The time comprises r2146 (days) and r2125 (milliseconds).
Note
The buffer parameters are cyclically updated in the background (refer to status signal in r2139).
The structure of the alarm buffer and the assignment of the indices is shown in r2122.
NOTICE
The time comprises r2130 (days) and r0948 (milliseconds).
Note
The buffer parameters are cyclically updated in the background (refer to status signal in r2139).
Note
0: No fault present.
Note
0: No alarm present.
Note
The buffer parameters are cyclically updated in the background (refer to status signal in r2139).
Note
The buffer parameters are cyclically updated in the background (refer to status signal in r2139).
NOTICE
The time comprises r2136 (days) and r2109 (milliseconds).
Note
The buffer parameters are cyclically updated in the background (refer to status signal in r2139).
NOTICE
The time comprises r2145 (days) and r2123 (milliseconds).
Note
The buffer parameters are cyclically updated in the background (refer to status signal in r2139).
NOTICE
The time comprises r2146 (days) and r2125 (milliseconds).
Note
The buffer parameters are cyclically updated in the background (refer to status signal in r2139).
Note
If the motor speed is less than the threshold value set in p2175 - and the motor is operated for longer than 200 ms at
the torque limit - then the motor is shut down and a fault is output.
Note
If value = 4:
Synchronization of the time in the drive with the time specified by the higher-level control system.
Note
For bit 03:
Activation of speed feedforward control.
For bit 04:
Activation of speed/torque feedforward control in the drive.
For bit 07:
Activation of the voltage precontrol.
Note
The value for the closed-loop position control is required by a higher-level control system.
Note
HF: High Frequency
LF: low frequency
For bit 00:
A PRBS signal (pseudo random binary signal) is superimposed on the current setpoint to be able to better identify the
mechanical controlled system.
For bit 01:
The identified mechanical resonance points are suppressed using current setpoint filters.
For bit 02:
The maximum speed controller gain is determined from the identified mechanical controlled system.
For bits 03, 04:
The measured value buffer length is set using these bits:
Bit 04 = 0 and bit 03 = 0 -> buffer length = 256
Bit 04 = 0 and bit 03 = 1 -> buffer length = 512
Bit 04 = 1 and bit 03 = 0 -> buffer length = 1024
Bit 04 = 1 and bit 03 = 1 -> buffer length = 2048
For bit 05:
A Hamming window is used to filter the measured time signals.
For bit 06:
The measurement checks the current controller frequency response and this is taken into account in the speed
controller loop. For high amplitudes in p5298, it is possible that the measurement is unsuccessful, as the converter
reaches its voltage limit.
For bits 07, 08, 09:
The measurement bandwidth is set using these bits:
Bit 09 = 0, bit 08 = 0, bit 07 = 0 -> bandwidth = 50 Hz
Bit 09 = 0, bit 08 = 0, bit 07 = 1 -> bandwidth = 100 Hz
Bit 09 = 0, bit 08 = 1, bit 07 = 0 -> bandwidth = 200 Hz
Bit 09 = 0, bit 08 = 1, bit 07 = 1 -> bandwidth = 400 Hz
Bit 09 = 1, bit 08 = 0, bit 07 = 0 -> bandwidth = 800 Hz
Bit 09 = 1, bit 08 = 0, bit 07 = 1 -> bandwidth = 1600 Hz
Zu Bit 10, 11:
Number of measuring periods.
Bit 11 = 0 and bit 10 = 0 -> number of measurements = 1
Bit 11 = 0 and bit 10 = 1 -> number of measurements = 2
Bit 11 = 1 and bit 10 = 0 -> number of measurements = 4
Bit 11 = 1 and bit 10 = 1 -> number of measurements = 8
For bit 12:
The PRBS signal is switched to the speed setpoint (in front of the filter).
For bit 13:
The input signal for the torque actual value is taken from in front of the current setpoints filters.
Note
The higher the dynamic factor, the faster and more unstable the control.
Note
If p5300 = -1:
One Button Tuning is deactivated and p5300 is automatically set = 0. Further, the presetting values for the speed
controller are restored.
If p5300 = 0:
To permanently save the values for the speed controller that have been determined, the parameters must be saved
in a non-volatile memory.
If p5300 = 1:
One Button Tuning is active.
The moment of inertia is determined once using a test signal. The controller parameters and current setpoint filters
are additionally determined once using a noise signal as excitation source. The steps to be executed can be configured
using p5301.
Note
For bit 00:
The speed controller gain is determined and set using a noise signal.
For bit 01:
Possibly required current setpoint filters are determined and set using a noise signal.
As a consequence, a higher dynamic performance can be achieved in the speed control loop.
For bit 02:
Using this bit, the moment of inertia is determined using a test signal. If this bit is not set, then the load moment of
inertia must be manually set using parameter p1498. The test signal must have been previously set using parameters
p5308 and p5309.
For bit 07:
With this function, these axes are adapted to the dynamic response set in p5275. This is necessary for interpolating
axes. The time in p5275 should be set according to the axis with the lowest dynamic response.
Note
For bit 00 = 1: The speed controller gain was set using One Button Tuning.
For bit 01 = 1: The current setpoint filter was set using One Button Tuning
For bit 02 = 1: The moment of inertia was determined.
Note
A value of 360 degrees corresponds to one motor revolution.
The position before the pulse enable is used as zero point.
Note
If, within this time, no setting values can be determined, then the drive is shut down with the corresponding fault.
Note
Pe: PROFIenergy profiles
Note
Pe: PROFIenergy profiles
Note
For two connections (Shared Device or system redundancy) the display in the index depends on the sequence in
which the connections are established.
The IP addresses of controllers 1 and 2 are displayed in r8961 and r8962.
The following states are displayed for system redundancy:
Primary controller: r8936[x] = 13
Backup controller: r8936[x] = 11
If value = 10:
If the connection remains in this state, then when using PROFINET IRT the following can apply:
- topology error (incorrect port assignment).
- synchronization missing.
r8937[0...5] PN diagnostics
Data type: Unsigned32 P group: -
Description: Display to diagnose the cyclic PROFINET connections.
Index: [0] = Number of cyclic connections
[1] = Number of send subslots of all connections
[2] = Number of send net data (bytes) of all connections
[3] = Number of receive subslots of all connections
[4] = Number of receive net data (bytes) of all connections
[5] = Connection type (RT, IRT)
Note
For index [5]:
Bit 0 = 1: there is at least one RT connection.
Bit 1 = 1: there is an IRT connection.
Note
BI:p8984[1] = 1 signal:
PROFINET interface X150 is enabled for access to the web server.
BI:p8984[1] = 0 signal:
PROFINET interface X150 is enabled for access to the web server.
Note
The acceptance test mode can only be selected if the motion monitoring functions integrated in the drive are enabled
(p9601.2).
Note
A change only becomes effective after a POWER ON.
SDI: Safe Direction (safe motion direction)
SLS: Safely Limited Speed
SOS: Safe Operating Stop
SS2E: Safe Stop 2 external (Safe Stop 2 with external stop)
SSM: Safe Speed Monitor (safety-relevant feedback signal from the speed monitoring)
Note
For the commissioning tool, after changing over the axis type, the units dependent on the axis type are only updated
after a project upload.
A change only becomes effective after a POWER ON.
NOTICE
When the "SLP" function is activated, the modulo function must be deactivated as otherwise fault F01681 will be
output.
If the absolute position is not enabled, then the parameterized modulo value is not taken into account.
Note
SLP: Safely Limited Position
SP: Safe Position
Note
A change only becomes effective after a POWER ON.
Note
SS1: Safe Stop 1 (corresponds to Stop Category 1 acc. to EN60204)
SS1E: Safe Stop 1 external (Safe Stop 1 with external stop)
For bit 00:
When the function is activated, a safety-relevant acknowledgment (internal event acknowledge) can be performed by
selecting/deselecting STO.
For bit 01:
When the function is activated, the active setpoint velocity limit (CO: r9733) is set to zero when STOP F is active.
For bit 03:
When the bit is activated – when selecting function SS1 or activating a STOP B – an SS1E or a STOP B with Stop,
which should be externally initiated, is triggered instead of SS1 with a drive-based braking response. As a
consequence, brake monitoring (SBR, SAM) is deactivated.
Note
For safe functions that are not enabled (p9501 = 0), the following applies:
- p9513 is automatically set when the system powers up.
For safety functions that are enabled (p9501 > 0), the following applies:
- p9513 is checked to see that it matches the encoder.
Note
- after starting the copy function (p9700 = 57 hex), p9515.0...5 are set according to the encoder.
For safe functions that are not enabled (p9501 = 0), the following applies:
- p9515.16 is automatically set when the system powers up.
For safety functions that are enabled (p9501 > 0), the following applies:
- p9515.16 is checked to see that it matches the encoder.
Note
For safe functions that are not enabled (p9501 = 0), the following applies:
- p9518 is automatically set when the system powers up.
For safety functions that are enabled (p9501 > 0), the following applies:
- p9518 is checked to see that it matches the encoder.
Note
G1_XIST1: encoder 1 position actual value 1 (PROFIdrive)
For safe functions that are not enabled (p9501 = 0), the following applies:
- p9519 is automatically set when the system powers up.
For safety functions that are enabled (p9501 > 0), the following applies:
- p9519 is checked to see that it matches the encoder.
NOTICE
The fourth decimal point can be rounded-off depending on the size of the entered number (from 3 places before the
decimal point).
Note
After starting the SI Motion copy function, this parameter is set after the encoder.
Note
After starting the SI Motion copy function, this parameter is set after the encoder.
Note
For safe functions that are not enabled (p9501 = 0), the following applies:
- p9525 is automatically set when the system powers up.
For safety functions that are enabled (p9501 > 0), the following applies:
- p9525 is checked to see that it matches the encoder.
Note
MSB: Most Significant Bit
For safe functions that are not enabled (p9501 = 0), the following applies:
- p9529 is automatically set when the system powers up.
For safety functions that are enabled (p9501 > 0), the following applies:
- p9529 is checked to see that it matches the encoder.
Note
SOS: Safe Operating Stop
Note
SLS: Safely Limited Speed
Note
The active actual speed limit is selected via safety-relevant inputs.
When selecting SOS or a STOP A ... D, setpoint 0 is specified in r9733.
SLS: Safely Limited Speed
Note
For a "linear axis with rotating motor" and factory setting of p9520, p9521 and p9522, the factory setting of p9542
corresponds to a position tolerance of 36 ° on the motor side.
Note
The filter time is effective only if the function is enabled (p9501.16 = 1).
The parameter is included in the data cross-check of the two monitoring channels.
The set time is rounded internally to an integer multiple of the monitoring clock cycle.
SSM: Safe Speed Monitor (safety-relevant feedback signal from the speed monitoring)
Note
SAM: Safe Acceleration Monitor (safe acceleration monitoring)
SBR: Safe Brake Ramp (safe brake ramp monitoring)
SSM: Safe Speed Monitor (safety-relevant feedback signal from the speed monitoring)
Note
The velocity hysteresis is effective only if the function is enabled (p9501.16 = 1).
The parameter is included in the data cross-check of the two monitoring channels.
SSM: Safe Speed Monitor (safety-relevant feedback signal from the speed monitoring)
Note
SAM: Safe Acceleration Monitor (safe acceleration monitoring)
Description: Sets the delay time for the SLS changeover and for the activation of SOS for the "SLS" and "SOS" functions.
When transitioning from a higher to a lower safely limited speed level, and when activating SOS, within this delay time,
the "old" speed level remains active.
This delay is also applicable when activating SLS from the state "SOS and SLS inactive" and activating SOS from the
state "SOS inactive".
Note
The set time is rounded internally to an integer multiple of the monitoring clock cycle.
SLS: Safely Limited Speed
SOS: Safe Operating Stop
Note
The set time is rounded internally to an integer multiple of the monitoring clock cycle.
SOS: Safe Operating Stop
Note
The set time is rounded internally to an integer multiple of the monitoring clock cycle.
SOS: Safe Operating Stop
Note
The set time is rounded internally to an integer multiple of the monitoring clock cycle.
Note
The set time is rounded internally to an integer multiple of the monitoring clock cycle.
Note
The set time is rounded internally to an integer multiple of the monitoring clock cycle.
STO: Safe Torque Off
Note
The set time is rounded internally to an integer multiple of the monitoring clock cycle.
Note
STO: Safe Torque Off
Note
The shutdown velocity has no effect for a value = 0.
SS1: Safe Stop 1
STO: Safe Torque Off
12: STOP C with delayed stop response when the bus fails
13: STOP D with delayed stop response when the bus fails
Index: [0] = Limit value SLS1
[1] = Limit value SLS2
[2] = Limit value SLS3
[3] = Limit value SLS4
Dependency: See also: p9531, p9580
Note
In an extended sense, bus failure is interpreted here as a communication error in the control signals of the safety
functions (e.g. via PROFIsafe).
SLS: Safely Limited Speed
Note
SDI: Safe Direction (safe motion direction)
Note
The set time is rounded internally to an integer multiple of the monitoring clock cycle.
SDI: Safe Direction (safe motion direction)
Note
In an extended sense, bus failure is interpreted here as a communication fault in the control signals of the safety
functions (e.g. via PROFIsafe).
SDI: Safe Direction (safe motion direction)
Note
SAM: Safe Acceleration Monitor (safe acceleration monitoring)
SBR: Safe Brake Ramp (safe brake ramp monitoring)
SSM: Safe Speed Monitor (safety-relevant feedback signal from the speed monitoring)
For p9568 = 0, the following applies:
The value in p9546 (SSM) is applied as the velocity limit for SAM/SBR.
Note
Acceptance test mode can only be selected if the safe motion monitoring functions are enabled.
Note
In an extended sense, bus failure is interpreted here as a communication error in the control signals of the safety
functions (e.g. via PROFIsafe).
The main use of the wait time is the function "Extended stopping and retraction" (ESR).
The set time is rounded internally to an integer multiple of the monitoring clock cycle.
Note
The set time is rounded internally to an integer multiple of the monitoring clock cycle.
The set time is internally limited (lower limit) to 2 safety monitoring clock cycles.
Note
The set time is rounded internally to an integer multiple of the monitoring clock cycle.
Note
Example:
r9590[0] = 5, r9590[1] = 10, r9590[2] = 1, r9590[3] = 0 --> SI Motion version V05.10.01.00
Description: Sets the enable signals for the safety functions integrated in the drive and the type of selection.
Only a selection of the subsequently listed settings is permissible:
0000 hex:
Safety functions integrated in the drive inhibited (no safety function).
0001 hex:
Basis functions are enabled via the onboard terminals.
0008 hex:
Basis functions are enabled via PROFIsafe.
0009 hex:
Basis functions are enabled via PROFIsafe and onboard terminals.
Bit field: Bit Signal name 1 signal 0 signal FP
00 STO enabled via terminals: Enable Inhibit -
03 Enable PROFIsafe Enable Inhibit -
Note
A change always becomes effective only after a POWER ON. Exception: change to p9601.0 becomes immediately
effective.
STO: Safe Torque Off
SS1: Safe Stop 1 (corresponds to Stop Category 1 acc. to EN60204)
SI: Safety Integrated
Note
The "SBC" function is not activated until at least one safety monitoring function has been enabled (i.e. p9501 not equal
to 0 and/or p9601 not equal to 0).
The parameterization "No motor holding brake available" and "Safe Brake Control" enabled (p1215 = 0, p9602 = 1)
does not make sense if a motor holding brake is not being used.
SBC: Safe Brake Control
SI: Safety Integrated
Note
A change only becomes effective after a POWER ON.
The PROFIsafe address in the drive must be identical with the address in the control.
Note
A change only becomes effective after a POWER ON.
To select the PROFIdrive telegram, PROFIsafe must have been enabled (p9601.3 = 1).
Note
For p9612 = 0 (STOP A):
The drive safely switches off the motor, the motor coasts down.
For p9612 = 1 (STOP B):
The drive brakes the motor with OFF3 ramp-down time until standstill is detected. STOP A is then selected.
The following must be observed:
- the transition time STOP F to STOP A (p9658) must be set longer or equal to the delay time (p9652).
Note
F-DI: Fail-safe Digital Input
Note
The debounce time is rounded to whole milliseconds.
Example:
Debounce time = 1 ms: Fault pulses of 1 ms are tolerated; only pulses longer than 2 ms result in a response.
Debounce time = 3 ms: Fault pulses of 3 ms are tolerated; only pulses longer than 4 ms result in a response.
The set debounce time impacts the response time of the safety function.
Note
Pulse cancellation after failure of PROFIsafe communication is delayed by this time if "STOP B" is set (p9612 = 1).
SS1: Safe Stop 1 (corresponds to Stop Category 1 acc. to EN60204)
Note
When p9653 is set = 1, the switchover is made from SS1 to SS1E - and the SS1 response is transferred to the control.
SS1E requires the externally initiated stop in order to be in conformance with stop Category 1 according to EN60204.
SS1: Safe Stop 1
SS1E: Safe Stop 1 external (Safe Stop 1 with external stop)
Note
The set time is rounded internally to an integer multiple of the monitoring clock cycle.
STOP F: Defect in a monitoring channel (error in the data cross-check)
STOP A: STO as a result of a fault detected by Safety Integrated
Note
STO: Safe Torque Off
Note
After replacement, when the drive powers up a fault is output.
Note
After replacement, when the drive powers up a fault is output.
Note
After replacement, when the drive powers up a fault is output.
NOTICE
It is not permissible that the safety commissioning mode is set in order to write to this parameter.
Note
After successful execution, this parameter is automatically reset to zero.
Parameters must be saved.
The parameter cannot be written to using a project download, and cannot be set in an offline project.
Note
For index [0]:
The display of the load-side position actual value on the first channel is updated in the monitoring clock cycle.
For index [1]:
The display of the load-side position actual value on the second channel is updated in the KDV clock cycle (r9724)
and delayed by one KDV clock cycle.
For index [2]:
The difference between the load-side position actual value in the first channel and load-side position actual value in
the second channel is updated in the KDV clock cycle (r9724) and delayed by one KDV clock cycle.
For index [3]:
The maximum difference between the load-side position actual value in the first channel and the load-side position
actual value in the second channel.
KDV: Data cross-check
Note
SBR: Safe Brake Ramp (safe brake ramp monitoring)
SDI: Safe Direction (safe motion direction)
SLS: Safely Limited Speed
SOS: Safe Operating Stop
Note
SSM: Safe Speed Monitor (safety-relevant feedback signal from the speed monitoring)
Note
The display is updated in the safety monitoring clock cycle.
Note
Regarding the units, this parameter should be interpreted as follows:
- linear axis: µm
- rotary axis: mdegrees
The value of this parameter is displayed in r9708 with units (mm or degrees).
The display is updated in the safety monitoring clock cycle.
For index [0]:
The display of the load-side position actual value on the first channel is updated in the monitoring clock cycle.
For index [1]:
The display of the load-side position actual value on the second channel is updated in the KDV clock cycle (r9724)
and delayed by one KDV clock cycle.
For index [2]:
The difference between the load-side position actual value in the first channel and load-side position actual value in
the second channel is updated in the KDV clock cycle (r9724) and delayed by one KDV clock cycle.
For index [3]:
The maximum difference between the load-side position actual value in the first channel and the load-side position
actual value in the second channel.
KDV: Data cross-check
Note
The display is updated in the safety monitoring clock cycle.
For linear axes, the following unit applies: millimeters per minute
For rotary axes, the following unit applies: revolutions per minute
Note
This parameter is only supplied with actual values in the case of Safety Integrated Extended Functions. For Safety
Integrated Basic Functions (SBC, SS1, STO), the value is equal to zero.
NOTICE
For bit 07:
The signal state behaves in an opposite way to the PROFIsafe Standard.
Note
This parameter is only supplied with actual values in the case of Safety Integrated Extended Functions. For Safety
Integrated Basic Functions (SBC, SS1, STO), the value is equal to zero.
For bit 07:
An internal event is displayed if a STOP A ... F is active.
Note
For bit 00:
A required dynamization is also displayed via alarm A01679.
For bit 01:
This bit can be used, to execute a drive-based or control-based ESR.
For bit 12:
An active test stop is also displayed using the safety message C01798.
ESR: Extended Stop and Retract
SAM: Safe Acceleration Monitor (safe acceleration monitoring)
SBR: Safe Brake Ramp (safe brake ramp monitoring)
Note
The significance of the individual message values is described in message C01711.
KDV: Data cross-check
For index [1, 2]:
When Safety message C01711 with message value >= 1000 occurs, these indices are not supplied with values.
Note
This parameter is not influenced by setting the axis type (p9502).
If the "SLS" or "SDI" function is not selected, r9733[0] shows p1082 and r9733[1] shows -p1082.
The display in r9733 can be delayed by up to one Safety monitoring clock cycle as compared to the display in r9719/
r9720 and r9721/r9722.
When selecting SOS or a STOP A ... D, setpoint 0 is specified in r9733.
Note
For bit 07:
An internal event is displayed if a STOP A ... F is active.
Note
For bit 00 = 1:
- a valid safety password was assigned.
For bit 01 = 1:
- a valid safety password was assigned (bit 0 = 1).
- safety parameters can be set.
Note
The PROFIsafe trailer at the end of the telegram is also displayed (2 words).
Note
The PROFIsafe trailer at the end of the telegram is also displayed (2 words).
Note
Example:
r9770[0] = 5, r9770[1] = 10, r9770[2] = 1, r9770[3] = 0 --> safety version V05.10.01.00
r9776 SI diagnostics
Data type: Unsigned32 P group: Safety Integrated
Description: Displays the operating state, referred to the safety functions.
Bit field: Bit Signal name 1 signal 0 signal FP
00 Safety parameter changed POWER ON required Yes No -
01 Safety functions enabled Yes No -
02 Safety component replaced and data save required Yes No -
03 Safety component replaced and acknowledge/save required Yes No -
Note
For bit 00 = 1:
At least one Safety parameter has been changed that will only take effect after a POWER ON.
For bit 01 = 1:
Safety functions (basic functions or extended functions) have been enabled and are active.
For bit 02 = 1:
A safety-relevant component has been replaced. Saving required (p0977 = 1).
For bit 03 = 1:
A safety-relevant component has been replaced. Acknowledging (p9702 = 29) and saving (p0977 = 1) required.
Note
The checksum changes when configuring safety functions.
Note
A complete list of numbers for cross-checked data items appears in fault F01611.
Note
SBT: Safe Brake Test
Note
The set time is rounded internally to an integer multiple of the monitoring clock cycle.
Note
The test torque effective for the brake test can be set for each sequence using a factor (p10210, p10220).
Note
The set time is rounded internally to an integer multiple of the monitoring clock cycle.
Description: Sets the test duration for sequence 2 for the safe brake test.
The test torque is available for this time at the closed brake.
Index: [0] = Brake 1
[1] = Reserved
Note
The set time is rounded internally to an integer multiple of the monitoring clock cycle.
Note
SS2E: Safe Stop 2 external (Safe Stop 2 with external stop, external STOP D)
For bits 05, 04:
For r10234.4 = 0 signal, it is possible to make a distinction as to whether the brake test was executed with error - or
has still not been executed - using bit 5.
Bit 5/4 = 0/0: The brake test has still not been executed since the last warm restart or POWER ON.
Bit 5/4 = 1/0: The last brake test that was executed had an error.
Note
The value remains displayed until the start of the next test sequence.
Note
The value remains displayed until the brake test is deselected.
Note
SCC: Safety Control Channel
Note
Parameter p60000 is an image of parameter p2000 in conformance with PROFIdrive.
A change always effects both parameters.
Detailed examples:
Acknowledge: IMMEDIATELY
Cause: An internal software error has occurred.
Fault value (r0949, interpret hexadecimal):
Only for internal Siemens troubleshooting.
Remedy: - carry out a POWER ON (switch-off/switch-on) for all components.
- upgrade firmware to later version.
- contact Technical Support.
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: The project download was interrupted.
Fault value (r0949, interpret decimal):
1: The user prematurely interrupted the project download.
2: The communication cable was interrupted (e.g. cable breakage, cable withdrawn).
3: The project download was prematurely terminated by the commissioning tool (e.g. STARTER, SCOUT).
100: Different versions between the firmware version and project files which were loaded by loading into the file system
"Download from memory card".
Note:
The response to an interrupted download is the state "first commissioning".
Remedy: - check the communication cable.
- download the project again.
- boot from previously saved files (switch-off/switch-on or p0976).
- when loading into the file system (download from memory card), use the matching version.
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: On the memory card, one file in the directory /SIEMENS/SINAMICS/DATA or /ADDON/SINAMICS/DATA has been illegally
changed with respect to that supplied from the factory. No changes are permitted in this directory.
Alarm value (r2124, interpret decimal):
zyx dec: x = Problem, y = Directory, z = File name
x = 1: File does not exist.
x = 2: Firmware version of the file does not match the software version.
x = 3: File checksum is incorrect.
y = 0: Directory /SIEMENS/SINAMICS/DATA/
y = 1: Directory /ADDON/SINAMICS/DATA/
z = 0: File MOTARM.ACX
z = 1: File MOTSRM.ACX
z = 2: File MOTSLM.ACX
z = 3: File ENCDATA.ACX
z = 4: File FILTDATA.ACX
z = 5: File BRKDATA.ACX
z = 6: File DAT_BEAR.ACX
z = 7: File CFG_BEAR.ACX
z = 8: File ENC_GEAR.ACX
z = 9: File CFG_BRK.ACX
z = 10: File THERMMOTMOD.ACX
z = 11: File MAPPING.ACX
z = 12: File LOADGEAR.ACX
z = 13: File MOTRSM.ACX
Remedy: For the file on the memory card involved, restore the status originally supplied from the factory.
Cause: The parameters of an individual drive object were saved (p0971 = 1), although there is still no backup of all drive system
parameters.
The saved object-specific parameters are not loaded the next time that the system powers up.
For the system to successfully power up, all of the parameters must have been completely backed up.
Alarm value (r2124, interpret decimal):
Only for internal Siemens troubleshooting.
Remedy: Save all parameters (p0977 = 1 or "copy RAM to ROM").
See also: p0977 (Save all parameters)
Reaction upon F: Servo: NONE (OFF1, OFF2, OFF3)
Acknowl. upon F: IMMEDIATELY
F01034 Units changeover: Calculation parameter values after reference value change unsuccessful
Message value: Parameter: %1
Drive object: All objects
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: The change of a reference parameter meant that for an involved parameter the selected value was not able to be re-
calculated in the per unit representation. The change was rejected and the original parameter value restored.
Fault value (r0949, parameter):
Parameter whose value was not able to be re-calculated.
See also: p0304, r0304, p0305, r0305, p2000, p2003
Remedy: - Select the value of the reference parameter such that the parameter involved can be calculated in the per unit
representation.
- Technology unit selection (p0595) before changing the reference parameter p0596, set p0595 = 1.
Cause: When the Control Unit is booted, no complete data set was found from the parameter back-up files. The last time that the
parameterization was saved, it was not completely carried out.
It is possible that the backup was interrupted by switching off or withdrawing the memory card.
Alarm value (r2124, interpret hexadecimal):
ddccbbaa hex:
aa = 01 hex:
Power up was realized without data backup. The drive is in the factory setting.
aa = 02 hex:
The last available backup data record was loaded. The parameterization must be checked. It is recommended that the
parameterization is downloaded again.
dd, cc, bb:
Only for internal Siemens troubleshooting.
See also: p0977
Remedy: - download the project again using the commissioning tool.
- save all parameters (p0977 = 1 or "copy RAM to ROM").
See also: p0977 (Save all parameters)
Reaction upon F: Servo: NONE (OFF1, OFF2, OFF3)
Acknowl. upon F: IMMEDIATELY
Cause: An error has occurred when downloading PSxxxyyy.ACX or PTxxxyyy.ACX files from the non-volatile memory.
Fault value (r0949, interpret hexadecimal):
Byte 1: yyy in the file name PSxxxyyy.ACX
yyy = 000 --> consistency back-up file
yyy = 001 ... 062 --> drive object number
yyy = 099 --> PROFIBUS parameter back-up file
Byte 2:
255: Incorrect drive object type.
254: Topology comparison unsuccessful -> drive object type was not able to be identified.
Reasons could be:
- incorrect component type in the actual topology
- Component does not exist in the actual topology.
- Component not active.
Additional values:
Only for internal Siemens troubleshooting.
Byte 4, 3:
Only for internal Siemens troubleshooting.
Remedy: - if you have saved the project data using the commissioning tool, download the project again. Save using the function
"Copy RAM to ROM" or with p0977 = 1. This means that the parameter files are again completely written to the non-volatile
memory.
- replace the memory card or Control Unit.
For byte 2 = 255:
- correct the drive object type (see p0107).
Reaction upon A: NONE
Acknowl. upon A: NONE
F01039 (A) ACX: Writing to the parameter back-up file was unsuccessful
Message value: %1
Drive object: All objects
Reaction: Servo: NONE (OFF1, OFF2, OFF3)
Acknowledge: IMMEDIATELY
Cause: Writing to at least one parameter back-up file PSxxxyyy.*** in the non-volatile memory was unsuccessful.
- in the directory /USER/SINAMICS/DATA/ at least one parameter back-up file PSxxxyyy.*** has the "read only" file attribute
and cannot be overwritten.
- there is not sufficient free memory space available.
- the non-volatile memory is defective and cannot be written to.
Fault value (r0949, interpret hexadecimal):
dcba hex
a = yyy in the file names PSxxxyyy.***
a = 000 --> consistency back-up file
a = 001 ... 062 --> drive object number
a = 070 --> FEPROM.BIN
a = 080 --> DEL4BOOT.TXT
a = 099 --> PROFIBUS parameter back-up file
b = xxx in the file names PSxxxyyy.***
b = 000 --> data save started with p0977 = 1 or p0971 = 1
b = 010 --> data save started with p0977 = 10
b = 011 --> data save started with p0977 = 11
b = 012 --> data save started with p0977 = 12
d, c:
Only for internal Siemens troubleshooting.
Remedy: - check the file attribute of the files (PSxxxyyy.***, CAxxxyyy.***, CCxxxyyy.***) and, if required, change from "read only"
to "writeable".
- check the free memory space in the non-volatile memory. Approx. 80 kbyte of free memory space is required for every
drive object in the system.
- replace the memory card or Control Unit.
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: An error was detected when downloading a project using the commissioning software (e.g. incorrect parameter value). It
is possible that the parameter limits are dependent on other parameters.
The detailed cause of the fault can be determined using the fault value.
Fault value (r0949, interpret hexadecimal):
ccbbaaaa hex
aaaa = Parameter
bb = Index
cc = fault cause
0: Parameter number illegal.
1: Parameter value cannot be changed.
2: Lower or upper value limit exceeded.
3: Sub-index incorrect.
4: No array, no sub-index.
5: Data type incorrect.
6: Setting not permitted (only resetting).
7: Descriptive element cannot be changed.
9: Descriptive data not available.
11: No master control.
15: No text array available.
17: Task cannot be executed due to operating state.
20: Illegal value.
21: Response too long.
22: Parameter address illegal.
23: Format illegal.
24: Number of values not consistent.
25: Drive object does not exist.
101: Presently deactivated.
104: Illegal value.
107: Write access not permitted when controller enabled.
108: Unit unknown.
109: Write access only in the commissioning state, encoder (p0010 = 4).
110: Write access only in the commissioning state, motor (p0010 = 3).
111: Write access only in the commissioning state, power unit (p0010 = 2).
112: Write access only in the quick commissioning mode (p0010 = 1).
113: Write access only in the ready mode (p0010 = 0).
114: Write access only in the commissioning state, parameter reset (p0010 = 30).
115: Write access only in the Safety Integrated commissioning state (p0010 = 95).
116: Write access only in the commissioning state, technological application/units (p0010 = 5).
117: Write access only in the commissioning state (p0010 not equal to 0).
118: Write access only in the commissioning state, download (p0010 = 29).
119: Parameter may not be written in download.
120: Write access only in the commissioning state, drive basic configuration (device: p0009 = 3).
121: Write access only in the commissioning state, define drive type (device: p0009 = 2).
122: Write access only in the commissioning state, data set basic configuration (device: p0009 = 4).
123: Write access only in the commissioning state, device configuration (device: p0009 = 1).
124: Write access only in the commissioning state, device download (device: p0009 = 29).
125: Write access only in the commissioning state, device parameter reset (device: p0009 = 30).
126: Write access only in the commissioning state, device ready (device: p0009 = 0).
127: Write access only in the commissioning state, device (device: p0009 not equal to 0).
129: Parameter may not be written in download.
130: Transfer of the master control is inhibited via binector input p0806.
131: Required BICO interconnection not possible because BICO output does not supply floating value
Cause: Parameterizing errors have been detected (e.g. incorrect parameter value). It is possible that the parameter limits are
dependent on other parameters.
The detailed cause of the fault can be determined using the fault value.
Fault value (r0949, interpret hexadecimal):
ccbbaaaa hex
aaaa = Parameter
bb = Index
cc = fault cause
0: Parameter number illegal.
1: Parameter value cannot be changed.
2: Lower or upper value limit exceeded.
3: Sub-index incorrect.
4: No array, no sub-index.
5: Data type incorrect.
6: Setting not permitted (only resetting).
7: Descriptive element cannot be changed.
9: Descriptive data not available.
11: No master control.
15: No text array available.
17: Task cannot be executed due to operating state.
20: Illegal value.
21: Response too long.
22: Parameter address illegal.
23: Format illegal.
24: Number of values not consistent.
25: Drive object does not exist.
101: Presently deactivated.
104: Illegal value.
107: Write access not permitted when controller enabled.
108: Unit unknown.
109: Write access only in the commissioning state, encoder (p0010 = 4).
110: Write access only in the commissioning state, motor (p0010 = 3).
111: Write access only in the commissioning state, power unit (p0010 = 2).
112: Write access only in the quick commissioning mode (p0010 = 1).
113: Write access only in the ready mode (p0010 = 0).
114: Write access only in the commissioning state, parameter reset (p0010 = 30).
115: Write access only in the Safety Integrated commissioning state (p0010 = 95).
116: Write access only in the commissioning state, technological application/units (p0010 = 5).
117: Write access only in the commissioning state (p0010 not equal to 0).
118: Write access only in the commissioning state, download (p0010 = 29).
119: Parameter may not be written in download.
120: Write access only in the commissioning state, drive basic configuration (device: p0009 = 3).
121: Write access only in the commissioning state, define drive type (device: p0009 = 2).
122: Write access only in the commissioning state, data set basic configuration (device: p0009 = 4).
123: Write access only in the commissioning state, device configuration (device: p0009 = 1).
124: Write access only in the commissioning state, device download (device: p0009 = 29).
125: Write access only in the commissioning state, device parameter reset (device: p0009 = 30).
126: Write access only in the commissioning state, device ready (device: p0009 = 0).
127: Write access only in the commissioning state, device (device: p0009 not equal to 0).
129: Parameter may not be written in download.
130: Transfer of the master control is inhibited via binector input p0806.
131: Required BICO interconnection not possible because BICO output does not supply floating value
Cause: When changing a sampling time (p0115[0], p0799 or p4099), inconsistency between the clock cycles has been identified.
Alarm value (r2124, interpret decimal):
1: Value lower than minimum value.
2: Value higher than maximum value.
3: Value not a multiple of 1.25 µs.
4: Value does not match isochronous PROFIBUS operation.
5: Value not a multiple of 125 µs.
6: Value not a multiple of 250 µs.
7: Value not a multiple of 375 µs.
8: Value not a multiple of 400 µs.
10: Special restriction of the drive object violated.
20: On a SERVO with a sampling time of 62.5 µs, more than two drive objects or one drive object of a type other than
SERVO have been detected on the same DRIVE-CLiQ line (a maximum of two SERVO type drive objects are permitted).
21: Value can be a multiple of the current controller sampling time of a servo or vector drive in the system (e.g. for TB30,
the values of all of the indices should be taken into account).
30: Value less than 31.25 µs.
31: Value less than 62.5 µs (31.25 µs is not supported for SMC10, SMC30, SMI10 and Double Motor Modules).
32: Value less than 125 µs.
33: Value less than 250 µs.
40: Nodes have been identified on the DRIVE-CLiQ line whose highest common denominator of the sampling times is less
than 125 µs. Further, none of the nodes has a sampling time of less than 125 µs.
41: A chassis unit was identified on the DRIVE-CLiQ line as a node. Further, the highest common denominator of the
sampling times of all of the nodes connected to the line is less than 250 µs.
42: An Active Line Module was identified on the DRIVE-CLiQ line as a node. Further, the highest common denominator
of the sampling times of all of the nodes connected to the line is less than 125 µs.
43: A Voltage Sensing Module (VSM) was identified on the DRIVE-CLiQ line as a node. Further, the highest common
denominator of the sampling times of all of the nodes connected to the line is not equal to the current controller sampling
time of the drive object of the VSM.
44: The highest common denominator of the sampling times of all of the components connected to the DRIVE-CLiQ line
is not the same for all components of this drive object (e.g. there are components on different DRIVE-CLiQ lines on which
different highest common denominators are generated).
45: A chassis parallel unit was identified on the DRIVE-CLiQ line as a node. Further, the highest common denominator of
the sampling times of all of the nodes connected to the line is less than 162.5 µs or 187.5 µs (for a 2x or 3x parallel
connection).
46: A node has been identified on the DRIVE-CLiQ line whose sampling time is not a multiple of the lowest sampling time
on this line.
52: Nodes have been identified on the DRIVE-CLiQ line whose highest common denominator of the sampling times is less
than 31.25 µs.
54: Nodes have been identified on the DRIVE-CLiQ line whose highest common denominator of the sampling times is less
than 62.5 µs.
56: Nodes have been identified on the DRIVE-CLiQ line whose highest common denominator of the sampling times is less
than 125 µs.
58: Nodes have been identified on the DRIVE-CLiQ line whose highest common denominator of the sampling times is less
than 250 µs.
99: Inconsistency of cross drive objects detected.
116: Recommended clock cycle in r0116[0...1].
General note:
The topology rules should be noted when connecting up DRIVE-CLiQ (refer to the appropriate product documentation).
The parameters of the sampling times can also be changed with automatic calculations.
Example for highest common denominator: 125 s, 125 µs, 62.5 µs --> 62.5 µs
Remedy: - check the DRIVE-CLiQ cables.
- set a valid sampling time.
Cause: Error when reading the read-only data of the EEPROM in the Option Board.
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
Remedy: - carry out a POWER ON (switch-off/switch-on).
- replace the Control Unit.
Cause: A function requested by the Control Unit is not supported by a DRIVE-CLiQ component.
Fault value (r0949, interpret decimal):
1: The component does not support the deactivation.
101: The Motor Module does not support an internal armature short-circuit.
102: The Motor Module does not support the deactivation.
201: The Sensor Module does not support actual value inversion (p0410.0 = 1) when using a Hall sensor (p0404.6 = 1)
for the commutation.
202: The Sensor Module does not support parking/unparking.
203: The Sensor Module does not support the deactivation.
204: The firmware of this Terminal Module 15 (TM15) does not support the application TM15DI/DO.
205: The Sensor Module does not support the selected temperature evaluation (r0458, r0459).
206: The firmware of this Terminal Modules TM41/TM31/TM15 refers to an old firmware version. It is urgently necessary
to upgrade the firmware to ensure disturbance-free operation.
207: The power unit with this hardware version does not support operation with device supply voltages of less than 380
V.
208: The Sensor Module does not support de-selection of commutation with zero mark (via p0430.23).
211: The Sensor Module does not support single-track encoders (r0459.10).
212: The Sensor Module does not support LVDT sensors (p4677.0).
213: The Sensor Module does not support the characteristic type (p4662).
214: The power unit does not support the temperature evaluation via PT1000 (r0193).
215: The Terminal Module does not support the temperature evaluation via PT1000
216: The Voltage Sensing Module (VSM) does not support operation with a PT1000 temperature sensor.
Remedy: Upgrade the firmware of the DRIVE-CLiQ component involved.
For fault value = 205, 214, 215:
- check parameter p0600 and p0601 and if required, adapt.
For fault value = 207:
- replace the power unit or if required set the device supply voltage higher (p0210).
For fault value = 208:
- check parameter p0430.23 and reset if necessary.
For fault value = 216:
- check the setting of the sensor type (p3665).
- use a Voltage Sensing module that supports operation with PT1000 (MLFB ...-xxx1).
Cause: The component number from the topology was not parameterized (p0121 (for power unit, refer to p0107), p0131 (for servo/
vector drives, refer to p0107), p0141, p0151, p0161).
Fault value (r0949, interpret decimal):
Data set number.
Note:
The fault also occurs if encoders have been configured (p0187 to p0189) but no component numbers exist for them.
In this case, the fault value includes the drive data set number plus 100 * encoder number (e.g. 3xx, if a component number
was not entered in p0141 for encoder 3 (p0189)).
Remedy: - enter missing component number.
- if required, remove the component and restart commissioning.
Acknowledge: NONE
Cause: p0978 contains a drive object number that does not exist.
Alarm value (r2124, interpret decimal):
Index of p0978 under which the drive object number can be determined.
Remedy: Set p0009 to 1 and change p0978:
Rules:
- p0978 must include all of the drive object numbers (p0101).
- it is not permissible for a drive object number to be repeated.
- by entering a 0, the drive objects with PZD are separated from those without PZD.
- only 2 partial lists are permitted. After the second 0, all values must be 0.
- dummy drive object numbers (255) are only permitted in the first partial list.
Cause: In p0978, dummy drive object numbers (255) are only permitted in the first partial list.
Alarm value (r2124, interpret decimal):
Index of p0978 under which the illegal value is located.
Remedy: Set p0009 to 1 and change p0978:
Rules:
- p0978 must include all of the drive object numbers (p0101).
- it is not permissible for a drive object number to be repeated.
- by entering a 0, the drive objects with PZD are separated from those without PZD.
- only 2 partial lists are permitted. After the second 0, all values must be 0.
- dummy drive object numbers (255) are only permitted in the first partial list.
Cause: The device target topology (p0099) does not correspond to the device actual topology (r0098).
The fault only occurs if the topology was commissioned using the automatic internal device mechanism and not using the
commissioning tool.
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
Remedy: One of the following counter-measures can be selected if no faults have occurred in the topology detection itself:
If commissioning is still not completed:
- carry out a self-commissioning routine (starting from p0009 = 1).
In general:
Set p0099 = r0098, set p0009 = 0; for existing Motor Modules, this results in servo drives being automatically generated
(p0107).
Generating servo drives: Set p0097 to 1, set p0009 to 0.
Generating vector drives: Set p0097 to 2, set p0009 to 0.
Generating vector drives with parallel circuit: Set p0097 to 12, set p0009 to 0.
In order to set configurations in p0108, before setting p0009 to 0, it is possible to first set p0009 to 2 and modify p0108.
The index corresponds to the drive object (p0107).
If commissioning has already been completed:
- re-establish the original connections and re-connect power to the Control Unit.
- restore the factory setting for the complete equipment (all of the drives) and allow automatic self-commissioning again.
- change the device parameterization to match the connections (this is only possible using the commissioning tool).
Notice:
Topology changes that result in this fault being generated cannot be accepted by the automatic function in the device, but
must be transferred using the commissioning tool and parameter download. The automatic function in the device only
allows constant topology to be used. Otherwise, when the topology is changed, all of the previous parameter settings are
lost and replaced by the factory setting.
Cause: In the actual topology, 2 Control Units are connected with one another through DRIVE-CLiQ.
As standard, this is not permitted.
It is only permitted if the Technology Extension OALINK has already been installed and activated on both Control Units.
Fault value (r0949, interpret hexadecimal):
yyxx hex:
yy = connection number of the Control Unit at which the second Control Unit is connected
xx = component number of the Control Unit at which the second Control Unit is connected
Note:
Pulse enable is withdrawn and prevented.
Remedy: In general:
- remove the connection to the second Control Unit and restart.
- for the S120M component DRIVE-CLiQ extension, interchange the hybrid cable (IN/OUT).
When using OALINK:
- remove the DRIVE-CLiQ connection and restart the systems.
- install OALINK on both Control Units and activate.
- check the configuration of the DRIVE-CLiQ ports in OALINK.
Cause: The detected actual topology contains SINUMERIK and SIMOTION components.
The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.
Alarm value (r2124, interpret hexadecimal):
ddccbbaa hex: cc = fault cause, bb = component class of the actual topology, aa = component number of the component
cc = 01 hex = 1 dec:
An NX10 or NX15 was connected to a SIMOTION control.
cc = 02 hex = 2 dec:
A CX32 was connected to a SINUMERIK control.
Remedy: For alarm value = 1:
Replace all NX10 or NX15 by a CX32.
For alarm value = 2:
Replace all CX32 by an NX10 or NX15.
Cause: When checking the actual topology, a ring-type connection was detected.
The fault value describes a component contained in the ring.
Fault value (r0949, interpret hexadecimal):
ccbbaaaa hex:
cc = connection number (%3)
bb = component class (% 2)
aaaa = preliminary component number (%1)
Component class:
0: Component unknown.
1: Control Unit
2: Motor Module
3: Line Module
4: Sensor Module
5: Voltage Sensing Module
6: Terminal Module
7: DRIVE-CLiQ Hub Module
8: Controller Extension
9: Filter Module
10: Hydraulic Module.
49: DRIVE-CLiQ component
50: Option slot
60: Encoder
70: DRIVE-CLiQ motor
71: Hydraulic cylinder
72: Hydraulic valve
80: Motor
Connection number:
0: Port 0, 1: Port 1, 2: Port 2, 3: Port 3, 4: Port 4, 5: Port 5
10: X100, 11: X101, 12: X102, 13: X103, 14: X104, 15: X105
20: X200, 21: X201, 22: X202, 23: X203
50: X500, 51: X501, 52: X502, 53: X503, 54: X504, 55: X505
Remedy: Output the fault value and remove the specified connection.
Note:
Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.
setpoint/actual value comparison).
Reaction: NONE
Acknowledge: NONE
Cause: The topology comparison has detected a Motor Module in the actual topology that has been incorrectly inserted with respect
to the target technology.
Alarm value (r2124, interpret hexadecimal):
ddccbbaa hex:
dd = connection number (%4)
cc = component number (%3)
bb = component class (% 2)
aa = component number of the incorrectly inserted component (% 1)
Note:
The component is described in dd, cc and bb, where the component involved is incorrectly inserted.
Component class and connection number are described in F01375.
The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.
Remedy: Adapting topologies:
- insert the components involved at the right connection (correct the actual topology).
- adapt the project/parameterizing in the commissioning tool (correct the target topology).
- automatically remove the topology error (p9904).
Note:
Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.
setpoint/actual value comparison).
Acknowledge: NONE
Cause: The topology comparison has detected a Terminal Module in the actual topology that has been incorrectly inserted with
respect to the target technology.
Alarm value (r2124, interpret hexadecimal):
ddccbbaa hex:
dd = connection number (%4)
cc = component number (%3)
bb = component class (% 2)
aa = component number of the incorrectly inserted component (% 1)
Note:
The component is described in dd, cc and bb, where the component involved is incorrectly inserted.
Component class and connection number are described in F01375.
The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.
Remedy: Adapting topologies:
- insert the components involved at the right connection (correct the actual topology).
- adapt the project/parameterizing in the commissioning tool (correct the target topology).
- automatically remove the topology error (p9904).
Note:
Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.
setpoint/actual value comparison).
Cause: The topology comparison has detected a controller extension 32 (CX32) in the actual topology that has been incorrectly
inserted with respect to the target topology.
Alarm value (r2124, interpret hexadecimal):
ddccbbaa hex:
dd = connection number (%4)
cc = component number (%3)
bb = component class (% 2)
aa = component number of the incorrectly inserted component (% 1)
Note:
The component is described in dd, cc and bb, where the component involved is incorrectly inserted.
Component class and connection number are described in F01375.
The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.
Remedy: Adapting topologies:
- insert the components involved at the right connection (correct the actual topology).
- adapt the project/parameterizing in the commissioning tool (correct the target topology).
- automatically remove the topology error (p9904).
Note:
Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.
setpoint/actual value comparison).
Cause: The topology comparison has detected a motor with DRIVE-CLiQ in the actual topology that has been incorrectly inserted
with respect to the target topology.
Alarm value (r2124, interpret hexadecimal):
ddccbbaa hex:
dd = connection number (%4)
cc = component number (%3)
bb = component class (% 2)
aa = component number of the incorrectly inserted component (% 1)
Note:
The component is described in dd, cc and bb, where the component involved is incorrectly inserted.
Component class and connection number are described in F01375.
The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.
Remedy: Adapting topologies:
- insert the components involved at the right connection (correct the actual topology).
- adapt the project/parameterizing in the commissioning tool (correct the target topology).
- automatically remove the topology error (p9904).
Note:
Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.
setpoint/actual value comparison).
Cause: The topology comparison has detected differences in the actual topology and target topologies in the electronic rating plate.
Alarm value (r2124, interpret hexadecimal):
ddccbbaa hex: aa = component number (%1), bb = component class of the target topology (%2), cc = component class
of the actual topology (%3), dd = difference (%4)
dd = 01 hex = 1 dec:
Different component type.
dd = 02 hex = 2 dec:
Different article number.
dd = 03 hex = 3 dec:
Different manufacturer.
dd = 04 hex = 4 dec:
For a multi-component slave, the incorrect subcomponent (index) is connected (e.g. Double Motor Module X201 instead
of X200) - or only a part of a multi-component slave is set to "deactivate and not available".
dd = 05 hex = 5 dec:
NX10 or NX15 used instead of CX32.
dd = 06 hex = 6 dec:
NX10 or NX15 used instead of CX32.
dd = 07 hex = 7 dec:
Different number of connections.
Note:
The component class is described in F01375.
The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.
Remedy: Adapting topologies:
- connect the expected component (correct the actual topology).
- adapt the project/parameterizing in the commissioning tool (correct the target topology).
Topology comparison - if required, adapt the comparison level:
- parameterize the topology comparison of all components (p9906).
- parameterize the topology comparison of one components (p9907, p9908).
Note:
Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.
setpoint/actual value comparison).
Cause: The topology comparison has detected a DRIVE-CLiQ Hub Module missing in the actual topology with respect to the target
topology.
Alarm value (r2124, interpret hexadecimal):
ddccbbaa hex:
dd = connection number (%4)
cc = component number (%3)
bb = component class (% 2)
aa = component number of the component that has not been inserted (% 1)
Note:
The component is described in dd, cc and bb, where the component has not been inserted.
Component class and connection number are described in F01375.
Remedy: Adapting topologies:
- insert the components involved at the right connection (correct the actual topology).
- adapt the project/parameterizing in the commissioning tool (correct the target topology).
Check the hardware:
- check the 24 V supply voltage.
- check DRIVE-CLiQ cables for interruption and contact problems.
- check that the component is working properly.
Note:
Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.
setpoint/actual value comparison).
Reaction: NONE
Acknowledge: NONE
Cause: The topology comparison has detected a DRIVE-CLiQ component missing in the actual topology with respect to the target
topology.
Alarm value (r2124, interpret hexadecimal):
ddccbbaa hex:
dd = connection number (%4)
cc = component number (%3)
bb = component class (% 2)
aa = component number of the component that has not been inserted (% 1)
Note:
The component is described in dd, cc and bb, where the component has not been inserted.
Component class and connection number are described in F01375.
Remedy: Adapting topologies:
- insert the components involved at the right connection (correct the actual topology).
- adapt the project/parameterizing in the commissioning tool (correct the target topology).
Check the hardware:
- check the 24 V supply voltage.
- check DRIVE-CLiQ cables for interruption and contact problems.
- check that the component is working properly.
Note:
Under "Topology --> Topology view" the commissioning tool where relevant offers improved diagnostics capability (e.g.
setpoint/actual value comparison).
Reaction: NONE
Acknowledge: NONE
Cause: The maximum number of BICO interconnections (signal sinks) when deactivating a drive object was exceeded.
When deactivating a drive object, all BICO interconnections (signal sinks) are listed in the following parameters:
- r9498[0...29]: List of the BI/CI parameters involved.
- r9499[0...29]: List of the associated BO/CO parameters.
Remedy: Not necessary.
This alarm is automatically withdrawn as soon as no BICO interconnection is entered in r9498[29] and r9499[29] (value =
0).
Notice:
When re-activating the drive object, all BICO interconnections should be checked and if required, re-established.
F01515 (A) BICO: Writing to parameter not permitted as the master control is active
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: When changing the number of CDS or when copying from CDS, the master control is active.
Remedy: If required, return the master control and repeat the operation.
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: The drive-integrated "Safety Integrated" function on monitoring channel 1 has detected a fault in the crosswise data
comparison between the two monitoring channels and has initiated a STOP F.
As a result of this fault, after the parameterized transition has expired (p9658), fault F01600 (SI CU: STOP A initiated) is
output.
Fault value (r0949, interpret decimal):
0: Stop request from the other monitoring channel.
1 ... 999:
Number of the cross-compared data that resulted in this fault. This number is also displayed in r9795.
2: SI enable safety functions (p9601). Crosswise data comparison is only carried out for the supported bits.
3: SI SGE changeover discrepancy time (p9650).
4: SI transition time STOP F to STOP A (p9658).
5: SI enable Safe Brake Control (p9602).
6: SI Motion enable safety functions (p9501).
7: SI delay time of STO for Safe Stop 1 (p9652).
8: SI PROFIsafe address (p9610).
9: SI debounce time for STO/SBC/SS1 (p9651).
14: SI PROFIsafe telegram selection (p9611).
15: SI PROFIsafe bus failure response (p9612).
1000: Watchdog timer has expired.
Within the time of approx. 5 x p9650, alternatively, the following was defined:
- the signal at F-DI for STO/SS1 continually changes with time intervals less than or equal to the discrepancy time (p9650).
- via PROFIsafe, STO (also as subsequent response) was continually selected and deselected with time intervals less
than or equal to the discrepancy time (p9650).
1001, 1002: Initialization error, change timer / check timer.
1900: CRC error in the SAFETY sector.
1901: CRC error in the ITCM sector.
1902: Overloading in the ITCM sector has occurred in operation.
1903: Internal parameterizing error for CRC calculation.
2000: Status of the STO selection for both monitoring channels different.
2001: Feedback signal of STO shutdown for both monitoring channels different.
2002: Status of the delay timer SS1 on both monitoring channels are different (status of the timer in p9650).
2003: Status of the STO terminal for both monitoring channels different.
6000 ... 6999:
Error in the PROFIsafe control.
For these fault values, the fail-safe control signals (fail-safe values) are transferred to the safety functions. If "STOP B after
failure of the PROFIsafe communication" (p9612) is parameterized, the transfer of the fail-safe value is delayed.
6000: A fatal PROFIsafe communication error has occurred.
6064 ... 6071: error when evaluating the F parameter. The values of the transferred F parameters do not match the expected
values in the PROFIsafe driver.
6064: Destination address and PROFIsafe address are different (F_Dest_Add).
6065: Destination address not valid (F_Dest_Add).
6066: Source address not valid (F_Source_Add).
6067: Watchdog time not valid (F_WD_Time).
6068: Incorrect SIL level (F_SIL).
6069: Incorrect F-CRC length (F_CRC_Length).
6070: Incorrect F parameter version (F_Par_Version).
6071: CRC error for the F parameters (CRC1). The transferred CRC value of the F parameters does not match the value
calculated in the PROFIsafe driver.
6072: F parameterization is inconsistent.
6165: A communications error was identified when receiving the PROFIsafe telegram. The fault can also occur if an
inconsistent or out-of-date PROFIsafe telegram has been received after switching the drive off and on or after plugging in
the PROFINET cable.
6166: A time monitoring error (timeout) was identified when receiving the PROFIsafe telegram.
- check the settings of the values of the F parameters and the F parameter CRC (CRC1) calculated from these at the
PROFIsafe slave and, if required, update.
For fault value = 6072:
- check the settings of the values for the F parameters and, if required, correct.
The following combinations are permissible for F parameters F_CRC_Length and F_Par_Version:
F_CRC_Length = 2-byte CRC and F_Par_Version = 0
F_CRC_Length = 3-byte CRC and F_Par_Version = 1
For fault value = 6165:
- if the fault occurs after powering up or after inserting the PROFINET cable, acknowledge the fault.
- check the configuration and communication at the PROFIsafe slave.
- check the setting of the value for F parameter F_WD_Time on the PROFIsafe slave and increase if necessary.
- check whether there is a DRIVE-CLiQ communication error between the two monitoring channels and, if required, carry
out a diagnostics routine for the faults identified.
- check whether all F parameters of the drive match the F parameters of the F host.
For fault value = 6166:
- check the configuration and communication at the PROFIsafe slave.
- check the setting of the value for F parameter F_WD_Time on the PROFIsafe slave and increase if necessary.
- evaluate diagnostic information in the F host.
- check PROFIsafe connection.
- check whether all F parameters of the drive match the F parameters of the F host.
Note:
CU: Control Unit
F-DI: Fail-safe Digital Input
SGE: Safety-relevant input
SI: Safety Integrated
SS1: Safe Stop 1 (corresponds to Stop Category 1 acc. to EN60204)
STO: Safe Torque Off
Reaction upon A: NONE
Acknowl. upon A: NONE
F01612 SI P1 (CU): STO inputs for power units connected in parallel different
Message value: Fault cause: %1 bin
Drive object: All objects
Reaction: NONE (OFF1, OFF2, OFF3)
Acknowledge: IMMEDIATELY (POWER ON)
Cause: The drive-integrated "Safety Integrated" function on the Control Unit (CU) has identified different states of the AND'ed STO
inputs for power units connected in parallel and has initiated a STOP F.
As a result of this fault, after the parameterized transition has expired (p9658), fault F01600 (SI CU: STOP A initiated) is
output.
Fault value (r0949, interpret binary):
Binary image of the digital inputs of the Control Unit that are used as signal source for the function "Safe Torque Off".
Remedy: - check the tolerance time SGE changeover and if required, increase the value (p9650).
- check the wiring of the safety-relevant inputs (SGE) (contact problems).
Note:
CU: Control Unit
SGE: Safety-relevant input
SI: Safety Integrated
STO: Safe Torque Off / SH: Safe standstill
Reaction: NONE
Acknowledge: NONE
Cause: The "Safe Torque Off" (STO) function of the basic functions has been selected in monitoring channel 1 using the input
terminal and is active.
Note:
- this message does not result in a safety stop response.
- this message is not output when STO is selected using the Extended Functions.
Remedy: Not necessary.
Note:
SI: Safety Integrated
STO: Safe Torque Off
Reaction upon F: OFF2
Acknowl. upon F: IMMEDIATELY (POWER ON)
Reaction upon A: NONE
Acknowl. upon A: NONE
Reaction: NONE
Acknowledge: NONE
Cause: A configuration of motor holding brake and SBC was detected that is not practical.
The following configurations can result in this message:
- "No motor holding brake available" (p1215 = 0) and "SBC" enabled (p9602 = 1).
Note:
SBC: Safe Brake Control
Remedy: Check the parameterization of the motor holding brake and SBC and correct.
See also: p1215, p9602
Reaction upon F: NONE (OFF1, OFF2, OFF3)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: "Safety Integrated" has identified that a component has been replaced.
It is no longer possible to operate the particular drive without fault.
When safety functions are active, after a component has been replaced it is necessary to carry out a partial acceptance
test.
Fault value (r0949, interpret binary):
Bit 0 = 1:
It has been identified that the drive has been replaced.
Bit 3 = 1:
It has been identified that the Sensor Module has been replaced.
Bit 5 = 1:
It has been identified that the sensor has been replaced.
Remedy: - acknowledge component replacement or "Copy RAM to ROM".
- save all parameters
- acknowledge fault.
Note:
In addition to the fault, diagnostics bits r9776.2 and r9776.3 are set.
See also: r9776 (SI diagnostics)
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: An internal error in the Safety Integrated software in monitoring channel 1 has occurred.
Note:
This fault results in a STOP A that cannot be acknowledged.
Fault value (r0949, interpret hexadecimal):
Only for internal Siemens troubleshooting.
Remedy: - carry out a POWER ON (switch-off/switch-on) for all components.
- re-commission the "Safety Integrated" function and carry out a POWER ON.
- upgrade the drive firmware to a later version.
- contact Technical Support.
- replace drive.
Note:
SI: Safety Integrated
Cause: One of the Safety Integrated monitoring clock cycles is not permissible.
- the monitoring clock cycle integrated in the drive cannot be maintained due to the communication conditions required in
the system.
- the monitoring clock cycle for safe motion monitoring functions is not permissible (p9500).
- the actual value sensing clock cycle for safe motion monitoring functions is not permissible (p9511).
- the sampling time for the current controller (p0112, p0115[0]) cannot be supported.
Note:
This fault results in a STOP A that cannot be acknowledged.
Fault value (r0949, interpret decimal):
For motion monitoring functions that are not enabled (p9601.2 = p9801.2 = 0, p9501 = 0), the following applies:
- Minimum setting for the monitoring clock cycle (in µs).
For motion monitoring functions that are enabled (p9601.2 = p9801.2 = 1 and/or p9501 > 0), the following applies:
100:
- no matching monitoring clock cycle was able to be found.
- an illegal actual value sensing clock cycle was set for S120M (p9511).
101:
- the monitoring clock cycle is not an integer multiple of the actual value sensing clock cycle.
- SINAMICS S120M: the monitoring clock cycle (p9500) is not an integer multiple of 2 ms.
102:
- An error has occurred when transferring the actual value sensing clock cycle to the Motor Module.
103:
- An error has occurred when transferring the actual value sensing clock cycle to the Sensor Module.
104, 105:
- four times the current controller sampling time (p0115[0]) is greater than 1 ms when operating with a non-isochronous
PROFIBUS.
- four times the current controller sampling time (p0115[0]) is greater than the DP clock cycle when operating with an
isochronous PROFIBUS.
- the DP clock cycle is not an integer multiple of the sampling time of the current controller (p0115[0]).
106:
- the monitoring clock cycle does not match the monitoring clock cycle of the TM54F.
107:
- the actual value sensing clock cycle (p9511) is less than four times the current controller sampling time (p0115[0]).
- the actual value sensing clock cycle (p9511) is not an integer multiple of the sampling time of the current controller
(p0115[0]).
108:
- the parameterized actual value sensing clock cycle cannot be set on this component
109:
- if the motion monitoring functions have been parameterized as encoderless (p9506), the actual value sensing clock cycle
(p9511) and the current controller clock cycle (p0115[0]) must be identical.
- SINAMICS S110: if the motion monitoring functions have been parameterized as encoderless (p9506), the actual value
sensing clock cycle p9511 must be = 250 µs.
110:
- the actual value sensing clock cycle (p9511) for safety with encoder (p9506 = 0) is less than 2 ms for this Control Unit
(e.g. CU305).
111:
- the monitoring clock cycle is not an integer multiple of the sampling time of the current controller (p0115[0]).
112:
- An actual value sensing clock cycle p9511 = 0 on a drive object of a Double Motor Module is not permissible in the existing
configuration.
200, 201:
- S120M: the monitoring clock cycle cannot be maintained as a result of the conditions required in the system.
202:
- the current controller sampling time is set to zero (p0115[0]).
Remedy: For enabled SI monitoring integrated in the drive (p9601/p9801 > 0):
- upgrade the firmware of the Control Unit to a later version.
For enabled motion monitoring function (p9501 > 0):
- correct the monitoring clock cycle (p9500) and carry out POWER ON.
For fault value = 100:
- for S120M, set the actual value sensing clock cycle to p9511 = 0.
For fault value = 101:
- actual value sensing clock cycle corresponds to position control clock cycle/DP clock cycle (factory setting).
- for motion monitoring functions integrated in the drive (p9601/p9801bit 2 = 1) the actual value sensing clock cycle can
be directly parameterized in p9511/p9311.
- SINAMICS S120M: set the monitoring clock cycle (p9500) to an integer multiple of 2 ms.
For fault value = 104, 105:
- set a separate actual value sensing clock cycle in p9511.
- restrict operation to a maximum of two vector drives. For the standard setting in p0112, p0115, the current controller
sampling time is automatically reduced to 250 µs. If the standard values were changed, then the current controller sampling
time (p0112, p0115) should be appropriately set.
- increase the DP clock cycle for operation with an isochronous PROFIBUS so that there is a multiple clock cycle ratio of
at least 4:1 between the DP clock cycle and the current controller sampling time. A clock cycle ratio of at least 8:1 is
recommended.
- With firmware version 2.5, please ensure that parameter p9510 is set to 1 in the drive (clock cycle synchronous operation).
For fault value = 106:
- set the parameters for the monitoring clock cycles the same (p10000 and p9500 / p9300).
For fault value = 107:
- set an actual value sensing clock cycle that matches the current controller clock cycle (p9511 >= 4 * p0115[0], 8 * p0115[0])
is recommended.
Note:
An actual value sensing clock cycle (p9511) that is set too low, can sporadically mean that safety messages C01711/
C30711 are output with message value 1020 or 1021.
For fault value = 108:
- set a suitable actual value sensing clock cycle in p9511.
- if the DP clock cycle is used as the actual value sensing clock cycle for operation with isochronous PROFIBUS (p9511
= 0), then a suitable DP clock cycle must be configured. This must be set to less than 8 ms. If this is not possible, then
p9511 must be set to the required actual value sensing clock cycle (< 8 ms).
- For SIMOTION D410-2, a suitable multiple of the DP clock cycle (e.g. 1, 2, 3, 4, 5, 6, 8, 10) must be parameterized.
Otherwise, the clock cycle must be set to less than 8 ms.
For fault value = 109:
- set the actual value sensing clock cycle in p9511 to the same value as the current controller clock cycle (p0115[0]).
- SINAMICS S110: set the actual value sensing clock cycle to p9511 = 250 µs.
For fault value = 110:
- set the actual value sensing clock cycle in p9511 to 2 ms or higher.
For fault value = 111:
- set the monitoring clock cycle in p9500 as an integer multiple of the sampling time of the current controller (p0115[0]).
For fault value = 112:
- set the actual value sensing clock cycle p9511 to the required value (not equal to zero).
For fault value = 200, 201:
- increase the current controller sampling time (p0115[0]).
- if required, reduce the number of components connected to the corresponding DRIVE-CLiQ line, or distribute the
components across several DRIVE-CLiQ sockets.
For fault value = 202:
- set the current controller sampling time to a sensible value (p0115[0]).
Note:
CU: Control Unit
MM: Motor Module
SI: Safety Integrated
Cause: The write request for one or several Safety Integrated parameters from monitoring channel 1 was rejected.
Note:
This fault does not result in a safety stop response.
Fault value (r0949, interpret decimal):
1: The Safety Integrated password is not set.
14: An attempt was made to enable the PROFIsafe communication - although the version of the PROFIsafe driver used
on both monitoring channels is different.
20: An attempt was made to enable the motion monitoring functions integrated in the drive and the STO function, both
controlled via F-DI.
23: For ESR, an attempt was made to enable the delay of STO, although this cannot be supported.
25: An attempt was made to parameterize a PROFIsafe telegram although this cannot be supported.
27: An attempt was made to activate the Basic Functions by controlling via TM54F although this is not supported.
28: An attempt was made to enable the "STO via terminals at the Power Module" function although this cannot be supported.
9612: An attempt was made to parameterize STOP B as stop response for PROFIsafe failure, although PROFIsafe is not
enabled.
Remedy: For fault value = 1:
- set the Safety Integrated password.
For fault value = 14, 23, 27:
- check whether there are faults in the safety function alignment between the two monitoring channels (F01655, F30655)
and if required, carry out diagnostics for the faults involved.
- upgrade the drive software.
For fault value = 20:
- correct the enable setting (p9601).
For fault value = 25:
- correct the telegram number setting (p9611).
For fault value = 28:
- correct the enable setting (p9601.7 = 0).
For fault value = 9612:
- establish communications with PROFIsafe (p9601).
- parameterize STOP A as the stop response for PROFIsafe failure (p9612 = 0).
Note:
CU: Control Unit
F-DI: Fail-safe Digital Input
SBC: Safe Brake Control
SI: Safety Integrated
SS1: Safe Stop 1 (corresponds to Stop Category 1 acc. to EN60204)
STO: Safe Torque Off
See also: p9501, p9601, p9612
Remedy: - use a Motor Module/Hydraulic Module that supports the safety-related functions.
- upgrade the Motor Module/Hydraulic Module software.
Note:
CU: Control Unit
SI: Safety Integrated
Cause: A system defect was detected before the last boot or in the actual one. The system might have been rebooted (reset).
Fault value (r0949, interpret hexadecimal):
200000 hex, 400000 hex, 8000yy hex (yy any):
- fault in the actual booting/operation.
800004 hex:
- parameters p9500/p9300 are, under certain circumstances, not the same. In addition, Safety message C01711/C30711
is displayed.
Additional values:
- defect before the last time that the system booted.
Remedy: - carry out a POWER ON (switch-off/switch-on).
- upgrade firmware to later version.
- contact Technical Support.
For fault value = 200000 hex, 400000 hex, 8000yy hex (yy any):
- ensure that the Control Unit is connected to the Power Module.
For fault value = 800004 hex:
- check that parameters p9500/p9300 are the same.
Note:
PM: Power Module
STO: Safe Torque Off
Cause: The parameterization of a Sensor Module used for Safety Integrated is not permissible.
Note:
This fault results in a STOP A that cannot be acknowledged.
Fault value (r0949, interpret decimal):
1: No encoder was parameterized for Safety Integrated.
2: An encoder was parameterized for Safety Integrated that does not have an A/B track (sine/cosine).
3: The encoder data set selected for Safety Integrated is still not valid.
4: A communication error with the encoder has occurred.
5: Number of relevant bits in the encoder coarse position invalid.
6: DRIVE-CLiQ encoder configuration invalid.
8: Parameterized Safety comparison algorithm not supported.
Remedy: For fault value = 1, 2:
- use and parameterize an encoder that Safety Integrated supports (encoder with track A/B sine-wave, p0404.4 = 1).
For fault value = 3:
- check whether the drive or drive commissioning function is active and if required, exit this (p0009 = p00010 = 0), save
the parameters (p0971 = 1) and carry out a POWER ON
For fault value = 4:
- check whether there is a DRIVE-CLiQ communication error between the Control Unit and the Sensor Module involved
and if required, carry out a diagnostics routine for the faults identified.
For fault value = 5:
- p9525 = 0 (not permissible). Check the encoder parameterization on the Sensor Modules involved.
For fault value = 6:
- check p9515.0 (for DRIVE-CLiQ encoders, the following applies: p9515.0 = 1). Check the encoder parameterization on
the Sensor Modules involved.
For fault value = 8:
- use and parameterize an encoder that implements an algorithm supported by Safety Integrated.
Note:
SI: Safety Integrated
Cause: The existing monitoring channel 2 software does not support safe motion monitoring, is not compatible to the software on
monitoring channel 1 - or there is a communications error between monitoring channels 1 and 2.
Note:
This fault results in a STOP A that cannot be acknowledged.
Fault value (r0949, decimal interpretation):
1:
The existing monitoring channel 2 software does not support the safe motion monitoring function.
2, 3, 6, 8:
There is a communication error between monitoring channel 1 and 2.
4, 5, 7:
The software on monitoring channel 2 is not compatible with the software on monitoring channel 1.
Remedy: - check whether there are faults in the safety function alignment between monitoring channel 1 and monitoring channel 2
(F01655, F30655) and if required, carry out diagnostics for the faults involved.
For fault value = 1:
- upgrade the drive software.
For fault value = 2, 3, 6, 8:
- check whether there are communication errors between monitoring channel 1 and monitoring channel 2 - and if required,
carry out diagnostics for the faults involved.
For fault value = 4, 5, 7:
- upgrade the drive software.
Note:
SI: Safety Integrated
Cause: The monitoring function enabled in p9501 and p9601 is not supported by the currently set PROFIsafe telegram (p9611).
Note:
This fault results in a STOP A that cannot be acknowledged.
Fault value (r0949, interpret bitwise binary):
Bit 18 = 1:
SS2E via PROFIsafe is not supported (p9501.18).
Bit 24 = 1:
Transfer SLS (SG) limit value via PROFIsafe not supported (p9501.24).
Bit 25 = 1:
Transfer safe position (SP) via PROFIsafe is not supported (p9501.25).
Bit 26 = 1:
Gearbox stage switchover via PROFIsafe is not supported (p9501.26).
Bit 28 = 1:
SCA via PROFIsafe is not supported (p9501.28).
Remedy: - Deselect the monitoring function involved (p9501, p9601).
- set the matching PROFIsafe telegram (p9611).
Note:
SCA: Safe Cam
SI: Safety Integrated
SLS: Safely Limited Speed
SP: Safe Position
SS2E: Safe Stop 2 external (Safe Stop 2 with external stop, external STOP D)
F01679 SI CU: Safety parameter settings and topology changed, warm restart/POWER ON required
Message value: -
Drive object: All objects
Reaction: OFF2 (OFF1, OFF3)
Acknowledge: POWER ON
Cause: Safety parameters have been changed; these will only take effect following a warm restart or POWER ON (see alarm
A01693).
A partial power up (boot) with modified configuration was then performed.
Remedy: - carry out a warm restart
- carry out a POWER ON (switch-off/switch-on).
Remedy: Correct parameter (if required, also on another monitoring channel, p9801).
If xxxx = 9501:
- de-select extended functions without selection (p9601.5).
If xxxx = 9501 and yyyy = 10:
De-select referencing via SCC (p9501.27).
For xxxx = 9501 and yyyy = 11:
De-select SS2E (p9501.18) - or enable PROFIsafe
For xxxx = 9501 and yyyy = 12:
De-select SCA (p9501.28).
If xxxx = 9507:
Set synchronous motor.
If xxxx = 9506:
Using the commissioning tool, copy the safety parameters, confirm the data change, backup the parameters and carry out
a power on.
If xxxx = 9522:
Correct the corresponding parameter.
If xxxx = 9547:
With hysteresis/filtering enabled (p9501.16 = 1), the following applies:
- set parameters p9546 and p9547 according to the following rule: p9547 <= 0.75 x p9546;
- the following rule must also be adhered to when actual value synchronization (p9501.3 = 1) is enabled: p9547 >= p9549;
If xxxx = 9601:
yyyy = 1:
Only enable motion monitoring functions integrated in the drive (p9601.2 = 1) and PROFIsafe (p9601.3 = 1).
yyyy = 2:
De-select Extended Functions without selection (p9601.5 = 0)
yyyy = 3:
De-select F-DI (p9601.4)
yyyy = 4:
De-select onboard F-DI (p9601.4) and F-DI via PROFIsafe (p9501.30).
yyyy = 5:
To transfer the SLS limit values via PROFIsafe (p9501.24 = 1), also enable PROFIsafe (p9601.3 =1) and motion monitoring
functions integrated in the drive (p9601.2 = 1).
yyyy = 6:
Deselect the transfer of the safe position via PROFIsafe (p9501.25 = 0)
yyyy = 7:
Deselect the safe switchover of gearbox stages (p9501.26 = 1)
yyyy = 13:
Also enable PROFIsafe (p9601.3) for the extended functions (p9601.2)
Note:
SSM: Safe Speed Monitor (safety-relevant feedback signal from the speed monitoring)
Cause: The monitoring function enabled in p9501, p9601, p9507 is not supported in this firmware version.
Note:
This fault results in a STOP A that cannot be acknowledged.
Fault value (r0949, interpret decimal):
1: Monitoring function SLP not supported (p9501.1).
2: Monitoring function SCA not supported (p9501.7 and p9501.8 ... 15).
3: Monitoring function SLS override not supported (p9501.5).
4: Monitoring function external ESR activation not supported (p9501.4).
5: Monitoring function F-DI in PROFIsafe not supported (p9501.30).
6: Enable actual value synchronization not supported (p9501.3).
9: Monitoring function not supported by the firmware or enable bit not used.
11: Encoderless monitoring functions (p9506.1) only supported for motion monitoring integrated in the drive (p9601.2).
20: Motion monitoring functions integrated in the drive are only supported in conjunction with PROFIsafe (p9501, p9601.1 ...
2 and p9801.1 ... 2).
21: Enable a safe motion monitoring function (in p9501), not supported for enabled basic functions via PROFIsafe (p9601.2
= 0, p9601.3 = 1).
26: Hysteresis and filtering for SSM monitoring function without an encoder not supported (p9501.16).
27: This hardware does not support onboard F-DI and F-DO.
28: Encoderless monitoring functions are not supported for synchronous motors (p9507.2).
33: Safety functions without selection not supported (p9601.5, p9801.5).
34: This module does not support safe position via PROFIsafe.
39: This module or software version of the CU/MM does not support safe gearbox stage switchover (p9501.26).
43: Motion monitoring functions SLP and SP as well as PROFIsafe telegrams 31/901/902 not supported for D410-2
(p9501.1/24/25/30, p9611).
44: This module/this software version does not support referencing via the safety control channel (p9501.27).
45: Deactivating SOS/SLS during an external STOP A is not supported (p9501.23).
46: This software version does not support control of the basis functions via TM54F and the simultaneous enable of the
extended functions or ncSI.
54: SCA function not supported (p9501.28).
9612: An attempt was made to parameterize STOP B as stop response for PROFIsafe failure, although PROFIsafe is not
enabled.
See also: p9612
Remedy: - de-select the monitoring functions involved (p9501, p9506, p9601, p9507).
For fault value = 9612:
- establish communications with PROFIsafe (p9601).
- parameterize STOP A as the stop response for PROFIsafe failure (p9612 = 0).
Note:
ESR: Extended Stop and Retract
SBR: Safe Brake Ramp (safe brake ramp monitoring)
SCA: Safe Cam
SDI: Safe Direction (safe motion direction)
SI: Safety Integrated
SLP: Safely Limited Position
SLS: Safely Limited Speed
SP: Safe Position
SS1E: Safe Stop 1 External (Safe Stop 1 with external stop)
SS2E: Safe Stop 2 external (Safe Stop 2 with external stop, external STOP D)
SOS: Safe Operating Stop
See also: p9501, p9601, p9612
Reaction: OFF2
Acknowledge: IMMEDIATELY (POWER ON)
Cause: The safety-relevant basic function "SOS/SLS" is not enabled in p9501 although other safety-relevant monitoring functions
are enabled.
Note:
This fault does not result in a safety stop response.
Remedy: Enable the function "SOS/SLS" (p9501.0) and carry out a POWER ON.
Note:
SI: Safety Integrated
SLS: Safely Limited Speed
SOS: Safe Operating Stop
See also: p9501
F01685 SI Motion P1 (CU): Safely limited speed limit value too high
Message value: %1
Drive object: All objects
Reaction: OFF2
Acknowledge: IMMEDIATELY (POWER ON)
Cause: The limit value for the function "Safely Limited Speed" (SLS) is greater than the speed that corresponds to an encoder
limit frequency of 500 kHz.
Note:
This fault does not result in a safety stop response.
Fault value (r0949, interpret decimal):
Maximum permissible speed.
Remedy: Correct the limit values for SLS and carry out a POWER ON.
Note:
SI: Safety Integrated
SLS: Safely Limited Speed
See also: p9531
Reaction: OFF2
Acknowledge: IMMEDIATELY (POWER ON)
Cause: For dbSI:
- at least one enabled "Safe cam" (SCA) is parameterized in p9536 or p9537 too close to the tolerance range around the
modulo position: the minus position value of a cam must be greater than the lower modulo limit + cam tolerance (p9540)
+ position tolerance (p9542); the plus position value of a cam must be less than the modulo limit - can tolerance (p9540)
- position tolerance (p9542). For a parameterized modulo position (p9505>0), the lower modulo limit = 0, the upper modulo
limit = p9505.
- the cam length of cam x = p9536[x]-p9537[x] is less than the cam tolerance + the position tolerance (= p9540 + p9542).
This also means that cams of the minus position value must be less than the plus position value.
For ncSI:
At least one enabled "Safety Cam" (SCA) is parameterized in p9536 or p9537 too close to the tolerance range around the
modulo position.
The following conditions must be complied with to assign cams to a cam track:
- the cam length of cam x = p9536[x]-p9537[x] must be greater or equal to the cam tolerance + the position tolerance (=
p9540 + p9542). This also means that for cams on a cam track, the minus position value must be less than the plus position
value.
- the distance between 2 cams x and y (minus position value[y] - plus position value[x] = p9537[y] - p9536[x]) on a cam
track must be greater than or equal to the cam tolerance + position tolerance (= p9540 + p9542).
Note:
This fault does not result in a safety stop response.
Fault value (r0949, interpret decimal):
Number of the "Safe Cam" with an illegal position.
See also: p9501
Remedy: Correct the cam position and carry out a POWER ON.
Note:
SCA: Safe Cam / SN: Safe software cam
SI: Safety Integrated
Cause: - it is not permissible to enable actual value synchronization for a 1-encoder system.
- it is not permissible to simultaneously enable actual value synchronization and a monitoring function with absolute
reference (SCA/SLP).
- it is not permissible to simultaneously enable actual value synchronization and safe position via PROFIsafe.
Note:
This fault results in a STOP A that cannot be acknowledged.
Remedy: - Either select the "actual value synchronization" function or parameterize a 2-encoder system.
- either deselect the function "actual value synchronization" or the monitoring functions with absolute reference (SCA/SLP)
and carry out a POWER ON.
- either deselect the "actual value synchronization" function or do not enable "Safe position via PROFIsafe".
Note:
SCA: Safe Cam / SN: Safe software cam
SI: Safety Integrated
SLP: Safely Limited Position / SE: Safe software limit switches
SP: Safe Position
See also: p9501
Cause: There is not sufficient memory space in the NVRAM on the drive to save parameters r9781 and r9782 (safety logbook).
Note:
This fault does not result in a safety stop response.
Fault value (r0949, interpret decimal):
1: There is no longer any free memory space in the NVRAM.
Remedy: For fault value = 1:
- de-select functions that are not required and that take up memory space in the NVRAM.
- contact Technical Support.
Note:
NVRAM: Non-Volatile Random Access Memory (non-volatile read and write memory)
A01693 (F) SI P1 (CU): Safety parameter setting changed, warm restart/POWER ON required
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: Safety parameters have been changed; these will only take effect following a warm restart or POWER ON.
Alarm value (r2124, interpret decimal):
Parameter number of the safety parameter which has changed, necessitating a warm restart or POWER ON.
Remedy: - carry out a warm restart
- carry out a POWER ON (switch-off/switch-on) for all components.
Note:
Before performing an acceptance test, a POWER ON must be carried out for all components.
Reaction upon F: NONE (OFF1, OFF2, OFF3)
Acknowl. upon F: POWER ON
F01694 (A) SI Motion CU: firmware version monitoring channel 2 older than monitoring channel 1
Message value: -
Drive object: All objects
Reaction: OFF2
Acknowledge: IMMEDIATELY (POWER ON)
Cause: The firmware version of monitoring channel 2 is older than that of monitoring channel 1
Note:
This message does not result in a safety stop response.
This message can occur, if after an automatic firmware update, a POWER ON was not carried out (Alarm A01007).
Remedy: A POWER ON must be carried out at the drive.
See also: r9590
Reaction upon A: NONE
Acknowl. upon A: NONE
A01696 (F) SI Motion: Test stop for the motion monitoring functions selected when booting
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The forced checking procedure (test stop) for the safe motion monitoring functions is already selected when booting, which
is not permissible.
This is the reason that the test is only carried out again after first selecting the forced checking procedure.
Note:
This message does not result in a safety stop response.
Remedy: De-select the forced checking procedure for the safe motion monitoring functions and then select again.
Note:
The signal source to select the forced checking procedure is set via binector input p9705.
SI: Safety Integrated
Reaction upon F: NONE (OFF1, OFF2, OFF3)
Acknowl. upon F: IMMEDIATELY (POWER ON)
A01697 (F) SI Motion: Test stop for motion monitoring functions required
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The time set in p9559 for the forced checking procedure (test stop) for the safe motion monitoring functions has been
exceeded. A new forced checking procedure is required.
After the next time the forced checking procedure is selected, the message is withdrawn and the monitoring time is reset.
Note:
- this message does not result in a safety stop response.
- As the switch-off signal paths are not automatically checked during booting, an alarm is always issued once booting is
complete.
- the test must be performed within a defined, maximum time interval (p9559, maximum of 9000 hours) in order to comply
with the requirements as laid down in the standards for timely fault detection and the conditions to calculate the failure
rates of safety functions (PFH value). Operation beyond this maximum time period is permissible if it can be ensured that
the forced checking procedure is performed before persons enter the hazardous area and who are depending on the safety
functions correctly functioning.
See also: p9559, r9765
Remedy: Carry out the forced checking procedure of the safety motion monitoring functions.
The signal source to select the forced checking procedure is set via binector input p9705.
Note:
SI: Safety Integrated
Reaction upon F: NONE (OFF1, OFF2, OFF3)
Acknowl. upon F: IMMEDIATELY (POWER ON)
Remedy: - remove the cause of the fault on the second monitoring channel.
- carry out a diagnostics routine for message C01706.
- carry out a diagnostics routine for message C01714.
- carry out a diagnostics routine for message C01701.
- carry out a diagnostics routine for message C01716.
- check the value in p9557 (where available), increase the value if necessary, and carry out a POWER ON
- check the switch-off signal path of monitoring channel 1 (check DRIVE-CLiQ communication if it has been implemented)
- replace drive.
This message can be acknowledged without a POWER ON as follows (safe acknowledgment):
- PROFIsafe.
- machine control panel.
Note:
SAM: Safe Acceleration Monitor (safe acceleration monitoring)
SBR: Safe Brake Ramp (safe brake ramp monitoring)
SI: Safety Integrated
Remedy: Check the braking behavior and, if necessary, adapt the parameterization of the parameter settings of the "SAM" or the
"SBR" function.
This message can be acknowledged without a POWER ON as follows (safe acknowledgment):
- PROFIsafe.
- machine control panel.
Note:
SAM: Safe Acceleration Monitor (safe acceleration monitoring)
SBR: Safe Brake Ramp (safe ramp monitoring)
SI: Safety Integrated
See also: p9548, p9581, p9582, p9583
Cause: When cross-comparing the two monitoring channels, the drive detected a difference between the input data or results of
the monitoring functions and initiated a STOP F. One of the monitoring functions no longer reliably functions - i.e. safe
operation is no longer possible.
If at least one monitoring function is active, then after the parameterized timer has expired, the message C01701 "SI
Motion: STOP B initiated" is output.
The message value that resulted in a STOP F is displayed in r9725.
The following described message values involve the data cross-check between the two monitoring channels (safety
functions integrated in the drive).
The message values may also occur in the following cases if the cause that is explicitly mentioned does not apply:
- For message values 3, 44 ... 57, 232 and 1-encoder system, differently set encoder parameters.
- incorrect synchronization.
Message value (r2124, interpret decimal):
0 to 999: number of the cross-compared data that resulted in this fault.
Message values that are not subsequently listed are only for internal Siemens troubleshooting.
0: Stop request from the other monitoring channel.
1: Status image of monitoring functions SOS, SLS, SAM/SBR or SDI (result list 1) (r9710[0], r9710[1]).
2: Status image of monitoring function SSM (result list 2) (r9711[0], r9711[1]).
3: The position actual value differential (r9713[0/1]) between the two monitoring channels is greater than the tolerance in
p9542.
4: Error when synchronizing the data cross-check between the two channels.
5: Function enable signals (p9501/p9301) Safety monitoring clock cycle too small (p9500/p9300).
6: Limit value for SLS1 (p9531[0]).
7: Limit value for SLS2 (p9531[1]).
8: Limit value for SLS3 (p9531[2]).
9: Limit value for SLS4 (p9531[3]).
10: Standstill tolerance (p9530).
31: Position tolerance (p9542/p9342) or (p9549/p9349) when actual value synchronization is enabled (p9501.3)
33: Time, speed switchover (p9551)
35: Delay time, STOP A (p9556).
36: Test time, STO (p9557).
37: Transition time, STOP C to SOS (p9552).
38: Transition time STOP D to SOS (p9553)
40: Stop response for SLS (p9561).
42: Shutdown speed STO (p9560).
43: Memory test, stop response (STOP A).
44 ... 57: General
Possible cause 1 (during commissioning or parameter modification)
The tolerance value for the monitoring function is not the same on the two monitoring channels.
Possible cause 2 (during active operation)
The limit values are based on the actual value (r9713[0/1]). If the safe actual values on the two monitoring channels do
not match, the limit values, which have been set at a defined interval, will also be different (i.e. corresponding to message
value 3). This can be ascertained by checking the safe actual positions.
Permissible deviation between the two monitoring channels: p9542.
44: Position actual value (r9713[0/1]) + limit value SLS1 (p9531[0]) * safety monitoring clock cycle.
45: Position actual value (r9713[0/1]) + limit value SLS1 (p9531[0]) * safety monitoring clock cycle.
46: Position actual value (r9713[0/1]) + limit value SLS2 (p9531[1]) * safety monitoring clock cycle.
47: Position actual value (r9713[0/1]) + limit value SLS2 (p9531[1]) * safety monitoring clock cycle.
48: Position actual value (r9713[0/1]) + limit value SLS3 (p9531[2]) * safety monitoring clock cycle.
49: Position actual value (r9713[0/1]) - limit value SLS3 (p9531[2]) * safety monitoring clock cycle.
50: Position actual value (r9713[0/1]) + limit value SLS4 (p9531[3]) * safety monitoring clock cycle.
51: Position actual value (r9713[0/1]) - limit value SLS4 (p9531[3]) * safety monitoring clock cycle.
52: Standstill position + tolerance (p9530).
53: Standstill position - tolerance (p9530).
54: Position actual value (r9713[0/1]) + limit value of SSM (p9546) * safety monitoring clock cycle + tolerance (p9542).
55: Position actual value (r9713[0/1]) + limit value of SSM (p9546) * safety monitoring clock cycle.
56: Position actual value (r9713[0/1]) - limit value of SSM (p9546) * safety monitoring clock cycle.
57: Position actual value (r9713[0/1]) - limit value of SSM (p9546) * safety monitoring clock cycle - tolerance (p9542).
58: Actual stop request.
75: Velocity limit of SSM (p9546).
When the function "SSM: hysteresis and filtering" (p9501.16 = 1) is enabled, this message value is also output for a different
hysteresis tolerance (p9547).
76: Stop response for SLS1 (p9563[0]).
77: Stop response for SLS2 (p9563[1]).
78: Stop response for SLS3 (p9563[2]).
79: Stop response for SLS4 (p9563[3]).
81: Velocity tolerance for SAM (p9548).
82: SGEs for SLS correction factor.
83: Acceptance test timer (p9558).
84: Transition time STOP F (p9555).
85: Transition time bus failure (p9580).
89: Encoder limit frequency.
230: Filter time constant for SSM.
231: Hysteresis tolerance for SSM.
232: Smoothed velocity actual value.
233: Limit value of SSM / safety monitoring clock cycle + hysteresis tolerance.
234: Limit value of SSM / safety monitoring clock cycle.
235: -Limit value of SSM / safety monitoring clock cycle.
236: -Limit value of SSM / safety monitoring clock cycle - hysteresis tolerance.
237: SGA SSM.
238: Speed limit value for SAM (p9568 or p9546).
239: Acceleration for SBR (p9581 and p9583).
240: Inverse value of acceleration for SBR (p9581 and p9583).
241: Deceleration time for SBR (p9582).
242: Encoderless safety (p9506).
243: Function configuration (p9507).
247: SDI tolerance (p9564).
248: SDI positive upper limit (7FFFFFFF hex).
249: Position actual value (r9713[0/1]) - SDI tolerance (p9564).
250: Position actual value (r9713[0/1]) + SDI tolerance (p9564).
251: SDI negative lower limit (80000001 hex).
252: SDI stop response (p9566).
253: SDI delay time (p9565).
256: Status image of monitoring functions SOS, SLS, test stop, SBR, SDI (result list 1 ext) (r9710).
259: PROFIsafe telegram (p9611) is different between the monitoring channels.
261: Scaling factor for acceleration for SBR different.
262: Scaling factor for the inverse value of the acceleration for SBR different.
265: Status image of all change functions (results list 1) (r9710).
268: SLP delay time differs (p9577).
270: Screen form for SGE image: all functions, which are not supported/enabled for the actual parameterization (p9501,
p9601 and p9506).
273: speed limit value for flattening the ramp for SAM/SBR different.
1000: Watchdog timer has expired. Too many signal changes have occurred at safety-relevant inputs.
1001: Initialization error of watchdog timer.
1005: STO already active for test stop selection.
1011: Acceptance test status between the monitoring channels differ.
1012: Plausibility violation of the actual value from the encoder.
- check the setting of the PROFIsafe address of the drive (p9610). It is not permissible for the PROFIsafe address to be
0 or FFFF!
- using the commissioning tool, copy the safety parameters and confirm the data change.
- carry out a POWER ON (switch-off/switch-on) for all components.
For message value = 5013, 5025:
- carry out a POWER ON (switch-off/switch-on) for all components.
- check the setting of the PROFIsafe address of the drive (p9610).
For message value = 5022:
- check the setting of the values of the F parameters at the PROFIsafe slave (F_SIL, F_CRC_Length, F_Par_Version,
F_Source_Add, F_Dest_add, F_WD_Time).
For message value = 5026:
- check the settings of the values of the F parameters and the F parameter CRC (CRC1) calculated from these at the
PROFIsafe slave and update.
For message value = 5065:
- check the configuration and communication at the PROFIsafe slave (cons. No. / CRC).
- check the setting of the value for F parameter F_WD_Time on the PROFIsafe slave and increase if necessary.
For message value = 5066:
- check the setting of the value for F parameter F_WD_Time on the PROFIsafe slave and increase if necessary.
- evaluate diagnostic information in the F host.
- check PROFIsafe connection.
For message value = 6000 ... 6999:
Refer to the description of the message values in safety fault F01611.
For message value = 7000:
- increase the parameterized tolerance (p9542).
- determine the actual position of CU (r9713[0] and the second channel r9713[1], and check the difference for plausibility.
For message value = 7002:
- carry out a POWER ON (switch-off/switch-on) for all components.
This message can be acknowledged without a POWER ON as follows (safe acknowledgment):
- PROFIsafe.
- machine control panel.
Cause: When cross checking and comparing the two monitoring channels, the drive detected a difference between parameters
or results of the F-IO processing and initiated a STOP F. One of the monitoring functions no longer reliably functions - i.e.
safe operation is no longer possible.
The safety message C01711 with message value 0 is also displayed due to initiation of STOP F.
If at least one monitoring function is active, the safety message C01701 "SI Motion: STOP B initiated" is output after the
parameterized timer has expired.
Message value (r9749, interpret decimal):
Number of the cross-compared data that resulted in this message.
1: SI discrepancy monitoring time inputs (p10002, p10102).
2: SI acknowledgment internal event input terminal (p10006, p10106).
3: SI STO input terminal (p10022, p10122).
4: SI SS1 input terminal (p10023, p10123).
5: SI SS2 input terminal (p10024, p10124).
6: SI SOS input terminal (p10025, p10125).
7: SI SLS input terminal (p10026, p10126).
8: SI SLS_Limit(1) input terminal (p10027, p10127).
9: SI SLS_Limit(2) input terminal (p10028, p10128).
10: SI Safe State signal selection (p10039, p10139).
11 SI F-DI input mode (p10040, p10140).
12: SI F-DO 0 signal sources (p10042, p10142).
13: Different states for static inactive signal sources (p10006, p10022 ... p10031).
14: SI discrepancy monitoring time outputs (p10002, p10102).
15: SI acknowledgment internal event (p10006, p10106).
16: SI test sensor feedback signal test mode selected for test stop (p10046, p10146, p10047, p10147).
17: SI delay time for test stop at DOs (p10001).
18 ... 25: SI test sensor feedback signal (p10046, p10146, p10047, p10147). Expected state of internal readback signal,
generated from the selected test stop mode.
26 ... 33: SI test sensor feedback signal (p10046, p10146, p10047, p10147). Expected state of external readback signal,
generated from the selected test stop mode.
34 ... 41: SI test sensor feedback signal (p10046, p10146, p10047, p10147). Expected state of second internal readback
signal, generated from the selected test stop mode.
42: Internal data for processing the second internal readback signal, generated from the selected test stop mode (p10047,
p10147).
43: Internal data for processing the internal readback signal, generated from the selected test stop mode (p10047, p10147).
44: Internal data for processing the external readback signal, generated from the selected test stop mode (p10047, p10147).
45: Internal data for initialization state of test stop mode, dependent upon test stop parameters.
46: SI digital inputs debounce time (p10017, p10117)
47: Selection F-DI for PROFIsafe (p10050, p10150)
48: Screen form of the F-DIs used (p10006, p10022 ... p10031).
49: SI SDI positive input terminal (p10030, p10130).
50: SI SDI negative input terminal (p10031, p10131).
51: SI SLP input terminal (p10032, p10132).
52: SI SLP select input terminal (p10033, p10133).
53: Internal data for retraction logic (p10009, p100109).
54: SI F-DI for retraction SLP (p10009, p100109).
Remedy: - check parameterization in the parameters involved and correct if required.
- ensure equality by copying the SI data to the second channel and then carry out an acceptance test.
- check monitoring clock cycle in p9500 and p9300 for equality.
This message can be acknowledged without a POWER ON as follows (safe acknowledgment):
- onboard F-DI (only CU310-2).
- PROFIsafe.
- machine control panel.
C01730 SI Motion P1 (CU): Reference block for dynamic safely limited speed invalid
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: IMMEDIATELY (POWER ON)
Cause: The reference block transferred via PROFIsafe is negative.
A reference block is used to generate a referred velocity limit value based on the reference quantity "Velocity limit value
SLS1" (p9531[0]).
The drive is stopped as a result of the configured stop response (p9563[0]).
Message value (r2124, interpret decimal):
requested, invalid reference block.
Remedy: In the PROFIsafe telegram, input data S_SLS_LIMIT_IST must be corrected.
This message can be acknowledged without a POWER ON as follows (safe acknowledgment):
- PROFIsafe.
Note:
SI: Safety Integrated
SLS: Safely Limited Speed
C01745 SI Motion P1 (CU): Checking braking torque for the brake test
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: POWER ON (IMMEDIATELY)
Cause: The scaling of the brake torque for the brake test can be changed using parameter p2003.
An acceptance test must be carried out again for the braking test. This determines whether the braking test is still carried
out with the correct braking torque.
Remedy: - carry out a POWER ON (switch-off/switch-on) for all components.
- repeat the acceptance test for the safe brake test if the brake test is used.
See also: p2003
A01788 SI: Automatic test stop waits for STO deselection via motion monitoring functions
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The automatic test stop (forced checking procedure) was not able to be carried out after powering up.
Possible causes:
- the STO function is selected via safe motion monitoring functions.
- a safety message is present, that resulted in a STO.
Note:
STO: Safe Torque Off
Remedy: - deselect STO via safe motion monitoring functions.
- remove the cause of the safety messages and acknowledge the messages.
Note:
The automatic test stop is performed after removing the cause.
A01789 SI: Automatic test stop and brake test when test stop is selected not permitted
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The parameterization of the automatic test stop (p9507.6/p9307.6) and the brake test when a test stop is selected (p10203
= 2) are not permissible.
The test stop is not automatically carried out when the powering up.
Remedy: - correct the parameter assignment.
- set p10203 not equal to 2 or deactivate the automatic test stop.
Note:
A warm restart or POWER ON is required to carry out the automatic test stop.
A01794 (N) SI Motion: check modulo value for safe position via PROFIsafe
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: When parameterizing the modulo value for safe position via PROFIsafe (p9505) the position actual value can jump when
the range that can be represented overflows.
Range that can be represented:
- 32-bit value: +/- 2048 revolutions
- 16-bit value: +/- 2048 revolutions (depending on p9574)
Remedy: Correct the parameter assignment.
Set p9505 to 2^n revolutions - and to complete revolutions (i.e. a multiple of 360 °).
Note:
This alarm can be hidden for the case that the possible position actual value jump can be tolerated for the particular
application, or does not represent a problem; for example because the parameterized modulo range fits "almost as integer
number" in the range of +/- 2048 revolutions that can be represented.
To re-parameterize the alarm to "NO REPORT", it is not permissible that the alarm is present. As a consequence, the
following sequence is required for the re-parameterization:
- correct p9505 to "2^n".
- re-parameterize the alarm using p2118 and p2119.
- set p9505 back to the required value.
Reaction upon N: NONE
Acknowl. upon N: NONE
A01795 SI Motion P1 (CU): Wait time after exiting the safe pulse cancellation expired
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: After exiting safe pulse cancellation, within the wait time of 5 seconds, encoderless actual value sensing was not able to
be activated for the extended functions without selection.
A change is again made into the "safe pulse cancellation" state.
Remedy: - check missing enable signals, which prevent the drive control from being commissioned (r0046).
- evaluate possible fault messages of the encoderless actual value sensing and remove.
Remedy: If, after a longer period of time, the message is not automatically withdrawn, the following checks have to be made:
- check any other PROFIsafe communication messages/signals present and evaluate them.
- check the operating state of the F-Host.
- check the communication connection to the F Host.
Note:
STO: Safe Torque Off
See also: p9601
Reaction upon F: NONE (OFF1, OFF2, OFF3)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
C01798 SI Motion P1 (CU): Test stop for motion monitoring functions running
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: IMMEDIATELY (POWER ON)
Cause: The forced checking procedure (test stop) for the safe motion monitoring functions is currently in progress.
Remedy: Not necessary.
The message is automatically withdrawn when the test stop has been completed.
Note:
SI: Safety Integrated
Cause: An SMI/DQI without motor data has been found (e.g. SMI installed as replacement part).
Alarm value (r2124, interpret decimal):
Component number from target topology.
Remedy: 1. Download the SMI/DQI data (motor/encoder data) from the data backup again (p4690, p4691).
2. Carry out a POWER ON (switch-off/switch-on) for this component.
Note:
DQI: DRIVE-CLiQ Sensor Integrated
SMI: SINAMICS Sensor Module Integrated
Remedy: Check the bus configuration on the master and the slave sides.
For alarm value = 1, 2:
- check the list of the drive objects with process data exchange (p0978).
Note:
With p0978[x] = 0, all of the following drive objects in the list are excluded from the process data exchange.
For alarm value = 2:
- check the number of data words for output and input to a drive object.
For alarm value = 211:
- Ensure offline version <= online version.
For alarm value = 223, 500:
- check the setting in p8839 and p8815.
- check for inserted but not configured CBE20.
- ensure that only one PZD interface is operated in clock synchronism or with PROFIsafe.
For alarm value = 255:
- check configured drive objects.
For alarm value = 256:
- check the configured telegram.
For alarm value = 501:
- check the set PROFIsafe address (p9610).
For alarm value = 502:
- check the set PROFIsafe telegram (p60022, p9611).
Reaction upon F: NONE (OFF1)
Acknowl. upon F: IMMEDIATELY
F01911 (N, A) PB/PN: clock cycle synchronous operation clock cycle failure
Message value: -
Drive object: All objects
Reaction: Servo: OFF1 (OFF3)
Acknowledge: IMMEDIATELY
Cause: The global control telegram to synchronize the clock cycles has failed - in cyclic operation - for several DP clock cycles or
has violated the time grid specified in the parameterizing telegram over several consecutive DP clock cycles (refer to the
bus cycle time, Tdp and Tpllw).
Remedy: - check the physical bus configuration (cable, connector, terminating resistor, shielding, etc.).
- check whether communication was briefly or permanently interrupted.
- check the bus and controller for utilization level (e.g. bus cycle time Tdp was set too short).
PB: PROFIBUS
PN: PROFINET
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F01915 (N, A) PB/PN: clock cycle synchronous operation sign-of-life failure drive object 1
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: Group display for problems with the sign-of-life of the master (isochronous operation) on the drive object 1 (Control Unit).
For central measurements, synchronism with the central master is lost.
Remedy: Note:
PB: PROFIBUS
PN: PROFINET
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
A01930 PB/PN: current controller sampling time clock cycle synch. not equal
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The current controller sampling time of all drives must be set the same for the clock cycle synchronous operation.
Alarm value (r2124, interpret decimal):
Number of the drive object with different current controller sampling time.
Remedy: Set current controller sampling time to identical values (p0115[0]).
Note:
PB: PROFIBUS
PN: PROFINET
A01931 PB/PN: speed controller sampling time clock cycle synch. not equal
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The speed controller sampling time of all drives must be set the same for the clock cycle synchronous operation.
Alarm value (r2124, interpret decimal):
Number of the drive object with the different speed controller sampling time.
Remedy: Set the speed controller sampling times to identical values (p0115[1]).
Note:
PB: PROFIBUS
PN: PROFINET
A01941 PB/PN: clock cycle signal missing when establishing bus communication
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The bus is in the data exchange state and clock synchronous operation has been selected using the parameterizing
telegram. The global control telegram for synchronization is not being received.
Remedy: Check the master application and bus configuration.
Note:
PB: PROFIBUS
PN: PROFINET
A01943 PB/PN: clock cycle signal error when establishing bus communication
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The bus is in the data exchange state and clock synchronous operation has been selected using the parameterizing
telegram.
The global control telegram for synchronization is being irregularly received.
-.the master is sending an irregular global control telegram.
- the master is using another clock synchronous DP clock cycle than was transferred to the slave in the parameterizing
telegram.
Remedy: - check the master application and bus configuration.
- check the consistency between the clock cycle input when configuring the slave and clock cycle setting at the master.
Note:
PB: PROFIBUS
PN: PROFINET
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.
Reaction upon A: NONE
Acknowl. upon A: NONE
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.
Acknowledge: NONE
Cause: The cyclic actual values and/or setpoints were not transferred within the specified times.
Alarm value (r2124, interpret hexadecimal):
Only for internal Siemens troubleshooting.
Remedy: Correctly set T_io_input or T_io_output.
Remedy: Use a SERVO / VECTOR / DC_CTRL drive object with the corresponding number.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
A02010 Function generator: Speed setpoint from the drive is not zero
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The speed setpoint of a drive selected for connection is greater than the value for the standstill detection set using p1226.
Remedy: For all of the drives specified for connection, set the speed setpoints to zero.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
Reaction: NONE
Acknowledge: NONE
Cause: The speed actual value of a drive selected for connection is greater than the value for the standstill detection set using
p1226.
Remedy: Set the relevant drives to zero speed before starting the function generator.
Note:
The alarm is reset as follows:
- remove the cause of this alarm.
- restart the function generator.
Cause: TRACE recording is not possible as at least one signal or trigger signal being used is under know-how protection.
Alarm value (r2124, interpret hexadecimal):
bbbbaaaa hex:
aaaa = 1: recorder 0
aaaa = 2: recorder 1
aaaa = 3: recorders 0 and 1
bbbb = parameter number (hexadecimal), that was not able to be written to.
Remedy: - Temporarily activate or deactivate know-how protection (p7766).
- include the signal in the OEM exception list (p7763, p7764).
- Where relevant do not record the signal.
A02058 Trace: Time slice clock cycle for endless trace not valid
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The selected time slice clock cycle cannot be used for the endless trace
Remedy: Enter the clock cycle of an existing time slice with a cycle time >= 2 ms for up to 4 recording channels or >= 4 ms from 5
recording channels per trace.
The existing time slices can be read out via p7901.
A02059 Trace: Time slice clock cycle for 2 x 8 recording channels not valid
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The selected time slice clock cycle cannot be used for more than 4 recording channels.
Remedy: Enter the clock cycle of an existing time slice with a cycle time >= 4 ms or reduce the number of recording channels to 4
per trace.
The existing time slices can be read out via p7901.
Reaction: NONE
Acknowledge: NONE
Cause: The trace parameter settings cannot be changed when the trace is active.
Remedy: - stop the trace before parameterization.
- if required, start the trace.
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: A technology function (e.g. Technology Extension, DCB library) does not exist on the drive device.
When configuring, a technology function is activated, which does not exist on the drive device. This can occur when
downloading a project or when powering up.
Remedy: - load the required technology function to the drive device.
- if required, deactivate the technology function not required in the configuration.
Note:
DCB: Drive Control Block
TEC: Technology Extension
Cause: Despite specification by the signal source the digital output has not been set.
Possible causes:
- power supply missing.
- the digital output is in current limiting (e.g. due to short-circuit).
- the digital output is being used for Safety Extended Functions.
- the control has authority to access the digital output by means of direct access (see also r0729).
Alarm value (r2124, interpret bitwise binary):
Digital output involved (structured the same as r0747).
Remedy: - check the 24 V power supply (e.g. X131.7 for CU305, ground is X131.8).
- check the output terminals for short-circuits.
- reset the signal source of the digital output for use by Safety Extended functions.
- carry out a POWER ON (switch-off/switch-on).
Reaction upon F: NONE
Acknowl. upon F: IMMEDIATELY (POWER ON)
Reaction upon N: NONE
Acknowl. upon N: NONE
A03550 TM: Speed setpoint filter natural frequency > Shannon frequency
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The natural filter frequency of the speed setpoint filter (p1417) is greater than or equal to the Shannon frequency.
The Shannon frequency is calculated according to the following formula:
0.5 / p4099[3]
Remedy: Reduce the natural frequency of the speed setpoint filter (PT2 low pass) (p1417).
Remedy: - check the feedback signals and parameter assignment (p0260 ... p0267).
- check the coolant feed.
F05060 Parallel circuit: Power unit firmware version does not match
Message value: Parameter: %1
Drive object: All objects
Reaction: OFF2
Acknowledge: IMMEDIATELY
Cause: Firmware from version V02.30.01.00 is required when connecting the power units in parallel.
Remedy: Update the firmware of the power units (at least V02.30.01.00).
Acknowledge: IMMEDIATELY
Cause: KTY84/PT1000:
The motor temperature has exceeded the fault threshold (p0605) or the timer (p0606) after the alarm threshold was
exceeded (p0604) has expired.
PTC, bimetallic NC contact:
The response threshold of 1650 Ohm was exceeded (for SME p4600 ... p4603 or for TM120 p4610 ... p4613 = 10, 30), or
the timer (p0606) has expired after 1650 Ohm has been exceeded (for SME p4600 ... p4603 or for TM120 p4610 ... p4613
= 12, 32).
Motor temperature model:
The calculated motor temperature is too high.
Possible causes:
- motor overloaded.
- motor ambient temperature too high.
- PTC / bimetallic NC contact: Wire breakage or sensor not connected.
- motor temperature model incorrectly parameterized.
Hysteresis:2K
Fault value (r0949, interpret decimal):
1, 2, 3, 4:
Number of the temperature channel leading to the message (for SME/TM120 (p0601 = 10, 11)).
200:
Motor temperature model 1 (I2t): temperature too high.
300:
Motor temperature model 3: after the monitoring time has expired, the temperature is still higher than the alarm threshold.
301:
Motor temperature model 3: temperature is too high, or the model has not been parameterized.
302:
Motor temperature model 3: Encoder temperature is not within the valid range.
See also: p0613
Remedy: - reduce the motor load.
- check the ambient temperature and the motor ventilation.
- check the wiring and temperature sensor connection.
- check monitoring limits.
- check the encoder type (p0404).
- check the motor type (p0300, p0301).
- check activation of the motor temperature model (p0612).
- check the motor temperature model parameters.
- check the encoder (p0404).
F07086 Units changeover: Parameter limit violation due to reference value change
Message value: Parameter: %1
Drive object: All objects
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: A reference parameter was changed in the system. This resulted in the fact that for the parameters involved, the selected
value was not able to be written in the per unit notation.
The values of the parameters were set to the corresponding violated minimum limit/maximum limit or to the factory setting.
Possible causes:
- the steady-state minimum limit/maximum limit or that defined in the application was violated.
Fault value (r0949, parameter):
Diagnostics parameter to display the parameters that were not able to be re-calculated.
See also: p0304, r0304, p0305, r0305, p2000, p2003
Remedy: Check the adapted parameter value and if required correct.
F07087 Drive: Encoderless operation not possible for the selected pulse frequency
Message value: Parameter: %1
Drive object: All objects
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: Encoderless operation is not possible for the selected pulse frequency (p1800).
Encoderless operation is activated under the following conditions:
- the changeover speed for encoderless operation (p1404) is less than the maximum speed (p0322).
- a control type with encoderless operation has been selected (p1300).
- encoder faults of the motor encoder result in a fault response with encoderless operation (p0491).
Remedy: Increase the pulse frequency (p1800).
Note:
In encoderless operation, the pulse frequency must be at least as high as one quarter of the current controller clock cycle
frequency (1/p0115[0]).
A07089 Changing over units: Function module activation is blocked because the units have been changed
over
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: An attempt was made to activate a function module. This is not permissible if the units have already been changed over.
Remedy: Restore units that have been changed over to the factory setting.
F07090 Drive: Upper torque limit less than the lower torque limit
Message value: -
Drive object: All objects
Reaction: OFF2 (NONE, OFF1, OFF3)
Acknowledge: IMMEDIATELY
Cause: The upper torque limit is lower than the lower torque limit.
Remedy: P1 must be >= P2 if parameter P1 is connected to p1522 and parameter P2 to p1523.
Acknowledge: IMMEDIATELY
Cause: An error was identified when executing the "Test signal" function (p5307.1 = 1) or auto tuning was selected (p5300 = 1).
The function was not executed or was canceled.
Fault value (r0949, interpret decimal):
yyyyxxxx hex: yyyy = error cause, xxxx = traversing distance
See also: p5308, p5309
Remedy: - enter the traversing path in parameter p5308 - or deselect the function involved in p5301.
- for fault cause = 1, 2, shorter traversing paths may be possible.
For fault cause = 1:
- deselect bit 0 and bit 1 in parameter p5301.
For fault cause = 2:
- deselect bit 2 in parameter p5301.
For fault cause= 3:
- deselect bit 4 and bit 5 in parameter p5301.
Reaction upon A: NONE
Acknowl. upon A: NONE
F07110 Drive: Sampling times and basic clock cycle do not match
Message value: Parameter: %1
Drive object: All objects
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: The parameterized sampling times do not match the basic clock cycle.
Fault value (r0949, interpret decimal):
The fault value specifies the parameter involved.
Remedy: Enter the current controller sampling times so that they are identical to the basic clock cycle, e.g. by selecting p0112. Note
which basic clock cycle is selected in p0111.
The sampling times in p0115 can only be changed manually in the sampling times pre-setting "Expert" (p0112).
A07329 (N) Drive: kT estimator, kT(iq) characteristic or voltage compensation does not function
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: A function of the function module "extended torque control" (r0108.1) was activated - however the (complete) function is
not available.
Alarm value (r2124, interpret decimal):
1 ... 3: The kT estimator is active (p1780.3 = 1) without a functioning compensation of the voltage emulation error in the
drive converter. This means that the accuracy is severely restricted.
1: The drive converter voltage emulation error "final value" is 0 (p1952).
2: The drive converter voltage emulation error "current offset" is 0 (p1953).
3: The compensation of the voltage emulation error is disabled (p1780.8 = 0).
4: The kT estimator (p1780.3 = 1), the kT(iq) characteristic (p1780.9 = 1) or the compensation of the voltage emulation
error (p1780.8 = 1) was activated without activating the function module "extended torque control" (when the function
module is activated, the following must apply: r0108.1 = 1).
5: the kT(iq) characteristic has been activated (p1780.9 = 1). However, the kT characteristic value kT1 is 0 (p0645). The
function is not active.
F07420 Drive: Current setpoint filter natural frequency > Shannon frequency
Message value: %1
Drive object: All objects
Reaction: NONE (OFF1, OFF2, OFF3)
Acknowledge: IMMEDIATELY (POWER ON)
Cause: One of the filter natural frequencies is greater than the Shannon frequency.
The Shannon frequency is calculated according to the following formula: 0.5 / p0115[0]
Fault value (r0949, interpret hexadecimal):
Bit 0: Filter 1 (p1658, p1660)
Bit 1: Filter 2 (p1663, p1665)
Bit 2: Filter 3 (p1668, p1670)
Bit 3: Filter 4 (p1673, p1675)
Bit 8 ... 15: Data set number (starting from zero)
Bit 16: Filter 5 (p5202, p5204) - extended current setpoint filter (r0108.21)
Bit 17: Filter 6 (p5207, p5209) - extended current setpoint filter (r0108.21)
Bit 18: Filter 7 (p5212, p5214) - extended current setpoint filter (r0108.21)
Bit 19: Filter 8 (p5217, p5219) - extended current setpoint filter (r0108.21)
Bit 20: Filter 9 (p5222, p5224) - extended current setpoint filter (r0108.21)
Bit 21: Filter 10 (p5227, p5229) - extended current setpoint filter (r0108.21)
Remedy: - reduce the numerator or denominator natural frequency of the current setpoint filter involved.
- reduce the current controller sampling time (p0115[0]).
- switch out the filter involved (p1656).
F07433 Drive: Closed-loop control with encoder is not possible as the encoder has not been unparked
Message value: %1
Drive object: All objects
Reaction: NONE (OFF1, OFF2, OFF3)
Acknowledge: IMMEDIATELY
Cause: The changeover to closed-loop control with encoder is not possible as the encoder has not been unparked.
Remedy: - check whether the encoder firmware supports the "parking" function (r0481.6 = 1).
- upgrade the firmware.
Note:
For long-stator motors (p3870.0 = 1), the following applies:
The encoder must have completed the unparking procedure (r3875.0 = 1) before a changeover can be made to closed-
loop control with encoder. The encoder is unparked using binector input p3876 = 0/1 signal and remains until a 0 signal
in this state.
F07434 Drive: It is not possible to change the direction of rotation with the pulses enabled
Message value: -
Drive object: All objects
Reaction: OFF2
Acknowledge: IMMEDIATELY
Cause: A drive data set was selected - with the pulses enabled - which has a different parameterized direction of rotation (p1821).
It is only possible to change the motor direction of rotation using p1821 when the pulses are inhibited.
Remedy: - change over the drive data set with the pulses inhibited.
- ensure that the changeover to a drive data set does not result in the motor direction of rotation being changed (i.e. for
these drive data sets, the same value must be in p1821).
See also: p1821
F07448 (A) Load gear: Position tracking, linear axis has exceeded the maximum range
Message value: -
Drive object: All objects
Reaction: Servo: OFF1 (NONE, OFF2, OFF3)
Acknowledge: IMMEDIATELY
Cause: For a configured linear axis/no modulo axis, the currently effective motor encoder (encoder 1) has exceeded the maximum
possible traversing range.
For the configured linear axis, the maximum traversing range is defined to be 64x (+/- 32x) of p0421. It should be read in
p2721 and interpreted as the number of load revolutions.
Note:
Only the motor encoder in the currently effective drive data set is monitored here. The actual effective drive data set is
displayed in x = r0051 and the corresponding motor encoder is specified in in p0187[x].
Remedy: The fault should be resolved as follows:
- select encoder commissioning (p0010 = 4).
- reset position tracking, position (p2720.2 = 1).
- deselect encoder commissioning (p0010 = 0).
The fault should then be acknowledged and the absolute encoder adjusted.
Reaction upon A: NONE
Acknowl. upon A: NONE
F07449 (A) Load gear: Position tracking actual position outside tolerance window
Message value: %1
Drive object: All objects
Reaction: Servo: OFF1 (NONE, OFF2, OFF3)
Acknowledge: IMMEDIATELY
Cause: When switched off, the currently effective motor encoder was moved through a distance greater than was parameterized
in the tolerance window. It is possible that there is no longer any reference between the mechanical system and encoder.
Note:
Only the motor encoder in the currently effective drive data set is monitored here. The actual effective drive data set is
displayed in x = r0051 and the corresponding motor encoder is specified in in p0187[x].
Fault value (r0949, interpret decimal):
Deviation (difference) to the last encoder position in increments of the absolute value after the measuring gear - if one is
being used. The sign designates the traversing direction.
Note:
The deviation (difference) found is also displayed in r2724.
Remedy: Reset the position tracking as follows:
- select encoder commissioning (p0010 = 4).
- reset position tracking, position (p2720.2 = 1).
- deselect encoder commissioning (p0010 = 0).
The fault should then be acknowledged and, if necessary, the absolute encoder adjusted (p2507).
See also: p0010
Reaction upon A: NONE
Acknowl. upon A: NONE
Acknowledge: IMMEDIATELY
Cause: Only for controlled line supply infeed/regenerative feedback units:
The power unit data set was not configured - this means that a data set number was not entered into the drive data set.
Fault value (r0949, interpret decimal):
Drive data set number of p0185.
Remedy: The index of the power unit data set associated with the drive data set should be entered into p0185.
A07504 Drive: Motor data set is not assigned to a drive data set
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: A motor data set is not assigned to a drive object.
All of the existing motor data sets in the drive data sets must be assigned using the MDS number (p0186[0...n]). There
must be at least as many drive data sets as motor data sets.
Alarm value (r2124, interpret decimal):
Number of the motor data set that has not been assigned.
Remedy: In the drive data sets, assign the non-assigned motor data set using the MDS number (p0186[0...n]).
- check whether all of the motor data sets are assigned to drive data sets.
- if required, delete superfluous motor data sets.
- if required, set up new drive data sets and assign to the corresponding motor data sets.
A07514 (N) Drive: Data structure does not correspond to the interface module
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The interface mode "SIMODRIVE 611 universal" was set (p2038 = 1) and the data structure does not correspond to this
mode.
The following settings are possible, depending on the number of data sets:
Number of DDS/MDS (p0180/p0130): p0186
1/1: p0186[0] = 0
2/2: p0186[0] = 0, p0186[1] = 1
4/4: p0186[0] = 0, p0186[1] = 1, p0186[2] = 2, p0186[3] = 3
8/8: p0186[0] = 0, p0186[1] = 1, p0186[2] = 2 ... p0186[7] = 7
16/16: p0186[0] = 0, p0186[1] = 1, p0186[2] = 2 ... p0186[15] = 15
32/32: p0186[0] = 0, p0186[1] = 1, p0186[2] = 2 ... p0186[31] = 31
2/1: p0186[0, 1] = 0
4/2: p0186[0, 1] = 0, p0186[1, 2] = 1
8/4: p0186[0, 1] = 0, p0186[1, 2] = 1, p0186[3, 4] = 2, p0186[5, 6] = 3
16/8: p0186[0, 1] = 0, p0186[1, 2] = 1, p0186[3, 4] = 2 ... p0186[14, 15] = 7
32/16: p0186[0, 1] = 0, p0186[1, 2] = 1, p0186[3, 4] = 2 ... p0186[30, 31] = 15
4/1: p0186[0, 1, 2, 3] = 0
8/2: p0186[0, 1, 2, 3] = 0, p0186[4, 5, 6, 7] = 1
16/4: p0186[0, 1, 2, 3] = 0, p0186[4, 5, 6, 7] = 1, p0186[8, 9, 10, 11] = 2, p0186[12, 13, 14, 15] = 3
32/8: p0186[0, 1, 2, 3] = 0, p0186[4, 5, 6, 7] = 1, p0186[8, 9, 10, 11] = 2 ... p0186[28, 29, 30, 31] = 7
8/1: p0186[0...7] = 0
16/2: p0186[0...7] = 0, p0186[8...15] = 1
32/4: p0186[0...7] = 0, p0186[8...15] = 1, p0186[16...23] = 2, p0186[24...31] = 3
16/1: p0186[0...15] = 0
32/2: p0186[0...15] = 0, p0186[16...31] = 1
32/1: p0186[0...31] = 0
9/2: p0186[0...7] = 0, p0186[8] = 1
10/2: p0186[0...7] = 0, p0186[8, 9] = 1
12/2: p0186[0...7] = 0, p0186[8...11] = 1
Remedy: - check the data structure according to the possible settings mentioned in the cause.
- check the interface mode (p2038).
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: The system has identified that two motor data sets were incorrectly parameterized.
Parameter r0313 (calculated from p0314, p0310, p0311), r0315 and p1982 may only have different values if the motor
data sets are assigned different motors. p0827 is used to assign the motors and/contactors.
It is not possible to toggle between motor data sets.
Fault value (r0949, interpret hexadecimal):
xxxxyyyy:
xxxx: First DDS with assigned MDS, yyyy: Second DDS with assigned MDS
Remedy: Correct the parameterization of the motor data sets.
Cause: The Sensor Module does not support the requested configuration.
For incorrect p0430 (cc = 0), the following applies:
- in p0430 (requested functions), at least 1 bit was set that is not set in r0458 (supported functions) (exception: Bit 19, 28,
29, 30, 31).
- p1982 > 0 (pole position identification requested), but r0458.16 = 0 (pole position identification not supported).
For incorrect p0437 (cc = 1), the following applies:
- in p0437 (requested functions), at least 1 bit was set that is not set in r0459 (supported functions).
Fault value (r0949, interpret hexadecimal):
ddccbbaa hex
aa: encoder data set number
bb: first incorrect bit
cc: incorrect parameter
cc = 0: incorrect parameter is p0430
cc = 1: incorrect parameter is p0437
cc = 2: incorrect parameter is r0459
dd: reserved (always 0)
Remedy: - check the encoder parameterization (p0430, p0437).
- check the pole position identification routine (p1982).
- use the matching encoder evaluation (r0458, r0459).
Reaction upon A: NONE
Acknowl. upon A: NONE
F07561 Drive encoder: Number of multiturn pulses is not to the power of two
Message value: Encoder data set: %1
Drive object: All objects
Reaction: Servo: OFF2 (IASC/DCBRK, NONE, OFF1, OFF3, STOP2)
Acknowledge: IMMEDIATELY (POWER ON)
Cause: The multiturn resolution in p0421 must be to the power of two.
Fault value (r0949, interpret decimal):
The fault value includes the encoder data set number involved.
Remedy: - check the parameterization (p0421, p0404.1, r0458.5).
- upgrade the Sensor Module firmware if necessary
F07562 (A) Drive, encoder: Position tracking, incremental encoder not possible
Message value: Fault cause: %1, component number: %2, encoder data set: %3
Cause: An encoder error was signaled for encoder 1 via the PROFIdrive encoder interface (G1_ZSW.15).
Alarm value (r2124, interpret decimal):
Error code from G1_XIST2, refer to the description regarding r0483.
Note:
This alarm is only output if p0480[0] is not equal to zero.
Encoder control word Gn_STW signal source (p0480[0...2], n = encoder 1, 2, 3)
Encoder status word Gn_ZSW (r0481[0...2], n = encoder 1, 2, 3)
Remedy: Acknowledge the encoder error using the encoder control word (G1_STW.15 = 1).
Reaction upon F: Servo: NONE (OFF1, OFF2, OFF3)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction: NONE
Acknowledge: NONE
Cause: Encoderless operation is active due to a fault (r1407.13 = 1).
Note:
The behavior for faults has been set to ENCODER fault response in p0491.
Remedy: - remove the cause of a possible encoder fault.
- carry out a POWER ON (switch-off/switch-on) for all components.
Acknowledge: IMMEDIATELY
Cause: The power unit parameters cannot be read or no parameters are stored in the power unit.
It is possible that the DRIVE-CLiQ cable between the Control Unit and power unit is interrupted or defective.
Note:
This fault also occurs if an incorrect topology was selected in the commissioning tool and this parameterization is then
downloaded to the Control Unit.
Remedy: - carry out a POWER ON (switch-off/switch-on) for all components.
- check the DRIVE-CLiQ cable between the Control Unit and power unit.
- check the power unit and replace if necessary.
- check the Control Unit, and if required replace it.
- after correcting the topology, the parameters must be again downloaded using the commissioning tool.
Remedy: Connect the original power unit and switch on the Control Unit again (POWER ON) or set p0201 to r0200 and exit
commissioning with p0010 = 0.
For infeeds, the following applies:
Line reactors or line filters must be used that are specified for the new power unit. A line supply and DC link identification
routine (p3410 = 5) must then be carried out. It is not possible to change the power unit without re-commissioning the
system if the type of infeed (A_Infeed, B_Infeed, S_Infeed), the type of construction/design (booksize, chassis) or the
voltage class differ between the old and new power units.
For inverters, the following applies:
If the new power unit is accepted, then if required, the current limit (p0640) can be reduced by a lower maximum current
of the power unit (r0209) (torque limits stay the same).
If not only the power unit is changed, but also the motor, then the motor must be re-commissioned (e.g. using p0010 = 1).
This is also necessary if motor data is still to be downloaded via DRIVE-CLiQ.
If the comparison stage in p9906 is set to 2, 3, then commissioning can be exited (p0010 = 0) and the fault acknowledged.
F07890 Internal voltage protection / internal armature short-circuit with STO active
Message value: -
Drive object: All objects
Reaction: OFF2
Acknowledge: IMMEDIATELY
Cause: The internal armature short-circuit (p1231 = 4) is not possible as Safe Torque Off (STO) is enabled. The pulses cannot be
enabled.
Remedy: Switch out the internal armature short-circuit (p1231=0) or deactivate Safe Torque Off (p9501 = p9561 = 0).
Note:
STO: Safe Torque Off / SH: Safe standstill
Cause: The absolute value of the speed difference from the two setpoints (p2151, p2154) and the speed actual value (r2169)
exceeds the tolerance threshold (p2163) longer than tolerated (p2164, p2166).
The alarm is only enabled for p2149.0 = 1.
Possible causes could be:
- the load torque is greater than the torque setpoint.
- when accelerating, the torque/current/power limit is reached. If the limits are not sufficient, then it is possible that the
drive has been dimensioned too small.
- for closed-loop torque control, the speed setpoint does not track the speed actual value.
- for active Vdc controller.
For U/f control, the overload condition is detected as the Imax controller is active.
Remedy: - increase p2163 and/or p2166.
- increase the torque/current/power limits.
- for closed-loop torque control: The speed setpoint should track the speed actual value.
- deactivate alarm with p2149.0 = 0.
F07904 (N, A) External armature short-circuit: Contactor feedback signal "Closed" missing
Message value: -
Drive object: All objects
Reaction: OFF2 (NONE)
Acknowledge: IMMEDIATELY
Cause: When closing, the contactor feedback signal (p1235) did not issue the signal "Closed" (r1239.1 = 1) within the monitoring
time (p1236).
Remedy: - check that the contactor feedback signal is correctly connected (p1235).
- check the logic of the contactor feedback signal (r1239.1 = 1: "Closed", r1239.1 = 0: "Open").
- increase the monitoring time (p1236).
- if required, set the external armature short-circuit without contactor feedback signal (p1231 = 2).
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F07905 (N, A) External armature short-circuit: Contactor feedback signal "Open" missing
Message value: -
Drive object: All objects
Reaction: OFF2 (NONE)
Acknowledge: IMMEDIATELY
Cause: When opening, the contactor feedback signal (p1235) did not issue the signal "Open" (r1239.1 = 0) within the monitoring
time (p1236).
Remedy: - check that the contactor feedback signal is correctly connected (p1235).
- check the logic of the contactor feedback signal (r1239.1 = 1: "Closed", r1239.1 = 0: "Open").
- increase the monitoring time (p1236).
- if required, set the external armature short-circuit without contactor feedback signal (p1231 = 2).
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Reaction: OFF2
Acknowledge: IMMEDIATELY
Cause: The armature short-circuit is incorrectly parameterized.
Fault value (r0949, interpret decimal):
zzzzyyxx: zzzz = fault cause, xx = motor data set
zzzz = 0001 hex = 1 dec:
A permanent-magnet synchronous motor has not been selected.
zzzz = 0002 hex = 2 dec:
No induction motor selected.
zzzz = 0065 hex = 101 dec:
External armature short-circuit: Output (r1239.0) not wired.
zzzz = 0066 hex = 102 dec:
External armature short-circuit with contactor feedback signal: No feedback signal connected (BI:p1235). The feedback
signal must be interconnected in all command data sets (CDS).
zzzz = 0067 hex = 103 dec:
External armature short-circuit without contactor feedback signal: Wait time when opening (p1237) is 0.
zzzz = 00C9 hex = 201 dec:
Internal voltage protection: The maximum output current of the Motor Module (r0209) is less than 1.8 x motor short-circuit
current (r0331).
zzzz = 00CA hex = 202 dec:
Internal voltage protection: A Motor Module in booksize or chassis format is not being used.
zzzz = 00CB hex = 203 dec:
Internal voltage protection: The motor short-circuit current (p0320) is greater than the maximum motor current (p0323).
zzzz = 00CC hex = 204 dec:
Internal voltage protection: The activation (p1231 = 4) is not given for all motor data sets with synchronous motors (p0300
= 2xx, 4xx).
Remedy: For fault value = 1:
- an armature short-circuit / voltage protection is only permissible for permanent-magnetic synchronous motors. The highest
position of the motor type in p0300 must either be 2 or 4.
For fault value = 101:
- the contactor for the external armature short-circuit configuration should be controlled using output signal r1239.0. For
instance, the signal can be connected to an output terminal via binector input p0738. Before this fault can be acknowledged,
p1231 must be set again.
For fault value = 102:
- if the external armature short circuit is selected with contactor feedback signal (p1231 = 1), then the feedback signal must
be connected to an input terminal (e.g. r0722.x) and then interconnected to binector input p1235.
- alternatively, the external armature short-circuit without contactor feedback signal (p1231 = 2) can be selected.
For fault value = 103:
- if the external armature short-circuit without contactor feedback signal (p1231 = 2) is selected, then a delay time must
be parameterized in p1237. This time must always be greater than the actual contactor opening time, as otherwise the
Motor Module would be short-circuited!
For fault value = 201:
- a Motor Module with a higher maximum current or a motor with a lower short-circuit current must be used. The maximum
Motor Module current must be higher than 1.8 x short-circuit current of the motor.
For fault value = 202:
- for internal voltage protection, use a Motor Module in booksize or chassis format.
For fault value = 203:
- for internal voltage protection, only use short-circuit proof motors.
For fault value = 204:
- the internal voltage protection must either be activated for all motor data sets with synchronous motors (p0300 = 2xx,
4xx) (p1231 = 3) or it must be deactivated for all motor data sets (p1231 not equal to 3). This therefore ensures that the
protection cannot be accidentally withdrawn as a result of a data set changeover. The fault can only be acknowledged if
this condition is fulfilled.
F07907 Internal armature short-circuit: Motor terminals are not at zero potential after pulse suppression
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: The function "Internal voltage protection" (p1231 = 3) was activated.
The following must be observed:
- when the internal voltage protection is active, after pulse suppression, all of the motor terminals are at half of the DC link
voltage (without an internal voltage protection, the motor terminals are at zero potential)!
- it is only permissible to use motors that are short-circuit proof (p0320 < p0323).
- the Motor Module must be able to continually conduct 180% short-circuit current (r0331) of the motor (r0289).
- the internal voltage protection cannot be interrupted due to a fault response. If an overcurrent condition occurs during
the active, internal voltage protection, then this can destroy the Motor Module and/or the motor.
- if the Motor Module does not support the autonomous, internal voltage protection (r0192.10 = 0), in order to ensure safe,
reliable functioning when the line supply fails, an external 24 V power supply (UPS) must be used for the components.
- if the Motor Module does support the autonomous, internal voltage protection (r0192.10 = 1), in order to ensure safe,
reliable functioning when the line supply fails, the 24 V power supply for the components must be provided through a
Control Supply Module.
- if the internal voltage protection is active, it is not permissible that the motor is driven by the load for a longer period of
time (e.g. as a result of loads that move the motor or another coupled motor).
Remedy: Not necessary.
This a note for the user.
Cause: KTY84/PT1000:
The motor temperature has exceeded the alarm threshold (p0604, p0616).
PTC:
The response threshold of 1650 Ohm was exceeded.
Alarm value (r2124, interpret decimal):
this is the number of the temperature channel leading to the message.
Remedy: - check the motor load.
- check the motor ambient temperature and cooling.
- check PTC or bimetallic NC contact.
- check the monitoring limits (p0604, p0605).
- activate/check the parameters of the motor temperature model (p0612, p0626 and following).
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: The drive-integrated "Safety Integrated" function in monitoring channel 2 has detected a brake control error and initiated
a STOP A.
- OCC cable shield is not correctly connected.
- defect in the brake control circuit of the drive.
Fault value (r0949, interpret decimal):
10, 11:
Fault in "open holding brake" operation.
- brake not closed or interrupted cable.
- ground fault in brake cable.
20:
Fault in "brake open" state.
- short-circuit in brake winding.
30, 31:
Fault in "close holding brake" operation.
- brake not closed or interrupted cable.
- short-circuit in brake winding.
40:
Fault in "brake closed" state.
50:
Fault in the brake control of the drive or a communication error (brake control diagnostics).
Remedy: - select STO and then de-select again.
- check the motor holding brake connection.
- check the function of the motor holding brake.
- carry out a diagnostics routine for the faults involved.
- check for EMC-compliant control cabinet design and cable routing (e.g. shield OCC cable with shield terminal and shield
plate, check the connection of the brake conductors).
- replace drive.
Note:
OCC: One Cable Connection (one cable system)
SBC: Safe Brake Control
SI: Safety Integrated
STO: Safe Torque Off
See also: p1215
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: - the motor parameters were incorrectly entered while commissioning (e.g. p0300 = 0, no motor)
- the braking resistor has still not been parameterized - commissioning cannot be completed.
Fault value (r0949, interpret decimal):
Parameter number involved.
300 (CU250S-2):
For this control mode, the motor type is not supported.
307:
The following motor parameters could be incorrect:
p0304, p0305, p0307, p0308, p0309
See also: p0304, r0304, p0305, r0305, p0307, r0307, p0311, r0311, p0322, r0322, p0323, r0323
Remedy: Compare the motor data with the rating plate data and if required, correct.
For fault value = 300 (CU250S-2):
Operate a motor type supported by the selected control mode.
Reaction upon A: NONE
Acknowl. upon A: NONE
F07956 (A) Drive: Motor code does not match the list (catalog) motor
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: The motor code of the connected motor with DRIVE-CLiQ does not match the possible list motor types (see selection in
p0300).
The connected motor with DRIVE-CLiQ might not be supported by this firmware version.
Fault value (r0949, interpret decimal):
Motor code of the connected motor with DRIVE-CLiQ.
Note:
The first three digits of the motor code generally correspond to the list motor type.
Remedy: Use a motor with DRIVE-CLiQ and the matching motor code.
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: The conditions to record the friction characteristic are not fulfilled.
Fault value (r0949, interpret decimal):
0046: Missing enable signals (r0046).
1082: The highest speed value to be approached (p3829) is greater than the maximum speed (p1082).
1084: The highest speed value to be approached (p3829) is greater than the maximum speed (r1084, p1083, p1085).
1087: The highest speed value to be approached (p3829) is greater than the maximum speed (r1087, p1086, p1088).
1110: Friction characteristic record, negative direction selected (p3845) and negative direction inhibited (p1110).
1111: Friction characteristic record, positive direction selected (p3845) and positive direction inhibited (p1111).
1198: Friction characteristic record selected (p3845 > 0) and negative (p1110) and positive directions (p1111) inhibited
(r1198).
1300: The control mode (p1300) has not been set to closed-loop speed control.
1755: For encoderless closed-loop control (p1300 = 20), the lowest speed value to be approached (p3820) is less than or
equal to the changeover speed, open-loop controlled operation (p1755).
1910: Motor data identification activated.
1960: Speed controller optimization activated.
3820 ... 3829: speed (p382x) cannot be approached.
3840: Friction characteristic incorrect.
3845: Friction characteristic record de-selected.
Remedy: Fulfill the conditions to record the friction characteristic.
For fault value = 0046:
- establish missing enable signals.
For fault value = 1082, 1084, 1087:
- Select the highest speed value to be approached (p3829) less than or equal to the maximum speed (p1082, r1084, r1087).
- Re-calculate the speed points along the friction characteristic (p0340 = 5).
For fault value = 1110:
- Select the friction characteristic record, positive direction (p3845).
For fault value = 1111:
- Select the friction characteristic record, negative direction (p3845).
For fault value = 1198:
- Enable the permitted direction (p1110, p1111, r1198).
For fault value = 1300:
- set the control mode (p1300) on the closed-loop speed control (p1300 = 20, 21).
For fault value = 1755:
- For encoderless closed-loop speed control (p1300 = 20) select the lowest speed value to be approached (p3820) greater
than the changeover speed of open-loop controlled operation (p1755).
- Re-calculate the speed points along the friction characteristic (p0340 = 5).
For fault value = 1910:
- Exit the motor data identification routine (p1910).
For fault value = 1960:
- Exit the speed controller optimization routine (p1960).
For fault value 3820 ... 3829:
- check the load at speed p382x.
- check the speed signal (r0063) for oscillation at speed p382x. Check the settings of the speed controller if applicable.
For fault value = 3840:
- Make the friction characteristic error-free (p3820 ... p3829, p3830 ... p3839, p3840).
For fault value = 3845:
- Activate the friction characteristic record (p3845).
Acknowledge: NONE
Cause: The angular commutation offset (p0431) was re-defined and has still not been saved.
In order to permanently accept the new value, it must be saved in a non-volatile fashion (p0971, p0977).
Remedy: Not necessary.
This alarm is automatically withdrawn after the data has been saved.
See also: p0977
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction: NONE
Acknowledge: NONE
Cause: The rotating measurement is activated. For the rotating measurement, the motor can accelerate up to the maximum speed
and with maximum torque. Only the parameterized current limit (p0640) and the maximum speed (p1082) are effective.
The behavior of the motor can be influenced using the direction inhibit (p1959.14, p1959.15) and the ramp-up/ramp-down
time (p1958).
The rotating measurement is carried out at the next switch-on command.
Remedy: Not necessary.
The alarm is automatically withdrawn after the rotating measurement has been successfully completed or for the setting
p1960 = 0.
Note:
If a POWER ON or a warm restart is performed with motor data identification selected, the motor data identification request
will be lost. If motor data identification is required, it will need to be selected again manually following ramp-up.
F07993 Drive: Incorrect direction of rotation of the field or encoder actual value inversion
Message value: -
Drive object: All objects
Reaction: OFF2 (NONE)
Acknowledge: IMMEDIATELY
Cause: Either the direction of the rotating field or the encoder actual value has an incorrect sign. The motor data identification
automatically changed the actual value inversion (p0410) in order to correct the control sense. This can result in a direction
of rotation change.
Note:
To acknowledge this fault, the correctness of the direction of rotation must first be acknowledged with p1910 = -2.
Remedy: Check the direction of rotation (also for the position controller, if one is being used).
If the direction of rotation is correct, the following applies:
No additional measures are required (except set p1910 = -2 and acknowledge fault).
If the direction of rotation is incorrect, the following applies:
To change the direction of rotation, two phases must be interchanged and the motor identification routine must be repeated.
F30017 Power unit: Hardware current limit has responded too often
Message value: Fault cause: %1 bin
Drive object: All objects
Reaction: OFF2
Acknowledge: IMMEDIATELY
Cause: The hardware current limitation in the relevant phase (see A30031, A30032, A30033) has responded too often. The number
of times the limit has been exceeded depends on the design and type of power unit.
For infeed units, the following applies:
- closed-loop control is incorrectly parameterized.
- load on the infeed is too high.
- Voltage Sensing Module incorrectly connected.
- line reactor missing or the incorrect type.
- power unit defective.
The following applies to Motor Modules:
- closed-loop control is incorrectly parameterized.
- fault in the motor or in the power cables.
- the power cables exceed the maximum permissible length.
- motor load too high
- power unit defective.
Fault value (r0949, interpret binary):
Bit 3: phase U
Bit 4: phase V
Bit 5: phase W
Additional bits:
Only for internal Siemens troubleshooting.
Note:
Fault value = 0 means that the phase with current limiting is not recognized (e.g. for blocksize device).
Acknowledge: IMMEDIATELY
Cause: The power has detected a ground fault.
Possible causes:
- ground fault in the power cables.
- ground fault at the motor.
- CT defective.
- when the brake closes, this causes the hardware DC current monitoring to respond.
- short-circuit at the braking resistor.
- the closed-loop circulating current control for devices connected in parallel (r0108.15 = 1) is either too slow or has been
set too fast.
Note:
For power units, a ground fault is also emulated in r3113.5.
Fault value (r0949, interpret decimal):
0:
- the hardware DC current monitoring has responded.
- short-circuit at the braking resistor.
> 0:
Absolute value, total current amplitude [20479 = r0209 * 1.4142].
Remedy: - check the power cable connections.
- check the motor.
- check the CT.
- check the cables and contacts of the brake connection (a wire is possibly broken).
- check the braking resistor.
For parallel switching devices (r0108.15 = 1) the following additionally applies:
- check the ground fault monitoring thresholds (p0287).
- check the setting of the closed-loop circulating current control (p7036, p7037).
Cause: The power unit DC link was not able to be precharged within the expected time.
1) There is no line supply voltage connected.
2) The line contactor/line side switch has not been closed.
3) The line supply voltage is too low.
4) Line supply voltage incorrectly set (p0210).
5) The precharging resistors are overheated as there were too many precharging operations per time unit.
6) The precharging resistors are overheated as the DC link capacitance is too high.
7) The precharging resistors are overheated because when there is no "ready for operation" (r0863.0) of the infeed unit,
power is taken from the DC link.
8) The precharging resistors are overheated as the line contactor was closed during the DC link fast discharge through
the Braking Module.
9) The DC link has either a ground fault or a short-circuit.
10) The precharging circuit is possibly defective (only for chassis units).
11) Infeed is defective and/or fuse has ruptured in the Motor Module (only Booksize units).
Fault value (r0949, interpret binary):
yyyyxxxx hex:
yyyy = power unit state
0: Fault status (wait for OFF and fault acknowledgment).
1: Restart inhibit (wait for OFF).
2: Overvoltage condition detected -> change into the fault state.
3: Undervoltage condition detected -> change into the fault state.
4: Wait for bridging contactor to open -> change into the fault state.
5: Wait for bridging contactor to open -> change into restart inhibit.
6: Wait for bypass contactor to open
7: Commissioning.
8: Ready for precharging.
9: Precharging started, DC link voltage lower than the minimum switch-on voltage
10: Precharging, DC link voltage end of precharging still not detected
11: Wait for the end of the de-bounce time of the main contactor after precharging has been completed.
12: Precharging completed, ready for pulse enable.
13: It was detected that the STO terminal was energized at the power unit
xxxx = Missing internal enable signals, power unit (inverted bit-coded, FFFF hex -> all internal enable signals available)
Bit 0: Power supply of the IGBT gating shut down.
Bit 1: Ground fault detected.
Bit 2: Peak current intervention.
Bit 3: I2t exceeded.
Bit 4. Thermal model overtemperature calculated.
Bit 5: (heat sink, gating module, power unit) overtemperature measured.
Bit 6: Reserved.
Bit 7: Overvoltage detected.
Bit 8: Power unit has completed precharging, ready for pulse enable.
Bit 9: STO terminal missing.
Bit 10: Overcurrent detected.
Bit 11: Armature short-circuit active.
Bit 12: DRIVE-CLiQ fault active.
Bit 13: Vce fault detected, transistor de-saturated due to overcurrent/short-circuit.
Bit 14: Undervoltage detected.
See also: p0210
Remedy: In general:
- check the line supply voltage at the input terminals.
- check the line supply voltage setting (p0210).
For booksize drive units, the following applies:
- wait (approx. 8 minutes) until the precharging resistors have cooled down. For this purpose, preferably disconnect the
infeed unit from the line supply.
For 5):
- carefully observe the permissible precharging frequency (refer to the appropriate Equipment Manual).
For 6):
- check the total capacitance of the DC link and reduce in accordance with the maximum permissible DC link capacitance
if necessary (refer to the appropriate Equipment Manual)
For 7):
- interconnect the ready-for-operation signal from the infeed unit (r0863.0) in the enable logic of the drives connected to
this DC link
For 8):
- check the connections of the external line contactor. The line contactor must be open during DC link fast discharge.
For 9):
- check the DC link for ground faults or short circuits.
For 11):
- check the DC link voltage of the infeed (r0070) and Motor Modules (r0070).
If the DC link voltage generated by the infeed (or external) is not displayed for the Motor Modules (r0070), then a fuse has
ruptured in the Motor Module.
See also: p0210
Cause: Hardware current limit for phase U responded. The pulsing in this phase is inhibited for one pulse period.
- closed-loop control is incorrectly parameterized.
- fault in the motor or in the power cables.
- the power cables exceed the maximum permissible length.
- motor load too high
- power unit defective.
Note:
Alarm A30031 is always output if, for a Power Module, the hardware current limiting of phase U, V or W responds.
Remedy: - check the motor data and if required, recalculate the control parameters (p0340 = 3). As an alternative, run a motor data
identification (p1910 = 1, p1960 = 1).
- check the motor circuit configuration (star/delta).
- check the motor load.
- check the power cable connections.
- check the power cables for short-circuit or ground fault.
- check the length of the power cables.
Remedy: - check the motor data and if required, recalculate the control parameters (p0340 = 3). As an alternative, run a motor data
identification (p1910 = 1, p1960 = 1).
- check the motor circuit configuration (star/delta).
- check the motor load.
- check the power cable connections.
- check the power cables for short-circuit or ground fault.
- check the length of the power cables.
Cause: For the power unit power supply, the lower threshold has been violated.
Alarm value (r2124, interpret hexadecimal):
yyxxxx hex: yy = channel, xxxx = voltage [0.1 V]
yy = 0: 24 V power supply
yy = 1: 48 V power supply
Remedy: - check the power supply of the power unit.
- carry out a POWER ON (switch-off/switch-on) for the component.
Reaction upon F: NONE (OFF1, OFF2)
Acknowl. upon F: IMMEDIATELY (POWER ON)
A30042 Power unit: Fan has reached the maximum operating hours
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The maximum operating time of at least one fan will soon be reached, or has already been exceeded.
Alarm value (r2124, interpret binary):
Bit 0 = 1:
The operating hours counter of the heat sink fan will reach the maximum operating time in 500 hours.
Bit 1 = 1:
The wear counter of the heat sink fan has reached 99 %. The remaining service life is 1%.
Bit 2 = 1:
The operating hours counter of the heat sink fan has exceeded the maximum operating time - and/or the wear counter
has exceeded 100%.
Bit 8 = 1:
The operating hours counter of the fan inside the device will reach the maximum operating time in 500 hours.
Bit 10 = 1:
The operating hours counter of the fan inside the device has exceeded the maximum operating time.
Remedy: For the fan involved, carry out the following:
- replace the fan.
- reset the operating hours counter (p0251, p0254).
Cause: For the power unit power supply, the upper threshold has been violated.
Alarm value (r2124, interpret hexadecimal):
yyxxxx hex: yy = channel, xxxx = voltage [0.1 V]
yy = 0: 24 V power supply
yy = 1: 48 V power supply
Remedy: Check the power supply of the power unit.
Reaction upon F: NONE (OFF1, OFF2, OFF3)
Acknowl. upon F: IMMEDIATELY (POWER ON)
Cause: Frequencies have been detected on the DC link voltage that would suggest line asymmetry or failure of a line phase.
It is also possible that a motor phase has failed.
Fault F30011 is output if the alarm is present and at the latest after 5 minutes.
The precise duration depends on the power unit type and the particular frequencies. For booksize and chassis power units,
the duration also depends on how long the alarm has been active.
Alarm value (r2124, interpret decimal):
Only for internal Siemens troubleshooting.
Remedy: - check the line phase connection.
- check the motor feeder cable connections.
If there is no phase failure of the line or motor, then line asymmetry is involved.
- reduce the power in order to avoid fault F30011.
Cause: A feedback signal for the precharging contactor (ALM, SLM, BLM diode) or the line contactor (BLM thyristor) interconnected
and the monitoring activated.
After switching-in/switching-out the contactor, a correct feedback signal was not received within the monitoring time set in
p0255[0, 2].
Fault value (r0949, interpret binary):
Bit 0: The time set in p0255[0, 2] was exceeded when switching-in/switching-out the contactor.
Bit 1: The precharging contactor was opened while precharging or in the infeed mode (BLM thyristor).
Bit 2: The precharging contactor was switched-in in the OFF state or during infeed operation.
Remedy: - check the monitoring time setting (p0255[0, 2]).
- check the contactor wiring and activation.
- replace the contactor.
Reaction upon A: NONE
Acknowl. upon A: NONE
Acknowledge: IMMEDIATELY
Cause: The following applies for CU31x and CUA31:
More than one setpoint telegram was not able to be transferred to the power unit module.
Remedy: The following applies for CU31x and CUA31:
Check the interface (adjustment and locking) to the power unit module.
F30074 (A) Communication error between the Control Unit and Power Module
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: IMMEDIATELY
Cause: Communications between the Control Unit (CU) and Power Module (PM) via the interface no longer possible. The CU may
have been withdrawn or is incorrectly inserted.
Fault value (r0949, interpret hexadecimal):
0 hex:
- a Control Unit with external 24 V supply was withdrawn from the Power Module during operation.
- with the Power Module switched off, the external 24 V supply for the Control Unit was interrupted for some time.
1 hex:
The Control Unit was withdrawn from the Power Module during operation, although the encoderless safe motion monitoring
functions are enabled. This is not supported. After re-inserting the Control Unit in operation, communications to the Power
Module no longer possible.
20A hex:
The Control Unit was inserted on a Power Module, which has another code number.
20B hex:
The Control Unit was inserted on a Power Module, which although it has the same code number, has a different serial
number.
601 hex:
The Control Unit was inserted on a Power Module, whose power/performance class (chassis unit) is not supported.
Remedy: Reinsert the Control Unit (CU) or the Control Unit Adapter (CUAxx) onto the original Power Module and continue operation.
If required, carry out a POWER ON for the CU and/or the CUA.
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: The power unit has detected an excessive rate of rise in the overvoltage range.
- closed-loop control is incorrectly parameterized.
- motor has a short-circuit or fault to ground (frame).
- U/f operation: Up ramp set too low.
- U/f operation: rated current of motor much greater than that of power unit.
- infeed: High discharge and post-charging currents for voltage dip.
- infeed: High post-charging currents for overload when motoring and DC link voltage dip.
- infeed: Short-circuit currents at switch-on due to the missing line reactor.
- power cables are not correctly connected.
- power cables exceed the maximum permissible length.
- power unit defective.
Additional causes for a parallel switching device (r0108.15 = 1):
- a power unit has tripped (switched off) due to a ground fault.
- the closed-loop circulating current control is either too slow or has been set too fast.
Fault value (r0949, interpret bitwise binary):
Bit 0: Phase U.
Bit 1: Phase V.
Bit 2: Phase W.
Remedy: - check the motor data - if required, carry out commissioning.
- check the motor circuit configuration (star-delta)
- U/f operation: Increase up ramp.
- U/f operation: Check assignment of rated currents of motor and power unit.
- infeed: Check the line supply quality.
- infeed: Reduce the motor load.
- infeed: Correct connection of the line reactor.
- check the power cable connections.
- check the power cables for short-circuit or ground fault.
- check the length of the power cables.
- replace power unit.
For a parallel switching device (r0108.15 = 1) the following additionally applies:
- check the ground fault monitoring thresholds (p0287).
- check the setting of the closed-loop circulating current control (p7036, p7037).
Cause: The power unit has executed too many switching operations for current limitation.
- closed-loop control is incorrectly parameterized.
- motor has a short-circuit or fault to ground (frame).
- U/f operation: Up ramp set too low.
- U/f operation: rated current of motor much greater than that of power unit.
- infeed: High discharge and post-charging currents for voltage dip.
- infeed: High post-charging currents for overload when motoring and DC link voltage dip.
- infeed: Short-circuit currents at switch-on due to the missing line reactor.
- power cables are not correctly connected.
- power cables exceed the maximum permissible length.
- power unit defective.
Additional causes for a parallel switching device (r0108.15 = 1):
- a power unit has tripped (switched off) due to a ground fault.
- the closed-loop circulating current control is either too slow or has been set too fast.
Fault value (r0949, interpret bitwise binary):
Bit 0: Phase U.
Bit 1: Phase V.
Bit 2: Phase W.
Remedy: - check the motor data - if required, carry out commissioning.
- check the motor circuit configuration (star-delta)
- U/f operation: Increase up ramp.
- U/f operation: Check assignment of rated currents of motor and power unit.
- infeed: Check the line supply quality.
- infeed: Reduce the motor load.
- infeed: Correct connection of the line reactor.
- check the power cable connections.
- check the power cables for short-circuit or ground fault.
- check the length of the power cables.
- replace power unit.
For a parallel switching device (r0108.15 = 1) the following additionally applies:
- check the ground fault monitoring thresholds (p0287).
- check the setting of the closed-loop circulating current control (p7036, p7037).
Cause: The drive-integrated "Safety Integrated" function in monitoring channel 2 has detected a brake control error and initiated
a STOP A.
- OCC cable shield is not correctly connected.
- defect in the brake control circuit of the drive.
Fault value (r0949, decimal interpretation):
100, 101, 102:
Fault in "open brake" operation.
- brake not closed or interrupted cable.
- ground fault in brake cable.
300, 301, 302:
Fault in "close brake" operation.
- brake not closed or interrupted cable.
200:
Fault in the "Brake open" state.
- short-circuit in brake winding.
201, 202:
Fault in the "Brake open" state.
- defective hardware.
400, 401, 402:
Fault in "brake closed" state.
60, 70:
Fault in the brake control of the drive or a communication error between the monitoring channels (brake control diagnostics).
Remedy: - select STO and then de-select again.
- check the motor holding brake connection.
- check the function of the motor holding brake.
- carry out a diagnostics routine for the faults involved.
- check for EMC-compliant control cabinet design and cable routing (e.g. shield OCC cable with shield terminal and shield
plate, check the connection of the brake conductors).
- replace drive.
Note:
OCC: One Cable Connection (one cable system)
SBC: Safe Brake Control
SI: Safety Integrated
STO: Safe Torque Off
A30640 (F) SI P2: Fault in the switch-off signal path of the second channel
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The Motor Module has detected a communication error with the higher-level control or the TM54F to transfer the safety-
relevant information or there is a communication error between Motor Modules connected in parallel.
Note:
This fault results in a STOP A that can be acknowledged.
Alarm value (r2124, interpret decimal):
Only for internal Siemens troubleshooting.
Remedy: For the higher-level control, the following applies:
- check the PROFIsafe address in the higher-level control and Motor Modules and if required, align.
- save all parameters (p0977 = 1).
- carry out a POWER ON (switch-off/switch-on) for all components.
For TM54F, carry out the following steps:
- start the copy function for the node identifier (p9700 = 1D hex).
- acknowledge hardware CRC (p9701 = EC hex).
- save all parameters (p0977 = 1).
- carry out a POWER ON (switch-off/switch-on) for all components.
For a parallel connection, the following applies:
- check the PROFIsafe address in both monitoring channels and if required, align.
- save all parameters (p0977 = 1).
- carry out a POWER ON (switch-off/switch-on) for all components.
The following generally applies:
- upgrade the Motor Module software.
Note:
MM: Motor Module
SI: Safety Integrated
Reaction upon F: NONE (OFF2)
Acknowl. upon F: IMMEDIATELY (POWER ON)
Cause: The "Safety Integrated" function on monitoring channel 2 requires an acceptance test.
Note:
This fault results in a STOP A that can be acknowledged.
Fault value (r0949, interpret decimal):
130: Safety parameters for monitoring channel 2 not available.
Note:
This fault value is always output when Safety Integrated is commissioned for the first time.
1000: Reference and actual checksum in monitoring channel 2 are not identical (booting).
- safety parameters set offline and loaded to the drive.
- at least one checksum-checked piece of data is defective.
2000: Reference and actual checksum in monitoring channel 2 are not identical (commissioning mode).
2003: Acceptance test is required as a safety parameter has been changed.
2005: The safety logbook has identified that the safety checksums have changed. An acceptance test is required.
3003: Acceptance test is required as a hardware-related safety parameter has been changed.
9999: Subsequent response of another safety-related fault that occurred when booting that requires an acceptance test.
Remedy: For fault value = 130:
- carry out safety commissioning routine.
For fault value = 1000:
- again carry out safety commissioning routine.
- replace the memory card or drive.
For fault value = 2000:
- confirm the data change using the commissioning tool
For fault value = 2003, 2005:
- carry out an acceptance test and generate an acceptance report.
The procedure when carrying out an acceptance test as well as an example of the acceptance report are provided in the
following literature:
SINAMICS Function Manual Safety Integrated
For fault value = 3003:
- carry out the function checks for the modified hardware and generate an acceptance report.
The procedure when carrying out an acceptance test as well as an example of the acceptance report are provided in the
following literature:
SINAMICS Function Manual Safety Integrated
For fault value = 9999:
- carry out diagnostics for the other safety-related fault that is present.
Note:
SI: Safety Integrated
A30666 (F) SI Motion P2: Steady-state (static) 1 signal at the F-DI for safe acknowledgment
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: A logical 1 signal is present at the F-DI configured in p10106 for more than 10 seconds.
If, at the F-DI no acknowledgment was performed for safe acknowledgment, then a steady-state logical and 0 signal must
be present. This avoids unintentional safety-relevant acknowledgment (or the "Internal Event Acknowledge" signal) if a
wire breaks or one of the two digital inputs bounces.
Remedy: Set the fail-safe digital input (F-DI) to a logical 0 signal (p10106).
Note:
F-DI: Fail-safe Digital Input
Reaction upon F: NONE
Acknowl. upon F: IMMEDIATELY
Remedy: - check whether there are faults in the safety function alignment between the two monitoring channels (F01655, F30655)
and if required, carry out diagnostics for the faults involved.
- use a Control Unit that supports the safe motion monitoring function.
- upgrade the Control Unit software.
Note:
SI: Safety Integrated
Cause: The monitoring function enabled in p9501, p9601, p9506, p9507 is not supported in this firmware version.
Note:
This message does not result in a safety stop response.
Fault value (r0949, decimal interpretation):
1: Monitoring function SLP not supported (p9501.1).
2: Monitoring function SCA not supported (p9501.7 and p9501.8..15).
3: Monitoring function SLS override not supported (p9501.5).
4: Monitoring function external ESR activation not supported (p9501.4).
5: Monitoring function F-DI in PROFIsafe not supported (p9501.30).
6: Enable actual value synchronization not supported (p9501.3).
9: Monitoring function not supported by the firmware or enable bit not used.
12: This drive does not support operation of safety functions with a higher-level control.
26: Hysteresis and filtering for SSM monitoring function without an encoder not supported (p9501.16).
27: This hardware does not support onboard F-DI and F-DO.
30: The firmware version of the Motor Module is older than the version of the Control Unit.
33: Safety functions without selection not supported (p9601.5).
34: This module does not support safe position via PROFIsafe.
39: This module or software version of the CU/MM does not support safe gearbox stage switchover (p9501.26).
44: This module/this software version does not support referencing via the safety control channel (p9501.27).
45: Deactivating SOS/SLS during an external STOP A is not supported (p9501.23).
54: SCA function not supported (p9501.28).
Remedy: - de-select the monitoring function involved (p9501, p9601, p9507, p9506).
- Upgrade the Motor Module firmware.
Note:
ESR: Extended Stop and Retract
F-DI: Fail-safe Digital Input
SBR: Safe Brake Ramp (safe brake ramp monitoring)
SCA: Safe Cam
SDI: Safe Direction (safe motion direction)
SI: Safety Integrated
SLP: Safely Limited Position
SLS: Safely Limited Speed
SP: Safe Position
SS1E: Safe Stop 1 External (Safe Stop 1 with external stop)
SS2E: Safe Stop 2 external (Safe Stop 2 with external stop, external STOP D)
See also: p9501, p9601
F30685 SI Motion P2: Safely Limited Speed limit value too high
Message value: %1
Drive object: All objects
Reaction: OFF2
Acknowledge: IMMEDIATELY (POWER ON)
Cause: The limit value for the function "Safely Limited Speed" (SLS) is greater than the speed that corresponds to an encoder
limit frequency of 500 kHz.
Note:
This message does not result in a safety stop response.
Fault value (r0949, interpret decimal):
Maximum permissible speed.
Remedy: Correct the limit values for SLS and carry out a POWER ON.
Note:
SI: Safety Integrated
SLS: Safely Limited Speed
Cause: At least one enabled "Safety Cam" (SCA) is parameterized in p9336 or p9337 too close to the tolerance range around the
modulo position.
- the minus position value of a cam must be greater than the lower modulo limit + cam tolerance (p9340) + position tolerance
(p9342).
- the plus position value of a cam must be less than the upper modulo limit - cam tolerance (p9340) - position tolerance
(p9342).
- when the modulo position is parameterized (p9305 > 0), the lower modulo limit = 0, the upper modulo limit = p9305.
- the cam length of cam x = p9336[x] - p9337[x] is less than the cam tolerance + position tolerance (= p9340 + p9342).
This also means that cams of the minus position value must be less than the plus position value.
Note:
This fault does not result in a safety stop response.
Fault value (r0949, interpret decimal):
Number of the "Safe Cam" with an illegal position.
See also: p9501
Remedy: Correct the cam position and carry out a POWER ON.
Note:
SCA: Safe Cam
SI: Safety Integrated
A30693 (F) SI P2: Safety parameter settings changed, warm restart/POWER ON required
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: Safety parameters have been changed; these will only take effect following a warm restart or POWER ON.
Alarm value (r2124, interpret decimal):
Parameter number of the safety parameter which has changed, necessitating a warm restart or POWER ON.
Remedy: - carry out a warm restart.
- carry out a POWER ON (switch-off/switch-on) for all components.
Note:
Before performing an acceptance test, a POWER ON must be carried out for all components.
Reaction upon F: NONE (OFF1, OFF2, OFF3)
Acknowl. upon F: POWER ON
Remedy: - check whether safety faults are present and if required carry out the appropriate diagnostic routines for the particular
faults.
- check whether the standstill tolerance matches the accuracy and control dynamic performance of the axis.
This message can be acknowledged without a POWER ON as follows (safe acknowledgment):
- PROFIsafe.
- machine control panel.
Note:
SI: Safety Integrated
SOS: Safe Operating Stop
See also: p9530
Cause: When cross-comparing the two monitoring channels, the drive detected a difference between the input data or results of
the monitoring functions and initiated a STOP F. One of the monitoring functions no longer reliably functions - i.e. safe
operation is no longer possible.
If at least one monitoring function is active, then after the parameterized timer has expired, the message C30701 "SI
Motion: STOP B initiated" is output.
The following message values may also occur in the following cases if the cause that is explicitly mentioned does not apply:
- incorrect synchronization.
Message value (r2124, interpret decimal):
0 ... 999:
Number of the cross-compared data that resulted in this message.
The significance of the individual message values is described in safety message C01711.
1000: Watchdog timer has expired. Too many signal changes have occurred at safety-relevant inputs.
1001: Initialization error of watchdog timer.
1005: STO already active for test stop selection.
1011: Acceptance test status between the monitoring channels differ.
1012: Plausibility violation of the actual value from the encoder.
1020: Cyc. communication failure between the monit. channels.
1021: Cyc. communication failure between the monit. channel and Sensor Module.
1023: Error in the effectiveness test in the DRIVE-CLiQ encoder
1030: Encoder fault detected from another monitoring channel.
1045: CRC of the standstill position incorrect.
5000 ... 5140:
PROFIsafe message values.
For these message values, the fail-safe control signals (fail-safe values) are transferred to the safety functions.
The significance of the individual message values is described in safety message C01711.
6000 ... 6166:
PROFIsafe message values (PROFIsafe driver for PROFIBUS DP V1/V2 and PROFINET).
For these message values, the fail-safe control signals (fail-safe values) are transferred to the safety functions. If "Stop B
after failure of the PROFISafe communication" is parameterized, the transfer of the fail-safe value is delayed.
The significance of the individual message values is described in safety fault F01611.
7000 ... 7002:
Message values of the "Safe position via PROFIsafe" function.
See also: p9555, r9725
C30730 SI Motion P2: Reference block for dynamic safely limited speed invalid
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: IMMEDIATELY (POWER ON)
Cause: The reference block transferred via PROFIsafe is negative.
A reference block is used to generate a referred velocity limit value based on the reference quantity "Velocity limit value
SLS1" (p9531[0]).
The drive is stopped as a result of the configured stop response (p9563[0]).
Message value (r2124, interpret decimal):
requested, invalid reference block.
Remedy: In the PROFIsafe telegram, input data S_SLS_LIMIT_IST must be corrected.
This message can be acknowledged without a POWER ON as follows (safe acknowledgment):
- PROFIsafe.
Note:
SI: Safety Integrated
SLS: Safely Limited Speed
A30788 Automatic test stop: wait for STO deselection via SMM
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The automatic test stop was not able to be carried out after powering up.
Possible causes:
- the STO function is selected via Safety Extended Functions.
- a safety message is present, that resulted in a STO.
Remedy: - Deselect STO via Safety Extended Functions.
- remove the cause of the safety messages and acknowledge the messages.
The automatic test stop is performed after removing the cause.
C30798 SI Motion P2: Test stop for motion monitoring functions running
Message value: -
Drive object: All objects
Reaction: NONE
Acknowledge: IMMEDIATELY (POWER ON)
Cause: The forced checking procedure (test stop) for the safe motion monitoring functions is currently in progress.
Remedy: Not necessary.
The message is automatically withdrawn when the test stop has been completed.
Note:
SI: Safety Integrated
Reaction: OFF2
Acknowledge: IMMEDIATELY
Cause: A time slice overflow has occurred.
Fault value (r0949, interpret decimal):
xx: time slice number
Remedy: - carry out a POWER ON (switch-off/switch-on) for all components.
- upgrade firmware to later version.
- contact Technical Support.
Acknowledge: NONE
Cause: When booting it was detected that the cause of the previous reset was an SAC watchdog timer overflow.
Remedy: - carry out a POWER ON (switch-off/switch-on) for all components.
- upgrade firmware to later version.
- contact Technical Support.
Reaction upon F: NONE (OFF2)
Acknowl. upon F: IMMEDIATELY
Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the power unit concerned. The nodes do not
send and receive in synchronism.
Fault cause:
33 (= 21 hex):
The cyclic telegram has not been received.
34 (= 22 hex):
Timeout in the telegram receive list.
64 (= 40 hex):
Timeout in the telegram send list.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON.
- replace the component involved (power unit, Control Unit).
Cause: A DRIVE-CLiQ communication error has occurred from the power unit to the Control Unit involved.
Data were not able to be sent.
Fault cause:
65 (= 41 hex):
Telegram type does not match send list.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: Carry out a POWER ON.
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- check the encoder type (encoder with equidistant zero marks).
- adapt the parameter for the distance between zero marks (p0424, p0425).
- if message output above speed threshold, reduce filter time if necessary (p0438).
- replace the encoder or encoder cable.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F31103 (N, A) Encoder 1: Signal level zero mark (track R) outside tolerance
Message value: R track: %1
Drive object: All objects
Reaction: Servo: ENCODER (IASC/DCBRK, NONE)
Acknowledge: PULSE INHIBIT
Cause: The zero mark signal level (track R) does not lie within the tolerance bandwidth for encoder 1.
The fault can be initiated when the unipolar voltage level is exceeded (RP/RN) or if the differential amplitude is undershot.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex: yyyy = 0, xxxx = Signal level, track R (16 bits with sign)
The response thresholds of the unipolar signal levels of the encoder are between < 1400 mV and > 3500 mV.
The response threshold for the differential signal level of the encoder is < -1600 mV.
A signal level of 500 mV peak value corresponds to the numerical value 5333 hex = 21299 dec.
Note:
The analog value of the amplitude error is not measured at the same time with the hardware fault output by the Sensor
Module.
The fault value can only be represented between -32768 ... 32767 dec (-770 ... 770 mV).
The signal level is not evaluated unless the following conditions are satisfied:
- Sensor Module properties available (r0459.31 = 1).
- monitoring active (p0437.31 = 1).
Remedy: - check the speed range; frequency characteristic (amplitude characteristic) of the measuring equipment might not be
sufficient for the speed range
- check that the encoder cables and shielding are routed in compliance with EMC.
- check the plug connections and contacts of the encoder cable.
- check the encoder type (encoder with zero marks).
- check whether the zero mark is connected and the signal cables RP and RN have been connected correctly (not connected
with the incorrect polarity).
- replace the encoder cable.
- if the coding disk is soiled or the lighting aged, replace the encoder.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: Serial communication protocol transfer error between the encoder and evaluation module.
Fault value (r0949, interpret binary):
Bit 0: Alarm bit in the position protocol.
Bit 1: Incorrect quiescent level on the data line.
Bit 2: Encoder does not respond (does not supply a start bit within 50 ms).
Bit 3: CRC error: The checksum in the protocol from the encoder does not match the data.
Bit 4: Encoder acknowledgment error: The encoder incorrectly understood the task (request) or cannot execute it.
Bit 5: Internal error in the serial driver: An illegal mode command was requested.
Bit 6: Timeout when cyclically reading.
Bit 7: Timeout for the register communication.
Bit 8: Protocol is too long (e.g. > 64 bits).
Bit 9: Receive buffer overflow.
Bit 10: Frame error when reading twice.
Bit 11: Parity error.
Bit 12: Data line signal level error during the monoflop time.
Bit 13: Data line incorrect.
Bit 14: Fault for the register communication.
Bit 15: Internal communication error.
Note:
For an EnDat 2.2 encoder, the significance of the fault value for F3x135 (x = 1, 2, 3) is described.
Remedy: For fault value, bit 0 = 1:
- Enc defect F31111 may provide additional details.
For fault value, bit 1 = 1:
- incorrect encoder type / replace the encoder or encoder cable.
For fault value, bit 2 = 1:
- incorrect encoder type / replace the encoder or encoder cable.
For fault value, bit 3 = 1:
- EMC / connect the cable shield, replace the encoder or encoder cable.
For fault value, bit 4 = 1:
- EMC / connect the cable shield, replace the encoder or encoder cable, replace the Sensor Module.
For fault value, bit 5 = 1:
- EMC / connect the cable shield, replace the encoder or encoder cable, replace the Sensor Module.
For fault value, bit 6 = 1:
- Update Sensor Module firmware.
For fault value, bit 7 = 1:
- incorrect encoder type / replace the encoder or encoder cable.
For fault value, bit 8 = 1:
- check parameterization (p0429.2).
For fault value, bit 9 = 1:
- EMC / connect the cable shield, replace the encoder or encoder cable, replace the Sensor Module.
For fault value, bit 10 = 1:
- check parameterization (p0429.2, p0449).
For fault value, bit 11 = 1:
- check parameterization (p0436).
For fault value, bit 12 = 1:
- check parameterization (p0429.6).
For fault value, bit 13 = 1:
- check data line.
For fault value, bit 14 = 1:
- incorrect encoder type / replace the encoder or encoder cable.
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: The signal level of the rectified encoder signals A and B of the encoder fall below the permissible limit value.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Signal level, track B (16 bits with sign).
xxxx = Signal level, track A (16 bits with sign).
The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %).
The response threshold is < 130 mV.
A signal level of 500 mV peak value corresponds to the numerical value 5333 hex = 21299 dec.
Note:
The analog values of the amplitude error are not measured at the same time with the hardware fault output by the Sensor
Module.
Remedy: - check that the encoder cables and shielding are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F31129 (N, A) Encoder 1: Position difference hall sensor/track C/D and A/B too large
Message value: %1
Drive object: All objects
Reaction: Servo: ENCODER (IASC/DCBRK, NONE)
Acknowledge: PULSE INHIBIT
Cause: The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° electrical or the error for the Hall signals is greater
than +/-60 ° electrical.
One period of track C/D corresponds to 360 ° mechanical.
One period of the Hall signal corresponds to 360 ° electrical.
The monitoring responds if, for example, Hall sensors are connected as equivalent for the C/D tracks with the incorrect
rotational sense or supply values that are not accurate enough.
After the fine synchronization using one reference mark or 2 reference marks for distance-coded encoders, this fault is no
longer initiated, but instead, Alarm A31429.
Fault value (r0949, interpret decimal):
For track C/D, the following applies:
Measured deviation as mechanical angle (16 bits with sign, 182 dec corresponds to 1 °).
For Hall signals, the following applies:
Measured deviation as electrical angle (16 bits with sign, 182 dec corresponds to 1 °).
Remedy: - track C or D not connected.
- correct the direction of rotation of the Hall sensor possibly connected as equivalent for track C/D.
- check that the encoder cables are routed in compliance with EMC.
- check the adjustment of the Hall sensor.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F31130 (N, A) Encoder 1: Zero mark and position error from the coarse synchronization
Message value: Angular deviation, electrical: %1, angle, mechanical: %2
Drive object: All objects
Reaction: Servo: ENCODER (IASC/DCBRK, NONE, OFF1, OFF2, OFF3, STOP2)
Acknowledge: PULSE INHIBIT
Cause: After initializing the pole position using track C/D, Hall signals or pole position identification routine, the zero mark was
detected outside the permissible range. For distance-coded encoders, the test is carried out after passing 2 zero marks.
Fine synchronization was not carried out.
When initializing via track C/D (p0404) then it is checked whether the zero mark occurs in an angular range of +/-18 °
mechanical.
When initializing via Hall sensors (p0404) or pole position identification (p1982) it is checked whether the zero mark occurs
in an angular range of +/-60 ° electrical.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex
yyyy: Determined mechanical zero mark position (can only be used for track C/D).
xxxx: Deviation of the zero mark from the expected position as electrical angle.
Scaling: 32768 dec = 180 °
Remedy: - check p0431 and, if necessary, correct (trigger via p1990 = 1 if necessary).
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- if the Hall sensor is used as an equivalent for track C/D, check the connection.
- check the connection of track C or D.
- replace the encoder or encoder cable.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check whether the coding disk is dirty or there are strong ambient magnetic fields.
- adapt the parameter for the clearance between zero marks (p0425).
- if message output above speed threshold, reduce filter time if necessary (p0438).
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: The encoder has identified a position determination fault (singleturn) and supplies status information bit by bit in an internal
status/fault word.
Some of these bits cause this fault to be triggered. Other bits are status displays. The status/fault word is displayed in the
fault value.
Note regarding the bit designation:
The first designation is valid for DRIVE-CLiQ encoders, the second for EnDat 2.2 encoders.
Fault value (r0949, interpret binary):
Bit 0: F1 (safety status display).
Bit 1: F2 (safety status display).
Bit 2: Reserved (lighting).
Bit 3: Reserved (signal amplitude).
Bit 4: Reserved (position value).
Bit 5: Reserved (overvoltage).
Bit 6: Reserved (undervoltage)/hardware fault EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 7: Reserved (overcurrent)/EnDat encoder withdrawn when not in the parked state (--> F3x110, x = 1, 2, 3).
Bit 8: Reserved (battery)/overcurrent EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 9: Reserved/overvoltage EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 11: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 12: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 13: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 14: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 15: Internal communication error (--> F3x110, x = 1, 2, 3).
Bit 16: Lighting (--> F3x135, x = 1, 2, 3).
Bit 17: Signal amplitude (--> F3x135, x = 1, 2, 3).
Bit 18: Singleturn position 1 (--> F3x135, x = 1, 2, 3).
Bit 19: Overvoltage (--> F3x135, x = 1, 2, 3).
Bit 20: Undervoltage (--> F3x135, x = 1, 2, 3).
Bit 21: Overcurrent (--> F3x135, x = 1, 2, 3).
Bit 22: Temperature exceeded (--> F3x405, x = 1, 2, 3).
Bit 23: Singleturn position 2 (safety status display).
Bit 24: Singleturn system (--> F3x135, x = 1, 2, 3).
Bit 25: Singleturn power down (--> F3x135, x = 1, 2, 3)
Bit 26: Multiturn position 1 (--> F3x136, x = 1, 2, 3).
Bit 27: Multiturn position 2 (--> F3x136, x = 1, 2, 3).
Bit 28: Multiturn system (--> F3x136, x = 1, 2, 3).
Bit 29: Multiturn power down (--> F3x136, x = 1, 2, 3).
Bit 30: Multiturn overflow/underflow (--> F3x136, x = 1, 2, 3).
Bit 31: Multiturn battery (reserved).
Remedy: - determine the detailed cause of the fault using the fault value.
- replace the encoder if necessary.
Note:
An EnDat 2.2 encoder may only be removed and inserted in the "Park" state.
If an EnDat 2.2 encoder was removed when not in the "Park" state, then after inserting the encoder, a POWER ON (switch-
off/switch-on) is necessary to acknowledge the fault.
Cause: The encoder has identified a position determination fault (multiturn) and supplies status information bit by bit in an internal
status/fault word.
Some of these bits cause this fault to be triggered. Other bits are status displays. The status/fault word is displayed in the
fault value.
Note regarding the bit designation:
The first designation is valid for DRIVE-CLiQ encoders, the second for EnDat 2.2 encoders.
Fault value (r0949, interpret binary):
Bit 0: F1 (safety status display).
Bit 1: F2 (safety status display).
Bit 2: Reserved (lighting).
Bit 3: Reserved (signal amplitude).
Bit 4: Reserved (position value).
Bit 5: Reserved (overvoltage).
Bit 6: Reserved (undervoltage)/hardware fault EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 7: Reserved (overcurrent)/EnDat encoder withdrawn when not in the parked state (--> F3x110, x = 1, 2, 3).
Bit 8: Reserved (battery)/overcurrent EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 9: Reserved/overvoltage EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 11: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 12: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 13: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 14: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 15: Internal communication error (--> F3x110, x = 1, 2, 3).
Bit 16: Lighting (--> F3x135, x = 1, 2, 3).
Bit 17: Signal amplitude (--> F3x135, x = 1, 2, 3).
Bit 18: Singleturn position 1 (--> F3x135, x = 1, 2, 3).
Bit 19: Overvoltage (--> F3x135, x = 1, 2, 3).
Bit 20: Undervoltage (--> F3x135, x = 1, 2, 3).
Bit 21: Overcurrent (--> F3x135, x = 1, 2, 3).
Bit 22: Temperature exceeded (--> F3x405, x = 1, 2, 3).
Bit 23: Singleturn position 2 (safety status display).
Bit 24: Singleturn system (--> F3x135, x = 1, 2, 3).
Bit 25: Singleturn power down (--> F3x135, x = 1, 2, 3)
Bit 26: Multiturn position 1 (--> F3x136, x = 1, 2, 3).
Bit 27: Multiturn position 2 (--> F3x136, x = 1, 2, 3).
Bit 28: Multiturn system (--> F3x136, x = 1, 2, 3).
Bit 29: Multiturn power down (--> F3x136, x = 1, 2, 3).
Bit 30: Multiturn overflow/underflow (--> F3x136, x = 1, 2, 3).
Bit 31: Multiturn battery (reserved).
Remedy: - determine the detailed cause of the fault using the fault value.
- replace the encoder if necessary.
Note:
An EnDat 2.2 encoder may only be removed and inserted in the "Park" state.
If an EnDat 2.2 encoder was removed when not in the "Park" state, then after inserting the encoder, a POWER ON (switch-
off/switch-on) is necessary to acknowledge the fault.
----------
Note:
For an encoder version that is not described here, please contact the encoder manufacturer for more detailed information
on the bit coding.
Remedy: - determine the detailed cause of the fault using the fault value.
- if required, replace the DRIVE-CLiQ encoder.
F31163 (N, A) Encoder 1: Analog sensor position value exceeds limit value
Message value: %1
Drive object: All objects
Reaction: Servo: ENCODER (IASC/DCBRK, NONE)
Acknowledge: PULSE INHIBIT
Cause: The position value has exceeded the permissible range of -0.5 ... +0.5.
Fault value (r0949, interpret decimal):
1: Position value from the LVDT sensor.
2: Position value from the encoder characteristic.
Remedy: For fault value = 1:
- check the LVDT ratio (p4678).
- check the reference signal connection at track B.
For fault value = 2:
- check the coefficients of the characteristic (p4663 ... p4666).
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
A31400 (F, N) Encoder 1: Zero mark distance error (alarm threshold exceeded)
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance.
For distance-coded encoders, the zero mark distance is determined from zero marks detected pairs. This means that if a
zero mark is missing, depending on the pair generation, this cannot result in a fault and also has no effect in the system.
The zero mark distance for the zero mark monitoring is set in p0425 (rotary encoder) or p0424 (linear encoder).
Alarm value (r2124, interpret decimal):
Last measured zero mark distance in increments (4 increments = 1 encoder pulse).
The sign designates the direction of motion when detecting the zero mark distance.
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- check the encoder type (encoder with equidistant zero marks).
- adapt the parameter for the distance between zero marks (p0424, p0425).
- replace the encoder or encoder cable.
Reaction upon F: Servo: NONE (ENCODER, IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: The absolute encoder fault word includes alarm bits that have been set.
Alarm value (r2124, interpret binary):
yyyyxxxx hex: yyyy = supplementary information, xxxx = fault cause
yyyy = 0:
Bit 0: Frequency exceeded (speed too high).
Bit 1: Temperature exceeded.
Bit 2: Control reserve, lighting system exceeded.
Bit 3: Battery discharged.
Bit 4: Reference point passed.
yyyy = 1:
Bit 0: Signal amplitude outside the control range.
Bit 1: Error multiturn interface
Bit 2: Internal data error (singleturn/multiturn not with single steps).
Bit 3: Error EEPROM interface.
Bit 4: SAR_converter error.
Bit 5: Fault for the register data transfer.
Bit 6: Internal error identified at the error pin (nErr).
Bit 7: Temperature threshold exceeded or fallen below.
Remedy: Replace encoder.
Reaction upon F: Servo: NONE (ENCODER, IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: The signal level (C^2 + D^2) of track C or D of the encoder or from the Hall signals, is not within the tolerance bandwidth.
Alarm value (r2124, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Signal level, track D (16 bits with sign).
xxxx = Signal level, track C (16 bits with sign).
The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %).
The response thresholds are < 230 mV (observe the frequency response of the encoder) and > 750 mV.
A signal level of 500 mV peak value corresponds to the numerical value 5333 hex = 21299 dec.
Note:
If the amplitude is not within the tolerance bandwidth, then it cannot be used to initialize the start position.
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
- check the Hall sensor box.
Reaction upon F: Servo: NONE (ENCODER, IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
A31422 (F, N) Encoder 1: Pulses per revolution square-wave encoder outside tolerance bandwidth
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance.
This alarm is triggered with active square-wave encoder PPR correction and re-parameterized fault 31131 if the
accumulator contains larger values than p4683 or p4684.
The zero mark distance for zero mark monitoring is set in p0425 (rotary encoder).
Alarm value (r2124, interpret decimal):
accumulated differential pulses in encoder pulses.
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- check the encoder type (encoder with equidistant zero marks).
- adapt the parameter for the distance between zero marks (p0424, p0425).
- replace the encoder or encoder cable.
Reaction upon F: Servo: NONE (ENCODER, IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
A31429 (F, N) Encoder 1: Position difference hall sensor/track C/D and A/B too large
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° electrical or the error for the Hall signals is greater
than +/-60 ° electrical.
One period of track C/D corresponds to 360 ° mechanical.
One period of the Hall signal corresponds to 360 ° electrical.
The monitoring responds if, for example, Hall sensors are connected as equivalent for the C/D tracks with the incorrect
rotational sense or supply values that are not accurate enough.
Alarm value (r2124, interpret decimal):
For track C/D, the following applies:
Measured deviation as mechanical angle (16 bits with sign, 182 dec corresponds to 1 °).
For Hall signals, the following applies:
Measured deviation as electrical angle (16 bits with sign, 182 dec corresponds to 1 °).
Remedy: - track C or D not connected.
- correct the direction of rotation of the Hall sensor possibly connected as equivalent for track C/D.
- check that the encoder cables are routed in compliance with EMC.
- check the adjustment of the Hall sensor.
Reaction upon F: Servo: NONE (ENCODER, IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: On track A/B, pulses have been lost or too many have been counted. These pulses are presently being corrected.
Alarm value (r2124, interpret decimal):
Last measured deviation of zero mark in increments (4 increments = 1 encoder pulse).
The sign designates the direction of motion when detecting the zero mark distance.
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check encoder limit frequency.
- adapt the parameter for the distance between zero marks (p0424, p0425).
Reaction upon F: Servo: NONE (ENCODER, IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
A31443 (F, N) Encoder 1: Signal level track C/D outside tolerance (alarm)
Message value: Fault cause: %1 bin
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The unipolar level (CP/CN or DP/DN) for encoder 1 is outside the permissible tolerance.
Alarm value (r2124, interpret binary):
Bit 0 = 1: Either CP or CN outside the tolerance.
Bit 16 = 1: Either DP or DN outside the tolerance.
The unipolar nominal signal level of the encoder must lie in the range 2500 mV +/- 500 mV.
The response thresholds are < 1700 mV and > 3300 mV.
Note:
The signal level is not evaluated unless the following conditions are satisfied:
- Sensor Module properties available (r0459.31 = 1).
- monitoring active (p0437.31 = 1).
Remedy: - check that the encoder cables and shielding are routed in compliance with EMC.
- check the plug connections and contacts of the encoder cable.
- are the C/D tracks connected correctly (have the signal cables CP and CN or DP and DN been interchanged)?
- replace the encoder cable.
Reaction upon F: Servo: NONE (ENCODER, IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
A31463 (N) Encoder 1: Analog sensor position value exceeds limit value
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The position value has exceeded the permissible range of -0.5 ... +0.5.
Alarm value (r2124, interpret decimal):
1: Position value from the LVDT sensor.
2: Position value from the encoder characteristic.
Remedy: For alarm value = 1:
- check the LVDT ratio (p4678).
- check the reference signal connection at track B.
For alarm value = 2:
- check the coefficients of the characteristic (p4663 ... p4666).
Reaction upon N: NONE
Acknowl. upon N: NONE
F31501 (N, A) Encoder 1: Position tracking encoder position outside tolerance window
Message value: %1
Drive object: All objects
Reaction: Servo: OFF1 (NONE, OFF2, OFF3)
Acknowledge: IMMEDIATELY
Cause: When switched off, the drive/encoder was moved through a distance greater than was parameterized in the tolerance
window. It is possible that there is no longer any reference between the mechanical system and encoder.
Fault value (r0949, interpret decimal):
Deviation (difference) to the last encoder position in increments of the absolute value.
The sign designates the traversing direction.
Note:
The deviation (difference) found is also displayed in r0477.
Remedy: Reset the position tracking as follows:
- select encoder commissioning (p0010 = 4).
- reset the position tracking as follows (p0411.2 = 1).
- deselect encoder commissioning (p0010 = 0).
The fault should then be acknowledged and, if necessary, the absolute encoder adjusted (p2507).
See also: p0010
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F31502 (N, A) Encoder 1: Encoder with measuring gear without valid signals
Message value: -
Drive object: All objects
Reaction: Servo: OFF1 (OFF2, OFF3)
Acknowledge: IMMEDIATELY
Cause: The encoder with measuring gear no longer provides any valid signals.
Remedy: It must be ensured that all of the encoders, with mounted measuring gear, provide valid actual values in operation.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: An internal software error has occurred in the Sensor Module of encoder 1.
Fault value (r0949, interpret decimal):
1: Background time slice is blocked.
2: Checksum over the code memory is not OK.
10000: OEM memory of the EnDat encoder contains data that cannot be interpreted.
11000 ... 11499: Descriptive data from EEPROM incorrect.
11500 ... 11899: Calibration data from EEPROM incorrect.
11900 ... 11999: Configuration data from EEPROM incorrect.
12000 ... 12008: communication with analog/digital converter faulted.
16000: DRIVE-CLiQ encoder initialization application error.
16001: DRIVE-CLiQ encoder initialization ALU error.
16002: DRIVE-CLiQ encoder HISI / SISI initialization error.
16003: DRIVE-CLiQ encoder safety initialization error.
16004: DRIVE-CLiQ encoder internal system error.
Remedy: - replace the Sensor Module.
- if required, upgrade the firmware in the Sensor Module.
- contact Technical Support.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 1) involved to the Control Unit.
Fault cause:
1 (= 01 hex):
Checksum error (CRC error).
2 (= 02 hex):
Telegram is shorter than specified in the length byte or in the receive list.
3 (= 03 hex):
Telegram is longer than specified in the length byte or in the receive list.
4 (= 04 hex):
The length of the receive telegram does not match the receive list.
5 (= 05 hex):
The type of the receive telegram does not match the receive list.
6 (= 06 hex):
The address of the power unit in the telegram and in the receive list do not match.
9 (= 09 hex):
The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply
voltage has failed.
16 (= 10 hex):
The receive telegram is too early.
17 (= 11 hex):
CRC error and the receive telegram is too early.
18 (= 12 hex):
The telegram is shorter than that specified in the length byte or in the receive list and the receive telegram is too early.
19 (= 13 hex):
The telegram is longer than that specified in the length byte or in the receive list and the receive telegram is too early.
20 (= 14 hex):
The length of the receive telegram does not match the receive list and the receive telegram is too early.
21 (= 15 hex):
The type of the receive telegram does not match the receive list and the receive telegram is too early.
22 (= 16 hex):
The address of the power unit in the telegram and in the receive list does not match and the receive telegram is too early.
25 (= 19 hex):
The error bit in the receive telegram is set and the receive telegram is too early.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- check the electrical cabinet design and cable routing for EMC compliance
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply
voltage has failed.
Fault cause:
9 (= 09 hex):
The power supply voltage for the components has failed.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- check the power supply voltage wiring for the DRIVE-CLiQ component (interrupted cable, contacts, ...).
- check the dimensioning of the power supply for the DRIVE-CLiQ component.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F31886 (N, A) Encoder 1 DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data
Message value: Component number: %1, fault cause: %2
Drive object: All objects
Reaction: Servo: ENCODER (IASC/DCBRK, NONE)
Acknowledge: IMMEDIATELY
Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 1) involved to the Control Unit.
Data were not able to be sent.
Fault cause:
65 (= 41 hex):
Telegram type does not match send list.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON.
- check whether the firmware version of the encoder (r0148) matches the firmware version of Control Unit (r0018).
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F31895 (N, A) Encoder 1 DRIVE-CLiQ (CU): Alternating cyclic data transfer error
Message value: Component number: %1, fault cause: %2
Drive object: All objects
Reaction: Servo: ENCODER (IASC/DCBRK, NONE)
Acknowledge: IMMEDIATELY
Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 1) involved to the Control Unit.
Fault cause:
11 (= 0B hex):
Synchronization error during alternating cyclic data transfer.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: Carry out a POWER ON.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: For the activated function "Data logger" (p0437.0 = 1) a fault has occurred with the Sensor Module. This alarm indicates
that the diagnostics data corresponding to the fault was saved on the memory card.
The diagnostics data is saved in the following folder:
/USER/SINAMICS/DATA/SMTRC00.BIN
...
/USER/SINAMICS/DATA/SMTRC07.BIN
/USER/SINAMICS/DATA/SMTRCIDX.TXT
The following information is contained in the TXT file:
- Display of the last written BIN file.
- Number of write operations that are still possible (from 10000 downwards).
Note:
Only Siemens can evaluate the BIN files.
Remedy: Not necessary.
This alarm is automatically withdrawn.
The data logger is ready to record the next fault case.
Reaction upon N: NONE
Acknowl. upon N: NONE
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- check the encoder type (encoder with equidistant zero marks).
- adapt the parameter for the clearance between zero marks (p0425).
- if message output above speed threshold, reduce filter time if necessary (p0438).
- when p0437.1 is active, check p4686.
- replace the encoder or encoder cable.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F32103 (N, A) Encoder 2: Signal level zero track (track R) outside tolerance
Message value: R track: %1
Drive object: All objects
Reaction: Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Acknowledge: IMMEDIATELY
Cause: The zero mark signal level (track R) does not lie within the tolerance bandwidth for encoder 2.
The fault can be initiated when the unipolar voltage level is exceeded (RP/RN) or if the differential amplitude is undershot.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex: yyyy = 0, xxxx = Signal level, track R (16 bits with sign)
The response thresholds of the unipolar signal levels of the encoder are between < 1400 mV and > 3500 mV.
The response threshold for the differential signal level of the encoder is < -1600 mV.
A signal level of 500 mV peak value corresponds to the numerical value 5333 hex = 21299 dec.
Note:
The analog value of the amplitude error is not measured at the same time with the hardware fault output by the Sensor
Module.
The fault value can only be represented between -32768 ... 32767 dec (-770 ... 770 mV).
The signal level is not evaluated unless the following conditions are satisfied:
- Sensor Module properties available (r0459.31 = 1).
- monitoring active (p0437.31 = 1).
Remedy: - check the speed range; frequency characteristic (amplitude characteristic) of the measuring equipment might not be
sufficient for the speed range
- check that the encoder cables and shielding are routed in compliance with EMC.
- check the plug connections and contacts of the encoder cable.
- check the encoder type (encoder with zero marks).
- check whether the zero mark is connected and the signal cables RP and RN have been connected correctly (not connected
with the incorrect polarity).
- replace the encoder cable.
- if the coding disk is soiled or the lighting aged, replace the encoder.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: Serial communication protocol transfer error between the encoder and evaluation module.
Fault value (r0949, interpret binary):
Bit 0: Alarm bit in the position protocol.
Bit 1: Incorrect quiescent level on the data line.
Bit 2: Encoder does not respond (does not supply a start bit within 50 ms).
Bit 3: CRC error: The checksum in the protocol from the encoder does not match the data.
Bit 4: Encoder acknowledgment error: The encoder incorrectly understood the task (request) or cannot execute it.
Bit 5: Internal error in the serial driver: An illegal mode command was requested.
Bit 6: Timeout when cyclically reading.
Bit 7: Timeout for the register communication.
Bit 8: Protocol is too long (e.g. > 64 bits).
Bit 9: Receive buffer overflow.
Bit 10: Frame error when reading twice.
Bit 11: Parity error.
Bit 12: Data line signal level error during the monoflop time.
Bit 13: Data line incorrect.
Bit 14: Fault for the register communication.
Bit 15: Internal communication error.
Note:
For an EnDat 2.2 encoder, the significance of the fault value for F3x135 (x = 1, 2, 3) is described.
Remedy: For fault value, bit 0 = 1:
- Enc defect F31111 may provide additional details.
For fault value, bit 1 = 1:
- incorrect encoder type / replace the encoder or encoder cable.
For fault value, bit 2 = 1:
- incorrect encoder type / replace the encoder or encoder cable.
For fault value, bit 3 = 1:
- EMC / connect the cable shield, replace the encoder or encoder cable.
For fault value, bit 4 = 1:
- EMC / connect the cable shield, replace the encoder or encoder cable, replace the Sensor Module.
For fault value, bit 5 = 1:
- EMC / connect the cable shield, replace the encoder or encoder cable, replace the Sensor Module.
For fault value, bit 6 = 1:
- Update Sensor Module firmware.
For fault value, bit 7 = 1:
- incorrect encoder type / replace the encoder or encoder cable.
For fault value, bit 8 = 1:
- check parameterization (p0429.2).
For fault value, bit 9 = 1:
- EMC / connect the cable shield, replace the encoder or encoder cable, replace the Sensor Module.
For fault value, bit 10 = 1:
- check parameterization (p0429.2, p0449).
For fault value, bit 11 = 1:
- check parameterization (p0436).
For fault value, bit 12 = 1:
- check parameterization (p0429.6).
For fault value, bit 13 = 1:
- check data line.
For fault value, bit 14 = 1:
- incorrect encoder type / replace the encoder or encoder cable.
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: The signal level of the rectified encoder signals A and B of the encoder fall below the permissible limit value.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Signal level, track B (16 bits with sign).
xxxx = Signal level, track A (16 bits with sign).
The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %).
The response threshold is < 130 mV.
A signal level of 500 mV peak value corresponds to the numerical value 5333 hex = 21299 dec.
Note:
The analog values of the amplitude error are not measured at the same time with the hardware fault output by the Sensor
Module.
Remedy: - check that the encoder cables and shielding are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F32129 (N, A) Encoder 2: Position difference hall sensor/track C/D and A/B too large
Message value: %1
Drive object: All objects
Reaction: Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Acknowledge: PULSE INHIBIT
Cause: The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° electrical or the error for the Hall signals is greater
than +/-60 ° electrical.
One period of track C/D corresponds to 360 ° mechanical.
One period of the Hall signal corresponds to 360 ° electrical.
The monitoring responds if, for example, Hall sensors are connected as equivalent for the C/D tracks with the incorrect
rotational sense or supply values that are not accurate enough.
After the fine synchronization using one reference mark or 2 reference marks for distance-coded encoders, this fault is no
longer initiated, but instead, Alarm A32429.
Fault value (r0949, interpret decimal):
For track C/D, the following applies:
Measured deviation as mechanical angle (16 bits with sign, 182 dec corresponds to 1 °).
For Hall signals, the following applies:
Measured deviation as electrical angle (16 bits with sign, 182 dec corresponds to 1 °).
Remedy: - track C or D not connected.
- correct the direction of rotation of the Hall sensor possibly connected as equivalent for track C/D.
- check that the encoder cables are routed in compliance with EMC.
- check the adjustment of the Hall sensor.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F32130 (N, A) Encoder 2: Zero mark and position error from the coarse synchronization
Message value: Angular deviation, electrical: %1, angle, mechanical: %2
Drive object: All objects
Reaction: Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Acknowledge: PULSE INHIBIT
Cause: After initializing the pole position using track C/D, Hall signals or pole position identification routine, the zero mark was
detected outside the permissible range. For distance-coded encoders, the test is carried out after passing 2 zero marks.
Fine synchronization was not carried out.
When initializing via track C/D (p0404) then it is checked whether the zero mark occurs in an angular range of +/-18 °
mechanical.
When initializing via Hall sensors (p0404) or pole position identification (p1982) it is checked whether the zero mark occurs
in an angular range of +/-60 ° electrical.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex
yyyy: Determined mechanical zero mark position (can only be used for track C/D).
xxxx: Deviation of the zero mark from the expected position as electrical angle.
Scaling: 32768 dec = 180 °
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- if the Hall sensor is used as an equivalent for track C/D, check the connection.
- check the connection of track C or D.
- replace the encoder or encoder cable.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check whether the coding disk is dirty or there are strong ambient magnetic fields.
- adapt the parameter for the clearance between zero marks (p0425).
- if message output above speed threshold, reduce filter time if necessary (p0438).
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: The encoder has identified a position determination fault (singleturn) and supplies status information bit by bit in an internal
status/fault word.
Some of these bits cause this fault to be triggered. Other bits are status displays. The status/fault word is displayed in the
fault value.
Note regarding the bit designation:
The first designation is valid for DRIVE-CLiQ encoders, the second for EnDat 2.2 encoders.
Fault value (r0949, interpret binary):
Bit 0: F1 (safety status display).
Bit 1: F2 (safety status display).
Bit 2: Reserved (lighting).
Bit 3: Reserved (signal amplitude).
Bit 4: Reserved (position value).
Bit 5: Reserved (overvoltage).
Bit 6: Reserved (undervoltage)/hardware fault EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 7: Reserved (overcurrent)/EnDat encoder withdrawn when not in the parked state (--> F3x110, x = 1, 2, 3).
Bit 8: Reserved (battery)/overcurrent EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 9: Reserved/overvoltage EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 11: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 12: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 13: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 14: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 15: Internal communication error (--> F3x110, x = 1, 2, 3).
Bit 16: Lighting (--> F3x135, x = 1, 2, 3).
Bit 17: Signal amplitude (--> F3x135, x = 1, 2, 3).
Bit 18: Singleturn position 1 (--> F3x135, x = 1, 2, 3).
Bit 19: Overvoltage (--> F3x135, x = 1, 2, 3).
Bit 20: Undervoltage (--> F3x135, x = 1, 2, 3).
Bit 21: Overcurrent (--> F3x135, x = 1, 2, 3).
Bit 22: Temperature exceeded (--> F3x405, x = 1, 2, 3).
Bit 23: Singleturn position 2 (safety status display).
Bit 24: Singleturn system (--> F3x135, x = 1, 2, 3).
Bit 25: Singleturn power down (--> F3x135, x = 1, 2, 3)
Bit 26: Multiturn position 1 (--> F3x136, x = 1, 2, 3).
Bit 27: Multiturn position 2 (--> F3x136, x = 1, 2, 3).
Bit 28: Multiturn system (--> F3x136, x = 1, 2, 3).
Bit 29: Multiturn power down (--> F3x136, x = 1, 2, 3).
Bit 30: Multiturn overflow/underflow (--> F3x136, x = 1, 2, 3).
Bit 31: Multiturn battery (reserved).
Remedy: - determine the detailed cause of the fault using the fault value.
- replace the encoder if necessary.
Note:
An EnDat 2.2 encoder may only be removed and inserted in the "Park" state.
If an EnDat 2.2 encoder was removed when not in the "Park" state, then after inserting the encoder, a POWER ON (switch-
off/switch-on) is necessary to acknowledge the fault.
Cause: The encoder has identified a position determination fault (multiturn) and supplies status information bit by bit in an internal
status/fault word.
Some of these bits cause this fault to be triggered. Other bits are status displays. The status/fault word is displayed in the
fault value.
Note regarding the bit designation:
The first designation is valid for DRIVE-CLiQ encoders, the second for EnDat 2.2 encoders.
Fault value (r0949, interpret binary):
Bit 0: F1 (safety status display).
Bit 1: F2 (safety status display).
Bit 2: Reserved (lighting).
Bit 3: Reserved (signal amplitude).
Bit 4: Reserved (position value).
Bit 5: Reserved (overvoltage).
Bit 6: Reserved (undervoltage)/hardware fault EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 7: Reserved (overcurrent)/EnDat encoder withdrawn when not in the parked state (--> F3x110, x = 1, 2, 3).
Bit 8: Reserved (battery)/overcurrent EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 9: Reserved/overvoltage EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 11: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 12: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 13: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 14: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 15: Internal communication error (--> F3x110, x = 1, 2, 3).
Bit 16: Lighting (--> F3x135, x = 1, 2, 3).
Bit 17: Signal amplitude (--> F3x135, x = 1, 2, 3).
Bit 18: Singleturn position 1 (--> F3x135, x = 1, 2, 3).
Bit 19: Overvoltage (--> F3x135, x = 1, 2, 3).
Bit 20: Undervoltage (--> F3x135, x = 1, 2, 3).
Bit 21: Overcurrent (--> F3x135, x = 1, 2, 3).
Bit 22: Temperature exceeded (--> F3x405, x = 1, 2, 3).
Bit 23: Singleturn position 2 (safety status display).
Bit 24: Singleturn system (--> F3x135, x = 1, 2, 3).
Bit 25: Singleturn power down (--> F3x135, x = 1, 2, 3)
Bit 26: Multiturn position 1 (--> F3x136, x = 1, 2, 3).
Bit 27: Multiturn position 2 (--> F3x136, x = 1, 2, 3).
Bit 28: Multiturn system (--> F3x136, x = 1, 2, 3).
Bit 29: Multiturn power down (--> F3x136, x = 1, 2, 3).
Bit 30: Multiturn overflow/underflow (--> F3x136, x = 1, 2, 3).
Bit 31: Multiturn battery (reserved).
Remedy: - determine the detailed cause of the fault using the fault value.
- replace the encoder if necessary.
Note:
An EnDat 2.2 encoder may only be removed and inserted in the "Park" state.
If an EnDat 2.2 encoder was removed when not in the "Park" state, then after inserting the encoder, a POWER ON (switch-
off/switch-on) is necessary to acknowledge the fault.
----------
Note:
For an encoder version that is not described here, please contact the encoder manufacturer for more detailed information
on the bit coding.
Remedy: - determine the detailed cause of the fault using the fault value.
- if required, replace the DRIVE-CLiQ encoder.
F32163 (N, A) Encoder 2: Analog sensor position value exceeds limit value
Message value: %1
Drive object: All objects
Reaction: Servo: OFF1 (IASC/DCBRK, NONE)
Acknowledge: PULSE INHIBIT
Cause: The position value has exceeded the permissible range of -0.5 ... +0.5.
Fault value (r0949, interpret decimal):
1: Position value from the LVDT sensor.
2: Position value from the encoder characteristic.
Remedy: For fault value = 1:
- check the LVDT ratio (p4678).
- check the reference signal connection at track B.
For fault value = 2:
- check the coefficients of the characteristic (p4663 ... p4666).
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
A32400 (F, N) Encoder 2: Zero mark distance error (alarm threshold exceeded)
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance.
For distance-coded encoders, the zero mark distance is determined from zero marks detected pairs. This means that if a
zero mark is missing, depending on the pair generation, this cannot result in a fault and also has no effect in the system.
The zero mark distance for the zero mark monitoring is set in p0425 (rotary encoder) or p0424 (linear encoder).
Alarm value (r2124, interpret decimal):
Last measured zero mark distance in increments (4 increments = 1 encoder pulse).
The sign designates the direction of motion when detecting the zero mark distance.
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- check the encoder type (encoder with equidistant zero marks).
- adapt the parameter for the distance between zero marks (p0424, p0425).
- replace the encoder or encoder cable.
Reaction upon F: Servo: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: The absolute encoder fault word includes alarm bits that have been set.
Alarm value (r2124, interpret binary):
yyyyxxxx hex: yyyy = supplementary information, xxxx = fault cause
yyyy = 0:
Bit 0: Frequency exceeded (speed too high).
Bit 1: Temperature exceeded.
Bit 2: Control reserve, lighting system exceeded.
Bit 3: Battery discharged.
Bit 4: Reference point passed.
yyyy = 1:
Bit 0: Signal amplitude outside the control range.
Bit 1: Error multiturn interface
Bit 2: Internal data error (singleturn/multiturn not with single steps).
Bit 3: Error EEPROM interface.
Bit 4: SAR converter error.
Bit 5: Fault for the register data transfer.
Bit 6: Internal error identified at the error pin (nErr).
Bit 7: Temperature threshold exceeded or fallen below.
Remedy: Replace encoder.
Reaction upon F: Servo: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: The signal level (C^2 + D^2) of track C or D of the encoder or from the Hall signals, is not within the tolerance bandwidth.
Alarm value (r2124, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Signal level, track D (16 bits with sign).
xxxx = Signal level, track C (16 bits with sign).
The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %).
The response thresholds are < 230 mV (observe the frequency response of the encoder) and > 750 mV.
A signal level of 500 mV peak value corresponds to the numerical value 5333 hex = 21299 dec.
Note:
If the amplitude is not within the tolerance bandwidth, then it cannot be used to initialize the start position.
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
- check the Hall sensor box.
Reaction upon F: Servo: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
A32422 (F, N) Encoder 2: Pulses per revolution square-wave encoder outside tolerance bandwidth
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance.
This alarm is triggered with active square-wave encoder PPR correction and re-parameterized fault 31131 if the
accumulator contains larger values than p4683 or p4684.
The zero mark distance for zero mark monitoring is set in p0425 (rotary encoder).
Alarm value (r2124, interpret decimal):
accumulated differential pulses in encoder pulses.
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- check the encoder type (encoder with equidistant zero marks).
- adapt the parameter for the distance between zero marks (p0424, p0425).
- replace the encoder or encoder cable.
Reaction upon F: Servo: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
A32429 (F, N) Encoder 2: Position difference hall sensor/track C/D and A/B too large
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° electrical or the error for the Hall signals is greater
than +/-60 ° electrical.
One period of track C/D corresponds to 360 ° mechanical.
One period of the Hall signal corresponds to 360 ° electrical.
The monitoring responds if, for example, Hall sensors are connected as equivalent for the C/D tracks with the incorrect
rotational sense or supply values that are not accurate enough.
Alarm value (r2124, interpret decimal):
For track C/D, the following applies:
Measured deviation as mechanical angle (16 bits with sign, 182 dec corresponds to 1 °).
For Hall signals, the following applies:
Measured deviation as electrical angle (16 bits with sign, 182 dec corresponds to 1 °).
Remedy: - track C or D not connected.
- correct the direction of rotation of the Hall sensor possibly connected as equivalent for track C/D.
- check that the encoder cables are routed in compliance with EMC.
- check the adjustment of the Hall sensor.
Reaction upon F: Servo: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: On track A/B, pulses have been lost or too many have been counted. These pulses are presently being corrected.
Alarm value (r2124, interpret decimal):
Last measured deviation of zero mark in increments (4 increments = 1 encoder pulse).
The sign designates the direction of motion when detecting the zero mark distance.
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check encoder limit frequency.
- adapt the parameter for the distance between zero marks (p0424, p0425).
Reaction upon F: Servo: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
A32443 (F, N) Encoder 2: Signal level track C/D outside tolerance (alarm)
Message value: Fault cause: %1 bin
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The unipolar level (CP/CN or DP/DN) for encoder 2 is outside the permissible tolerance.
Alarm value (r2124, interpret binary):
Bit 0 = 1: Either CP or CN outside the tolerance.
Bit 16 = 1: Either DP or DN outside the tolerance.
The unipolar nominal signal level of the encoder must lie in the range 2500 mV +/- 500 mV.
The response thresholds are < 1700 mV and > 3300 mV.
Note:
The signal level is not evaluated unless the following conditions are satisfied:
- Sensor Module properties available (r0459.31 = 1).
- monitoring active (p0437.31 = 1).
Remedy: - check that the encoder cables and shielding are routed in compliance with EMC.
- check the plug connections and contacts of the encoder cable.
- are the C/D tracks connected correctly (have the signal cables CP and CN or DP and DN been interchanged)?
- replace the encoder cable.
Reaction upon F: Servo: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
A32463 (N) Encoder 2: Analog sensor position value exceeds limit value
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The position value has exceeded the permissible range of -0.5 ... +0.5.
Alarm value (r2124, interpret decimal):
1: Position value from the LVDT sensor.
2: Position value from the encoder characteristic.
Remedy: For alarm value = 1:
- check the LVDT ratio (p4678).
- check the reference signal connection at track B.
For alarm value = 2:
- check the coefficients of the characteristic (p4663 ... p4666).
Reaction upon N: NONE
Acknowl. upon N: NONE
F32501 (N, A) Encoder 2: Position tracking encoder position outside tolerance window
Message value: %1
Drive object: All objects
Reaction: OFF1 (NONE, OFF2, OFF3)
Acknowledge: IMMEDIATELY
Cause: When switched off, the drive/encoder was moved through a distance greater than was parameterized in the tolerance
window. It is possible that there is no longer any reference between the mechanical system and encoder.
Fault value (r0949, interpret decimal):
Deviation (difference) to the last encoder position in increments of the absolute value.
The sign designates the traversing direction.
Note:
The deviation (difference) found is also displayed in r0477.
Remedy: Reset the position tracking as follows:
- select encoder commissioning (p0010 = 4).
- reset the position tracking as follows (p0411.2 = 1).
- deselect encoder commissioning (p0010 = 0).
The fault should then be acknowledged and, if necessary, the absolute encoder adjusted (p2507).
See also: p0010
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F32502 (N, A) Encoder 2: Encoder with measuring gear without valid signals
Message value: -
Drive object: All objects
Reaction: OFF1 (OFF2, OFF3)
Acknowledge: IMMEDIATELY
Cause: The encoder with measuring gear no longer provides any valid signals.
Remedy: It must be ensured that all of the encoders, with mounted measuring gear, provide valid actual values in operation.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
A32700 Encoder 2: Effectivity test does not supply the expected value
Message value: Fault cause: %1 bin
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set.
Alarm value (r2124, interpret binary):
Bit x = 1: Effectivity test x unsuccessful.
Remedy: Replace encoder.
Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned. The nodes do not send
and receive in synchronism.
Fault cause:
33 (= 21 hex):
The cyclic telegram has not been received.
34 (= 22 hex):
Timeout in the telegram receive list.
64 (= 40 hex):
Timeout in the telegram send list.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON.
- replace the component involved.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded.
Fault cause:
32 (= 20 hex):
Error in the telegram header.
35 (= 23 hex):
Receive error: The telegram buffer memory contains an error.
66 (= 42 hex):
Send error: The telegram buffer memory contains an error.
67 (= 43 hex):
Send error: The telegram buffer memory contains an error.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
- check the electrical cabinet design and cable routing for EMC compliance
- if required, use another DRIVE-CLiQ socket (p9904).
- replace the component involved.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: An internal software error has occurred in the Sensor Module of encoder 2.
Fault value (r0949, interpret decimal):
1: Background time slice is blocked.
2: Checksum over the code memory is not OK.
10000: OEM memory of the EnDat encoder contains data that cannot be interpreted.
11000 ... 11499: Descriptive data from EEPROM incorrect.
11500 ... 11899: Calibration data from EEPROM incorrect.
11900 ... 11999: Configuration data from EEPROM incorrect.
12000 ... 12008: communication with analog/digital converter faulted.
16000: DRIVE-CLiQ encoder initialization application error.
16001: DRIVE-CLiQ encoder initialization ALU error.
16002: DRIVE-CLiQ encoder HISI / SISI initialization error.
16003: DRIVE-CLiQ encoder safety initialization error.
16004: DRIVE-CLiQ encoder internal system error.
Remedy: - replace the Sensor Module.
- if required, upgrade the firmware in the Sensor Module.
- contact Technical Support.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit.
Fault cause:
1 (= 01 hex):
Checksum error (CRC error).
2 (= 02 hex):
Telegram is shorter than specified in the length byte or in the receive list.
3 (= 03 hex):
Telegram is longer than specified in the length byte or in the receive list.
4 (= 04 hex):
The length of the receive telegram does not match the receive list.
5 (= 05 hex):
The type of the receive telegram does not match the receive list.
6 (= 06 hex):
The address of the power unit in the telegram and in the receive list do not match.
9 (= 09 hex):
The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply
voltage has failed.
16 (= 10 hex):
The receive telegram is too early.
17 (= 11 hex):
CRC error and the receive telegram is too early.
18 (= 12 hex):
The telegram is shorter than that specified in the length byte or in the receive list and the receive telegram is too early.
19 (= 13 hex):
The telegram is longer than that specified in the length byte or in the receive list and the receive telegram is too early.
20 (= 14 hex):
The length of the receive telegram does not match the receive list and the receive telegram is too early.
21 (= 15 hex):
The type of the receive telegram does not match the receive list and the receive telegram is too early.
22 (= 16 hex):
The address of the power unit in the telegram and in the receive list does not match and the receive telegram is too early.
25 (= 19 hex):
The error bit in the receive telegram is set and the receive telegram is too early.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- check the electrical cabinet design and cable routing for EMC compliance
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply
voltage has failed.
Fault cause:
9 (= 09 hex):
The power supply voltage for the components has failed.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- check the power supply voltage wiring for the DRIVE-CLiQ component (interrupted cable, contacts, ...).
- check the dimensioning of the power supply for the DRIVE-CLiQ component.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F32886 (N, A) Encoder 2 DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data
Message value: Component number: %1, fault cause: %2
Drive object: All objects
Reaction: Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Acknowledge: IMMEDIATELY
Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit.
Data were not able to be sent.
Fault cause:
65 (= 41 hex):
Telegram type does not match send list.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: Carry out a POWER ON.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F32895 (N, A) Encoder 2 DRIVE-CLiQ (CU): Alternating cyclic data transfer error
Message value: Component number: %1, fault cause: %2
Drive object: All objects
Reaction: Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Acknowledge: IMMEDIATELY
Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 2) involved to the Control Unit.
Fault cause:
11 (= 0B hex):
Synchronization error during alternating cyclic data transfer.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: Carry out a POWER ON.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: For the activated function "Data logger" (p0437.0 = 1) a fault has occurred with the Sensor Module. This alarm indicates
that the diagnostics data corresponding to the fault was saved on the memory card.
The diagnostics data is saved in the following folder:
/USER/SINAMICS/DATA/SMTRC00.BIN
...
/USER/SINAMICS/DATA/SMTRC07.BIN
/USER/SINAMICS/DATA/SMTRCIDX.TXT
The following information is contained in the TXT file:
- Display of the last written BIN file.
- Number of write operations that are still possible (from 10000 downwards).
Note:
Only Siemens can evaluate the BIN files.
Remedy: Not necessary.
This alarm is automatically withdrawn.
The data logger is ready to record the next fault case.
Reaction upon N: NONE
Acknowl. upon N: NONE
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- check the encoder type (encoder with equidistant zero marks).
- adapt the parameter for the clearance between zero marks (p0425).
- if message output above speed threshold, reduce filter time if necessary (p0438).
- when p0437.1 is active, check p4686.
- replace the encoder or encoder cable.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F33103 (N, A) Encoder 3: Signal level zero track (track R) outside tolerance
Message value: R track: %1
Drive object: All objects
Reaction: Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Acknowledge: IMMEDIATELY
Cause: The zero mark signal level (track R) does not lie within the tolerance bandwidth for encoder 1.
The fault can be initiated when the unipolar voltage level is exceeded (RP/RN) or if the differential amplitude is undershot.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex: yyyy = 0, xxxx = Signal level, track R (16 bits with sign)
The response thresholds of the unipolar signal levels of the encoder are between < 1400 mV and > 3500 mV.
The response threshold for the differential signal level of the encoder is < -1600 mV.
A signal level of 500 mV peak value corresponds to the numerical value 5333 hex = 21299 dec.
Note:
The analog value of the amplitude error is not measured at the same time with the hardware fault output by the Sensor
Module.
The fault value can only be represented between -32768 ... 32767 dec (-770 ... 770 mV).
The signal level is not evaluated unless the following conditions are satisfied:
- Sensor Module properties available (r0459.31 = 1).
- monitoring active (p0437.31 = 1).
Remedy: - check the speed range; frequency characteristic (amplitude characteristic) of the measuring equipment might not be
sufficient for the speed range
- check that the encoder cables and shielding are routed in compliance with EMC.
- check the plug connections and contacts of the encoder cable.
- check the encoder type (encoder with zero marks).
- check whether the zero mark is connected and the signal cables RP and RN have been connected correctly (not connected
with the incorrect polarity).
- replace the encoder cable.
- if the coding disk is soiled or the lighting aged, replace the encoder.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: Serial communication protocol transfer error between the encoder and evaluation module.
Fault value (r0949, interpret binary):
Bit 0: Alarm bit in the position protocol.
Bit 1: Incorrect quiescent level on the data line.
Bit 2: Encoder does not respond (does not supply a start bit within 50 ms).
Bit 3: CRC error: The checksum in the protocol from the encoder does not match the data.
Bit 4: Encoder acknowledgment error: The encoder incorrectly understood the task (request) or cannot execute it.
Bit 5: Internal error in the serial driver: An illegal mode command was requested.
Bit 6: Timeout when cyclically reading.
Bit 7: Timeout for the register communication.
Bit 8: Protocol is too long (e.g. > 64 bits).
Bit 9: Receive buffer overflow.
Bit 10: Frame error when reading twice.
Bit 11: Parity error.
Bit 12: Data line signal level error during the monoflop time.
Bit 13: Data line incorrect.
Bit 14: Fault for the register communication.
Bit 15: Internal communication error.
Note:
For an EnDat 2.2 encoder, the significance of the fault value for F3x135 (x = 1, 2, 3) is described.
Remedy: For fault value, bit 0 = 1:
- Enc defect F31111 may provide additional details.
For fault value, bit 1 = 1:
- incorrect encoder type / replace the encoder or encoder cable.
For fault value, bit 2 = 1:
- incorrect encoder type / replace the encoder or encoder cable.
For fault value, bit 3 = 1:
- EMC / connect the cable shield, replace the encoder or encoder cable.
For fault value, bit 4 = 1:
- EMC / connect the cable shield, replace the encoder or encoder cable, replace the Sensor Module.
For fault value, bit 5 = 1:
- EMC / connect the cable shield, replace the encoder or encoder cable, replace the Sensor Module.
For fault value, bit 6 = 1:
- Update Sensor Module firmware.
For fault value, bit 7 = 1:
- incorrect encoder type / replace the encoder or encoder cable.
For fault value, bit 8 = 1:
- check parameterization (p0429.2).
For fault value, bit 9 = 1:
- EMC / connect the cable shield, replace the encoder or encoder cable, replace the Sensor Module.
For fault value, bit 10 = 1:
- check parameterization (p0429.2, p0449).
For fault value, bit 11 = 1:
- check parameterization (p0436).
For fault value, bit 12 = 1:
- check parameterization (p0429.6).
For fault value, bit 13 = 1:
- check data line.
For fault value, bit 14 = 1:
- incorrect encoder type / replace the encoder or encoder cable.
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: The signal level of the rectified encoder signals A and B of the encoder fall below the permissible limit value.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Signal level, track B (16 bits with sign).
xxxx = Signal level, track A (16 bits with sign).
The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %).
The response threshold is < 130 mV.
A signal level of 500 mV peak value corresponds to the numerical value 5333 hex = 21299 dec.
Note:
The analog values of the amplitude error are not measured at the same time with the hardware fault output by the Sensor
Module.
Remedy: - check that the encoder cables and shielding are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F33129 (N, A) Encoder 3: Position difference hall sensor/track C/D and A/B too large
Message value: %1
Drive object: All objects
Reaction: Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Acknowledge: PULSE INHIBIT
Cause: The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° electrical or the error for the Hall signals is greater
than +/-60 ° electrical.
One period of track C/D corresponds to 360 ° mechanical.
One period of the Hall signal corresponds to 360 ° electrical.
The monitoring responds if, for example, Hall sensors are connected as equivalent for the C/D tracks with the incorrect
rotational sense or supply values that are not accurate enough.
After the fine synchronization using one reference mark or 2 reference marks for distance-coded encoders, this fault is no
longer initiated, but instead, Alarm A33429.
Fault value (r0949, interpret decimal):
For track C/D, the following applies:
Measured deviation as mechanical angle (16 bits with sign, 182 dec corresponds to 1 °).
For Hall signals, the following applies:
Measured deviation as electrical angle (16 bits with sign, 182 dec corresponds to 1 °).
Remedy: - track C or D not connected.
- correct the direction of rotation of the Hall sensor possibly connected as equivalent for track C/D.
- check that the encoder cables are routed in compliance with EMC.
- check the adjustment of the Hall sensor.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F33130 (N, A) Encoder 3: Zero mark and position error from the coarse synchronization
Message value: Angular deviation, electrical: %1, angle, mechanical: %2
Drive object: All objects
Reaction: Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Acknowledge: PULSE INHIBIT
Cause: After initializing the pole position using track C/D, Hall signals or pole position identification routine, the zero mark was
detected outside the permissible range. For distance-coded encoders, the test is carried out after passing 2 zero marks.
Fine synchronization was not carried out.
When initializing via track C/D (p0404) then it is checked whether the zero mark occurs in an angular range of +/-18 °
mechanical.
When initializing via Hall sensors (p0404) or pole position identification (p1982) it is checked whether the zero mark occurs
in an angular range of +/-60 ° electrical.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex
yyyy: Determined mechanical zero mark position (can only be used for track C/D).
xxxx: Deviation of the zero mark from the expected position as electrical angle.
Scaling: 32768 dec = 180 °
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- if the Hall sensor is used as an equivalent for track C/D, check the connection.
- check the connection of track C or D.
- replace the encoder or encoder cable.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check whether the coding disk is dirty or there are strong ambient magnetic fields.
- adapt the parameter for the clearance between zero marks (p0425).
- if message output above speed threshold, reduce filter time if necessary (p0438).
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: The encoder has identified a position determination fault (singleturn) and supplies status information bit by bit in an internal
status/fault word.
Some of these bits cause this fault to be triggered. Other bits are status displays. The status/fault word is displayed in the
fault value.
Note regarding the bit designation:
The first designation is valid for DRIVE-CLiQ encoders, the second for EnDat 2.2 encoders.
Fault value (r0949, interpret binary):
Bit 0: F1 (safety status display).
Bit 1: F2 (safety status display).
Bit 2: Reserved (lighting).
Bit 3: Reserved (signal amplitude).
Bit 4: Reserved (position value).
Bit 5: Reserved (overvoltage).
Bit 6: Reserved (undervoltage)/hardware fault EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 7: Reserved (overcurrent)/EnDat encoder withdrawn when not in the parked state (--> F3x110, x = 1, 2, 3).
Bit 8: Reserved (battery)/overcurrent EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 9: Reserved/overvoltage EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 11: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 12: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 13: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 14: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 15: Internal communication error (--> F3x110, x = 1, 2, 3).
Bit 16: Lighting (--> F3x135, x = 1, 2, 3).
Bit 17: Signal amplitude (--> F3x135, x = 1, 2, 3).
Bit 18: Singleturn position 1 (--> F3x135, x = 1, 2, 3).
Bit 19: Overvoltage (--> F3x135, x = 1, 2, 3).
Bit 20: Undervoltage (--> F3x135, x = 1, 2, 3).
Bit 21: Overcurrent (--> F3x135, x = 1, 2, 3).
Bit 22: Temperature exceeded (--> F3x405, x = 1, 2, 3).
Bit 23: Singleturn position 2 (safety status display).
Bit 24: Singleturn system (--> F3x135, x = 1, 2, 3).
Bit 25: Singleturn power down (--> F3x135, x = 1, 2, 3)
Bit 26: Multiturn position 1 (--> F3x136, x = 1, 2, 3).
Bit 27: Multiturn position 2 (--> F3x136, x = 1, 2, 3).
Bit 28: Multiturn system (--> F3x136, x = 1, 2, 3).
Bit 29: Multiturn power down (--> F3x136, x = 1, 2, 3).
Bit 30: Multiturn overflow/underflow (--> F3x136, x = 1, 2, 3).
Bit 31: Multiturn battery (reserved).
Remedy: - determine the detailed cause of the fault using the fault value.
- replace the encoder if necessary.
Note:
An EnDat 2.2 encoder may only be removed and inserted in the "Park" state.
If an EnDat 2.2 encoder was removed when not in the "Park" state, then after inserting the encoder, a POWER ON (switch-
off/switch-on) is necessary to acknowledge the fault.
Cause: The encoder has identified a position determination fault (multiturn) and supplies status information bit by bit in an internal
status/fault word.
Some of these bits cause this fault to be triggered. Other bits are status displays. The status/fault word is displayed in the
fault value.
Note regarding the bit designation:
The first designation is valid for DRIVE-CLiQ encoders, the second for EnDat 2.2 encoders.
Fault value (r0949, interpret binary):
Bit 0: F1 (safety status display).
Bit 1: F2 (safety status display).
Bit 2: Reserved (lighting).
Bit 3: Reserved (signal amplitude).
Bit 4: Reserved (position value).
Bit 5: Reserved (overvoltage).
Bit 6: Reserved (undervoltage)/hardware fault EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 7: Reserved (overcurrent)/EnDat encoder withdrawn when not in the parked state (--> F3x110, x = 1, 2, 3).
Bit 8: Reserved (battery)/overcurrent EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 9: Reserved/overvoltage EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 11: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 12: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 13: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 14: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 15: Internal communication error (--> F3x110, x = 1, 2, 3).
Bit 16: Lighting (--> F3x135, x = 1, 2, 3).
Bit 17: Signal amplitude (--> F3x135, x = 1, 2, 3).
Bit 18: Singleturn position 1 (--> F3x135, x = 1, 2, 3).
Bit 19: Overvoltage (--> F3x135, x = 1, 2, 3).
Bit 20: Undervoltage (--> F3x135, x = 1, 2, 3).
Bit 21: Overcurrent (--> F3x135, x = 1, 2, 3).
Bit 22: Temperature exceeded (--> F3x405, x = 1, 2, 3).
Bit 23: Singleturn position 2 (safety status display).
Bit 24: Singleturn system (--> F3x135, x = 1, 2, 3).
Bit 25: Singleturn power down (--> F3x135, x = 1, 2, 3)
Bit 26: Multiturn position 1 (--> F3x136, x = 1, 2, 3).
Bit 27: Multiturn position 2 (--> F3x136, x = 1, 2, 3).
Bit 28: Multiturn system (--> F3x136, x = 1, 2, 3).
Bit 29: Multiturn power down (--> F3x136, x = 1, 2, 3).
Bit 30: Multiturn overflow/underflow (--> F3x136, x = 1, 2, 3).
Bit 31: Multiturn battery (reserved).
Remedy: - determine the detailed cause of the fault using the fault value.
- replace the encoder if necessary.
Note:
An EnDat 2.2 encoder may only be removed and inserted in the "Park" state.
If an EnDat 2.2 encoder was removed when not in the "Park" state, then after inserting the encoder, a POWER ON (switch-
off/switch-on) is necessary to acknowledge the fault.
----------
Note:
For an encoder version that is not described here, please contact the encoder manufacturer for more detailed information
on the bit coding.
Remedy: - determine the detailed cause of the fault using the fault value.
- if required, replace the DRIVE-CLiQ encoder.
F33163 (N, A) Encoder 3: Analog sensor position value exceeds limit value
Message value: %1
Drive object: All objects
Reaction: Servo: OFF1 (IASC/DCBRK, NONE)
Acknowledge: PULSE INHIBIT
Cause: The position value has exceeded the permissible range of -0.5 ... +0.5.
Fault value (r0949, interpret decimal):
1: Position value from the LVDT sensor.
2: Position value from the encoder characteristic.
Remedy: For fault value = 1:
- check the LVDT ratio (p4678).
- check the reference signal connection at track B.
For fault value = 2:
- check the coefficients of the characteristic (p4663 ... p4666).
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
A33400 (F, N) Encoder 3: Zero mark distance error (alarm threshold exceeded)
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance.
For distance-coded encoders, the zero mark distance is determined from zero marks detected pairs. This means that if a
zero mark is missing, depending on the pair generation, this cannot result in a fault and also has no effect in the system.
The zero mark distance for the zero mark monitoring is set in p0425 (rotary encoder) or p0424 (linear encoder).
Alarm value (r2124, interpret decimal):
Last measured zero mark distance in increments (4 increments = 1 encoder pulse).
The sign designates the direction of motion when detecting the zero mark distance.
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- check the encoder type (encoder with equidistant zero marks).
- adapt the parameter for the distance between zero marks (p0424, p0425).
- replace the encoder or encoder cable.
Reaction upon F: Servo: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: The absolute encoder fault word includes alarm bits that have been set.
Alarm value (r2124, interpret binary):
yyyyxxxx hex: yyyy = supplementary information, xxxx = fault cause
yyyy = 0:
Bit 0: Frequency exceeded (speed too high).
Bit 1: Temperature exceeded.
Bit 2: Control reserve, lighting system exceeded.
Bit 3: Battery discharged.
Bit 4: Reference point passed.
yyyy = 1:
Bit 0: Signal amplitude outside the control range.
Bit 1: Error multiturn interface
Bit 2: Internal data error (singleturn/multiturn not with single steps).
Bit 3: Error EEPROM interface.
Bit 4: SAR converter error.
Bit 5: Fault for the register data transfer.
Bit 6: Internal error identified at the error pin (nErr).
Bit 7: Temperature threshold exceeded or fallen below.
Remedy: Replace encoder.
Reaction upon F: Servo: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: The signal level (C^2 + D^2) of track C or D of the encoder or from the Hall signals, is not within the tolerance bandwidth.
Alarm value (r2124, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Signal level, track D (16 bits with sign).
xxxx = Signal level, track C (16 bits with sign).
The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %).
The response thresholds are < 230 mV (observe the frequency response of the encoder) and > 750 mV.
A signal level of 500 mV peak value corresponds to the numerical value 5333 hex = 21299 dec.
Note:
If the amplitude is not within the tolerance bandwidth, then it cannot be used to initialize the start position.
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
- check the Hall sensor box.
Reaction upon F: Servo: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
A33422 (F, N) Encoder 3: Pulses per revolution square-wave encoder outside tolerance bandwidth
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The measured zero mark distance does not correspond to the parameterized zero mark distance.
This alarm is triggered with active square-wave encoder PPR correction and re-parameterized fault 31131 if the
accumulator contains larger values than p4683 or p4684.
The zero mark distance for zero mark monitoring is set in p0425 (rotary encoder).
Alarm value (r2124, interpret decimal):
accumulated differential pulses in encoder pulses.
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- check the encoder type (encoder with equidistant zero marks).
- adapt the parameter for the distance between zero marks (p0424, p0425).
- replace the encoder or encoder cable.
Reaction upon F: Servo: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
A33429 (F, N) Encoder 3: Position difference hall sensor/track C/D and A/B too large
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° electrical or the error for the Hall signals is greater
than +/-60 ° electrical.
One period of track C/D corresponds to 360 ° mechanical.
One period of the Hall signal corresponds to 360 ° electrical.
The monitoring responds if, for example, Hall sensors are connected as equivalent for the C/D tracks with the incorrect
rotational sense or supply values that are not accurate enough.
Alarm value (r2124, interpret decimal):
For track C/D, the following applies:
Measured deviation as mechanical angle (16 bits with sign, 182 dec corresponds to 1 °).
For Hall signals, the following applies:
Measured deviation as electrical angle (16 bits with sign, 182 dec corresponds to 1 °).
Remedy: - track C or D not connected.
- correct the direction of rotation of the Hall sensor possibly connected as equivalent for track C/D.
- check that the encoder cables are routed in compliance with EMC.
- check the adjustment of the Hall sensor.
Reaction upon F: Servo: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: On track A/B, pulses have been lost or too many have been counted. These pulses are presently being corrected.
Alarm value (r2124, interpret decimal):
Last measured deviation of zero mark in increments (4 increments = 1 encoder pulse).
The sign designates the direction of motion when detecting the zero mark distance.
Remedy: - check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check encoder limit frequency.
- adapt the parameter for the distance between zero marks (p0424, p0425).
Reaction upon F: Servo: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
A33443 (F, N) Encoder 3: Signal level track C/D outside tolerance (alarm)
Message value: Fault cause: %1 bin
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The unipolar level (CP/CN or DP/DN) for encoder 3 is outside the permissible tolerance.
Alarm value (r2124, interpret binary):
Bit 0 = 1: Either CP or CN outside the tolerance.
Bit 16 = 1: Either DP or DN outside the tolerance.
The unipolar nominal signal level of the encoder must lie in the range 2500 mV +/- 500 mV.
The response thresholds are < 1700 mV and > 3300 mV.
Note:
The signal level is not evaluated unless the following conditions are satisfied:
- Sensor Module properties available (r0459.31 = 1).
- monitoring active (p0437.31 = 1).
Remedy: - check that the encoder cables and shielding are routed in compliance with EMC.
- check the plug connections and contacts of the encoder cable.
- are the C/D tracks connected correctly (have the signal cables CP and CN or DP and DN been interchanged)?
- replace the encoder cable.
Reaction upon F: Servo: NONE (IASC/DCBRK, OFF1, OFF2, OFF3, STOP2)
Acknowl. upon F: IMMEDIATELY
Reaction upon N: NONE
Acknowl. upon N: NONE
A33463 (N) Encoder 3: Analog sensor position value exceeds limit value
Message value: %1
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The position value has exceeded the permissible range of -0.5 ... +0.5.
Alarm value (r2124, interpret decimal):
1: Position value from the LVDT sensor.
2: Position value from the encoder characteristic.
Remedy: For alarm value = 1:
- check the LVDT ratio (p4678).
- check the reference signal connection at track B.
For alarm value = 2:
- check the coefficients of the characteristic (p4663 ... p4666).
Reaction upon N: NONE
Acknowl. upon N: NONE
F33501 (N, A) Encoder 3: Position tracking encoder position outside tolerance window
Message value: %1
Drive object: All objects
Reaction: OFF1 (NONE, OFF2, OFF3)
Acknowledge: IMMEDIATELY
Cause: When switched off, the drive/encoder was moved through a distance greater than was parameterized in the tolerance
window. It is possible that there is no longer any reference between the mechanical system and encoder.
Fault value (r0949, interpret decimal):
Deviation (difference) to the last encoder position in increments of the absolute value.
The sign designates the traversing direction.
Note:
The deviation (difference) found is also displayed in r0477.
Remedy: Reset the position tracking as follows:
- select encoder commissioning (p0010 = 4).
- reset the position tracking as follows (p0411.2 = 1).
- deselect encoder commissioning (p0010 = 0).
The fault should then be acknowledged and, if necessary, the absolute encoder adjusted (p2507).
See also: p0010
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F33502 (N, A) Encoder 3: Encoder with measuring gear without valid signals
Message value: -
Drive object: All objects
Reaction: OFF1 (OFF2, OFF3)
Acknowledge: IMMEDIATELY
Cause: The encoder with measuring gear no longer provides any valid signals.
Remedy: It must be ensured that all of the encoders, with mounted measuring gear, provide valid actual values in operation.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
A33700 Encoder 3: Effectivity test does not supply the expected value
Message value: Fault cause: %1 bin
Drive object: All objects
Reaction: NONE
Acknowledge: NONE
Cause: The DRIVE-CLiQ encoder fault word supplies fault bits that have been set.
Alarm value (r2124, interpret binary):
Bit x = 1: Effectivity test x unsuccessful.
Remedy: Replace encoder.
Cause: A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned. The nodes do not send
and receive in synchronism.
Fault cause:
33 (= 21 hex):
The cyclic telegram has not been received.
34 (= 22 hex):
Timeout in the telegram receive list.
64 (= 40 hex):
Timeout in the telegram send list.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON.
- replace the component involved.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded.
Fault cause:
32 (= 20 hex):
Error in the telegram header.
35 (= 23 hex):
Receive error: The telegram buffer memory contains an error.
66 (= 42 hex):
Send error: The telegram buffer memory contains an error.
67 (= 43 hex):
Send error: The telegram buffer memory contains an error.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
- check the electrical cabinet design and cable routing for EMC compliance
- if required, use another DRIVE-CLiQ socket (p9904).
- replace the component involved.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: An internal software error has occurred in the Sensor Module of encoder 3.
Fault value (r0949, interpret decimal):
1: Background time slice is blocked.
2: Checksum over the code memory is not OK.
10000: OEM memory of the EnDat encoder contains data that cannot be interpreted.
11000 ... 11499: Descriptive data from EEPROM incorrect.
11500 ... 11899: Calibration data from EEPROM incorrect.
11900 ... 11999: Configuration data from EEPROM incorrect.
12000 ... 12008: communication with analog/digital converter faulted.
16000: DRIVE-CLiQ encoder initialization application error.
16001: DRIVE-CLiQ encoder initialization ALU error.
16002: DRIVE-CLiQ encoder HISI / SISI initialization error.
16003: DRIVE-CLiQ encoder safety initialization error.
16004: DRIVE-CLiQ encoder internal system error.
Remedy: - replace the Sensor Module.
- if required, upgrade the firmware in the Sensor Module.
- contact Technical Support.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit.
Fault cause:
1 (= 01 hex):
Checksum error (CRC error).
2 (= 02 hex):
Telegram is shorter than specified in the length byte or in the receive list.
3 (= 03 hex):
Telegram is longer than specified in the length byte or in the receive list.
4 (= 04 hex):
The length of the receive telegram does not match the receive list.
5 (= 05 hex):
The type of the receive telegram does not match the receive list.
6 (= 06 hex):
The address of the power unit in the telegram and in the receive list do not match.
9 (= 09 hex):
The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply
voltage has failed.
16 (= 10 hex):
The receive telegram is too early.
17 (= 11 hex):
CRC error and the receive telegram is too early.
18 (= 12 hex):
The telegram is shorter than that specified in the length byte or in the receive list and the receive telegram is too early.
19 (= 13 hex):
The telegram is longer than that specified in the length byte or in the receive list and the receive telegram is too early.
20 (= 14 hex):
The length of the receive telegram does not match the receive list and the receive telegram is too early.
21 (= 15 hex):
The type of the receive telegram does not match the receive list and the receive telegram is too early.
22 (= 16 hex):
The address of the power unit in the telegram and in the receive list does not match and the receive telegram is too early.
25 (= 19 hex):
The error bit in the receive telegram is set and the receive telegram is too early.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- check the electrical cabinet design and cable routing for EMC compliance
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply
voltage has failed.
Fault cause:
9 (= 09 hex):
The power supply voltage for the components has failed.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- check the power supply voltage wiring for the DRIVE-CLiQ component (interrupted cable, contacts, ...).
- check the dimensioning of the power supply for the DRIVE-CLiQ component.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F33886 (N, A) Encoder 3 DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data
Message value: Component number: %1, fault cause: %2
Drive object: All objects
Reaction: Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Acknowledge: IMMEDIATELY
Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit.
Data were not able to be sent.
Fault cause:
65 (= 41 hex):
Telegram type does not match send list.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: Carry out a POWER ON.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
F33895 (N, A) Encoder 3 DRIVE-CLiQ (CU): Alternating cyclic data transfer error
Message value: Component number: %1, fault cause: %2
Drive object: All objects
Reaction: Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Acknowledge: IMMEDIATELY
Cause: A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit.
Fault cause:
11 (= 0B hex):
Synchronization error during alternating cyclic data transfer.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: Carry out a POWER ON.
Reaction upon N: NONE
Acknowl. upon N: NONE
Reaction upon A: NONE
Acknowl. upon A: NONE
Cause: For the activated function "Data logger" (p0437.0 = 1) a fault has occurred with the Sensor Module. This alarm indicates
that the diagnostics data corresponding to the fault was saved on the memory card.
The diagnostics data is saved in the following folder:
/USER/SINAMICS/DATA/SMTRC00.BIN
...
/USER/SINAMICS/DATA/SMTRC07.BIN
/USER/SINAMICS/DATA/SMTRCIDX.TXT
The following information is contained in the TXT file:
- Display of the last written BIN file.
- Number of write operations that are still possible (from 10000 downwards).
Note:
Only Siemens can evaluate the BIN files.
Remedy: Not necessary.
This alarm is automatically withdrawn.
The data logger is ready to record the next fault case.
Reaction upon N: NONE
Acknowl. upon N: NONE
Cause: A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit.
Fault cause:
1 (= 01 hex):
Checksum error (CRC error).
2 (= 02 hex):
Telegram is shorter than specified in the length byte or in the receive list.
3 (= 03 hex):
Telegram is longer than specified in the length byte or in the receive list.
4 (= 04 hex):
The length of the receive telegram does not match the receive list.
5 (= 05 hex):
The type of the receive telegram does not match the receive list.
6 (= 06 hex):
The address of the power unit in the telegram and in the receive list do not match.
9 (= 09 hex):
The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply
voltage has failed.
16 (= 10 hex):
The receive telegram is too early.
17 (= 11 hex):
CRC error and the receive telegram is too early.
18 (= 12 hex):
The telegram is shorter than that specified in the length byte or in the receive list and the receive telegram is too early.
19 (= 13 hex):
The telegram is longer than that specified in the length byte or in the receive list and the receive telegram is too early.
20 (= 14 hex):
The length of the receive telegram does not match the receive list and the receive telegram is too early.
21 (= 15 hex):
The type of the receive telegram does not match the receive list and the receive telegram is too early.
22 (= 16 hex):
The address of the power unit in the telegram and in the receive list does not match and the receive telegram is too early.
25 (= 19 hex):
The error bit in the receive telegram is set and the receive telegram is too early.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- check the electrical cabinet design and cable routing for EMC compliance
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply
voltage has failed.
Fault cause:
9 (= 09 hex):
The power supply voltage for the components has failed.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- check the power supply voltage wiring for the DRIVE-CLiQ component (interrupted cable, contacts, ...).
- check the dimensioning of the power supply for the DRIVE-CLiQ component.
Cause: A DRIVE-CLiQ communication error has occurred from the Terminal Module involved (TM) to the Control Unit.
Fault cause:
1 (= 01 hex):
Checksum error (CRC error).
2 (= 02 hex):
Telegram is shorter than specified in the length byte or in the receive list.
3 (= 03 hex):
Telegram is longer than specified in the length byte or in the receive list.
4 (= 04 hex):
The length of the receive telegram does not match the receive list.
5 (= 05 hex):
The type of the receive telegram does not match the receive list.
6 (= 06 hex):
The address of the power unit in the telegram and in the receive list do not match.
9 (= 09 hex):
The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply
voltage has failed.
16 (= 10 hex):
The receive telegram is too early.
17 (= 11 hex):
CRC error and the receive telegram is too early.
18 (= 12 hex):
The telegram is shorter than that specified in the length byte or in the receive list and the receive telegram is too early.
19 (= 13 hex):
The telegram is longer than that specified in the length byte or in the receive list and the receive telegram is too early.
20 (= 14 hex):
The length of the receive telegram does not match the receive list and the receive telegram is too early.
21 (= 15 hex):
The type of the receive telegram does not match the receive list and the receive telegram is too early.
22 (= 16 hex):
The address of the power unit in the telegram and in the receive list does not match and the receive telegram is too early.
25 (= 19 hex):
The error bit in the receive telegram is set and the receive telegram is too early.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- check the electrical cabinet design and cable routing for EMC compliance
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply
voltage has failed.
Fault cause:
9 (= 09 hex):
The power supply voltage for the components has failed.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- check the power supply voltage wiring for the DRIVE-CLiQ component (interrupted cable, contacts, ...).
- check the dimensioning of the power supply for the DRIVE-CLiQ component.
Cause: DRIVE-CLiQ communication error from DRIVE-CLiQ Hub Module in question to Control Unit.
Fault cause:
1 (= 01 hex):
Checksum error (CRC error).
2 (= 02 hex):
Telegram is shorter than specified in the length byte or in the receive list.
3 (= 03 hex):
Telegram is longer than specified in the length byte or in the receive list.
4 (= 04 hex):
The length of the receive telegram does not match the receive list.
5 (= 05 hex):
The type of the receive telegram does not match the receive list.
6 (= 06 hex):
The address of the power unit in the telegram and in the receive list do not match.
9 (= 09 hex):
The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply
voltage has failed.
16 (= 10 hex):
The receive telegram is too early.
17 (= 11 hex):
CRC error and the receive telegram is too early.
18 (= 12 hex):
The telegram is shorter than that specified in the length byte or in the receive list and the receive telegram is too early.
19 (= 13 hex):
The telegram is longer than that specified in the length byte or in the receive list and the receive telegram is too early.
20 (= 14 hex):
The length of the receive telegram does not match the receive list and the receive telegram is too early.
21 (= 15 hex):
The type of the receive telegram does not match the receive list and the receive telegram is too early.
22 (= 16 hex):
The address of the power unit in the telegram and in the receive list does not match and the receive telegram is too early.
25 (= 19 hex):
The error bit in the receive telegram is set and the receive telegram is too early.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- check the electrical cabinet design and cable routing for EMC compliance
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply
voltage has failed.
Fault cause:
9 (= 09 hex):
The power supply voltage for the components has failed.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- check the power supply voltage wiring for the DRIVE-CLiQ component (interrupted cable, contacts, ...).
- check the dimensioning of the power supply for the DRIVE-CLiQ component.
Acknowledge: IMMEDIATELY
Cause: The connection to one of the heat sink temperature sensors in the HF Damping Module is interrupted.
Fault value (r0949, interpret hexadecimal):
Bit 0: HF Damping Module
Bit 1: HF Choke Module
Remedy: Contact the manufacturer.
Note:
HF Choke Module (reactor module)
HF Damping Module
Cause: The chip temperature has exceeded the permissible limit value.
- the permissible load duty cycle was not maintained.
- insufficient cooling, fan failure.
- overload.
- ambient temperature too high.
- pulse frequency too high.
Fault value (r0949, interpret decimal):
Temperature difference between the heat sink and chip [0.01 °C].
Remedy: - adapt the load duty cycle.
- check whether the fan is running.
- check the fan elements.
- check whether the ambient temperature is in the permissible range.
- check the motor load.
- reduce the pulse frequency if this is higher than the rated pulse frequency.
Note:
HF Damping Module
See also: r0037
Acknowledge: POWER ON
Cause: EEPROM data error of the HF Damping Module.
Fault value (r0949, interpret hexadecimal):
0: The EEPROM data read in from the HF Damping Module is inconsistent.
1: EEPROM data is not compatible to the firmware of the HF Damping Module.
Additional values:
Only for internal Siemens troubleshooting.
Remedy: For fault value = 0:
Replace the HF Damping Module or update the EEPROM data.
For fault value = 1:
If necessary, upgrade the firmware to a later version.
Note:
HF Damping Module
Cause: There is a DRIVE-CLiQ communication error between the Control Unit and the HF Damping Module. The nodes do not
send and receive in synchronism.
Fault cause:
33 (= 21 hex):
The cyclic telegram has not been received.
34 (= 22 hex):
Timeout in the telegram receive list.
64 (= 40 hex):
Timeout in the telegram send list.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON.
- replace the component involved.
Note:
HF Damping Module
Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded.
Fault cause:
32 (= 20 hex):
Error in the telegram header.
35 (= 23 hex):
Receive error: The telegram buffer memory contains an error.
66 (= 42 hex):
Send error: The telegram buffer memory contains an error.
67 (= 43 hex):
Send error: The telegram buffer memory contains an error.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
- check the electrical cabinet design and cable routing for EMC compliance
- if required, use another DRIVE-CLiQ socket (p9904).
- replace the component involved.
Note:
HF Damping Module
Cause: DRIVE-CLiQ communication error from the HF Damping Module to the Control Unit.
Fault cause:
1 (= 01 hex):
Checksum error (CRC error).
2 (= 02 hex):
Telegram is shorter than specified in the length byte or in the receive list.
3 (= 03 hex):
Telegram is longer than specified in the length byte or in the receive list.
4 (= 04 hex):
The length of the receive telegram does not match the receive list.
5 (= 05 hex):
The type of the receive telegram does not match the receive list.
6 (= 06 hex):
The address of the power unit in the telegram and in the receive list do not match.
9 (= 09 hex):
The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply
voltage has failed.
16 (= 10 hex):
The receive telegram is too early.
17 (= 11 hex):
CRC error and the receive telegram is too early.
18 (= 12 hex):
The telegram is shorter than that specified in the length byte or in the receive list and the receive telegram is too early.
19 (= 13 hex):
The telegram is longer than that specified in the length byte or in the receive list and the receive telegram is too early.
20 (= 14 hex):
The length of the receive telegram does not match the receive list and the receive telegram is too early.
21 (= 15 hex):
The type of the receive telegram does not match the receive list and the receive telegram is too early.
22 (= 16 hex):
The address of the power unit in the telegram and in the receive list does not match and the receive telegram is too early.
25 (= 19 hex):
The error bit in the receive telegram is set and the receive telegram is too early.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- check the electrical cabinet design and cable routing for EMC compliance
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
Note:
HF Damping Module
Cause: The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply
voltage has failed.
Fault cause:
9 (= 09 hex):
The power supply voltage for the components has failed.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- check the power supply voltage wiring for the DRIVE-CLiQ component (interrupted cable, contacts, ...).
- check the dimensioning of the power supply for the DRIVE-CLiQ component.
Cause: DRIVE-CLiQ communication error from the HF Damping Module to the Control Unit.
Data were not able to be sent.
Fault cause:
65 (= 41 hex):
Telegram type does not match send list.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: Carry out a POWER ON.
Note:
HF Damping Module
Cause: DRIVE-CLiQ communication error from the HF Damping Module to the Control Unit.
Fault cause:
11 (= 0B hex):
Synchronization error during alternating cyclic data transfer.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: Carry out a POWER ON.
Note:
HF Damping Module
Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the controller extension involved.
Fault cause:
1 (= 01 hex):
Checksum error (CRC error).
2 (= 02 hex):
Telegram is shorter than specified in the length byte or in the receive list.
3 (= 03 hex):
Telegram is longer than specified in the length byte or in the receive list.
4 (= 04 hex):
The length of the receive telegram does not match the receive list.
5 (= 05 hex):
The type of the receive telegram does not match the receive list.
6 (= 06 hex):
The address of the component in the telegram and in the receive list do not match.
7 (= 07 hex):
A SYNC telegram is expected - but the received telegram is not a SYNC telegram.
8 (= 08 hex):
No SYNC telegram is expected - but the received telegram is one.
9 (= 09 hex):
The error bit in the receive telegram is set.
16 (= 10 hex):
The receive telegram is too early.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- check the electrical cabinet design and cable routing for EMC compliance
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
Cause: A DRIVE-CLiQ communications error has occurred from the Control Unit to the controller extension involved. The nodes
do not send and receive in synchronism.
Fault cause:
33 (= 21 hex):
The cyclic telegram has not been received.
34 (= 22 hex):
Timeout in the telegram receive list.
64 (= 40 hex):
Timeout in the telegram send list.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- replace the component involved.
Cause: A DRIVE-CLiQ communications error has occurred from the controller extension involved to the Control Unit.
Fault cause:
1 (= 01 hex):
Checksum error (CRC error).
2 (= 02 hex):
Telegram is shorter than specified in the length byte or in the receive list.
3 (= 03 hex):
Telegram is longer than specified in the length byte or in the receive list.
4 (= 04 hex):
The length of the receive telegram does not match the receive list.
5 (= 05 hex):
The type of the receive telegram does not match the receive list.
6 (= 06 hex):
The address of the power unit in the telegram and in the receive list do not match.
9 (= 09 hex):
The error bit in the receive telegram is set.
16 (= 10 hex):
The receive telegram is too early.
17 (= 11 hex):
CRC error and the receive telegram is too early.
18 (= 12 hex):
The telegram is shorter than that specified in the length byte or in the receive list and the receive telegram is too early.
19 (= 13 hex):
The telegram is longer than that specified in the length byte or in the receive list and the receive telegram is too early.
20 (= 14 hex):
The length of the receive telegram does not match the receive list and the receive telegram is too early.
21 (= 15 hex):
The type of the receive telegram does not match the receive list and the receive telegram is too early.
22 (= 16 hex):
The address of the power unit in the telegram and in the receive list does not match and the receive telegram is too early.
25 (= 19 hex):
The error bit in the receive telegram is set and the receive telegram is too early.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - carry out a POWER ON (switch-off/switch-on).
- check the electrical cabinet design and cable routing for EMC compliance
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
Cause: Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded.
Fault cause:
32 (= 20 hex):
Error in the telegram header.
35 (= 23 hex):
Receive error: The telegram buffer memory contains an error.
66 (= 42 hex):
Send error: The telegram buffer memory contains an error.
67 (= 43 hex):
Send error: The telegram buffer memory contains an error.
96 (= 60 hex):
Response received too late during runtime measurement.
97 (= 61 hex):
Time taken to exchange characteristic data too long.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy: - check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
- check the electrical cabinet design and cable routing for EMC compliance
- if required, use another DRIVE-CLiQ socket (p9904).
- replace the component involved.
Telegram 3
Telegram 3 transfers the control words 1 and 2 (STW1, STW2), the status words 1 and 2
(ZSW1, ZSW2), the speed setpoint and actual value (NSOLL_B, NIST_B), control word and
status word of encoder 1 (G1_STW, G1_ZSW), and the actual position value 1 and 2 of
encoder 1 (G1_XIST1, G1_XIST2).
Telegram 5
In addition to the values of telegram 3, telegram 5 transfers the values for position deviation
(XERR) and gain factor for the position controller (KPC).
Telegram 102
In addition to the values of telegram 3, telegram 102 transfers the value for the torque reduction
(MOMRED) and the alarm word (MELDW).
3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3='
Telegram 105
In addition to the values of telegram 3, telegram 105 transfers the value for the torque reduction
(MOMRED), the alarm word (MELDW), the values for the position deviation (XERR) and the
gain factor for the position controller (KPC).
3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3=' 3='
Telegram 700
Using the Safety Info Channel (SIC), telegram 700 transfers the safety status word 1B
(S_ZSW1B) and the value for the limitation of the setpoint velocity (S_V_LIMIT_B).
6B 6B9B/,0,7B%
=6:%
Telegram 701
In addition to telegram 700, telegram 701 transfers the following data:
● Via the Safety Control Channel (SCC) the safety control word 1B (S_STW1B) and the safety
control word 3B (S_STW3B).
● Via the Safety Info Channel (SIC) the safety status word 2B (S_ZSW2B) and the safety
status word 3B (S_ZSW3B).
Telegram 750
Telegram 750 is a supplementary telegram for the torque control with the following data:
● The controller sends the additional torque (M_ADD) and the positive and negative torque
limit (M_LIMIT_POS, M_LIMIT_NEG) to the converter.
● The converter sends the actual torque (M_ACT) to the controller.
0B$'' 0B/,0,7
B326
0B/,0,7
B1(*
0B$&7
Telegram 750 can be transferred in addition to telegram 700 or 701. The order can be set in
HW Config.
Telegram 30
Telegram 30 transfers safety control word 1 (S_STW1) and safety status word 1 (S_ZSW1).
3='
6B
67:
6B
=6:
Telegram 901
Telegram 901 will be needed in the future for the Extended Safety Functions and is
meaningless in this version.
Note
Representation of the sending direction Controller -> Converter and Converter -> Controller
The left column always shows the process data that is sent from the controller to the converter
(control words and setpoints).
The process data that is sent from the converter to the controller is displayed in the right column
(status words and actual values).
6DIHW\VWDWXVZRUG%6B=6:%
Bit Meaning
00 Reserved
01 Reserved
02 Reserved
03 Reserved
04 Reserved
05 Reserved
06 Reserved
07 Reserved
08 Reserved
09 Reserved
10 Reserved
11 Reserved
12 Test stop active
13 Test stop requested
14 Reserved
15 Reserved
0HVVDJHZRUG0(/':
Bit Meaning
00 Ramp-up ended
01 Torque utilization < threshold 2
02 nact < speed threshold 3
03 nact < speed threshold 2
04 Reserved
05 Variable signal functions
06 No warning motor overtemperature
07 No warning converter overtemperature
08 Actual/setpoint deviation within the tolerance
09 Reserved
10 Reserved
11 Servo enable
12 Drives ready
13 Pulses enabled
14 Reserved
15 Reserved
A.2 What is the difference between the Emergency Off and Emergency
Stop functions?
"Emergency Off" and "Emergency Stop" are commands that minimize different risks in the
machine or plant.
Solution with the STO is not suitable for safely switching Select STO.
STO safety function off a voltage.
integrated in the
drive
Safety Integrated
The converters comply with the requirements relating to functional safety/safety of machinery.
RoHS
The converters comply with directive 2011/65/EU regarding limiting the use of certain
hazardous substances.
Eurasian conformity
The converter complies with the requirements of the Russia/Belarus/Kazakhstan customs
union (EAC).
Feature Standard
Degree of protection IEC / EN 60034‑5
Cooling 1)
IEC / EN 60034‑6
Type of construction IEC / EN 60034‑7
Connection designations IEC / EN 60034‑8
Noise levels 1)
IEC / EN 60034‑9
Temperature monitoring IEC / EN 60034‑11
Vibration severity levels 1)
IEC / EN 60034‑14
1)
Standard component, e.g. cannot be applied to built-in motors
Relevant directives
The following directives are relevant for SIMOTICS motors.
Eurasian conformity
SIMOTICS motors comply with the requirements of the customs union Russia/Belarus/
Kazakhstan (EAC).
Underwriters Laboratories
SIMOTICS motors are generally in compliance with UL and cUL as components of motor
applications, and are appropriately listed.
Specifically developed motors and functions are the exceptions in this case. Here, it is
important that you carefully observe the contents of the quotation and that there is a cUL mark
on the rating plate!
Quality systems
Siemens AG employs a quality management system that meets the requirements of ISO 9001
and ISO 14001.
Certificates for SIMOTICS motors can be downloaded from the Internet at the following link:
Certificates for SIMOTICS motors (https://support.industry.siemens.com/cs/ww/de/ps/13347/
cert)
A.4 Certifications
The safety functions of the SINAMICS S drive system meet the following requirements:
● Category 3 to DIN EN ISO 13849‑1
● Performance level (PL) d according to DIN EN ISO 13849-1
● Safety integrity level 2 (SIL 2) according to IEC 61508 and EN 61800-5-2
In addition, most of the safety functions of the SINAMICS S have been certified by independent
institutes. A list of currently certified components is available on request from your local
Siemens office.
A.5.1 Overview
The "Transport Layer Security" (TLS) protocol enables encrypted data transfer between a client
and the SINAMICS drive. HTTPS access of the browser to the drive is based on the "Transport
Layer Security" protocol. This section informs you which steps you need to follow to enable
encrypted data transfer between a browser (client) and the SINAMICS (server).
You will find information on the configuration or your IP connection in Section:
"Configuring the IP connection (Page 158)" .
Delivery state
A private key is generated as a file on the device as default configuration when you first use
HTTPS so that you can access the drive via HTTPS in the SINAMICS delivery state. During
an HTTPS access using this key, a warning is issued in the browser that the certificate is
unknown.
Duration of validity
The certificates are valid up to 2030.
After expiration of the validity period, install new valid certificates on all the relevant drives.
Note
Security
The use of a default configuration described in the following is not the most secure way of
transferring data using the HTTPS protocol to your drive with the Web server.
For this reason, it should only be used in secure networks (e.g. your PROFINET below a PLC)
or for direct point-to-point connections on the Service interface X127.
Procedure
1. First open an HTTPS Web server connection to your drive in the browser.
2. The firmware then creates a new server certificate and a private server key from the root
certificate and the private key, if they are not already available. This certificate is
individualized for the IP address of the interface used for the communication.
3. Following this, a warning is issued on the standard browser that the certificate is unknown.
4. Import the server certificate into your standard browser or deactivate the security warnings
for the SINAMICS Websites.
The exact procedure for the import can be found in the online help of the used browser.
Opera
Click "Still continue" in order to be able to communicate via a secure HTTPS connection.
Mozilla Firefox
1. Click "Extended".
The information for the security certificate is displayed.
2. Click "Add exception" in order to be able to communicate via a secure HTTPS connection.
Click "Continue to this website" in order to be able to communicate via a secure HTTPS
connection.
Google Chrome
1. Click "EXTENDED".
The information for the security certificate is displayed.
2. Click "Continue to <IP address>" in order to be able to communicate via a secure HTTPS
connection.
Note
The following list of abbreviations includes the abbreviations and meanings as used for the
SINAMICS.
C
Cable break, 71
F
Certificates Fault, 174
EAC, 748 Acknowledging, 174
EC Declaration of Conformity, 748 Faults and alarms
UL and cUL, 748 Overview, 291
Checksums, 149 Ferrite core
COM (PROFINET link), 167 Attach, 97
Commissioning Forced checking procedure, 144
Assigning drive names in the web server, 118
Basic commissioning, 119
Configuring administrator access, 108 H
Configuring brake control, 125
Hotline, 4
Configuring digital inputs, 127
HTTP, 106
Perform One Button Tuning, 119
HTTPS, 106
Preparing the hardware, 106
Security certificate, 751
Safety Integrated, 136
With security certificate, 750
Setting limits, 124
Test Safety Integrated settings, 148
Concentricity, 184
Configure IP connection, 158
I
Connection type, 106 Interfaces, 106
Control panel IP21 degree of protection, 87
Control mode, 122 IT system, 39
Monitoring mode, 122
L
D LED
Data backup COM, 167
Backing up parameters externally, 154 RDY, 166, 167
Restore factory settings, 155 Line supply type, 39
Restoring the parameter data, 155 List of faults and alarms, 291
DE: Drive End (end with the motor shaft), 183
M S
Memory card, 219 Safety Integrated
Missing enables, 122 Checksums, 149
Commissioning, 136
Diagnostics, 149
N Password, 146
Read-only mode, 148
Navigation, 111
Status, 149
NDE: Non Drive End, 183
Safety Integrated Basic Functions
Neutral conductor, 39
Configuring, 68
SBC, 61
SS1, 63
O SS1E, 65
OCC, 118 SS1-t, 63
One Cable Connection, 118 STO, 58
Safety Integrated Functions
Basic Functions, 57
P Overview, 57
Safety notes
Parameter list
Electrical installation, 93
Filtering, 132
Saving
Parameters
Permanently (non-volatile), 161
Configuring the parameter list, 130
SBC (Safe Brake Control), 61
Filtering the parameter list, 132
Acceptance test, 79
Overview, 225
Sequence diagram, 62
Structure, 225
SD card, (Article number)
Password
Self-configuration, 118
Changing, 157
Siemens Service Center, 4
Defining, 157
Signal states, 166
Deleting, 157
Smooth running, 184
Password for Safety Integrated, 146
Spare parts package, 221
Power distribution systems, 39
SS1 (Safe Stop 1)
PROFIsafe telegrams, 740
Acceptance test, 80
Protective conductor, 39
SS1E
Sequence diagram, 66
SS1-t
R Sequence diagram, 64
Rating plate, 27 Standard telegrams
RDY (Ready), 166, 167 Telegram 102, 737
Response times, 73 Telegram 105, 738
Basic Functions via PROFIsafe (CU310‑2 and Telegram 3, 737
CU320‑2), 74 Telegram 5, 737
Basic Functions via terminals on the Control Unit Standards
and the Motor Module, 73 EN 61800-3, 746
RoHS, 748 Status
Safety functions, 149
Status display
On the converter, 165
Via LEDs, 165
V
Vibration response, 183
W
Web server
Access rights, 114
Activating/deactivating time synchronization, 160
Assigning a device name, 118
Automatic logout, 117
Basic commissioning, 119
Call the control panel, 122
Changing the password, 157
Configure IP connection, 158
Configuring brake control, 125
Configuring digital inputs, 127
Configuring user accounts, 156
Defining a new password, 157
Deleting the password, 157
Diagnostics of the communication settings, 152
Editing the parameter list, 130
Filtering the parameter list, 132
Login, 116
Logout, 117
Navigation, 111
Siemens AG
Digital Factory
Motion Control
Postfach 3180
D-91050 Erlangen
Germany
For additional
information on the
SINAMICS S210,
scan the QR code