Looking for:
Wincc basic v11 download free
Country-specific features, however, are not only available for texts. There are many instances when it is also necessary to adapt graphics to country-specific conditions, which might, for example, rule out the use of certain colors or which take regionally established operating symbols into consideration.
For this reason, the central graphic collection of the system also supports the management of multi-language graphics. Investment security as configuration data can be migrated Implemented solutions and configurations and applications that have been created using a great deal of expertise and effort are among the most valuable possessions of machine manufacturers and plant constructors or system integrators.
Investment security therefore means that any innovation in the engineering software, however far-reaching and revolutionary it may be, must never lead to customers no longer being able to use their engineering efforts. SIMATIC software has always been developed in such a way that a migration is ensured to the greatest possible extent with the lowest possible outlay.
After the migration, the engineering data is available in WinCC. It is also possible to import the Runtime data such as logs and alarms during the migration. In this way, the history of a running system is not lost after a migration. HMI configuration data can be easily created via this. HMI tags and alarms can also be exported. This is helpful for translating them independently of the engineering software.
When exporting the texts, the point of usage and, for example, the name of the corresponding screen or alarm is also exported, so that the text can be translated in context. After the translation, the XML file can be re-imported into the TIA Portal project and the translated texts are available in the configuration data. Simulation systems provide effective support with the development of programs and the actual application.
A simulated test environment including controller and process reduces, for example, commissioning times and thus costs. Depending on the progress of the project, the functionality to be tested, and the degree of integration, three kinds of simulation are available:. HMI tag simulation with tag table The testing of the configuration without a connected controller or without a running process via the tag simulator cost-effectively checks an HMI project for inner consistency.
In the simulator, the configured tags are simulated; for example, do the configured color changes agree with the value pattern of a tag? The configured tags can be manipulated, activated and deactivated in the course of simulation. The simulator provides various kinds of simulations for this sine, random, increment, etc.
HMI project simulation with a connected, real controller The simulation of a WinCC configuration in communication with a real controller provides the greatest degree of integration and accuracy. The PowerTags are directly provided with the values of the real process in the plant.
The Compatibility Tool is a function provided by the Industry Online Support with which you can select compatible software products or check the compatibility of existing configurations. The WinCC Engineering Software is available on a graduated price and performance basis, that can be tailored to your specific operator control and monitoring devices in an optimum way.
Upward compatibility is always ensured within the WinCC offering. You can upgrade your version by purchasing power packs. Powerpacks give the user the option to adapt the engineering software to increasing requirements at any time.
You cannot use powerpacks to change a program version. WinCC Basic V WinCC Advanced V To keep you program up-to-date you can purchase Upgrades or sign a Software Update Service contract.
In this case the customer receives so called Combo Licenses which allow engineering on both platforms. These Combo Licenses can be upgraded like normal Floating Licenses when a new program version is available.
Owners of a V15 license can update their program version to V WinCC Comfort V WinCC Professional V V14 max. All you need is a valid software license for the latest available version.
Up to 32 alarms and up to user-definable analog alarms can be derived from one PowerTag. Moreover, internal tags without process linking are available for free as additional system performance. Within the framework of Online and Technical Support, Siemens Industry offers a wide range of services.
Online Support, Technical Support Siemens Industry’s spare parts services are available worldwide and provide smooth and fast supply of spare parts — and thus optimal plant availability. Further education for all Siemens industrial products – directly from the manufacturer, individually, with the latest methods. You want to discuss your specific challenges with us or are looking for the right project partner? Contact our regional offices — we are looking forward to hearing from you!
Perfect access to automation in digital enterprises: complete access to the entire digitalized automation. Whether single-user systems, multi-user systems, or even widely distributed systems: you can use Siemens SCADA systems to visualize machines, lines, and entire plants and thus ensure transparency. Do you need the optimum configuration for planning your project?
This page requires JavaScript in order to be fully functional and displayed correctly. Please enable JavaScript and reload the site. It looks like you are using a browser that is not fully supported. Please note that there might be constraints on site display and usability.
For the best experience we suggest that you download the newest version of a supported browser:. Benefits Innovative configuration interface based on the latest software technologies Comprehensive library concept for user-definable objects and faceplates Intelligent tools for graphical configuration and mass data handling. An operating philosophy and a data model without loss of functionality.
On-the-fly data consistency. Cross-reference list and display of screen properties. Ready-to-use diagnostics. Ready-to-use diagnostics The timely knowledge of faulted or faulty modules and devices is essential for avoiding long downtimes. Engineering Tools. Configuration without dead ends. Configuration without dead ends Time-saving configuration means: delegating tasks.
Configuration with helpful details. Configuration with helpful details Engineering time is expensive and yet it is often wasted on time-consuming detailed work. Configuring the dynamic way. Configuring the dynamic way It has long been known that animations and dynamic objects are not a gimmick, but rather they are an effective means of improving the operating ergonomics.
Configuring with tables. Configuring with tables Automation tasks can generally be grouped into different focal points, for which there are special input screens. Libraries and Faceplates. For example: Can the user only save and retrieve objects of a specific complexity in libraries? Can the library elements be protected from unauthorized access?
Can libraries be integrated in projects or can they be deliberately created to be cross-project by design? How high is the adaptation effort required for the integration of library elements in a project? Libraries – versions and objects. Libraries – versions and objects The libraries can be used to the same extent when creating a control program and when configuring the HMI application. Libraries are available in two versions: Objects that are frequently needed in the current task are stored locally in the project library.
Global libraries can be saved on a fileserver, for example, and then be utilized by several users Libraries contain two basic types of objects: Types are objects that can be centrally modified Copy templates are simple copies of configuration objects If types are modified, all occurrences of this type in a project are automatically updated by the library management system if the user approves the update.
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. K3SC Win ECIF Windows 8, G5-Series Vista 32bit and 64bit. G5-Series Win7 32bit and 64bit. G5-Series Windows 8, G5-Series WinXP.
SigmaV – USB driver for bit systems. Same functionality and supported devices than Sysmac Studio Standard Edition except for the controller. CX-One software allows users to build, configure and program a host of devices such as PLCs, HMIs and motion-control systems and networks using just one software package with one installation and license number. Download CX-One v4. It can be manufactured for the customer. Download NB Designer V1. CX-DRIVE reduce the time and complexity of configuring, commissioning and maintaining servos and inverters with a single software tool.
Download FQ Tool V2. Machine Expert v1. Machine Expert Basic v1. Twido Suite. ZelioSoft2 V5. Vijeo Designer V6. Vijeo Designer Lite V1. SoMove V2. Lexium CT. Motion Sizer V4. SoSafe V1. Proclima v8. Efficlima v2. Download Machine Expert v1. Download Machine Expert Basic v1. Download Twido Suite.
Download ZelioSoft2 V5. Download SoMachine v4. Download Vijeo Designer V6. Download Vijeo Designer Lite V1.
One moment, please.SIMATIC WinCC V7 Basic Software
The engineering framework into which the software products are integrated standardizes all shared functions — also in their on-screen representation. User benefits range from intuitive operation through the editors’ integrated intelligence to the advantages of a shared database, which ensures highest transparency and absolute consistency. Reusability saves engineering effort and simultaneously increases the quality of the solution.
Reusability extends to acquired knowledge in using the software just as much as it does to existing engineering blocks that have been developed and tested. A comprehensive library concept makes them available for new projects, no matter whether they are single operator controls or entire visualization solutions. For the first time, the TIA Portal combines the engineering systems for the diverse automation tasks. The shared framework, uniform interface, and the same type of configuration of comparable automation tasks ensures a short familiarization period with a high recognition value.
For decades, the development of automation software was aimed at more functionality and more efficiency. Engineering software was developed to the point where it became a highly specialized, tailored tool for a given task. Only with the increasing importance of software ergonomics did software developers begin to look beyond their own tool and begin to include the approaches of other developers with regard to user interfaces in their considerations.
The look and feel of the software products also became more uniform under the influence of office software. In this development, the TIA Portal represents the next logical step: from similar to shared, from related to integrated. The system generates all of the necessary settings, such as the connection, HMI tag and screen object for you. Whether you have selected an individual tag or are using a multiple selection plays no role in this. A user-friendly selection window allows you to select the corresponding object.
The entire TIA Portal provides selection windows for configuration, which eliminates error-prone, manual and especially multiple entries of the object names. One problem of traditional engineering systems is guaranteeing consistent data management. Every engineering tool only guarantees data consistency within its own system. Even if an attempt is made to standardize the interfaces, the configuring engineer is mainly responsible for the availability and consistency of the data, with all of the accompanying disadvantages such as additional work expenditure and increased susceptibility to errors.
The TIA Portal is based on shared data management: Any changes to application data which are made at any point in a project are automatically and immediately repeated at all of the other points of use. The various editors of the TIA Portal do not have to be opened for this. For service or plant personnel, it is often difficult to get acquainted with a project and to analyze the individual project specifics.
The ideal tools in this case are a cross-reference list with the filtered tabular listing of all of the tags, screens and functions defined in the project and the central display of the screen properties. The different views show where the object is used or what other objects are used by the selected object. There are no program limits for cross-reference lists either, which means that even linked PLC tags of a screen object are displayed in the respective blocks.
In this way, the TIA Portal creates transparency in the project and facilitates the change configuration even after a long period of time. The timely knowledge of faulted or faulty modules and devices is essential for avoiding long downtimes.
Therefore, constant monitoring of the plant is of the utmost importance. The TIA Portal provides support with its ready-to-use diagnostic mechanisms.
No additional comprehensive configurations of the diagnostics are necessary. Activating the devices for the system diagnostics generates alarms derived from the configured plant layout in the “Devices and Networks” editor.
These can be displayed in the HMI. In addition, WinCC provides a diagnostics viewer for the Comfort Panels, which can automatically display the information and alarms. If you want to significantly lower costs, you will need simple and efficient tools for configuring — and intuitive operator prompting. Time-saving configuration means: delegating tasks. One example is the device wizard: The most important settings can be configured right when the device is being created. User-defined settings can be saved and imported directly when creating another device.
There is no need for redefining. This allows you to ensure that all of the devices of a production line have the same basic configuration and are identical in appearance. Often a comparable WinCC project already exists and a great deal of it can be imported.
Even if it has been designed for other target devices, this does not mean that the configuration must be started from the beginning, because the configuration is freely scalable. In the machine-level area, the target HMI device can be easily switched via the device switch-over.
The system provides detailed information about any functions that might be different and detailed specifications for adapting the configurations. System expansions and thus project adaptations can be carried out with a minimum of outlay. Engineering time is expensive and yet it is often wasted on time-consuming detailed work.
User-friendly functions, like the familiar ones from special graphics software, effectively support and speed up the creation of precise, visually appealing HMI screens. The graphics editor allows, for example, the alignment and positioning of screen objects by means of adjustable grids, snaplines that can be hidden or shown, functions such as horizontal and vertical centering, or the even distribution and alignment with adjacent objects.
There are no more time-consuming manual pixel corrections. The WinCC “Screens” editor supports configuration in 32 screen layers. For complex screens involving several overlaid objects, individual levels can be hidden to provide a clearer overview. To this end, all layers with the screen objects they contain are clearly displayed in the “Layout” task card. The editor gives you the capability of conveniently moving the objects between the layers at a central point.
The layer assignments in the object’s properties are updated automatically. Of course, this also applies to grouped objects. Individual objects can be conveniently removed from the group, added, detached, and moved by means of dragging and dropping. The grouping of any screen objects facilitates working with many individual elements. All properties of grouped objects are displayed at the group can can be changed there without ungrouping the group.
It has long been known that animations and dynamic objects are not a gimmick, but rather they are an effective means of improving the operating ergonomics. A side-effect which must not be underestimated: The translation costs for multi-language configurations are reduced with each image. The increasing quality and resolution of the displays on HMI devices and improved performance result in new capabilities of integrating more complex animations.
WinCC accomplishes the creation of dynamic objects in minimal time. No programming knowledge is required. For many standard tasks in Runtime, pre-defined functions can be easily selected by means of drag and drop. If the requirements are very individualized, dynamization can also be implemented on the basis of integrated VB scripts.
Automation tasks can generally be grouped into different focal points, for which there are special input screens. Editors for creating screens, the alarm system, the tag management, the blocks, the device configuration, etc.
At many points in the TIA Portal, there are table-based editors, which give the user a quick and simple overview. The immediate mastering of editors, even at first glance, thanks to their uniform appearance, the simultaneous changing of many objects, and even the simple copying of properties inevitably increase the efficiency.
Well-known office functions are available in the TIA Portal for conveniently and quickly configuring mass data. An example: You can intelligently create hundreds of tags with only one movement of the mouse. Either the properties are retained, object names are adapted, or addresses are increased automatically.
In doing this, each editor supports the implementation of an individual special task, e. Cross-relationships between the individual editors are often difficult to track. As a result of this, an object-oriented approach was chosen for the WinCC tag editor. In addition to the configuration of the tags, a determination can also be made as to whether this tag should initiate an alarm and the logging of it. This not only helps the first time you create a project, but it also helps later by providing a quick overview of existing configurations.
The use of building blocks and libraries are work techniques that have been around as long as the copy function itself. The benefits of these techniques, such as time savings, reusability and guaranteed quality are obvious. In actuality, the benefits depend directly on how comprehensive and consistent the library idea is implemented in a library concept. For example:. The benefits of reusability can only be fully utilized if a library concept combines a very high degree of flexibility with practicality and user-friendliness.
The library concept of the TIA Portal ideally meets these requirements. The libraries can be used to the same extent when creating a control program and when configuring the HMI application. The library can be structured in a user-specific way, according to the requirements of the project. Libraries can contain all types of configuration objects, from simple HMI basic elements and entire screens to completely configured HMI devices.
An object that is stored in the library only has to be configured once. Subsequently, it can be reused as often as necessary. Objects that are frequently needed in the current task are stored locally in the project library. The project library is characterized by the fact that it belongs to the project and is opened, closed, but also saved along with it. Objects that are used across projects can be managed in global libraries. Global libraries can be saved on a fileserver, for example, and then be utilized by several users.
If types are modified, all occurrences of this type in a project are automatically updated by the library management system if the user approves the update.
Types are either user-defined data types HmiUDT or faceplates. User-defined data types can be used to describe the data of a complex automation object e.
As an interface to a faceplate they reduce the wiring overhead, because, as a result, only one structured tag of the same data type can be assigned to the interface of the block. Faceplates are created as a group of display and operating objects, so that they can then be used like other screen objects from a library.
A faceplate integrates itself into a project via its interface. Only the user-defined properties that are important for the block to function during runtime are set at this interface. The user then only has to deal with this concentrated interface in order to define the dynamic properties of the block and the screen objects it contains. The central modification capability also improves the error correction at this point or the subsequent expansion of previously used instances of the faceplate.
WinCC already provides a large number of scalable and dynamizable objects in standard HMI libraries:. Finally, the “HMI Symbol Library” contains a number of technological and industry-specific objects such as pipes, motors, valves, etc.
The openness of the Engineering Software manifests itself in more than just one way: individual functional enhancements by employing scripts, importing or exporting mass data, e.
Openess after all is also a perequisite for a comprehensive Runtime simulation. Normally, screens, links and dynamic processes are configured via simple and user-friendly dialogs. For individual, flexible expansions, VBScript provides a powerful and easy to learn script language based on Visual Basic. A user-friendly editor and code templates also facilitate the programming. The Auto complete function permits high-speed programming of the accesses to runtime objects and a simple creation of control sequences in the script.
Debugging is possible in the simulator during the engineering and, if required, also at runtime. The scripts themselves have access to the properties and methods of all WinCC graphic objects, to ActiveX Controls and to the object model of applications from other manufacturers.
This allows the dynamic behavior of objects to be controlled, and it also allows a connection between WinCC and applications from other manufacturers to be established easily e. Machine manufacturers normally supply customers from around the world. The localizability of user interfaces has long been an indispensable feature in terms of global competition. At the same time, the customers of machine manufacturers and plant constructors are becoming increasing multinational in their structure, but for reasons of productivity and quality assurance they insist on the global standardization of production processes in their plants.
The service personnel of a machine manufacturer provide support to plants in several countries and the capability of being able to switch over to a familiar interface language supports both the teleservicing and onsite service.
Finally, it is no longer unusual that the operators of a plant have varying degrees of proficiency in various languages, which makes it a good idea in terms of operational safety to have the capability of switching over to the respective mother tongue.
All of these are reasons for deciding on HMI software that is not limited in terms of language diversity. WinCC supports up to 32 languages for creating multi-lingual configurations, up to 32 of which can be selected during operation depending on the target system. Vice versa it is of course possible to import all these texts after they are translated to any language.
The appropriate operator language is independent regardless of the language of the installed operating system. Every operator can individually choose the language of the displayed texts. For example it is possible to display messages simultaneously using different languages when working in international teams. WinCC allows you to implement display languages in a simple and cost-effective manner. This is independent of the language set in the operating system.
This means that it is possible to display multiple languages parallel to each other, such as message texts in European and Asian languages. This makes commissioning considerably easier in international teams.
Resulting from the integration of the cross-reference editor it is on one hand possible to locate very fast the places where a special variable is used for example in case of troubleshooting. On the other hand it is possible to release non used variables to align the license costs optimal to the actual project.
Using the WinCC User Administration you consistently can assign and check the access rights of the users regardless if it is a local access or if the access is web based. For up to user groups with up to single users each the access rights for WinCC functions can be administered. In total it is possible to assign different permissions. Therefore it also covers the extended FDA safety requirements.
But it is also possible to login using a chip card where name, domain and password is saved in encrypted form. The modern graphics system of WinCC supports the work of a project engineer as well by the use of standardized preconfigured picture components as when creating user definable picture components and faceplates.
The use of these components enables the project developer to create his own at any time reusable company specific project standards which results in a much shorter Time-to- Market for the project. Global settings which can be done in the graphics system enable the project engineers to implement once defined company standards in a WinCC project and to apply these timesaving to all picture objects which have the same attributes.
It is also possible to export these settings and to import them again to any other WinCC project. On one hand this possibility supports the in-house standardizing in an efficient way and on the other hand it provides the opportunity that several project engineers can work on huge applications simultaneously in accordance with the company standards.
When creating images it is of course possible to do Direct2D soft shadows and to integrate SVG — files. Instead of using discrete colors the color palette is working with color indexes. This enables the user to realize customer-specific designs in a very simple way. If for example a customer wants to change the color from red to orange he only has to assign the color orange to the index for the color red. While changing this, the color of all red objects having the same index changes to orange Applying modular design makes it simple to create and to centrally manage custom specific faceplates.
Changes are automatically applied to all points where the faceplate is utilized. For example efficient operation is possible by the use of application specific menus and toolbars.
It is possible as usual in Windows to either fix them or to leave them movable. This makes configuring even more efficient. Libraries and wizards accelerate make the setup of projects easier. Therefore they reduce the error rate dramatically. Historical process information is saved as WinCC process value archives in the integrated, high-performance SQL database.
The memory requirement is optimized through efficient algorithms and intelligent, loss-free compression functions such as the Swinging Door algorithm. To reduce the amount of data for long-term archiving, the data can be compressed even further.
To do so, the maximum value, minimum value or weighted mean, the sum or the difference is calculated for adjustable periods of time e. In addition to automatic archiving, it is possible to add values manually to the archive or to modify archive values later with the appropriate authorization. This is required, for example, for laboratory values in some industries. For reasons of traceability, these values are marked as “modified manually” and the process is documented with an operation message.
Efficient controls are integrated into WinCC process pictures for the display of current or historical data. Process values can be displayed as a table or analyzed using a trend display.
The display is either predefined or can be adjusted individually by the operator, if authorized. Numerous means of representation guarantee the best possible overview. The freely configurable toolbar functions also provide the option of integrating project-specific functions.
In combination with the Ruler Controls, there is also the option of performing statistical calculations online without the need for programming. The relevant statistics — maximum and minimum value, average value, weighted mean, integral and total — are displayed without delay for a time range selected in the Trend Control.
Here, the display of the message information can be adapted precisely to the requirements of the operator. The settings made can be saved in user-specific or global templates. The contents can then be exported directly as CSV file or printed out as report.
A freely definable toolbar function also offers a maximum degree of flexibility. For examples, project-specific functions can be integrated. To maintain an overview when there is a large numbers of incoming messages, unimportant operating messages can be suppressed from the screen display via an alarm hiding function.
The hidden messages are then archived in the background. Numerous integrated statistics functions allow a comprehensive analysis of process states. The message hit list shows how long certain messages were pending on average and in total message duration and similarly the average and the total acknowledgment time.
Of course, the messages can be filtered here by relevant events, message locations and time intervals. This indicates quickly where critical points and bottlenecks in the production are located.
To sort the messages in the message display for an evaluation, you can simply select the column heading and the required sorting criterion for example, “Frequency, descending”. Historical plant data can be simply compiled in web-based dashboards or reports without programming knowledge. This ensures comprehensive access to plant information for each target group in the company managers, quality assurance, maintenance at all times. During runtime, this data is exchanged simultaneously with the automation partners e.
All change data is recorded in a tamper-proof database – the so-called Audit Trail – and displayed using the Audit Viewer. The two calendar options expand WinCC with calendar-based functionality. Joint calendar control is hereby used to plan times or validity periods.
To be able to meet growing requirements, the visualization must be expandable at any time without causing technology incompatibilities or requiring completely new configurations. Redundancy solutions for highest availability and security can be built up as well. In addition to scalable configurations, WinCC options and AddOns offer customer-fit extensions for technological and industry specific solutions. In this way, several coordinated operator control and monitoring stations can be operated together with networked automation systems.
All devices with HTML5-capable browser are supported. Using the WinCC PerformanceMonitor shows weak points of production and to suitable optimization potential can be derived. Therefore, plant-specific key figures KPIs for individual devices, machines, or entire production lines can be calculated and analyzed in machine or line-oriented production plants.
The required formulas e. It is possible to link KPIs with context data to get further correlations e. Thanks to innovative technology, all important information is consistently available — rapidly, flexibly and safely. Benefit from information provision anytime and anywhere with mobile SCADA solutions — also with available tablet or smartphone hardware.
The application of multitouch gestures in industrial environments opens the door to modern operating concepts. Using such a flexible access to gain plant data extends the classical control room as it is today. Depending on the application area it is possible to monitor only as well as to control the process. Because of the individual access to process data using the mobile Scada the user will be informed. The reports created are always available on Web-based user interfaces and can be automatically distributed by email.
State-of-the-art, innovative operational concepts with multi-touch gestures are rapidly gaining significance in the industrial environment. The gestures that users know from consumer devices are particularly useful for more simple and intuitive operation of complex production plants.
You can implement functionality such as zoom or wiping, for example, for screen navigation and panning. A wide range of specific and generic communication channels and protocols give you powerful and flexible ways to connect WinCC to a variety of OT devices and forward data to other IT applications e.
High performance, latest technology, easy data exchange to the IT level. Leverage valuable data from production management via an open bidirectional REST interface. It reduces the complexity of interfaces and data formats. Extensions of the runtime system Using WinCC it is possible to realize connections and dynamic sequences without programming only by the use of standard dialogues. Examples for such scripts are the conversion of values or the automatic start of reports or of individual messages.
When programming VB scripts you are supported by the use of a proprietary, comfortable editor with debugging support. When using scripts you have full access to the properties of all WinCC graphical objects and to the controls as well as to the object model of WinCC and the applications of other manufacturers.
This is very helpful for writing custom specific enhancements including debugging. By using this functionality engineers and users can make full use of their Visual Basic-knowledge. VBA can be used to realize own standards, to handle recurring tasks, to create menu entries or configuration dialogues.
This saves time and money. The WinCC function modules are exposed using interfaces which allow access to the data and the functions of the configuration environment as well as to the runtime system itself. Using this interface you are able to apply WinCC-projecting functionality and runtime functions to your scripts or to write autonomous applications with direct access to the WinCC system..
Starting with WinCC V7. Also numerous additional ActiveX-elements and a configuration toolset containing Visual Basic Templates is included for the simple creation of ActiveX-Controls. The development of individual controls supports the creation of industry- and technological functions as protected and standardized modules.
This reusable controls shorten your time-to-market and protect your know-how. NET Framework 3.
