Siemens 3964R User Manual
Wonderware Siemens 3964R
I/O Server
User’s Guide
Revision S
June 2002
Wonderware
All rights reserved. No part of this documentation shall be reproduced, stored in a
retrieval system, or transmitted by any means, electronic, mechanical, photocopying,
recording, or otherwise, without the prior written permission of the Invensys Systems,
Inc. No copyright or patent liability is assumed with respect to the use of the information
contained herein. Although every precaution has been taken in the preparation of this
documentation, the publisher and the author assume no responsibility for errors or
omissions. Neither is any liability assumed for damages resulting from the use of the
information contained herein.
The information in this documentation is subject to change without notice and does not
represent a commitment on the part of Invensys Systems, Inc. The software described in
this documentation is furnished under a license or nondisclosure agreement. This
software may be used or copied only in accordance with the terms of these agreements.
2002 Invensys Systems Inc. All Rights Reserved.
Invensys Systems, Inc.
33 Commercial Street
Foxboro, MA 02035
(949) 727-3200
http://www.wonderware.com
Trademarks
All terms mentioned in this book that are known to be trademarks or service marks have
been appropriately capitalized. Invensys Systems, Inc. cannot attest to the accuracy of
this information. Use of a term in this book should not be regarded as affecting the
validity of any trademark or service mark.
Alarm Logger, ActiveFactory, ArchestrA, Avantis, DBDump, DBLoad, DTAnalyst,
FactoryFocus, FactoryOffice, FactorySuite, hotlinks, InBatch, InControl, IndustrialRAD,
IndustrialSQL Server, InTouch, InTrack, MaintenanceSuite, MuniSuite, QI Analyst,
SCADAlarm, SCADASuite, SuiteLink, SuiteVoyager, WindowMaker, WindowViewer,
Wonderware, and Wonderware Logger are trademarks of Invensys plc, its subsidiaries
and affiliates. All other brands may be trademarks of their respective owners.
i
Contents
Introduction .............................................................................................................................1
Communication Protocols ...................................................................................................1
Accessing Remote Items via the I/O Server............................................................................2
Configuring the I/O Server......................................................................................................3
Configuring a Communication Port ........................................................................................4
Communication Port Settings..............................................................................................4
Saving the I/O Server’s Configuration File.............................................................................6
Save Configuration..............................................................................................................6
Saving Multiple Configuration Files ...................................................................................6
Configuring a Topic Definition ...............................................................................................7
Topic Definition ..................................................................................................................7
S3964R Topic Definition ....................................................................................................8
Configuring the I/O Server Settings ......................................................................................10
Server Settings................................................................................................................... 10
Accessing I/O Server Help .................................................................................................... 12
Contents.............................................................................................................................12
How to Use Help ............................................................................................................... 12
About S3964R ...................................................................................................................12
Item Names (S5 Item Syntax)................................................................................................13
Data Blocks/Extended Range Data Blocks....................................................................13
Flags ..............................................................................................................................14
Inputs .............................................................................................................................14
Outputs ..........................................................................................................................15
System Data Area ..........................................................................................................15
Absolute Address...........................................................................................................16
Timers............................................................................................................................ 16
Counters.........................................................................................................................16
Item/Point Naming Examples............................................................................................17
Item Names (S7 Item Syntax)................................................................................................18
Data Blocks ...................................................................................................................18
Flags ..............................................................................................................................19
Inputs .............................................................................................................................20
Outputs ..........................................................................................................................21
Timers............................................................................................................................ 21
Counters.........................................................................................................................21
Item/Point Naming Examples............................................................................................22
Monitoring the Status of Communications with a PLC.........................................................23
ii
Using the Status Item in Excel.......................................................................................... 23
Monitoring the Status of Communications with InTouch..................................................... 23
Using DDEStatus and IOStatus in Excel .......................................................................... 23
Reading Values from the I/O Server into Excel.................................................................... 24
Writing Values to the I/O Server from Excel ....................................................................... 25
Troubleshooting I/O Server Communication Problems........................................................ 26
Debugging Communication Between InTouch and an I/O Server ................................... 26
Debugging Communication Between SuiteLink and an I/O Server ................................. 28
Debugging Communication Between an I/O Server and a PLC....................................... 29
Special Wonderware Logger Messages ................................................................................ 36
Siemens REPTEL Errors .............................................................................................. 36
1
Wonderware Siemens
3964R I/O Server
Introduction
The Wonderware
remainder of this user’s guide) is a Microsoft
as a communication protocol server. It allows other Windows application programs
access to data within the SIMATIC S5 and S7 family of PLCs (also referred to as
devices). The server allows the PC to access a Siemens PLC through a CPU or CP
which supports the 3964R protocol with RK512. While the server is primarily intended
for use with Wonderware InTouch
Microsoft Windows program capable of acting as a DDE, FastDDE, or SuiteLink
client.
Communication Protocols
Siemens 3964R I/O Server (referred to as the server through the
(version 3.01 or later), it may be used by any
Windows application program that acts
Dynamic Data Exchange (DDE) is a communication protocol developed by Microsoft
to allow applications in the Windows environment to send/receive data and instructions
to/from each other. It implements a client-server relationship between two concurrently
running applications. The server application provides the data and accepts requests
from any other application interested in its data. Requesting applications are called
clients. Some applications such as InTouch and Microsoft Excel can simultaneously be
both a client and a server.
FastDDE provides a means of packing many proprietary Wonderware DDE messages
into a single Microsoft DDE message. This packing improves efficiency and
performance by reducing the total number of DDE transactions required between a
client and a server. Although Wonderware's FastDDE has extended the usefulness of
DDE for our industry, this extension is being pushed to its performance constraints in
distributed environments.
NetDDE
over local area networks and through serial ports. Network extensions are available to
allow DDE links between applications running on different computers connected via
networks or modems. For example, NetDDE supports DDE between applications
running on IBM
applications running on non-PC based platforms under operating environments such as
VMS
extends the standard Windows DDE functionality to include communication
compatible computers connected via LAN or modem and DDE-aware
and UNIX.
2
SuiteLink uses a TCP/IP based protocol and is designed specifically to meet industrial
needs such as data integrity, high-throughput, and improved diagnostics. This protocol
standard is only supported on Microsoft Windows NT 4.0 and Windows 2000.
SuiteLink is not a replacement for DDE, FastDDE, or NetDDE. The protocol used
between a client and a server depends on your network connections and configurations.
SuiteLink was designed to be the industrial data network distribution standard and
provides the following features:
• Value Time Quality (VTQ) places a time stamp and quality indicator on all data
values delivered to VTQ-aware clients.
• Extensive diagnostics of the data throughput, server loading, computer resource
consumption, and network transport are made accessible through the Microsoft
Windows NT and Windows 2000 operating systems Performance Monitor. This
feature is critical for the scheme and maintenance of distributed industrial
networks.
• Consistent high data volumes can be maintained between applications regardless if
the applications are on a single node or distributed over a large node count.
• The network transport protocol is TCP/IP using Microsoft’s standard WinSock
interface.
Accessing Remote Items via the I/O Server
The communication protocol addresses an element of data in a conversation that uses a
three-part naming convention that includes the application name, topic name and item
name. The following briefly describes each portion of this naming convention:
application name The name of the Windows program (server) that will be
accessing the data element. In the case of data coming from
or going to Siemens equipment via this server, the
application portion of the address is S3964R.
topic name Meaningful names are configured in the server to identify
specific devices. These names are then used as the topic
name in all conversations to that device. For example,
S115U.
Note You can define multiple topic names for the same
device (PLC) to poll different points at different rates.
item name A specific data element within the specified topic. For
example, when using this server, an item can be a relay,
timer, counter, register, etc., in the PLC.
Note The item/point names are predefined by the server.
The term "point" is used interchangeably with the term
"item" in this user's guide.
For more information on item/point names, see the
“Item Names" section later in this user's guide.
3
Configuring the I/O Server
Once the server has been installed, a small amount of configuration is required.
Configuring the server automatically creates a configuration file named S3964R.CFG.
This file stores the configuration information for the adapter cards or communication
ports and all of the topic definitions (described in detail later).
The configuration file is automatically saved to the directory in which the server is
installed unless a different directory is specified.
To perform the required configurations, start up the server
by double-clicking on its icon. If the server starts up as an
icon, double-click on the icon to open the server's window.
To access the options used for the various configurations, open the Configure menu:
Note If any of the options appear grayed, then these options are not available with this
software version.
4
Configuring a Communication Port
Use the Communication Port Settings option from the Configure Menu to configure
the communication ports that will be used for communication with Siemens devices.
When this option is selected, this dialog box will appear:
Communication Port Settings
Note All communication ports can be configured without leaving this dialog box.
Repeat these steps; select a COM Port, set configuration, and click Save.
Select a communication port connected to the Siemens device.
Enter the amount of time (in seconds) that all PLCs connected via this communication
port will be given to reply to commands from the server.
Note This timeout is sustained only when the PLC fails to respond. When the PLC is
responding normally, there is no penalty. The default value of 1 second should be
sufficient for most configurations.
Select the Baud Rate (serial bit rate) setting that matches the configuration of the
Siemens device.
5
Select the number of Data Bits that matches the configuration of the Siemens device.
Select the number of Stop Bits that matches the configuration of the Siemens device. If
the Baud Rate is greater than 300, the Stop Bits should be set to 1.
Select the Parity setting that matches the configuration of the Siemens device.
All devices on a single communication port must be configured with the same Baud
Rate, Data Bits, Stop Bits, and Parity.
Click Defaults to reset the settings to their default values without saving changes.
Click Save to save settings for the selected COM Port. The dialog box will remain
displayed giving you the option to configure additional COM Ports.
Click Done to close the dialog box. If the settings have not been saved, the following
dialog box will appear:
Click Yes to save settings for the COM Port.
Click No to prevent saving the settings.
Click Cancel to return to the Communication Port Settings dialog box without saving
the settings.
Note For most of these settings only one setting is allowed. All other possibilities are
disabled.
6
Saving the I/O Server’s Configuration File
If a configuration file does not currently exist in the configuration file directory, the
server will automatically display the Save Configuration dialog box:
Save Configuration
This field displays the drive\directory into which the server will save the current
configuration file. To save the configuration file to a different directory, enter the path
for that directory in this field.
This option is selected and disabled on initial entry to the Save Configuration dialog
box. This field becomes active if the Configuration File Directory is changed. Once
enabled, selecting this option will record a new Configuration File path in the WIN.INI
file. This option allows the server to find its configuration file automatically each time
it is started.
Note When the server initially starts up, it attempts to locate its default configuration
file by first checking the WIN.INI file for a previously specified path. If a path is not
present in the WIN.INI file, the server will assume that the current working directory is
to be used.
Click Defaults to reset the settings to their default values without saving changes.
Click OK to save the configuration file to the specified directory.
Saving Multiple Configuration Files
There is no limit to the number of configuration files that you can create as long as they
are saved in separate directories. However, all cfg files must have the name
S3964R.CFG. This allows you to have multiple configuration files that can be accessed
by using a special switch (/d:). For example, to start the server using a configuration
file located in a different directory, click the Start button on the Taskbar, then choose
Run and enter the following in the Open combo box:
S3964R /d:c:\directoryname
7
Configuring a Topic Definition
Use the Topic Definition option from the Configure menu to create new, modify, or
delete topic definitions. One or more topic definitions must exist for each PLC that the
server will communicate with. Each topic definition must contain a unique name for
the PLC associated with it. When this option is selected, the Topic Definition dialog
box will appear:
Topic Definition
Note Once topics have been defined, their names will be listed in the Topics section of
this dialog box.
Click this button to close the dialog box and accept any new definitions, modifications
or deletions made.
To modify or view an existing topic definition, select its name in the list and click on
this button. The S3964R Topic Definition dialog box (described below) will appear
displaying the selected topic definition.
To delete an existing topic definition, select its name in the list and click on this button.
(A message box will appear prompting you to confirm the deletion.)
To add a new topic definition, click on this button. The S3964R Topic Definition
dialog box will appear:
8
S3964R Topic Definition
Enter a unique name (up to 32-characters long with the first character being alphabetic)
for the PLC in this field.
Note When communicating with InTouch, this exact name is used as the topic name in
the Access Name definition.
The communications port currently associated with this topic will appear in this field.
To select a different port, click on the down arrow to open the list of communication
ports. Click on the name of the communications port to be associated with this topic.
Enter the address on the communications card in the PLC chassis.
Enter the frequency (in milliseconds) that the server will read (poll) the items/points
associated with this topic.
Set the option S7 Item Syntax on if you want to use this syntax insted of S5 Item syntax
(e.g. if connecting to Step 7 PLC’s).
Loading...