Related Manuals for Siemens 3964R
Summary of Contents for Siemens 3964R
- Page 1 Wonderware Siemens 3964R I/O Server User’s Guide Revision S June 2002 Wonderware...
- Page 2 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.
-
Page 3: Table Of Contents
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... - Page 4 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...
-
Page 5: Introduction
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 ... -
Page 6: Accessing Remote Items Via The I/O Server
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. -
Page 7: Configuring The I/O Server
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. -
Page 8: Configuring A Communication Port
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. - Page 9 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.
-
Page 10: Saving The I/O Server's Configuration File
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. -
Page 11: Configuring A Topic Definition
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. -
Page 12: S3964R Topic Definition
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. - Page 13 Set the option Optimized Writes on if you want to increase the speed of poking and don’t need to retain the poke order. Set the option Forced Read Modify Write on if you want to have a polling before every poke of Bits or Bytes.
-
Page 14: Configuring The I/O Server Settings
Configuring the I/O Server Settings Use the Server Settings option from the Configure menu to change the protocol timer, network using Wonderware NetDDE, change the default configuration file path, or to enable the server to start automatically as a Windows NT service. Note When configuring the server on Windows NT, the user must be logged on with system administrator privileges. - Page 15 Enabling this option will cause the server to start as a Windows NT service. Windows NT offers the capability of running applications even when a user is not logged on to the system. This is valuable when systems must operate in an unattended mode.
-
Page 16: Accessing I/O Server Help
Accessing I/O Server Help The Help menu contains three options that are used to access help for the server. The following briefly describes the Help menu options. Contents This option is used to display the table of contents for the Help file. How to Use Help This option is used to access a list of basic instructions for using the Help file. -
Page 17: Item Names (S5 Item Syntax)
Item Names (S5 Item Syntax) The Siemens 3964R I/O Server supports item/point names that are consistent with the point naming convention used by Siemens 3964R CPs. The tables below list the item/point names supported by the server: Data Blocks/Extended Range Data Blocks... -
Page 18: Flags
Flags Data Items Suffix Tag Type Range Format Fm.b Discrete 0 or 1 Mm.b Discrete 0 or 1 Byte Integer 0 to 255 Integer 0 to 255 Integer 0 to 255 Integer -128 to 127 Word Integer 0 to 65535 Integer 0 to 65535 Integer... -
Page 19: Outputs
Outputs Data Items Suffix Tag Type Range Format Qn.b Discrete 0 or 1 An.b Discrete 0 or 1 Byte Integer 0 to 255 Integer 0 to 255 Integer -128 to 127 Word Integer 0 to 65535 Integer 0 to 65535 Integer -32768 to 32767 Integer... -
Page 20: Absolute Address
Absolute Address Data Items Suffix Tag Type Range Format Word Integer 0 to 65535 Integer 0 to 999 Message 0.0 to 999.3 Note All Absolute Addresses are Read Only (h= 0 to FFFF (hex)). Timers Data Items Suffix Tag Type Range Format Word... -
Page 21: Item/Point Naming Examples
Item/Point Naming Examples The following examples show the correct format for item/point names: DB11DW7BCD data block 11 data word 7 value in controller is represented in BCD and has a range of -999 to 999 DX87DL14KF extended range data block 87 left byte of data word 14 value in controller is binary and has a range of -128 to 127 DB87DR14... -
Page 22: Item Names (S7 Item Syntax)
Item Names (S7 Item Syntax) The Siemens 3964R I/O Server supports the S7 item/point names that will be translated internal into S5 item/point names. This means not all S7 items/points can be used by this server. The tables below list the item/point names supported by the server:... -
Page 23: Flags
Flags Data Items Suffix Tag Type Range Format FXm.b Discrete 0 or 1 MXm.b Discrete 0 or 1 Byte Integer 0 to 255 Integer 0 to 255 FBYTEm Integer 0 to 255 MBYTEm Integer 0 to 255 Char FCHARm Integer -128 to 127 MCHARm Integer... -
Page 24: Inputs
Inputs Data Items Suffix Tag Type Range Format Im.b Discrete 0 or 1 Em.b Discrete 0 or 1 IXm.b Discrete 0 or 1 EXm.b Discrete 0 or 1 Byte Integer 0 to 255 Integer 0 to 255 IBYTEm Integer 0 to 255 EBYTEm Integer 0 to 255... -
Page 25: Outputs
Outputs Data Items Suffix Tag Type Range Format Qm.b Discrete 0 or 1 Am.b Discrete 0 or 1 QXm.b Discrete 0 or 1 AXm.b Discrete 0 or 1 Byte Integer 0 to 255 Integer 0 to 255 QBYTEm Integer 0 to 255 ABYTEm Integer 0 to 255... -
Page 26: Item/Point Naming Examples
Item/Point Naming Examples The following examples show the correct format for item/point names: DB20,X6.1 S7 item corresponds to S5 item DB20D3.9 DB20,X7.1 S7 item corresponds to S5 item DB20D3.1 DB100,B4 S7 item corresponds to S5 item DB100DL2 DB100,B5 S7 item corresponds to S5 item DB100DR2 DB100,CHAR8 S7 item corresponds to S5 item DB100DL4KF DB30,W10... -
Page 27: Monitoring The Status Of Communications With A Plc
Monitoring the Status of Communications with a PLC For each topic name (PLC), there is a built-in discrete item that can be used to monitor the status of communications with the PLC. The discrete item, Status, is set to 0 when communication with the PLC fails and is set to 1 when communication is successful. -
Page 28: Reading Values From The I/O Server Into Excel
Reading Values from the I/O Server into Excel Values may be read directly into Excel spreadsheets from the server by entering a DDE formula into a cell using the following format: =applicationname|topicname!itemname Example formula: =S3964R|S115U!DB10DW20KF where: S3964R Is the name of the server application name. S115U Is the exact topic name defined in the server for the PLC. -
Page 29: Writing Values To The I/O Server From Excel
Writing Values to the I/O Server from Excel Values may be written to the server from Microsoft Excel by creating an Excel macro that uses the POKE command. The proper command is entered in Excel as follows: channel=INITIATE("applicationname","topicname") =POKE(channel,"itemname", Data_Reference) =TERMINATE (channel) =RETURN() The following describes each of the above POKE macro statements:... -
Page 30: Troubleshooting I/O Server Communication Problems
Troubleshooting I/O Server Communication Problems This section provides you with some simple steps that can be taken to ascertain and correct communication problems. The problems described here represent the most probable causes of communication failure. Note This is a general troubleshooting guide and for the sake of brevity we cannot cover every possible source of communication problems. - Page 31 The information in the second line indicates that you have at least one I/O type tagname defined in your Tagname Dictionary that is associated with an Access Name that defines OMRONFO as the Application Name, and HLPLC as the Topic Name.
-
Page 32: Debugging Communication Between Suitelink And An I/O Server
5. If the topic name is different, either correct it in the server or switch to WindowMaker and correct it in the Access Name definition. 6. Once you performed the above procedure, restart WindowViewer and switch to the server program. Data should now appear in the server’s program window to indicate that WindowViewer and the server are communicating. -
Page 33: Debugging Communication Between An I/O Server And A Plc
Debugging Communication Between an I/O Server and a PLC This section provides you with simple steps to diagnose and correct server to PLC communication problems. The debug techniques listed below address both serial and board servers. Disregard any information that is not applicable to the server type that you are using. - Page 34 2. On Windows 3.1 or Windows for Workgroups, start the Terminal program. On Windows 95 or Windows NT, start the HyperTerminal program. 3. Configure the Terminal (or HyperTerminal) program to use the same communication port with the same settings (baud rate, parity, stop bits and so on) as the hardware device.
- Page 35 The Wonderware Web site requires that you register before you will be given access. 3. If (1. and 2.) above do not work, verify the value of the ComBoostTime parameter in your file. This parameter represents the number of milliseconds that SYSTEM a virtual machine can process a COM interrupt.
- Page 36 5. Double-click the System icon. The System Properties dialog box will appear. Click the Device Manager tab and select the COM port that you are using for the server. For example: 6. Click Properties. The Properties dialog box will appear. Click the Port Settings tab.
- Page 37 7. Click Advanced. The Advanced Port Settings dialog box appears: 8. Lower the default Receive Buffer and Transmit Buffer settings to their minimum. Lowering these settings may solve I/O communication problems for portable computers (notebook, or laptops) and framing errors for standard computers. 9.
- Page 38 Try using a different COM port for the I/O Server. If you are installing an I/O Server or configuring a board based I/O Server on a computer that is running the Windows NT operating system, verify that you are logged on with Administrator privileges. Without Administrator privileges, the server and Server Install program cannot make the necessary edits to the Windows NT Registry during installation or board configuration of the server.
- Page 39 Verify the PLC is properly configured and the cable is good by using the programming software for the PLC. When testing, run the programming software and communicate with the server at the same time. The ability to perform this test depends upon the type of PLC that you are using. Reinstall the I/O Server and verify that you are using the latest version.
-
Page 40: Special Wonderware Logger Messages
All Siemens REPTEL errors will be reported in the Wonderware Logger with the following format: Siemens CP52xREPTEL Error XXH XX is the REPTEL error number reported. Please refer to the Siemens CP52X manual for the detailed REPTEL error listings, descriptions and suggested remedies.