Escolar Documentos
Profissional Documentos
Cultura Documentos
Guide to updating firmware from versions V4.3.x through V4.6.x to V4.7.x for SINAMICS S120 with CU310-2 and CU320-2
Contents
1 Hardware requirements ........................................................................................................................................................... 3
1 HARDWARE REQUIREMENTS
The hardware release of the Control Units determines which firmware versions can be installed.
The CU310-2DP (order number 6SL3040-1LA00-0AA0) and CU310-2PN (order number 6SL3040-1LA01-0AA0) are not supported
by firmware versions lower than V4.4.
Any hardware release of the CU320-2DP with order number 6SL3040-1MA00-0AA0 can be upgraded to device version V4.6 /
V4.7.
The CU320-2 PN with order number 6SL3040-1MA01-0AA0 is supported by firmware version V4.4 and higher.
The hardware version of your Control Unit is specified on the type plate:
1
The 2GB CompactFlash cards are an essential requirement for use of the feature Powerfail-proof firmware update via web
server.
2.1 Preconditions
The starting situation involves a SINAMICS S120 converter on which the installed firmware version is to be changed.
If the firmware has a new device version number (e.g. if you are updating versions V4.3.x through 4.6.x to V4.7.x), you must
also select the relevant drive unit in the STARTER project tree and then select the required device version by clicking on menu
options Target device Device version with the right mouse button:
2
SSP: SINAMICS Support Package:
The appropriate SSP for the firmware is stored in subdirectory ADDON\SINAMICS\ES_TOOL\SSP in the zip file containing the
new firmware
Fig. 2-2: STARTER menu "Device version" with new update version selected
NOTICE
All project data and parameters on the CompactFlash card are deleted by the upgrade process described below!
Insert this CompactFlash card into the reader connected to/in the PC/PG
Use Windows Explorer to move the contents of the temporary directory to the CompactFlash card.
Execute the command Load to File System in the context menu (right mouse button) (see Fig. 2-3)
In the dialog which now appears (see Fig. 2-4), select the drive / main directory of the CompactFlash card under Select
target and then start the project export to the CompactFlash card.
The project will now be transferred with all drive parameter settings including DCC libraries (if applicable) to the CompactFlash
card.
Alternatively, you can copy the project to the CompactFlash card at a later time (when you are connected online to the drive
unit) using command Download followed by "Copy RAM to ROM".
During this process, the RDY (READY) LED on the Control Unit flashes orange at a frequency of 0.5 Hz.
Fig. 2-5: STARTER alarm display while updating of component firmware is in progress
When the firmware update process is complete, the LED flashes faster at 2 Hz.
Warning 1007 is active for the upgraded components and is displayed in the STARTER alarm window:
The current firmware versions of the modules are displayed in the STARTER version overview:
3.1 Preconditions
Physical network connection (Ethernet) between the Control Unit and the PC/PG
The following guide explains the steps you need to take in order to update firmware via the SINAMICS web server on a
Windows PC.
The process of creating a network connection using the commissioning interface is described by way of an example below:
Ethernet
connection
3
The firmware update process can be used, for example, to import hotfixes or service packs of version V4.6
Open the properties box for this network connection by clicking on the relevant command in the context menu (right
mouse button)
Make a note of the existing settings so that you can restore them later!
Select the settings as they are shown in Fig. 3-4 and confirm by clicking on the OK button:
Note
In the steps described above, it has been assumed that the network settings for the commissioning interface are still the same
as the factory settings (p8901 – p8904). If this is not the case, an IP address contained in the same subnet as the IP address of
the Control Unit must be entered in the dialog shown in Fig. 3-4 .
Check the network connection and the network settings on the PC/PG and the Control Unit if the ping is unsuccessful (see Fig.
3-5).
If the Ping worked, but the start page of the web server is not displayed, then the problem is probably attributable to one of
the following:
2. The proxy server settings of the web browser are not correct
The method of changing proxy server settings varies depending on the web browser product and can differ from version to
version of the same web browser product. Consult the Help function of the relevant browser product for instructions.
IMPORTANT
Before you make any changes, make a note of the existing settings so that you can restore them after the firmware has been
updated!
Fig. 3-9: Start page of web server when Control Unit is not parameterized
Set up a link to the Control Unit in STARTER (see also Chapter 2.3.2)
Select the relevant drive (not the Control Unit) in the project navigator
In the context menu (right mouse button), select the command "Web server".
Now activate the web server and the user administrator in the web server dialog:
Fig. 3-11: Activating the web server and web server users in STARTER
In the box Send new update data , select the zip file containing the new firmware on your PC/PG:
Click on button Send update data to start the firmware update process:
Now be patient and follow the status messages / instructions displayed by the web server.
After you have restarted the Control Unit (if necessary), refresh the web page displayed for the drive in the web
browser by pressing key F5 .
You can now check whether the firmware update was successful / unsuccessful by examining the version data
displayed on the web server start page and by selecting tab Messages and Logs Diagbuffer (log in using your
administrator ID):
Fig. 3-15: Checking the success of the firmware update in the diag buffer
Any active messages are displayed on tab Messages and Logs Alarms Drive where they can also be acknowledged.
Messages which cannot be acknowledged must be processed accordingly.