CU240S to CU240E 2 Replacement
CU240S to CU240E 2 Replacement
CU240S to CU240E 2 Replacement
(Firmware V4.4)
SINAMICS G120
Clicking the link below directly displays the download page of this document.
http://support.automation.siemens.com/WW/view/en/55644272
Question
What do I have to observe if I wish to replace a member of the CU240S family
(CU240S, CU240S DP, CU240S DP-F, CU240S PN or CU240S PN-F) of
SINAMICS G120 by a CU240E-2 (Firmware V4.4)?
Answer
To respond to this question with the appropriate amount of detail, follow the
instructions and notes listed in this document.
Table of contents
1 Presentation of SINAMICS G120 CU240E-2...................................................5
1.1 Restrictions between CU240S and CU240E-2 ...................................6
1.2 Adaptations that must be made when making the changeover ...........7
2 Hardware.........................................................................................................9
2.1 Dimensions .......................................................................................9
3 IO interface ...................................................................................................10
3.1 Terminal assignment ....................................................................... 10
3.2 Digital inputs....................................................................................11
3.2.1 Changes to the number of digital inputs ........................................... 11
3.2.2 Changes to the fail-safe inputs (F-DI)............................................... 11
3.2.3 Transferring the status of the F-DI via PROFIsafe ............................ 11
3.2.4 Changing the reference potential and PNP / NPN logic .................... 11
3.2.5 Changed BICO interconnection of the digital inputs..........................12
3.2.6 Simulating the digital inputs ............................................................. 12
3.2.7 Monitoring the load/speed via a digital input..................................... 12
3.3 Digital outputs..................................................................................13
3.3.1 Modified parameter numbers ........................................................... 13
3.3.2 Hardware change DO1 .................................................................... 13
3.4 Analog inputs...................................................................................13
3.4.1 Modified factory setting.................................................................... 13
3.4.2 Changed ADU dead zone (p761) ..................................................... 13
3.4.3 Simulation of the analog inputs ........................................................ 14
4 Communication ............................................................................................15
4.1 GSD files.........................................................................................15
4.2 Routing through a CPU.................................................................... 15
4.3 Teleservice......................................................................................16
4.3.1 Teleservice via a CPU ..................................................................... 16
4.3.2 Teleservice directly to the fieldbus ................................................... 17
4.4 Slave-to-slave traffic ........................................................................ 18
4.5 Direct HMI connection ..................................................................... 18
5 Local operator control via BOP-2 or IOP..................................................... 19
5.1 Manual operation with BOP-2 / IOP ................................................. 19
5.2 Status signals of the BOP-2 / IOP operator control panels................ 19
6 Parameterization ..........................................................................................20
6.1 Elimination of closed-control modes................................................. 20
6.2 Changed reference quantities .......................................................... 20
6.3 Fixed setpoints that can be freely used ............................................ 20
6.4 Parameterizing the command and setpoint sources ......................... 20
6.5 Expanding the command/drive data sets.......................................... 20
6.6 Change for the second ramp function via JOG ramp-function
generator.........................................................................................21
6.7 U/f points along a characteristic (U/f with programmable
characteristic) ..................................................................................21
6.8 Speed-dependent controller adaptation............................................ 21
6.9 Operating hours counter .................................................................. 21
6.10 Changes to the braking chopper ...................................................... 21
6.11 Expansion of the motor holding brake function ................................. 21
6.12 Changes to the free function blocks (FFBs)...................................... 22
6.13 Changes to the phase failure monitoring .......................................... 22
With the changeover from CU240S to CU240E-2, you must observe the following
restrictions:
- Digital inputs:
o The CU240E-2 family has only 6 digital inputs, contrary to the CU240S
family
- Fail-safe inputs:
o The CU240E-2 family has no separate F-DIs, contrary to the CU240S
family. The F-DIs of the CU240E-2 are formed from two standard
digital inputs
- Encoder interface:
o The CU240E-2 family has no interface for a speed controller, and as a
consequence, only supports encoderless (sensorless) closed-loop
2 Hardware
2.1 Dimensions
Changed dimensions between the CU240S and CU240E-2
Width:
No change
Height without fieldbus connector (177 mm for CU240S, with shield connection
plate, 220mm):
199mm
with shield connection plate, 255mm
Depth (63mm for the CU240S with/without BOP):
39mm without BOP-2 / IOP
50mm with BOP-2
60mm with IOP
CU240S CU240E-2
3 IO interface
3.1 Terminal assignment
The terminals of the CU240S will be compared with those of the CU240E-2 family.
Changes between the CU240S and CU240E-2 have been color coded.
CU240S CU240E-2
Function Terminal Name Terminal Name Note
1 +10V OUT 1 +10V Out
Power supply AI
2 0V OUT 2 GND OUT
3 AI0+ 3 AI0+
Analog input AI0 Can also be used as additional digital input (DI11)
4 AI0- 4 AI0-
Digital input 0 5 DI0 5 DI0 For the CU240E-2 F and E-2 DP F, the two DIs can be re-parameterized
Digital input 1 6 DI1 6 DI1 to form F-DI0
Digital input 2 7 DI2 7 DI2 For the CU240E-2 F and E-2 DP F, the two DIs can be re-parameterized
Digital input 3 8 DI3 8 DI3 to form F-DI1
For the CU240E-2 and E-2 D the two DIs can be re-parameterized to form
Digital input 4 16 DI4 16 DI4
F-DI0
For the CU240E-2 F and E-2 DP F the two DIs can be reparameterized to
Digital input 5 17 DI5 17 DI5 form F-DI2
18 DO0 NC 18 DO0 NC
Relay output DO0 19 DO0 NO 19 DO0 NO
20 DO0 COM 20 DO0 COM
21 DO1 NO 21 DO1+
Relay/digital output DO1 Changeover from relay to transistor output
22 DO1 COM 22 DO1-
23 DO2 NC 23 DO2 NC
Relay output DO2 24 DO2 NO 24 DO2 NO
25 DO2 COM 25 DO2 COM
26 AO1+ 26 AO1+
Analog output AO1
27 AO1- 27 GND
Reference potential for +24V 28 U0V 28 GND
Pin 1 0V
29 RS485 -A Pin 2 RS485P
RS485 interface RS485 interface for CU240E-2 and CU240E-2 F via separate connector
30 RS485 -B Pin 3 RS485N
Pin 4 Shield
Contrary to the CU240S (up to 9 DIs), the CU240E-2 family only has 6 digital
inputs. However, the two analog inputs, if these are not required, can be used as
two digital inputs.
The CU240E-2 family has, contrary to the CU240S family, no separate fail-safe
digital inputs. For the CU240E-2, the F-DIs are formed from two standard DIs (see
Chapter 3.1)
- CU240E-2, CU240E-2 DP and CU240E-2 PN up to 1 F-DI
- CU240E-2 –F, CU240E-2 DP-F and CU240E-2 PN-F up to 3 F-DIs
New function
Using PROFIsafe, for the CU240E-2 DP-F, the status of the F-DIs can be
transferred to the F-CPU in a safety-relevant fashion so that these are available as
distributed F I/O. For details, refer to Chapter 7
The reference potential terminal 69 on the CU240S was, for the CU240E-2,
distributed over two terminals (terminals 69 and 34). Also refer to Chapter 3.1.
Terminal 69: Reference potential for DI0, DI2 and DI4
Terminal 34: Reference potential for DI1, DI3 and DI5
The PNP / NPN logic changeover of the digital inputs is, for the CU240E-2, no
longer realized by parameterization (CU240S: p725) and the wiring; it is only
defined using the input wiring.
For an internal power supply
- For PNP logic: Connect terminals 34 and 69 with terminal 28.
- For NPN logic: Connect terminals 34 and 69 with terminal 9.
For an external power supply
- For PNP logic: Connect terminals 34 and 69 with the system ground.
- For NPN logic: Connect terminals 34 and 69 with the system 24 V.
For more information refer to the List Manual Link (Chapter 2, function diagram
2220).
Previously, the digital inputs for BICO interconnection had to be enabled using the
value 99; this is now no longer required. The interconnection can now be made
directly without having to use p701…p706 or p701...p709 (no longer available in
CU240E-2). In addition, inverted signals of the digital inputs are available.
CU240S CU240E-2
New function
The digital inputs can now be simulated for test purposes using the STARTER
parameterizing software.
New function
Using this function, load failure can be monitored as well as a speed deviation. For
details, refer to the operating instructions Link (Chapters 7.9.5 and 7.9.6).
The parameter numbers of the DOs are shifted in the expert list by one position (for
example DO0: CU240S = p731, CU240E-2 = p730).
DO1 (terminal 21 / 22) was changed from being a relay output (CU240S) to a
transistor output (CU240E-2).
The factory setting was changed from 0 – 10V (CU240S) to +/- 10V (CU240E-2).
This parameter is no longer shown in the graphic display, but is still in the expert
list.
CU240S
Using this function in the CU240S, if the analog values around 0 V are
suppressed, then this function can only be implemented by using FFBs (free
function blocks). We are presently working on an integrated solution.
New function
Now, the analog inputs can be simulated for test purposes using the STARTER
parameterizing software.
4 Communication
Existing programs to control a SINAMICS G120 with CU240S via a fieldbus from a
PLC, in most cases can still be used for the CU240E-2. For example, if parameters
are accessed via cyclic or non-cyclic communication, then the only change that is
required is as a result of the modified parameter numbers.
In order to use the new or extended safety functions, the safety programs in an F-
CPU must be correspondingly adapted (refer to Chapter 7)
4.3 Teleservice
4.3.1 Teleservice via a CPU
A Teleservice Adapter II and a CPU, which is listed under Routing (Chapter 4.2) and which supports data set routing, are required.
With this configuration, the Teleservice Adapter is directly connected to the fieldbus. This is why it is of no significance that the CPU
supports data set routing.
- Presently, not possible with Profibus. Presently, the Teleservice Adapter II does not support this functionality.
- For Profinet, with a CU240E-2 PN, it is possible using the Teleservice Adapter IE Basic.
BOP BOP-2
6 Parameterization
It is not possible to directly migrate from CU240S projects to CU240E-2 as a result
of the modified parameter structure.
The drive must be recommissioned using BOP-2, IOP or STARTER.
6.6 Change for the second ramp function via JOG ramp-
function generator
It is no longer possible to use the JOG ramp-function generator to implement a
second ramp function.
However, when using the data set changeover (DDS), up to 4 different
parameterizable ramp functions are now available. The data set changeover can
be implemented in operation via digital inputs or via the fieldbus. For details, refer
to the operating instructions Link (Chapter 7.11).
Writing data to an MMC / SD card has been significantly simplified for the CU240E-
2. Parameter changes are automatically saved to the memory card.
For details, refer to the Operating Instructions in Chapter 4.6 Link and FAQ Link
7 Safety functions
The safety functions known from the CU240S have been expanded. The following
table provides an overview of the available safety functions and how they are
possibly controlled.
Information:
- Just as before, speed acquisition using a speed encoder is not required for
these safety functions.
- STO is permissible for all applications, where Emergency Stop functionality
is required.
- SS1, SLS, SSM and SDI are not permissible for loads that drive the motor
or that are continuously in the regenerating mode (also referred to the
function manual, Safety Integrated, Chapter 2.2 Link).
- The F-DIs are formed by combining 2 standard DIs through the appropriate
parameter assignment (also see Chapter 3.1).
The SS1 safety function was extended as follows when compared to the CU240S
family.
- Braking the motor after activating SS1 can now be set using the following
parameter assignment:
Braking ramp monitoring:
After selecting SS1, SINAMICS G120 automatically brakes
along the OFF3 ramp. The deceleration is monitored using
the SBR ramp (Safe Brake Ramp). STO is activated when
standstill is reached
Acceleration monitoring:
After selecting SS1, SINAMICS G120 does not decelerate
along the OFF3 ramp, but can be independently
decelerated.
The speed is safely monitored to ensure that the drive does
not accelerate.
When the "shutdown velocity/speed SS1“ is reached, or
after the "SS1 delay time" has expired, then STO is
activated
- The SS1 ramp time (brake ramp monitoring mode) was increased, for the
CU240S (99s referred to 200Hz) in the CU240E-2 family to 1000s (referred
to the reference speed, e.g.1500 rpm).
Safely and reliably stopping high moments of inertia.
- For the CU240S family, it was possible to interrupt/cancel SS1 by
withdrawing the SS1 request before reaching the SS1 standstill detection
frequency. This is no longer possible for the CU240E-2 family. The SS1
request remains active until STO is internally activated.
The SLS safety function was extended and revised as follows when compared to
the CU240S family.
- The various SLS modes of the CU240S family have been integrated in the
CU240E-2 family into one "mode". Simplify commissioning and the
possibility of implementing new safety concepts
- With the CU240E-2 DP F and CU240E-2 PN-F for control via PROFIsafe
there are now 4 SLS limit values available that can be parameterized.
New safety concepts can be implemented
- When activating SLS at standstill, current must flow through the motor
within 5 seconds. For the CU240S family, it is no longer necessary that a
minimum speed is reached during these 5 seconds. Simplifies the
control
- The behavior of the SINAMICS G120 when activating SLS (automatic or
manual speed reduction) can be set using the SS1 brake ramp or
acceleration monitoring.
- The response to a limit value violation when SLS is active can be selected
to either be a STOP A (STO) or STOP B (SS1) (CU240S, only STO is
possible) In the case of a fault, the motor can now be safely braked and
no longer coasts down unbraked.
This safety function prevents the motor being operated in an unsafe direction of
rotation. A speed encoder is not required for this safety function.
New safety concepts can be implemented, for example, staying in a
hazardous/dangerous area while a part of the system is being moved out of this
hazardous/dangerous area or setting-up operation with a safely inhibited direction
of rotation
* Selecting whether byte 0 / bit 4 or byte 1 / bit 0 should be used to control SLS is realized through the
appropriate parameter assignment
* Extended Safety functions (CU240E-2 –F, CU240E-2 DP-F and CU240E-2 PN-F)
* Extended Safety functions (CU240E-2 –F, CU240E-2 DP-F and CU240E-2 PN-F)
The PROFIsafe telegram 900 differs from the PROFIsafe telegram 30 in so much,
that for this telegram, the status of the fail-safe digital inputs is also transferred
(byte 3, bit 0…2)