Upgrade instructions for the SIMOTION I-Device (PROFINET) SIMOTION V4.1 V4.2 or higher FAQ March 2012 Service & Support Answers for industry.
Question This entry is from the Siemens Industry Online Support. The general terms of use (http://www.siemens.com/terms_of_use) apply. Clicking the link below directly displays the download page of this document. http://support.automation.siemens.com/ww/view/en/49911496 Caution The functions and solutions described in this article confine themselves to the realization of the automation task predominantly. Please take into account furthermore that corresponding protective measures have to be taken up in the context of Industrial Security when connecting your equipment to other parts of the plant, the enterprise network or the Internet. Further information can be found under the Content-ID 50203404. http://support.automation.siemens.com/ww/view/en/50203404 Question Answer How can a SIMOTION project, which was created with SCOUT V4.1 and which uses PROFINET I-Device functionality, be edited using SCOUT V4.2 or higher? To fully answer this question, follow the handling instructions and notes listed in this document. 2 1.1, Entry ID: 49911496
Table of contents Table of contents 1 General information... 4 1.1 Requirements... 4 1.2 I-Device functionality... 4 1.3 Editing an I-Device project using SCOUT V4.2 or higher... 6 1.3.1 Possible scenarios... 6 1.3.2 SIMATIC controllers as higher-level IO-Controllers... 6 2 Upgrade to SIMOTION V4.2 or higher... 7 2.1 Upgrading a SIMOTION station in the project... 7 2.2 Adaptations to the I-Device project... 10 2.2.1 Adding an input or output submodule... 10 2.2.2 Newly generating and installing the GSD file for the I Device... 11 2.2.3 Adaptations in the user program... 12 2.3 Adaptations to the higher-level IO-Controller project... 14 2.3.1 Deleting the old substitute I-Device... 14 2.3.2 Installing the GSD file for the new substitute I-Device... 14 2.3.3 Inserting a new substitute I-Device... 15 2.3.4 Adaptations in the user program... 17 3 Editing the I-Device of a SIMOTION station V4.1... 18 3.1 I-Device and higher-level IO-Controller in different projects... 18 3.2 I-Device and higer-level controller in one project... 20 1.1, Entry ID: 49911496 3
1 0BGeneral information 1 General information 1.1 Requirements The information in this document applies to the following versions: STEP7 V5.5 HF4 or higher S7 300 from firmware V3.2.3 and higher S7 400 from firmware V6 and higher SIMOTION V4.2 or higher SIMOTION V4.2 or higher has not been released with STEP7 V5.4! SIMOTION V4.1 has not been released with STEP7 V5.5! 1.2 I-Device functionality Description Since SIMOTION V4.1.1.6 the I-Slave coupling known from PROFIBUS has been available for PROFINET. For PROFINET this functionality is known as I-Device. This supports data exchange between controls via I/O areas. An I-Device is a controller, which in addition to IO-Controller functionality, also has the role of an IO device to the higher-level IO-Controller. The term I-Device stands for intelligent IO device. Applications The I-Device functionality is used for data exchange with other controllers, for modular machines and plants/systems with distributed synchronous operation (across projects). Configuration The following steps are necessary to configure an I-Device: 1. Activate the I-Device functionality 2. Configure the I/O areas 3. Generate a GSD file (Generic Station Description) for the I-Device 4. Create the substitute I-Device (GSD file installation) 5. Insert the substitute I-Device in the higher-level IO-Controller Additional information can be found in the following FAQ: http://support.automation.siemens.com/ww/view/de/38494882 4 1.1, Entry ID: 49911496
1 0BGeneral information I-Device functionality from SIMOTION V4.2 and higher From STEP7 V5.5 and higher, SIMATIC controllers can also be configured as I-Device. The I-Device functionality of SIMOTION and SIMATIC controllers has been consistently standardized. Within the framework of the standardization, the version of the GSD file was set from V2.1 or V2.2 to V2.25. If a SIMOTION station with I-Device functionality is upgraded to V4.2 or higher, then the substitute I-Device must be replaced in the higher-level project of the IO-Controller, even if nothing changes regarding the I-Device configuration. This procedure is described in detail in Chapter 2. The I-Device of a SIMOTION station V4.1 is still generated in SCOUT 4.2 or higher and STEP7 V5.5 as GSD file V2.1 or V2.2. Versions of the GSD file for the I-Device The version of the GSD file depends on the configured SIMOTION version and is automatically defined by the engineering system. Table 1-1: Versions of the GSD file for the I-Device SIMOTION version Version of the GSD file V4.1 V2.1 (RT I-Device) V2.2 (IRT I-Device) V4.2 or higher V2.25 (RT + IRT I-Device) 1.1, Entry ID: 49911496 5
1 0BGeneral information 1.3 Editing an I-Device project using SCOUT V4.2 or higher 1.3.1 Possible scenarios Fig. 1-1: Scenarios Open the SIMOTION project using SCOUT V4.2 or higher The SIMOTION devices will not be upgrade to V4.2 or higher. No changes will be made at the I-Device. [2] Changes will be made at the I-Device. The SIMOTION devices will be upgraded to V4.2 or higher. [1] No changes will be made at the I-Device. Changes will be made at the I-Device. Please observe Chapter 3. Observe the Upgrade Instructions acc. to Chapter 2. The GSD file must be newly generated for the I-Device. The substitute I-Device should be replaced at the higher-level IO controller. Both hardware configurations (IO controller + I-Device) must be downloaded. [1] If there are several substitute I-Devices and at least one on SIMOTION V4.2 or higher must be upgraded, then the higher-level IO controller must also be upgraded. [2] Regarding the I-Device configuration, no additional actions are required! 1.3.2 SIMATIC controllers as higher-level IO-Controllers The SIMATIC controllers S7 300 from firmware V3.2.3 and higher and S7 400 from firmware V6 and higher support the old and new SIMOTION I-Devices (see Table 1-1). For the new I- Devices these firmware versions are absolute necessary. It is recommended that the SIMATIC controllers are upgraded to these firmware versions! 6 1.1, Entry ID: 49911496
2 Upgrade to SIMOTION V4.2 or higher 2.1 Upgrading a SIMOTION station in the project Open the SIMOTION project If you open an old SIMOTION project with SCOUT V4.2 or higher, then information is displayed which indicates that the old project must be converted to V4.2 or higher so that it can be edited. This message must be confirmed with "OK". However, the SIMOTION stations contained in the project are still not upgraded to V4.2 or higher. Fig. 2-1: Converting a SIMOTION project V4.1 to V4.2 [1] [1] Message is analogue for converting SIMOTION project V4.1 or V4.2 to higher version. If you alternatively create a new SIMOTION project from an XML Project export, then the message above is not displayed. Replacing a module In addition to the firmware, the SIMOTION station in the project must be upgraded to V4.2 or higher. For this purpose, the module replacement function is available in HW-Config (see Fig. 2-2, right mouse key on the station "Replace Object "). In HW-Config, a module can only be replaced within a SIMOTION platform (C, D, or P). If the SIMOTION platform also changes (C, D or P), then in SCOUT, the station must be exported as object and imported into an already existing SIMOTION station of the required platform. The information from Fig. 2-2, that a component with the displayed MLFB with V4.1 should be replaced by one with V4.2, must be confirmed with "Yes". 1.1, Entry ID: 49911496 7
Fig. 2-2: Upgrading a SIMOTION station in the project [2] [2] Message is analogue for converting SIMOTION project V4.1 or V4.2 to higher version. If the I-Device functionality is activated in the upgraded station, then the information is displayed that the GSD file for the I-Device must be newly generated and installed. The substitute I-Device must be replaced at the higher-level IO- Controller. Diagnostic addresses and station number have been changed, which means that the user program may have to be adapted. Fig. 2-3: Information to the I-Device after a module has been replaced If a SIMOTION station is upgraded to V4.2 or higher, but nothing changes at the I-Device configuration, then Chapters 2.2 and 2.3 should still be taken into account. 8 1.1, Entry ID: 49911496
Saving and compiling the project If the old I-Device had only input or only output submodules, then a compilation error would be output after the upgrade (see Fig. 2-4). Fig. 2-4: Compilation error In order to resolve the above compilation error, at least one input or output submodule must be added at the I-Device (see Chapter 2.2.1). 1.1, Entry ID: 49911496 9
2.2 Adaptations to the I-Device project 2.2.1 Adding an input or output submodule Fig. 2-5: Configuring at least one input and one output submodule From SIMOTION V4.2 and higher, I-Device requires at least one input and one output submodule. If this is not the case, then one input or one output submodule must be created (see Fig. 2-5). 1. Their properties are opened by double-clicking on the PROFINET interface in HW-Config. 2. If the SIMOTION controller is operated as I-Device, then the "I-Device mode" must be activated under the "I-Device" tab. 3. The missing input or output submodule can be added under the same tab using the "New " button. 10 1.1, Entry ID: 49911496
2.2.2 Newly generating and installing the GSD file for the I Device Fig. 2-6: Generating the GSD file for the I-Device Fig. 2-7: Generating and installing GSD file V2.25 1. The GSD file of the I-Device is newly generated by pressing the "Create" button. 2. If the project of the higher-level IO-Controller is edited using the same engineering system, then by pressing the "Install" button, the GSD file that was just generated, can be installed. 1.1, Entry ID: 49911496 11
If the I-Device project and the project of the higher-level IO-Controller are on different engineering systems, then the GSD file must be exported (see Fig. 2-7, "Export" button) and installed in the engineering system for the higher-level project (see Chapter 0). The exported GSD file can be saved locally and sent by E-mail. 2.2.3 Adaptations in the user program After the upgrade, the diagnostics address and station number of the I-Devices change. This is the reason, that these must be changed in the user program assuming that a user program is being used. The following SIMOTION system functions also use the diagnostic address as an input parameter: _activatedpslave(logicaladdressofdpstation) _deactivatedpslave(logicaladdressofdpstation) _getstateofdpslave(logicaladdressofdpstation) _getstateofalldpstation(logicaldiagnosticaddress) _getstateofalldpslaves(logicaldiagnosticaddress) _getstateofsingledpslave(logicaldiagnosticaddress) _getdpstationaddressfromlogdiagnosticaddress(logdiagnosticaddress) etc. The following SIMOTION system functions use the station number as input parameter: _getstationtype(stationaddress) _getlogdiagnosticaddressfromdpstationaddress(dpstationaddress) etc. 12 1.1, Entry ID: 49911496
Fig. 2-8: Diagnostics address and station number of the I-Device OLD NEW NEW For the SIMOTION I-Device from V4.2 and higher, it is no longer possible to change the diagnostics address in HW-Config. 1.1, Entry ID: 49911496 13
2.3 Adaptations to the higher-level IO-Controller project 2.3.1 Deleting the old substitute I-Device The old substitute I-Device must be deleted and replaced in the higher-level IO- Controller. Please note down the I/O areas of the old submodules, and accept them at the new substitute I-Device. 2.3.2 Installing the GSD file for the new substitute I-Device The GSD file exported under Chapter 2.2 for the I-Device, must be installed in the engineering system of the higher-level IO-Controller. If this has not been done yet, proceed as follows. Fig. 2-9: Installing a GSD file 14 1.1, Entry ID: 49911496
Fig. 2-10: Selecting and installing a GSD file A GSD file V2.25 is generated for the I-Device using a SIMOTION V4.2 or higher. In order to be able to import a GSD file V2.25, STEP7 V5.5 HF4 is required as a minimum. The old GSD file is not deleted when installing a newer version. However, in the hardware catalog under "PROFINET IO "Preconfigured Stations" only the latest GSD file is displayed. In order to access an older GSD file, in the folder <Program Files>\Siemens\STEP7\S7DATA\GSD, the newer GSD files must be deleted and the hardware catalog updated. Please ensure that you delete the correct GSD file! 2.3.3 Inserting a new substitute I-Device The hardware catalog is updated after installing the GSD file. The new GSD file appears in the folder "PROFINET IO Preconfigured Stations". When inserting the substitute I-Device, it must be noted that this must have the same name as the PROFINET interface of the associated controller (e.g. "CBEx30xPNxIOx2", see Fig. 2-11 and Fig. 2-6). The question as to whether the substitute I-Device refers to already existing hardware, must be answered with "yes" (see Fig. 2-12). 1.1, Entry ID: 49911496 15
Fig. 2-11: Integrating the substitute I-Device in the higher-level IO-Controller project Please check the IO addresses of the input and output submodules. It may be necessary to adapt these to your particular application (e.g. configuring an external master/leading value). Fig. 2-12: Adapting the name of the substitute I-Device 16 1.1, Entry ID: 49911496
2.3.4 Adaptations in the user program If, under Chapter 2.2, the "Parameter assignment for the PN interface and its ports on the higher-level IO-controller" checkbox was not set under the "I-Device" tab when configuring the I-Device (see Fig. 2-13), then the diagnostics address of the substitute I-Device changes. The logical address of the first input submodule is set as diagnostics address of the substitute I-Device. The user program must be adapted if the diagnostics address of the substitute I- Device is used there. The following SIMOTION system functions use the diagnostics address as input parameter: _activatedpslave(logicaladdressofdpstation) _deactivatedpslave(logicaladdressofdpstation) _getstateofdpslave(logicaladdressofdpstation) _getstateofalldpstation(logicaldiagnosticaddress) _getstateofalldpslaves(logicaldiagnosticaddress) _getstateofsingledpslave(logicaldiagnosticaddress) etc. Fig. 2-13: Parameter assignment for the PN interface and its ports on the higher-level IO-controller 1.1, Entry ID: 49911496 17
3 2BEditing the I-Device of a SIMOTION station V4.1 3 Editing the I-Device of a SIMOTION station V4.1 3.1 I-Device and higher-level IO-Controller in different projects If the I-Device of a SIMOTION station V4.1 is edited using SCOUT V4.2.1 or higher and STEP7 V5.5 HF4 or HF5 or higher, and a GSD file V2.1 or V2.2 is created, this GSD file can be installed in a engineering system with STEP7 V5.4 SP5 or higher. If the installation is done with STEP7 V5.4 SP5 the following restrictions has to be considered. Restrictions If the substitute I-Device is linked through this GSD file, generated with SCOUT V4.2.1 or higher and STEP7 5.5 HF4 or higher, to the higher-level IO-Controller, the IP address of the substitute I-Device is permanently set to the IP address of the belonging SIMOTION device. In that case the IP address can not be flexibly assigned by the IO-Controller (see Fig. 3-1 Settings are grayed out): Fig. 3-1: IP address can not be assigned by higher-level IO-Controller (display in STEP7 V5.4 SP5) 18 1.1, Entry ID: 49911496
3 2BEditing the I-Device of a SIMOTION station V4.1 Scenario The scenario is relevant only for modular machine concepts, where several substitute I-Devices are derived from one GSD file, and the IP address of the inserted I-Device must be flexibly adapted. Avoidance of the restriction There are 3 possibilities to avoid the restriction: 1. The I-Device configuration and the generation of the GSD file is made with SCOUT V4.1 and STEP7 V5.4 SP5. Then the IP address can also be adapted. The corresponding setting is no longer grayed out. 2. The restriction can also be avoided if you upgrade the SIMOTION device to V4.2 or higher. Then the procedure described in Chapter 2 applies. 3. However, should it be absolutely necessary to edit the I-Device of a SIMOTION device V4.1 with SCOUT V4.2/STEP7 5.5 HF4 or higher and to generate the necessary GSD file, it is possible in exceptional cases to manipulate the GSD file after its generation. Should this be necessary in exceptional cases, please contact the following address: Application Center SIEMENS Siemens AG Industry I DT MC PMA APC Frauenauracher Str. 80 D-91056 Erlangen, Germany Fax: +49 (9131) 98-1297 mailto: profinet.team.motioncontrol.i-dt@siemens.com 1.1, Entry ID: 49911496 19
3 2BEditing the I-Device of a SIMOTION station V4.1 3.2 I-Device and higer-level controller in one project If a project with SIMOTION stations V4.1 will be opened by SCOUT V4.2.1 or higher and STEP7 V5.5 HF4 or higher, the SIMOTION I-Device configuration can be edit. After changing the I-Device configuration a new GSD file (GSD V2.1 or V2.2) must be generated and installed. The substitute I-Device then is connected via the GSD file to the higher-level IO-Controller. The project can be compiled and loaded without errors. If the project is stored and archived in the format of Version V4.1 and after that imported in SCOUT V4.1 and STEP7 V5.4 SP5 it cannot be compiled without errors (see Fig. 3.2). Fig. 3-2 Compiler error message In that case the GSD file for the I-Device must be new generated and installed with SCOUT V4.1 and STEP7 V5.4 SP5. The substitute I-Device at the higher-level IO- Controller must be replaced. After that the SIMOTION project V4.1 can be compiled with SCOUT V4.1 and STEP7 V5.4 SP5 without errors. Please note that the new substitute I-Device must have the same device name like the belonging SIMOTION device. The system changes the device name by itself with any postfix. 20 1.1, Entry ID: 49911496