WITS Level 0 Passive Driver Help Kepware Technologies

Similar documents
Toshiba Serial Driver Help Kepware Technologies

Siemens S7 MPI Driver Help Kepware Technologies

Modbus ASCII Driver Kepware, Inc.

ODBC Client Driver Help Kepware, Inc.

Ping Device Driver Help Schneider Electric

DNP Master Ethernet Driver Help Kepware Technologies

The Answer to the 14 Most Frequently Asked Modbus Questions

Virtual Integrated Design Getting started with RS232 Hex Com Tool v6.0

Kepware Technologies Optimizing KEPServerEX V5 Projects

Configuration of Kepware OPC Server in PanelMate Configuration Editor

Alarms & Events Plug-In Help Kepware, Inc.

Allen-Bradley. Bar Code. 2-D Hand-Held. Programming Guide. Bar Code. Scanners. (Cat. No HTG-4)

CONTROL MICROSYSTEMS DNP3. User and Reference Manual

Modicon Modbus Protocol Reference Guide. PI MBUS 300 Rev. J

OPERATOR INTERFACE PRODUCTS APPLICATION NOTE. Xycom 4800/2000 OIL (Operator Interface Language)- Series Terminals: Backup and Restore with ProComm

7.7 Ethernet Communication (AFPX-COM5)

Technical Note. Configuring an Omron PLC with Omron FINS Ethernet Driver. 1. Introduction

Modbus Communications for PanelView Terminals

Additional Setup Instructions for Modbus: RTU, ASCII, TCP, Omni & Enron

RS-232 Communications Using BobCAD-CAM. RS-232 Introduction

SNMP Agent Plug-In Help Kepware Technologies

Using HyperTerminal with Agilent General Purpose Instruments

Technical Support Bulletin Nr.18 Modbus Tips

To perform Ethernet setup and communication verification, first perform RS232 setup and communication verification:

Process Control and Automation using Modbus Protocol

Kiwi SyslogGen. A Freeware Syslog message generator for Windows. by SolarWinds, Inc.

IP Link Device Interface Communication Sheet

System Monitor Driver Help Kepware Technologies

CONCEPT1 RS232 COMMUNICATION

Configuring Serial Terminal Emulation Programs

Advantech WebAccess Device Driver Guide. BwSNMP Advantech WebAccess to SNMP Agent (Simple Network Management Protocol) Device Driver Guide

MTS Master Custom Communications Protocol APPLICATION NOTES

TAP Interface Specifications

PRODUCT MANUAL SKX OPEN SKX ADVANCE ZN1RX-SKXOPEN. Edition 2 Version 1.1

METROLOGIC INSTRUMENTS, INC. IS4225 ScanGlove USB Addendum for the MetroSelect Single-Line Configuration Guide

Settle-to-File Credit Card Driver for 3700 POS

User Manuals. Connection to Siemens S5 PU (AS511) Part Number: Version: 2. Date:

This document explains how to configure and use the IOPRINT+ Print Server in the Unix TCP/IP environment.

How To Set Up A Modbus Cda On A Pc Or Maca (Powerline) With A Powerline (Powergen) And A Powergen (Powerbee) (Powernet) (Operating System) (Control Microsci

1.Eastron SDM220Modbus Smart Meter Modbus Protocol Implementation V1.0

How To Connect A Directsofl To A Powerpoint With An Acd With An Ctel With An Dm-Tel Modem On A Pc Or Ipad Or Ipa (Powerpoint) With A Powerline 2 (Powerline

eztcp Technical Document Modbus/TCP of eztcp Caution: Specifications of this document may be changed without prior notice for improvement.

1 Serial RS232 to Ethernet Adapter Installation Guide

ND48-RS ASCII A2.04 Communication Protocol

Introduction: Implementation of the MVI56-MCM module for modbus communications:

How-To Set Custom Scale Format for FedEx Ship Manager

Moven Studio realtime. streaming

DataLogger Kepware, Inc.

SUDT AccessPort TM Advanced Terminal / Monitor / Debugger Version 1.37 User Manual

SNMP Driver Help Kepware, Inc.

How to use KEPServerEX OPC Server (Kepware) with iologik 4000 (Modbus TCP/IP NA-4010 and Modbus Serial NA-4020/NA-4021)

IP Link Device Interface Communication Sheet

WIZnet S2E (Serial-to-Ethernet) Device s Configuration Tool Programming Guide

2015/02/07 05:41 1/23 WIZ550WEB Users' Guide

SNMP Driver Help Schneider Electric

How to Connect WinCC V6 to TOP Server OPC Servers

Application Note 2. Using the TCPDIAL & TCPPERM Commands to Connect Two TransPort router Serial Interfaces Over TCP/IP.

RMCS Installation Guide

Import and Export User Guide. PowerSchool 7.x Student Information System

4511 MODBUS RTU. Configuration Manual. HART transparent driver. No. 9107MCM100(1328)

Modbus Protocol. PDF format version of the MODBUS Protocol. The original was found at:

RcWare SoftPLC OPC server. Setup guide

Using Logix5000 Controllers as Masters or Slaves on Modbus

Siemens S7 TCP/IP Master with TIA S7 Tag Import Communications Driver

Computer Networks. Data Link Layer

SYMETRIX SOLUTIONS: TECH TIP August 2015

Import and Export User Guide PowerSchool Student Information System

Using IDENT M System T with Modbus/TCP

This document explains how to use your Web Browser to configure the 100BaseT IOPRINT+ Print Server models. Connecting to the IOPRINT+ Print Server

This document explains how to use your Web Browser to configure the 100BaseT Print Server models

KEPServerEX Client Connectivity Guide

Moxa EDS-SNMP OPC Server Pro User s Manual.

TSX ETY 110 Module 8

Different Ways of Connecting to. 3DLevelScanner II. A.P.M Automation Solutions LTD. Version 3.0

RS-485 Protocol Manual

CENTRONICS interface and Parallel Printer Port LPT

Omron I/O Driver (Series 2) Programmable Serial Interface Card

Modbus and ION Technology

Part No. : MUL PROGRAMMING GUIDE

OCS Training Workshop LAB14. Setup

LifeSize Networker Installation Guide

Configuring CSS Remote Access Methods

TOP Server DNP 3.0 Suite. Background & Best Practices

SNMP Agent Plug-In Help Kepware Technologies

User Manual Connection to Beckhoff ADS serial

Operating Instruction MEW01652 Revision -

MATRIX 210. Host Mode Programming

Kepware Technologies KEPServerEX Client Connectivity Guide for GE's Proficy ifix

Allen-Bradley ControlLogix Ethernet Driver Help Kepware Technologies

TELOCATOR ALPHANUMERIC PROTOCOL (TAP)

User Manual Revision English Converter / Adapter Ethernet to RS232 / RS485 (Order Code: HD HD M HD HD M)

MODBUS MASTER/SLAVE Serial and Ethernet Communication Server

Motion Control Products Application note Connecting CP600 to motion products via Modbus TCP

Product Manual. UDC 2300 UDC 3000 UDC 3300 UDC 5000 UDC 6000 UDC 6300 Universal Digital Controllers. RS422/485 ASCII Communications Option

DeviceMaster UP Modbus Controller to Controller Communication

How to Obtain an OPC License--5. Creating a System Code 5 Entering an Authorization Code 6. Getting Started with SNMP Editor--7

EMG Ethernet Modbus Gateway User Manual

ENET-710. ENET Ethernet Module ENET-710 JAN / 06 FOUNDATION

Time Synchronization & Timekeeping

ADSL Router Quick Installation Guide Revised, edited and illustrated by Neo

Transcription:

WITS Level 0 Passive Driver Help 2012 Kepware Technologies

WITS Level 0 Passive Driver Help 2 Table of Contents Table of Contents 2 WITS Level 0 Passive Driver Help 3 Overview 3 Channel Setup 4 Device Setup 5 Settings 5 Data Types Description 7 Address Descriptions 8 Error Descriptions 9 Device '<device name>' item '<WITS ID>', Write value length exceeds maximum frame length. Truncating to 1024 bytes Device '<device name>', Abandoning current message after <time in ms> ms of inactivity 9 Device '<device name>', Communications have timed out after <time in seconds> seconds of inactivity Device '<device name>', Invalid delimiter. Expecting '<configured delimiter>'. Discarding 10 Device '<device name>', Message parsing error. Discarding 10 Device '<device name>', More than 4096 bytes in item '<WITS ID>' data. Discarding remainder of message 10 Device '<device name>', Non-numeric WITS ID found: '<WITS ID>'. Discarding 10 Device '<device name>', Non-printable character '<hex byte>' found in WITS ID. Discarding 10 Device '<device name>', Non-printable character '<hex byte>' in item '<WITS ID>' data. Discarding 11 Device '<device name>', Received Null value '<Null value>' for item '<WITS ID>'. Setting tag to bad quality 11 Device '<device name>', Value '<value>' is invalid for item '<WITS ID>' with data type '<data type>'. Setting tag to bad quality 11 Device '<device name>', Value '<value>' out of range for item '<WITS ID>' with data type '<data type>'. Setting tag to bad quality 11 Unable to write to address '<address>' on device '<device name>'. Invalid socket 11 Index 13 9 9

3 WITS Level 0 Passive Driver Help WITS Level 0 Passive Driver Help Help version 1.004 CONTENTS Overview What is the WITS Level 0 Passive Driver? Channel Setup How do I specify timeout settings for the channel? Device Setup How do I configure devices for use with this driver? Data Types Description What data types does this driver support? Address Descriptions How do I address a data location on a WITS Level 0 Passive Driver device? Error Descriptions What error messages are produced by the WITS Level 0 Passive Driver? Overview The WITS Level 0 Passive Driver provides an easy and reliable way to connect WITS Level 0 devices to OPC client applications, including HMI, SCADA, Historian, MES, ERP and countless custom applications. It is intended for use with devices that support Level 0 of the WITS protocol and transmit unsolicited data.

WITS Level 0 Passive Driver Help 4 Channel Setup Timeout Descriptions of the parameters are as follows: Communications Timeout: This parameter specifies the time in seconds that the driver will wait between receiving unsolicited messages. When the timeout expires, the device s error state will be set and all tags owned by the associated device will be set to Bad quality. A value of 0 will disable the timeout. The valid range is 0 to 3600 seconds. The default setting is 0 seconds. Note: When left at the default disabled setting, users will not receive error messages if communications with the device stop. Inter-Character Timeout: This parameter specifies the time in milliseconds that the driver will wait between receiving bytes within a message. When the timeout expires, the device s error state will be set, the current message will be abandoned, and the driver will interpret the next received byte as the beginning of a new message. The valid range is 50 to 1000 milliseconds. The default setting is 250 milliseconds.

5 WITS Level 0 Passive Driver Help Device Setup Supported Devices All devices that transmit unsolicited WITS Level 0 data. Communication Protocol WITS Level 0. Supported Communication Parameters Baud Rate: All major Baud rates. Parity: Odd, Even, and None. Data Bits: 8. Stop Bits: 1 and 2. Note: Not all of the listed configurations may be supported in every device. Maximum Number of Channels and Devices The maximum number of channels supported by this driver is 256. The maximum number of devices supported is 256 (1 device per channel). Unsolicited Ethernet Encapsulation This driver supports Unsolicited Ethernet Encapsulation, which allows the driver to communicate with serial devices attached to an Ethernet network using a terminal server. It may be enabled for the channel in the Communications tab of Channel Properties. For more information, refer to the OPC server's help file. Automatic Tag Database Generation This driver supports the Automatic Tag Database Generation of all pre-defined WITS records. For more information on pre-defined WITS records, refer to W.I.T.S. Wellsite Information Transfer Specification. Cable Diagram Settings

WITS Level 0 Passive Driver Help 6 Descriptions of the parameters are as follows: Delimiter: This parameter specifies the sequence of characters that the driver will expect between the lines of a WITS Level 0 message. Options include <CR><LF>, <LF><CR>, <CR>, and <LF>. The default setting is <CR><LF>. Descriptions of the options are as follows: <CR><LF>: This option is a carriage return followed by a line feed. <LF><CR>: This option is a line feed followed by a carriage return. <CR>: This option is a carriage return. <LF>: This option is a line feed. Update local value on write: When checked, this option will update the local value immediately when a tag is written. This option should be disabled when the WITS device is expected to echo the written item back to the driver. The default setting is unchecked. Note: If the device is in an error state, the tag's value will not be updated until the error state is cleared. Inter-write delay: This parameter specifies the minimum amount of time that the driver will wait in between sending requests to the target device. The default setting is 0 milliseconds.

7 WITS Level 0 Passive Driver Help Data Types Description Data Type Short Long DWord Float String Description Signed 16 bit value bit 0 is the low bit bit 14 is the high bit bit 15 is the sign bit Signed 32 bit value bit 0 is the low bit bit 30 is the high bit bit 31 is the sign bit Unsigned 32 bit value bit 0 is the low bit bit 31 is the high bit 32 bit floating point value bit 0 is the low bit bit 31 is the high bit Null terminated ASCII string Strings up to a length of 4096 characters are supported.

WITS Level 0 Passive Driver Help 8 Address Descriptions The default data type is displayed in bold. Address Range Data Type Access xxxx 0001-9999 Short, DWord, Long, Float, String Read/Write Note 1: The WITS Level 0 Passive Driver supports the full range of addresses between 0001 and 9999. If the address is pre-defined in the WITS specification, the default data type will be equal to the pre-defined item's data type. If the address is not pre-defined, the default data type will be String. Note 2: For more information on pre-defined WITS records, refer to W.I.T.S. Wellsite Information Transfer Specification.

9 WITS Level 0 Passive Driver Help Error Descriptions The following error/warning messages may be generated. Click on the link for a description of the message. Device '<device name>' item '<WITS ID>', Write value length exceeds maximum frame length. Truncating to 1024 bytes Device '<device name>', Abandoning current message after <time in ms> ms of inactivity Device '<device name>', Communications have timed out after <time in seconds> seconds of inactivity Device '<device name>', Invalid delimiter. Expecting '<configured delimiter>'. Discarding Device '<device name>', Message parsing error. Discarding Device '<device name>', More than 4096 bytes in item '<WITS ID>' data. Discarding remainder of message Device '<device name>', Non-numeric WITS ID found: '<WITS ID>'. Discarding Device '<device name>', Non-printable character '<hex byte>' found in WITS ID. Discarding Device '<device name>', Non-printable character '<hex byte>' in item '<WITS ID>' data. Discarding Device '<device name>', Received Null value '<Null value>' for item '<WITS ID>'. Setting tag to bad quality Device '<device name>', Value '<value>' is invalid for item '<WITS ID>' with data type '<data type>'. Setting tag to bad quality Device '<device name>', Value '<value>' out of range for item '<WITS ID>' with data type '<data type>'. Setting tag to bad quality Unable to write to address '<address>' on device '<device name>'. Invalid socket Device '<device name>' item '<WITS ID>', Write value length exceeds maximum frame length. Truncating to 1024 bytes The written value is greater than 1024 characters. If truncation is not acceptable, write values that are less than or equal to 1024 characters. Device '<device name>', Abandoning current message after <time in ms> ms of inactivity The connection with the device was lost partway through message reception. 1. Ensure that the device is sending valid WITS Level 0 messages. 2. Ensure that the connection with the device is reliable. 3. Adjust the value of the Inter-Character Timeout parameter. Device '<device name>', Communications have timed out after <time in seconds> seconds of inactivity The connection with the device has not been established or has been lost.

WITS Level 0 Passive Driver Help 10 1. Verify the connection with the device. 2. Adjust the value of the Communication Timeout parameter. Device '<device name>', Invalid delimiter. Expecting '<configured delimiter>'. Discarding The delimiter sent by the device is not equal to the delimiter that was configured. Ensure that the delimiter sent by the device is equal to the delimiter that was configured. Device '<device name>', Message parsing error. Discarding An incorrect character was received when a header (&&) or trailer (!!) was expected. Solution Verify that the data being sent follows the WITS Level 0 protocol. Device '<device name>', More than 4096 bytes in item '<WITS ID>' data. Discarding A line of data is greater than 4096 bytes long. Reduce the data sent by WITS Level 0 devices to 4096 bytes or fewer. Device '<device name>', Non-numeric WITS ID found: '<WITS ID>'. Discarding 1. A non-numeric character was received as part of a WITS ID. This may be due to noise on the transmission medium or an invalid WITS ID being sent by the device. 2. The configured delimiter is part of, but not equal to, the delimiter sent by the device. 1. Ensure that the WITS device only transmits numeric WITS IDs. 2. Ensure that the delimiter is correctly configured. Device '<device name>', Non-printable character '<hex byte>' found in WITS ID. Discarding 1. A non-printable character was received in a WITS ID. This may be due to noise on the transmission medium or an invalid WITS ID being sent by the device. 2. The configured delimiter is part of, but not equal to, the delimiter sent by the device.

11 WITS Level 0 Passive Driver Help 1. Ensure the WITS device transmits only printable ASCII characters. 2. Ensure that the delimiter is correctly configured. Device '<device name>', Non-printable character '<hex byte>' in item '<WITS ID>' data. Discarding A non-printable character was received in the value of an item. This may be due to noise on the transmission medium or an invalid value being sent by the device. Ensure that the WITS device only transmits printable ASCII characters. Device '<device name>', Received Null value '<Null value>' for item '<WITS ID>'. Setting tag to bad quality Either -8888 or -9999 was received as the value of an item. Ensure that the Null value transmission was expected. Device '<device name>', Value '<value>' is invalid for item '<WITS ID>' with data type '<data type>'. Setting tag to bad quality A tag with a numeric data type received a value from a device with a non-numeric character. Ensure that the data sent by the device is valid, and that the appropriate data type is configured. Device '<device name>', Value '<value>' out of range for item '<WITS ID>' with data type '<data type>'. Setting tag to bad quality The received data is outside the range of values allowed for the configured numeric data type. Ensure that the data sent by the device is valid, and that the appropriate data type is configured. Unable to write to address '<address>' on device '<device name>'. Invalid socket Error When using unsolicited Ethernet Encapsulation, the WITS device's address will be unknown until the first message is received from the device. This error message occurs when a write is made to one of the device's items before its address is known.

WITS Level 0 Passive Driver Help 12 When the driver is configured for unsolicited Ethernet Encapsulation, users should ensure that writes are only made after the WITS device has sent a message to the driver.

13 WITS Level 0 Passive Driver Help Index A Address Descriptions 8 C Channel Setup 4 D Data Types Description 7 Device '<device name>' item '<WITS ID>', Write value length exceeds maximum frame length. Truncating to 1024 bytes 9 Device '<device name>', Abandoning current message after <time in ms> ms of inactivity 9 Device '<device name>', Communications have timed out after <time in seconds> seconds of inactivity Device '<device name>', Invalid delimiter. Expecting '<configured delimiter>'. Discarding 9 10 Device '<device name>', Message parsing error. Discarding 10 Device '<device name>', More than 4096 bytes in item '<WITS ID>' data. Discarding 10 Device '<device name>', Non-numeric WITS ID found '<WITS ID>'. Discarding 10 Device '<device name>', Non-printable character '<hex byte>' found in WITS ID. Discarding 10 Device '<device name>', Non-printable character '<hex byte>' in item '<WITS ID>' data. Discarding Device '<device name>', Received Null value '<Null value>' for item '<WITS ID>'. Setting tag to bad quality 11 11 Device '<device name>', Value '<value>' is invalid for item '<WITS ID>' with data type '<data 11 type>'. Setting tag to bad quality Device '<device name>', Value '<value>' out of range for item '<WITS ID>' with data type '<data type>'. Setting tag to bad quality 11 Device Setup 5

WITS Level 0 Passive Driver Help 14 E Error Descriptions 9 H Help Contents 3 O Overview 3 S Settings 5 U Unable to write to address '<address>' on device '<device name>'. Invalid socket 11