Wonderware Operations Integration Supervisory Texas Instruments TI500 Server (G-1.2 Series)

Similar documents
Wonderware Operations Integration Supervisory Mitsubishi Electric MELSEC Server (G-1.2 Series)

Wonderware Operations Integration Supervisory AutomationDirect ADPRO Server (G-1.2 Series)

Wonderware Operations Integration Supervisory Beckhoff TWINCAT Server (G-1.2 Series)

Device/PLC Connection Manuals

Wonderware Operations Integration - Supervisory Server Manager (G-1.2 Series) User Guide

IntelaTrac 2017 SP1 Release Notes. January 2018

CTI 2500P-ACP1 Application Coprocessor User Manual. Version 1.14

ArchestrA Log Flag Editor User s Guide Invensys Systems, Inc.

Wonderware DAServer 1.0 for Mitsubishi Ethernet User s Guide

Wonderware DAServer 1.0 for Omron FINS Ethernet User s Guide

Object Viewer User s Guide

Wonderware DAServer for Omron FINS Ethernet User s Guide

Wonderware Operations Integration Supervisory BACnet/IP BACLITE Server (G-1.2 Series)

Wonderware. Historian Server. Scenarios Guide. Version January 2016

Wonderware DAServer for Omron FINS Serial User s Guide

Wonderware Wonderware ArchestrA License Manager Guide

ArchestrA Web Exporter Guide

Historian Administration Guide

Wonderware Operations Integration - Supervisory SIDirect Server (G-1.1 Series)

Wonderware SmartGlance

TIWAY Host Adapter Driver Help Kepware Technologies

Wonderware FactorySuite

Wonderware. Historian Server. Glossary. Version January 2016

Course Description. InBatch Software

Wonderware Information Server Win-XML Exporter User s Guide. Invensys Systems, Inc.

INTRODUCTION... 2 GENERAL INFORMATION... 3 DEVICE CHARACTERISTICS... 3 LINK CHARACTERISTICS... 3 DRIVER CHARACTERISTICS... 4 CONFORMANCE TESTING...

Simatic / TI 505 Ethernet Driver PTC Inc. All Rights Reserved.

InTouch Access Anywhere User Guide

Contrex M-Series Driver Help Kepware Technologies

Contents. IDEC Communication Driver. Driver for Serial communication with Devices using the IDEC MicroSmart Communication Protocol INTRODUCTION...

Wonderware. ABTCP DAServer User s Guide. Wonderware. Version 1.5 Last Revision: 3/21/07

Yokogawa YS100 Driver PTC Inc. All Rights Reserved.

TI NITP Driver Programmable Serial Interface Card

Yokogawa YS100 Serial Driver Help Kepware Technologies

Application Versions. Functions List. GetAlarmLogConnStatus( ) Tech Note 506 Alarm DB Logger Status Functions

7TMELFX. IGSS Mitsubishi FX-Series Interface Driver User s Manual

InBatch Installation Guide. Invensys Systems, Inc.

Tech Note 1006 Managing Symbol Script Timeouts When Using WW MES API Pop-up Dialogs

DTSX3000 Communications(Modbus) Guide

Technical Information Sheet

Tech Note 997 Setting up the InBatch 2012 R2 Batch Events Feature on a 2-Node System

Lufkin Modbus Serial Driver Help Kepware Technologies

Introduction. Application Versions. Table of Contents. $PingNode Object Template Configuration

Modbus ASCII Serial Device Driver Help 2009 Kepware Technologies

Honeywell UDC Ethernet Driver Help Kepware Technologies

Opto 22 Ethernet Driver Help Kepware Technologies

Wonderware FactorySuite

Eaton Corporation Cutler-Hammer Business Unit 811 Green Crest Drive Columbus, OH PanelMate Texas Instruments Communication Driver Manual

This document is for information purposes only and is subject to change without notice.

Cutler-Hammer D50/300 Driver PTC Inc. All Rights Reserved.

Summary. Business Value

Tech Note 715 Resolving Issues with DAServer Diagnostic Node on the Windows 2008 Operating System

Fuji Flex Driver Help Kepware Technologies

Philips P8/PC20 Driver PTC Inc. All Rights Reserved.

Information Server Administration Guide

Network Setup for AppEngine Redundancy

Proficy* Historian OPC C OLLECTOR G UIDE. Version 6.0 June 2015

AutomationDirect K Sequence Driver PTC Inc. All Rights Reserved.

Mitsubishi FX Net Driver PTC Inc. All Rights Reserved.

INTRODUCTION...2 GENERAL INFORMATION...3 DEVICE CHARACTERISTICS...3 LINK CHARACTERISTICS...3 DRIVER CHARACTERISTICS...3 CONFORMANCE TESTING...

CTI 2500 Series Controller PROGRAMMING REFERENCE MANUAL

Yokogawa YS100 Driver PTC Inc. All Rights Reserved.

Power Monitor / Power Monitor 51A. Quick guide to set up a connection with the Power Monitor devices through the Weidmüller Serial/Ethernet Converter

2014 Software Global Client Conference

2014 Software Global Client Conference

DiaLog Elite. Modbus RTU User Guide. Publish Date: January 1, 2005 Document Version 1.2

CTI 2500 Series Processor Firmware Revision History

Rotork Pakscan Driver for DeltaV Programmable Serial Interface Card

Yokogawa HR Driver PTC Inc. All Rights Reserved.

Siemens S7-200 Driver PTC Inc. All Rights Reserved.

For more information Contact with details of the application.

EGW1-IA3-MB User s Manual

7TS7TCP. IGSS Siemens S7 TCP/IP Interface Driver. User s Manual

Fuji Flex Driver PTC Inc. All Rights Reserved.

Siemens S7 MPI Driver PTC Inc. All Rights Reserved.

Tech Note 710 Wonderware MES Operations Capability Object: Configuring Rolling Counter Reset

Tech Note 680 Configuring ActiveFactory for ArchestrA License Server Communication Across a Firewall

Wonderware InTouch Client Driver Help Kepware Technologies

This document is for information purposes only and is subject to change without notice.

Telemecanique Uni-Telway Driver PTC Inc. All Rights Reserved.

Tech Note 920 Resolving Disabled ActiveFactory Reporting Website for Wonderware System Platform R2

Alstom Redundant Ethernet Driver Help Kepware Technologies

Technical Information Sheet

DCON Communication Driver

7TS7TCP (Driver 72) IGSS Siemens S7 TCP/IP Interface Driver. User s Manual

Tech Note 901 Configuring Smart Card Authentication for ArchestrA System Platform 2012

B series Controller Communications VI Library

Tech Note 892 Configuring Microsoft SQL Server 2008 Express Server Authentication for Use with InTouch Alarm DB Logger

CTI 2500 Series Processor Firmware Revision History

Omron Toolbus Driver Help Kepware Technologies

HydroComp LAN-Floating License: Server and Client Installation Copyright 2018 HydroComp, Inc. All Rights Reserved.

ABB Modbus RTU Driver for JMobile

PLC Workshop Suite for CTI 2500 Series Product Bulletin: Enhanced Instructions

Analog Devices Driver Kepware, Inc.

W600/W900 Modbus. Instruction Manual

Modbus Unsolicited Serial Driver PTC Inc. All Rights Reserved.

Communication Driver DCON

Wonderware InTouch HMI Getting Started Guide

Tech Note 751 Installing InBatch Report Contents for Wonderware Information Server (WIS)

Industrial-Automation System HIMatrix. MODBUS Master/Slave. Manual

Transcription:

Wonderware Operations Integration Supervisory Texas Instruments TI500 Server (G-1.2 Series)

Contents Contents WONDERWARE OPERATIONS INTEGRATION - SUPERVISORY TEXAS INSTRUMENTS TI500 SERVER (G-1.2 SERIES)...3 Legal Information...4 Technical Support... 5 Introduction to the TI500 OI Server...6 Configuring the TI500 OI Server...7 Direct Serial Communication and Serial Encapsulation...7 Configuring a Channel's Communication Settings... 8 Setting a Device's Station ID...8 TI500 OI Server Reference...10 Item Reference Syntax... 10 Address Descriptions...11 Supported Data Types... 13 Examples of Item References...13 TI500 OI Server Error Codes...14 Page 2

Wonderware Operations Integration - Supervisory Texas Instruments TI500 Server (G-1.2 Series) This document describes the technical specifications and configuration options for the Wonderware Operations Integration - Supervisory Texas Instruments TI500 Server (or TI500 OI Server, for short). Last revision 2016-05-27 Page 3

Legal Information 2016 Schneider Electric Software, LLC. 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 Schneider Electric Software, LLC. No liability is assumed with respect to the use of the information contained herein. Although precaution has been taken in the preparation of this documentation, Schneider Electric Software, LLC assumes no responsibility for errors or omissions. The information in this documentation is subject to change without notice and does not represent a commitment on the part of Schneider Electric Software, LLC. The software described in this documentation is furnished under a license agreement. This software may be used or copied only in accordance with the terms of such license agreement. ArchestrA, Avantis, DYNSIM, EYESIM, InBatch, InduSoft, IntelaTrac, InTouch, PIPEPHASE, PRO/II, PROVISION, ROMeo, Schneider Electric, SIM4ME, SimCentral, SimSci, Skelta, SmartGlance, Spiral Software, VISUAL FLARE, WindowMaker, WindowViewer, and Wonderware are trademarks of Schneider Electric SE, its subsidiaries, and affiliated companies. An extensive listing of Schneider Electric Software, LLC trademarks can be found at: http://software.invensys.com/legal/trademarks/. All other brands may be trademarks of their respective owners. Schneider Electric Software, LLC 26561 Rancho Parkway South Lake Forest, CA 92630 U.S.A. (949) 727-3200 http://software.invensys.com/ For comments or suggestions about the product documentation, send an e-mail message to ProductDocumentationComments@schneider-electric.com. Page 4

Technical Support Wonderware Technical Support offers a variety of support options to answer any questions on Wonderware products and their implementation. Before you contact Technical Support, refer to the relevant section(s) in this documentation for a possible solution to the problem. If you need to contact technical support for help, have the following information ready: The type and version of the operating system you are using. Details of how to recreate the problem. The exact wording of the error messages you saw. Any relevant output listing from the Log Viewer or any other diagnostic applications. Details of what you did to try to solve the problem(s) and your results. If known, the Wonderware Technical Support case number assigned to your problem, if this is an ongoing problem. Page 5

Introduction to the TI500 OI Server These are the technical specifications for Wonderware Operations Integration - Supervisory Texas Instruments TI500 Server. Requirements TI500 OI Server requires Wonderware Operations Integration Core G-1.2 or later. Supported hardware and software This OI Server connects to the following 500 Series PLCs from Texas Instruments (Siemens): TI545 TI565 TI575 CTI2500 For RS 232/Ethernet communication, CTI2500-C100 PLCs can use either the TBP or NITP. (The specific protocol can be selected in the communication settings.) To program CTI2500-C100 PLCs, you need PLC WorkShop Suite for Siemens 505. For more information, go to: www.fast-soft.com/page.php?20 Conformance The following hardware and software was used for conformance testing of this OI Server. Configuration #1: Device: CTI2500-C100 PLC with PLC WorkShop Suite for Siemens 505 Module Port: 1505 Module IP Address: 10.13.63.161 Protocol: NITP Serial Encapsulation mode: Ethernet Page 6

Configuring the TI500 OI Server Each server instance has its own hierarchy of objects, and each object has parameters that you need to configure in order to establish communication between the OI Server and individual devices on the network. You can view a TI500 server instance's configuration hierarchy under its Configuration node. This section only describes how to configure object parameters for a TI500 server instance. For more general information about adding and configuring objects, see "Configuring Your OI Server" in the Operations Integration Server Manager Help. Direct Serial Communication and Serial Encapsulation This OI Server supports direct serial communication with the target device, as well as serial encapsulation over a TCP/IP or UDP/IP network link. Direct serial communication requires that the target device be directly connected to the computer that is running this OI Server. If you plan to use direct serial communication, you need to know the serial communication settings (e.g., baud rate, parity, etc.) that have been configured on the device, because you must configure this OI Server to match those settings. Serial encapsulation enables serial communication with a target device that is connected to a terminal server on your TCP/IP or UDP/IP network. The terminal server is like a virtual serial port: it converts TCP or UDP messages to serial data and then relays them to the connected device. If you plan to use serial encapsulation, the target device should already be connected to the terminal server, and you need to know the IP address of the terminal server and the port number assigned to the device. Serial encapsulation over a TCP/IP or UDP/IP link All of the serial communication settings are included in the OI Server's channel parameters. To configure the serial communication settings for a channel: 1. In the Operations Integration Server Manager, navigate to the ChannelSelector object that you want to configure: a) Expand the Operations Integration Server Manager, expand the node group, expand Local (or the remote computer name), and then expand Operations Integration Supervisory Servers. b) Locate and expand Texas Instruments - TI500, and then expand its Configuration node. c) Select the ChannelSelector object that you want to configure. The channel parameters are displayed in the details pane on the right. 2. In the Serial Encapsulation box, select the encapsulation mode: Option Description None TCP/IP UDP/IP Direct serial communication with the device. Serial encapsulation over a TCP/IP Ethernet connection. Serial encapsulation over a UPD/IP Ethernet connection. 3. If you selected None above, configure the direct serial communication settings: a) In the COM box, select the COM port to which the target device is connected. Page 7

b) In the Baud Rate, Data Bits, Stop Bits, and Parity boxes, configure the serial communication settings to match the settings that have already been configured on the target device. 4. If you selected either TCP/IP or UDP/IP above, configure the serial encapsulation settings: a) In the IP Address box, type the IP address of the terminal server. b) In the Port Number box, type the port number on the terminal server that has been assigned to the target device. c) If you want to make the target device responsible for establishing communication with this OI Server, select Server Mode. Note: This option is not available for UDP/IP. 5. Proceed with configuring the rest of the channel parameters, as described in this documentation. Configuring a Channel's Communication Settings Configure the communication settings for a selected channel to ensure uninterrupted communication with the device network. Write word bits An option to allow or disallow writing to individual bits of a Word. Select one of the following: Value Option Description 0 No Do not allow writing to individual bits. 1 Yes Allow writing to individual bits. Protocol The specific transport protocol to be used. Select one of the following: Value Option Description 0 TBP Transparent Byte Protocol 1 NITP Non-Intelligent Terminal Protocol Signed or Unsigned Value Max Block Size Advanced Whether register values are unsigned or signed by default. Select either Signed or Unsigned. The maximum number of bytes that will be requested from the device in a single read operation. You can type any value from 0 to 64, but the defalult value is 7. Click this button to open the Advanced Settings dialog box, which provides access to additional communication settings such as timeouts, retries, and buffer sizes. You might need to change these settings if the DAServer behaves unexpectedly during run time, but the default settings should work for most network configurations. For more information about these settings, see "Advanced Settings" in Operations Integration Server Manager Help. Setting a Device's Station ID Set the station ID for a selected device so that the OI Server can identify and communicate with it on the network. Syntax A station ID is required only for Ethernet encapsulation. In other words, it is required only if both of the following conditions apply: Page 8

Serial encapsulation is enabled, as an alternative to direct serial communication, in order to connect to a terminal server via Ethernet; and The target device is also connected via Ethernet but has its own address that is different from terminal server's address. Otherwise, if both conditions do not apply, you may leave the station ID blank. Note: If serial encapsulation is not enabled, this OI Server can only do direct serial communication. There is no option to do Ethernet communication only. The station ID for a target device must use the following syntax: <IP address>:<port Number> The following syntax diagram shows all of the possible options: IP address:port number IP address port number The IP address of the target device. The port number of the PLC program running on the target device. The default port is 1505, but you can use the PLC programming software to change it if necessary. Please note the pipe character ( ) at the end of the station ID, after the port number. It indicates that the station ID should override the address of the terminal server, as configured in the Serial Encapsulation settings. Examples Examples of valid station IDs: 192.168.0.5:1505 10.13.63.90:1505 Page 9

TI500 OI Server Reference Use item references to access data stored in memory registers in connected devices, as well as to access standard system items in the OI Server itself. This section only describes the item reference syntax and options for the TI500 server. For more general information about item references, see "Managing Device Items" and "Item Reference Descriptions" in the Operations Integration Server Manager Help. Item Reference Syntax Item references in this OI Server use the following syntax. For digital registers (i.e., register types X, Y, C), use the following syntax: <register type><address> For analog registers (i.e., register types V, K, TCP, TCC, WX, WY), use either of the following syntaxes: <register type><address>:[bit] <register type><address><data type> The following syntax diagram shows all of the possible options: { { X Y C }address { V K TCP TCC WX WY }address{ :bit F R. D } } register type The type of memory register on the target device: Type X Y C V K TCP TCC WX WY Description Discrete Input Discrete Output Control Relay Variable Memory Constant Memory Timer/Count Preset Memory Timer/Count Count Memory Word Input Memory Word Output Memory address The address of the memory register on the target device. bit The bit number (0 to 15) to be accessed in the memory register. This parameter is optional; if no bit is specified, the entire 16-bit Word is used by default. data type The data type of the memory register: Type F Description Floating point or real number (32-bit) Page 10

Type Description R Floating point or real number (32-bit). Floating point or real number (32-bit) D DWord (i.e., unsigned, 32-bit decimal) Note: F, R, and. all mean the same thing and can be used interchangeably. This parameter is optional; if no type is specified, it is considered to be Word (i.e., unsigned, 16- bit decimal) by default. Address Descriptions The address descriptions consist of the register type, its item name and the allowable range of values, the default data type, allowable suffixes (if any), and allowable access methods. Register Type Item Reference Data Type Access Item Name Discrete Input X 0000 to 0377 Bit Read only Discrete Output Y 1000 to 1177 Bit Read/Write Control relay C 0000 to 0177 Bit Read/Write Variable Memory V 0000 to 0777 Word Read/Write Constant Memory K 0000 to 0777 Word Read/Write Timer/Count Preset Memory TCP 0000 to 0777 Word Read/Write Timer/Count Count Memory TCC 0000 to 1777 Word Read/Write Word Input Memory WX 0000 to 0777 Word Read only Word Output Memory WY 0000 to 0377 Word Read/Write Unsupported register types The following registers are also implemented in this OI Server, but they have not been validated in conformance tests. Range Register Type Loop Process Variable Loop Setpoint Loop Output Loop Bias Loop Error Loop Gain Loop Rate Loop Reset Loop V-flags RAMP/SOAK flags Analog Alarm Process Variable Analog Alarm Setpoint Analog Alarm flags Item Name LPV LSP LMN LMX LERR LKC LTD LTI LVF LRSF APV ASP AVF Page 11

Register Type Loop Process Variable High Limit Loop Process Variable Low Limit Analog Alarm Process Variable High Limit Analog Alarm Process Variable Low Limit Loop Sample Rate (in seconds) Analog Alarm Sample Rate (in seconds) Loop High Alarm Limit Loop Low Alarm Limit Loop Orange Deviation Alarm Limit Loop Yellow Deviation Alarm Limit Loop Setpoint High Limit Loop Setpoint Low Limit Most-significant word of Loop C-flags Least-significant word of Loop C-flags Loop High-High Alarm Limit Loop Low-Low Alarm Limit Loop Rate-of-Change Alarm Limit (in Engineering Units per minute) Loop Alarm Deadband Analog Alarm High Alarm Limit Analog Alarm Low Alarm Limit Analog Alarm Orange Deviation Alarm Limit Analog Alarm Yellow Deviation Alarm Limit Analog Alarm Setpoint High Limit Analog Alarm Setpoint Low Limit Most-significant word of Analog Alarm C-flags Least-significant word of Analog Alarm C-flags Analog Alarm High-High Alarm Limit Analog Alarm Low-Low Alarm Limit Analog Alarm Rate-of-Change Alarm Limit (in Engineering Units per minute) Analog Alarm Alarm Deadband Analog Alarm Error Loop Derivative Gain-limiting coefficient Loop RAMP/SOAK Step Number Loop Alarm / Alarm Acknowledge flags Analog Alarm / Alarm Acknowledge flags Loop Peak Elapsed Time Value Represents the elapsed time from when the process is scheduled until it completes execution (TI545, TI555,TI575). Analog Alarm Peak Elapsed Time Value Item Name LPVH LPVL APVL APVH LTS ATS LHA LLA LODA LYDA LSPH LSPL LCFH LCFL LHHA LLLA LRCA LADB AHA ALA AODA AYDA ASPH ASPL ACFH ACFL AHHA ALLA ARCA AADB AERR LDK LRSN LACK AACK LPET APET Page 12

Register Type Represents the elapsed time from when the process is scheduled until it completes execution (TI545, TI555, TI575). SF PGM Peak Elapsed Time Value Represents the elapsed time from when the process is scheduled until it completes execution (TI545, TI555, TI575). Item Name PPET Supported Data Types The data type is specified as a suffix in the item syntax. This OI Server supports the following data types. Data Type Suffix Description Bit (Boolean) :bit Single bit. Bit 0 is the low bit. Bit 15 is the high bit. Float F R. Floating point or real number (32-bit). DWord D Unsigned, 32-bit decimal value. Bit 0 is the low bit. Bit 31 is the high bit. Examples of Item References These are examples of valid item references for this OI Server. For more information about the referenced addresses, see the manufacturer's documentation for your device. Register Type Address on the Device Item Reference Discrete Input X1000 X1000 Discrete Output Y0007 Y7 Control relay C1400 C1400 Variable Memory Constant Memory Timer/Count Preset Memory Timer/Count Count Memory Word Input Memory Word Output Memory V00001 (Float format) V00100 (DWord format) K0007 K0026 TCP0010 TCP0053 TCC0017 TCC0020 WX0000 (DWord format) WX0000 (Float format) WY0007 WY0021 V1F V1:0 V100D V100:8 K7 K7:7 K26 K26:6 TCP10 TCP53 TCC17 TCC20 WX0D WX0F WY7 WY21:1 Page 13

TI500 OI Server Error Codes The following tables describe the additional error codes that you might receive when poll/poke requests and operations fail. Code Description Possible Causes Solution 1 Protocol Error OI Server settings do not match the PLC settings. 2 Invalid Command OI Server settings do not match the PLC settings. 3 Invalid Response OI Server settings do not match the PLC settings. 4 Invalid Block Size The PLC model does not accept the number of bytes requested or sent. 5 Invalid Header One or more of the specified item references does not use the required syntax. 6 Invalid Address One or more of the specified item references does not use the required syntax. 9 Word bit write is not enabled Attempted to write to a word bit without enabling it in the channel settings. 14 Busy Error Disconnected cables Device is turned off, or in Stop or error mode Station number is wrong Check the PLC settings, and then configure the OI Server settings to match. Check the PLC settings, and then configure the OI Server settings to match. Check the PLC settings, and then configure the OI Server settings to match. Adjust the Max Block Size (in the channel settings). Verify the item references according to the syntax provided in this documentation, and then correct them if necessary. Verify the item references according to the syntax provided in this documentation, and then correct them if necessary. Select the Write word bits option (in the channel settings). Check the cable wiring. Check the device state. It must be RUN Check the station number. Check the configuration. 15 Invalid Entry Invalid entry or entries for channel settings. Check Write word bits or Protocol (in the channel settings) and make sure they are each set to either 0 or 1, according to the descriptions provided in this documentation. 16 Configured block size is not supported by PLC The OI Server is requesting more registers than what is supported by the PLC model. Set the Max Block Size (in the channel settings) to a value that is supported by the PLC model. The default value is 7. 17 Invalid entry for block size The specified maximum block size is invalid. Set Max Block Size (in the channel settings) to an integer value from 1 to 64. 18 Invalid block size The specified maximum block size is invalid. Set Max Block Size (in the channel settings) to an integer value from 1 to 64. Code Description Possible Causes Solution 0 OK Communicating without error. None required. -15 Timeout waiting for message to start Disconnected cables. PLC is turned off, in stop mode, or in error mode. Wrong station number. Wrong parity (for serial communication). Wrong RTS/CTS configuration (for serial communication). Check cable wiring. Check the PLC mode it must be RUN. Check the station number. Increase the timeout in the driver's advanced settings. Check the RTS/CTS configuration (for serial communication). Page 14