Looking for:
Wincc basic v11 sp2 download |
- Wincc basic v11 sp2 download
Remove any license keys present on the HMI device. After restoring has been carried out, re-install the license keys on the HMI device.
Non-licensed mode Runtime add-ons can also be used without a license without restriction. An alert for nonlicensed mode is presented every 10 minutes by a window requiring acknowledgment. When you install a license, the associated license key is removed from the license key storage location. Note A license key cannot be copied. The copy protection employed prevents the license keys from being copied.
Data backup Remove the license keys on the HMI device when backing up data on the HMI device and when creating a backup during device replacement. You use the Automation License Manager to back up license keys of a HMI device to the storage area of the license key. Observe all warnings and notices. This capability means you can store multiple licenses of the same type at one location.
Save all license keys of the HMI device to the same storage location. Invalid license after time zone change The installed license no longer functions in the following case. If you change the time zone on a WinCC PC as follows: From a time based on a complete hour to a time not based on a complete hour.
To avoid this inconvenience, uninstall the license key under the time zone setting that was set when the license key was installed. Example: You have installed the license key with a time zone setting based on a full hour. Then also uninstall the license key with a time zone setting based on a full hour. This behavior does not apply to the trial license.
Defective license A license is defective in the following cases: If the license key is no longer accessible at the storage area. If the license key disappears during its transfer to the destination drive. You can use the Automation License Manager to repair the defective license.
The system alerts you at brief intervals that you are working in non-licensed mode. You have the one-time option of activating a trial license. The trial license expires after 21 days. WinCC can no longer be started. WinCC cannot be started. An alert for non-licensed mode is presented every 10 minutes by a window requiring acknowledgment.
Availability of licenses The licenses for the products of the TIA Portal are usually supplied on the installation data medium and installed automatically by the Automation Licence Manager during the installation process of the TIA Portal. If you remove the TIA Portal, the corresponding licenses are also removed automatically. Licenses still required should be secured. Provision of the Automation License Manager The Automation License Manager is supplied on the installation data medium and is transferred automatically during the installation process.
If the Automation License Manager finds a valid license key for this software, the software can be used according to the license usage terms associated with this license key. Note For additional information on how to manage your licenses with the Automation License Manager , refer to the documentation supplied with the Automation License Manager. See also Notes on the system requirements Page 57 Starting installation Page 69 Displaying the installed software Page 72 Modifying or updating installed products Page 73 Repairing installed products Page 75 Starting to uninstall Page 76 Installation log Page Function of the installation log The progress during the following installation processes is logged in a file: Installing products Modifying or updating already installed products Repairing an existing installation Uninstalling products If errors occur during the installation process or warnings are issued, these can be evaluated with the help of the log file.
You can do this yourself or contact product support. Installation logs storage location The log file is the most recent file with the file extension ". You can enter this environment variable in the address bar of Windows Explorer to open the folder with the log files. With this information, Product Support can determine whether the installation was executed properly.
CAB files that were generated during earlier installation processes are saved with a date ID in the "Reports" directory.
Introduction Software packages are installed automatically by the setup program. The setup program starts once the installation medium has been inserted in the drive. Requirement Hardware and software of the programming device or PC meet the system requirements.
You have administrator privileges on your computer. All running programs are closed. Procedure To install the software packages, follow these steps: 1. Insert the installation medium in the relevant drive. The setup program starts automatically unless you have disabled Autostart on the programming device or PC.
If the setup program does not start up automatically, start it manually by double-clicking the "Start. The dialog for selecting the setup language opens. Choose the language in which you want the setup program dialogs to be displayed. To read the information on the product and installation, click the "Read Notes" or "Installation Notes" button.
The help file containing the notes opens. Once you have read the notes, close the help file and click the "Next" button. The dialog for selecting the product languages opens. Select the languages for the product user interface, and click the "Next" button. Note "English" is always installed as the basic product language.
The dialog for selecting the product configuration opens. Select the products you want to install: If you wish to install the program in a minimal configuration, click on the "Minimal" button. If you wish to install the program in a typical configuration, click on the "Typical" button. If you wish to personally select the products to be installed, click on the "User-defined" button.
Then select the check boxes for the products you wish to install. If you want to create a shortcut on the desktop, select the "Create desktop shortcut" check box. Click the "Browse" button if you want to change the target directory for the installation. Note that the length of the installation path must not exceed 89 characters. Click the "Next" button. The dialog for the license terms opens.
To continue the installation, read and accept all license agreements and click "Next". If changes to the security and permissions settings are required in order to install the TIA Portal, the security settings dialog opens. To continue the installation, accept the changes to the security and permissions settings, and click the "Next" button. The next dialog displays an overview of the installation settings.
Check the selected installation settings. If you want to make any changes, click the "Back" button until you reach the point in the dialog where you want to make changes. Once you have completed the desired changes, return to the overview by clicking on "Next". Click the "Install" button. Installation is started. Note If no license key is found during installation, you have the chance to transfer it to your PC.
If you skip the license transfer, you can register it later with the Automation License Manager. If the installation was successful, a message to this effect is displayed on the screen. If errors occurred during installation, an error message is displayed informing you of the type of errors. It may be necessary to restart the computer. If this is the case, select the "Yes, restart my computer now.
Then click "Restart". If the computer does not reboot, click "Exit". Procedure To install a Support Package, follow these steps: 1. Click "Support packages" in the "Options" menu. The "Detailed information" dialog opens. A table lists all support packages from the directory that you selected as the storage location for support packages in the settings. If you want to install a support package that is not in the list, you have the following options: If the support package is already on your computer, you can add it to the list by selecting "Add from the file system".
Then you can add it from the file system. Select the support package that you want to install. Click "Install. Close and then restart the TIA Portal. Displaying the installed software You can find out which software is installed at any time. In addition, you can request additional information on the installed automation software to be displayed. Procedure To display an overview of the software installed, follow these steps: 1. Click "Installed software" in the "Help" menu.
The "Installed software" dialog opens. You will see the installed software products in the dialog. Expand the entries to see which version is installed in each case. If you would like to display additional information on the installed automation software, click the link on the "Detailed information about installed software" dialog.
Chose the topic you want more information about in the area navigation. Modifying or updating installed products You have the option to modify installed products using the setup program or to update to a new version. Procedure To modify or update installed products, follow these steps: 1. The dialog for selecting the installation variant opens.
Select the check boxes of the product languages that you want to install. You can remove previously installed product languages by clearing the corresponding check boxes. Note Note that the product language "English" cannot be removed. Select the check boxes of the components that you want to install. You can remove previously installed components by clearing the corresponding check boxes. Note Note that you cannot change the target directory because the existing installation is being modified.
Click the "Modify" button. This starts the installation of the additional components. Note If the installation was successful, a message to this effect is displayed on the screen. Repairing installed products You have the option to repair installed products by completely reinstalling them using the setup program.
Procedure To repair installed products, follow these steps: 1. Select the "Repair" option button, and click the "Next" button.
Click the "Repair" button. This starts the repair of the existing installation. Introduction Software packages are removed automatically by the setup program. Once started, the setup program guides you step-by-step through the entire removal procedure.
You have two options for removing: Removing selected components via the Control Panel Removing a product using the installation medium Note The Automation License Manager will not be removed automatically when you remove the software packages, because it is used for the administration of several license keys for products supplied by Siemens AG. Removing selected components via the Control Panel To remove selected software packages, follow these steps: 1.
Double click on "Add or Remove Programs" in the control panel. The "Add or Remove Programs" dialog opens. Select the software package to be removed in the dialog "Add or Remove Programs", and click "Remove".
Select the language in which you want the setup program dialogs to be displayed and click the "Next" button. The dialog for selecting the products you want to remove opens. Select the check boxes for the products that you want to remove and click the "Next" button. Check the list with the products to be removed. If you want to make any changes, click the "Back" button. Click the "Uninstall" button. Removal begins.
Removing a product using the installation medium To remove all software packages, follow these steps: 1. Select the "Uninstall" option button and click the "Next" button.
System requirements for the migration tool The following system requirements apply to the use of the migration tool: All products used to create the source project must be installed. For example, all HSPs for the devices used in the source project are required.
Normally, the migration tool is installed without the TIA Portal. Because the TIA Portal has its own integrated migration function, a separate installation of the migration tool is not necessary. Procedure To install the migration tool, proceed as follows: 1.
Run the downloaded file. The setup program for the migration tool will open. First, select the language in which the setup should be displayed and click the "Next" button. The page for selecting the software language is displayed. Since the migration tool is provided exclusively in English, you cannot choose any other language for the installation.
Therefore, click "Next" to proceed to the next step. The page for selecting the product is displayed. The migration tool consists solely of a software component. Therefore, the migration tool is already selected. To create a Desktop icon for starting the migration tool, select the check box "Create Desktop icon".
Then click the "Next" button. The page for confirming the licensing terms is shown. Click on an entry in the list of license terms to read the selected license term. If you agree with all license terms, select the check box "I accept the terms of the displayed license agreement".
An overview of the installation is displayed. The installation is performed with the displayed settings. Uninstalling the migration tool The migration tool can be removed using the Control Panel. Procedure To remove the migration tool, follow these steps: 1. Open the Control Panel. A confirmation prompt appears. Click the "Uninstall" button to confirm this prompt. The migration tool will be removed.
Migration of existing projects You can migrate projects from earlier automation solutions to the TIA Portal. Each time you migrate, a new project is created for the migrated data with which you can then work. Any projects already open are closed first. The migration is then displayed in the table of the project history. From here, you have access to a log file that is created automatically for the migration. In principle, all products listed there are supported by the TIA Portal during migration.
Any additional requirements that must be met depend on the initial products that were used and the currently installed products. Procedure during migration The migration process is divided into the following basic steps: 1. In this case, you can directly migrate the source project. Migrating projects 4. Checking the migration log A log is created for each migration, in which the result of the migration is stored.
In this log, you can find information on project components that have been lost or modified, or, when applicable, the reasons why the migration of a project could not be performed. Check this log after migration. Immediately after completion of the migration, the log is displayed in the Inspector window.
You can also open the log from the project history. If a migration is not possible, you can decide where the log will be saved. Correcting the migrated project Because the configurations of the initial project may not always be completely compatible with the TIA Portal, not all configurations are transferred in identical form in the migrated project.
You should therefore work through the points in the migration log systematically. Excluding the hardware configuration from the migration If you know at the outset that hardware used in the initial project is not supported by the TIA Portal, you can exclude the hardware configuration from the migration.
In this case, only the software is migrated. An unspecified device is then generated in the migrated project for the devices contained in the initial project.
The hardware and network configurations and the connection are not migrated. You can convert the unspecified devices into suitable devices after the migration and create any network configurations and connections manually. Preparing projects with the migration tool Migrating projects with the migration tool.
Therefore, the initial project must first be converted to a compatible format for the migration. You then copy the migration file to the programming device or PC on which the current version of the TIA Portal is installed. Procedure for migration with the migration tool To perform a migration without the initial software, the following preparatory steps are necessary: 1.
Start the migration tool and use it to convert the source project to the migration file format with file extension ". This also includes all necessary service packs, hardware support packages and all expansion software that is needed to process the initial project. If individual products are not installed it may not be possible to perform the migration or the migration may be incomplete.
Copy the migration file to the target system on which a current version of the TIA Portal is installed. Note that the target system must have been installed with all software needed to configure the complete set of devices contained in the migration. Perform the migration within the TIA Portal, and specify the migration file as the source. Following the migration, check the log file and work through the information provided there for the newly created project in a systematic manner.
Read the information in the Inspector window with special care after the first compilation of the configuration. Click this shortcut. Alternatively, you can call the migration tool directly in Windows Explorer. To start the migration tool, click the "Siemens. Creating a migration file The section below describes how you can use the migration tool to convert the initial project into a migration file that can be read by the TIA Portal. Following conversion, this file is transferred to the target system and migrated there.
You can specify whether the migration file should contain the entire project, including the complete hardware configuration and the associated software, or whether you want to migrate the software only.
Requirement The suitable, original software with a valid license is installed for all configurations used in the initial project. The initial project is not provided with access protection. The initial project must be consistent, otherwise problem-free migration cannot be assured. Procedure To create the migration file, follow these steps: 1. Choose the path of the source file for the migration in the "Storage Location Path " field. Select the check box "Exclude hardware configuration" to migrate the software only.
Choose the path and the file name for the migration file in the "Intermediate file". Click the "Migrate" button. Result: A migration file is created. Finally, copy this file to the target system and migrate this file in the TIA Portal. See also Migrating projects Page 85 Calling the migration tool Page 84 Migrating projects with the migration tool Page Requirement There is already a converted file in the format AM11 available or the original software with a valid license is installed for all the configurations in the initial project.
Read the additional information on the requirements in the help for the respective products installed. Note System hibernation during the migration While a migration is running, the system should not be changed to the standby or hibernate mode. Otherwise the migration will be aborted. Procedure To migrate a project, follow these steps: 1. Select the "Migrate project" command in the "Project" menu.
The "Migrate project" dialog opens. Specify the path and the file name for the project to be migrated in the "Source path" field. Choose either a project in the AM11 migration format or in the format of the initial project. If you have selected a migration file that was created using the migration tool, the check box is disabled. In this case, you must specify if you wish to exclude the hardware configuration of the migration before the conversion with the migration tool. Choose a name for the new project in the "Project name" box.
Choose a path in the "Target path" box where the new project will be created. Enter your name or the name of another person responsible for the project in the "Author" field. Enter a comment in the "Comment" box, if you require one. Click "Migrate". Result The initial project is converted. The system outputs a message when the migration is complete. From here, you can directly open a log for the migration. The newly created project then opens in the project view.
The migration log is also displayed in the Inspector window. See also Post-editing integrated projects Page Migrating projects with the migration tool Page 82 Creating a migration file Page Displaying the history of the migration If a project was created by migration, the migration will be listed in the table of the project history.
You can open the migration log in the table. The time of the migration is also shown. Procedure To display the migration in an overview table, follow these steps: 1.
Select the open project in the project tree. Select "Properties" in the shortcut menu of the project. The dialog with the properties of the project opens.
Select the "Project history" group in the area navigation. The overview table is displayed. Displaying the log file of the migration A log file is created for each migration. The log file contains the following information: Migrated objects Modifications to objects made during migration Errors that occurred during migration.
Procedure To display the log file of the migration, follow these steps: 1. Click on the link to the log file in the "Log file" column. The log file is displayed in the Microsoft Internet Explorer. The following version of WinCC flexible is supported: WinCC flexible SP2 The following sections describe the operating devices that are supported and the required conditions for a successful migration.
If you wish to continue to use such projects in WinCC, you must first migrate them to a supported version of WinCC flexible. The data will not be evaluated to see if they are consistent in the project you want to migrate.
If errors or warnings are output in a source project during compilation, these will not be resolved as part of the migration. This means you should be able to compile the project without errors prior to migration.
Note the scope of a project during migration. The features of WinCC apply for migration. See Engineering system Page for additional information. Unique object names The objects are clearly identified by the folders in which they are contained in WinCC flexible.
Screen elements in groups are clearly identified by the group name. The name of screen elements must be unique within a screen. The uniqueness of the name is verified during migration. If a name is not unique according to the new rule, the object in question will be renamed. A renamed object will receive the suffix " Mign", where "n" stands for a sequential number.
Example: In WinCC flexible, tags located in different folders may have the same name. This means tags with the same name from different folders will be renamed during migration. Affected objects The following objects are renamed if necessary: Screens Screen objects Recipes Tags. Cancelling migration The migration is cancelled in the following cases: If the project to be migrated is opened in the engineering system or in Runtime. If not enough memory space is available on the hard disk to create a a copy for migration of the project.
If the migration cannot address the project database due to problems with the installed SQLServer. If the migration cannot address the project database due to missing user authorization.
If the project was created with a version not supported by the migration. Saving the project in the migration format You do not have to execute the migration of a WinCC flexible project completely on the PC on which the project is available. You can prepare the migration by saving the project in the migration format. The migration tool is available for saving a WinCC flexible project in the migration format. See the section "Auto-Hotspot" for more information on the migration tool.
A new project is therefore created automatically for project migration. You cannot migrate to an existing project. The migration can be started in both the Portal view and the Project view.
You should only migrate a project in a newly started TIA portal. Information on the migration of integrated project can be found in the Chapter Migrating integrated projects WinCC flexible Page If you only want to save the project in migration format, you can use the migration tool.
See Basics on migration WinCC flexible for additional information. Requirement A project from WinCC flexible is available. The project is not open in WinCC flexible.
Procedure Migrate a project in the Portal view as follows: 1. Change the information for the project to be created, if necessary. For example, change the project name or project path. The data to be migrated is created in the new project.
A new project is created and migration of the data is started: The Project view opens. The progress of the migration is shown in a migration window. All information about the migration is saved in a log file. The project is saved and a message displayed upon completion of the migration. The message contains a link that you can use to open the log. These devices contain the migrated data, such as screens, alarms and tags. Opening the migration log at a later point in time The migration log is saved together with the migrated project.
You can view the log at a later point in time. Open the log as follows: 1. Select the project in the project tree. Select the "Properties" command in the shortcut menu. Click "Project History" in the "Properties" dialog. Click on the log file. The migration log opens. Compiling a migrated project Once you have successfully migrated a WinCC flexible project, you need to recompile it before loading it to the HMI device. The project will only compile successfully if it was capable of errorfree compiling prior to migration.
If errors occur during compilation of the migrated project, they have to be eliminated. Once compiling is successfully completed, load the project to the HMI device. Once you have migrated the project, you must configure the settings for loading.
The dialog "Advanced Loading" is opened. Configure the required settings for the interface. Click the "Load" button. The project is recompiled and the dialog "Load preview" is opened. Expand the "Overwrite" entry and verify the settings for the following options: Would you like to overwrite the existing user administration data from this device Would you like to overwrite the existing recipe data on HMI system Configure the options as you want to use them in the project in the future.
Subsequently, load the project to the HMI device. There may be some functions in a WinCC flexible project that are not supported by a Basic Panel, for example, because the device type has been switched. These unsupported functions are not migrated. Adaptations before migration If the HMI device has changed in the project being migrated, the project needs to be recompiled before migration. The compilation process will adjust the size of the screens and screen elements.
Basically, all object types and functions that are available and can be mapped to the new project environment will be fully migrated. Some global object types are not migrated, for example, dictionaries and global libraries. Supported object types The following object types are supported for migration: Animations Scheduler User administration Area pointer Screens Screen template Data types Function lists Graphics lists Display and operating elements Migration supports all display and operating elements available on the supported HMI devices.
Alarms Alarm classes Alarm groups Project library Project languages. Unsupported object types The following object types are not supported by migration: Global libraries Dictionaries Project versions Change log. Migration of the screen template WinCC offers an extended concept for working with screen templates.
WinCC offers a global screen and several templates for each device. During migration of a template from WinCC flexible, the objects contained there and the properties configured in the template are migrated to different templates of WinCC.
The connection of the objects and properties to the respective template is automatically adapted. Migration of system functions The names of some system functions have changed in WinCC. System functions which have changed their names are renamed.
This concerns the following system functions:. Introduction The standardization of object properties from WinCC V7 and WinCC flexible requires changes to the object properties during the migration process. The migration calculates the changes in such a way that the representation of the objects after migration is the same as prior to migration. Changes made during migration result in different units of measurements and values in the configuration for some object properties.
Migrating the font settings of an object In WinCC V7 and WinCC flexible, the unit of measurement "point" is used to denote the size of the fonts used for an object. In WinCC, the unit of measurement "pixel" is used to denote the size of the fonts used for an object.
The different units of measurement result in changes to the numerical values for the font sizes after migration. Example: Font style before migration Arial 10 points Arial 16 points Tahoma 10 points Tahoma 16 points Font style after migration Arial 13 pixels Arial 21 pixels Tahoma 13 pixels Tahoma 21 pixels.
In WinCC, the range of values for object margins is limited to values between 0 and Introduction You need to make some special considerations when migrating tags. The following aspects should be distinguished: Migrating data types of tags Migrating internal tags Migrating external tags Tag names. You can find additional details on this in the section "Migration of data types WinCC flexible Page ".
Migrating tags Tags are always fully migrated. Only the data type names and tag names may change due to migration. Migrating names of tags In WinCC flexible, tags located in different folders can have the same name.
You can find additional details on this in the section "Basics on migration WinCC flexible Page 88 ". Migrating alarm groups Migration will migrate only those alarm groups actually in use. Alarm groups with an ID from will be migrated A corresponding alarm group is created in WinCC for each alarm class in the system. These alarm groups created by the system are assigned IDs beginning with the number 32 and consecutively incremented. The 4 pre-defined message classes in every WinCC project are automatically given IDs by their alarm groups.
Additionally created alarm group and an additional ID is assigned to each user-defined alarm class. This step also changes the assignment of the alarm group names to the IDs. Also note: When migrating alarm groups that supposedly have the same group name, the migration adapts the name.
This occurs, for example, when a group name contains a space at the end of the name. The migration deletes all existing spaces at the end of names. If two groups obtained the same group names due to this deletion, the migration adds the suffix " Mign" to the group name of the following alarm groups, where "n" stands for a sequential number.
The changed concept may cause the display of messages to change following migration. You then have to deactivate this display class in WinCC. You then have to activate this display class in WinCC. The display class is dependent on the settings in STEP 7. To activate the display in WinCC, the display class "0" must be activated.
Introduction WinCC offers the same options for configuring projects in different languages as those available in WinCC flexible. All languages supported by WinCC are included in the migration of a project. Migrating language-dependent content The following language-dependent content is migrated: Project languages Project texts Fonts for display in runtime Language-dependent graphics You need to consider the following when migrating language-dependent content: The operating system on the PC performing the migration must support the project languages used in the project.
The fonts used for runtime display must be installed on the PC performing the migration. Dictionaries are not supported by the migration. Editiing language of integrated projects following migration During migration of an integrated project, the project components to be migrated from STEP 7 and WinCC flexible also bring their respective settings for the editing language.
In WinCC there is only one editing language for all project components. Migration activates for the mgrated project the editing language which was set in STEP 7 prior to migration. If this setting is not the same as the setting from WinCC flexible, the configured texts are no longer visible in WinCC.
No text is displayed at the usage locations, or only the entry "Text" can be seen. To make the texts visible, you must change the editing language. Click the "Tasks" taskcard at.
Unsupported languages The migration of language-dependent content depends on whether or not WinCC supports the respective language. If a project only contains project languages not supported by WinCC, the project will not be migrated. If a project contains supported and unsupported project languages, only the supported languages will be migrated.
The editing language and reference language are set to a supported language. Introduction You need to consider two different cases when migrating from libraries: 1. Migrating a project library 2. Migrating a global library.
Migrating a project library A project library is stored together with the project data in the project file. For this reason, a project library is migrated with the same restrictions as the project data.
Migrating a global library Global libraries are not supported by the migration. The library objects used in the project will be migrated, however. The library objects are copied when used in the project and then no longer have a connection to the library. To migrate a global library, you must copy or move the objects contained in the library to the project library. The objects are then included in the migration. In WinCC, you move the migrated objects to a new global library that is created.
You can copy or move both individual objects or entire library categories. Introduction When migrating a project, only the configuration data will be migrated. The runtime data are not affected. You need to update the runtime data following migration. The runtime data consists of the following: Runtime project The runtime project contains the compiled project data.
Recipe data and user administration The recipe data and user administration are data that can be changed in runtime. If the recipe data and user administration were changed in runtime, you need to back up this information from the HMI device before you load the migrated project.
You can then load the migrated project to the HMI device. Finally, you load the saved recipe data and user administration back to the HMI device. You can find additional details on this in the section "Auto-Hotspot". Introduction To continue using the recipe data and user administration in a migrated project, you first need to back up this data from the HMI device.
Then load the data into the migrated WinCC project. Use ProSave to back up the data. Procedure Proceed as follows to back up the recipe data and user administration: 1. Start ProSave. Select the device type and the connection parameters in the "General" tab. Open the "Backup" tab. Select the "Recipes from the device memory" entry in the "Data type" box. Do not select "Complete backup" because otherwise you will not be able to select separately when restoring the recipe data.
Navigate to the desired location in the "Save as" box and click "Start Backup". The recipe data are saved. Select "User administration" in the "Data type" box and click "Start Backup". The user administration is saved. For additional information refer to the online help for ProSave.
Alternatively, you can back up the recipe data and user administration via the ProSave integrated in WinCC flexible. Back up the recipe data and user administration as described in steps Introduction To continue using saved recipe data and user administration after the migration, you first need to compile the migrated project and load it to the HMI device.
You can then transfer the saved data to the HMI device. Use ProSave to restore the data. Requirement The migrated project has been transferred to the HMI device and is running in runtime. Procedure Proceed as follows to load the saved recipe data and user administration to the HMI device: 1. Open the "Restore" tab. Navigate to the location of the saved recipe data in the "Opening Click "Start Restore". The recipe data will be transferred to the HMI device..
Repeat steps to restore the user administration. The user administration will be transferred to the HMI device. Restore the recipe data and user administration as described in steps The connections remain intact. Migrating an integrated project When migrating an integrated project, the same requirements apply for the WinCC flexible component as those for the migration of a non-integrated WinCC flexible project. The "Online" property must be activated on the configured connection.
A connection with deactivated "Online" property is not migrated. In addition to the requirements for the WinCC flexible component, there are also requirements for the STEP 7 component of the integrated project. For detailed information, refer to the documentation for STEP 7. To fully migrate an integrated project and then edit it, the following components must be installed on the PC performing the migration: STEP 7 V5. An integrated project is always fully migrated. If you only want to migrate the WinCC flexible project it contains, you need to separate it from the STEP 7 project before the migration.
The project is opened with WinCC flexible. WinCC flexible saves a non-integrated copy of the project.
During migration, the data is copied from the existing project and migrated to a new project. STEP 7 and all add-on packages used are installed. The TIA portal is newly started. No project is open in WinCC. The integrated project is not open. Procedure Proceed as follows to migrate an integrated project in the Portal view: 1.
A message is displayed upon completion of the migration. Once migration is completed, save the project. Once the migration is complete, you will find a newly created device for each migrated HMI device and controller in the project tree. These devices include the migrated data. The naming takes place in accordance with IEC conventions. Because only the names change, there are no changes to the internal tags for the configuration.
Migrating external data types See the following pages for how to map the available communication drivers. Mapping of the S7 data type "Char" The S7 data type "Char" is a data type for mapping characters according to the specification.
However, since this data type is often used for reading and writing numerical values, it is mapped in WinCC to the S7 data type "Byte". If this should be the case during migration, an alarm will appear in the output window. If the S7 data type "Char" is used for numerical values and negative numbers were configured at the point of use, the result is an error in mapping to the S7 data type "Byte".
The S7 data type "Byte" cannot map any negative numbers. You have to adapt the configuration accordingly to correct the error. Use a signed data type, such as the data type "Int", for processing positive and negative numerical values. If the S7 data type "Char" is used for mapping characters, you must change the configuration after migration. To represent characters, use the data type "String".
When an integrated project is migrated, the data type "Char" in WinCC is also migrated to the data type "Byte". As a result of changing the data type of the HMI tag, symbolic addressing of the tags in question is not migrated. After migration. If you want to restore symbolic addressing, you have to change the configuration accordingly after the migration. Mapping an array of the S7 data type "Char" An array of the S7 data type "Char" is mapped to an array of the data type "Byte" during migration.
If an array of the S7 data type "Char" is used for numerical values and negative numbers were configured at the point of use, the result is an error in mapping to an array of the S7 data type "Byte". Mapping of the S7 data type "Counter" An external tag with the S7 data type "Counter" with counter address is mapped to the S7 data type "Counter".
The address will be retained. If an external tag with the S7 data type "Counter" addresses a data block or a bit memory address, it is is mapped to the S7 data type "Word". The S7 data type "Counter" has a value range of Ensure that you are observing the value range. The length of the array corresponds to the length of the originally configured data type "StringChar".
The expression for an array with an element is "Array[ Mapping of the S7 data type "Timer" An external tag with the S7 data type "Timer" with timer address is mapped to the S7 data type "Timer". If an external tag with the S7 data type "Timer" addresses a data block or a bit memory address, it is is mapped to the S7 data type "S5 Time". Introduction When an integrated project is migrated, the complete project will be migrated with components from Wind and STEP 7. Configured connections between control and visualization remain intact.
Migrating an integrated project When migrating an integrated project, the same requirements apply for the STEP 7 component as those for migration of a non-integrated STEP 7 project. For detailed information, refer to the documentation for Wind. This enables you to convert the initial project to a format that can be read for the IA Portal. Migration of the STEP 7 part of an integrated project An integrated project is always fully migrated.
Individual components cannot be migrated on their own. Then, save the project again and select the "Reorganize" function during saving. The Wind parts are then automatically removed during the saving of the copy. Migration of an integrated project without the hardware configuration You can migrate an integrated project just like any other project without the hardware configuration.
In this case, only the software of the initial project is migrated. The STEP 7 devices, network configurations, connections and interrupts used in the initial project are not migrated. However, HMI devices are always retained even if you migrate without hardware configuration.
HMI modules that are plugged into a PC station are converted to a separate Station during the migration. References to HMI devices are not imported during migration. The following chapters describe, by way of example, how you post-edit an integrated project after the migration, in order to restore the full functionality of source project. Migration will be canceled. Post-editing integrated projects If you have migrated an integrated project without hardware configuration, unspecified CPUs are used instead of the CPUs of the original project.
Since no connection can exist between an unspecified CPU and an HMI device, connections from the source project are also imported only unspecified. The following figure shows the state after a Migration without hardware configuration in an example project:. To continue to use an integrated project after the migration, follow these steps: 1. Convert the unspecified devices into suitable devices again.
Connect all HMI tags to the newly created integrated connection. Delete the non-integrated HMI connection. You can define general parameters and home the CPUs already in the user program. However, the project is not fully functional until the unspecified CPU has been specified. Share your experience WinCC V7. Direct download via magnet link..
Wincc V11 Crack Download wincc-vcrack-download. Download wincc flexible sp3 download rapidshare. Download wincc 7. Download "wincc 7. Comfort,,V11,,Download,,Torrent,, wincc-comfort. Phn mm Wincc V13 Pro Runtime l mt. Visit us and download wincc 7. Free downloads. Look at most relevant Wincc v11 torrent websites out of 15 Thousand at KeyOptimize.
Wincc v11 torrent found at. Free download wincc v11 sp2 download torrent Files at Software Informer. Audit Viewer enables the user to display, query, filter, print and export the following audit..
No comments:
Post a Comment