Updating SIMOTION Devices SIMOTION. SIMOTION SCOUT Updating SIMOTION Devices. Preface. Overview. Updating 2. Restoring 3.

Transcription

1 Preface Overview 1 SIMOTION SIMOTION SCOUT Updating 2 Restoring 3 A Appendix A Operating Instructions 02/2012

2 Legal information 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 with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken. CAUTION without a safety alert symbol, indicates that property damage can result if proper precautions are not taken. NOTICE indicates that an unintended result or situation can occur if the relevant information is not taken into account. 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. Siemens AG Industry Sector Postfach NÜRNBERG GERMANY Copyright Siemens AG All rights reserved

3 Preface Content This document is part of the documentation package Service and Diagnostics. Scope of validity This manual is valid for SIMOTION SCOUT product level V4.3: SIMOTION SCOUT V4.3 (Engineering System of the SIMOTION product range) SIMOTION Kernel V4.3 SIMOTION Cam, Cam_ext and TControl technology packages Sections in this manual This manual describes a simple way of exchanging the configuration or firmware of one or more SIMOTION devices. This procedure is called updating. Overview General overview of update data and media, of update scenarios, and of the people involved Updating Description of the individual stages of updating Restoring Information about restoring Operating Instructions, 02/2012 3

4 Preface SIMOTION Documentation An overview of the SIMOTION documentation can be found in a separate list of references. This documentation is included as electronic documentation in the scope of delivery of SIMOTION SCOUT. It comprises 10 documentation packages. The following documentation packages are available for SIMOTION V4.3: SIMOTION Engineering System SIMOTION System and Function Descriptions SIMOTION Service and Diagnostics SIMOTION IT SIMOTION Programming SIMOTION Programming - References SIMOTION C SIMOTION P SIMOTION D SIMOTION Supplementary Documentation Hotline and Internet addresses Additional information Click the following link to find information on the the following topics: Ordering documentation/overview of documentation Additional links to download documents Using documentation online (find and search in manuals/information) Please send any questions about the technical documentation (e.g. suggestions for improvement, corrections) to the following address: docu.motioncontrol@siemens.com My Documentation Manager Click the following link for information on how to compile documentation individually on the basis of Siemens content and how to adapt this for the purpose of your own machine documentation: 4 Operating Instructions, 02/2012

5 Preface Training Click the following link for information on SITRAIN - Siemens training courses for automation products, systems and solutions: FAQs Frequently Asked Questions can be found in SIMOTION Utilities & Applications, which are included in the scope of delivery of SIMOTION SCOUT, and in the Service&Support pages in Product Support: Technical support Country-specific telephone numbers for technical support are provided on the Internet under Contact: Operating Instructions, 02/2012 5

6 Preface 6 Operating Instructions, 02/2012

7 Table of contents Preface Overview Data flow and handling update data Update data, update archive, and update media Update data behavior within a SIMOTION device Assigning update data to devices Single and multiple updates Device-specific update media Transferring device-specific user data to the update data Updating Overview Creating update data using SIMOTION SCOUT Creating update data with the Device Update tool Creating update data, including copying to a USB memory stick Creating update data, including copying to a CF/MMC card Creating update data, including creating an IT DIAG file Creating update data as an update archive Copying to the update media on the basis of an update archive Copying to an update medium without SIMOTION SCOUT Transferring the update data Copying data to a USB memory stick Copying data to a CF/MMC card Creating an IT DIAG file and copying update data Transferring update data to the SIMOTION device Behavior of the retain data during updating Receiving unit data SIMOTION device status during updating Transferring update data from the update medium to SIMOTION devices Updating a module with a USB memory stick Updating a module with a CF/MMC card Updating a module with an IT DIAG file Possible error messages for the Device Update tool Restoring Restoring a SIMOTION device SIMOTION device status during restoring Particular aspects of restoring SIMOTION devices...81 Operating Instructions, 02/2012 7

8 Table of contents A Appendix A A.1 Restoring the original status of a USB memory stick Index Operating Instructions, 02/2012

9 Overview 1 SIMOTION offers a convenient solution for updating SIMOTION devices or SIMOTION projects for machine manufacturers and machine operators. Updating does not simply refer to an update to a higher version of firmware; rather, in general terms it refers to switching to a defined configuration, e.g. a project update. It is also possible to return (restore) to a previous configuration. Update or restore procedures can easily be performed on SIMOTION devices locally or remotely. The data can be imported to a SIMOTION device via a portable, handy storage medium or a communication connection. Options and advantages There is an extensive range of options available for updating SIMOTION devices. These include, for example: User-friendly creation of update data via SIMOTION SCOUT with the aid of the Device Update tool (at the machine manufacturer's site) SIMOTION device updates independent of time and place (without SIMOTION SCOUT, at the machine operator's site) Update data can be sent from the machine manufacturer to the machine operator via e- mail or post No need for license-key handling, i.e. the licenses are retained or are updated at the same time. Retain data is retained. An update which has been imported can be discarded again, and the previous configuration restored. You can update either a single SIMOTION device or multiple devices from one or more SIMOTION projects. You can limit the update to configuration subsets, e.g. only project data. Single or multiple updates Various update scenarios are possible: When performing a single update, only one SIMOTION device is updated, while one or more SIMOTION devices from one or more projects can be updated when performing a multiple update. Operating Instructions, 02/2012 9

10 Overview Update data Update data is data that is created via SIMOTION SCOUT on the basis of one or more SIMOTION projects. The update data contains all the information required for updating or restoring the data on a SIMOTION device. This includes: SIMOTION project Technology packages User data (unit data, IT DIAG data) Firmware Handling update data The update data is created by the machine manufacturer's application developer using SIMOTION SCOUT. The update data can then be handled flexibly depending on both the SIMOTION device (SIMOTION C, D, or P) and the customer requirements: Creating update data and then copying them to a storage or update medium: CF/MMC card USB memory stick SIMOTION IT DIAG file or Creating an update archive Alternatively, the update data can be created and stored in an archive on the computer, so that it can be imported to an update medium that is compatible with the SIMOTION device at a later point in time. The data can be transferred to an update medium at either the machine manufacturer's site or the machine operator's site. For this purpose, the machine manufacturer transfers their update archive to the users at the machine operator's site. The user imports the update data into the SIMOTION device(s) on an operator-guided basis, without any involvement by the application developer, thereby updating the SIMOTION device(s) (SIMOTION SCOUT does not need to be available on-site). 10 Operating Instructions, 02/2012

11 Overview 1.1 Data flow and handling update data 1.1 Data flow and handling update data The machine manufacturer's application developer creates the update data using the SIMOTION SCOUT engineering system. He or she writes the SIMOTION applications and puts them into operation. The user at the machine operator's site carries out service work on the machine. The user receives the update data from the application developer and transfers them to the machine. There is no need for SIMOTION SCOUT to be available on-site in order to transfer the update data to the SIMOTION device or to update a SIMOTION project. The user at the machine operator's site can import the previously created update data, which are located on an update medium, to the SIMOTION device. The figure below provides an overview of how the update data are handled. Update media are a CF/MMC card, a USB memory stick, and an IT DIAG file. Alternatively, the user has the option of creating and storing update data in an update archive, and then creating the update medium at a later point. This can be carried out by either the application developer at the machine manufacturer's site or by the user at the machine operator's site. The update data can be imported to an update medium immediately after they have been created by the application developer. The CF/MMC card and USB memory stick types of update media can be sent to the machine operator via post or IT DIAG file, or electronically via the update archive. The update data are generally transferred to the SIMOTION devices by the user at the machine operator's site. Operating Instructions, 02/

12 Overview 1.1 Data flow and handling update data Figure 1-1 Data flow and handling of the update data at the machine manufacturer's and machine operator's sites 12 Operating Instructions, 02/2012

13 Overview 1.2 Update data, update archive, and update media 1.2 Update data, update archive, and update media Update data is required to update a SIMOTION device or SIMOTION project. The newly created update data can be stored in an update archive or saved onto an update medium immediately. The advantage of the update archive or the update media is that the update data created at the machine manufacturer's site can be used by the machine operator anywhere and at any time. SIMOTION SCOUT is not required in order to transfer the update data on-site. Update data The configuration is determined on the basis of the composition of the update data. Update data is all the data required for an update procedure. The update data is created using SIMOTION SCOUT. The update data contains the following data: Firmware (FW): The firmware comprises all the firmware components that are required to operate the respective SIMOTION device (e.g. drive FW, CBE FW, TM FW, BIOS, etc.) Project data: The project data contains all the data required to operate the respective SIMOTION device. SIMOTION D also contains the drive configuration for the SINAMICS Integrated and the CX32/CX32-2. Technology packages (TP) User data (e.g. HTML pages, SSL keys, SIMOTION project for data storage on a memory card, IT DIAG data, JAVA programs, and unit data sets) SCOUT project archive (for data storage on the memory card) It is assumed, in principle, that all of the update data components referred to above are to be updated. However, only individual update data components can be updated, e.g. only the technology packages. This is at the discretion of the user and is defined when the update data is created. Note For SIMOTION P, there are currently only plans to update the project data, technology packages and user data. The firmware cannot be updated because of its dependence on other Windows components. Update archive The update data created using SIMOTION SCOUT is stored in an update archive if it is not imported to an update medium. The update archive is a directory tree in which all of the update data is saved. Operating Instructions, 02/

14 Overview 1.2 Update data, update archive, and update media Update media The term "update media" is used to refer to storage media, on which the update data is saved before being imported to the SIMOTION devices to be updated. The update media used with SIMOTION are a USB memory stick, a CF/MMC card, and an IT DIAG file. The choice of update media depends on the SIMOTION devices to be updated. In order to upgrade an individual device for SIMOTION C or SIMOTION D, the update can be copied to a CF/MMC card, or an IT DIAG file (also for several devices) can be created. SIMOTION D4x5/D4x5-2 also supports the option of using a USB memory stick as the update medium. The USB memory stick can be used to update one or more SIMOTION devices. With SIMOTION P, you can choose to update one or more devices using either a USB memory stick or an IT DIAG file. To find an overview of which update medium is suitable for which SIMOTION device, go to: Device-specific update media (Page 21) 14 Operating Instructions, 02/2012

15 Overview 1.3 Update data behavior within a SIMOTION device 1.3 Update data behavior within a SIMOTION device Each SIMOTION device has a memory card containing the most important data for the device, such as firmware, technology packages, project data, and saved retain data. In the case of SIMOTION D this is the CF card (Compact Flash Card), and in SIMOTION C the MMC (Micro Memory Card), while for SIMOTION P the memory card takes the form of a virtual memory card on the hard disk. If a SIMOTION device is updated, the data on the memory card in the SIMOTION device behave as follows: Figure 1-2 Update data behavior within a SIMOTION device Operating Instructions, 02/

16 Overview 1.3 Update data behavior within a SIMOTION device 1. The update data are transferred from the update medium to the memory card in the SIMOTION device. (USB memory stick, IT DIAG). In the case of a CF/MMC card, this mechanism takes place via a CF/MMC adapter. 2. The existing data are then saved on the memory card. 3. The update data are applied when the device is restarted. 4. The memory card now contains both the update data and, concurrently, the saved data from the previous configuration. 5. In the event of an error, or if the new application does not meet your requirements, you can revert back to the saved data. These are activated when you perform a restore function, overwriting the update data. Note The current configuration data are saved as restore data when updating. The SIMOTION device has only one backup. If the same update data are imported twice by mistake, the backed up restore data will also be overwritten. In order to back up data over a longer period of time, the update archive can be backed up separately (onto a DVD, for example). 16 Operating Instructions, 02/2012

17 Overview 1.4 Assigning update data to devices 1.4 Assigning update data to devices The device name which was saved in the project is contained in the update data. This name is used for assigning the update data to the relevant device. The name is saved persistently on the device. Since the name is saved persistently within the SIMOTION device, a corresponding device assignment takes place during the update. Operating Instructions, 02/

18 Overview 1.5 Single and multiple updates 1.5 Single and multiple updates Update data can be created for both a single SIMOTION device or multiple SIMOTION devices relating to one or more SIMOTION projects. During multiple updates, i.e. when updating at least two SIMOTION devices, it is imperative that device names are assigned. If the device names in the update data do not match the persistently saved names of the devices to be updated, the update cannot take place. An exception to this is the single update of a device that has not yet been assigned a persistently saved name. In this case, the device receives its name from the update data. In a single update scenario, it is also possible to force an update if the device names do not match. Single update Update data for a single SIMOTION device are created during a single update. This scenario is recommended in the case of large projects, for example, in which only one SIMOTION device from a project is to be updated. 18 Operating Instructions, 02/2012

19 Overview 1.5 Single and multiple updates The following scenarios are depicted in the figure: The SIMOTION device to be updated does not have a name. The update is carried out and the SIMOTION device to be updated is assigned the SIMOTION device name D435_1 from the update data. The SIMOTION device to be updated and the SIMOTION device from which the update data have been created have the same name. The data are updated without any query. The SIMOTION device to be updated and the SIMOTION device from which the update data originate do not share the same name. It is assumed, in principle, that they are two different SIMOTION devices, and that the data are not updated. If there is an explicit request for the data from SIMOTION device D435_1 to be applied by SIMOTION device D435_4, the Force update option can be selected. This means that the SIMOTION device is assigned the complete set of new data, including the device name. The option to force an update only exists when updating a single SIMOTION device. See also: Assigning update data to devices (Page 17) Multiple update Where multiple updates are concerned, the update data are created for at least two, if not all, of the SIMOTION devices from one or more SIMOTION projects. Either update data components of a project or the entire project can be updated. This is at the discretion of the user. However, it is imperative that the devices from the update data and the devices to be updated have the same names. Update data from two different SIMOTION devices with the same name (e.g. from different projects) may not be created at the same time because the data cannot be assigned. See also: Assigning update data to devices (Page 17) The graphic below shows the pool of update data which has been created for the SIMOTION D435_1, D435_2, and D435_3 devices, and which is still located on an update medium. Where multiple updates are concerned, the device names from the update data must match the persistently saved device names from the SIMOTION devices to be updated, in order to guarantee that the update data are assigned correctly. If this is not the case, the update cannot be performed. Operating Instructions, 02/

20 Overview 1.5 Single and multiple updates 20 Operating Instructions, 02/2012

21 Overview 1.6 Device-specific update media 1.6 Device-specific update media The table below provides an overview of which update media can be used for which SIMOTION devices, and in which update scenarios: Table 1-1 Overview of the update scenarios in combination with SIMOTION devices and update media SIMOTION device USB memory stick IT DIAG CF/MMC C C240 / C240 PN - Single/multiple update Single update D4x5/D4x5-2 Single/multiple update Single/multiple update Single update D410 - Single/multiple update Single update P320/P350 Single/multiple update Single/multiple update - Note Requirement for updating or restoring: SIMOTION SCOUT V4.1 SP2 or higher Firmware on the SIMOTION device to be updated, V4.1 SP2 or higher Update data must contain firmware V4.1 SP2 or higher (if firmware is selected). Note The SIMOTION device is started from the USB memory stick when updating devices via a USB memory stick. For this reason, a bootable USB memory stick must be used. We recommend SIMATIC memory sticks. Due to the rapid developments within the market for USB memory sticks, it is not possible to make any additional recommendations. For information on this, go to: Note Because of the size of the memory card, the update or restore function is not possible for the SIMOTION C With the SIMOTION C240, a 64 MB MMC must be used for the update or restore function because a 32 MB MMC (supplied V4.0 HF2) does not have sufficient memory space. With the SIMOTION C240 / C240 PN, the function is partly limited due to the memory space available on the MMC (not with large projects). For information on this, go to: Operating Instructions, 02/

22 Overview 1.7 Transferring device-specific user data to the update data 1.7 Transferring device-specific user data to the update data Definition of user data The following data is not part of the SIMOTION project within the context of updating and must, therefore, be provided by the user: SIMOTION IT (IT_DIAG) IT_CONF Data for configuring the web interface (e.g. WEBCFG.XML) SETTINGS Settings for watch tables and traces from IT DIAG IT_FILES User websites JAVA_PRG Java programs (*.class, *.jar) JAVA_DAT Files which are used from Java Unit data sets (UDS) In the unit data sets, values from unit variables (e.g. machine data from commissioning) can be saved during runtime in data sets on the memory card using _save/_export UnitDataSet. These are uniquely identified by the unit name and data set number (refer also to the Basic Functions Function Manual, section "Backing up data from the user program"). In order to be able to use the data sets in the user data when updating, they must first be transferred via a card reader or FTP from the memory card to the PC. The data records are available after the saving to the card under \ USER \ SIMOTION \ USER_DIR \. Alternatively, the Save Variables function in SIMOTION SCOUT can be used. Assigning user data to the SIMOTION device Only the user knows that user data has been assigned to the SIMOTION device to be updated. The following points must be clarified in order to enable user update data to be transferred: Which user data is involved here? (Content) Where is the user data located? (Source) Where should the data be imported to? (SIMOTION device) To ensure that all information is available, the user data must be provided in a directory structure that has already been defined. 22 Operating Instructions, 02/2012

23 Overview 1.7 Transferring device-specific user data to the update data Directory structure of the user data The user data is to be stored in the following defined directory structure, as shown in the figure. The directory structure is created using a new folder in Windows Explorer. The structure must be accessible via Windows Explorer. The data can be saved on the hard disk, a USB memory stick, or in a network folder, for example. The ID of the user-specific folder is defined by the user. Operating Instructions, 02/

24 Overview 1.7 Transferring device-specific user data to the update data Figure 1-3 Directory structure for saving user data 24 Operating Instructions, 02/2012

25 Overview 1.7 Transferring device-specific user data to the update data The path to a user-specific file must be specified when importing user data via the Device Update tool. See also: Creating update data with the Device Update tool (Page 29), Select additional options dialog. The user data for all the devices from the projects are located in the user-specific folder. Data saved in the subdirectory all is imported to all the devices to be updated. Data saved in device-specific folders, e.g. <Device1>, is only imported to the SIMOTION device whose name matches the folder name. In the event of a conflict, if data is available for a device from both the all subdirectory and a device-specific folder (e.g. <Device1>), the user data from the device-specific folder is used. Operating Instructions, 02/

26 Overview 1.7 Transferring device-specific user data to the update data 26 Operating Instructions, 02/2012

27 2 2.1 Overview Updating procedure The following section provides an overview of the procedure for updating a SIMOTION device: Creating update data (machine manufacturer) Update data is created on an operator-guided basis via the Device Update tool at the machine manufacturer's site, using the SIMOTION SCOUT engineering system. This is conducted by the application developer as part of commissioning or service. Copying the update media (machine manufacturer or machine operator) Once the update media has been created, it can either be saved directly to an update medium or stored as an update archive. If data is to be copied to the update medium at a later date, the update data that has been created is saved in an update archive (File system). This can be called up at any time and imported to an update medium. Data is copied to an update medium without SIMOTION SCOUT: This can be performed by either the application developer at the machine manufacturer's site or by the user at the machine operator's site. Transferring data from the update medium to the SIMOTION device (machine operator) Update data can also be imported from the update medium to the SIMOTION device, irrespective of time and place, using the Device Update tool on an operator-guided basis. Note If the parameterization of the SINAMICS Safety Integrated functions is contained in the update data, these functions must be activated after the update. See also SINAMICS S120 Safety Integrated Function Manual. Operating Instructions, 02/

28 2.1 Overview Saving update data to the update media or as an update archive After the Device Update tool procedure has been completed, the special features of saving to the update media (USB memory stick, CF/MMC card, or IT DIAG file) are described. The creation of the update archive is also examined. Creating update data with SIMOTION SCOUT and transferring data to an update medium Creating update data, including copying to a USB memory stick (Page 45) Creating update data, including copying to a CF/MMC card (Page 47) Creating update data, including creating an IT DIAG file (Page 47) Creating update data as an update archive (Page 48) Copying to the update media on the basis of an update archive Copying data to a USB memory stick (Page 55) Copying data to a CF/MMC card (Page 56) Creating an IT DIAG file and copying update data (Page 57) Transferring update data from the update medium to SIMOTION devices Updating a module with a USB memory stick (Page 66) Updating a module with a CF/MMC card (Page 70) Updating a module with an IT DIAG file (Page 72) 28 Operating Instructions, 02/2012

29 2.2 Creating update data using SIMOTION SCOUT 2.2 Creating update data using SIMOTION SCOUT The section below describes how update data are created. Update data are created on an operator-guided basis using SIMOTION SCOUT. The individual data items are selected step-by-step using a wizard Creating update data with the Device Update tool Requirements The following data is required in order to create update data: SIMOTION SCOUT V4.1 SP2 or higher installed SIMOTION project(s) One or more SIMOTION devices (firmware V4.1 SP2 or higher) Current SIMOTION FWSP (Firmware Support Package) is installed (applies as of > V4.1 SP2) User data Update data creation procedure Update data is essentially created using SIMOTION SCOUT as follows: Call up the Device Update tool via the SIMOTION SCOUT menu Choose whether to create update data or restore data Select a project Select a device Select data Select further options (e.g. user data) Enter the version details Display the summary Copy the update data to an update medium or save it in an archive (to be copied to an update medium at a later date) Operating Instructions, 02/

30 2.2 Creating update data using SIMOTION SCOUT How to create update data Call up the Device Update tool via SIMOTION SCOUT. This will give you a step-by-step guide to creating the required update data, which is then either saved in an update archive or imported directly to an update medium. Note If you call up the Device Update tool via an open project, the project is automatically selected in the dialog. If you also wish to save an archived SIMOTION SCOUT project in the update data, you must close the project before creating the update data. 1. Select Project > Start device update tool directly in SIMOTION SCOUT. Figure 2-1 SIMOTION SCOUT: Start Device Update tool 30 Operating Instructions, 02/2012

31 2.2 Creating update data using SIMOTION SCOUT 2. The Device Update tool opens at the start screen Welcome to the SIMOTION Device Update tool V (The Device Update tool is in English.) Here, you can decide whether data is to be created for the purpose of updating or restoring a SIMOTION device or a SIMOTION project. Select Create update data if you wish to create data for updating a device or project. "Updating" means changing to a specific, defined configuration from update data components; this may even be an older version than the current SIMOTION device. Select the Select configuration of data which were formerly stored option if you are already updating a device/devices or a project/projects for a second time and wish to restore the default settings for projects, devices, and data from the last update. This information can be taken either from an update archive or directly from the update medium. Specify the path to the target folder for the update archive, IT DIAG file, or the drive to the update medium that is connected to the PC (USB memory stick, CF/MMC). The Device Update tool guides you through this step-by-step. The default settings can also be changed if required. If you have selected this option, the Version information dialog is also displayed and write-protected (refer to point 7). Operating Instructions, 02/

32 2.2 Creating update data using SIMOTION SCOUT Select Create restore trigger if you wish to create data for restoring a device or project. When restoring data, activate the configuration saved on the memory card for the SIMOTION device during the last update. Further information can be found in the section Downgrading (Page 77). Figure 2-2 Start screen for Device Update tool Always click Next to proceed to the next dialog box. 32 Operating Instructions, 02/2012

33 2.2 Creating update data using SIMOTION SCOUT 3. The Select SIMOTION projects dialog then opens. All the projects that have been saved for SIMOTION SCOUT in the standard path or have already been opened on this computer using SIMOTION SCOUT appear here. Figure 2-3 Select SIMOTION Projects dialog Please select one or more SIMOTION projects for which you wish to generate update data. The currently open project is automatically selected. Via button Select all you can select all displayed projects. Via Select none you can undo the project selection. Under Path of selected project the path of the selected project is displayed. Operating Instructions, 02/

34 2.2 Creating update data using SIMOTION SCOUT 4. In the next dialog (Select Devices), all devices assigned to the previously selected projects are displayed. Select the device(s) for which you wish to create update data. Using the Select all button, select all devices shown that were selected in the dialog prior to this. You can deselect the devices by clicking Select none. The path for the project containing the selected device is displayed under Project path of selected device. Figure 2-4 Select Devices dialog Note The selected devices from the selected projects must possess different device names. If there are two devices with the same name, only one of them can be selected. See also: Assigning update data to devices (Page 17) 34 Operating Instructions, 02/2012

35 2.2 Creating update data using SIMOTION SCOUT 5. In the Select data dialog, select the data to be stored in the update archive for each selected device. The options of which update data is to be created can be selected separately for each SIMOTION device. Figure 2-5 Select Data dialog The following options can be selected on the left-hand side of the dialog in the device tree: Project (without TPs): Project data without technology packages TPs: Technology packages The technology packages selected in the Select Technology Packages dialog box in SIMOTION SCOUT are added to the update. Archive (compressed scout project file): The archive data contains the entire archived SIMOTION SCOUT project belonging to this device (ZIP file). If the update data is created via an open SIMOTION project, the archive cannot be created. Note If SCOUT projects already archived on the memory card are to be deleted, this can be carried out via a card reader or FTP. Operating Instructions, 02/

36 2.2 Creating update data using SIMOTION SCOUT User data: Your user data Further information on user data can be found at: Transferring device-specific user data to the update data (Page 22) Firmware: In order to be able to add the firmware to the update data, it is necessary to install a corresponding SIMOTION FWSP (Firmware Support Package). Note The compatible SIMOTION FWSP (Firmware Support Package) is automatically supplied as of SIMOTION SCOUT installation V4.1 SP4. Subsequent hotfixes (HFs) are also provided as SIMOTION FWSPs via the SIMOTION Product Support pages on the Internet at: Only one FWSP version can be installed within a main version. Check whether the installed FWSP corresponds to the desired firmware version. If this is not the case, install the correct FWSP. You can define the selection options for all devices using the checkboxes on the righthand side of the dialog: Using Select options, you can select all data for all devices with the Select all option. Selecting Select none deselects all devices. Using Global select options, you can select certain options which are assigned to all devices. For example, in this case Project (project data), TPs (technology packages), and User data have been selected on a global basis for the selected devices as update data to be created. By clicking the Apply button, the selection made on the right-hand side of the dialog is assigned to the left-hand side, thereby validating the selection for the devices. The settings on the right-hand side of the dialog are not saved for the next time the Device Update tool is run. Note For SIMOTION P, there are currently only plans to update the project data, technology packages and user data. The firmware cannot be updated because of its dependence on other Windows components. 36 Operating Instructions, 02/2012

37 2.2 Creating update data using SIMOTION SCOUT 6. In the Select additional options dialog, you can select additional options and specify whether the user data is to be replaced or extended. Figure 2-6 Select Additional Options dialog Using the Force update option, you can carry out an update even if the name of the device from the update data is not identical to the persistently saved device name of the SIMOTION device to be updated. The device to be updated receives the name of the device from the update data if you click Force update. This option is only available if precisely one device has been selected (single update). The option is deactivated in the example shown because two devices have been selected. Enter the path to the user data under User data path. This option can only be selected if the User data is selected as the update data to be created in the Select data dialog box. Operating Instructions, 02/

38 2.2 Creating update data using SIMOTION SCOUT The data provided from the User data path is displayed on the folder structure on the left-hand side of the dialog box. The option Merge or Replace must be selected separately for each SIMOTION device. The selection of the user data is already defined in the user-specific folder. Note The options Replace and Merge refer to the directory level, i.e. file contents are not changed. Further information about the behavior for Replace and Merge is at the end of this section. On the right-hand side of the dialog, under Select options you can specify whether the user data is to be split and replaced according to IT Config, IT Files, IT Settings, Java Program, Java Data and Unit Data Sets (Replace all), or whether the existing data is to be extended to include new information (Merge all). For the significance of user data, refer to Acceptance of device-specific user data into update data (Page 22) For example, if Unit Data Sets and Replace all are selected, and no data is contained within the relevant user-specific folder, the Unit Data Sets (unit data) on the memory card are deleted. By clicking the Apply button, the selection on the right-hand side of the dialog is assigned to the left-hand side, thereby validating the selection for all devices. The settings on the right-hand side of the dialog are not saved for the next time the Device Update tool is run. The options can also be selected separately for each SIMOTION device on the lefthand side of the device tree. If the button Next is grayed after the selection, this refers to an insufficient selection as the check is executed automatically. Please check if in the directory under User data path no user data has been saved for a device or if the selection on the left-hand side in the device tree or on the right-hand side in the dialog under Select options is incomplete. 38 Operating Instructions, 02/2012

39 2.2 Creating update data using SIMOTION SCOUT 7. Enter the version information for the update data in the Add version information dialog: Author Version Date Comment The update information is attached to the update data and can be displayed throughout the entire update procedure. Figure 2-7 Add version information dialog Operating Instructions, 02/

40 2.2 Creating update data using SIMOTION SCOUT 8. You can call up a summary of the projects and devices you have selected, as well as their associated components, in the Summary dialog box. Figure 2-8 Summary dialog 40 Operating Instructions, 02/2012

41 2.2 Creating update data using SIMOTION SCOUT 9. In the Select storage location/media dialog, you can specify whether the update data created is to be copied to a specific update medium, or is to be saved in an update archive in order to be written to an update medium at a later date. File system (Update archive) The data is to be exported to a File system in order to be written to an update medium at a later date. An update archive is created: This can be called up at a later date from outside the SIMOTION SCOUT context in order to copy to an update medium (USB memory stick, CF/MMC card) or transfer the data via a communication connection (IT DIAG file). See also Creating update data as an update archive (Page 48) To call up the update archive, refer to Transferring the update data (Page 49) USB memory stick If you select USB memory stick, the update data is written directly to a USB memory stick inserted previously. Check the drive setting. This USB memory stick will have to be formatted before it can be used for updating purposes for the first time. Select the Format as update stick option. See also Creating update data, including copying to a USB memory stick (Page 45) Should you wish to undo the formatting of the USB memory stick, refer to Restoring the original status of a USB memory stick (Page 85) CF/MMC If you select CF/MMC, the update data is written directly to a CF/MMC card. See also Creating update data, including copying to a CF/MMC card (Page 47) IT DIAG file If you select IT DIAG file, the update data is written to an IT DIAG file. If update data is created for multiple SIMOTION devices, an IT DIAG file with the same name as the device (<Device_name>.zip) is generally created for each device. See also Creating update data, including creating an IT DIAG file (Page 47). Operating Instructions, 02/

42 2.2 Creating update data using SIMOTION SCOUT Figure 2-9 Select storage location/media dialog Once you have selected the update medium, click Finish to activate the creation of the update data. 42 Operating Instructions, 02/2012

43 2.2 Creating update data using SIMOTION SCOUT 10. After the update data has been created, the Succeeded dialog appears. All successfully created update data is listed here and the storage location recorded. Close the Device Update tool by clicking the Close button. Figure 2-10 Exit window for the Device Update tool Canceling the Device Update tool As a rule, the Device Update tool can be canceled after every step by clicking the Cancel button. If the data has already begun to be written to the update medium, you cannot cancel this action until the procedure is complete. Operating Instructions, 02/

44 2.2 Creating update data using SIMOTION SCOUT Behavior after Merge or Replace The following table shows the behavior of original and new files after Merge and Replace. Original files Update files After Merge After Replace Backup files File 1 (original) File 1 (original) File 1 (original) * File 2 (original) File 2 (new) File 2 (new) File 2 (new) File 2 (original) File 3 (original) File 3 (original) File 3 (original) -- * File 4 (new) File 4 (new) File 4 (new) -- * In the example, File 2 is replaced and File 4 is added. For the Merge option, the original files are adopted and only replaced by new files with the same name or expanded by new files. For the Replace option, only the new files are adopted. The original files are backed up for Merge and Replace and can be restored. 44 Operating Instructions, 02/2012

45 2.2 Creating update data using SIMOTION SCOUT Creating update data, including copying to a USB memory stick The USB memory stick can be used both for single and multiple updates with SIMOTION D4x5/D4x5-2 and SIMOTION P devices, i.e. you can update either a single device or multiple devices. See also Device-specific update media (Page 21) Particular aspects of saving update data on a USB memory stick The USB memory stick, with at least a 512 MB capacity, appears as a logical drive when plugged into the PC. The USB memory stick must be formatted when it is used for the first time (Format as update stick option). You require administrator rights to do this. The following hardware is required in order to update a SIMOTION D4x5/D4x5-2 using a USB memory stick: Table 2-1 Hardware required for USB memory stick updates Module Order no. Minimum hardware release required 1) SIMOTION D425 DP 6AU AA00-0AA0????? F2)???????? SIMOTION D425 DP/PN SIMOTION D435 DP 6AU AA00-0AA0??????? Update via USB memory stick is not supported SIMOTION D435 DP/PN SIMOTION D435 6AU AA00-0AA1 F 2) SIMOTION D445 6AU AA00-0AA0 A SIMOTION D AU AA00-0AA1 A SIMOTION D445-2 DP/PN 6AU AD00-0AA0 B SIMOTION D455-2 DP/PN 6AU AD00-0AA0 B 1) The hardware release can be found on the rating plates on the SIMOTION D 2) Modules with hardware release A to E can be updated (update to BIOS V ) With SIMOTION D425/D435, a BIOS version of at least V is required for USB support. Modules as of hardware release F are supplied with a corresponding BIOS version. A BIOS update can be conducted on SIMOTION D425/D435 modules with a BIOS version < V Operating Instructions, 02/

46 2.2 Creating update data using SIMOTION SCOUT If you wish to conduct a BIOS update, refer to the Commissioning Manual for the SIMOTION D4x5. Note Note the following information The SIMOTION device is started from the USB memory stick when updating devices via a USB memory stick. For this reason, a bootable USB memory stick must be used. With the exception of SIMATIC USB memory sticks, due to the rapid developments within the market for USB memory sticks it is not possible to give any concrete recommendations. For information on this, go to: If you are using the USB memory stick to update SIMOTION devices for the first time, it is imperative that you format the stick first. Unless it is formatted, the USB memory stick will not work, nor will the update process. Once the USB memory stick has been formatted, the amount of space which can be used in Windows is limited to 450 MB, irrespective of how much memory capacity is actually available. During formatting, all the existing data on the USB memory stick is permanently deleted. The system checks the size of the USB memory stick. If this is less than 512 MB, this option is not available in the Store data dialog box. The USB memory stick has to be restored to its original formatting if you wish to use it for any other purpose. Refer to: Restoring the original status of a USB memory stick (Page 85). 46 Operating Instructions, 02/2012

47 2.2 Creating update data using SIMOTION SCOUT Creating update data, including copying to a CF/MMC card The CF/MMC card can be used exclusively for single updates with SIMOTION C and SIMOTION D devices, i.e. only one device can be updated. See also Device-specific update media (Page 21) Particular aspects of saving update data on a CF/MMC card The CF/MMC card is inserted into the PC or CF/MMC card adapter and is visible as a logical drive. Note Note the following information You can only perform updates using a CF/MMC card if there already is a bootable SIMOTION system present on the target card, i.e. at the very least, executable firmware V4.1 SP2 must be present. A blank CF/MMC card cannot be updated. If the Device Update tool has not finished or the copying procedure has been interrupted, updating with the CF/MMC card will not be possible. If an error occurs while data is being written to the CF/MMC card - for example, a power failure - all the data on the card may be lost. With an MMC (SIMOTION C), a restore can only be carried out via a restore archive or IT DIAG Creating update data, including creating an IT DIAG file IT DIAG can be used for single and multiple updates, i.e. you can update either one or more than one SIMOTION device. IT DIAG is a suitable update medium for all update scenarios and all SIMOTION devices. If update data are created for multiple SIMOTION devices, an IT DIAG file with the same name as the device (<Device_name>.zip) is generally created for each device. See also Device-specific update media (Page 21). Particular aspects of saving update data as an IT DIAG file Note Note the following information If there already is an IT DIAG file in the selected directory, an error message appears and the process is stopped. First delete the existing IT DIAG file from the directory; you will then be able save the new IT DIAG file. Operating Instructions, 02/

48 2.2 Creating update data using SIMOTION SCOUT Creating update data as an update archive The update data are created using the Device Update tool in SIMOTION SCOUT on an operator-guided basis, and then saved as an update archive in a directory. Select the File system option in the second-to-last dialog box in the Device Update tool (Select storage location/media ). Enter the path to a blank directory here. As soon as the Device Update tool is closed, the update data selected and created previously are written to the directory and stored there for later use. The update archive can be called up independently of SIMOTION SCOUT at a later point in time, so that it can be copied to an update medium. Particular aspects of saving the update data as an update archive Note Note the following information If data are already present in the directory selected, an error message is output and the process is stopped. No data are written. Select another blank directory in the Select storage location/media dialog. The update data are then written to the newly appointed directory. If the CF/MMC card has been selected as an update medium, the update medium may only be one device. 48 Operating Instructions, 02/2012

49 2.3 Copying to the update media on the basis of an update archive 2.3 Copying to the update media on the basis of an update archive Copying to an update medium without SIMOTION SCOUT Requirements The update data has already been created and is located in an update archive. SIMOTION Device Update tool (update archive component) SIMOTION SCOUT is not required to be installed Released for the Windows XP SP3, Windows 7 Ultimate and Windows 7 Professional operating systems Sequence The data is copied to the update media independently of SIMOTION SCOUT; therefore, this can be conducted at either the machine manufacturer's site or the machine operator's site. All that is required is the update archive in which all the update data and the SIMOTION Device Update tool are saved Transferring the update data The SIMOTION Device Update tool is part of the update archive that is created within the context of SIMOTION SCOUT. You call up the Device Update tool for the purpose of transferring update data from an update archive to an update medium. This involves starting the SIMOTION Device Update tool via a batch file, independently of SIMOTION SCOUT. Proceed as follows: 1. Open the update archive directory. 2. Start the upd_tool.bat batch file; this starts the SIMOTION Device Update tool. Operating Instructions, 02/

50 2.3 Copying to the update media on the basis of an update archive 3. The Welcome to the SIMOTION Device Update tool V dialog appears as the start screen. (The Device Update tool is in English.) Figure 2-11 Device Update tool start screen, for transferring update data to an update medium 4. Click Load update data/restore trigger to call up either an update archive created using SIMOTION SCOUT or a restore archive. Select the path in which the update archive has been saved. Click Next to proceed to the next dialog box. 50 Operating Instructions, 02/2012

51 2.3 Copying to the update media on the basis of an update archive 5. The Version Information dialog box contains the stored identification data that was entered during the creation of the update data. Figure 2-12 Displaying the identification data for the update archive Operating Instructions, 02/

52 2.3 Copying to the update media on the basis of an update archive 6. Select the update medium in the Select storage location/media dialog box. Data will then be written directly to this. You can select from the following: USB memory stick CF/MMC card IT DIAG The update medium you can use depends on the SIMOTION device or on whether a single or a multiple update is taking place. You can find an overview under: Device-specific update media (Page 21) Click Finish to activate and execute the copying of data to the update medium. The following data can be created during this procedure: USB memory stick: Update medium for SIMOTION D4x5/D4x5-2 and SIMOTION P. Update data for one or more SIMOTION devices is saved on this update medium. If you are using the USB stick as an update medium for the first time, you must format it. To do this, select Format as update stick. See also Copying data to a USB memory stick (Page 55) CF/MMC: Memory cards are an update medium for single updates on the SIMOTION C and SIMOTION D. Update data for a single SIMOTION device is saved on this update medium. See also Copying data to a CF/MMC card (Page 56) IT DIAG file: SIMOTION IT DIAG is an update medium that is suitable for all update scenarios (single and multiple update) and all SIMOTION hardware platforms (SIMOTION C, D, P). If update data is created for multiple SIMOTION devices, an IT DIAG file with the same name as the device (<Device_name>.zip) is generally created for each device. See also Creating an IT DIAG file and copying the update data (Page 57) 52 Operating Instructions, 02/2012

53 2.3 Copying to the update media on the basis of an update archive Figure 2-13 Selecting the update medium 7. The final Succeeded dialog in the Device Update tool shows which devices the update data from the update archive have been stored for, and at what location. Operating Instructions, 02/

54 2.3 Copying to the update media on the basis of an update archive Figure 2-14 Final Succeeded dialog Canceling the Device Update tool The Device Update tool can be canceled after every step by clicking the Cancel button. However, if the data has already begun to be written to the update medium, you cannot cancel this action until the procedure is complete. 54 Operating Instructions, 02/2012

55 2.3 Copying to the update media on the basis of an update archive Copying data to a USB memory stick The USB memory stick can be used both for single and multiple updates with SIMOTION D4x5/D4x5-2 and SIMOTION P devices, i.e. you can update either a single device or multiple devices. See also Device-specific update media (Page 21) Note The SIMOTION device is started from the USB memory stick when updating devices via a USB memory stick. For this reason, a bootable USB memory stick must be used. With the exception of SIMATIC USB memory sticks, due to the rapid developments within the market for USB memory sticks it is not possible to make any other concrete recommendations. For information on this, go to: Particular aspects of transferring update data from the update archive to a USB memory stick The USB memory stick, with at least a 512 MB capacity, appears as a logical drive when plugged into the PC. The USB memory stick must be formatted when it is used for the first time (Format as update stick option). You require administrator rights to do this. The following hardware is required in order to update a SIMOTION D4x5/D4x5-2 using a USB memory stick: Table 2-2 Hardware required for USB memory stick updates Module Order no. Minimum hardware release required 1) SIMOTION D425 6AU AA00-0AA0 F 2) SIMOTION D435 6AU AA00-0AA0 Update via USB memory stick is not supported SIMOTION D435 6AU AA00-0AA1 F 2) SIMOTION D445 6AU AA00-0AA0 A SIMOTION D AU AA00-0AA1 A SIMOTION D445-2 DP/PN 6AU AD00-0AA0 B SIMOTION D455-2 DP/PN 6AU AD00-0AA0 B 1) The hardware release can be found on the rating plates on the SIMOTION D 2) Modules with hardware release A to E can be updated (update to BIOS V ) With SIMOTION D425/D435, a BIOS version of at least V is required for USB support. Modules as of hardware release F are supplied with a corresponding BIOS version. A BIOS update can be conducted on SIMOTION D425/D435 modules with a BIOS version < V Operating Instructions, 02/

56 2.3 Copying to the update media on the basis of an update archive If you wish to conduct a BIOS update, refer to the Commissioning Manual for the SIMOTION D4x5. Note Note the following information If you are using the USB memory stick to update SIMOTION devices for the first time, it is imperative that you format the stick first. Unless it is formatted, the USB memory stick will not work, nor will the update process. Once the USB memory stick has been formatted, the amount of space which can be used in Windows is limited to 450 MB, irrespective of how much memory capacity is actually available. During formatting, all the existing data on the USB memory stick is permanently deleted. The system checks the size of the USB memory stick. If this is less than 512 MB, this option is not available in the Store data dialog box. The USB memory stick has to be restored to its original formatting if you wish to use it for any other purpose. Refer to: Restoring the original status of a USB memory stick (Page 85) Copying data to a CF/MMC card The CF/MMC card can be used exclusively for single updates with SIMOTION C and SIMOTION D devices, i.e. only one device can be updated. See also Device-specific update media (Page 21) Particular aspects of transferring update data from the update archive to a CF/MMC card The CF/MMC card is inserted into the PC or CF/MMC card adapter and is visible as a logical drive. Note Note the following information You can only perform updates using a CF/MMC card if there already is a bootable SIMOTION system present on the target card, i.e. at the very least, there must be executable firmware V4.1 SP2. A blank CF/MMC card cannot be updated. If the Device Update tool has not finished or the copying procedure has been interrupted, updating with the CF/MMC card will not be possible. If an error occurs while data are being written to the CF/MMC card - for example, a power failure - all the data on the card may be lost. If an update using an MMC (with C2xx) fails, or should the user wish to restore the previous configuration for any other reason, the restore data must be created at the machine manufacturer's site via SIMOTION SCOUT, or the restore may take place via IT DIAG. 56 Operating Instructions, 02/2012

57 2.3 Copying to the update media on the basis of an update archive Creating an IT DIAG file and copying update data IT DIAG can be used for single and multiple updates, i.e. you can update either one or more than one SIMOTION device. IT DIAG is a suitable update medium for all update scenarios and all SIMOTION devices. If update data are created for multiple SIMOTION devices, an IT DIAG file with the same name as the device (<Device_name>.zip) is generally created for each device. See also Device-specific update media (Page 21) Particular aspects of transferring update data from the update archive to the IT DIAG file Note Note the following information If there already is an IT DIAG file in the selected directory, an error message appears and the process is stopped. First delete the existing IT DIAG file from the directory; you will then be able save the new IT DIAG file. Operating Instructions, 02/

58 2.4 Transferring update data to the SIMOTION device 2.4 Transferring update data to the SIMOTION device After update data has been created, it must be transferred to the relevant SIMOTION device. The starting point for this is the update media to which the update data has already been written. An update medium (USB memory stick or CF/MMC card) is either inserted into the SIMOTION device to be updated, or the update data is transferred to the SIMOTION device via a communication connection (IT DIAG). The update procedure is triggered by restarting the SIMOTION device to be updated. Once the update data has been transferred to the memory card in the device for the first time, the data is saved (this applies to the USB memory stick and IT DIAG). The update data is activated as the current configuration after the SIMOTION device has been restarted. Note If the parameterization of the SINAMICS Safety Integrated functions is contained in the update data, these functions must be activated after the update. See also SINAMICS S120 Safety Integrated Function Manual. Requirements for updating: Firmware on the SIMOTION device to be updated, V4.1 SP2 or higher Update data must contain firmware V4.1 SP2 or higher (if firmware is selected). Updating devices Updating a module with a USB memory stick (Page 66) Updating a module with a CF/MMC card (Page 70) Updating a module with IT DIAG (Page 72) 58 Operating Instructions, 02/2012

59 2.4 Transferring update data to the SIMOTION device Behavior of the retain data during updating Overview After the update data have been transferred to the SIMOTION device, the device is restarted and the update data are applied. During rebooting, the non-volatile data that are saved in the SIMOTION device is checked to determine its compatibility with the current configuration. Compatibility checks are conducted in relation to: Retain kernel data Device-global retain variables Unit retain variables TO retain data SIMOTION retain data behavior during updating The retain data are kept if the firmware version is compatible. Compatibility exists: If no changes have been made to the retain data Compiling a project in SIMOTION SCOUT does not entail any changes, nor does updating within a version of SIMOTION SCOUT. The retain data are kept when the project is updated. If no structural change has been made, the retain data are always kept, regardless of the firmware version. If structural changes are made during the update, the retain data can be saved before updating begins and then transferred again. (See SIMOTION SCOUT function "Save and restore variables".) Note Observe the update instructions contained in the Readme. Behavior of the SINAMICS retain data The SINAMICS retain data are kept during updates. All SINAMICS retain data can be located in the retain memory and interpreted by a new version of the firmware. Operating Instructions, 02/

60 2.4 Transferring update data to the SIMOTION device Receiving unit data Behavior of SIMOTION unit data during updating After the update data has been transferred to the SIMOTION device, the device is restarted and the update data is applied. When loading a unit data set, a check is executed for compatibility with the current unit. Data saved with _saveunitdataset is only compatible if the data structure within the unit has not changed. Data saved with _exportunitdataset() remains compatible even after the structure of the unit has been changed, i.e. the data is kept even after a change in the version or project (identical unit and data names). Whether existing unit data sets should be kept (Merge) or deleted (Replace) can be specified using the Device Update tool. New unit data sets can replace existing ones (Replace) or extend them (Merge). Replace means that all existing unit data sets are deleted and the new unit data sets are applied. Merge means that all existing unit data sets are kept and the new unit data sets are added to them. The only exception are the unit data sets with identical names. In this case, the existing unit data sets will be replaced with the new ones. Further information on the Replace and Merge options can be found at: Creating update data with the Device Update tool (Page 29) in the Select additonal options dialog box. Additional references Additional information on the functions can be found in: SIMOTION Basic Functions Function Manual SIMOTION System Functions/Variables Devices List Manual SIMOTION SCOUT Configuration Manual SIMOTION SCOUT Online Help 60 Operating Instructions, 02/2012

61 2.4 Transferring update data to the SIMOTION device SIMOTION device status during updating Status of SIMOTION devices The table below provides an overview of the possible statuses, the corresponding LEDs, and their significance for SIMOTION devices during the update procedure. Table 2-3 LED display on SIMOTION D for "Copying update data via USB memory stick to the memory card" LED display Status Meaning Description RDY LED flashes yellow/green at 0.5 Hz, later longer green and yellow phases (< 10 s) USB in progress Update running, data is being copied from the USB memory stick to the memory card. Update in progress. Do not switch off the SIMOTION device. RDY LED constantly red USB ERROR 1 Error copying from the USB memory stick Error occurred while copying. SIMOTION device is waiting. No communication possible with the SIMOTION device. Required operator actions: 1. Switch off the device. 2. Remove the USB memory stick. 3. Switch on Device boots up in the starting configuration. RDY LED must be constantly green for > 10 s so that the procedure is completed USB done Data has been successfully copied from the USB memory stick to the memory card. SIMOTION device is waiting. No communication possible with the device. Required operator actions: 1. Switch off the device. 2. Remove the USB memory stick. 3. Switch on (this starts the actual update procedure (see following table: LED display when updating the devices)) RDY LED flashes yellow at 0.5 Hz (longer than 10 s) USB BOOT ERROR Booting is not possible from the used USB memory stick. See Device-specific update media (Page 21) Operating Instructions, 02/

62 2.4 Transferring update data to the SIMOTION device Table 2-4 LED display when updating the devices LED display Status Meaning Description SIMOTION D/P: SF LED flashes green at 0.5 Hz SIMOTION C: SF LED flashes red at 2 Hz SF LED flickers red (10 Hz) IN PROGRESS Update running Update in progress. Do not switch off the SIMOTION device. ERROR 2 Possible errors are: Error backing up the configuration; update has not been accepted Defective update; update data has been copied, but is defective. SIMOTION device is booting up in STOP with start inhibit After OFF/ON, the device boots up in the starting configuration. If required, a restore must be activated. SF LED off 1) DONE 1 Update successfully completed SIMOTION device boots up with the updated configuration. 1) The update has been successfully completed when the SF LED goes out; the device then boots up automatically in the updated configuration. (SF LED display then depends on the respective mode of the device.) The update status is shown not only via the LEDs, but also in the device diagnostics on the Syslog tab. Syslog can also be read via IT DIAG. 62 Operating Instructions, 02/2012

63 2.4 Transferring update data to the SIMOTION device Flow diagram: "Copying update data via USB memory stick to the memory card" The figure below illustrates the processes that run during updating within the SIMOTION device, using the USB memory stick as an example of an update medium. The status and corresponding LED are displayed with different colors by way of analogy. Operating Instructions, 02/

64 2.4 Transferring update data to the SIMOTION device Note In this procedure, only the update data is copied from the USB memory stick to the memory card (e.g. for SIMOTION D from USB memory stick to CF card). The actual update procedure must be initiated in a further step (see flow diagram: "Updating the device"). 64 Operating Instructions, 02/2012

65 2.4 Transferring update data to the SIMOTION device Flow diagram: "Updating a SIMOTION device" The figure below shows how a SIMOTION device can be updated once the update data has been copied to the device's memory card. The status and corresponding LED are displayed with different colors by way of analogy. Operating Instructions, 02/

66 2.4 Transferring update data to the SIMOTION device Transferring update data from the update medium to SIMOTION devices Updating a module with a USB memory stick Requirements USB memory stick updates are supported by the SIMOTION D4x5/D4x5-2 and SIMOTION P devices. Requirements for updating with a USB memory stick: USB memory stick, to which the required update data has already been copied SIMOTION device(s) to be updated A CF card with sufficient memory capacity for the data to be copied must be inserted into the SIMOTION device(s) to be updated. The following hardware is required in order to update a SIMOTION D4x5/D4x5-2 using a USB memory stick: Table 2-5 Hardware required for USB memory stick updates Module Order no. Minimum hardware release required 1) SIMOTION D425 6AU AA00-0AA0 F 2) SIMOTION D435 6AU AA00-0AA0 Update via USB memory stick is not supported SIMOTION D435 6AU AA00-0AA1 F 2) SIMOTION D445 6AU AA00-0AA0 A SIMOTION D AU AA00-0AA1 A SIMOTION D445-2 DP/PN 6AU AD00-0AA0 B SIMOTION D455-2 DP/PN 6AU AD00-0AA0 B 1) The hardware release can be found on the rating plates on the SIMOTION D 2) Modules with hardware release A to E can be updated (update to BIOS V ) With SIMOTION D425/D435, a BIOS version of at least V is required for USB support. Modules as of hardware release F are supplied with a corresponding BIOS version. A BIOS update can be conducted on SIMOTION D425/D435 modules with a BIOS version < V If you wish to conduct a BIOS update, refer to the Commissioning Manual for the SIMOTION D4x5. 66 Operating Instructions, 02/2012

67 2.4 Transferring update data to the SIMOTION device Procedure for updating the SIMOTION D4x5/D4x5-2 When using a USB memory stick to perform an update, proceed as follows: 1. Check the position of the Service selector switch (for D4x5: SIM/NCK; for D4x5-2: SVC/NCK). The switch position must be at Insert the USB memory stick in one of the two USB interfaces of the activated SIMOTION D4x5/D4x5-2. (Only one USB memory stick may be inserted.) 3. Switch the device OFF/ON or reset it using the RESET button. 4. The SIMOTION D4x5/D4x5-2 will now begin copying the data from the USB memory stick to the CF card. The copying procedure starts with some LED state changes and is finally displayed by a yellow/green flashing RDY-LED (0.5 Hz). In the end phase of the update, the RDY LED has longer green and yellow phases (< 10 s). After completion of the copying procedure the RDY-LED changes to: Constant green (only when the RDY-LED is constantly green for > 10 s, has the copying procedure been completed successfully) Constant red, if copying was not successful Meaning of the 7-segment display 0 No memory card available. 1 Internal error 2 Internal error 3 No or incomplete update data available on the USB memory stick. 4 No update data can be copied because there is no project available in the SIMOTION device, but update data for several SIMOTION devices is available on the USB memory stick. Because of the missing project on the SIMOTION device, assignment to the data on the USB memory stick is not possible. 5 The update data cannot be copied, for example, because there is not sufficient memory space. 6 Internal error 7 Unknown update data available on the USB memory stick. 5. Switch off the SIMOTION D4x5/D4x5-2 and remove the USB memory stick. Operating Instructions, 02/

68 2.4 Transferring update data to the SIMOTION device 6. Switch the SIMOTION D4x5/D4x5-2 back on. The system now starts the update procedure. The SF LED flashes green (0.5 Hz) during the update. The procedure can take several minutes. 7. Observe the green flashing of the SF LED: As soon as the update procedure has been completed successfully, the SF LED goes out. The device then boots up automatically in the updated configuration. (The SF LED display then depends on the respective mode of the device.) If the update procedure was not successful, the SF LED flickers red (10 Hz). Note If the update has not been successful in terms of the application (for example, the machine is not behaving as desired), it can be undone using an operator action. Note If the firmware is being updated for SIMOTION D, depending on the firmware version on the SINAMICS components (DRIVE-CLiQ components, TB30, PM340, etc.), the component firmware will also be automatically updated. This procedure can take up to several minutes and is indicated by LED displays. A firmware update on DRIVE-CLiQ components is indicated by the RDY LED flashing red and green: FW update running: RDY LED flashes slowly (0.5 Hz) FW update complete: RDY LED flashes quickly (2 Hz) These flashing patterns are also displayed on the yellow RDY LED on the SIMOTION D/CX32/CX32-2, and indicate that the firmware update has been carried out on components connected to the SIMOTION D/CX32/CX32-2 or that all components have completed the firmware update. After the firmware update has been completed on all components, a POWER ON must be carried out for all updated components. 68 Operating Instructions, 02/2012

69 2.4 Transferring update data to the SIMOTION device Procedure for updating the SIMOTION P 1. The USB memory stick, to which the update data has been copied, is inserted into one of the available USB ports on the SIMOTION P. Updating or restoring is started automatically. 2. If the SIMOTION P is running at that point, you will be prompted to switch the SIMOTION P off. Figure 2-15 SIMOTION P: Query after the USB memory stick is inserted 3. After you click y to confirm, the device is switched off, and the update is started automatically. The data is copied from the USB memory stick to the SIMOTION P's hard disk. While this process is running, you will be kept informed of progress via SIMOTION P Update. 4. Once the copying procedure is complete, you will be prompted whether you wish to restart the SIMOTION P. If you click y to confirm, the SIMOTION P is restarted. Figure 2-16 SIMOTION P: Device restart enquiry 5. The update or restore is activated when the SIMOTION P is restarted. Operating Instructions, 02/

70 2.4 Transferring update data to the SIMOTION device Updating a module with a CF/MMC card Requirements CF/MMC card to which the required update data has already been copied SIMOTION device which is to be updated The memory card must have sufficient free storage space (for the active configuration, update data, and backup) Note Only update data for one specific SIMOTION device can be saved on the CF/MMC card. Procedure 1. Switch off the SIMOTION device to be updated. 2. Insert the CF/MMC card into the SIMOTION device. 3. Switch the SIMOTION device on again. The system now starts the update procedure. During the update, the SF LED flashes: Green for SIMOTION D (0.5 Hz) Red for SIMOTION C (2 Hz) The update procedure can take several minutes. 70 Operating Instructions, 02/2012

71 2.4 Transferring update data to the SIMOTION device 4. Observe the flashing of the SF LED: As soon as the update procedure has been completed successfully, the SF LED goes out. The device then boots up automatically in the updated configuration. (The SF LED display then depends on the respective mode of the device.) If the update procedure was not successful, the SF LED flickers red (10 Hz). Note If the firmware is being updated for SIMOTION D, depending on the firmware version on the SINAMICS components (DRIVE-CLiQ components, TB30, PM340, etc.), the component firmware will also be automatically updated. This procedure can take up to several minutes and is indicated by LED displays. An FW update on DRIVE-CLiQ components is indicated by the RDY LED flashing red/green: FW update running: RDY LED flashing slowly (0.5 Hz) FW update complete: RDY LED flashes quickly (2 Hz) These flashing patterns are also displayed on the yellow RDY LED on the SIMOTION D/CX32/CX32-2, and indicate that the firmware update has been carried out on components connected to the SIMOTION D/CX32/CX32-2 or that all components have completed the firmware update. After the firmware update has been completed on all components, a POWER ON must be carried out for all updated components. Operating Instructions, 02/

72 2.4 Transferring update data to the SIMOTION device Updating a module with an IT DIAG file Requirements The update or restore data has already been created and is available in.zip format in an IT DIAG file. There must be a browser installed on the computer that is in use. The computer is connected via TCP/IP to the SIMOTION device to be updated. A memory card with sufficient memory capacity for the data to be copied must be inserted into the SIMOTION device(s) to be updated. SIMOTION device update or restore procedures via IT DIAG must be performed in STOP mode. Sufficient memory capacity on the CF/MMC card: Memory capacity is required for the current configuration, the backup copy, and the ZIP file Note Switching off the control during data transfer may lead to loss of data on the CF/MMC card. Procedure 1. Establish a connection via the browser to the SIMOTION device to be updated. The system sends the HTML start screen to the browser. 2. Select the Manage Config page and then the Device Update tab. The system sends the authentication page to the browser. 3. Log in on the Manage Config page using the password. 4. In the Device Update tab, select the stored IT Diag file (the update data) at Send new update data using the button. 72 Operating Instructions, 02/2012

73 2.4 Transferring update data to the SIMOTION device 5. Click Send update data to copy the update data to the memory card in the SIMOTION device. The data from the existing configuration is renamed and backed up, and can be retrieved again at any time. In the event of a data restore, this data is activated again. 6. The SIMOTION device is restarted. When the device is booted, the data which has recently been imported is applied as the current configuration and activated. Note If the firmware is being updated for SIMOTION D, depending on the firmware version on the SINAMICS components (DRIVE-CLiQ components, TB30, PM340, etc.), the component firmware will also be automatically updated. This procedure can take up to several minutes and is indicated by LED displays. An FW update on DRIVE-CLiQ components is indicated by the RDY LED flashing red/green: FW update running: RDY LED flashes slowly (0.5 Hz) FW update complete: RDY LED flashes quickly (2 Hz) These flashing patterns are also displayed on the yellow RDY LED on the SIMOTION D/CX32, and indicate that the firmware update has been carried out on components connected to the SIMOTION D/CX32/CX32-2 or that all components have completed the firmware update. After the firmware update has been completed on all components, a POWER ON must be carried out for all updated components. Operating Instructions, 02/

74 2.4 Transferring update data to the SIMOTION device Figure 2-17 IT DIAG - Manage Config tab Saving and archiving the current configuration Get selected data: Select this button if you wish to save and archive the current configuration of the SIMOTION device externally. The data is saved on the PC as a.zip file. The configuration saved here can be restored and activated again at a later date (e.g. in the event of a defective memory card) by clicking Send update data. You can choose between archiving the entire configuration or only certain subsets, e.g. firmware (FW), technology packages (TP), project and/or user data (Scout archive, IT DIAG, and UDS (Unit Data Sets)). You will find additional information about the Restore last update button in the section titled Restoring a SIMOTION device (Page 77). 74 Operating Instructions, 02/2012

75 2.5 Possible error messages for the Device Update tool 2.5 Possible error messages for the Device Update tool Error messages and possible solutions The error messages in the following list can occur when the Device Update tool is being run. The error messages are in English. Possible causes and remedies are described in the table below. Error message Cause Solution To add firmware to the update data, the firmware must be provided by installing a FW Support Package (FWSP). Currently, there is no appropriate FWSP installed. Please refer to the SCOUT documentation to get more information about the FWSP. The following selected projects are not consistent: In order to generate update data out of those projects, you must recompile them first. The firmware must be updated for at least one device. The corresponding SIMOTION FWSP (Firmware Support Package) is not available. The selected projects are not compiled in SIMOTION SCOUT. Compiled and consistent projects are required for updating. Please install the SIMOTION FWSP (Firmware Support Package). FWSP for versions, service packs (SPs), and hotfixes (HFs) are provided on the SIMOTION Product Support pages on the World Wide Web at: iew/en/ Projects that you wish to update must first be compiled in SIMOTION SCOUT and checked for consistency. With the project open, select: Project > Save and compile changes Project > Check consistency To add the selected archive data, the corresponding SCOUT project must not be opened by SCOUT. Please close the corresponding project within SCOUT or deselect the project within the SIMOTION Device Update tool. The selected projects contain devices with identical names. To generate update data, all device names must be unique. Please deselect appropriate projects or rename the corresponding devices names to become unique. This applies to the following devices The selected directory already contains data. Please select an empty directory, or delete all the data in the chosen directory. Projects opened in SIMOTION SCOUT cannot be archived. Several projects were selected when creating update data and devices with identical names exist within this project. The target directory for the update data must be empty. Before you call up and run the Device Update tool, close the project in SIMOTION SCOUT. Create the update data individually for each project or assign unique names to the devices. Select an empty directory or delete the data from an existing one. Operating Instructions, 02/

76 2.5 Possible error messages for the Device Update tool Error message Cause Solution No access to SCOUT. <Device name> not found on card. Error occurred while accessing the project. An attempt has been made to copy update data to a CF/MMC card. A project is already located on the card and the existing device name does not match the device name in the update data. If SIMOTION SCOUT is online, go offline. Contact the hotline in other cases. If the overwriting of the project on the card is required, select the option Force update in the Select additional options dialog. 76 Operating Instructions, 02/2012

77 Restoring 3 In the following cases it is recommended that you perform a restore on a SIMOTION project or device: Restoring to a previous configuration whenever an error occurs during updating Since a SIMOTION device update may fail, this ensures that communication capability is maintained, even after an update failure. If, for instance, the updated firmware is not recognized, the SIMOTION device may be restored to the firmware that was previously valid. Restoring in situations where a SIMOTION device or project has been successful but the new configuration has failed to perform as required; option of returning to the previous configuration. 3.1 Restoring a SIMOTION device Overview During restoring procedures, it makes no difference whether the previous update was successful or unsuccessful. In either case, the device is restored to the configuration backed up most recently. If the update could not be carried out, the communication capability of the device is restored. Restoring is triggered off by an explicit action by the user. When a restore is carried out, the SIMOTION device reverts to the configuration saved at the last update. As long as the initial state of the SIMOTION device is not restored after an unsuccessful update attempt, the device remains in the state STOP with ALS. This means that, at the very least, communication capability will be ensured. A restore procedure is necessary in order to resume work on a SIMOTION project following an unsuccessful update. Following a successful update, the device can be restored specifically to the data that had been backed up previously. This is the case if, for example, the new configuration has failed to perform as required and you wish to return to the previous configuration. A backup is created as the first step in every update procedure. The device can only be restored to this backup. Operating Instructions, 02/

78 Restoring 3.1 Restoring a SIMOTION device Characteristics of a failed update A project failure may manifest itself as follows: The SIMOTION device will not go into RUN. The SIMOTION device goes into RUN but performs incorrectly. The new firmware has not been updated. The previous firmware state is restored, as a result of which the new project or the new technology packages cannot be loaded. The causes of this behavior are displayed in the diagnostics buffer entries. The specified information can be transmitted via the diagnostics pages in IT DIAG, for example. The SIMOTION device displays a request for an overall reset. Requirements for restoring A backup of the previous configuration was created during the update procedure, which ensured that a backup of the data exists. The configuration includes firmware (FW), technology package(s) (TP), project(s), and any user data which may exist. Triggering a restore A restore is triggered by saving the restore archive to the memory card, by means of operator actions on the SIMOTION device or the Restore last update button in the Manage Config (IT Diag) dialog. The SIMOTION D4x5/D4x5-2 and SIMOTION D410 devices support restoring by means of switch settings on the device. Alternatively, the restore action can be activated on all SIMOTION devices by transferring the restore archive. Refer to Particular aspects of restoring SIMOTION devices (Page 81) Backup data The backed up data from a SIMOTION device is retained as long as the backup exists, i.e. until it is overwritten by another update. Should errors occur during the update procedure, the device can be restored to the backup. SIMOTION data behavior during restoring Current retain data The retain data will be restored only if the firmware is restored or if data structures are not compatible. Behavior is described under: Behavior of the retain data during updating (Page 59). Current diagnostic buffer The content at the time of backup is activated again. You can find additional information in the section Particular aspects of restoring SIMOTION devices (Page 81) Behavior of the SINAMICS retain data during restoring After a firmware restore has been carried out, the SINAMICS retain data is in the same state as when the data was backed up. 78 Operating Instructions, 02/2012

79 Restoring 3.2 SIMOTION device status during restoring 3.2 SIMOTION device status during restoring Status of SIMOTION devices The table below provides an overview of the possible statuses, the corresponding LEDs, and their meanings for SIMOTION devices during the restore process. Table 3-1 Overview of SIMOTION device status during restoring LED display Status Meaning Description SIMOTION D/P: IN PROGRESS Restore running Restore in progress. SF LED flashes green Note at 0.5 Hz Do not switch off the SIMOTION device. SIMOTION C: SF LED flashes red at 2 Hz SF LED flickers red (10 Hz) ERROR 4 Restore error SIMOTION device is booting up in STOP with start inhibit After OFF/ON, the device boots up in STOP with start inhibit. SF LED off 1) DONE 2 Restore successfully completed SF LED flickers red (10 Hz) ERROR 6 Fault (SIMOTION D only) Service selector switch is still set at Restore. SIMOTION device boots up with the restored configuration SIMOTION device boots up in STOP with start inhibit. Switch the device off, reset the Service selector switch and switch the device back on. If the restoration was otherwise successful, the devices boots up with the restored configuration. 1) The restore has been successfully completed when the SF LED goes out; the device then boots up automatically in the restored configuration. (The SF LED display then depends on the respective mode of the device.) The restore status is shown not only via the LEDs, but also in the device diagnostics on the tabs diagnostic buffer and Syslog. Operating Instructions, 02/

80 Restoring 3.2 SIMOTION device status during restoring Flow diagram: "Restoring a SIMOTION device" The figure below shows how a SIMOTION device restore may proceed once the restore archive has been transferred to the memory card of the SIMOTION device. The status displays appear in different colors by way of analogy. 80 Operating Instructions, 02/2012

81 Restoring 3.3 Particular aspects of restoring SIMOTION devices 3.3 Particular aspects of restoring SIMOTION devices Requirements During restoring procedures, it makes no difference whether the previous update was successful or unsuccessful. The procedure is identical for every SIMOTION device. A distinction is made between SIMOTION devices where a restore can be requested via an operator control. The user can also request a restore via IT DIAG for SIMOTION devices with Ethernet/PROFINET interfaces. For all SIMOTION devices, restore data can be created as a restore archive on an operator-guided basis via the Device Update tool. These can then be saved to the memory card of the SIMOTION device. Table 3-2 Assignment of restore options to SIMOTION devices SIMOTION device Restore options Implementation C2xx Creating the restore archive via the Device Update tool Machine manufacturer D4x5/D4x5-2 Preferred solution: Machine operator Via Service selector switch on the device Alternative: Create the restore archive via the device update tool D410 Preferred solution: Machine operator Via Service selector switch on the device Alternative: Create the restore archive via the device update tool P320/P350 Creating the restore archive via the Device Update tool Machine manufacturer In principle, all SIMOTION devices with Ethernet interfaces can be restored via IT DIAG for any restore scenario; this can be carried out by the machine operator. Restoring the SIMOTION D4x5/D4x5-2 via an operator control on the device The user can use an operator control to carry out a restore at the machine operator's site without any involvement by the machine manufacturer, since there is no need for SIMOTION SCOUT. 1. Switch off the SIMOTION D4x5/D4x5-2 device. 2. Set the Service selector switch to B. For D4x5: SIM/NCK; for D4x5-2: SVC/NCK) 3. Switch the SIMOTION D4x5/D4x5-2 on again. The system restores the data that was backed up during the update procedure. The data from the update procedure will be deleted. Operating Instructions, 02/

82 Restoring 3.3 Particular aspects of restoring SIMOTION devices 4. The restore procedure is indicated by a green flashing SF LED (0.5 Hz) and can take several minutes. Reset the Service selector switch immediately to 0 after the flashing code is displayed. 5. Observe the flashing of the SF LED: As soon as the restore procedure has been completed successfully, the SF LED goes out. The device then boots up automatically in the restored configuration. (The SF LED display then depends on the respective mode of the device.) If the restore procedure was not successful, the SF LED flickers red (10 Hz). Note If the Service selector switch is not reset or not reset in good time to 0, this results in fault state Service selector switch is still set to restore (SF LED flickers red at 10 Hz). In this case, switch the SIMOTION D4x5/D4x5-2 off, reset the Service selector switch and switch the D4x5/D4x5-2 on again. If the restoration was otherwise successful, the SIMOTION D4x5/D4x5-2 boots up with the restored configuration. Restoring the SIMOTION D410 via an operator control on the device The user can use an operator control to carry out a restore at the machine operator's site without any involvement by the machine manufacturer, since there is no need for SIMOTION SCOUT. 1. Switch the SIMOTION D410 off. 2. Set the Service selector switch to Restore. (DIP switch 6 to ON and DIP switch 7 to OFF) 3. Switch the SIMOTION D410 on again. The system restores the data that was backed up during the update procedure. The data from the restore procedure is deleted. 4. The restore procedure is indicated by a green flashing SF LED (0.5 Hz) and can take several minutes. Reset the Service selector switch immediately the flashing code is displayed (DIP switch 6 to OFF and DIP switch 7 to OFF). 5. Observe the flashing of the SF LED: As soon as the restore procedure has been completed successfully, the SF LED goes out. The device then boots up automatically in the restored configuration. (The SF LED display then depends on the respective mode of the device.) If the restore procedure was not successful, the SF LED flickers red (10 Hz). 82 Operating Instructions, 02/2012

83 Restoring 3.3 Particular aspects of restoring SIMOTION devices Note If the Service selector switch is not reset or not reset in good time, this results in fault state Service selector switch is still set to restore (SF LED flickers red at 10 Hz). In this case, switch the SIMOTION D410 off, reset the Service selector switch and switch the SIMOTION D410 on again. If the restoration was otherwise successful, the SIMOTION D410 boots up with the restored configuration. Restoring firmware for SIMOTION D Note If the firmware is being restored for SIMOTION D, depending on the firmware version on the SINAMICS components (DRIVE-CLiQ components, TB30, PM340, etc.), the component firmware will also be automatically restored. This procedure can take up to several minutes and is indicated by LED displays. A firmware update on DRIVE-CLiQ components is indicated by the RDY LED flashing red and green: FW update running: RDY LED flashes slowly (0.5 Hz) FW update complete: RDY LED flashes quickly (2 Hz) These flashing patterns are also displayed on the yellow RDY LED on the SIMOTION D/CX32/CX32-2, and indicate that the firmware update has been carried out on components connected to the SIMOTION D/CX32/CX32-2 or that all components have completed the firmware update. After the firmware update has been completed on all components, a POWER ON must be carried out for all restored components. Operating Instructions, 02/

84 Restoring 3.3 Particular aspects of restoring SIMOTION devices Restoring via the restore archive A restore archive is created at the machine manufacturer's site using the Device Update tool function in SIMOTION SCOUT. When restoring, you are guided through the Device Update tool (just as is the case with updating). 1. Select Project > Start Device Update tool in the open SIMOTION project. 2. The Device Update tool opens with the start screen Welcome to the SIMOTION Device Update tool V Here, you can decide which data is to be created for updating or restoring a SIMOTION device. Select Create restore trigger, since you wish to create data for restoring a device. 3. The subsequent steps in this procedure are identical to those involved in updating. Refer to: Creating update data with the Device Update tool (Page 29) Restoring via SIMOTION IT DIAG The user can use SIMOTION IT DIAG to carry out a restore at the machine operator's site without any involvement by the machine manufacturer, since there is no need for SIMOTION SCOUT. In the IT DIAG Manage Config tab, under CPU update select the Restore last update button to activate the backup in the device. The system restores the data saved during the update. The data from the update procedure will be deleted. Once this is complete, the SIMOTION device restarts. After ramping up, the configuration is restored to its pre-update status. See also: Updating a module with IT DIAG (Page 72) 84 Operating Instructions, 02/2012

85 Appendix A A A.1 Restoring the original status of a USB memory stick Requirements A USB memory stick has to be formatted once before it can be used as an update medium for the first time. A bootable update medium is created during formatting. The USB stick's memory is limited to a fixed value of 450 MB, irrespective of how much memory capacity is actually available. Various partitions, which are required for updating, are created. To restore the USB memory stick to its original status, it is not enough to simply format it as the partitions have to be deleted first. Note A USB memory stick formatted using the Device Update Tool can only be restored under Windows XP and can then be used again. Procedure Before formatting the USB memory stick, the existing partitions must be deleted and a partition encompassing the entire USB memory stick must be created. The procedure is as follows: 1. Insert the USB memory stick that has been formatted as an update medium into a USB port on the computer. 2. Right-click the My Computer icon on your desktop and select Manage from the pop-up menu. Alternatively, you can also open the Windows Explorer. Right-click My Computer in the Start menu window and select Manage from the pop-up menu. The Computer Management window opens. Operating Instructions, 02/

86 Appendix A A.1 Restoring the original status of a USB memory stick 3. Scroll down the Computer Management window until you reach Disk Management. In this example the USB memory stick appears under drive letter (F:).. The total memory capacity of the USB memory stick is shown at the top right-hand side of the window under Capacity. The different partitions and the memory capacity that is currently available for use appear in the bottom right of the window under Disk 2. The USB memory stick is divided into three partitions: VOLUME (F:) MB FAT32 - Healthy: The area on the left is the partition which is visible in Windows; this contains the update data. 30 MB - Healthy: The area in the middle is the partition containing the LINUX system GB - Not allocated: The area on the right is the partition containing the part of the USB memory stick which is of no relevance to the update data. The size varies depending on the memory capacity of the USB memory stick. This partition is not allocated and cannot, therefore, be read by Windows either. Figure A-1 Computer Management window 4. In order to create a complete partition again, the LINUX partition which is not visible in Windows must be deleted. Right-click the middle partition (in this case 30 MB) and select Delete Partition... from the pop-up menu. 86 Operating Instructions, 02/2012

87 Appendix A A.1 Restoring the original status of a USB memory stick 5. Click Yes in the dialog box that appears to confirm that you wish to delete the partition. Figure A-2 Disk Management 6. There is now only a single unallocated partition available under Disk 2 in the Computer Management window. Selecting the middle partition also automatically deletes the partition on the left-hand side containing the update data. Figure A-3 Computer Management window In order to create a new partition, right-click the unallocated partition and select Activate new partition in the pop-up menu. Operating Instructions, 02/

88 Appendix A A.1 Restoring the original status of a USB memory stick 7. The New Partition Wizard appears. Run the wizard, as indicated in the steps below. Click Next to proceed to the next window. Figure A-4 "New Partition Wizard" start screen 8. Confirm Primary partition as the partition type. Figure A-5 Wizard: Defining the partition type 88 Operating Instructions, 02/2012

89 Appendix A A.1 Restoring the original status of a USB memory stick 9. Confirm the partition size. Figure A-6 Wizard: Defining the partition size 10. Assign the drive into which the USB memory stick is to be inserted. Figure A-7 Wizard: Assign the drive letter or path. Operating Instructions, 02/

90 Appendix A A.1 Restoring the original status of a USB memory stick 11. Choose the following settings in order to format the partition: File system to be used: FAT Allocation unit size: Standard Volume identifier: Volume Figure A-8 Wizard: Format a partition 90 Operating Instructions, 02/2012