Safety Guidelines
This manual contains notices you have to observe in order to ensure your personal safety, as well as to
prevent damage to property. The notices referring to your personal safety are highlighted in the manual
by a safety alert symbol, notices referring to property damage only have no safety alert symbol. The
notices shown below are graded according to the degree of danger.
!Danger
indicates that death or severe personal injury will result if proper precautions are not taken.
!Warning
indicates that death or severe personal injury may result if proper precautions are not taken.
!Caution
with a safety alert symbol indicates that minor personal injury can result if proper precautions are not
taken.
Caution
without a safety alert symbol indicates that property damage can result if proper precautions are not
taken.
Notice
indicates that an unintended result or situation can occur if the corresponding notice is not taken into
account.
If more than one degree of danger is present, the warning notice representing the highest degree of
danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a
warning relating to property damage.
Qualified Personnel
The device/system may only be set up and used in conjunction with this documentation. Commissioning
and operation of a device/system may only be performed by qualified personnel.Within the context of
the safety notices in this documentation qualified persons are defined as persons who are authorized to
commission, ground and label devices, systems and circuits in accordance with established safety
practices and standards.
Prescribed Usage
Note the following:
!Warning
This device and its components may only be used for the applications described in the catalog or the
technical description, and only in connection with devices or components from other manufacturers
which have been approved or recommended by Siemens.
Correct, reliable operation of the product requires proper transport, storage, positioning and assembly
as well as careful operation and maintenance.
Trademarks
All names identified by ® are registered trademarks of the Siemens AG.
The remaining trademarks in this publication may be trademarks whose use by third parties for their
own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and
software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency.
However, the information in this publication is reviewed regularly and any necessary corrections are
included in subsequent editions.
Siemens AG
Automation and Drives
Postfach 4848
90437 NÜRNBERG
GERMANY
Copyright © Siemens AG 2006
A5E00767204-01
Siemens AG 2006
Technical data subject to change.
Preface
Purpose of the Manual
This manual provides the information necessary to use the PCS 7/505 OS
Channel.
Required Basic Knowledge
Readers are presumed to be knowledgeable in the use of PCS 7.
Where is this Manual valid?
This manual is valid for the software package PCS 7/505 OS Option for V6.1.
Training Centers
Siemens Technical Training Center provides extensive training for all levels of
plant personnel to ensure optimal performance from PCS 7 control systems.
Classes include extensive hands-on activities using appropriate equipment, making
the training directly and immediately applicable.
On-line information is available: http://www.sea.siemens.com/sitrain
Siemens also offers a number of training courses to familiarize you with the
SIMATIC S7 automation system. Please contact your regional training center or
our central training center in D 90327 Nuremberg, Germany for details:
Telephone: +49 (911) 895-3200.
Internet: http://www.sitrain.com
PCS 7/505 Channel
AE00767204-01 iii
Preface
A&D Technical Support
Worldwide, available 24 hours a day:
Beijing
Nürnberg
Johnson City
United States: Johnson City, TN Worldwide: Nürnberg Asia / Australia: Beijing
Technical Support
24 hours a day, 365 days a year
Phone:+49 (180) 5050-222
Fax:+49 (180) 5050-223
E-Mail: ad.support@siemens.com
GMT:+1:00
Technical Support and Authorization
Local time: Monday to Friday
8:00 AM to 5:00 PM
Telephone:+1 (423) 262 2522
or +1 (800) 333-7421 (USA only)
Fax:+1 (423) 262 2289
Mail to: techsupport.sea@siemens.com
GMT: -5:00
Authorization
Local time: Monday to Friday
8:00 AM to 5:00 PM
Phone: +49 (180) 5050-222
Fax: +49 (180) 5050-223
Mail to: ad.support@siemens.com
GMT: +1:00
Technical Support and Authorization
Local time: Monday to Friday
8:00 AM to 5:00 PM
Phone:+86 10 64 75 75 75
Fax:+86 10 64 74 74 74
Mail to:ad.support.asia@siemens.com
GMT:+8:00
Automation and Drives Service and Support International
http://www.siemens.com/automation/service&support
The languages of the SIMATIC Hotlines and the authorization hotline are generally German and English.
PCS 7/505 Channel
iv AE00767204-01
1 Editing Channel Properties 1-1
1.1 The Host Tab .................................................................................................... 1-2
1.1.1 Channel Unit Configuration ..............................................................................1-3
1.2 The Communication Tab .................................................................................. 1-7
1.2.1 Interface to Simatic 505 Controllers .................................................................1-8
1.2.2 Total Operations ............................................................................................... 1-9
1.2.3 Single Tag Reads ...........................................................................................1-10
1.2.4 Single Tag Writes ...........................................................................................1-11
1.2.5 Tag List Reads................................................................................................ 1-12
1.2.6 Poll Time.........................................................................................................1-13
1.2.7 Tag Counts .....................................................................................................1-14
2 Diagnostic Counters 2-1
3 Editing Tag Parameters 3-1
4 Configuring the CP1613 Card 4-1
4.1 Using the Set PG-PC Interface......................................................................... 4-2
4.1.1 CP1613 MAC Addresses..................................................................................4-3
4.2 Using the Configuration Console.................................................................... 4-10
4.3 Requirements for 505 Communications ......................................................... 4-12
4.4 Using Both S7 and 505 Controllers ................................................................ 4-12
5 Connection Properties 5-1
5.1 Channel Connection Configuration................................................................... 5-1
6 OSx Compatibility 6-1
6.1 Pre-OSx 4.1.2A Must Not Use RBE ................................................................. 6-1
6.2 OSx 4.1.2A Can Use RBE................................................................................ 6-3
7 Remarks on 505 Utilities 7-1
PCS 7/505 Channel
A5E00767204-01 1-1
Editing Channel Properties
PCS 7/505 Channel
1-2 A5E00767204-01
1 Editing Channel Properties
To display the 505 System Parameters properties, follow these steps:
1. Select Start>Simatic>WinCC>Window Control Center. The WinCC Explorer
opens.
2. Open the desired project if it has not opened automatically.
3. In the left pane, double-click Tag Management. The SIMATIC 505 entry appears.
4. Double-click the SIMATIC 505 entry. The Tf Channel Unit appears.
5. Right-click the Tf Channel Unit and select System Parameters.The Tf System
Parameter property page appears.
PCS 7/505 Channel
A5E00767204-01 1-1
Editing Channel Properties
1.1 The Host Tab
PCS 7/505 Channel
1-2 A5E00767204-01
Editing Channel Properties
1.1.1 Channel Unit Configuration
It is very important to define the channel’s TF Host Name uniquely for each PCS 7
server system. For reasons explained later in this document, the first character of the
TF Host Name should also be unique among all PCS 7 505 systems on the same
network. The TF Host Name is used as part of the 505 connection configuration. The
TF Host Name is also used to form the default Ethernet Address for the CP1613. On
the PCS 7 system, the TF Host Name is used in each 505 connection configured in
the LDB for the CP1613. On the channel’s UNIT configuration (for the TF Channel), the
System Properties screen is used to enter the TF Host Name.
Note
Whenever the software is installed, reinstalled, or upgraded, the TF Host name
field is reset to blank. The correct TF Host Name must be entered.
The TF Host Name is unique for the system that will be running the project. The TF
Host Name is stored in the Windows registry on the system where it is entered (it is not
stored as part of the WinCC project) If duplicating or copying a project to another
computer the 505 Channel Unit must be again configured to have a unique TF Host
Name on the system that will be running the project.
The System Properties screen also holds buttons for the CP Configuration Reports.
However, these reports are generated only when the system has been taken to
RUNTIME after making any configuration change.
To configure the channel unit, you must complete these tasks in order:
xConfigure the TF Host Name for your PCS 7 server system.
xConfigure each TF Channel connection (discussed later).
xTake PCS 7 to runtime and display the "CP Configuration Reports". Choose Main
to view the report corresponding to the first CP1613. This report will show the
configuration parameters you need to set using the H1 Configurator. Likewise,
choose Alternate for the second CP1613 if present.
xFrom the information in the CP Configuration Reports, use the H1 Configurator to
configure and verify each individual CP1434TF configuration for every 505
controller.
xUse the Set PG-PC Interface to test and confirm that the connections can be
established.
The CP1434TF connection configuration is made by applying the existing OSx naming
conventions:
xEach Host/Connection name is used in an 8-character uppercase TSAP value.
xThe ALT TSAP value always begins with the character "A".
xEach Host/Connection name is truncated to the 8-character limit.
xIf required, each Host/Connection name is appended with asterisks to make it an
8-character value.
PCS 7/505 Channel
A5E00767204-01 1-3
Editing Channel Properties
In the CP1434TF module, its Local TSAP corresponds to the name given in the
channel Connection configuration and its Remote TSAP corresponds to the TF Host
Name given in the channel Unit configuration. The exact details for configuring each
505 CP1434TF module are presented in the CP Configuration Reports that are
accessible from the channel’s UNIT configuration screen.
The CP Configuration Reports are deleted when any Channel configuration change is
made. The CP Configuration Reports are newly generated when the channel goes into
Runtime. Therefore, when the CP Configuration Reports are viewed they will match the
latest configuration for the channel as it entered Runtime.
The following screen shots show a MAIN CP Configuration Report and its
corresponding H1 Configurator screen shot of the connection configuration for the 505
CP1434TF module.
The lines in the CP1434MAIN.TXT report file corresponds to the order for the
configuration of the connection using the H1 Configurator.
PCS 7/505 Channel
1-4 A5E00767204-01
Editing Channel Properties
As mentioned earlier, the TF HOST NAME text is used to form the Remote TSAP text
configured for a connection. It is important that the TF HOST NAME is unique for each
system, since the 505 CP1434TF connection configuration is dependent on the
uniqueness of its paired Local and Remote TSAP values. This uniqueness permits
usage of the value 000000000000 as the Remote Ethernet Address. This type of
configuration is known as "partially specified" and allows a connection to any partner
specifying the exact Local and Remote TSAP values in its connection request. This
type of configuration is preferred since it is independent of the partner’s (CP1613)
Ethernet address.
The PCS7 505 channel automatically configures the host’s CP1613 cards. This
configuration consists of the creation of a text file that lists the connections to be
placed onto the CP1613 card. This text file is converted into a binary file (having the
extension "LDB") that is loaded into the CP1613. This LDB (local database) file holds
the set of 505 TF connections used by the PCS7 505 channel. One parameter in the
LDB file is the Ethernet Address of the CP1613. This parameter is never actually
activated by the PCS7 505 LDB for the CP1613. However, it is possible to intentionally
or unintentionally activate this address when navigating the menus within the SIMATIC
NET utilities for "Set PG-PC Interface" or the "Configuration Console".
PCS 7/505 Channel
A5E00767204-01 1-5
Editing Channel Properties
Even though the PCS7 505 LDB does not set the Ethernet address for the CP11613, it
must create one for the purposes of successfully building the LDB file for the CP1613.
For this reason, it must create a unique Ethernet address. The address created will be
08.00.06.01.XX.A1 for the first CP1613 and 08.00.01.01.XX.A2 for the second
CP1613. The value XX is replaced with the hexadecimal value of the first character in
the TF HOST NAME.
PCS 7/505 Channel
1-6 A5E00767204-01
Editing Channel Properties
1.2 The Communication Tab
The parameters are described in the sections below.
PCS 7/505 Channel
A5E00767204-01 1-7
Editing Channel Properties
1.2.1 Interface to Simatic 505 Controllers
The Reset All Statistics button at the lower right works only if the channel is in
runtime mode. The commands invoked write to a specific registry key that the channel
monitors. When the key is reset, it clears all the statistic tags and updates the registry.
The default settings are valid for most user applications. Contact the Technical
Information Center (TIC) for more information.
PCS 7/505 Channel
1-8 A5E00767204-01
Editing Channel Properties
1.2.2 Total Operations
Field Description
Set Limits per Resource Set the number of operations (reads, writes, normal updates)
that can be outstanding between the controller and the channel
at any time. If there are more operations pending in the
channel, they are waiting for operations at the controller to
complete.
Set Limits for Interface Set the total number of operations (reads, writes, and updates)
that can be outstanding between all of the controllers and the
channel at any time.
In Progress This is the total number of operations that are currently
outstanding between all controllers and the channel.
Queued This is the number of operations that are waiting to be
processed by a 505 controller because there are currently
operations outstanding, and these operations would put the
number above one of the limits.
Cumulative Total This is the total number of reads and writes that have occurred
to the 505 controllers. Click the Reset button to get statistical
information about the channel (the number of operations over
time).
Cumulative Failed This is the total number of read/write operations to the 505
controllers that failed. Click the Reset button to get statistical
information about the channel (the number of operations over
time).
PCS 7/505 Channel
A5E00767204-01 1-9
Editing Channel Properties
1.2.3 Single Tag Reads
Field Description
Set Limits per Resource This is the total number of reads (Asynch Read or Synch
Read) that can be outstanding between a 505 controller and
the channel. This number should be well below the Total
Operations limit in order to keep read requests from
preventing other data from updating.
Set Limits for Interface This is the total number of reads (Asynch Read or Synch
Read) that can be outstanding between all 505 controllers
and the channel. This number should be well below the Total
Operations limit in order to keep read requests from
preventing other data from updating.
In Progress This is the number of single tag reads currently outstanding
between a 505 controller and the channel.
Queued This is the number of single tag reads that are waiting to be
processed by a 505 controller because there are currently
single tag reads outstanding, and these reads would put the
number above one of the limits.
Cumulative Total This is the total number of single tag reads that have occurred
between the channel and the 505 controllers. Click the Reset
button to get statistical information about the channel (the
number of reads over time).
Cumulative Failed This is the total number of single tag reads that have failed
between the channel and the 505 controllers. Click the Reset
button to get statistical information about the channel (the
number of reads that failed over time).
PCS 7/505 Channel
1-10 A5E00767204-01
Editing Channel Properties
1.2.4 Single Tag Writes
Field Description
Set Limits per Resource Set the total number of writes (Asynch Write or Synch Write)
that can be outstanding between a 505 controller and the
channel. This number should be well below the Total
Operations limit to keep write requests from preventing other
data from updating.
Set Limits for Interface Set the total number of writes ( Asynch Write or Synch Write)
that can be outstanding between all 505 controllers and the
channel. This number should be well below the Total
Operations limit to keep write requests from preventing other
data from updating.
In Progress This is the number of single tag writes currently outstanding
between a 505 controller and the channel.
Queued This is the number of single tag writes that are waiting to be
processed by a 505 controller because there are currently
single tag writes outstanding, and these writes would put the
number above one of the limits.
Cumulative Total This is the total number of single tag writes that have
occurred between the channel and the 505 controllers. Click
the Reset button to get statistical information about the
channel (the number of writes over time).
Cumulative Failed This is the total number of single tag writes that have failed
between the channel and the 505 controllers. Click the Reset
button to get statistical information about the channel (the
number of writes that failed over time).
PCS 7/505 Channel
A5E00767204-01 1-11
Editing Channel Properties
1.2.5 Tag List Reads
Field Description
Set Limits per Resource Set the total number of update operations (normal
background processing) that can be outstanding between a
505 controller and the channel. This number should be on
the order of the Total Operations limit in order to keep the
data updating as fast as possible. The data tags are broken
up into multiple lists for updating at the controller to optimize
performance.
Set Limits per Interface Set the total number of update operations (normal
background processing) that can be outstanding between all
505 controllers and the channel. This number should be on
the order of the Total Operations limit to keep the data
updating as fast as possible.
In Progress This is the number of update operations currently
outstanding between a 505 controller and the channel.
Queued This is the number of update operations that are waiting to
be processed by a 505 controller because there are currently
update operations outstanding, and these update operations
would put the number above one of the limits.
Cumulative Total This is the total number of update operations that have
occurred between the channel and the 505 controllers. This
can be reset to get statistical information about the channel
(the number of updates over time).
Cumulative Failed This is the total number of update operations that have failed
between the channel and the 505 controllers. This can be
reset in order to get statistical information about the channel
(the number of updates that failed over time).
PCS 7/505 Channel
1-12 A5E00767204-01
Editing Channel Properties
1.2.6 Poll Time
Field Description
Last Poll Time This is the last loop time in milliseconds observed for
the 505 API execution thread.
Long Loop Trigger Time This is the maximum time in milliseconds expected for
good execution of the loop. When this value is
exceeded, the Total Tag List Overruns field is
incremented.
Poll Delay Time This is the number of milliseconds to delay between
API polling loops.
Maximum Last Poll Loop Time This is the maximum LastPollLoopTime.
Total Cumulative Long Loops This is the number of loops that exceeded
Limits.PollLoopTime to execute, indicating
excessive API delays, API problems, or unexpected
resolving of tags synchronously in Async calls.
Total Tag List Overruns This is the number of tag lists that have exceeded their
scan rate (could be partially due to delays in starting the
scan because of limits on active operations). This field
indicates whether the scan rate can support the 505
workload.
PCS 7/505 Channel
A5E00767204-01 1-13
Editing Channel Properties
1.2.7 Tag Counts
Field Description
Active Tags This is the total number of active 505 tags. If two OPC clients are
reading the same 505 tag, this count will only increment by one.
Recent Inactive Tags This is the number of 505 tags that have become inactive within the
last 12 hours.
Inactive Tags This is the number of 505 tags that have been inactive for more than
12 hours. These need to be re-verified by the 505 controller.
Total Tag Lists This is the total number of 505 tag lists. The tags are broken up into
multiple tag lists to optimize read performance.
Total Tags This is the total number of 505 tags that are currently created in the
channel.
Maximum Tag List Length This is the maximum number of tags allowed in a tag list. This
number can be changed to further optimize tag update performance.
Combine Single Tag Reads This setting allows multiple single tag reads to be combined into a
larger list in order to optimize performance of single tag reads.
Force Tag List Compare This is the number of updates from the 505 controller where the
value is actually read from the 505 controller whether it has changed
or not, and injected into the channel. Normally, data updated from a
505 controller only occurs when a value has changed.
Tag Cache Aging Rate When a tag is created in the channel and then deleted, information
about the tag is stored in a cache so that future operations to the
same tag can be quicker. This value represents the time, in
milliseconds, that a tag will be held in the cache.
Total Lookups to Tag Cache This is the total number of times that the tag cache has been
checked for a tag that was previously used. This can be reset to get
statistical information (the number of tag look-ups over time).
Total Hits on Tag Cache This is the total number of times that the tag cache was checked,
and the requested item was found in it. This can be reset in order to
get statistical information (the number of successful tag look-ups
over time).
PCS 7/505 Channel
1-14 A5E00767204-01
2 Diagnostic Counters
In the WinCC Channel Diagnosis window, the Channels/Connections tab displays the
current channel and connections to WinCC. Selecting a channel in the left pane
displays the available counters and their value for the channel. Selecting a connection
listed beneath a channel displays the available counters for the connection. The
Configuration tab leads to functions that enable various logging mechanisms. Enabling
logging can, however, degrade performance.
To display the WinCC Channel Diagnosis window:
With a 505 OS application running, Select Start > Programs > WinCC > Tools >
Channel Diagnosis.
PCS 7/505 Channel
A5E00767204-01 2-1
Diagnostic Counters
PCS 7/505 Channel
2-2 A5E00767204-01
3 Editing Tag Parameters
The software channel connecting the 505 system and the OS includes a mechanism
for manually creating OS tags and linking them to 505 data structures. This is done in
the Tf Tag Parameter window. Tags are ordinarily created automatically by the DBA
utility, but this manual mechanism provides an opportunity to intervene.
To link OS tags to 505 data structures, follow these steps:
1. Select Start > SIMATIC > WinCC > Windows Control Center. The WinCC Explorer
opens.
2. Open the desired project if it has not opened automatically.
3. In the left pane, double-click Tag Management. The SIMATIC 505 entry appears.
4. Double-click the SIMATIC 505 entry. The Tf Channel Unit appears.
5. Right-click the selected connection and select New Tag. The Tag Properties
window opens, with the default name NewTag and a default data type of Binary
Tag. (The new tag is an OS tag. It is linked to a 505 tag in a later step.)
6. Assign an appropriate name and data type to the tag. Assign a length if necessary.
Click the Select button to the right of the Address field.
PCS 7/505 Channel
A5E00767204-01 3-1
Editing Tag Parameters
The Address tab provides, for reference, the OS Tag Name. In the Name field, enter the 505 tag
name that you want to associate with the new OS tag. Also configure the 505 Memory Type,
Address, Count, and Read Only properties. Consult the 505 user documentation for details.
PCS 7/505 Channel
3-2 A5E00767204-01
Editing Tag Parameters
7. Click the OK button to finish.
PCS 7/505 Channel
A5E00767204-01 3-3
Editing Tag Parameters
PCS 7/505 Channel
3-4 A5E00767204-01
4 Configuring the CP1613 Card
The CP1613 has the capability to function as a standard Ethernet card and to also
support devices other than the 505 controllers. However, the SIMATIC 505 CP1434TF
RBE channel is designed only to use the Technology Function (TF) functionality
provided by the CP1613 LDB file. Additionally, as indicated by the channel name, the
only module supported by the channel is the 505 CP1434TF module. For these
reasons, any use of a separate system database file (SDB) or other Ethernet controller
module is not supported. The driver named NDIS (to provide standard TCP/IP Ethernet
support) is also not suitable and is not recommended since its installation prevents
activation of a new or changed LDB file until after a reboot has occurred.
Up to four CP1613 cards can be physically supported, provided the memory slots are
available on the Windows machine. Up to two of these CP1613 cards can be assigned
for exclusive use as the MAIN and ALT networks for the SIMATIC 505 CP1434TF RBE
channel.
After installation of the PCS7 505 Option software onto a system already having the
CP1613 cards installed, only a single setting for each CP1613 must be manually
configured. Two separate utilities can be used to do the configuration. Either utility can
be used. The utility is used to make the settings that identify the CP1613 cards to be
used by the SIMATIC 505 CP1434TF RBE channel. The settings are named CP_H1_1
for the card to be used as the MAIN network by the channel and CP_H1_2 for the ALT
network. The unique assignments of CP_H1_1 and CP_H1_2 can be freely made to
any CP1613 that is to be used exclusively by the SIMATIC 505 CP1434TF RBE
channel.
Both of the configuration utilities are located under the Windows START menu for
SIMATIC->SIMATIC NET->Settings. The first utility is the Set PG-PC Interface. The
second utility is the Configuration Console.
PCS 7/505 Channel
A5E00767204-01 4-1
Configuring the CP1613 Card
4.1 Using the Set PG-PC Interface
This SIMATIC NET utility is used for the one-time configuration of the settings for
CP_H1_1 and CP_H1_2. Each of these access points must be assigned to a specific
CP1613(ISO) setting for one of the CP1613 boards. Typically, the assignment is made
so that CP_H1_1 is assigned to the CP1613(ISO) setting for the first CP1613 board
(used as the channel’s MAIN network) and CP_H1_2 is assigned to the
CP1613(ISO)<Board 2> for the second CP1613 board (used as the channel’s ALT
network).
To make the assignments, follow these steps:
1. From the Windows START menu, select Start > SIMATIC > SIMATIC NET >
Settings > Set PG-PC Interface.
2. From the Access Path tab, select the Access Point from the drop down list. In the
example below, CP_H1_1 is selected.
3. In the middle region of the screen, scroll to locate and double-click to select the
Interface Parameter Assignment. In the example below, CP1613(ISO) is
selected.
PCS 7/505 Channel
4-2 A5E00767204-01
Configuring the CP1613 Card
4. Follow the same procedure to specify the configuration for the CP_H1_2 setting.
4.1.1 CP1613 MAC Addresses
The user should not change the MAC address of a CP1613. If the MAC address is
inadvertently changed, the following procedure describes how to restore the CP1613
firmware address.
The PCS7 505 OS Option automatically builds and loads the 505 TF connection
configuration for the CP1613 board. The CP1613 board has a preset Ethernet MAC
address that is not changed by the automatic configuration. However, it is possible to
inadvertently cause the CP1613’s preset MAC address to be overwritten.
If the SIMATIC NET utility “SET PG/PC INTERFACE” is used to check the
configuration of the CP1613, the following screen will be shown:
PCS 7/505 Channel
A5E00767204-01 4-3
Configuring the CP1613 Card
For the MAIN CP1613, the “Access Point” will be “CP_H1_1: ÆCP1613(ISO)”. The
ALT CP1613 is indicated by the “Access Point” of “CP_H1_2: ÆCP1613(ISO)”. If
“Properties” is selected, the following screen is shown:
PCS 7/505 Channel
4-4 A5E00767204-01
Configuring the CP1613 Card
The MAC address field is shown. This field should not be edited! If the property page for
“TF Protocol” is selected, the following screen is shown:
PCS 7/505 Channel
A5E00767204-01 4-5
Configuring the CP1613 Card
The settings on this page should not be edited! If this page is dismissed with any
choice other than CANCEL, the following message box will appear:
The correct selection is NO. However, if YES is selected, the following screen appears:
PCS 7/505 Channel
4-6 A5E00767204-01
Configuring the CP1613 Card
The MAC address will now be either 08-00-06-XX-A1 for the MAIN CP1613, or 08-00-
06-XX-A2 for the ALT CP1613. The XX value will vary depending upon the “TF HOST
NAME” configured in the PCS7 TF Channel “System Properties” (selected from WinCC
Explorer, “Tag Management”). These default MAC address values should never be
applied. If they were applied then it might be possible to have duplicate MAC
addresses on the network (for the case of different servers using the same XX value).
If either of these MAC addresses appears in the field, the field should be deleted:
PCS 7/505 Channel
A5E00767204-01 4-7
Configuring the CP1613 Card
After deleting the field, select OK and the following message box appears:
Select OK and then restart the system. However, if PCS7 is not in runtime then it is
possible to select the MODE property page and to manually restart the CP1613
immediately:
PCS 7/505 Channel
4-8 A5E00767204-01
Configuring the CP1613 Card
PCS 7/505 Channel
A5E00767204-01 4-9
Configuring the CP1613 Card
4.2 Using the Configuration Console
Another utility which can be used to specify the CP_H1_1 and CP_H1_2 settings is the
Configuration Console. The only required configuration needed here is made under the
Access Points setting. Follow these steps:
1. From the Windows START menu, select Start > SIMATIC > SIMATIC NET >
Settings > Configuration Console.
-
2. Double-click on Access points to display the entire list in a single view.
3. To change an access point, double-click the point. Only the CP_H1_1 and
CP_H1_2 access points are applicable for the SIMATIC 505 CP1434TF RBE
channel.
PCS 7/505 Channel
4-10 A5E00767204-01
Configuring the CP1613 Card
4. The CP_H1_1 and CP_H1_2 access points must be assigned to a CP1613(ISO)
interface. For example, assign CP_H1_1 to CP1613(ISO) and assign CP_H1_2 to
CP1613(ISO)<Board 2>.
PCS 7/505 Channel
A5E00767204-01 4-11
Configuring the CP1613 Card
4.3 Requirements for 505 Communications
The PCS7 505 system requires the CP1613 to run in the mode setting for "PG
Operation". This mode setting is required in order to run the "TF Protocol"
communications interface. This interface utilizes the "local database" (LDB) that is built
automatically by the PCS7 505 "SIMATIC 505 CP1434 TF RBE" channel. The "TF
Protocol" is a layer 4 (ISO), MAC addressed based protocol. It is the only protocol
supported by the 505 plc's CP1434TF module. It is also the only protocol supported by
the "SIMATIC 505 CP1434 TF RBE" channel for the PCS7 505 system.
The "SIMATIC 505 CP1434 TF RBE" channel must use the CP1613 Ethernet card for
its TF Communications. This is the only Ethernet card that can be used for 505
communications.
A PCS7 505 server with one CP1613 will use the Simatic Net Access point named
"CP_H1_1:" (that is assigned to the "CP1613(ISO)" interface). A PCS7 505 server with
two CP11613s where both of the CP1613s are used for 505 TF communications will
have the second card set to use the Simatic Net Access point named "CP_H1_2:" (that
is assigned to "CP1613(ISO)<board 2>" interface).
4.4 Using Both S7 and 505 Controllers
In order to communicate with S7 PLCs on a PCS7 505 server, you need to assign the
S7 plc communications to use separate Ethernet card(s). This is required since the S7
communications must run in an Ethernet card that has been set to the "Configured
Mode". The configured mode is required in order for the Simatic Manager NETPRO
utility to download the "system database" (SDB) to the server's Ethernet card.
Communications to the S7 can be configured to use a CP1613 and also other non-
Siemens Ethernet cards. Refer to the documentation for the S7 channel for more
information.
PCS 7/505 Channel
4-12 A5E00767204-01
5 Connection Properties
5.1 Channel Connection Configuration
The channel connection actually has two separate names that can be configured freely
to be the same or different. The first name shown on the General configuration screen
is the PCS 7 connection name. The name shown on the Properties > Connection
screen is the TF Name that is used only for the configuration of the connections (in the
505 CP1434TF module). Both the channel’s TF Host Name and the separate
connection name have been purposely provided to make it easy for a PCS 7 system
to "take over" and replace an existing OSx system without having to reconfigure the
505 CP1434TF modules. However, if the PCS 7 system and OSx system must both
run during a change-over, then new connections in the CP1434TF modules must be
configured for the PCS 7 system.
Test of Connection Configuration
First, make sure that you have configured the following components:
xA TF Host Name for the channel
xAll of the channel connections
xEach of the 505 CP1434TF modules
PCS 7/505 Channel
A5E00767204-01 5-1
Connection Properties
Then take the channel to runtime. You can use the WinCC Tool called Channel
Diagnosis to verify that the connections are established.
If the connections fail to appear with the green check mark, then it is likely that the
configuration of the CP1613 module does not agree with the corresponding
configuration in the 505 CP1434TF module.
You can use the Set PG-PC Interface utility to check the connection configuration
independently. Follow these steps:
1. From the Windows START menu, select Start > SIMATIC > SIMATIC NET >
Settings > Set PG-PC Interface.
2. Select an access point (for example, CP_H1_1:CP1613(ISO)).
PCS 7/505 Channel
5-2 A5E00767204-01
Connection Properties
3. Click the Diagnostics button to display the following screen.
4. Click the TF Protocol tab.
Either one or two notice or warning windows appear. Select OK to dismiss each window.
PCS 7/505 Channel
A5E00767204-01 5-3
Connection Properties
The TF Protocol dialog appears. Click the Test button on this window.
The test should show the Node name which matches your channel configuration of the
TF Host Name and the Association count should match the number of channel
connections configured for the network. Use the slider to scroll down the list of
connections. If the text active appears, then the CP1613 has successfully established
a connection to the CP1434TF.
However, if the text establish appears, the connection remains in the establish mode
and is not becoming active, most likely due to an incorrect configuration in either the
CP1434TF or in the SIMATIC 505 CP1434TF RBE channel, such that the two
configurations are not in agreement. If you have more than one CP1613, then
establish could appear if the network cables are connected to the wrong CP1613.
(Reverse the cable connections and check again.)
PCS 7/505 Channel
5-4 A5E00767204-01
Connection Properties
PCS 7/505 Channel
A5E00767204-01 5-5
Connection Properties
PCS 7/505 Channel
5-6 A5E00767204-01
6 OSx Compatibility
The Report by Exception (RBE) functionality is implemented as a managed resource
between the 505 controller and a host system. The host downloads a set of RBE
definitions for the 505 controller to monitor and to provide notifications of data changes.
Each RBE definition must have a unique identifier that is used to associate the data
values within the notifications.
Whenever more than one host system is simultaneously performing RBE to the same
505 controller, conflicts in management of the RBE resource and the set of RBE
definitions are likely to occur. Special changes have been made only for the OSx
4.1.2A release to handle these conflicts. This is the only OSx release capable of
running RBE at the same time as the PCS 7 SIMATIC 505 CP1434TF RBE channel.
Any earlier release of OSx must have settings manually applied to force RBE to be
disabled. An OSx release older than OSx 4.1.2A running RBE at the same time as the
PCS 7 SIMATIC 505 CP1434TF RBE can have adverse effects on both systems.
6.1 Pre-OSx 4.1.2A Must Not Use RBE
A special patch diskette has been created for use on the OSx releases of 3.1.2A
through 4.1.1. This patch diskette can be obtained from the Siemens hotline. It is the
OSx patch name DEX20270. If your OSx release is earlier than 3.1.2A, you will need
to contact the Siemens hotline for the procedure to disable RBE.
If you must run OSx at the same time as the PCS 7 505 channel and you do not have
the DEX20270 patch, you can manually make the OSx database change that the patch
diskette makes. The following manual procedure is applicable only for OSx releases
3.1.2A through 4.1.1.
If you have the patch DEX20270, apply it with the same procedure as any OSx patch.
If you do not have the patch, then carefully follow the detailed steps discussed below.
Of course, using the patch is highly recommended.
PCS 7/505 Channel
A5E00767204-01 6-1
OSx Compatibility
The OSx database change is in the CONFIG relation for the record having a KEY=48.
This record needs to have its VALUE changed from 0 to 1. This change assumes that
another CONFIG record having KEY=47 is still set to its default value of 1. You can
login to Unix as the "tistar" user on each node of your OSx system and make the
change when OSx is in an OFFLINE state. The preferred method is to make the
change once on a SYSADMIN node, change it to the PRIMARY and then SYNC your
other nodes to it. Follow these steps:
1. At the Unix command line, type mnu and press Enter to execute the OSx menu
utility.
2. Next type ret and press Enter.
3. At the prompt for Relation, type 11 and press Enter.
4. At the prompt for Attribute, type key and press Enter.
5. At the prompt for Operator, press Enter.
6. At the prompt for Value, type 48 and press Enter.
7. At the prompt for Do you want…, press Enter. The current database record is
displayed.
8. At the prompt for <Record number nnn>, remember the value shown and press
Enter.
9. Now back at the prompt for Choose one of the menu items, type rep and press
Enter.
10. At the prompt for Relation, type 11 and press Enter.
11. At the prompt for Record, type the value previously displayed to you as <Record
number nnn>, and press Enter.
12. At the line showing TYPE=2 followed by a line for New Value, press Enter.
13. At the line showing VALUE=0 followed by a line for New Value, you change the
current value from 0 to 1. Type 1 and press Enter.
14. At the line showing DESCRIPTOR followed by a line for New Value, press Enter.
You have now completed the database change.
PCS 7/505 Channel
6-2 A5E00767204-01
OSx Compatibility
6.2 OSx 4.1.2A Can Use RBE
Changes have been made to OSx 4.1.2A to permit it to share the RBE resource and
the RBE definitions with a PCS 7 system. In order for this to work as intended, the tag
files used to install the tags in PCS 7 must come directly from OSx 4.1.2A (instead of
from APT). In OSx 4.1.2A, you use the OSx menu bar command for Tags->Save from
OSx to File to get the install.tag file written to a diskette.
OSx 4.1.2A also includes changes to make its management and usage of RBE
compatible with the PCS 7 usage of RBE. When the PCS 7 tags have been installed
with tags from the OSx file, they will have the same RBE definitions such that a given
RBE identifier is the same on both systems. In this case, there is only a single RBE
definition for this given RBE identifier in the 505. As OSx and PCS 7 are maintained
independently, you might eventually make configuration changes which result in
different RBE identifiers used on each system. These RBE might either be distinct
identifiers used on only one of the systems, or else they might be the same RBE
identifier used for different tags on each system. In any event, the RBE management
on each system recognizes and handles its own RBE. For instance, any conflicting
RBE identifier is kept by the originating host which defines it first in the 505 controller,
and the other system will automatically handle it as a scanned value rather than as an
RBE value.
When two systems have separate RBE identifiers, the space required in the 505
controller to hold the RBE definitions will increase. For this reason, you might need to
leave more 505 memory unassigned in order to make it available for RBE. The 505
controller has default storage for RBE sized to hold approximately 500 RBE definitions.
When more space is needed, then APT or TISOFT can be used to make the memory
configuration change.
Another change has been made to OSx 4.1.2A to easily turn off RBE on a 505
controller basis. This is done from the OSx Network Setup utility (in the Offline state)
by selecting a Control Node to MODIFY and then changing its value for RBE
DELIVERY to zero. This causes OSx to not use RBE for the 505 controller.
OSx 4.1.2A was changed to easily allow RBE to run as a new PCS 7 system is being
installed as an upgrade to an existing OSx system. OSx 4.1.2A has also been modified
to easily turn off RBE. A special patch for releases prior to OSx 4.1.2A has also been
provided to make it easy to turn off RBE for the older OSx releases to take care of the
customers who wish to now upgrade directly to PCS 7 without having to further
upgrade their OSx release first.
PCS 7/505 Channel
A5E00767204-01 6-3
OSx Compatibility
PCS 7/505 Channel
6-4 A5E00767204-01
7 Remarks on 505 Utilities
The 505 utilities of TISOFT, APT, and the H1 Configurator should not be run on the
PCS 7 server system. These utilities should only be run from an existing Windows
system where they are already installed (such as on a laptop). Attempts to run these
utilities on the PCS 7 server system will impair the performance of the PCS 7 system
and possibly the 505 utility itself. In particular, the PCS 7 system is designed for
exclusive use of the CP1613 interface. If a 505 utility is using the CP1613, it will lock
the card and prevent the 505 channel from operating. It is also not advisable to run any
505 utility even as a serial connection for performance reasons, particularly when in a
constant debug/status update mode.
The SIMATIC 505 CP1434TF RBE channel automatically builds its own local database
(LDB) file for each CP1613 it uses (for its MAIN network and optionally, a second ALT
network). For this reason, there is no need to do any configuration of connections
using the SIMATIC NET utility provided for "Configuring with COML TF".
The SIMATIC 505 CP1434TF RBE channel not only builds the LDB files, but it also
restarts and resets the CP1613 cards whenever a change to the LDB file has occurred.
The LDB will only change if a channel UNIT or CONNECTION property has changed.
PCS 7/505 Channel
A5E00767204-01 7-1
Remarks on 505 Utilities
PCS 7/505 Channel
7-2 A5E00767204-01
