Readme file for the "SIMATIC NET, PC Software V8.0 + SP1" CD with important information on the products

 

 

The following table lists your SIMATIC NET PC product with the corresponding software components (setup modules):

 

Install the components shown on the right for your SIMATIC NET product listed below

SIMATIC NET, PC Software, V8.0

SIMATIC NCM PC V5.4 + SP5 (service pack 5) + HF5 (hotfix 5)

Industrial Ethernet

 

 

S7-1613

Yes

Yes

S7-REDCONNECT

Yes

 

Power Pack S7-REDCONNECT

Yes

 

SOFTNET-S7

Yes

Yes

SOFTNET-S7 Lean

Yes

Yes

SOFTNET-PG

Yes

 

 

 

 

SNMP OPC Server

 

 

SNMP OPC Server Basic

Yes

Yes

SNMP OPC Server Extended

Yes

Yes

SNMP OPC Server Power Pack

Yes

Yes

 

 

 

PROFINET

 

 

SOFTNET PN IO

Yes

Yes

 

 

 

PROFIBUS

 

 

S7-5613

Yes

Yes

DP-5613

Yes

Yes

SOFTNET-S7

Yes

Yes

SOFTNET-DP

Yes

Yes

SOFTNET-DP Slave

Yes

Yes

CP 5613 (DP-Base Programming Interface)

Yes

Yes

 

 

C79000-S8976-C016-13-1, © Siemens AG 2002 to 2010

This file contains important information on the products of the
"SIMATIC NET, PC Software V8.0 + SP1" CD. Instead of the suffix with the year "Edition 2010" used with the previous SIMATIC NET CD versions, the version number, in this case V8.0 is now used.

 

The "SIMATIC NET, PC Software V8.0 +SP1" CD has been released for operation with Windows 7 (Professional, Enterprise, Ultimate), 32-bit.

 

Before installing the SIMATIC NET CD, please read the installation instructions installation_en.pdf on the SIMATIC NET CD in the \doc subfolder. To be able to do this, first install Acrobat Reader that you will find in the \sw\acroread folder.

 

The following sections deal with the SIMATIC NET PC products (Sections 1 to 22), and these are followed by general topics.

 

Please read the section relevant to your product carefully. If there are other sections that are important for a product, this will be pointed out in the product sections themselves.

 

The SIMATIC NET products are available on different data media:

-          SIMATIC NET PC Software

-          SIMATIC NCM PC

Link for German: http://support.automation.siemens.com/WW/view/de/12660737

Link for English: http://support.automation.siemens.com/WW/view/en/12660737

 

All authorizations (licenses) that you have for previous products (Edition 2008 or older) must be replaced. To do this, use our upgrade products with upgrade license keys.

 

You will find further SIMATIC NET documents on the accompanying CD "SIMATIC NET, Manual Collection".
You will also find SIMATIC NET documents on the Internet:
http://support.automation.siemens.com/ -> section Self-help, enter the product name; Reaction: In the search area Manuals/BA you will see a list of documents.

 

 

 

Contents

 

1.       Communications processor CP 5613 FO, CP 5613 A2, CP 5614 A2, CP 5603, CP 5623, CP 5624

2.       DP-5613

3.       S7-5613

4.       FMS-5613

5.       The CP 5512 communications processor

6.       The communications processor CP 5611 A2/CP 5621

7.       The CP 5711 communications processor

8.       SOFTNET-S7 (for PROFIBUS)

9.       SOFTNET-DP (for PROFIBUS)

10.      SOFTNET DP slave (for PROFIBUS)

11.      CP 1613 A2 communications processor

12.      CP 1623 communications processor

13.      S7-1613

14.      TF-1613

15.      S7-REDCONNECT and S7-REDCONNECT upgrade

16.      The CP 1612 and CP 1612 A2 communications processor

17.      SOFTNET PN IO

18.      SOFTNET-S7 for Industrial Ethernet

19.      SOFTNET-S7 Lean for Industrial Ethernet

20.      SOFTNET-PG for Industrial Ethernet

21.      PN OPC Server

22.      SNMP OPC Server

23.      General requirements, notes, and restrictions

24.      Information, restrictions and notes relating to OPC

25.      Notes on license keys

26.      Requirements and restrictions relating to hardware in general

27.      Compatibility

28.      Notes on C programming interfaces

29.      Notes on project engineering, configuration and NCM

30.      Development environments and compilers supported

31.      Routing

32.      Operating systems 32 bit

33.      Trace

 

 

 

1.    Communications processor CP 5613 FO, CP 5613 A2, CP 5614 A2, CP 5603, CP 5623, CP 5624

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

Where the CP 5613 is referred to below, this relates to the communications processors CP 5613 FO, CP 5603, CP 5623, CP 5614 FO, CP 5613 A2, CP 5614 A2, CP 5624 unless specific types are named explicitly. CP 5613 (without A2) is no longer supported.

 

Where the CP 5614 is referred to below, this relates to the communications processor types CP 5614 FO, CP 5614 A2, CP 5624; unless specific types are named explicitly. CP 5614 (without A2) and CP 5614 FO is no longer supported.

 

 

1.1        Version history

 

Version

Changes/additionally supported functions

V8.0

·             Windows 7, 32 Bit is supported

 

 

1.2        GSD file handling for the slave submodule CP 5614/CP 5613 A2/CP 5623 and CP 5603

 

For information on using the device master file (GSD), refer to the FAQ under entry ID 21687843 on the pages of SIEMENS Customer Support http://support.automation.siemens.com/WW/view/en/21687843.

 

 

1.3        Restrictions

 

Restriction for constant bus cycle time for CP 5623 and CP 5624

The DP_cycle_time function is not supported by the SIMATIC NET CD V8.0.

 

Interface parameter setting "Auto"

Operation of the CP 5613 with the "Auto" interface parameter setting has not been released.

  

Do not uninstall/deactivate the CP

Configured CPs must not be uninstalled/deactivated.

If you use the WinAC software product, the CPs must never be deactivated.

 

Hot plugging

The communications processors CP 5613 and CP 5614 are not released for hot plugging.

 

Do not modify user-specific parameter assignment data in the GSD file

User-specific parameter assignment data in the GSD file should not be modified when operating along with to FDL.

 

Rack PC 840 V2 with CP 5613 A2/CP 5614 A2 with product versions 1 and 2

The communications processors CP 5613 A2/CP 5614 A2 with product versions 1 and 2 may be operated in the rack PC 840 V2 only in the PCI slots 5, 6 and 8.
This restriction no longer applies as of product version 3.

 

Expanded addressing with DPC2

Subnet addressing is not supported in DPC2.

 

Receiving bus parameters

Receiving bus parameters is supported only by the "Set PG/PC Interface" program.

 

Hyperthreading

Operation with hyperthreading activated is released only for the CP 5603, CP 5613 A2, CP 5614 A2, CP 5623 and CP 5624.

To work with the other CP 5613/CP 5614 module types, turn hyperthreading off in the BIOS.

For operation with CP 5613 FO, you should also turn off the multi-core and multi-CPU function.

 

 

1.4        Notes on project engineering and configuration

 

Configuring the CP 5614 A2/CP 5624 as a slave

The CP 5614 A2/CP 5624 are configured as slaves using GSD files. If necessary, you can orient yourself on two sample files for the CP 5614 A2/CP 5624, that are copied to "<Installation folder>\SIMATIC.NET\DP\DEMO_GSD" when you install software. You can import these files in SIMATIC STEP 7/NCM PC and change their configuration accordingly. If you require the Ident number of the slave, you can take this from the relevant GSD file. Refer to Section 1.2 for related information.

 

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

Link German: http://support.automation.siemens.com/WW/view/de/15227599

Link English: http://support.automation.siemens.com/WW/view/en/15227599

In this document, the information on FMS is not valid.

 

Bus parameters

When using PG operation, please note that if the bus parameters are incorrectly set, you must reset and restart with the "Set PG/PC Interface" program or Configuration Console after correcting the bus parameters.

 

 

1.5        Notes on the "Programming Interface DP-Base for CP 5613/CP 5614" manual

 

Access point for the Transfer sample program for CP 5614

The Transfer sample program for the CP 5614 always uses access point "CP_L2_1:"

 

 

 

2.    DP-5613

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

Where the CP 5613 is referred to below, this relates to the communications processors CP 5603, CP 5613 A2, CP 5613 FO, CP 5623, CP 5614 A2, CP 5624; unless specific types are named explicitly.

 

 

2.1        Version history

 

Version

Changes/additionally supported functions

V8.0

·             Windows 7, 32 Bit is supported

 

 

2.2        Restrictions

 

Communication partners

The DP master of the CP 5613 can be operated with certified DP slaves. With non-certified partners such as S7 slaves, the full range of functions is not guaranteed in all cases.

The DP slave of the CP 5614 A2 can be operated with certified DP master stations.

 

The "DP_get_pointer( )" function call returns timeout during simultaneous operation with the DP OPC server

The DP OPC server uses the powerful DP‑Base interface for communication.
It can therefore not be used at the same time by a C user program. One effect of the double usage is that the "DP_get_pointer( )" function call returns a timeout when used simultaneously with the DP OPC server.

 

DPC2 transport calls are not supported

DPC2 transport calls are not supported by the CP 5613.

 

Further restrictions

For information on the following topics, refer to Section 1.3, "Restrictions":

·         Interface parameter setting "Auto"

·         Installation of the SIMATIC NET CD

·         Hot plugging

·         Rack-PC 840 V2 with CP 5613 A2/CP 5614 A2

·         Receiving bus parameters

·         Hyperthreading

 

Restrictions to the CP 5613 as DP slave

A CP 5603 / CP 5613 A2 / CP 5623  communications processor as DP slave can only communicate with one (1) DP master using the DPC2 protocol (1) DP master. DPC2 data record jobs from other class 2 masters are rejected with a communications error. Reading I/O data and slave diagnostics are possible without any restrictions.

 

 

2.3         Notes on project engineering and configuration

 

Further information

For more detailed information, refer to Section 1.4, "Notes on project engineering and configuration":

 

 

 

3.    S7-5613

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

Where the CP 5613 is referred to below, this relates to the communications processors CP 5613 FO, CP 5613 A2, CP 5614 A2 unless specific types are named explicitly.

 

3.1        Version history

 

Version

Changes/additionally supported functions

V8.0

·        Windows 7, 32 Bit is supported

 

 

3.2        Restrictions

 

S7 programming interface: return values of the "s7_receive" function

When evaluating the return values of the "s7_receive" function, if unexpected values occur, the "s7_discard_msg" function must be called in the default branch of the corresponding switch instruction.

 

Further information

For information on the following topics, refer to Section 1.3, "Restrictions":

·         Interface parameter setting "Auto"

·         Installation of the SIMATIC NET CD

·         Hot plugging

·         Receiving bus parameters

·         Hyperthreading

 

 

3.3        Notes on project engineering and configuration

 

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

·       Link German: http://support.automation.siemens.com/WW/view/de/15227599

·       Link English: http://support.automation.siemens.com/WW/view/en/15227599

 

CP 5613 as MPI interface

If you use a CP 5613 as MPI interface, make sure that the PROFIBUS profile is enabled automatically if no further access point is mapped on the MPI profile. This occurs, for example, when S7ONLINE was the only access point for the CP 5613, is mapped from "CP5613_5614(MPI)" to "PC internal (local)" and you want to continue using the CP 5613 as MPI interface.

 

Information on configuration

If connection establishment of a fully configured connection is started by a station that has a different station address from the configured station, the connection between the two partners will be established despite the difference.

 

Further information

For more detailed information, refer to Section 1.4, „Notes on project engineering and configuration“:

 

 

 

4.    FMS-5613

 The FMS communications protocol is no longer supported by this SIMATIC NET software.

 

 

 

5.    The CP 5512 communications processor

 

Configured mode

The CP 5512 is not released for configured mode!

 

Please read the Installation Instructions/product information supplied in paper form with the CP 5512.

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

 

 

6.    The communications processor CP 5611 A2/CP 5621

 

Restricted release

When using the communications processors CP 5611 A2 and CP 5621 in multi core or multiprocessor systems, operation in PROFIBUS networks up to a maximum of 1.5 Mbps is released. If higher baud rates are used, problems will be encountered on the bus during operation.

 

 

Please read the Installation Instructions supplied in paper form with the CP 5611 A2/CP 5621.

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

 

6.1        Restrictions

  

Expanded addressing with DPC2

Subnet addressing is not supported in DPC2.

 

 

6.2        Notes on project engineering and configuration

 

Properties page in the Station configuration Editor

In the properties page of the Station configuration Editor, only fixed PROFIBUS bus profiles can be created for node initialization.

User-specific bus parameters for large network spans and networks such as redundant OLM rings can be specified with the "SIMATIC STEP 7/NCM PC" software tool.

 

The CP 5611 A2 is no longer detected

If a CP 5611 A2 communications processor is no longer detected by the SIMATIC environment after inserting it in a different PCI slot, all the CPs of the type CP 5611 A2 will have to be uninstalled in the "Device Manager" under SIMATIC NET.

Afterwards start the "Find New Hardware" in the Device Manager and follow the instructions of the operating system.

 

 

7.    The CP 5711 communications processor

 

Please read the Installation Instructions/product information supplied in paper form with the CP 5711.

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

 

7.1        Restrictions

 

Number of supported CP 5711 modules:
One CP 5711 per PC is supported.

Expanded addressing with DPC2

Subnet addressing is not supported in DPC2.

 

Properties page in the Station configuration Editor

In the properties page of the Station configuration Editor, only fixed PROFIBUS bus profiles can be created for node initialization.

User-specific bus parameters for large network spans and networks such as redundant OLM rings can be specified with the "SIMATIC STEP 7/NCM PC" tool.

 

Restrictions configuring S7 connections

All communications modules of a PC must always be connected to a network in the STEP 7 project, otherwise even the S7 connections of a connected communications module do not work.

 

S7 programming interface: return values of the "s7_receive" function

When evaluating the return values of the "s7_receive" function, if unexpected values occur, the "s7_discard_msg" function must be called in the default branch of the corresponding switch instruction.

 

Error: Remote downloading of a configuration via a CP 5711 with SIMATIC STEP 7 / NCM PC is not possible.

 

Cause:

The CP 5711 was removed in configured mode and then reinserted (not permitted!)

 

Remedy:

a) Delete and then add the CP 5711 again in the Station Configuration Editor

b) Reconfigure the PC station

 

The CP 5711 is no longer visible in the PG/PC panel

If the CP 5711 is configured and the computer changes to the sleep state with the PG/PC panel open, the module is no longer visible in the PG/PC panel after exiting sleep state. This will only be recognized when the PG/PC panel is closed and reopened.

 

Remedy, To make the module visible again in the PG/PC panel:
Restart the computer or remove and reinsert the USB cable of the module.

 

 

 

8.    SOFTNET-S7 (for PROFIBUS)

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

 

8.1        Version history

 

Version

Changes/additionally supported functions

V8.0

·        Windows 7, 32 Bit is supported

 

 

8.2        Restrictions

 

No parallel operation

Operating several SOFTNET CPs in one computer is not supported unless the second CP is used solely for configuration purposes with STEP 7.

The parallel operation of several protocols via SOFTNET CPs is not supported.

 

Properties page in the Station configuration Editor

In the properties page of the Station configuration Editor, only fixed PROFIBUS bus profiles can be created for node initialization.

User-specific bus parameters for large network spans and networks such as redundant OLM rings can be specified with the "SIMATIC STEP 7/NCM PC " tool.

  

Communications processors CP 5411, CP 5511 and CP 5611

The communications processors CP 5411, CP 5511 and CP 5611 (all without the A2 suffix) are no longer supported by the SIMATIC NET software.

 

Restrictions configuring S7 connections

All communications modules of a PC must always be connected to a network in the STEP 7 project, otherwise even the S7 connections of a connected communications module do not work.

 

S7 programming interface: return values of the "s7_receive" function

When evaluating the return values of the "s7_receive" function, if unexpected values occur, the "s7_discard_msg" function must be called in the default branch of the corresponding switch instruction.

 

 

8.3        Notes on project engineering and configuration

 

Module cannot be started in the Station Configuration Editor

If there is a disruption on PROFIBUS (for example a bus short-circuit or duplicate node address), it is not possible to start the SOFTNET PROFIBUS module. In this case, eliminate the disruption before you try to start the module again.

 

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

·          Link German: http://support.automation.siemens.com/WW/view/de/15227599

·          Link English: http://support.automation.siemens.com/WW/view/en/15227599

 

Message "CP 5611 A2 is no longer detected"

For information on the problem "CP 5611 A2 is no longer detected", refer to Section 6.2, "Notes on project engineering and configuration".

 

Further information on configuration

If connection establishment of a fully configured connection is started by a station that has a different station address from the configured station, the connection between the two partners will be established despite the difference.

 

 

 

9.    SOFTNET-DP (for PROFIBUS)

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

 

9.1    Version history

 

Version

Changes/additionally supported functions

V8.0

·        Windows 7, 32 Bit is supported

 

 

9.2    Restrictions

 

No parallel operation

Operating several SOFTNET CPs in one computer is not supported unless the second CP is used solely for configuration purposes with STEP 7.

The parallel operation of several protocols via SOFTNET CPs is not supported.

 

Communications processors CP 5411, CP 5511 and CP 5611

The communications processors CP 5411, CP 5511 and CP 5611 (all without the A2 suffix) are no longer supported by the SIMATIC NET software.

 

DPC2 transport call is not supported

DPC2 transport calls are not supported.

 

 

9.3    Notes on project engineering and configuration

 

Module cannot be started in the Station Configuration Editor

If there is a disruption on PROFIBUS (for example a bus short-circuit or duplicate node address), it is not possible to start the SOFTNET PROFIBUS module. In this case, eliminate the disruption before you try to start the module again.

 

Properties page in the Station configuration Editor

In the properties page of the Station configuration Editor, only fixed PROFIBUS bus profiles can be created for node initialization.

User-specific bus parameters for large network spans and networks such as redundant OLM rings can be specified with the "SIMATIC STEP 7/NCM PC " tool.

 

Message "CP 5611 is no longer detected"

For information on the problem "CP 5611 is no longer detected", refer to Section 6.2, "Notes on project engineering and configuration".

 

 

10.           SOFTNET DP slave (for PROFIBUS)

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

 

10.1    Version history

 

Version

Changes/additionally supported functions

V8.0

·        Windows 7, 32 Bit is supported

 

 

10.2    Restrictions

 

No parallel operation

Operating several SOFTNET CPs in one computer is not supported unless the second CP is used solely for configuration purposes with STEP 7.

The parallel operation of several protocols via SOFTNET CPs is not supported.

 

Communications processors CP 5411, CP 5511 and CP 5611

The communications processors CP 5411, CP 5511 and CP 5611 (all without the A2 suffix) are no longer supported by the SIMATIC NET software.

 

10.3    Notes on project engineering and configuration

 

Module cannot be started in the Station Configuration Editor

If there is a disruption on PROFIBUS (for example a bus short-circuit or duplicate node address), it is not possible to start the SOFTNET PROFIBUS module. In this case, eliminate the disruption before you try to start the module again.

 

Properties page in the Station configuration Editor

In the properties page of the Station configuration Editor, only fixed PROFIBUS bus profiles can be created for node initialization.

User-specific bus parameters for large network spans and networks such as redundant OLM rings can be specified with the "SIMATIC STEP 7/NCM PC " software tool.

 

Active / passive slave

The CP 5611 A2 and CP 5621 modules can be operated as active slaves (a special form of slave that is also PROFIBUS master at the same time).

In the configured mode, you can decide whether the slave is an active or passive slave in SIMATIC NCM PC or STEP 7.

Note the following: The configuration cannot be downloaded to a passive slave from a remote station.

With an active slave, the values are set in the configuration or in "Set PG/PC Interface" since they are common to the master and slave.

If the bus parameters for an active slave are set using "Set PG/PC Interface", make sure that the bus parameters of the master and slave match.

 

Message "CP 5611 is no longer detected"

For information on the problem "CP 5611 is no longer detected", refer to Section 6.2, "Notes on project engineering and configuration".

 

 

11.           CP 1613 A2 communications processor

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

Where the CP 1613 A2 is named below, this relates only to this CP; a CP 1613 (without the A2 suffix) is no longer supported.

 

As of the "SIMATIC NET PC Software, Edition 2007" CD, the two drivers for the CP 1613 (for industrial communication and for office/NDIS access) have been replaced by a common driver. This is displayed in the Device Manager under Network adapters.

 

 

11.1    Restrictions

 

Not with SOFTNET IE

It is not possible to operate SOFTNET IE over the CP 1613 A2.

 

IP addresses

The IP address for the automation protocols via ISO-on-TCP (synonymous with TCP/IP (RFC 1006)) must be different from the NDIS IP address for communication over PC networks.

 

Uninstalling / deactivating CPs using the "Device Manager"

Configured CPs must not be uninstalled/deactivated using the "Device Manager".

If you use the WinAC software product, the CPs must never be deactivated.

 

Deactivating protocols

The protocols TCP/IP and ISO must be deactivated since they are necessary for configured operation!

 

Downloading the Firmware

Using a CP 1613 A2, no firmware can be downloaded to a CP 1616 or to S7 CPs.

 

 

11.2    Notes on commissioning

 

Current driver disk (exclusive PC network operation)

Please compare the version of the driver disk / driver CD of your SIMATIC NET Ethernet software products with the versions on the SIMATIC NET CD (sw\Driverdisk folder). If this is newer, please create a new driver disk / CD by copying the content of the folder (sw\Driverdisk) to an empty CD and then use this as the driver disk.

 

Two TCP/IP addresses

On the CP 1613 A2, you can set two IP addresses during configuration; the reason for this is as follows:

On the one hand, the CP 1613 A2 communications processor is intended for operation with office communications protocols, for example TCP/IP. The office communications protocols run on the PC.

On the other hand, the CP 1613 A2 can also be used for automation purposes with the SIEMENS industrial protocols (SEND/RECEIVE, SAPI-S7). The protocols can either be handled over the transport protocol ISO or TCP/IP. Both transport protocols run in the firmware of the CP 1613. The interfacing of the TCP/IP transport protocol to the SIEMENS industrial protocol is according to the RFC 1006 specification.

This means that a total of two TCP/IP transport protocol functions can be operated on the CP 1613 A2 at the same time:

·          Office communications interfacing

·          Interfacing SIEMENS industrial protocols

Both interfaces must be assigned different TCP/IP addresses to identify them uniquely.

 

MAC addresses

After installing a new CP 1613 A2 module, you should always compare its active MAC address with the MAC addresses of other CP 1613 A2 modules or other Ethernet modules. Make sure that all the Ethernet modules operated in a network have different MAC addresses.

If the CP 1613 A2 installed in the computer is replaced by another CP 1613 A2 in the same slot, the new CP 1613 A2 will be assigned the MAC address of the CP 1613 A2 that was removed from the computer.

Even if the module is taken out of configured mode, it retains the MAC address. If you do not want the module in the network any more, change the MAC address or uninstall the CP.

Follow the steps below:

1.       After it has been taken out of the Station configuration Editor (out of configured mode), select the relevant module and uninstall it.

2.       Then restart your computer.

 

Time-of-day frames

When configuring the time intervals with STEP 7, only intervals of 1 s or 10 s are possible.

 

CP 1613 A2 is displayed in the device manager as "Ethernet Controller"

Select the relevant module and uninstall it. Then restart your computer.

 

Driver signature is not recognized

Sporadically, the signature of the CP 1613 driver is not recognized.

If this occurs, confirm the warning from the operating system with "Yes" to install the driver.

 

Passive connection establishment with the CP 1613 A2

If connections are established to the CP 1613 A2, the connection establishment timeout should not be set too low (for example with 64 connections, higher than 8000 ms).

 

Disabling the NDIS interface

The NDIS interface of the CP 1613 A2 must not be disabled. The linked protocols may only be removed if the CP 1613 is not in configured mode.

 

Using the firmware trace with more than one module

When you enable the firmware trace, check that the name of the trace file is different for each CP1613 A2.

 

 

11.3    Notes on project engineering and configuration

 

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

·         Link German: http://support.automation.siemens.com/WW/view/de/15227599

·         Link English: http://support.automation.siemens.com/WW/view/en/15227599

 

 

 

12.           CP 1623 communications processor

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

Update of a SIMATIC NET CD/DVD

An update of a SIMATIC NET CD/DVD using a driver CD after consultation with Customer Support is permitted.

 

 

12.1    Restrictions

 

General

The restrictions to the CP 1613 A2 listed in Section 11.1 also apply to the CP 1623.

 

XDB import with more than one CP 1623 installed

If more than one CP 1623 is installed in the computer, importing a configuration in the Station configuration Editor (XDB import) is possible only when the set addresses of the CP 1623 communications processor were adapted to the configuration previously in the "Configuration Console“.

If only the MAC addresses were configured, only the MAC addresses need to be set.

If only the IP addresses were configured, only the IP addresses need to be set.

If MAC and IP addresses were configured, both must be set.

 

Configuration in mixed operation CP 1613 A2/CP 1623

If the CP 1613 A2 and CP 1623 are used at the same time in one computer and you want to assign the configuration of a CP 1613 A2 to a CP 1623, the module assignment must be adapted in SIMATIC STEP7/NCM PC.

The module assignment is made in the "HW Config"/"PC Config" program in the object properties of the module, "Assignment" tab. The interface of the CP 1623 you want to configure must be entered there in the input boxes of the interface parameter assignment used.

This must be adapted for every CP 1623 that is to receive the configuration of a CP 1613 A2.

 

Port diagnostics over SNMP

Only the diagnostics of port 1 can be queried via SNMP.

 

Restriction for XDB import

Please note that an XDB import can only be made when the Station configuration Editor shows that >all< components can be replaced by compatible components.

 

 

12.2    Notes on commissioning

 

Current driver diskette (exclusive PC network operation)

Compare the version of this SIMATIC NET CP 1612 software product with the version of your driver diskette. If the version of the SIMATIC NET CP 1612 software product is newer than that of the driver diskette, please create a new driver diskette by copying the content of the folder (e. g.: …\SW\cp1512_cp1612) to an empty diskette and then use this as the driver diskette.

 

General

The notes on the CP 1613 A2 listed in Section 11.2 also apply to the CP 1623.

 

 

12.3    Notes on project engineering and configuration

 

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

·         Link German: http://support.automation.siemens.com/WW/view/de/15227599

·         Link English: http://support.automation.siemens.com/WW/view/en/15227599

 

 

13.           S7-1613

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

 

13.1    Version history

 

Version

Changes/additionally supported functions

V8.0

·        Windows 7, 32 Bit is supported

 

 

13.2    Restrictions and notes

 

SAPI S7: Passive connection establishment with the ISO protocol

Passive connection establishment at SAPI S7 with the ISO protocol has not been released.

 

PC network operation

PC network operation is released only for the TCP/IP protocol.

 

Number does not match slot

If there is more than one CP 1613 A2/CP 1623 module plugged in, the number of the module assigned by the SIMATIC NET software provides no information about the physical slot.

 

Restrictions configuring S7 connections

All communications modules of a PC must always be connected to a network in the STEP 7 project, otherwise even the S7 connections of a connected communications module do not work.

 

S7 programming interface: return values of the "s7_receive" function

When evaluating the return values of the "s7_receive" function, if unexpected values occur, the "s7_discard_msg" function must be called in the default branch of the corresponding switch instruction.

 

T communication

T communication is not supported by the SIMATIC NET PC products.

 

PC-PC communication with CP 1613 A2/CP 1623 to SOFTNET-S7 with Fast Acknowledge

Communication between a PC with a CP 1613 A2/CP 1623 communications processor and another PC with SOFTNET-S7 over ISO-on-TCP (synonymous with TCP/IP (RFC 1006)) is not possible under the following conditions:

·          PC with CP 1613 A2/CP 1623 only sends.

·          PC with CP 1613 A2 /CP 1623 does not provide receive resources.

·          "Fast Acknowledge is activated" ("Configuration Console").

Remedy: Disable fast acknowledge in SOFTNET S7.

 

 

13.3    Notes on project engineering and configuration

 

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

Link German: http://support.automation.siemens.com/WW/view/de/15227599

Link English: http://support.automation.siemens.com/WW/view/en/15227599

 

 

 

14.           TF-1613

 

The TF communications protocol is no longer supported by this SIMATIC NET software.

 

 

 

15.           S7-REDCONNECT and S7-REDCONNECT upgrade

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

Please note the descriptions of fault tolerant systems in the "Industrial communication with PG/PC" manual.

 

 

15.1    Version history

 

Version

Changes/additionally supported functions

V8.0

·        Windows 7, 32 Bit is supported

 

 

15.2    Notes on the product

 

Use of the "Power Pack S7-REDCONNECT" product

The "Power Pack S7-REDCONNECT" product is intended for users who have already installed the "S7-1613" product (with the current CD, "SIMATIC NET, PC Software V8.0") and now want to use the functions of "S7-REDCONNECT".

 

 

15.3    Restrictions

 

Do not use AUI cable

The CP 1613 A2 has two jacks for connecting network cables: The 15-pin sub-D female connector with slide locking mechanism both for connection of an AUI transceiver cable (AUI ‑  Attachment Unit Interface) and for connecting an ITP cable (ITP  –  Industrial Twisted Pair), and the RJ-45 jack for connecting a TP cable (TP  –  Twisted Pair).

For fault-tolerant connections, use only the 15-pin D-sub female connector for ITP cable or the RJ-45 jack for TP cable but not the AUI port for AUI transceiver cables!

 

Not between PCs

Redundant S7 connections between PCs are not possible.

 

Deactivating protocols

The protocols TCP/IP and ISO must be activated since they are necessary for configured operation!

 

Restrictions configuring S7 connections

All communications modules of a PC must always be connected to a network in the STEP 7 project, otherwise even the S7 connections of a connected communications module do not work.

 

S7 programming interface: return values of the "s7_receive" function

When evaluating the return values of the "s7_receive" function, if unexpected values occur, the "s7_discard_msg" function must be called in the default branch of the corresponding switch instruction.

 

Sporadic connection aborts

·         When using older versions of the CP 443-1 (up to "CP 443-1 EX02"), switching over between stop/start on an H-CPU can lead to connection aborts; Remedy: Replace the CP with a new version of the CP.

·         If there is continuously high CPU usage on the PC, connection aborts are possible with slower network components; Remedy: Whenever possible, use 100 Mbps, full duplex.

 

 

15.4    Notes on installation, configuration, project engineering

 

Fixed parameter values

The settings of persistence count and abort timeout using the SAPI S7 mini DB have no effect on fault-tolerant S7 connections. On such connections, fixed internal values are used to achieve the necessary, short failover times.

 

How to configure fault tolerance

 

Step

Description

1

Enter all the hardware components of your automation system in STEP 7, HW Config. These include both the CPs in the SIMATIC S7 stations as well as the user applications on the PCs and the SIMATIC NET network adapters.

2

Following this, you can configure the fault tolerant S7 connections for the individual user programs:

·         After saving in HW Config, you set the addresses for the CPs with STEP 7, NetPro and connect the CPs to the appropriate subnets.

·         Select "S7 connection fault-tolerant" for the connection type parameter.

·         In the properties dialog, you decide whether you want to 2 or 4 path redundancy for this connection by activating the "max. CP redundancy" check box.

3

Save and compile in NetPro to generate the databases (SDB and XDB files). Download the databases to the S7 stations and download or import them to the configure PC stations.

 

For more detailed information, refer to the "Commissioning PC Stations (with Advanced PC Configuration)" manual.

 

Please remember that following any change in the connection configuration in STEP 7, NetPro the current configuration must be downloaded or imported again into the S7 and PC stations.

 

Configuring a CP 443-1

If you insert a CP 443-1 into a SIMATIC S7 station, the "Activate fast failover of the connection" check box must be activated (dialog box "Properties – CP 443-1 ..." ->Options -> Ethernet Profile for Fault-Tolerant Connections -> activate fast failover of the connection).

 

How 4-path redundancy functions

If you have configured your fault-tolerant S7 connection with maximum CP redundancy (4 paths), if the productive or reserve path fails, another connection path will be established (assuming it is available). The failover can take between several seconds and several minutes depending on your configuration.

The connection is then redundant again (over a new path).

Please note that depending on the configuration, it is possible that the two connection paths now include non-redundant components (not ideal redundancy). At this point, one further redundant component can fail without S7 communication being disturbed (as long as it is not used by both paths).

For more detailed information, refer to the document "Industrial Communication for PG/PC".

 

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

Link German: http://support.automation.siemens.com/WW/view/de/15227599

Link English: http://support.automation.siemens.com/WW/view/en/15227599

 

 

15.5    "S7 Connection Diagnostics"

 

Area of application

This program makes it easier to commission fault-tolerant connections and informs you when there is a problem on a specific connection path.


Connection diagnostics can only diagnose connections that were configured with STEP 7 or NCM PC. Connections configured with COML S7 are not visible.

 

Start

The use of the diagnostic program is possible only when you have downloaded a STEP 7 and accordingly a NCM PC configuration.

You start the diagnostic program from the SIMATIC path (Windows Start menu Start -> ...  -> SIMATIC -> SIMATIC NET -> S7 Connection Diagnostic).

 

Online help

Click on the ?  menu command-> Contents for information on the program.

 

Dealing with memory access violations

If there is a memory access violation in an application that works with S7-REDCONNECT, or if it no longer reacts for one reason or another, it is possible that the display in the diagnostic program is no longer refreshed. In this case, you must restart all applications that use S7 connections.

 

Software diagnostic interface

It is also possible to read diagnostic data from your own user program. See Section "Diagnostic Services for Fault-tolerant Connections" in the "S7 Programming Interface" manual.

 

 

 

16.           The CP 1612 and CP 1612 A2 communications processor

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

 

16.1    Version history

 

Version

Changes/Additionally Supported Functions

V8.0

·        Windows 7, 32 Bit is supported

 

 

16.2    Notes

 

 Current driver disk (exclusive PC network operation)

Please compare the version of the driver disk / driver CD of your SIMATIC NET Ethernet software products with the versions on the SIMATIC NET CD (sw\Driverdisk folder). If this is newer, please create a new driver disk / CD by copying the content of the folder (sw\Driverdisk) to an empty CD and then use this as the driver disk.

 

 

16.3    Restrictions

 

Modules per computer

Per computer, only one module of the type CP 1612/CP 1612 A2 or IE General can be used in configured mode.

 

Hot plugging

The CP 1612 and CP 1612 A2 communications processors are not approved for hot plugging. 

 

 

17.           SOFTNET PN IO

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

 

17.1    Version history

 

Version

Changes/additionally supported functions

V8.0

·        Windows 7, 32 Bit is supported

 

 

17.2    Notes on the product

 

PNIO_data_read( ) without user data

The PNIO_data_read( ) function can also be called with the parameters "BufLen=0" and "pBuffer=NULL" to simply read the remote status of the communications partner.

 

Recompiling applications

Improvements were made to SN PN IO that have repercussions on earlier versions. You should therefore recompile applications that use the C interface of SN PN IO if your application was created with a version of the SIMATIC NET CD older than Edition 2008.

 

 Defining the preprocessor directive "PNIO_Softnet"

In an SOFTNET PN IO application that uses the C interface of SOFTNET PN IO, the PNIO_SOFTNET #define must be defined before header files are linked.

 

 

17.3    Restrictions

 

Number of network adapters

A maximum of one (1) network adapter with SOFTNET PN IO can be operated.

 

Deactivating Ethernet network cards

Ethernet network cards must not be deactivated.

 

Deactivating protocols

None of the protocols TCP/IP, PROFINET IO RT, and ISO must be deactivated since they are necessary for configured operation!

 

Writing to individual submodules of an ET 200S

It is only possible to write to individual submodules of an ET 200S station after all submodules of this station (with status=Good) have been written to. This applies both during startup and when a station returns following station failure.

This restriction is due to the firmware version of the ET 200S and does not apply as of version V2.0.0.

 

Update times for cyclic data exchange

The update time proposed by STEP 7 must be increased as follows if you have a larger hardware configuration:

·         up to 16 devices: 8 ms

·         up to 32 devices: 16 ms

·         up to 64 devices: 32 ms

The information above applies in 100 Mbps full duplex mode, with an adequately powerful PC (CPU utilization < 40%).

 

Operation with CP 1613 A2 or CP 1623

It is not possible to operate SN PROFINET IO over the CP 1613 A2 or CP 1623 .

 

Restrictions in the PROFINET IO-Base user programming interface

The use of CLEAR mode in the current version is not adequate to switch IO devices to the safe status. For all modules, the function "PNIO_data_write" must be called with the parameter "IOLocState=BAD".

The "PNIO_data_read" function can be executed even in CLEAR mode.

The use of the CLEAR mode is therefore not released even with the OPC interface using the "&mode()" and "&modeval()" items. The "PNIO_controller_close()" function must only be used in the OFFLINE mode.

The user may only call "PNIO_set_mode" again when a previous "PNIO_set_mode" job was acknowledged with PNIO_CBE_MODE_IND.

 

PNIO_rec_read_req (send read data record job) parameter "Length"

"Length" parameter: Maximum length of the data record (in bytes) to be transferred by the IO device. The pointer to the data record and its actual length is returned by the callback event PNIO_CBE_REC_READ_CONF.

 

Callback event PNIO_CBE_REC_READ_CONF (report result of a read data record job)

"Length" parameter: Length of the transferred data record (in bytes) to which "pBuffer" points.

"pAddr": Address of the module of the device that answered the read data record job.

 

Hyperthreading

On PCs with activated hyperthreading, it may take longer for the PROFINET IO system to start up (several minutes): Remedy: Disable hyperthreading (BIOS).

 

Data records

This version supports reading of data records only up to a length of 480 bytes.

 

"Accessible nodes“ and "Assign Ethernet address“ in PROFINET IO mode

When running a PROFINET IO user program, the "Accessible nodes" function in STEP 7 or the "Assign Ethernet Address" function in NCM S7 diagnostics must not be executed via the same Ethernet interface. First exit your PROFINET IO user program or use different Ethernet interfaces.

 

Download during PROFINET IO operation

While a PROFINET IO user program is active, there must be no download of a configuration. First shut down your PROFINET IO user program.

 

No XDB import in "offline mode"

During the XDB import of a SOFTNET PN IO project, the "Work in offline mode" check box must not be selected. Otherwise calls for the PROFINET IO Base interface are rejected with the error message "PNIO_ERR_INVALID_CONFIG"

 

Sporadic connection aborts under load

If you experience sporadic connection aborts, you should check whether processes on the computer are sometimes interrupting the SOFTNET PN IO data flow. IO load can, for example, be caused by the Windows indexing service, the background defragmentation or heavy network traffic.

If there is no improvement after reducing simultaneously running processes, the system stability can be improved by increasing the default update time of 8 ms to 16 ms or 32 ms.

You should consider updating the hardware if the kernel times exceed the 40% mark for longer periods in the Windows task manager. Here, a modern multi-core CPU is much more resilient to connection aborts caused by IO load than a single core CPU.

If these measures do not bring about an improvement in the system performance, please contact Customer Support to work out an individual solution.

 

Simultaneous operation of a C application and the PROFINET IO OPC server is not released

In SIMATIC STEP 7/NCM PC, if the PROFINET IO controller of an IE general CP is assigned to the OPC server application, simultaneous operation of an unassigned C IO Base application and the assigned PROFINET IO OPC server is not released.

 

 

17.4    Notes on project engineering and configuration

 

Network bridge

With a network card that has been added to a "Network bridge" added, it is not possible to operate SOFTNET Industrial Ethernet.

If you want to use a network card inserted in a network bridge for SIMATIC NET products, you must first remove it from the network bridge before installing the "SIMATIC NET, Software CD".

 

Deactivated network adapters

When you install the SIMATIC PC software over older versions, deactivated network adapters are reactivated.

 

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

Link German: http://support.automation.siemens.com/WW/view/de/15227599

Link English: http://support.automation.siemens.com/WW/view/en/15227599

 

Registering a network adapter for configured mode

A network adapter only needs to be registered for configured mode when the configuration was downloaded with SIMATIC STEP 7/NCM PC to the PC station or imported using an XDB file before the computer was restarted.

 

PROFINET IO OPC server and security settings

If the "Disable" button was clicked in the "Security" dialog in the "Configuration Console" program, you will need to click the "Enable" button (remote basic and OPC communication first before you can resume remote communication over the PROFINET IO OPC server.

 

 

 

18.           SOFTNET-S7 for Industrial Ethernet

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

 

18.1    Version history

 

Version

Changes/additionally supported functions

V8.0

·        Windows 7, 32 Bit is supported

 

 

18.2    Restrictions

 

SAPI S7: Passive connection establishment with the ISO protocol

Passive connection establishment at SAPI S7 with the ISO protocol has not been released.

 

Number of network adapters

A maximum of 1 (one) network adapter with SOFTNET-S7 can be operated.

 

Deactivating Ethernet network cards

Ethernet network cards must not be deactivated.

Deactivating protocols

None of the protocols TCP/IP, PROFINET IO RT, and ISO must be deactivated since they are necessary for configured operation!

 

Note on the SEND/RECEIVE programming interface and OPC, use of expedited data over ISO connections

If data packets of the "Expedited Data" type are transferred on a SEND/RECEIVE ISO connection, the receiving application at the PC must make sure that this data is actually accepted. Otherwise, the buffering of these data packets can lead to a lack of memory that can eventually cause the connection to be terminated.

This means that if you use an ISO connection with your OPC user program, a receive item must be activated on this connection.

 

Restrictions configuring S7 connections

All communications modules must always be connected to a network in the STEP 7 project, otherwise even the S7 connections of a connected communications module do not work.

 

S7 programming interface

Return values of the "s7_receive" function: When evaluating the return values of the "s7_receive" function, the "s7_discard_msg" function must be called if unexpected values occur, for example in the default branch of the corresponding switch instruction.

 

T communication

T communication is not supported by the SIMATIC NET PC products.

 

Loss of connections

If the number of input buffers of the used CP is less than the number of packets that come from the network, connections may abort.

 

High number of connections with long frames

If you have a high number of connections (for example more than 32) and the PDU length is greater than 960 bytes, you should disable fast acknowledge otherwise there may be a frame overload.

 

WLAN (Wireless LAN)

WLAN PC modules (Wireless LAN) are supported only with PG functionality with the TCP/IP protocol. 

 

S7 communication between an S7-1200 (firmware version V1.0) and SIMATIC NET OPC

The S7-1200 stations do not support all properties of S7 communication with OPC. Only the variables services and some S7-specific information variables have been released.

 

In the variables service, only access and monitoring of data blocks, inputs, outputs and bit memory is possible. Data blocks are accessible only via S7 communication if the option "Symbolic addressing only" is not enabled in STEP 7 BASIC V10.5.

 

Of the S7-specific information variables, only &identify(), &statepath() and &statepathval() are supported.

 

A maximum of two S7 connections between an S7-1200 and a SIMATIC NET OPC server have been released. The following connection establishment parameters must also be set:

 

At "http://support.automation.siemens.com/WW/view/en/39960679", you will find instructions for setting up an S7 connection between an S7-1200 and SIMATIC NET OPC with the SIMATIC NCM PC tool.

 

You can also set up an S7 connection between an S7-1200 and SIMATIC NET OPC with COML S7 (Configuration Management local - configuration software for S7 connections). See manual "Industrial Communication with PG/PC Volume 2 - Interfaces", section 2.5.12.

 

 

18.3    Notes on project engineering and configuration

 

IE General in stop mode after starting up

In individual cases, it is possible that a component of the type "IE General" configured in a PC station remains in Stop mode after the PC station has started up and the diagnostic entry indicates an 0x381 error in the router subsystem. In this case, reconfigure and load the PC station again.

 

Special parameter setting

If you want to operate a configured ISO transport connection between a PG/PC and a SIMATIC programmable controller, please use the parameter settings shown below on the SIMATIC programmable controller.

 

Parameters

Value

Retransmission Time for data transfer

2000 ms or higher

Retransmission max. count for data transfer

10 or higher

 

Lower values, for example the default values, can cause the connection to break down.

 

Multiple protocol operation

Multiple protocol mode means that you can communicate with the S7 protocol and the SEND/RECEIVE protocol at the same time. With each of these protocols, you can decide whether or not you want to use the ISO or ISO-on-TCP (synonymous with TCP/IP (RFC 1006)) transport protocol.

 

Message MAC address does not exist in Configuration Console

If you receive the message that the MAC address does not exist in the "Configuration Console" program, you have probably accidentally deleted the "SIMATIC Industrial Ethernet (ISO)" protocol. Reinstall the protocol.

 

Network bridge

With a network card that has been added to a "Network bridge" added, it is not possible to operate SOFTNET Industrial Ethernet.

If you want to use a network card inserted in a network bridge for SIMATIC NET products, you must first remove it from the network bridge before installing the "SIMATIC NET, Software CD".

 

Deactivated network adapters

When you install the SIMATIC PC software over older versions, deactivated network adapters are reactivated.

 

Multiple IP addresses

For the S7 connections, only the last IP address in the IP address list can be used.

IP address list, see: "Extended TCP/IP Settings" dialog.

 

Configuration limits and performance data of the modules

You will find the configuration limits and performance data of the modules on the Siemens Web pages as FAQs under entry ID 15227599.

Link German: http://support.automation.siemens.com/WW/view/de/15227599

Link English: http://support.automation.siemens.com/WW/view/en/15227599

 

Registering a network adapter for configured mode

A network adapter only needs to be registered for configured mode when the configuration was downloaded with SIMATIC STEP 7/NCM PC to the PC station or imported using an XDB file before the computer was restarted.

 

Matching up connection monitoring times

In SIMATIC STEP 7/NCM PC, HW Config, you can select the connection monitoring time of an Industrial Ethernet SOFTNET module in the "Options" tab. This should be lower than the value of the connection establishment timeout and job timeout in the "OPC" tab of the "Properties S7 Connection" dialog in SIMATIC STEP 7/NCM PC, NetPro.

 

Note specifically for "SOFTNET-S7 for Industrial Ethernet":

Out-of-date STEP 7 hardware catalog

SOFTNET-S7 supports connections as of V6.0 64.

STEP 7 to V5.1 SP2 does not display this in the hardware catalog.

 

The "Configuration Console" program does not detect installation removal in isolated cases

In isolated cases, it is possible that the "Configuration Console" program does not recognize the installation or removal of a module. In this case, restart your computer.
Note: If "Configuration Console" has not recognized the module after it is installed, the module will not be able to communicate over SIMATIC NET.

 

Unsatisfactory transmission rate on a separate network

If the transmission rate on a separate network is not satisfactory, check the following conditions:

·       You have installed two SOFTNET IE network adapters in a PC

·       The first network adapter is used for SIMATIC NET products

·       The second network adapter communicates over the separate network

To increase the transmission rate, delete the gateway entry of the first network adapter used by SIMATIC NET products in the Windows network settings.

 

 

19.           SOFTNET-S7 Lean for Industrial Ethernet

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

 

19.1    Version history

 

Version

Changes/additionally supported functions

V8.0

·        Windows 7, 32 Bit is supported

 

 

Note

·       The same restrictions apply to "SOFTNET-S7 Lean for Industrial Ethernet" as for "SOFTNET-S7 for Industrial Ethernet" in Section 18.2, "Restrictions".

·       The same Notes on configuration and project engineering apply to "SOFTNET-S7 Lean for Industrial Ethernet" as for SOFTNET-S7 for Industrial Ethernet in Section 18.3, "Notes on configuration and project engineering".

 

 

20.           SOFTNET-PG for Industrial Ethernet

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

 

20.1    Version history

 

Version

Changes/additionally supported functions

V8.0

·        Windows 7, 32 Bit is supported

 

 

20.2    Restrictions

 

PG functions only

The "SOFTNET-PG" product allows operation of PG functions only (SIMATIC STEP 7).

 

Number of network adapters

A maximum of 1 (one) network adapter with SOFTNET-PG can be operated.

 

 

20.3    Notes on project engineering and configuration

 

Further information

For information on the following topics, refer to Section 18.3, "Notes on configuration and project engineering":

·         Message MAC address does not exist in Configuration Console

·         Network bridge

·         Deactivated network adapters

 

 

 

21.           PN OPC Server

 

The PN OPC server is no longer supported by this SIMATIC NET software.

 

 

 

22.           SNMP OPC Server

 

Please make sure that you read the following sections in this document:

Section 23, "General requirements, notes, and restrictions"

Section 24, "Information, restrictions and notes relating to OPC"

Section 25, "Notes on license keys"

Section 26, "Requirements and restrictions relating to hardware in general"

Section 28, "Notes on C programming interfaces"

Section 29, "Notes on project engineering, configuration and NCM"

Section 32, "Operating systems 32 bit"

You only need to read the other sections if they relate directly to your product.

 

 

22.1    Version history

 

Version

Changes/additionally supported functions

V8.0

·        Windows 7, 32 Bit is supported

 

 

22.2    Licenses

 

There is a license key for each performance level of the "SNMP OPC server":

·         1 license key for administration of up to 20 IP addresses in the "Basic" version.

·         1 license key for administration of 20 or more IP addresses with the "Extended" version.

 

The Extended version therefore uses 2 license keys and both must be transferred from the supplied USB key stick.

 

SNMP OPC server "PowerPack" is an extension package for the basic version and contains the license key for administration of more than 20 IP addresses.

 

 

22.3    Restrictions

 

Under some circumstances, SNMP variables cannot be modified in less than 2 seconds

Depending on the SNMP device, SNMP variables cannot be modified or read in less than 2 seconds.

 

Update and cycle times of one millisecond

Update and cycle times of one millisecond cause 100% CPU utilization even with a medium sized configuration and make the computer unusable.

 

Information variable &ping( ) does not send ICMP ping packets on the network

The information variable &ping( ) uses the Microsoft ICMP ping functions. Under certain circumstances that cannot be defined in detail, this does not send any ICMP ping packets on the network.

 

 

22.4    Notes on project engineering and configuration

 

SNMP profile "Profil_IPC_V11.txt" must not be modified

The SNMP profile "Profil_IPC_V11.txt" is a predefined profile. This must not be modified.

Below, you will find two notes on the monitoring of SNMP devices:

 

Note 1 on monitoring SNMP devices

If you want to monitor a network adapter in a PC station as an SNMP device, make sure that you make the following settings:

·         The SNMP service must be installed on station.

·         The community configuration for the SNMP service must match your plant configuration.

·         The UDP port for the SNMP service must be enabled in the firewall configuration.

 

Note 2 on monitoring SNMP devices

You want to monitor CP 1613 A2 as an SNMP device, make sure that the following settings are made:

·         The software of the CD "SIMATIC NET, PC Software" version 6.2 SP1 or higher must be installed on the PC in which the CP 1613 A2 is inserted.

·         The "private" or "public" community must be set in the plant configuration if you want to read values.

·         The "private" community must be set in the plant configuration if you also want to write values.

 

Select the SNMP device timeout significantly higher than the update rate and the update rate significantly higher than the cycle time

Where possible, select a timeout value (default 9000 ms) that is higher than the update rate (for example 500 ms) by a factor of 10 on the OPC client. The update rate should be higher than the cycle time of the OPC server (default 100 ms) by a factor of approximately 5.

If you are using a large number of SNMP devices (for example 100 devices) each using approximately 100 OPC items, the timeouts should be increased to the highest setting of 60 000 ms. The update rate should be set lower by a factor of 10 or approximately 6000 ms. The cycle time of 100 ms can be kept.

 

 

 

23.           General requirements, notes, and restrictions

 

23.1    Restrictions

 

Installation of the SIMATIC NET CD

If the computer name (My Computer->System Properties->Computer Name) contains special characters such as ä, ö, ü, ß, _ or others, it is not possible to install the SIMATIC NET CD.

The only characters allowed are (a-z), (A-Z), (0-9) and (-).

 

When installing or updating the SIMATIC NET software, there must be no SIMATIC NET modules in operation.

Following a driver update always reboot.  

Functionalities that cause problems

The following functionality is not supported because of potential problems during operation with SIMATIC NET:

·         The status "hidden" and "superhidden" must not be modified later for files installed
with SIMATIC NET.

·         It is not possible to assign UNC path names for databases or programs of SIMATIC NET.

·         User programs that communicate using SIMATIC NET must not be used as Windows services (background processes) and must not be triggered in the Autostart group to avoid undefined initialization statuses during startup. Instead, use the Autostart function for applications and services in the "Configuration Console".

·         Configuration Console: Changing bus profiles (DP, standard, ...) is not permitted. Instead use Set PG/PC Interface.

·         Set PG/PC Interface: When you set the bus parameters in the "Standard" and "Universal (DP/FMS)" profiles, the network configuration must be specified explicitly.

 

Functions that have not been released

The following functions are not released because they have not been tested:

·         Installation on replaceable disks or enlarged hard disks ("DFS") is not released.

·         Installation in a folder that references other drives (known as "junction points") is not supported.

·         The "Disk Quota" property is not supported, in other words, if you have set a maximum value, this could nevertheless be exceeded when you install SIMATIC NET software.

·         Industrial Ethernet must not be operated with IPSec.

·         Industrial Ethernet must not be used in VPN (Virtual Private Networks).

 

Server operation with domain controller support is not released

The "SIMATIC NET, PC Software V8.0" CD has not been released for server operation with domain controller support.

 

Required Microsoft software packages:

Do not uninstall the Microsoft software packages

because these are required by the SIMATIC NET CD software.

 

Multiple Ethernet CPs in the same IP subnet

Multiple Ethernet adapters should not be operated in one PC in the same IP subnet. This can lead to functional problems (see also http://support.microsoft.com/kb/175767/EN-US/).

 

 

23.2    Further notes

 

Fujitsu-Siemens PC with mainboard D2608

If you are installing the SIMATIC NET CD on a Fujitsu-Siemens PC with mainboard D2608 and BIOS version 6.00 R1.04.2608.A1, you will first need to update the BIOS to version 6.00 R1.11.2608.A1 from Jan. 28, 2009 or a newer version.

 

Error message while installing over an existing installation

If you install over an existing installation, the following message may be displayed by the service control manager:

 

"At least one service or driver failed during system startup. Use Event Viewer to examine the event log..."

 

You can ignore this message. The error is irrelevant because the PC will be started up again and the service will start then.

 

DCOM error in the Event Viewer

The configuration of a PC station with PCS7/APACS + option V6.0 replaces the DA0350.DLL from version 3.50.3602 with version 3.51.1608.0. As a result, the Event Viewer displays the message "DCOM Error" every two minutes for the SIMATIC NET Configuration Server and SIMATIC NET Configuration Service. These entries have no effect on SIMATIC NET DCOM communication.

 

DCOM settings and MSI installation

If you have changed the standard DCOM settings as described in the "Commissioning PC Stations Manual and Quick Start" to allow communication with the DCOM OPC server, you cannot install/uninstall any further MSI-based programs (this also applies to installing or configuring Microsoft IIS and activating the OPC XML DA Web service because the Microsoft Management Console does not accept the authorization). This restriction does not, however, apply when you install a "SIMATIC NET, PC Software" CD or a new service pack.

If you need to do this, you must change the default DCOM settings while you install and configure. Follow the steps below:

1.  Note down the settings made on your PC for the parameters "Default Authentication Level"  and "Default Impersonation Level" (taskbar Start -> Run -> "dcomcnfg"  and open  ->  Default Properties -> tab, dialog section Default Distributed COM Communication Properties).

2.  Set the parameters as follows:

 

Parameters

Setting

Default Authentication Level

Connect

Default Impersonation Level

Identify

 

Restart your PC. It is now possible to install/uninstall a further MSI-based program. SIMATIC NET applications that communicate using the DCOM server, are, however, no longer fully functional.

3.  Set the original settings for the "Default Authentication Level" and "Default Impersonation Level" again.

 

This restriction does not, however, apply when you install a "SIMATIC NET, PC Software" CD or a new service pack.

 

OPC trace paths

Storage space for OPC trace paths must be set up for all users with write permissions. The proposed value after installation already references an OPC trace path with suitable write permissions. If the trace path is changed, this must also be given write permissions for all users.

 

New installation paths for configuration and program data as of the "SIMATIC NET, PC-Software V8.0" CD

To support the Windows 7 32-bit operating system as of V8.0, new installation paths for modifiable configuration and program data as recommended by Microsoft:

·         Program data (trace and log data) for all users

-   Path in the file system in Windows 7: <drive:>\Users\Public\Documents\Siemens\SIMATIC.NET

·         Configuration data, for example for the OPC protocol server

-   Path in the file system in Windows 7 (hidden path in the file system): <drive:>\ProgramData\Siemens\SIMATIC.NET.

 

Installing and removing modules in the Device Manager

When you remove a module from the PC, the operating system usually asks you whether or not you also want to remove the driver. If you answer this question with "Yes", the driver must then be reinstalled if you want to use this module again. All drivers can be reinstalled from the SIMATIC NET CD; Ethernet drivers can also be installed from the driver disk.

 

Delays in TCP communication with multiple network adapters on different networks

When using more than one network adapter with various TCP/IP configurations, delays of up to several seconds are possible in TCP/IP communication.

If, for example, a standard gateway is configured on a second network adapter, the re-establishment of a TCP/IP SNMP connection over the first network adapter can take many seconds if the connection establishment is first attempted over the second adapter.

Remedy: Enter the required IP addresses in the local static ARP table.

 

 

Installation error when overinstalling SIMATIC NET software

If you are overinstalling, the message "s7oiehsx.exe – Error in application" is output in rare cases. You can ignore the error message and continue the installation.

 

 

Adopting security settings for other firewall manually

If you use a firewall from another vendor instead of the firewall from Microsoft, the security settings from the "Configuration Console" are not adopted. In this case, the settings must be made by the user as described in the online help for this topic. When blocking communication, the procedure is the same.

 

Firewall profiles in Windows 7 prevent communication after changing profiles.

As of Windows 7, the profiles for modules can switchover automatically if, for example, the module is disconnected from the DHCP server. The installation only enables the firewall settings for the active profiles. If the profiles change later, communication is blocked. This can be remedied in the "Configuration Console" with the "Allow" button in the "Security" dialog. If this is clicked (possibly after clicking "Deny"), the firewall settings are enabled again for communication. By clicking this button, all profiles for the modules are released for communication.

 

 

 

24.           Information, restrictions and notes relating to OPC

 

24.1    OPC as standard interface

 

The SIMATIC NET software products have access via OPC as the default interface. The user therefore has standardized access options for all protocols of these products.

 

 

24.2    Restriction with OPC

 

OPC DA V1.0: The IOPCAsyncIO, IDataObject interfaces are no longer released 

The OPC DA V1.0 IOPCAsyncIO, IDataObject interfaces are no longer released.

 

 

OPC UA functionality after changing the computer name

If the computer name is changed after installing the CD, certificates installed for OPC UA are invalid and OPC UA is no longer capable of functioning.

Remedy: Create a new UA configuration with the "Configuration Console" in "OPC-UA Certificates" with ->"Recreate OPC UA configuration".

 

OPC UA Discovery: Discovery of computer names is case-sensitive

When discovering computer names (OPC UA Discovery), the names must differ by more than simply upper or lower case letters.

Use the new OPC Data .NET control, this restriction does not then apply.

 

OPC Scout V10: No support of OPC UA methods

The OPC Scout V10 does not support calls of OPC UA methods.

 

OPC Automation interface is not released for multi-thread user programs

The OPC Automation interface cannot ensure data consistency if there is simultaneous access by several threads. There is also a possibility of illegal memory access. The use of the OPC Automation interface in multi-thread user programs is therefore not released.

 

Automation Interface for Alarms and Events not yet available

The Automation Interface for Alarms and Events described in the documentation supplied with the "SIMATIC NET, PC Software" CD is not yet available in this version of the "SIMATIC NET, PC Software" CD.

 

100 % CPU utilization with OPC Alarms and Events leads to memory leaks

At 100 % CPU utilization of the OPC Alarms and Events server, no memory can be released. Avoid this high utilization.

 

OPC XML Web service: byte array returns "E_BADTYPE"

When accessing OPC XML items of the PROFINET byte array data type "VT_ARRAY|VT_UI1", the error "E_BADTYPE" is returned for the "GetProperties" or "Browse" call.

 

Detectable data types when converting from symbol files of the type SSD, WSD

When you convert a symbol file of the type SSD, WSD to the type STI in the Symbol File Configurator, only the data types of symbols of imported STEP 7 projects and free symbols with protocol ID S7 can be detected. In these cases, VT_EMPTY is entered. You then need to change the data type manually in the Symbol File Configurator. OPC clients, such as the OPC Scout V10 require the data type of the item to be able to write values.

 

If there is high CPU utilization, data change messages arrive more slowly

If there is a high CPU utilization (approaching 100%), data change messages may be reported over the DP OPC server to the OPC client with a delay. This also applies when "Hardware Events of Slave IO Data" was configured.

If you use a single thread C user program that uses the DP-Base interface instead of OPC, this delay does not occur.

 

Polling time restriction in DP slave operation of the CP 5614 A2 and CP 5624

If you use consecutive calls for synchronous reading from the device or synchronous writing to device over OPC with DP-V1 protocols, make sure that this does not occur faster than the standard polling time.

 

Which DP mode for the CP 5613/CP 5614 as DP slave?

A CP 5603 / CP 5613 A2 / CP 5623 / CP 5613 FO / CP 5614 A2 / CP 5624 communications processor as a DP slave can only be operated as a DP-V0 slave via OPC.

 

Restricted operation of a SOFTNET DP master class 2, for example CP 5611 A2, with an active hardnet DP master, for example CP 5613 A2

Browsing the OPC address space of the slaves of a Softnet DP master class 2 and the use of its OPC items is not possible while a Hardnet DP master class 1 is monitoring these DP slaves over OPC. The slaves then no longer appear in the address space, OPC items belonging to them cannot be used.

 

Writing output items when the DP master is not in the OPERATE mode

Please note that written output items can only be sent to the DP slave when the DP master is in the OPERATE mode. In another DP master statuses, although the operation is acknowledged with S_OK, the items are not sent to the DP slave.

 

Downloading the configuration of a PC station

Close the Symbol File Configurator during download of the project engineering PC station.

 

PROFINET IO OPC server: browsing for DP slaves downstream from the IE/PB Link PN IO

If an IE/PB Link PN IO is used as a proxy IO device, the actual names of the slaves on PROFIBUS cannot be displayed. "IE-PB-Link" is displayed as the name plus a device ID.

 

Symbol File Configurator: User interface inoperable during time-intensive activities

During activities such as CSV import, CSV export and saving files with an extensive content, there may be long waiting times. The user interface is not updated during this time. This makes parallel operation impossible. Please wait until complete.

 

S7 connections with OPC over Industrial Ethernet

If a PC is used both as client and server for S7 services, for example S7 variable server, the connection property

"Maximum number of parallel network jobs" must be set to 2 in STEP 7. You will find this parameter in the "Properties S7 Connections" dialog.

 

S7 Server services with OPC server V6.3 configuration released

The S7 server services have been released only with OPC server V6.3 configurations of the PC station.

 

Do not use OPC Alarms & Events from the S7-200 station

S7-200 stations do not support OPC Alarms & Events. Do not configure any S7 connections to an S7-200 or S7-300 station over the OPC server in SIMATIC STEP 7/NCM PC/NetPro with activated alarms. Otherwise connections may abort.

 

Absence of DP slave data in the OPC Scout with DP master class 2

The absence of DP slaves in the display in the master class 2 part of the OPC Scout (DP master class 2) indicates that the TTR time set in the configuration is too short.

The TTR time should be increased in the configuration (user-defined parameters).

 

Supported data types with deadband functionality

The SIMATIC NET OPC server supports deadband functionality with the following data types:
Analog data (EUType =1) and canonical types VT_I1,VT_I2, VT_I4, VT_R4, VT_R8,  VT_UI1, VT_UI2, VT_UI4.

  

Symbols in the root directory of the symbol file with V6.2.1

A symbol file created with "SIMATIC NET, PC Software" CD V6.2.1 with symbols in the root directory of the symbol file cannot be opened with the Symbol File Configurator as of version V6.3. Nor is it is possible to browse the namespace via OPC.
Remedy: CSV export of the symbols in V6.2.1, then CSV import as of V6.3.

 

No PROFINET IO communication over OPC

Sporadically, it is possible that no PN IO communication can be established over OPC after starting up the PC. In this case, exit the OPC server and restart it in the "Configuration Console" with "Applications" -> "OPC Settings" -> "Exit OPC Server" -> "Start OPC Server".
Then restart your OPC application.

 

Reading/writing data records over OPC with a CP 5614 A2/CP 5624 DP slave

Reading/writing data records over OPC is not supported with the
CP 5614 A2 / CP 5603 / CP 5613 A2 / CP 5623 / CP 5624 DP slave.

 

Replacing a CP 5614 A2 with a CP 5624

If OPC is used as the interface in a DP slave, when you replace a CP 5614 A2 communications processor with a CP 5624 communications processor or vice versa, note the following:

·         Before uninstalling the CP, operation with OPC must be deactivated in the DP slave settings in the "Configuration Console" (uncheck "Use DP slave module with OPC" and confirm with "Apply")

·         After installing a new CP, the settings must be made again in the "Configuration Console". For more detailed information, refer to the "Commissioning PC Stations" manual.

 

DP-V1 slave diagnostic interrupts are not acknowledged over the DP OPC server

Configured diagnostic interrupts are not explicitly acknowledged by DP-V1 slaves over the DP OPC server. Use the DP‑Base interface for this. This is not possible for applications with an OPC interface. Applications with a DP‑Base interface support this functionality.

 

PROFINET IO OPC server: Changes OFFLINE <-> OPERATE are permitted

Contrary to the description in the "Industrial Communication with PG/PC Volume 2 - Interfaces" manual Section 2.9.7, mode changes to any mode are possible with the "&mode()" OPC or "&modeval()" item, so that, for example, a direct change from OFFLINE to OPERATE is possible and vice versa.

The OFFLINE mode can be set, for example, to stop the IO controller. Only during startup (when the first client connects to the OPC server), contrary to the description, there is no automatic change to CLEAR mode but to OPERATE mode if "Set PNIO controller automatically to OPERATE" was configured with NCM.

 

Release of the SIMATIC NET OPC data OCX

The OPC data OCX is released for the following operating systems and compilers:

·         Under Windows 7, 23 Bit

       Visual Studio 2008 + SP1, C# and VB.NET

No graphic linking of operator control elements in Visual Studio .NET with the SIMATIC NET OPC data OCX

The graphic linking of operator control elements such as text boxes with OPC communication variables in the properties dialog of the SIMATIC NET OPC data OCX component is not possible with Visual Studio .NET. Operator control elements must be linked directly in the program code.

Use the new OPC Data .NET control, this restriction does not then apply.

 

Restricted data types in SIMATIC NET OPC data OCX in Visual Basic

The SIMATIC NET OPC data OCX in Visual Basic does not support the following data types of OPC items and VT_ARRAY arrays of this data type:

Data types: VT_I1 (CHAR), VT_UI2 (WORD), VT_UI4 (DWORD)

Instead, use the existing the automation data types, for example:
BYTE instead of CHAR, INT instead of WORD and LONG instead of DWORD.

Use the new OPC Data .NET control, this restriction does not then apply.

 

SEND/RECEIVE ISO connections and data packages of the "Expedited Data" type

If data packets of the "Expedited Data" type are transferred on a SEND/RECEIVE ISO connection, the receiving application at the PC must make sure that this data is actually accepted. Otherwise, the buffering of these data packets can lead to a lack of memory that can eventually cause the connection to be terminated.

This means that if you use a SEND/RECEIVE ISO connection with your OPC user program, a receive item must be activated on this connection.

 

S7 connection establishment when required takes longer during startup

In SIMATIC STP7/NCM PC, you can configure S7 connections to be established "when required".

The communication of the OPC functions is then established only when necessary which can cause the connection establishment to take longer and OPC reports errors during the start-up phase.

 

OPC symbol files: "\" in the symbol file folder name is not released

The "\" character (backslash) is not released for use in symbol file folder names for OPC symbols. Folders in OPC symbols can be defined in the OPC symbol file configurator or based on the station name in STEP 7.

 

OPC XML-DA: Product-specific error messages without error text

With product-specific error messages, no error text is returned with OPC XML-DA but rather the error number. Refer to the manual "Industrial Communication with PG/PC Volume 2" for the error text.

 

Waiting for the OPC server to finish

When you close all OPC applications or exit the OPC server using the "Configuration Console", exiting the underlying OPC server can take several seconds. Do not start any new OPC applications during this time and wait until the OPC server has finished. Exiting the OPC DA server can be followed in the Task Manager by monitoring the "opcdaservice" process.

 

OPC SEND/RECEIVE: Connection establishment timeout must be higher than 2000 ms

The "connection establishment timeout" parameter of the OPC server in STEP 7/NetPro, OPC property for ISO, ISO-on-TCP and TCP connections must be higher than 2000 ms.

 

OPC-S7 server can terminate itself when memory is exhausted

If there is no more free memory on the PC, the OPC-S7 server can terminate itself.

 

Memory requirements of the OPC server

When using configurations approaching the configuration limits, make sure that the OPC server has adequate free memory for managing data.

 

OPC SEND/RECEIVE: Optimization of FETCH/WRITE direct access variable services cannot be disabled

The configurable optimization of direct variable services for ISO, ISO-on-TCP and TCP connections of the type FETCH or WRITE cannot be permanently disabled.

 

OPC Data Access 3.0: MaxAge functionality has not been released

The OPC Data Access 3.0: MaxAge functionality has not been released If this functionality is used, data is always read from the IO device. This makes reading from the cache impossible.

 

Avoid other OPC calls in the OPC callback routines

Function calls with longer execution times should be avoided to prevent other callbacks from being delayed.

 

Use a local copy of the OPC RCWs for .NET-OPC-RCW programs

For .NET-OPC-RCW programs, a local copy of the OPC RCWs used must be copied to the folder of the application. This setting (local copy) for the OPC RCW references can also be made in the MS Visual Studio project of the OPC application.

 

Changing languages in ongoing operation

An OPC Alarms and Events application cannot make a language change as long as it still has active subscriptions. After closing all subscriptions, the language can be switched over.

 

Symbol File Configurator: Following CSV import, new symbol entries are not displayed

New symbol entries are not displayed following a CSV import. The imported values are only visible after closing and reopening the symbol file.

 

OPC DA: Time stamp 1.1.1601 for "OnDataChange" with BAD quality

With data change messages ("OnDataChange") with the quality OPC_QUALITY_BAD, a time stamp 1.1.1601 can be reported although a message with quality OPC_QUALITY_WAITING_FOR_INITIAL_DATA with an up-to-date current time stamp was returned earlier.

 

It was not possible to shut down all OPC servers

The command to shut down the OPC servers can be sent with the "Configuration Console".

Please note the following situations:

      In some situations, the entire communication is not terminated and lower-level processes continue to run.

      The fact that it was not possible to shut down all OPC servers is shown in the "Configuration Console". To shut down the entire communication, the system must be restarted.

 

OPC S7 symbol field elements are not displayed in OPC UA browsing
To ensure compatibility, OPC S7 symbol field elements are still displayed in OPC DA browsing.

 

OPC Scout V10: Only one OPC server per view tested and passed

Only one OPC server per DA and AE view has been passed during testing. Use multiple views for multiple OPC servers and, where necessary, adapt the update times for server and view specifically.

 

OPC Scout V10: While browsing the name space of an OPC DA server, if it shuts down, this is not displayed

While browsing the name space of an OPC DA server, if it shuts down, this is not displayed. In the workbook, the shutting down of an OPC DA server (if there is a IShutdown interface) is indicated by a special server icon.

 

Monitoring the connection to the XML DA server

The lack of replies to SubscriptionPolledRefresh or a reply with InvalidServerSubHandles indicates that the XML DA server is not available. Once this has been recognized, repeat subscription calls periodically (approx. every 5 s) until there is a positive response to the call. The XML DA server is then available again.

 

OPC Scout V10: Error states of an OPC XML DA server in the DA view

In the DA view of the OPC Scout V10, some error states of an OPC XML DA server are not detected and dealt with.

 

DA OPC Server: The RemoveItems() call is slow in the active group

The RemoveItems() call from the DA OPC server is slow within an active OPC group. Disable the group first or remove the group completely.

 

DA OPC Server: Individual RemoveItems() calls are not recommended in the active group

Individual RemoveItems( ) calls by the DA OPC server within an active OPC group are not recommended. If you want to achieve higher performance with a large number of items, disable the group first.

 

Symbol editor

If the high-speed PNIO OPC server (inproc) is configured, it is not possible to browse the PNIO name space in the "Add New Symbol" dialog of the symbol editor.

If you want to use this function, the normal PNIO OPC server (outproc) must be configured, for example by selecting several additional protocols.

 

OPC Scout V10: Long wait times and values holdup with slow response by the OPC server

With slow responses by the OPC server, for example, when the connection is interrupted or when browsing a namespace with tens of thousands of items per level or with multiple reads that have no connection to the device, you will have to expect correspondingly long wait times on the user interface. During this time, no input to the OPC Scout V10 is possible and monitored items are not updated.

Such wait times can also occur when writing or generating values. It must be taken into account that if there is an interrupted connection to a device, the values via error-free connections will also be delayed.

Generating values for all connection partners will sometimes be held up until the interrupted connection is restored. The values that were generated and accumulated up to this point will be written all at once when the connection is re-established.

 

OPC Scout V10: Use only up to 500 items, 500 array elements and 5 alarms/s continuously

The OPC scout has only been released for the use of up to 500 items, 500 array elements and 5 alarms/s continuously. If the number of items or array elements is exceeded and the alarms are received too quickly, there may be significant delays, inoperability or exceptions.  Exceeding the released limits must be prevented either by a suitable configuration by the user or a different client must be used.

 

OPC UA server: No deadbands

Deadbands are not supported in the version of the OPC UA server.

 

UA S7 OPC server does not support access to multidimensional arrays

Do not access multidimensional arrays, because the UA S7 OPC server does not support interpretation of this data.

 

UA S7 OPC server incorrectly allows lower update times than the configured cycle time

With the UA S7 OPC server, if the requested update time of a subscription, for example with OPC Scout V10, is lower than the cycle time of the S7 OPC server configured in STEP 7/HW Config, the lower update time is nevertheless confirmed.

 

Non-existent but configured symbol file prevents connection to the OPC server

A non-existent symbol file that is entered in the configuration prevents the connection being established to the OPC server. Connection establishment is rejected with an error message.

 

OPC Alarms & Events with OPC server 7.0 or earlier and OPC server 8.0 with unconfigured alarms: Event messages for non-existent alarms

If the Notify (SFB36) or Alarm (SFB33) alarms are already present when the connection from the OPC server to the PLC is established, alarms for signals 2 to 8 will be generated and must be acknowledged although they do not exist on this PLC. The OPC server 8.0 with configured alarms no longer reacts in this way.

 

S7 connection diagnostics items &connectionstate(), &connectiontype() and &hconnectionwaystate() are not released for COML S7 connections

The S7 connection diagnostics items &connectionstate(), &connectiontype() and &hconnectionwaystate() are not released for locally configured COML S7 connections

They exist for other S7 connections, however with COML S7 connections, they do not achieve the quality GOOD. This also applies to OPC UA S7 for the S7 connection diagnostics properties connectiontype, connectionstate and hconnectionwaystate.

 

In many places, the documentation still describes the OPC Scout prior to the CD 2008

The "Configuration Console" guidelines and "Commissioning PC Stations", "Industrial Communication with PG/PC" manuals in many places still describe the sample OPC Client OPC Scout in the version prior to CD 2008. The new OPC Scout V10 as of CD 2008 replaces the OPC Scout. As of CD V8.0, only the OPC Scout V10 is supplied. Working with the OPC Scout V10 is described in the relevant online help.

 

COML S7 - no synchronization with existing local addresses during import

When importing a COML S7 configuration, the remote S7 partner addresses it contains are not checked to establish whether or not they are the same as local addresses on the PC station. Avoid having the same addresses.

 

OPC S7: The data types DATE, S5TIMEBCD are not released

The OPC S7 data types DATE, S5TIMEBCD (OPC UA S7 date, s7tbcd) are not released, These are nevertheless accepted at runtime as value items or nodes and are even available in "New Definition" and S7 templates. If you use S7-ATI symbols, they are both mapped to the data type WORD.

 

OPC Scout V10: Changed user authentication types and computer names of an OPC UA servers are not detected automatically

The authentication types of an OPC UA server and its computer name are stored in a user profile and are re-used. If the authentication type or computer name of the OPC UA server changes, this is not detected automatically by the OPC Scout. The previous OPC UA server must be removed explicitly from the workbook and in the Server Explorer, rebrowsed for endpoints and relinked with a new user logon. As an alternative, the user profile can be deleted. A change to a certificate and identification of a user is detected, the user is then asked in a dialog whether or not the change is acceptable.

 

OPC Alarms & Events: Multilanguage alarm texts

The alarm texts, alarm sources and alarm areas can be made available to the OPC server in the default language of the STEP 7 project, restricted to the languages German (de-DE), English (en-US), French (fr-FR), Spanish (es-ES) and Italian (it-IT) and optionally in English as the second language. If the OPC client wants texts in a language that is not available to the OPC server due to the configuration, it supplies these texts in the default language or if the text is not available in this language in English (en-US). If texts are not configured, the OPC server generates a default text. OPC UA A&C is released only for the languages "de" (de-DE) and "en" ("en-US").

 

OPC Alarms & Events and OPC UA A&C: Multilanguage consistent naming of alarm sources and areas

The naming of alarms, alarm sources and alarm areas must be translated and used consistently in multiple language configurations. Otherwise, alarms and alarm areas may be incorrectly assigned. With certain filter settings, this can in turn mean that expected alarms are not forwarded to the OPC client. The following example illustrates the problem:

 

The table shows 5 alarms that were configured with different source and area information in German and English.

 

 

German (default language)

English (second language)

Problem

Alarm

Area\source

Area\source

 

Alarm1

Auto\Motor\Ölfilter

car\engine\oil filter

ok

Alarm2

Auto\Motor\Batterie

car\engine\power\battery

An additional level was introduced in the translation.

Alarm3

Auto\Motor\Ventil

car\fuel\valve

The name of the second area level was translated differently compared with Alarm1.

Alarm4

Auto\Kraftstoff\Ventil

car\engine\valve

The name (Kraftstoff) at the second area level has the same corresponding term (engine) as another name (Motor) in Alarm1.

Alarm5

 

car\engine\turbo

The alarm has not configured area information in the default language. The English translation is not empty.

 

During configuration, no consistency check is performed. Internally, the OPC server solves the inconsistencies in the table, which can result in the following hierarchy A of area and source names.

 

Hierarchy A: German (English)

Notes

Root

 

     Alarm5

 

     Auto (car)

 

          Motor (engine)

The term engine was the first (for example in Alarm1) match for Motor.

              Ölfilter (oil filter)

 

                   Alarm1

 

              Batterie (Batterie)

The additional level in the translation does not match and the German term is therefore used in English.

                   Alarm2

 

              Ventil (valve)

 

                   Alarm3

 

          Kraftstoff (Kraftstoff)

The corresponding term engine from Alarm4 is already being used for Motor. The German term is therefore used in English.

              Ventil (valve)

 

                   Alarm4

 

 

If the configured texts are evaluated in a different order, the following hierarchy B could also result.

 

Hierarchy B: German (English)

Notes

Root

 

     Alarm5

 

     Auto (car)

 

          Motor (fuel)

The term fuel was the first match for Motor (for example in Alarm1).

              Ölfilter (oil filter)

 

                   Alarm1

 

              Batterie (Batterie)

The additional level in the translation does not match and the German term is therefore used in English.

                   Alarm2

 

              Ventil (valve)

 

                   Alarm3

 

          Kraftstoff (engine)

The corresponding term engine from Alarm4 is already being used for Kraftstoff.

              Ventil (valve)

 

                   Alarm4

 

 

To avoid inconsistencies being resolved unexpectedly as shown above, there must be a 1 to 1 match between the terms in the different languages at each hierarchy level in the configuration.

 

OPC UA server: Case-sensitivity in names

Generally in OPC UA, names are case-sensitive. This includes connection names, alarm names, source and area names. The names must be written exactly as they were configured. Unconfigured alarm and diagnostics texts as well as source and area names are provided by the OPC server in lower-case letters and they must also be used as such.

 

S7 OPC UA server: Language for node identifier and the default language

The S7 OPC UA server decides the language used to form the node identifiers for area and source names of alarms according to the following rules. The language is then also the default language in which it supplies localized text if the client does not select a language.

1.       English, if the language setting English was selected as the first or second language for alarm texts in the STEP 7 project.

2.       Default language if the language setting default language was selected for alarm texts in the STEP 7 project.

3.       English, if no language was selected for alarm texts in the STEP 7 project. Default texts are then generated internally in English.

 

S7 OPC UA server with large number of alarms and conditions available only 50 s (or longer) following download

If you make use of the full released number of 5000 S7 alarms in German and other S7 alarms in English, and consequently with many alarms and conditions, the S7 OPC UA server will only be available after approximately 50 s (or longer).  If your client registers before this time has elapsed, the connection establishment (CreateSecureChannel) to the endpoint of the server will fail.

 

SIMATIC NET OPC DATA CONTROL for .NET only released with MS Visual Studio 2008

The data control for .NET is released only with MS Visual Studio 2008, Windows Forms and .NET Framework 3.5 and higher.

 

SIMATIC NET control elements OPCServerBrowser and OPCItemBrowser are not released for separate use

The SIMATIC NET control elements OPCServerBrowser and OPCItemBrowser for MS Visual Studio 2008 are not released for separate use. These control elements are intended for use within the OPC data control .NET OPCDAConnector.

 

Properties dialog of the OPC data control OCX is not released for MS Visual Studio 2008

The use of the Properties dialog of the OPC data control OCX is not released for MS Visual Studio 2008.

 

OPC server diagnostics only with OPC.SimaticNET with several selected protocols

The OPC server diagnostics (in the namespace under SERVER:) is available only with the server OPC.SimaticNET with several selected protocols (in "Configuration Console" ... Protocol Selection"). It is not available with the single protocol data access OPC servers such as OPC.SimaticNET.DP and OPC.SimaticNET.PD. It is also not available with OPC Alarms & Events servers.

The restriction applies also to OPC XML Data Access.

 

Without the IPv4 protocol, no remote nodes are found in the Windows network via NETBIOS

In a Windows network, nodes are ideally found using the NETBIOS functions linked to IPv4. If the IPv4 protocol of an Ethernet LAN connection is turned off, and the IPv6 protocol is active, no further nodes can be found using the NETBIOS search. This also applies to the browse functions in the namespace for remote OPC server in the OPC Scout V10.

 

PNIO UA OPC servers: Different data buffer of data record access via PNIOCOM: and PNIO:

The PROFINET IO UA OPC server uses different internal data buffers for data record access using the COM-compatible syntax with the namespace identifier PNIOCOM: compared with access using the UA syntax with the identifier PNIO:. If access is mixed, changes made in one syntax are not known in the other.

This also applies to simultaneous access to data records via the PROFINET IO COM Data Access interface.

 

COML S7 configuration does not support setting properties of the OPC server

The local COML S7 configuration in "Configuration Console" does not support any options for setting the properties of the OPC server such as cycle time for the S7 protocol. Default values, for example 100 ms for the cycle time are then used. If you want to adapt these parameters, you will need to use configured S7 connections and PC stations in STEP 7.

 

Once an OPC UA client certificate has lapsed, the cyclic renewal of the SecureChannel during ongoing operation is denied

Once the validity of an OPC UA client certificate has lapsed, the cyclic renewal of the SecureChannel is also denied in ongoing operation.

 

Connection diagnostics items only return one connection parameter for fault-tolerant S7 connections

With fault-tolerant S7 connections, the following connection diagnostics items for the S7 protocol return only one of the available connection parameters:

&cp(),

&remoteaddress(),

&remotesap() und

&localsap()

and S7 protocol for OPC UA

cp,

remoteaddress,

remotesap and

localsap

 

When enabling COML S7 connections, a previous S7 target symbol file remains selected

If a configuration with S7 symbols is downloaded to a PC station and then a local COML S7 configuration is enabled in "Configuration Console", the previously loaded S7 target symbol file remains selected. Disable this in "Configuration Console -> Manage Symbol File".

 

When COML S7 connections are enabled, restricted access rights for OPC items loaded previously with STEP 7 are retained

If a configuration with restricted access rights for OPC items was downloaded to a PC station and a local COML S7 configuration is then enabled in "Configuration Console", the previously downloaded access rights for OPC items are retained. To change these, the access rights must be reconfigured STEP 7.

 

OPC UA: IndexRange access to UA array elements is not released

Access via the IndexRange parameter to UA field elements of a node of the type array is not released.

 

First shut down relevant communication via OPC before exiting the OPC servers

Shut down any relevant communication with your plant via OPC, for example change your PROFINET IO devices to a safe state via the PROFINET IO OPC server before you exit the OPC servers in "Configuration Console".

 

The number of OPC UA clients/sessions is restricted to 50

The number of OPC UA clients or sessions for the SIMATIC NET OPC UA server communication is restricted to 50.

 

Locally configured alarm texts do not support browsing of the alarm name space

With locally configured alarm texts in the scores7.msg file for OPC servers <V8.0, browsing the alarm name space is not supported, configured ConditionNames are not displayed.

 

 

 

24.3    Note

 

Hidden message window of the Management Console

When you close the Management Console, and have not saved all the changes, a message window sometimes appears with the prompt "Do you want to apply the new settings?" after you have closed the main window.  The text in the title bar of the message window indicates the dialog in which you have not saved the last changes.

 

Assigning permissions for using symbol files with the OPC XML-DA Web service

The OPC XML-DA Web service uses other services to work with symbols. These services require adequate rights for access to the folders in which the STI or SSD symbol files are stored and for the files themselves.

Please make sure that the following users have "full access" to these files and folders:

 

Operating system

User
in a German operating system

User
in an English operating system

Windows 7

User "NETZWERKDIENST"

User "NETWORK SERVICE"

 

 

Assigning permissions for creating trace files of the OPC XML-DA Web service

The OPC XML-DA Web service uses the following additional services to create trace files:

·         under Windows 7, the network services

Please assign read and write permissions to these services for the folders in which the trace files will be stored.

 

Automatic resetting of the OPC XML-DA Web service

The Internet Information server can be configured so that it is automatically reset when certain events occur.

In Windows 7, the default for automatic resetting is after 29 hours operating time. Note the following:

·         This setting can lead to response delays.

·         Following each reset, active subscriptions are lost and must be sent again.

 

Error "0xC00481FF - E_SERVER_DOWN" when browsing

When browsing symbols using the OPC XML-DA interface, the error "0xC00481FF - E_SERVER_DOWN" occurs sporadically; please repeat your browsing.

 

Values when browsing without adequate privileges

When browsing a symbol file without the required permissions and with default prefix, the value "E_FAIL" is returned and without prefix, the value "S_FALSE".

 

OPC XML-DA server requires enabling of remote basic and OPC communication

If you want to use the OPC XML-DA server, you will need to click the Allow "remote basic communication and OPC communication" button in the "Configuration Console" program in "SIMATIC NET Configuration -> Applications -> OPC Settings -> Security".

 

Expanded OPC XML-DA Web service trace without adequate rights

Generally, the Web service writes its traces in two circulating files whose path can be specified with the "Configuration Console". If these files cannot be created or written to due to an error, for example inadequate access rights, a context trace entry is generated. This is only possible if the following entry is made in the configuration file "<installationpath>\simatic.net\opc2\binxml\web.config":

<trace

enabled="true"

requestLimit="10"

pageOutput="false"

traceMode="SortByTime"

localOnly="false"

/>

With the instruction >enabled="true"<, the trace is always enabled.

With >pageOutput="true"<, the trace can also be displayed automatically on the first page of the Web service in Debug mode.

The context trace is an online trace provided by the Web service as long as it is running. It can be displayed with any browser, for example the Internet Explorer.

To achieve this, "Trace.axd" instead of the start page "SOPCWeb.asmx" is simply appended to the corresponding virtual directory, for example http://localhost/OPC.Simatic.NET/ Trace.axd.

 

OPC XML Web service "RequestOptions.ItemPath”

If parameter "RequestOptions.ItemPath" is set to "true" or "false", the ItemPath in the path is returned and not zero.

 

The "SIMATIC NET Core Server" services are logged in the Event Viewer

Starting or exiting the "SIMATIC NET Core Server" OPC protocol services is logged as information in the Event Viewer of the operating system under System. This is a system property. Remember that the Event Viewer can only hold a limited number of entries.

 

PROFINET IO OPC server: Cycle time must not be the same as the protocol call rate

The configured cycle time of the PROFINET IO OPC server is not automatically the interval at which the underlying PROFINET IO protocol interface calls are made. Depending on the required update rate of an OPC client, the call rate can also be slower.

 

Improved performance with group calls when reading and writing

If you use group calls instead of individual calls one after the other when reading and writing OPC items, it is possible to improve throughput considerably since the OPC server can often achieve an internal optimization. Conversely, loss of performance can be expected if you use lots of individual jobs at short intervals.

 

Configuration Console: Option "Use as target for S7 symbol download" not enabled

If the option "Use as target for S7 symbol download" is disabled, downloading symbols from STEP 7 causes an error entry in the diagnostic buffer of the Station Configuration Editor and the OPC server changes to "Stop". If you have configured S7 symbols, enable this option.

 

Configuration Console: OPC protocol selection with symbols

As of SIMATIC NET V6.3, OPC symbols can be used without protocols activated in the OPC Protocol Selection. One use case is to use symbols to provide a restricted address space with restricted access permissions. The symbols can also be used with more than one selected protocol regardless of the type. The selected protocol (or protocols) is/are then displayed in the name space. If only one protocol is selected, the activate configuration is more efficient; only the selected protocol can be used in the symbols as previously.

 

Differing access permissions with the OPC methods "ValidateItem" and "GetProperties”

If different access permissions are specified for symbolic items in the Symbol File Configurator from close that actually exist, the actual permissions are returned when the access permissions are queried using the "ValidateItem" OPC method. The "GetProperties" method returns the permissions assigned in the symbol file.

 

Updating RCWs in .NET applications

With new versions of the "SIMATIC NET, PC-Software" CD, new versions of the custom interface for .NET (Runtime Callable Wrapper (RCW), OpcRcw.Da, OpcRcw.Comn) are supplied by the OPC Foundation.

Please note: If you have not used a local copy of the previous .NET-RCWs in your application, you must recompile your program.

 

Configured default priority per EventID for alarms before configured priority in instance data block before alarm block message severity before generally configured default priority

With the OPC Alarms and Events server "OPC.SimaticNetAlarms" and "OPC.SimaticNet.AE" and the OPC UA S7 server, S7 alarms with severity can be received. These alarms can be configured in STEP 7/NetPro in the S7 connection properties of the OPC server and in the corresponding instance data block. Note the following:

The configurable default priority for alarms per EventID overrides the S7 priority configured in the instance data block (as of OPC servers 8.0, this cannot be configured for OPC servers 7.0 or earlier).

The S7 priority configured in the instance data block (as of OPC servers 8.0, this cannot be configured for OPC servers 7.0 or earlier) overrides the programmable alarm severity of a block ALARM, ALARM_8P or NOTIFY in an S7 program.

The programmable alarm message severity of an ALARM, ALARM_8P or NOTIFY block in the S7 program overrides the general, non EventID-specific configurable default priority for alarms.

Priorities should be configured according to the grading above for alarms without programmed severity such as ALARM_S and ALARM_SQ.

 

OPC security settings when changing domains

In the "Configuration Console", the OPC security settings for the Windows Firewall and DCOM can be enabled. Note that the settings for the Windows Firewall and DCOM configuration depend on the Windows logon. If, for example, you subsequently enter the PC in a Windows domain, the OPC security settings for the Windows Firewall and DCOM must be enabled again in the "Configuration Console".

 

New SEND/RECEIVE receive data item with OnDataChange callback even without a data change

New SEND/RECEIVE item:

"SR:[<connectionname>]receivedata{,subarea_address}{Itemattribute}"

Functionally, the item corresponds to the previous receive item with the following difference: When an item of this type is active, new data is signaled even if the content has not changed. This makes it possible for a client to receive both changed and unchanged data buffers sent by the partner. This is, however, not OPC-compliant. The OnDataChange callback is also no faster than the negotiated update rate. You should therefore always set update rates faster than the send rate of the SEND/RECEIVE data.

 

New DP SlaveXXRestart item for restarting DP slaves

New DP item:

"DP:[<devicename>]SlaveXXSlvRestart"; data type: VT_BOOL, write access only.

Slaves can be restarted with this new DP item; in other words, deactivated and reactivated with one item. The two function calls are made at an interval corresponding to the configured cycle time; possible values:

·         Write "True": restart slave XX.

·         Write "False": no function (return value: value range error).

 

No CSV import of EUHi and EULo values in exponential representation

Values in exponential representation for the relative deadband high and low limits "EUHi" and "EULo" cannot be adopted in the Symbol File Configurator with a CSV import. Do not use and high numbers in exponential representation. The only important value for the OPC deadband function, in any case, is the difference between the EUHi and EULo.

 

OPC XML-DA: Slower performance with a large name space

Function calls over OPC XML-DA do not depend on previous calls. Prior results are not buffered. This means that the entire name space must be searched again for every call, individual calls are therefore slowed down depending on the size of the name space. For cyclic reading, we therefore recommend the use of subscriptions so that the name space does not need to be searched for every query.

 

Extended range of values for quality

The range of values for the quality of an item has been extended. In particular for data that has not yet initialized, the quality OPC_QUALITY_WAITING_FOR_INITIAL_DATA (0x20) can be returned when reading. Please remember this when creating OPC applications.

Prior to evaluation, mask the returned value for the quality with OPC_QUALITY_MASK (0xc0) if you are only interested in the following quality values:

·         OPC_QUALITY_GOOD (0xc0)

·         OPC_QUALITY_UNCERTAIN (0x40)

·         OPC_QUALITY_BAD (0x00)

 

Extended project engineering from OPC server V6.4

The OPC server V6.4 has been extended by the following functions:

·         The EU values for symbols set by SIMATIC STEP 7/NCM PC are supported when the symbols are downloaded.

·         If the "Maintain connection permanently" option was selected in SIMATIC STEP 7/NCM PC, an immediate response is possible when interrupted connections are detected (see option "Immediate response when interrupted connection is detected"):

- On S7 connections

- On SEND/RECEIVE connections with the FETCH or WRITE jobs.

 

Improved value range checks when writing OPC items

The value range check when writing OPC items has been improved.
Values outside the valid range are rejected with an error message.
Example: Writing -127 to an unsigned byte item (range of values 0 through 255) is not possible.

 

OPC XML-DA: .NET Framework 1.1 clients should use localized times

.NET Framework 1.1 clients should use localized times.
The OPC XML-DA server then converts these to UTC time. Only as of .NET Framework 2.0, is it possible to distinguish system DateTime variables between local and UTC time representation using the "Kind" property.
If possible, use .NET Framework 3.5.
.NET Framework 1.1 clients should transfer local times; the UTC time can be obtained from the reply time of the "GetStatus Response" function. This is calculated as UTC time in the OPC XML-DA server.

 

New error codes if "Immediate response when interrupted connection is detected" is configured

For the S7 protocol, the additional error codes  0x85270206L and 0x05270206L have been introduced with the meaning "no connection to the S7 communication partner, immediate error return configured".

For the SEND/RECEIVE protocol, the additional error codes 0x85270301L and 0x05270301L have been introduced with the meaning "No connection to the SR communication partner, immediate error return configured".

 

OPC XML-DA server: Correction for variables of the "dateTime" type

If an OPC client writes variables of the type "dateTime", the OPC XML-DA server converts the values of the variable to UTC time and forwards them in this form.

When they are read, the variables are interpreted as UTC time by the OPC XML-DA server, converted to local time and forwarded.

If you want to correct the values of the variables on the OPC client, the following conversion can be made. This is suitable for C# or VB.NET.

"dt" is the value of a variable of the type "dateTime".

·         Correction before writing the value "dt" of client in partner device:
dt = dt.Add(dt.Substract(dt.ToUniversalTime( )))

·         Correction after reading the value "dt" from the client:
dt = dt.Subtract(dt.Subtract(dt.ToUniversalTime( ))

 

A change in the configuration may require a restart on the computer

If components involved in a configuration change are still being used, it is possible that the Station configuration Editor reports the still active components and proposes a computer restart.

If the component is still active during a repetition, exit the remote OPC client programs and OPC servers that access the computer using DCOM. If necessary, disable the automatic startup of OPC client programs before the restart.

As soon as the configuration changes have been made following the restart, the automatic startup of OPC client programs can now be enabled again. All programs that were previously exited, can be started again.

 

Possible language mixtures on the OPC interface

Remember that a mixture of languages can occur on the OPC interface when the operating system language and installation language differ from the language requested on the OPC interface ("localeID"). This becomes noticeable, for example, when reading and writing the data types VT_R4, VT_R8 and VT_DATE in string format:

Examples of mixed languages:

1.) Writing on a German system with an English "localeID".

VT_R4: "1,0"German, despite English "localeID"; in this case a comma instead of a period.

VT_DATE: "30.11.2006"German despite English "localeID".

2.) Reading on a German system with an English "localeID".
VT_R4: "1.0"
VT_DATE: "11/30/06"

 

Updating of time stamps in OPC PROFIBUS DP

During DP communication with communications processors (CP 5613 or CP 5614), when reading over OPC, the time stamp never changes unless the values have changed (applies to both inputs and outputs).

SOFTNET DP (CP 5611 A2, CP 5621 and CP 5711) supplies new time stamps for inputs (updated as a result of reading), however, not for outputs.

 

Close OPC clients before making project engineering and configuration changes

Prior to making any project engineering or configuration changes, please close your OPC clients. Start the OPC clients only after completing the changes, for example, XDB import in the Station configuration Editor.

 

Changed startup on the OPC DA server

When activating OPC groups with items, the OPC server can initially only return the quality OPC_QUALITY_WAITING_FOR_INITIAL_VALUE (= 0x20) with data values of the type VT_EMPTY. This behavior is in compliance with the standard, however, an OPC client should be in a position to handle this returned information. Please check your existing OPC clients to see whether adaptations are necessary.

 

Adapting the OPC job timeout of SR and S7 connections to the communication load and CPU usage

Please adapt the OPC job timeout of SR and S7 connections to the communication load and CPU usage. If you are unsure, use the default settings.

 

If you have a large configuration, select a higher job timeout

With a large configuration (approximately 10,000 items) not only the communication delay on the network but also the processing time for OPC jobs on the OPC servers becomes relevant. You should then select higher job timeouts of approximately 15 s for 100 000 items, to avoid connection aborts due to the configured job timeout being exceeded.

 

Asynchronous OPC jobs not executed deterministically

Depending on the available operating system resources and delay time on the network and on the partner device, multiple consecutive asynchronous OPC jobs are executed almost simultaneously. One job overtaking another is perfectly possible, the practically simultaneous accesses do not keep to any deterministic order. An OPC client must take this behavior into account.

 

Select cycle times for the OPC server that are significantly shorter than the monitoring times

The cycle time configured in SIMATIC STEP 7/NCM PC for the various protocols of the OPC server should be selected so that it is significantly shorter than the shortest configured monitoring time (recommendation: at least a factor of 5).

 

IOPCBrowse::Browse: The ContinuationPoint loses its validity after browsing further at a different level

The OPC-DA-3.0 feature, IOPCBrowse::Browse" always returns a ContinuationPoint other than the zero string when there are other elements at the relevant browsing level. This ContinuationPoint must be specified when continuing to browse the next elements of the level. If, however, you have browsed a different level in the meantime between calling the function the first and second time, the previously obtained BrowsingPoint loses its validity and cannot be used to browse further elements.

 

Write-protected symbol files cannot be used

STI and SSD symbol files cannot be used if the "write-protected" attribute is set.

 

Assigning permissions for using symbol files with the DA OPC server

The DA OPC server uses other services to work with symbols.

These services require adequate rights for access to the folders in which the STI or SSD symbol files are stored and for the files themselves. Make sure that the "interactive" or "configured" users have "full access" to these files and folders:

 

OPC DA 3.0: OPCBrowseServerAddressSpace::BrowseProperties( ) also reads from IO devices

Note that the OPC DA 3.0 method "IOPCBrowseServerAddressSpace::BrowseProperties( )" also reads properties and data values from IO devices.

If the IO device is unobtainable, the method call can take a long time.

 

PROFINET IO OPC server: Precise length information for addressing

Remember that with simple addressing, reading and writing of PROFINET IO data requires the precise configured length information (with advanced addressing, subaddressing is also possible).

Example:

An IO module with a length of 4 bytes can only be partially read via an OPC item PNIO:[CTRL1]EWORD0 (2 bytes).

The following are, for example, permitted: "PNIO:[CTRL1]IB0,4" or "PNIO:[CTRL1]IDWORD0".

 

Programming recommendation: Implement exception handling for OPC interfaces

We recommend that you implement exception handling for OPC applications (try {... IOPCServer:: ...} catch(exception){...} ) to cover exceptions as can occur when shutting down the OPC servers.

 

OPC XML DA: Allowing remote OPC communication necessary

To work with OPC XML DA, allow remote OPC communication in the security settings in the "Configuration Console" program.

 

OPC XML DA: Writing DateTime variables in unspecified format

Writing DateTime variables in unspecified format is not permitted.

 

Symbol files with prefix simplify the name resolution

For OPC symbols, it is possible to use several symbol files that differ from each other in the prefix. The first symbol file in the list has no (or an empty) prefix.

In OPC, a symbol must be assigned directly to the symbol files or the various protocols (S7:, DP:, PN:, ...). If a symbol file without a prefix is used, this assignment can take longer since it is necessary to search through all possible protocols. To simplify this search, you should only use symbol files with a prefix, since the assignment between prefix and symbol file is unique for these symbols.

 

OPC DA: Monitored data changes can be old

Monitored data changes (OnDataChange) can be old until the confirmed update interval (RevisedUpdateRate) because data is read cyclically on the OPC server and in the underlying communication protocol of the PC station according to the update rate.

If the communication protocol signals new values to the OPC server shortly after a message has just been sent to the OPC client by the OPC server, this new value can only be signaled to the OPC client after the update interval has expired.

 

Differences between written and read values in DPC2 data records

A written value of an OPC DPC2 data record item cannot be read out identically using the same item or an item with the same address, slot and index. There may be device-specific differences in DPC2 data records between the written and read value.

 

No S7 connection termination after exiting the OPC clients with the OPC UA protocol activated

If the OPC S7 server is operating, for example permanently if the OPC UA protocol is active, S7 connections via OPC itself are not terminated if the OPC client deregisters the corresponding items. The S7 connection is terminated only if the option "Automatic termination after e.g. 60 s" is configured in NCM.

Alternatively, if not required, disable the OPC UA protocol.

 

With the OPC UA PROFINET IO protocol activated: PROFINET IO controllers in OPERATE only with the first registered OPC UA client

If OPC UA for the PROFINET IO protocol is enabled, a configured PROFINET IO controller for the OPC server changes to OPERATE mode as soon as the first OPC UA client is registered with the OPC UA PROFINET IO server. If no OPC UA client has connected, for example after starting up the computer, a configured PROFINET IO controller for the OPC server remains in OFFLINE mode.

 

If the OPC-UA S7 protocol is activated: Permanent S7 connection establishment only with the first registered OPC UA client

If OPC UA for the S7 protocol is enabled, permanent configured S7 connections are established as soon as the first OPC UA client is registered with the OPC UA S7 server. If no OPC UA client has connected, for example after starting up the computer, no permanent S7 connections will be established.

 

Access permissions for symbolic items

The access permissions for symbols can be selected freely. These permissions are displayed when browsing. When accessing the items, these permissions may be further restricted by the OPC server.

Example: A symbol for peripheral output is defined with write/read permissions.

When it is accessed, however, only writing is permitted since the system does not allow peripheral outputs to be read.

 

UA OPC server: Relationship between cycle time and update time

The update rates used by the UA OPC servers for SIMATIC NET are multiples of the cycle time configured for the S7 protocol (or the fixed default value of 100 ms for COML S7 connections). The shortest possible update time is the cycle time.

 

OPC Scout V10: Only suitable data types can be written

The data type of the value to be written, must match the read data type of the OPC item. If no usable data type is returned by the item, for example, VT_EMPTY, it is not possible to write to this item with the OPC-Scout V10.

 

OPC servers retain items that have been used in work memory

The COM DA, XML DA and UA OPC servers retain items that have been used in work memory. This memory is released again only after exiting the OPC servers.

 

OPC: Procedure for avoiding connection aborts

As a general rule, all configuration parameters, in particular timeout times, cycle time, alarms, must be matched up with each other depending on the plant configuration (hardware and software), the configuration limits and the way the client and other active applications work.

If the job timeout times are too short, this can result in connection aborts if larger jobs are sent at the same time by COM or UA clients, for example, when initializing, reading, writing, enabling and disabling larger amounts of items.

 

In the SNMP agent, set the maximum reaction time with which the SNMP agent replies to a query from the SNMP client.

 

- This is specified in milliseconds (ms)

- Range of values : 50 to 60000

- Default value: 9000 (9 s)

 

Where possible, select a timeout value (default 9000 ms) that is higher than the update rate (for example 500 ms) by a factor of 10 on the OPC client display unit. The update rate should be higher than the cycle time of the OPC server (default 100 ms) by a factor of approximately 5. 

If you are using a large number of SNMP devices (for example 100) each using approximately 100 OPC items, the timeouts should be increased to the highest setting of 60 000 ms. The update rates should be increased to approximately 5000 ms. The cycle time of 100 ms can be kept.

 

High handle usage of the UA S7 OPC server

The UA S7 OPC server uses a maximum of one event handle of the operating system per used "MonitoredItem". During operation, the number of these handles can therefore rise to the number of used items.

 

Programming manual "Industrial Communication with PG/PC Volume 2 - Interfaces, Release 9": Errors in the syntax and in some to the examples for the UA S7 OPC server in Sections 2.6.9.2 and 2.6.9.3 (buffer-oriented services)

·         Page 144: Syntax for "bsend"
incorrect (period (".") instead comma (",") between "buffer length" and "address":
< c o n n e c t i o n n a m e > . b s e n d < r i d > .
< b u f f e r l e n g t h > . < a d d r e s s > {
Correct:
< c o n n e c t i o n n a m e > . b s e n d < r i d > .
< b u f f e r l e n g t h > , < a d d r e s s > {

·         Page 145: Example of "brcv" (period (".") after BRCV instead no period)
incorrect: S7-OPC-1.BRCV.1.10,X4,78
correct:    S7-OPC-1.BRCV1.10,X4,78

·         Page 146: Example (period (".") after "16" instead comma (",") and "D" instead "DW")
incorrect: S7-OPC-1.BSEND1.16.2,D
correct:    S7-OPC-1.BSEND1.16,2,DW

·         Page 146: Example (period (".") after "32" instead comma (","))
incorrect: S7-OPC-1.BSEND1.32.20,R,2
correct:    S7-OPC-1.BSEND1.32,20,R,2

 

Remote UA OPC server mode requires IP name resolution

The IP name resolution of the remote computer name must work to allow use of the remote mode of a UA OPC server.

You can test this with the ping function in a command console.
If the name cannot be resolved, check in the Windows Firewall, to see whether "File and Printer Sharing" is permitted as an exception.

The name resolution in the <system folder>\system32\drivers\etc\hosts file can also be achieved by assigning the reachable remote IP address to the remote computer name.

 

An incorrect number of items causes an access violation

The COM DA AddItems() or ValidateItems() call with less items than specified in the number of items parameter causes an exception (0xC0000005 access violation) in the lower-level operating system file RPCRT4.dll when accessing the high-speed inproc DP-OPC server OPC.SimaticNET.DP. Avoid such parameter assignment errors and provide an exception handling routine in the user program to deal with the exception.

 

S7 diagnostics items &connectionstate() and &connectiontype() only GOOD when connection established

The S7 diagnostics items &connectionstate() und &connectiontype() achieve the quality GOOD only after successful S7 connection establishment. Only then can the values be used.

 

OPC UA S7 namespace identifier 1 without computer name

The OPC UA S7 namespace identifier for NamespaceID 1 is unique without the computer name as of CD V8.0 thanks to the use of a GUID. Up to now, the value <hostname>.Siemens.Automation.SimaticNET.S7 was used as the namespace identifier for NamespaceID 1. As ServerName OPC.SimaticNET.S7@<hostname>. To be less sensitive to renaming the computer, as of CD V8.0, the unique identifier 1 urn:Siemens.Automation.SimaticNET.S7:{GUID}, (also as ServerURI), and the ServerName OPC.SimaticNET.S7 are used. Remember this modification on your OPC UA client.

 

OPC Scout V10 DA view and AE view for COM servers: No automatic reconnection after OPC server IShutdown and restart

In the DA view of an OPC Scout V10 workbook, items of several OPC COM servers can be monitored and even values generated. If one of these connected OPC servers is shut down and reports this via its IShutdown interface, this status is indicated by a special icon for this OPC server, the monitored items belonging to it are displayed as BAD. Other items of other OPC servers continue to be monitored and values continue to be generated. If the OPC server that was shut down is started up again, the DA view of the OPC Scout V10 does not reconnect. Reconnect the OPC server involved yourself; stop and restart monitoring and value generation of the DA view again because this registration is not automatically renewed.

 

OPC Scout V10: Item properties: DWORD integers "0" are displayed as a floating point number "0.0000"

In the Item properties tab of the Server Explorer of the OPC Scout V10, "0" item values of the OLE data type integer DWORD (unsigned 32-bit) are displayed as a floating point number "0.0000" because the OPC property item value is registered as Visual Basic data type (automation data type) double (floating point number double precision).

 

Self-issued OPC UA certificates are indicated as not trustworthy

OPC UA certificates are not indicated as trustworthy by the Windows certificate management if they were self-issued and not stored in the trustworthy storage folder. The SIMATIC NET OPC UA certificates are self-issued at the time of installation and stored in the "UA Applications" storage folder and in Windows 7 in the hidden path in the file system :<system drive>:\ProgramData\Siemens\OPC\PKI\CA\Certs\. The Windows certificate management also indicates this as untrustworthy.

 

Sample programs for OPC UA

Good starting points for creating your own OPC UA DA and Alarm & Conditions C# clients for -.Net are

 

1.       for DA: OPC UA SDK 1.00 DataAccess Quickstart and

2.       for Alarms & Conditions OPC UA SDK 1.00 AlarmConditions Quickstart.

 

Both can be downloaded by corporate members at www.opcfoundation.org.

 

These programs have two operating modes. The "Use security" mode must be called with opc.tcp://computername:4845. After the first call, the error message "Could not open UA TCP request channel" appears. After closing the client, the "Data Access Client" or "Alarm Condition Client" certificate can be enabled with accept in the "Configuration Console" in the OPC UA Certificates tab. The client can then be restarted. The "Use Security" mode will now work.

 

The mode without "Use Security" can only be used if the OPC UA Server "opc.tcp:\\pipe\localsS7" was previously disabled. To do this, you need to remove the following entry from the file C:\ProgramData\Siemens\SIMATIC.NET\opc2\binS7\ScoreS7.xml:

<UaEndpoint>

<SerializerType>Binary</SerializerType>

<Url>opc.tcp:\\.\pipe\locals7</Url>

<SecuritySetting>

<SecurityPolicy>http://opcfoundation.org/UA/SecurityPolicy#None</SecurityPolicy>

<MessageSecurityMode>None</MessageSecurityMode>

</SecuritySetting>

</UaEndpoint>

 

The UA server is now stopped by "Configuration Console" and then restarted. This mode also works now.

 

OPC S7 UA A&C: Shower of alarms if the connection to S7 aborts

OPC S7 UA A&C behaves differently from OPC S7 A&E if there is a connection abort. If there is a connection abort, OPC S7 A&E does not generate any alarms except for the Statepath alarms. If there is a connection abort, OPC S7 UA A&C, however, generates an event with StatusCode=0x80310000 (OpcUa_BadNoCommunication) for every configured alarm. If you use the full range of 5000 configured alarms, your application must be able to process the shower of 5000 events. If you do not want this to happen, then use suitable filter conditions.

 

S7 associated values in alarm text %Y of the type DateAndTime: Without an additional language identifier, the date is English for a German client

In the configured alarm texts for S7 alarms, associated values of the type DateAndTime can be inserted by specifying %Y. The DateAndTime value is then always formatted in English, for example "12/24/2010 2.59:59 PM". If an additional language identifier corresponding to the Win API function setlocale followed by "#", in other words, %Ydeu# or %Yeng# is specified, the formatting can be made language-specific. Even more detail can be specified by adding the formatting of the Win API function strftime, in other words %Ydeu#%H:%M:%S.

The syntax is in BNF notation:

 

<associatedvalueformatdate>:=   "%Y"|"%Y"<localesetlocale>|

            "%Y#"<formatdatestrftime>|"%Y"<localesetlocale>"#"<formatdatestrftime>

           

<localesetlocale>:=        language string corresponding to C function setlocale

<formatdatestrftime>:=   format string corresponding to C function strftime with expansion %s

 

List of data blocks is only read out once from the S7 device after connection establishment

When browsing the OPC S7 namespace of S7 connections, the existing data blocks are listed as a separate branch. To reduce load, the list of data blocks is only read out once from the S7 device after connection establishment.

 

UA certificate management: first delete previous certificate before a new certificate can be accepted from the same client

If a remote UA client certificate has already been accepted in the UA certificate management in "Configuration Console", no further certificate can be accepted from the same client and domain. First delete the previous certificate; the new certificate can then be accepted.

 

Configurable S7-OPC Alarms-und-Events alarm texts in local text file "scores7.msg" for OPC servers < V8.0

For OPC servers < V8, configurable multiple language S7 OPC Alarms and Events message texts can still be entered in the local text file "scores7.msg" in the following hidden path in the file system

Windows 7:

<Systemdrive:>\ProgramData\Siemens\SIMATIC.NET\opc2\bins7

Use the syntax description and the examples in the comments in this file.

Example of an English (LCID=1033) alarm text for the alarm event ID "200" of the S7 connection "S7-Connection_01":

[S7-Connection_01]

ALARM200=0,1033,"Message text for ALARM200, neutral and US language"

The value "DatabaseMessages=<path to 'scores7.msg'>" must also be entered in the "Protocol" section of the "scores7.ini" file.

Path to Scores7.ini:

Windows 7:

<Systemdrive:>\ProgramData\Siemens\SIMATIC.NET\opc2\ini

 

Remember that the values for the SOURCE and CondtionName pair must be unique.

 

With the SuppressUnusedMessages=1 parameter setting in the global section of the "scores7.msg" file, only the alarms configured in the scores7.msg file are forwarded. This parameter therefore represents a flexible and configurable filter for unwanted alarm messages.

 

As of OPC servers V8.0, alarm texts can be configured and downloaded in STEP 7 V5.5 or higher. As of OPC servers V8.0, configuration with the local alarm text file "scores7.msg" is no longer released.

 

 

 

25.           Notes on license keys

 

The basis on which the software on this "SIMATIC NET, PC Software“ CD is used are the following "General Conditions for Use of Software" of Siemens AG

·         Within the Federal Republic of Germany
The "General Conditions for Use of Software Products for Automation and Drives Engineering" apply to licensees with offices registered in Germany.

·         For the export market
The "General Conditions for Use of Software Products for Automation & Drives" apply to licensees with offices registered outside Germany.

 

 

25.1    Trial mode

 

As long as no other license to use this software has been obtained, this software only runs in its trial mode. The user is granted a non-exclusive and non-transferable license for the program in trial mode. The end user is not entitled to copy, pass on or distribute this software. Furthermore the end-user is not entitled to decompile or modify the software or to link it into other programs. The use of this software in its trial mode is at the end-user's own risk. Since the software in the trial mode is distributed free of charge, the authors are only liable in case of intent or gross negligence. The software is provided "as is" without any representation or warranty of any kind either expressed or implied including but not limited to implied warranties for merchantibility or fitness for use.

 

AS LONG AS THIS PROGRAM ONLY RUNS IN ITS TRIAL MODE, IT IS ONLY MEANT TO BE AN EXAMPLE OF THE FULL VERSION OF THE PROGRAM. IT IS NOT MEANT TO BE USED IN CONNECTION WITH LIVE MACHINE OPERATIONS. ANY SUCH USE IS AT THE USER'S OWN RISK.

 

 

25.2    USB key stick

 

(Does not apply to the product CP 5613/CP 5614 (DP‑Base))

You require a USB key stick for each of the SIMATIC NET software products. This contains one or more license keys required to operate the product. A USB key stick can also contain license keys for several products. During installation, these keys are transferred to the hard disk of the destination system. The products cannot be operated normally without license keys. In emergencies (loss of the USB key stick), the software can be operated and messages are displayed indicating the absence of the license. If a fault or error occurs (problem with USB key stick), please contact our Customer Support, Tel.: +49 (0)911 895 7222, Fax: +49 (0)911 895 7223, via Email www.siemens.de/automation/support-request

 

 

25.3    Important notes on handling USB key sticks and license keys

 

Note the following:

·         It is not possible to make a backup of the USB key stick.

·         The license keys are stored in the hidden folder "\ax nf zz" on the drive you specified during installation.
Do not delete the "\ax nf zz" folder or any files it contains.

·         It is not possible to transfer the license keys by simply copying them from the hard disk to a USB key stick or from the USB key stick to hard disk..

·         If you uninstall SIMATIC NET products with an uninstaller that uninstalls programs in Windows, you may lose the license keys.
If you want to uninstall these products with the uninstaller, you must first transfer the license keys back to the USB key stick. Use the "Automation License Manager" program for this. If you do not remove the licenses, the uninstaller may destroy the license keys for these products.

·         If you want to reformat your hard disk, you must first transfer the license keys back to the USB key stick using the "Automation License Manager" program (Start menu Start ->... -> SIMATIC -> License Management -> Automation License Manager, alternative: link on desktop). Otherwise the license keys will be lost and you will no longer be able to use the products. When you transfer the license keys back, make sure that you insert the same USB key stick from which you originally installed them.

 

 

25.4    Installing and uninstalling license keys at a later point in time

 

Make sure that you transfer the license keys back to the original USB key sticks.

 

Uninstalling license keys

You can uninstall license keys at any time with the "Automation License Manager" program.

Follow the steps outlined below to transfer (uninstall) license keys from the hard disk to the USB key stick(s):

·         Insert the USB key stick in a USB interface.

·         Open the "Automation License Manager" from the Start menu (Start -> ... -> Simatic -> License Management -> Automation License Manager, alternative: link on Desktop) and transfer the license keys back to the USB key stick.

 

Transferring UCL license keys

To transfer the UCL license keys to the PC, please use the "setup.exe" program on the UCL license key CD.

 

Retransferring license keys

To transfer license keys from the hard disk back to the USB key stick under Windows, please use the Automation License Manager installed from the "SIMATIC NET, PC Software" CD.

 

 

 

26.           Requirements and restrictions relating to hardware in general

 

Where the CP 5613 is referred to below, this relates to the communications processors CP 5603, CP 5613 FO, CP 5613 A2, CP 5614 A2, CP 5623, CP 5624 unless specific types are named explicitly. CP 5613 (without A2), CP 5614 (without A2) and CP 5614 FO are no longer supported.

 

 

26.1    Note

 

Using ACPI (standby and hibernation mode)

ACPI (standby and hibernation mode) is not supported. The "Energy saver" or "Sleep" buttons under the Start button must also not be used. This also applies to corresponding key functions on the keyboard or on the housing. If there is a change to "Power saving" or "Sleep", then depending on the hardware configuration, it is possible that the PVC will no longer wake up.

 

Preventing a change to sleep mode

When communicating via a SIMATIC NET module, your computer should not go to sleep mode automatically. To prevent the sleep mode, disable "Sleep" in the current profile:

·          In the Start menu, select Start -> Control Panel -> Hardware and Sound -> Power Options and check whether  the parameter  "Power save“ is set to "Never"  in the current profile.

·          Change the module to configured mode.

·          Reject hibernation in your application.

 

If your PC has already been changed to the sleep state, it must be restarted with a reset (press the On/Off button for approximately 10 seconds).

 

Power saver mode not allowed

The power saver mode is not allowed when working with the "SIMATIC NET, PC Software" CD. The current profile is therefore adapted by the installation.

If you go to the "Power Options" menu in Vista or Windows 7, (Start menu Start -> Control Panel -> Hardware and Sound -> Power Options) and change to a different power saving profile or reconfigure your PC's power saving mode, change the settings so that your PC does not change to power saving mode after a longer period of inactivity ("Change plan settings" -> set the power saving mode to "never").

 

A single service for which the Station Manager waits during startup was not started.

The following error entry may be found in the diagnostics of the Station configuration Editor:
"1 service(s), which the Station Manager waits for when it starts up was (were) not started."
This entry means that a function that must be processed before the Station Manager starts is not yet complete.

This function might be the plug-and-play manager of the "SIMATIC NET, PC Software" CD that looks for new hardware. If it is the plug-and-play manager, you can ignore the entry. This is then simply a delay and not an error. To check whether the plug-and-play manager is still running, follow the steps below:

Check the status of the service "SIMATIC NET P&PManager" in the services in the Control Panel of your operating system . If the status is still "Starting", the search for new hardware is not yet complete.

 

Removing communication modules in configured mode

Communication modules (CPs) in configured mode (including PCMCIA, PC cards or USB) must not be removed from the PC during operation; this also applies to the information area of the Start bar of Windows "Stop <module>").

 

Recommendation for communications processors with preprocessing

If the utilization of the PC CPU can briefly exceed 90 %, we recommend CPs with separate preprocessing (CP 1613 A2, CP 1623, CP 5613 A2, CP 5623, CP 5614 A2 and CP 5624) because the communication can then be handled mainly on the communications module.

 

Installing/uninstalling new hardware

After installing or removing new hardware, Windows must be started at least once by a user with administrator privileges.

 

 

26.2    Restrictions

 

Using a SIMATIC NET CP in a docking station

Docking stations with the dock in/dock out functionality are not supported.

 

 

26.3    Computer requirements

 

Minimum requirements for PG/PCs

The products of this SIMATIC NET Software Products were tested on PGs/PCs that meet the following minimum requirements:

 

Operating system

Minimum requirements

Windows 7
Professional 32 bit

2.4 GHz PCs with 1 GB RAM,

XGA 1024x768 with 16-bit color

Windows 7
Enterprise 32 bit

2,4 GHz PCs with 1 GB RAM,

XGA 1024x768 with 16-bit color

Windows 7
Ultimate 32 bit

2.4 GHz PCs with 1 GB RAM,

XGA 1024x768 with 16-bit color

 

 

 

27.           Compatibility

 

No release for SIMOTION

The SIMATIC NET PC Software CD V8.0 with Windows 7 32-bit is not released for operation with SIMOTION.

 

 

 

28.           Notes on C programming interfaces

 

Following protocols are explicit supported by the C programming interface:

 

 

28.1    Notes and restrictions relating to the SAPI-S7 programming interface

 

S7 communication with C applications

In SIMATIC STEP 7/NCM PC, connections used by C applications should not be configured as permanent OPC connections.

Otherwise, these connections will be established when the UA protocol is activated and are no longer available for the C application.

 

Connection reestablishment

Between the call for the "s7_abort( )" function and the "s7_initiate_req( )" function, there must be a waiting period of approximately 1 second. During this time, the "s7_receive( )" function can be called (polling or in Windows Messages by SAPI-S7).

Note that if a connection is aborted due to a problem (s7_receive = S7_ABORT_IND), the subsequent connection establishment with "s7_initiate_req( )" may only succeed after a maximum wait time of 90 seconds since the connection partner continued to occupy connection resources.

 

Reaction to error codes

If a function returns the value ERR_RETRY, the corresponding request must be repeated.

Example: s7_get_read_cnf = ERR_RETRY -> Repeat s7_read_req

 

Not all variable types

The variable types supported by the S7 protocol are at present not completely supported by all S7 servers (therefore the variable types STRING, TIMER, COUNTER and bit arrays should not be used).

 

Duration before a timeout is signaled

In the data transfer phase, the time required before an Abort indication is received is as follows for a CP 1613 A2/CP 1623 with ISO:

·         No data traffic

150 s

·         With data traffic

50 s

 

Restrictions SAPI-S7

The following functional restrictions apply to this version of the product.

 

Service/Function

Restriction

s7_get_vfd_ustate_ind

This service is not yet permitted.

s7_vfd_state_req

This service can only be used on other (remote) devices.

Variable services

The variable types supported by the S7 protocol are at present not completely supported by all S7 servers (therefore the variable types STRING, TIMER, COUNTER and bit arrays should not be used).

Trace functions

The functions

·         s7_write_trace_buffer()

·         s7_mini_db_set()
with the parameters:
- S7_MINI_DB_TRACE_FILENAME
- S7_MINI_DB_TRACE_TARGET
- S7_ MINI_DB_TRACE_MAXFILES
- S7_MINI_DB_TRACE_MAXLINES
- S7_MINI_DB_TRACE_DEPTH
- S7_MINI_DB_TRACE_SELECT
- S7_MINI_DB_TRACE_NO_LINES

are no longer available as of SIMATIC NET CD V8.0 since as of V8.0, a uniform, cross-module trace was introduced.

 

 

 

Multithread operation

Note that the "s7_receive( )" call and the corresponding processing function must run in the same thread.

 

Autostart

Do not start an S7 application using the Windows Autostart program group, Instead, use the Autostart functions of the "Configuration Console" tool to launch PC user programs following startup.

 

s7_get_diag_ind returns incorrect diagnostic information

When using "s7_get_diag_ind( )", diagnostic information can be lost.

 

s7_get_await_initiate_cnf

Section 3.4.4 "s7_get_await_initiate_cnf()" on page 66 of the "S7 Programming Interface" manual incorrectly states:
"...Following this, the corresponding processing function 's7_get_initiate_cnf( )‘ must be called for internal..."
The function described in the section is, of course, meant::

"...Following this, the corresponding processing function 's7_get_await_initiate_cnf() must be called for internal..." ;

  

PC-PC connection

If you use S7 connections for communication from PC to PC, the S7_MINI_DB_INIT_RSP_PDU_SIZE parameter set with the "s7_mini_db_set" function, may be a maximum of "480" if the ONLINE mode is set in the Station configuration Editor.

 

S7 programming interface: return values of the "s7_receive" function

When evaluating the return values of the "s7_receive" function, if unexpected values occur, for example, in the default branch of the corresponding switch instruction, the "s7_discard_msg" function must be called.

 

Configuring

In SIMATIC STEP 7/NCM PC, "PLC à Configure" may only be used when there is no communication with other partners.

 

 

 

29.           Notes on project engineering, configuration and NCM

 

XDB import

XDB import must only be done when there is no communication taking place with other partners.

 

Configuring

In SIMATIC STEP 7/NCM PC, "PLC à Configure" may only be used when there is no communication with other partners.

 

Configuring a CP 1623 with SIMATIC STEP 7/NCM PC

If two or more CP 1623s were configured in a project, an IP address is required to distinguish the CPs during online configuration with SIMATIC STEP 7/NCM PC. This means that the CP 1623s (when there is more than one) must be configured with MAC and IP address.

 

Extra readme file for SIMATIC NCM PC

Please read the notes in the readme file ("ncm_readme.htm” ) for the product SIMATIC NCM PC on the "SIMATIC NET, PC Software" CD or in the service pack download area.

 

Diagnostics

In the Station configuration Editor, context-sensitive diagnostics of individual components (activated with the right mouse button -> Diagnostics) is available only when SIMATIC STEP 7/NCM PC is installed on the PC.

Remote diagnostics is possible when SIMATIC STEP 7/NCM PC uses its own diagnostics.

 

Complete description of the topic

The configuration of a PC using SIMATIC NCM PC and the related software is described in detail in the "Commissioning PC Stations" and "Industrial Communication with PG/PC" manuals.

 

Commissioning the PC with PROFIBUS communications processors

As long as the configuration of the PROFIBUS communications processors is not yet completed, the modules must not be connected to the network of the operational system!

When configuring a PROFIBUS communications processor, the station address, for example, must be set. Randomly set addresses can cause problems on the plant bus!

 

Downloading or importing does not work

Before downloading or importing configuration data, the "S7 Connection Diagnostics" program must be exited.

 

Downloading a PC station via the "PC Internal" access point

With certain network configurations, the following reaction can occur sporadically:
When downloading to a SIMATIC PC station using the "PC Internal" access point, a message appears telling you that the system data block, for example, 1001 or 1007 cannot be deleted.
In this case, restart the download – and the download to the station will succeed.

 

Downloading to a PC station and avoiding modifications to the configuration

During a download by the SIMATIC NCM Manager, "HW Config" or "NetPro" to the locals SIMATIC PC station, no changes, for example deleting an application, must be made in the Station configuration Editor.

 

Dealing with problems when downloading or importing

Before downloading or importing configuration data, the "S7 Connection Diagnostics" program must be exited.

 

Error message immediately after installation

On some computers, the message "Application error caused a stack fault in module <unknown> ..." can appear immediately after installation and existing authorizations are not detected. To eliminate the problem, reboot your computer.

When you start SIMATIC NET, if you see the message "Softbus device not running! Cancel will terminate the S7RTM", this means that an important component of SIMATIC NET is not correctly installed. In this case, click the "Cancel" button and install the "SIMATIC NET, PC Software" CD again. If the problem persists, please contact the hotline.

 

When downloading configurations, note the following

User programs that do not communicate over the OPC interface must be terminated before downloading the configuration with SIMATIC STEP 7/NCM PC and then restarted.

 

Downloading or importing an XDB file of configurations with several hundred connections takes several minutes

Downloading or importing an XDB file of configurations with several hundred connections can take several minutes. Please wait until complete.

 

Configuring the "Access Point of the Application"

You can set an "access point of the application" both with the "Configuration Console" program and with the "Set PG/PC Interface" program. Never use both programs at the same time.

 

Configuration of the Information Service

When you install SIMATIC NET, PC Software an information service is installed that informs the user of special operating events. The events include the following:

·         A trace is active for a protocol or a software component.

·         An OPC protocol is deactivated.

The information service indicates the monitoring function with an icon in the status area of the taskbar.

A flashing warning triangle in the icon indicates a special operating event.

If you double-click on the icon, you open the window of the information service. Here, you will see the operating events listed. To read the detailed information of a message, click on the relevant row in the table of events.

You can close the information service if you are not interested in special operating events. Simply right-click on the icon in the status area of the taskbar and select the "Exit" menu command. The information service will then close down after a few seconds. It is also possible to restart the information service from the Start menu.

 

Installing STEP 7 after installing the "SIMATIC NET, PC Software" CD

If STEP 7 is installed after the "SIMATIC NET, PC Software" CD and if the access point S7ONLINE is assigned to the CP 5613 A2/CP 5613 FO/CP 5614 A2, the assignment must be confirmed explicitly in "Set PG/PC Interface" or the "Configuration Console" prior to communication.

 

Installation of SIMATIC NCM PC on a separate PC without SIMATIC NET, PC software

If SIMATIC NCM PC is installed on a separate PC, it is only possible to download the configuration to other PCs if a product from SIMATIC NET PC Software is also installed, for example IE Softnet PG.

 

Instance DBs on the OPC server with S7 symbols

Instance DBs are taken into account in the configuration of the OPC server with S7 symbols in STEP 7 as of version 5.3 SP1.

 

S7 symbol names with period (.) are not permitted.

With the S7 symbols for the OPC server application, symbol names with the period "." character can be configured but they cannot be used on the PC station by an OPC server and are rejected as invalid items.

 

Do not set CCAgent to "Pause"

After logging on, the "CCAgent State" dialog can be started in the information area of the taskbar. Do not set the "Pause" option. Otherwise, you can no longer start, log off or change user.

The WinCC processes "CCServer" and "CCAgent" must then be exited by an administrator.

 

Diagnostic buffer entry in the Station configuration Editor "The CP with index ... is not operational"

If the message "The CP with index ....is not operational" appears in the diagnostic buffer of the Station configuration Editor, follow the steps below:

Change to network diagnostics of the "Configuration Console" program or "Set PG/PC Interface". Run diagnostics for the CP. The diagnostic information indicates the exact nature of the problem.

 

Diagnostic buffer entries when a download fails

In some situations, it is possible that a component rejects downloaded project engineering data. In such cases, the message "Module ... (index ?) in station ... cannot be started. Do you want to display the module status with the diagnostic buffer? Yes on no.". Please note that the diagnostic buffer cannot be displayed at this point. Use the diagnostic buffer of the target station.

 

Error message in the diagnostic buffer of the Station configuration Editor "The sdb is incorrect"

When importing XDB files ("Import Station" in the Station configuration Editor), the message "The sdb is incorrect"/"component database is invalid" can be entered in the diagnostic buffer. If this problem occurs, it means that the project engineering configuration of your DP master system was not accepted. To apply the configuration, use the download function of SIMATIC STEP 7/NCM PC and download the PC station again.

 

Assignment of the CPs to the real hardware in the Station configuration Editor

Following any change to the configuration (during station import etc.), please check the assignment of the CP modules in the Station configuration Editor compared with the hardware installed in the PC; with PROFIBUS modules using their buzz functions if available.

To be able to assign a module uniquely when importing a station, the module type, module version, and the interface parameter assignment must match the settings of the existing real hardware exactly.

 

NCM does not support archiving and dearchiving

You can, however, archive or dearchive the project data in the project directory <project path> yourself, for example with "WinZip".

To archive, follow the steps outlined below:

1. Install "WinZip"

2. Change to the Windows Explorer.

3. Select the project in the project folder (as default, the projects are in <INSTALLDIR>\SIMATIC_NCM\S7proj)

4. By right-clicking -> WinZip, the project can be archived.

To extract, follow the steps outlined below:

1. Double-click on the archive

2. Click the "Extract" button.

3. To open the project with the SIMATIC NCM PC Manager, use the "Browse" button in the "Open Project" dialog.

 

Configuring the target system: Target computers (except your own) are not displayed in the list of accessible nodes

If the target computer was disconnected from the network or when several network adapters are attached to the network, the network adapter installed in your own PC must be reinitialized.

Follow the steps outlined below to reinitialize the network adapter:

1. Open the Windows Explorer.

2. Open "My Computer" in the Windows Explorer.

3. Click on the "SIMATIC Shell" entry with the right mouse button and select "Settings". Reaction: The "Settings" dialog appears.

4. Select the network adapter intended for communication and confirm with OK.

5. Confirm the message indicating the that the communication service will be reinitialized with OK. (Note: As a check, the name of the activated adapter is colored blue.)

Please note that a target computer can only be reached over the initialized network adapter, in other words, only over the adapter highlighted in blue in the "SIMATIC Shell".

 

Connection abort when downloading to the SIMATIC PC station

If the download aborts when downloading a SIMATIC PC station due to a component that cannot be stopped, the PC station may be in an inconsistent status following the aborted download. You can find the cause in the diagnostic buffer of the Station configuration Editor.
The reason why the component cannot be stopped is that there is still communication active over this component. Please close the active communication and repeat the download.

 

No symbolic addressing with OPC in a multiproject context until STEP 7 V5.4

If S7 connections are created between two different projects of a multiproject in STEP 7 up to V5.4, no symbols are available in the S7 tab of the OPC server with the  "Selected" button. Even if you select "Use symbols - All", no symbol file is generated. If you want to use symbolic access, please avoid using any cross-project connections. As of STEP 7 V5.4, the OPC symbols can also be used for multiprojects. Make sure, however, that the station names are unique.

 

Unexpected message "Missing SW product/optional package" when opening a STEP 7 project

Projects that display this error message when they are opened in SIMATIC NCM PC, can only be opened with STEP 7.

  

OPC server - PROFINET IO – Item-specific rights are not adopted

The settings item-specific rights in the "PROFINET IO" tab in the "Edit..." dialog of the OPC server are not adopted after "Save and Compile". Use the default rights for all items to restrict access rights.

 

Loading a configuration locally

To load a configuration on the local station, the S7ONLINE access point must be set to the interface parameter assignment "PC-internal".

 

Remote configuration download

If you receive the following message when attempting a remote configuration download:

"Download to module (33:16662) online: The connection cannot be established to the target module." You should restart your PC if the repeated download attempt does not work.

 

XDB import failed

If the computer is restarted soon after an XDB import or download of configuration data, this can lead to an OPC client, for example the OPC Scout, not recognizing the configuration data. In this case, repeat the download of the configuration data.

 

Firewire modules

Network adapters such as the 1394 are not supported by SIMATIC NET, PC Software and must not be inserted even in the Station configuration Editor.

 

Inserting/removing communications processors

If you insert a further communications processor or remove an inserted communications processor, it is possible that no component is displayed in the Station configuration Editor. In this case, reboot the computer.

 

Error when inserting an "IE_General" module

If you add a component of the type "IE_General" in the "Components" tab of the Station configuration Editor, an error can occur in the internal "pniopcac.exe" program (Event Viewer -> Application -> double-click on "Application Error" -> "Failed application pniopcac.exe ...").

This does not have any negative effect on the functionality of the module, unless it is used as a PROFINET IO controller. In this case, download a PROFINET IO configuration. The error then no longer occurs.

 

Restarting the OPC server after downloading a changed destination address

If the configuration of a non-local PC station is downloaded with a different Ethernet destination address from that of the module configured there, it is possible that the OPC server on the destination station must be restarted.

This can be done at the project engineering station.

1.  Start the "NCM S7 Diagnostics" program (Start menu Start -> ... -> STEP 7 ‑>  NCM S7 -> Diagnostics).

2   Open an online connection with the following parameters:

·       Node address = address of the CP on the destination computer

·       Slot = index of the OPC server in the Station configuration Editor

3a Start the OPC server with the call: Operating Mode -> Start Module.

3b The OPC server can also be started locally by selecting the OPC server in the Station configuration Editor and selecting the "Run" function in the context-menu (right mouse button).

 

No remote download to the PC station while the OPC XML DA Web service is running

Remote downloading to the PC station is rejected while an OPC XML DA Web service application is running on the target PC station.

Prior to remote project engineering, close down the Internet Information Server (IIS) on the target PC station and with it the OPC XML DA Web service and your application.

 

Remote configuration of the PC station

For the remote configuration of the PC station in SIMATIC STEP 7/NCM PC, you should also allow "remote basic and OPC communication" on the target computer ("Configuration Console" under "Security").

 

Changing the Ethernet station address by configuration

If you download a configuration to a target PC and the station address (for example MAC address or IP address) of the communications processor of the target PC is changed as a result, the download aborts since the remaining data can no longer be downloaded after changing the station address.

For this reason, changing the MAC address or the IP address by configuring is not permitted.

 

"Automatic termination after:“ of a "TCP connection" not released

The setting "Automatic termination after:“ available with the "Details of Connection Establishment“ button in the properties of a "TCP connection" of the OPC server is not released in SIMATIC STEP 7/NCM.

 

Language changeover

After changing the language, the PC should be restarted or the user should be logged off from time to time so that all applications adopt the new language.

 

Constraints for downloading 1 000 000 OPC S7 symbols

1 000 000 OPC S7 symbols with an average symbol length of 24 characters of the SIMATIC S7-station name length, data block name length and data block variable name length can be configured, compiled and downloaded in STEP 7 to the PC station or imported there. If you reduce the average character length, you can configure more OPC S7 symbols.

 

Configured access protection of the S7 OPC servers in "HW Config" is not effective for UA OPC access

On the properties page of "HW Config" of the S7 OPC server, the access protection and OPC item-specific rights can be set. This configuration does not take effect for the UA S7 OPC protocol after downloading. To assign rights, set the OPC item-specific rights using the S7 symbols on the same properties page.

 

Indexing for faster searching can lead to communications problems
If, for example, in Windows 7, the indexing of the PC files is enabled, and if traces were created in the indexed area, the high processing load can disrupt communication (recognizable, for example, by loss of connections to partner devices).
In this case disable indexing of these folders or the indexing on the entire PC.

 

Compatibility between modules

Configurations of compatible modules can be downloaded to modules installed in the PC. The following overview shows the combinations available.

 

Module

Compatible (SIMATIC STEP7/NCM) configuration that can be loaded

CP 1612 A2

CP 1612

CP 1613 A2

CP 1613

CP 1623

CP 1613

CP 5603

(CP 5613) + CP 5613 FO + CP 5613 A2

CP 5613 A2

(CP 5613) + CP 5613 FO

CP 5614 A2

(CP 5613) + CP 5613 FO + CP 5613 A2 + CP 5614 + CP 5614 FO

CP 5614 FO

(CP 5613) + CP 5613 FO + CP 5614

CP 5621

CP 5611 + CP 5611 A2

CP 5623

(CP 5613) + CP 5613 FO + CP 5613 A2

CP 5624

(CP 5613) + CP 5613 FO + CP 5614 + CP 5614 FO + CP 5613 A2 + CP 5614 A2 + CP 5623

CP 5711

CP 5512

 

(CP 5613) only with XDB import

 

 

XDB import when more than one compatible CP is inserted in the computer

If several compatible CPs are installed in the computer, it is only possible to import a configuration in the Station Configuration Editor (XDB import) if the module assignment has already been adapted in SIMATIC STEP 7/NCM PC. The module assignment is made in the "HW Config" or "PC Config" program in the object properties of the module, "Assignment" tab. Here, the interface of the CP to be configured should be entered in the input boxes of the interface parameter assignment being used so that several CPs of the same type can be assigned.

 

Configuration with COML S7

COML S7 is used for the fast configuration of modules. The configuration is assigned to one module or more specifically one module name. If the module is removed from the PC, the configuration is lost.

 

If you want to replace one module with another, follow these steps: 1. Export the COML S7 configuration. To do this go to "Modules" in the Configuration Console and select "Export COML S7 connection lists" with the right mouse button.
2. Replace the module.

3. Import the COML S7 configuration.

 

SIMATIC NET notification service not displayed in the information area

The SIMATIC NET notification service is not displayed in the information area on the taskbar in Windows 7. We strongly recommend that you display the icon of the SIMATIC NET notification service. Configure the Windows 7 the taskbar to do this.

 

Restriction of the access rights in HW Config for OPC UA server items has no effect

In SIMATIC STEP 7/NCM PC HW Config, the access rights for all and for specific selected OPC items can be restricted for the OPC server protocols PROFINET IO and S7 of a SIMATIC PC station. This configuration is ineffective for access to these items via the OPC UA interface.

 

 

 

30.           Development environments and compilers supported

 

Compilers supported:

The following compilers can be used with the SIMATIC NET products under the following Windows operating systems:

·          Windows 7 32 Bit
- Visual Studio 2008 + SP1, C, C++; with OPC also C# and VB.NET

 

.NET-Framework

In Windows 7, .NET-Framework 3.5 is already installed so it no longer needs to be installed to be able to use the SIMATIC NET CD.

The expansions of .NET-Framework 3.5 compared with .NET-Framework V2.0

were not tested with the "SIMATIC NET PC Software" CD.

 

 

 

31.           Routing

 

Routing

If you use this SIMATIC NET product on a PC/PG with a SIMATIC STEP 7/NCM PC V5 product, you can use the routing functionality. For information on configuring, refer to the STEP 7 documentation.

 

What is routing?

As of STEP 7 V5, it is possible to reach S7 stations online beyond the boundaries of a subnet using a PG/PC, for example to download user programs or a hardware configuration or to run tests and diagnostic functions. You can attach the programming device at any point in the network and establish an online connection to all stations accessible via gateways.

 

Operating inter-subnet connections

As of Version V6.0.5 of the SIMATIC NET, PC software with SIMATIC STEP 7 as of V5.2/SIMATIC NCM PC as of V5.2 it is possible to operate S7 connections over several subnets, for example from a PC over Ethernet, an IE/PB Link to an AS station with a PROFIBUS CP. Currently only configurations with one (1) gateway and from Ethernet to PROFIBUS or vice versa are released.

 

 

32.           Operating systems 32 bit

 

The products of this "SIMATIC NET, PC Software" CD can be operated with the following operating systems:

 

Operating Systems 32 bit

Minimum requirements

Windows 7

Professional, Ultimate or Enterprise

 

 

Of the Chinese language versions, only the language version "Simplified Chinese" is supported, however not in the Multilanguage versions of Windows. The multilanguage version is released for the languages German and English; the other languages were not tested.

 

 

32.1    General information

 

The "SIMATIC NET, PC Software" CD consists of several setups and after they have been installed, the Microsoft operating systems create restore points. It is pointless to restore to an interim setup status, in other words, to the status of a half installed "SIMATIC NET, PC Software" CD.

 

If you change Ethernet adapters or modify (configure) the MAC addresses, Microsoft changes the installation ID. This affects the activation ID, in other words, after several changes, it becomes necessary to reactivate the license.

  

Required privileges

Under Windows 7, you must have or administrator privileges to start the software tool "Set PG/PC Interface" or "Configuration Console".

 

If you want to add a new user after installing the SIMATIC NET CD, you will need to include this user in the "Siemens TIA Engineer" group. Otherwise the installation routine of the SIMATIC NET CD enters the current user in the "Siemens TIA Engineer" group during the installation, assuming the user has administrator privileges.

 

Upgrade to newer Windows operating systems

If you upgrade from Windows Vista to Windows 7 you must first uninstall all the SIMATIC NET products. After uninstalling the products, you can then upgrade to the new Windows version. The SIMATIC NET, PC software V8.0 can then be installed.

 

Only one operating system per computer permitted

SIMATIC NET PC software products are supported only on computers on which one operating system and one only is installed. Computers with multiple selectable operating systems are not permitted.

 

Hardware wizard dialog in Windows 7

If a SIMATIC NET module is installed in the computer, it is possible that after you have installed the SIMATIC CD and restarted the PC, the module is not installed automatically. Instead, the Hardware Manager or its Wizard for new hardware appears. Under Windows XP + SP2, the wizard starts by asking you whether it should search for current drivers on the Windows Update Server. Choose "No, not this time" and then click the buttons "Next" and "Next" again and then "Finish".

 

 

Language detection of Windows

The language detection of Windows is not supported.

 

Restoring files

When Windows prompts you to insert the Windows CD to restore files, follow the instruction and confirm with "OK".

 

Windows domain profiles overwrite local settings

In a Windows domain, a domain administrator can make local settings on workstations that are adopted when the workstation logs on with the domain and overwrite the existing local settings.

Among other things, this affects:

·         Windows Firewall

·         Virus scanners

·         Group policy

·         Entries in the registry

·         Access rights in the file system

Note that settings relevant to SIMATIC NET involving the firewall, the DCOM configuration and necessary access permissions in the file system can be changed and the functionality impaired.

 

As of Windows Vista, the firewall allows the configuration of outgoing connections

In the default setting, outgoing connections are allowed in Windows Vista. You can, however, change this behavior and/or define your own rules. The SIMATIC NET software assumes the default setting. If you make changes for outgoing connections that impact SIMATIC NET, SIMATIC NET functionality may be impaired.

 

Windows Defender causes communication interruptions of several seconds

The Windows Defender regularly checks the system for malware. This check can cause interruptions of SIMATIC NET communications lasting several seconds. If the PC is used in a secure, protected environment, the Windows Defender should therefore be disabled.

 

 

32.2    Restrictions

 

Messages from the Windows Defender service

Ignore the messages when the Microsoft Defender service classifies the "SIMATIC NET, Software CD" as potentially unwanted.

 

Parental control

The use of parental control can lead to restrictions in operator control and the running of the SIMATIC NET PC software that may affect safety.Parental control has not been approved with the "SIMATIC NET, PC Software V8.0" CD.

 

Network load balancing

Distributed servers are not supported for automation networks by SIMATIC NET.

 

Quality Windows Audio Video Experience

Changes in the prioritization can reduce the performance of SN PN IO and lead to failure of IO devices.

 

RPC over HTTP proxy

Was not tested and is therefore not released.

 

Windows System Resource Manager

The limitation of resources can lead to non-functioning of industrial communication.

 

Connection Manager Administration Kit

Supports the administrator in management of remote nodes. Network access protection allows the configuration of access conditions but this has not yet been tested and released for industrial networks.

 

Failover Clustering

Failover clustering has not been approved with the "SIMATIC NET, PC Software V8.0" CD.

 

Group Policy Management

Group policy management has not been approved with the "SIMATIC NET, PC Software V8.0" CD.

  

 

32.3    No real time

 

Windows

Windows is not a real-time operating system. Real-time requirements cannot therefore be met.

As a result, it is possible that when starting programs or reading files, your application is not executed for several 100 ms.

The points below will help you to optimize your system and to achieve reaction times approaching those of a real-time system:

·         You should have enough memory so that Windows only seldom needs to use the page file.

·         Avoid intensive access to diskettes, hard disks, or CD drives such as occurs when starting up large programs.

 

Simultaneous network load

If there is a high network load due to parallel communication, for example copying files, a temporary station failure followed by return of the station can occur. This is due to the lack of real-time properties in WINDOWS.

This must be taken into account in the user program.

Increasing the update time of the PROFINET IO system reduces the incidence of these failures.

 

 

32.4    Terminal services with Windows 7

 

Description

With the terminal service, all work with SIMATIC NET PC software products can be performed via a Windows Terminal. Possible conflicts due to connecting several terminals have been eliminated. For a terminal user, this means:

·         Programs for configuring and assigning parameter values for the SIMATIC NET software such as "Configuration Console" or "Station configuration Editor" can be operated at the same time from one terminal.

·         From a terminal, the Station configuration Editor has only read access.

·         Messages from SIMATIC NET products (error messages, run-time messages) are displayed on all logged on terminals.

 

Further important aspects of using terminal services

The terminal client may not shut down a terminal server that handles industrial communication.

 

Installation of SIMATIC NET PC products

Please note that Setup switches the Windows Server with installed terminal services to the "installation mode" from the "user mode" during installation of SIMATIC NET PC Products.

Once the installation is successfully completed, the server continues in the user mode again after you restart.

 

Further information

You will find wide-ranging help on the terminal services in the help system of the Microsoft Windows Server.

 

Restrictions affecting configuration

It is not possible to configure with the SIMATIC NET PC Manager in SIMATIC NCM PC on terminal service clients.

 

Programs started from a remote terminal client can hang for several seconds

If you start an application on a terminal server from a remote terminal client, this may hang for several seconds if the connection between the terminal client and terminal server is disrupted or the terminal client computer changes to the sleep mode. This can lead to temporary computer blockages of several seconds on the terminal server if the communication connection between the PC/PG and terminal is interrupted.

 

Configuration with the Station Configuration Editor and other services with remote desktop or terminal services

Configuring modules with several sessions running at the same time causes problems because this can result in inconsistent statuses. For this reason, configuration with more than one open service is blocked at critical points. This may mean that boxes that can normally be edited are grayed out if terminal services are operating. Before you can edit in this situation, the terminal services must be disabled.

 

 

32.5    VMware V7.0.1 32 bit

 

SIMATIC NET PC software with VMware V7.0.1 32-bit

 

Must not be used for productive operation, only for testing and simulation.

 

The following hardware support is possible:

 

Please note the following points if you use SIMATIC NET PC software with VMware:

 

- Softnet Ethernet with S7, SR (without Fetch / Write communication) protocols
via IE General

- Softnet Profibus with S7, FDL, DP, DP2 protocols via CP 5711

- Depending on the number of communications partners used, it may be necessary to extend the monitoring times of the protocols.

 

Note on CP 1612 A2: If a CP 1612 A2 is used in the host system, then in contrast to an installation on a standard PC, this must be configured as "IE General" and not as "CP 1612". The reason for this is that VM Ware "bridges" the entered network adapters of the host to the guest mode.

 

Note on CP 5711: If the module is not correctly recognized in the virtual environment, it can be assigned to the guest with "Disconnect (Connect to Host)" and repeated "Connect (Disconnect from Host)". In this case the configuration must be reloaded.

 

Note on license keys: If license keys are stored on virtual data media, they can easily be lost. As a result, no replacement can be supplied if they are lost.

 

 

 

33.           Trace

 

33.1    OPC-trace

 

To help with troubleshooting, there is an OPC-trace that can be activated in the Configuration Console. To do this, select “SIMATIC NET Configuration -> Applications -> OPC Settings -> OPC-Trace” in the left-hand navigation window (configuration tree).

 

In the right-hand window, you will then see the traces available for OPC.

 

33.2    Working with the trace concept

 

At the left-hand edge of the navigation window you can select the module whose trace you want to activate.

Each module has a submenu:

 

General: displays general information on the module (driver information / current applications / users …)

Trace Settings: depending on the module, you can see where and which functionality will be traced.

View Trace File: if you open this window, the current trace entries are displayed directly in the open window.

The updating of this window (if several are open, further tabs are displayed) requires time to process and the windows should only be displayed if you want to trace an error online.

Activated traces are indicated by a red exclamation point in the left navigation menu.