show the entry list

WinCC flexible Options -- Product information -- WinCC flexible /OPC-Server 
What options are there in WinCC flexible for using a Multi Panel or Mobile Panel as an OPC server? 
What should you watch out with regard to licenses for WinCC flexible and panels? 
What alternatives are there to the SOAP web service in Microsoft Windows Vista? 
Which settings are required in Windows XP SP2 and WinCC flexible for server-client communication via OPC-DCOM? 
Which settings are required in Windows 2000, Windows XP, Windows Vista and WinCC flexible for server-client communication via OPC XML? 

What options are there in WinCC flexible for using a Multi Panel or Mobile Panel as an OPC server?Go to beginning
Part number:

Please follow the instructions and information in the PDF document.

22701694_WinCC_flexible_OPC_XML_V1_2_e.pdf ( 1176 KB )  

Contents
The following points are covered in the document.

1 Introduction
2 What are OPC and OPC XML?
3 OPC XML versions with a Multi Panel or Mobile Panel
   3.1 Version A - OPC DA client with OPC XML gateway via COM
   3.2 Version B - OPC DA client with OPC XML gateway via DCOM
   3.3 Version C - OPC XML DA client without OPC XML gateway
4 Requirements
   4.1 Hardware and software requirements
   4.2 OPC XML-compatible panels
5 Configuration of the different versions
   5.1 Configuration of the OPC XML DA server (Multi Panel / Mobile Panel)
   5.2 Configuration of the OPC XML gateway
   5.3 Configuration of an OPC DA client with ProTool/Pro
   5.4 Configuration of an OPC DA client with WinCC flexible
   5.5 Configuration of an OPC DA client with the Microsoft Excel macro
   5.6 Configuration of an OPC DA client with WinCC
   5.7 Configuration of an OPC XML DA client with WinCC
   5.8 Download

Sample projects

Attachment 1: OPC_XML_Project.zip ( 7257 KB )  

Attachment 2: OPC_Client_V1_2.zip ( 40 KB )

Additional Keywords
OPC Foundation, OPC = (Object Linking and Embedding for Process Control),
COM = (Component Object Model), DCOM = (Distributed Component Object Model)

 

What should you watch out with regard to licenses for WinCC flexible and panels?Go to beginning
Part number:

Introduction
This FAQ entry describes what to pay attention to with regard to licenses and authorizations for WinCC flexible. This entry covers licenses for panels, WinCC flexible ES and WinCC flexible RT.

Please follow the instructions in the PDF file (Attachment 1). The following points are covered in the document.

1 General Information about Licenses
   1.1 License, Certificate of License and License Key
   1.2 Why Do You Need Licenses?
   1.3 Available License Types
   1.4 Licenses for Options and Services of WinCC flexible ES/RT
2 How Do You Transfer Licenses?
   2.1 Which Software is Needed?
   2.2 How Do You Transfer License Keys?
   2.3 Transferring License Keys to an Operator Panel via Automation License Manager
   2.4 Removing License Keys from an Operator Panel via Automation License Manager
3 License Key Backup
   3.1 Which Software is Needed?
   3.2 When Do You Have to Back Up License Keys?
   3.3 Backup and Restore
4 Upgrading Licenses
   4.1 What Is a License Upgrade and What Types Are There?
   4.2 Requirements for an Upgrade
   4.3 Upgrading Using the Automation License Manager
5 Special Features of WinAC MP
   5.1 License Keys for WinAC Types
   5.2 License Keys for WinAC Versions.
   5.3 Other Special Features
   6 Frequently Asked Questions
   6.1 How Do You Repair a Defective License?
   6.2 Why is a License Invalid After Changing Time Zones?
   6.3 Why are License Keys Not Recognized?
   6.4 Where is the "Old" License Key Located after an Upgrade?
   6.5 How Do You Retrieve a Lost License Key?
   6.6 Why are Licenses from TP 177 Not in the Backup?
   6.7 Can You Use a License for WinCC flexible 2008 also for WinCC flexible 2007?
   6.8 Can You Change the Versions of WinCC flexible by Replacing Licenses?
         (This does not apply for Micro and China Edition)

Attachment 1: WinCC_flexible_Lizenzen_en.pdf ( 922 KB )

Attachment 2 lists the licenses required for the various options and services in WinCC flexible Runtime (RT) and WinCC flexible Engineering System (ES).

Attachment 2: License_Key_List_e_V1_1.pdf ( 15 KB )

Keywords
License repair, License destruction, License installation connection, License upgrade, ALM, Automation License Manager, License defective, License not recognized

What alternatives are there to the SOAP web service in Microsoft Windows Vista?Go to beginning
Part number:

Explanation:
WinCC flexible permits you to utilize the web service (SOAP). The web service (SOAP) is based on the Simple Object Access Protocol. This permits you to access the tags of an operator panel from an external application via Ethernet.

Note:
The Microsoft SOAP toolkit that is needed on the PC for accessing a SOAP service, is not supported by Microsoft Windows Vista.

Contents:
1. Alternative to SOAP
2. Requirements
3. Performance of OPC XML
4. Excel as OPC DA Client
5. Links

1. Alternative to SOAP
You can use OPC XML as an alternative to the web service (SOAP). For this, the operator panel has to function as the OPC XML DA server. You can do this in the device settings of the WinCC flexible project.


Bild 01 - OPC XML Verbindung

The application that accesses the OPC XML DA server must act as an OPC DA client or as an OPC XML DA client. The OPC XML gateway - see Fig. 01 - is required in addition if you use an OPC DA client. More information on implementation is available in Entry ID: 25677751.

Note:
OPC XML is also based on the web service (SOAP) and must be supported by the operator panel - see Requirements. For this reason, the Microsoft SOAP toolkit is not needed on the PC.
From a PC with Windows XP, the web service (SOAP) can continue to be used for communication with an operator panel as long as it is enabled in WinCC flexible ES.

2. Requirements

  • OPC XML Gateway1)
  • Microsoft .Net Framework1)
  • Windows 20002), Windows XP or Windows Vista3)
  • Multi Panel as from the 270 series or Mobile Panel as from the 270 series
  • License Key "WinCC flexible / OPC Server for MPs"

Key:
1) On the WinCC flexible Installation CD.
2) Only with WinCC flexible 2004 / 2005 / 2007
3) As from WinCC flexible 2008

Note:
The option OPC via XML is not supported by all operator panels that also support the web service (SOAP).

3. Performance of OPC XML
OPC XML connections are designed for the exchange of small volumes of data. The performance of OPC XML DA is significantly below that of OPC DA and thus only very few tags per picture should be requested. 

  • Configure the cycle time of the tags to be not less than 1 second.
  • Only about 30 tags per picture should be requested.
  • Tags of the "String" type only support valid ASCII values from 20 hex to 7F hex .

4. Excel as OPC DA client
Access to the OPC XML DA server is also possible via a macro (OPC DA client) in Excel. The OPC XML gateway is required in addition for accessing an OPC XML DA server from an OPC DA client. You can find the function manual in Entry ID: 22701694 where you can download it free of charge.

More information is also available from the document entitled "Getting Started Options".

5. Links
 
  Entry ID
Configuring an OPC XML connection 25677751
WinCC flexible Getting Started Options
Chapter 5 - OPC (Edition: 04/2006)
18657078

Keywords:
XML = Extensible Markup Language, OPC Foundation, OPC = Object Linking and Embedding for Process Control

Which settings are required in Windows XP SP2 and WinCC flexible for server-client communication via OPC-DCOM?Go to beginning
Part number:

Introduction
OPC (OLE for Process Control) is an original standardized and manufacturer-independent software interface. Because of the further development of the OPC standard, the designation OPC is now used for an interface family. OPC Data Access (OPC DA) is based on the Windows technology COM (Component Object Model) and DCOM (Distributed Component Object Model).

DCOM is COM with the additional capability of accessing objects across computer boundaries. This technology makes it possible to connect various components of different manufactures with each other via a standardized interface.

An OPC configuration consists of at least one OPC server and one OPC client. The OPC server can forward data at an OPC client and vice versa. Although OPC is not tied to a standard protocol, the TCP/IC protocol is preferred.


Fig. 01

Fig. 01 shows the basic configuration of an OPC client and an OPC server.

Note
In WinCC flexible, only PCs and Panel PCs can exchange data via DCOM. Communication between a Multi Panel and one or several PCs is possible with OPC XML DA.

Link
Configuring an OPC XML DA connection
Entry ID: 25677751

Remark
The following example uses a WinCC flexible OPC server and a WinCC flexible OPC client. Since OPC via DCOM is an open interface, both the WinCC flexible OPC server and the WinCC flexible OPC client can communicate with other OPC components.

Contents

  1. Configuring the DCOM interface in Windows XP, settings of the OPC server in DCOM and firewall settings
  2. Configuring the WinCC flexible OPC server
  3. Configuring the WinCC flexible OPC client
  4. Downloading the WinCC flexible sample projects

1. Configuring the DCOM interface in Windows XP, settings of the OPC server in DCOM and firewall settings
Take the settings required from the PDF document below. This document is also available as a readme on the WinCC flexible DVD. It is located in the folder entitled "<DVD drive>:\CD3\Support\OPC\".

Attachment 1: OPC_via_DCOM_e.pdf ( 908 KB )

Note:
You can also use the DCOM interface settings in Windows Vista and Windows 7.

2. Configuring the WinCC flexible OPC server
This example explains the configuration of a WinCC flexible project as OPC server.
 
No. Procedure
1 Create a new project
  • Start WinCC flexible and then click on "Project > New" in the program menu.
  • Select "PC > WinCC flexible Runtime".
2 Configure a connection
  • Click on "Project > Device_1... > Communication > Connections".
  • Insert a new connection via the program menu "Insert > New object - Connections".

    Note
    In this example we use the communication driver "SIMATIC S7 300/400". You can configure any other connection that is available in WinCC flexible.

    Note
    If WinCC flexible is working as the OPC server, this OPC connection is not configured explicitly in the "Connections" tab. The configuration takes place in the "Device settings" - see Point 4.
     
  • If necessary, change the slot of the SIMATIC S7 controller to "2" when using the communication driver "SIMATIC S7 300/400".
3 Create tags
  • Create three "Variable_x" tags of the "Int" type and connect them with the connection "Connection_1".
  • Use the memory areas "MW 10", "MW 12" and "MW 14" for the three external tags.
  • Create an additional internal tag of the "Int" type called "Variable_4".
4 Configure WinCC flexible as the OPC server
  • Switch to the "Device Settings" tab.
  • Enable the option "Act as OPC server".

    Note
    If WinCC flexible acts as OPC server, all the internal and external tags that have been created in WinCC flexible are available to the OPC server.
5 Creating I/O and text fields
  • Add six text fields with the following designations:
    - OPC DA Server
    - Variable_1
    - Variable_2
    - Variable_3
    - Variable_4
    - internal tag
  • Add another four I/O fields and arrange all the text and I/O fields as shown in the figure.


Fig. 02

6 Connect tags
  • Link all four tags to the I/O fields.
7 Start WinCC flexible RT
  • Transfer at least the OB1 to the controller and set the controller in the "Run" mode.

    Note
    You can also use PLCSIM to test it as an alternative to the S7 controller.
     
  • Make sure that the PG/PC interface is set to "MPI" if it has been configured.
  • Start the WinCC flexible Runtime.

3. Configuring WinCC flexible OPC clients
The Runtime of the WinCC flexible OPC server must be started in order to configure the connection of the OPC client tags to the WinCC flexible OPC server.
 
No. Procedure
1 Create a new project
  • Start WinCC flexible and then click on "Project > New" in the program menu.
  • Select "PC > WinCC flexible Runtime".
2 Create a connection
  • Add a new connection in the same way as for the WinCC flexible OPC server project.
  • Choose "OPC" as communication driver.
  • Select the OPC server "OPC.SimaticHMI.HmiRTm" from WinCC flexible on the computer where the OPC server is available.

    Note
    If no OPC server is displayed on the relevant computer, then the network communication is disrupted and the access is denied in Windows.

    Remedy

    Network communication:

    • Verify all Ethernet components (hub, switch, router, patch cable etc.).
    • Check all network settings (IP addresses, subnet mask, ping etc.).

    Checking access:

    • Open the Windows Explorer and click on "Network environment".
    • Then click on "Entire Network > Microsoft Windows Network".
    • Double-click on the computer where the OPC server or client is available.
    • Log on with the relevant user name and password.

      Note
      If no logon dialog appears, deactivate the guest account in the user Windows user administration.
       
    • Do the same on all the relevant computers.


Fig. 03

3 Define tags
  • Create four tags of the "Short" type with the connection "Connection_1".
  • Open the OPC browser by clicking on the corresponding "Symbol" field for each tag.
  • Connect each tag to the relevant item.

    Note
    If you can access the computer where the OPC server is available via Windows Explorer, then check the DCOM settings.


Fig. 04

4 Create I/O and text fields
  • Add five text fields with the following designations:
    - OPC DA Client
    - Variable_1
    - Variable_2
    - Variable_3
    - Variable_4
  • Add another four I/O fields and arrange all the text and I/O fields as shown in Fig. 25.
  • Link all the relevant tags to the I/O fields.
5 WinCC flexible Runtime
  • Start the WinCC flexible Runtime.

4. Download the WinCC flexible sample projects
The download in Attachment 2 contains the project described above in which WinCC flexible acts as OPC server.

Attachment 2: WinCC_flexible_OPC_DA_Server.zip ( 1875 KB )

Attachment 3 contains the WinCC flexible project that has been configured as OPC client.

Attachment 3: WinCC_flexible_OPC_DA_Client.zip ( 1924 KB )

Keywords
OPC Foundation, Object Linking and Embedding for Process Control

Which settings are required in Windows 2000, Windows XP, Windows Vista and WinCC flexible for server-client communication via OPC XML?Go to beginning
Part number:

Introduction:
Multi Panels and Mobile Panels as from the 270 series can also act optionally as OPC XML DA servers. Communication via DCOM with the OPC XML DA server of the Multi Panel or Mobile Panel is not possible, because the realtime operating system Windows CE has no DCOM interface. Therefore, an OPC XML gateway is always required for communication between a PC (OPC DA client) and a multi panel or mobile panel (OPC XML DA server). The OPC XML gateway implements communication from XML to COM or DCOM.

Contents:

  1. What is OPC?
  2. Function description of the OPC XML gateway
  3. Performance of OPC XML DA
  4. Overview of necessary settings
    4.1 Settings of the OPC DA server and OPC DA client in DCOM
    4.2 Installation and settings on the OPC XML gateway and manager
    4.3 Firewall settings
    4.4 Configuration of the WinCC flexible OPC XML DA server
    4.5 Configuration of the WinCC flexible OPC DA client
  5. Download

1. What is OPC?
OPC (OLE for Process Control) originally designated a standardized and manufacturer-independent software interface. With the further development of the OPC standard, the designation OPC is currently used for an interface family that enables the compatibility of different automation systems. OPC Data Access (OPC DA) is based on the Windows technology COM (Component Object Model) and DCOM (Distributed Component Object Model).

DCOM is COM with the additional capability of accessing objects across computer boundaries. This technology makes it possible to connect various components of different manufacturers with each other via a standardized interface.

Communication via DCOM is usually limited to local networks, because Port 135 is used for this and must not be occupied. Most providers lock this port for security reasons. However, this can be implemented via a VPN tunnel. The data exchange via XML enables the communication with the platform-independent protocol SOAP (Simple Object Access Protocol) via the Internet or the intranet. Communication via XML is done via the standard Port 80 for HTTP.

An OPC XML DA configuration consists of at least one OPC XML DA server and one OPC DA client. The OPC XML DA server is a web service and can forward and receive data to/from an OPC client. The OPC DA client accesses the OPC XML server via the OPC XML gateway that handles the communication between OPC and XML.


Fig. 01

Figure 01 shows the basic configuration of an OPC DA client and an OPC XML DA server.
 
HMI device Data communication Operating system OPC server OPC client
PC, Panel PC DCOM Windows 2000
Windows XP
Windows XP embedded1)
Windows Vista
OPC DA server OPC DA client
MP270B, MP277, MP370, MP377,
Mobile Panel 277
XML Windows CE OPC XML server -
1)

Only on platforms released for it (e.g. Panel PC 477)

Table 01 - OPC configuration

2. Function description of the OPC XML gateway
The OPC XML gateway is required if the application - such as WinCC flexible - has no direct OPC XML DA interface. The OPC XML gateway is not required if you use an OPC XML DA client.

A web service is started on the multi panel or mobile panel when you start up the WinCC flexible Runtime, which is also designated as OPC XML DA server. The communication on XML basis takes place between the OPC XML DA client that is implemented in the OPC XML gateway and the OPC XML DA server - see Fig.02 ( 26 KB ) . The OPC XML DA client is a wrapper that makes the data available to the higher-level OPC DA server. If the OPC DA client is on the same computer (PC 1), then the data communication takes place via the COM interface.


Fig. 02 - OPC-XML-Gateway

If the access on the OPC DA server (OPC.Siemens.XML) takes place from a separate computer (PC 2) then settings must be made in the DCOM interface. You can avoid these DCOM settings if an OPC XML gateway is installed on every computer and appropriately configured - see Fig. 03.


Fig. 03

Remark:
The following example uses an MP 277 as WinCC flexible OPC XML DA server and one WinCC flexible OPC DA client. Since OPC DA and OPC XML are open interfaces, both the WinCC flexible OPC XML DA server and the WinCC flexible OPC DA client can communicate with other components. Requirement for implementing the OPC XML solution is the OPC XML gateway.

3. Performance of OPC XML DA
OPC XML connections are designed for the exchange of small volumes of data. The performance of OPC XML DA is significantly below that of OPC DA and thus only very few tags per picture should be requested. 

  • Configure the cycle time of the tags to be not less than 1 second.
  • Only about 30 tags per picture should be requested.
  • Tags of the "String" type only support valid ASCII values from 20 hex to 7F hex.

4. Overview of necessary settings
The following settings are to be made.

        4.1 Settings of the OPC DA server and OPC DA client in DCOM
        4.2 Installation and settings on the OPC XML gateway and manager
        4.3 Firewall settings
        4.4 Configuration of the WinCC flexible OPC XML DA server
        4.5 Configuration of the WinCC flexible OPC DA client

4.1. Settings of the OPC DA server and the OPC DA client in DCOM
You carry out the settings in DCOM only if the OPC XML gateway is used on another computer - see Fig. 02 ( 26 KB ) .

The "OPC.Siemens.XML" is used as OPC DA server. This OPC DA server must be configured on the PC on which the OPC XML gateway is installed. The start and access releases in DCOM have to be carried out on both PCs. More information on DCOM configuration is available in Entry ID: 31198863.

4.2 Installation and settings on the OPC XML gateway and manager
The OPC XML gateway must only be installed if an OPC DA client and not an OPC XML DA client is used.

Installation notes:
The OPC XML manager is only released for the operating systems that are also valid for the relevant WinCC flexible versions.

More information is available in Entry ID: 22055368.

Use only the version of the OPC XML gateway that is supplied with the relevant WinCC flexible version, with which you have configured the OPC XML server.
 
No. Procedure
1 Install the OPC XML manager

WinCC flexible 2004:

  • Copy the program "OPCXmlManager.exe" from the installation CD from the directory "\Disk2\Support\OPCXML" into a directory of your choice on the relevant PC.

As of WinCC flexible 2005:

  • The setup for installing the "OPC XML gateway" is on the WinCC flexible CD2 under "WinCCflexible\setup\OPCXMLWrapper\Disk1". Double-click on the "Setup.exe" file.
  • Under "Language", select the interface language of the Setup program.
  • Select "Installation" to start the installation.
  • Run the installation following the instructions on the monitor.
2 Opening the OPC XML manager

WinCC flexible 2004:

  • Open the "OPC XML Manager" in your chosen directory by double-clicking on "OPCXmlManager.exe".
  • In the OPC XML Manager click on the "Add..." button.

WinCC flexible 2005:

  • In the "Start" menu, select the program "SIMATIC > WinCC flexible > WinCC flexible Runtime > XmlMuxConfig".
  • In the OPC XML Manager click on the "Add..." button.

As of WinCC flexible 2007:

  • In the "Start" menu, select the program "SIMATIC > OPC-XML Gateway > OPC XML Manager".
  • In the OPC XML Manager click on the "Add..." button.


Fig. 04

3 Add the prefix and host name

WinCC flexible 2004:

  • Enter the host name or the IP address (such as 150.150.150.20).
  • Confirm the input with the "OK" button.
  • Close the OPC XML manager.
  • Open "OpcXml Settings" in the "Control Panel".
  • Enter the computer name or the IP address of the operator panel.
  • Close "OpcXml-Settings" with "OK".

As of WinCC flexible 2005:

  • Enter the prefix (for example, "Prefix") and host name or IP address (for example, 150.150.150.20).

    Explanation Parameters:

    [Prefix]
    The prefix specifies the OPC XML DA server where the tag is assigned.

    [Host Name]
    Device name or IP address of the OPC XML DA server.
     
  • Confirm the input with the "OK" button.
  • Close the OPC XML manager.


Fig. 05

4.3 Firewall settings
The ports given in Entry ID 24534065 must be enabled for OPC XML communication.

4.4 Configuration of the OPC XML DA server
In this example we explain how to configure a WinCC flexible project as OPC XML DA server.

Note:
Only operator panels listed in Table 01 can be used as OPC XML DA servers.
 
No. Procedure
1 Create a new project
  • Start WinCC flexible and then click on "Project > New" in the program menu.
  • Select, for example, "Multi Panels > 270 > MP 277 10" Touch".

    Note:
    Only Multi Panels can be used as OPC XML DA servers.

Fig. 06
2 Configure a connection
  • Click on "Project > Device_1... > Communication > Connections".
  • Insert a new connection via the program menu "Insert > New object - Connections".

    Note:
    In this example you use the communication driver "SIMATIC S7 300/400". You can configure any other connection that is available in WinCC flexible.

    Remark:
    If WinCC flexible is working as the OPC server, this connection is not configured explicitly in the "Connections" tab. The configuration takes place in the "Device settings" - see Point 4.
     
  • If necessary, change the slot of the SIMATIC S7 controller to "2" when using the communication driver "SIMATIC S7 300/400".


Fig. 07

3 Create tags
  • Create three "Variable_x" tags of the "Int" type and connect them with the connection "Connection_1".
  • Use the memory areas "MW 10", "MW 12", and "MW 14" for the three external tags.
  • Create an additional internal tag of the "Int" type called "Variable_4".


Fig. 08

4 Configure WinCC flexible as the OPC server
  • Switch to the "Device Settings" tab.
  • Enable the option "Act as OPC server".

    Note:
    If WinCC flexible acts as OPC server, all the internal and external tags that have been created in WinCC flexible are available to the OPC server.


Fig. 09

5 Creating I/O and text fields
  • Add six text fields with the following designations:
    - "OPC XML Server"
    - "Variable_1"
    - "Variable_2"
    - "Variable_3"
    - "Variable_4"
    - "internal tag"
  • Add another four I/O fields and arrange all the text and I/O fields as shown in Fig.10.


Fig. 10

6 Start WinCC flexible RT
  • Transfer the hardware configuration and at least OB1 to the controller. Then switch the S7 controller to RUN mode.
  • Make sure that the PG/PC interface is set to "MPI" if it has been configured.
  • Transfer the WinCC flexible project to the Multi Panel and start Runtime.


Fig. 11

4.5 Configuration of the WinCC flexible OPC DA client
Runtime of the WinCC flexible OPC server must be started in order to configure connection of the OPC DA client tags to the WinCC flexible OPC server.
 
No. Procedure
1 Create a new project
  • Start WinCC flexible and then click on "Project > New" in the program menu (see Fig. 06 ( 8 KB ) ).
  • Select "PC > WinCC flexible Runtime".
2 Create a connection

WinCC flexible 2004:

  • Add a new connection in the same way as for the WinCC flexible OPC server project.
  • Select "OPC" as communication driver and then the OPC server that is specified in the "OPCxml - Manager" under the category "ProgID" (such as "1_OPC.Siemens.XML").

As of WinCC flexible 2005:

  • Add a new connection in the same way as for the WinCC flexible OPC server project.
  • Select "OPC" as a communication driver and then the WinCC flexible OPC server "OPC.Siemens.XML".
  • Specify the name of the computer on which the WinCC flexible OPC server or the OPC XML gateway is available.


Fig. 12

3 Define tags
  • Create four tags of the "Short" type with the connection "Connection_1".

    Note:
    The data type set for the OPC XML DA server must be identical to that of the OPC DA client. When you browse - see Fig.013 - the data type of the OPC server is automatically transferred.
     
  • Open the OPC browser by clicking on the corresponding "Symbol" field for each tag.
  • Connect each tag to the relevant item.

    Note (as of WinCC flexible 2005):
    You do not need the symbolic connection if you enter the following syntax as address:

    Example:
    [Prefix]
    :Win CC Flexible RT <@>[tag name] 

    Explanation Parameter:

    [Prefix]
    The prefix specifies the OPC XML DA server where the tag is assigned.

    [Tag name]
    Device name or IP address of the OPC XML DA server


Fig. 13

Note:
Note the following for OPC XML DA connections:

  • Configure the cycle time of the tags to be not less than 1 second. OPC XML connections are designed for the exchange of small volumes of data and thus only a few tags should be requested - approx. 30 per picture.
  • With the tag name and with tags of the "String" type, only valid ASCII values from 0x20(hex) to 0x7F(hex) are supported.
4 Create I/O and text fields
  • Add five text fields with the following designations:
    - "OPC DA Client"
    - "Variable_1"
    - "Variable_2"
    - "Variable_3"
    - "Variable_4"
  • Add another four I/O fields and arrange all the text and I/O fields as shown in Fig.14.
  • Link all the relevant tags to the I/O fields.


Fig. 14

5 WinCC flexible Runtime
  • Start WinCC flexible Runtime.


Fig. 15

5. Download the WinCC flexible sample projects:
The download in Attachment 1 contains the project described above in which WinCC flexible acts as OPC server.

Attachment 1: WinCC_flexible_OPC_XML_Server.zip ( 1664 KB )

Attachment 2 contains the WinCC flexible project that has been configured as OPC client.

Attachment 2: WinCC_flexible_OPC_XML_Client.zip ( 1659 KB )

Runnability and test environment:
The following table lists the components that have been used to create this entry and verify the functions described.
 
Components Product and version designation
PC operating system Microsoft Windows XP SP2
Standard tools OPC XML Manager V1.0
Engineering tool STEP 7 V5.4 SP1
HMI software WinCC flexible 2005 SP1 HF7
HMI system MP 277 10"

Keywords:
OPC Foundation, Object Linking and Embedding for Process Control

 Entry ID:28958971   Date:2012-04-02 
I regard this article....as helpfulas not helpful                                 






























related links
Automation Licence Manager
How do you install, uninstall and ...
SIMATIC Industrial software SIMAT ...
SIMATIC Industrial software SIMAT ...
STEP 7 Professional V11.0 SP1
mySupport
My Documentation Manager 
Newsletter 
CAx-Download-Manager 
Support Request
To this entry
Print
Create PDF 
Send to a friend
QuickLinks
Compatibility tool 
Help
Online Help
Guided Tour