0% found this document useful (0 votes)

41 views71 pages

OIMBTCP

OIMBTC

Uploaded by

said_rahmansyah4750

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

41 views71 pages

OIMBTCP

OIMBTC

Uploaded by

said_rahmansyah4750

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 71

AVEVA™

Communication Drivers Pack – Modicon

- MBTCP Driver

User Guide
© 2020 AVEVA Group plc and its subsidiaries. All rights reserved.

No part of this documentation shall be reproduced, stored in a ret rieval system, or transmitted by any
means, electronic, mechanical, photocopying, rec ording, or otherwise, without the prior written
permission of AVEVA. No liability is assumed with respect to the use of the information contained herein.
Although precaution has been taken in the preparation of this doc umentation, AVEVA 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 AVEVA. The soft ware described in this
documentation is furnished under a license agreement. This soft ware may be used or copied only in
accordance with the terms of such license agreement.
ArchestrA, Aquis, Avantis, Citect, DYNSIM, eDNA, EYESIM, InBatch, InduSoft, InStep, Int elaTrac,
InTouch, OASyS, PIPEPHASE, PRiSM, PRO/II, PROV ISION, ROMeo, SIM4ME, SimCentral, SimSci,
Skelta, SmartGlance, Spiral Software, Termis, WindowMaker, WindowViewer, and Wonderware are
trademarks of AVEVA and/or its subsidiaries. An extensive listing of AVEVA trademarks can be found at:
https://sw.aveva.com/legal. All other brands may be trademarks of their respective owners.
Publication date: Friday, November 20, 2020
Contact Information
AVEVA Group plc
High Cross
Madingley Road
Cambridge
CB3 0HB. UK
https://sw.aveva.com/
For information on how to cont act sales and customer training, see https://sw.aveva.com/contact.
For information on how to cont act technical support, see https://sw.aveva.com/support.
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

Contents
Chapter 1 Introduction to the MBTCP Communication Driver........................................ 5
About the MB TCP Communication Driver ................................................................................... 5
Generic Modbus Controllers ...................................................................................................... 5
Supported Client Protocols ........................................................................................................ 6
OPC ................................................................................................................................... 6
SuiteLink ............................................................................................................................ 6
DDE/FastDDE ..................................................................................................................... 6
DDE ............................................................................................................................. 7
FastDDE ....................................................................................................................... 7
Supported Device Protocols....................................................................................................... 7
Modbus TCP/IP Ethernet Protocol ........................................................................................ 7

Chapter 2 Configuring the MBTCP Communication Driver............................................. 9

Configuring the MB TCP Communication Driver ........................................................................... 9
Preparing the MB TCP Communication Driver ........................................................................ 9
MBTCP Hierarchy in the OI Server Manager ....................................................................... 10
Configuring TCPIP _PORT Object ................................................................................. 11
Configuring Connections to TCP IP_P ort Object ............................................................. 12
String-Data Handling ................................................................................................... 39
Message Optimization ................................................................................................. 40
Configuring Device Redundancy .............................................................................................. 40
Device Group Definitions ......................................................................................................... 41
Device Item Definitions ............................................................................................................ 44
Exporting and Importing Communic ation Driver Item Data ......................................................... 45
Scan-Based Message Handling ......................................................................................... 47
Unsolicited Message Handling ........................................................................................... 47
Unsolicited Message Behavior...................................................................................... 47
Unsolicited Message Configuration ............................................................................... 47

MBTCP OI Reference............................................................................................................ 49
Data Types ............................................................................................................................. 49
Support for 64-bit Data Types ............................................................................................ 49
Data and Register Types ......................................................................................................... 50
Modbus Item Naming .............................................................................................................. 51
Register-Number Item Names ............................................................................................ 51
Item Names Using the Modicon PLC Register Addresses .................................................... 54
Absolute Notation Item Names ........................................................................................... 54
Modulo-10000 Point Item Names ....................................................................................... 55
Modulo-10000 Items, BCD Register Ty pe, and Concept Data Structures .............................. 56
Zero- and One-B ased Addressing ............................................................................................ 57

3
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide Contents

Generic OPC Syntax ............................................................................................................... 57

Supported MBTCP OI Server Hardware and Firmware .............................................................. 57
Cont roller Function Codes ....................................................................................................... 58
Modbus Exception Codes ........................................................................................................ 59
TCP Port ................................................................................................................................ 60

Troubleshooting the MBTCP Communication Driver ....................................................... 61

Error Messages and Codes ..................................................................................................... 61
Communication Driver Error Messages ............................................................................... 61
Server-Specific Error Codes ............................................................................................... 71

4
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

C HAPTER 1
Introduction to the MBTCP Communication
Driver

About the MBTCP Communication Driver

The MB TCP Communication Driver is a Microsoft Windows application program that acts as a
communications protoc ol server. It allows other Windows application programs access to data in the
Modicon-family of controllers (also referred to as devices), including the TS X P remium, TS X Quantum,
and TS X Momentum that are connected to the Communicati on Driver through the computers’ Ethernet
ports using the Modbus TCP/IP protoc ol.
This Communication Driver is hosted by the OI Server Manager, a Microsoft Management Console
(MMC) snap-in, which is a part of the ArchestrA System Management Console (SMC) s uite of utilities.
Many high-level functions and user-interface elements of the OI Server Manager are universal to all
Communication Drivers, and only the documentation for the OI Server Manager contains descriptions of
those universal functions/UI elements. Therefore, reading the documentation for both the MMC and the
OI Server Manager is critical to understanding this user’s guide. To read the documentation about the
MMC and OI Server Manager, right-click the OI Server Manager icon and select the Help menu. B oth the
MMC Help and the Communication Drivers Pack Help are displayed.
The shortcut menu items described in this doc ument typically represent only a subset of any actual
shortcut menu. Most items in each shortcut menu are standard Windows commands. For more
information about those commands, please see Help, by right-clicking the System Management Console
icon.

Generic Modbus Controllers

Starting in version 1.1 of the MB TCP Communication Driver, additional Modbus devices that are not
listed in the supported hardware will be supported. These Modbus devic es, referred to as Generic
Modbus devices/controllers in this document and in the implementation of the Communication Driver,
must be capable of supporting the Modbus Controller Function Codes on page 58, Modbus Exception
Codes on page 59, and Dat a Types on page 49.
Compared to the PLCs listed in Supported MBTCP OI Server Hardware and Firmware on page 57, the
Generic Modbus devices/controllers offer the following additional capabilities:
 Configurable TCP Port Number.
 Support of Modbus devices that cannot handle multiple-coil write in one message.
 Support of Modbus devices that cannot handle multiple-holding-register write in one message.
 Configurable 4-digit, 5-digit, or 6-digit addressing.
 The maximum addressable register range will be verified by the Modbus devices and does not need
to be configured into the Communication Driver.
 Access to data in Modbus PLCs that support 64-bit data types such as integer and floating point
value dat a types. In support of accessing 64 -bit data types, the order of the PLC memory registers
written to and read from are configurable.

5
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideIntroduction to the MBTCP Communication Driver

 Configurable Zero Based Addressing to enable addressing both in Modbus PLCs that are
zero-based, such as the TS X Premium, and in Modbus PLCs that are one -based. Zero-based
addressing means that the first address bit (character) begins at 0 rather than at 1.

Supported Client Protocols

The MB TCP Communication Driver communicates with clients and PLCs using the following different
communications protoc ols:
 OPC on page 6
 SuiteLink on page 6
 DDE/FastDDE on page 6

OPC
OPC (OLE for Proc ess Control) is a non -propriet ary set of standard interfac es based upon Microsoft’s
OLE/COM technology. This standard makes possible interoperability between automation/control
applications, field systems/ devices and business/offic e applications. A voiding the traditional
requirement of software/application developers to write custom d rivers to exchange data with field
devic es, OPC defines a c ommon, high performance interface that permits this work to be done once, and
then easily reused by HMI, SCA DA, control and custom applications. Over the network, OPC uses
DCOM (Distributed COM) for remote communications.

SuiteLink
SuiteLink uses a TCP/ IP-based protoc ol and is designed specifically to meet industrial needs such as
data integrity, high throughput, and easier diagnostics. This TCP/IP standard is support ed on Windows
NT and Windows NT-t echnology-based operating systems (for example, Windows 2000, Windows XP,
and Windows 2003).
SuiteLink is not a replacement for DDE, FastDDE, or NetDDE. The protocol used bet ween a client and a
server depends on your network connections and configurations. SuiteLink provides the following
features:
 Value Time Quality (V TQ) places a timestamp 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 operating system’s performance monit or. This
feature is critical for the operation and maintenance of distrib uted 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.

DDE/FastDDE
The DDE/FastDDE communication protocols allow communication between a client and a server. For
DDE/FastDDE communications the Communication Driver must be activated in Desktop mode (must
start from command line).

6
Introduction to the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

DDE
DDE is a communic ations protocol that 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 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.

Note: On Windows Vista and later operating systems, Local DDE is supported only when the
Communication Driver is activated from its executable file or launched from InTouc h. Local DDE is not
supported when the Communication Driver is activated from the SMC.

FastDDE
FastDDE provides a means of packing multiple DDE messages into a single message. This packing
improves efficiency and performance by reducing the total number of DDE transactions required
between a client and a server.
Although FastDDE has extended the usefulness of DDE for our industry, this extension is being pushed
to its performance constraints in distributed environments.

Supported Device Protocols

The Modbus Ethernet (MB TCP ) Communication Driver is designed to provide connectivity to the family
of Modicon cont rollers through the following supported network communications protocol:
 Modbus TCP/IP Ethernet protocol

Note: The MB TCP Communication Driver is capable of supporting dual network (NIC) cards in a system.

Modbus TCP/IP Ethernet Protocol

The Modbus TCP/IP Ethernet protocol is a part of the MB TCP Communication Driver, which must be
installed on your computer and configured for t he PLC with which you wish to communicate. The Modb us
TCP/IP Ethernet protocol can be used in a net work with up to 1024 slave devices.
 Direct Connectivity
The Modbus TCP/IP Ethernet protocol is utilized to directly connect to the following Modicon
controllers through the TCP/ IP port.
o TS X Quantum controllers
o TS X Momentum controllers
o TS X Premium controllers
o Generic Modbus TCP (4-Digit, 5-Digit, and 6-Digit) cont rollers
 Indirect Connectivity
The TCP/ IP Ethernet protocol, through the TCP/ IP port and down to either a Modbus Bridge or
NR& D Pen-T Bridge is used to communicate with the following cont rollers:
o Compact 984 controllers (via RS232)
o Modicon Micro controllers (via RS232)
o TS X Momentum controllers (via RS232 or RS 485)
o Generic Modbus Serial (4-Digit, 5-Digit, 6-Digit) controllers (via Serial RS 485)

7
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideIntroduction to the MBTCP Communication Driver

For more information about Modbus Bridge models and other supported hardware, see Supported
MBTCP OI Server Hardware and Firmware on page 57.

Note: For more information on the Modbus protocol and to better understand how to read and write data
to the different Modicon controllers, please refer to the Modicon "Modbus Protocol Referenc e Guide"
(PI-MBUS-300).

8
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

C HAPTER 2
Configuring the MBTCP Communication
Driver

Configuring the MBTCP Communication Driver

Network Communication Bridge/Int erface Modules are the communication links between the MB TCP
Communication Driver and its support ed Modicon -family of cont rollers (also referred to as devices ),
including the TS X P remium, TS X Quantum, and TS X Momentum that are connected to the
Communication Driver through the computers’ Ethernet ports using the Modbus TCP/IP protoc ol. You
must create these links within the OI Server Manager hierarc hy to bridge/route control and information
data between different networks to target controllers.
This is accomplished by creating P ort Objects. These Port Objects simulate the physical hardware layout
and must be built to establish communications to each of the controllers. Once you have built the MB TCP
hierarchy, you can configure the respective devices for communications. Finally, you can creat e the
desired Device Groups for each controller.
Before you add these Ports in the SMC, you must identify your hardware topology to the devices being
connected.

Note: For more information on the Modbus protocol and to better understand how to read and write data
to the different Modicon controllers, please refer to the Modicon Modbus Protoc ol Reference Guide
(PI-MBUS-300).

Preparing the MBTCP Communication Driver

To prepare the MBTCP Communication Driver
1. The MB TCP Communication Driver is installed along with the Communication Drivers Pack. It is a
selectable option during the Communication Drivers Pack installation.
2. After the installation, start the System Manager Cons ole by clicking the Start button on the Windows
taskbar and pointing to Programs.
3. Point to the AVEVA folder that contains the System Management Console, then click System
Management Console.
4. From the System Management Console tree, click on Operations Integration Server Manager.
5. Click on Default Group, then the Local node.
o Under the Local node, the Communication Driver name is OI.MB TCP

Note: See the Communication Drivers Pack Help for general information about working in this
snap-in environment.

6. Before the Communication Driver is started, you must first build the device hierarchy to establish
communications to each of the controllers.

9
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

Important: For step-by-step procedures on how to build the device hierarchy, see MBTCP Hierarchy
in the OI Server Manager on page 10.

Note: Selecting the Configuration object of the hierarchy tree displays the Global Paramet ers
configuration view for this Communication Driver. The default Poke Mode settings for the
Communication Driver is Optimization mode. Configure all other global parameters as required for
this Communication Driver. For more information about the Global Parameters configuration view,
including descriptions of the different Poke Modes, see the Communication Drivers Pack Help. You
can access that documentation by right-clicking the OI Server Manager icon and selecting the Help
menu, and then navigating through the Communication Drivers Pack Help.

Important: Any Global Parameters that appear dimmed are either not supported or cannot be
configured for this Communication Driver. Simulation Mode is not supported.

7. When the MB TCP hierarchy build has been completed, you can start configuring the respective
devic es for communications.
8. You may create the desired Device Groups for each controller by:
o Navigating to the object of interest in the OI Server Manager tree view.
o Clicking on the Device Groups tab.
o Right -clicking in the Device Groups dialog box and selecting the A dd command from t he shortcut
menu.

Important: For step-by -step procedures on configuring Device Groups, see Device Group
Definitions on page 41.

9. Finally, you may create the desired Device Items for eac h controller by:
o Navigating to the object of interest in the OI Server Manager tree view.
o Clicking on the Device It ems tab.
o Right -clicking in the Device Items dialog box and selecting the Add command from the shortcut
menu.

Note: When any configuration view is in an open state and you open the same server the second
time, the Communication Driver locks the second instance of this same-server access for any update
or configuration activities. Access to this second opening instance will resume after the first one has
been closed.

The Communication Driver is now ready for use. In order to use the Communication Driver, you must
activate it.
 If you are using an OPC Client, the Communication Driver can be auto -started.
 If you are using DDE/SuiteLink, you must start the Communication Driver either as a manual or
automatic service.
 To activate the Communication Driver, right-click on the appropri ate serve instance, such as
OI.MB TCP.4, and select Activate Server from the shortcut menu.

MBTCP Hierarchy in the OI Server Manager

Before attempting to configure your Communication Driver, you should determine the hierarchical
structure of your network/PLC environment.

10
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

Note: The default name created from adding a hierarchy object is in the format of
New_ObjectName_###, where ObjectName is the name of the object type and ### is a numeric value
starting from "000" enumerated sequentially per hierarchy object. The hierarchy object name is up to 32
characters long. The link name for the OP C items is constructed by assembling the respective object
names of the nodes along the hierarchy tree in the logical order, starting from this Communication
Driver’s TCPIP _PORT root down to the leaf. Therefore, the link name is always unique for the
Communication Driver.

Configuring TCPIP_PORT Object

The configuration specific the MBTCP Communication Driver hierarchy tree under the OI Server
Manager starts at the TCPIP_P ORT object.
1. Configure the TCPIP_P ORT object from the Configuration branch of the hierarchy after the
Communication Driver has been installed.
2. Rename this object as appropriate.

Important: If you subs equently clear your configuration hierarchy, you must create this
TCPIP _PORT object from the Configuration branch of the hierarchy. From this point, all of the
following instructions apply.

To create a TCPIP_PORT object from the Configuration branch

1. Right -click on Configuration.
2. Select Add TCPIP_PORT Connection from the shortcut menu.
o A new TCPIP_P ORT object is created as a node in the hierarchy tree.
o Default name is New_TCP IP_PORT_000.
3. Rename the newly created object as appropriate.
o The New_TCPIP _PORT_000 Parameters configuration view (right pane) is displayed.

This configuration view has one element:

11
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

o Port number: Dis plays the default port (socket) number, whic h is 502.

Note: The MB TCP Communication Driver uses port 502 as the default port number to contact the
PLC. The port number in this display is dimmed and is not changeable in this view. However, the
actual port to be used by the Generic Modbus PLCs can be configured in the ModbusPLC object.
This setting will override the port setting in the TCP IP_PORT object. Controllers configured under
the ModbusBridge object will always use port number 502.

From the New_PORT_TCP IP_000 branch of the Communication Driver hierarchy, the following
objects can be created:
o ModbusBridge Object
o TS XQuantum Object (representing the TS XQuantum cont roller)
o TS XMoment um Object (representing the TS XMomentum controller)
o TS XPremium Object (representing the TS XPremium cont roller)
o ModbusPLC Object (representing the Modbus Generic 4-Digit, 5-Digit, or 6-Digit controller)

Important: Eac h hardware c onfigured has a limitation to the number of connections it can support at
one time. Please refer to the respective hardware’s documentation for the maximum number of
simultaneous Modbus/ TCP server connections it can support.

Note: The TS XQuantum, TS XMomentum, TS XPremium, and ModbusPLC objects represent the
logical endpoint to the hardware hierarchy. If y ou add a ModbusBridge object, you must configure an
additional leaf on the hierarchy.

Configuring Connections to TCPIP_Port Object

For all topics within a book that are not Chapter topics.

ModbusBridge Connection
To add ModbusBridge connection to your MBTCP hierarchy
1. Right -click on the TCPIP _PORT branch, and select Add ModbusBridge Connection from the
shortcut menu.
A new ModbusBridge object is created. Default name is New_ModbusBridge_000.

Note: You can add up to 247 objects of each type to the hierarchy. However, the bridge itself limits
the number of PLCs that can be connected to the serial line.

2. Rename as appropriate.

12
Configuring the MBTCP Comm unication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

The New_ModbusBridge_000 P arameters configuration view is displayed.

This configuration view has four configurable elements.

 Bridge Type: From the drop-down menu, select the type of communications bridge to use for the
connection to the TCP/IP Port.
o Modbus Bridge: (Default) This attribute is editable. For this selection, the default value of
Maximum outstanding messages is 2. The maximum value is 4, and the minimum value is 1.
o NR& D Pen-T Bridge: (Alternative bridge type) This attribute is not editable. For this selection, the
default value of Maximum outstanding messages is 1. The Port number and Maximum
outstanding messages fields are disabled.
 Network address: Enter the host name or IP address of the bridge.
o The number of characters should not exceed 255.
o The field cannot be blank (number of characters cannot be zero).
o The default value is 1.0.0.0.
 Port number: Displays the default port (socket) number, which is 502.
 Maximum outstanding message s: Enter the maximum number of queued messages allowed in
the Modbus Bridge.

Note: The Bridge Type used governs the value configured.

From the ModbusBridge branch of the Communic ation Driver hierarchy, the following objects can be
created:
o Compact984 Object
o ModiconMicro Object
o TS XMoment umRS Object
o ModbusPLCRS Object

Compact984 Connection
The Compact984 connection can be created only from the ModbusBridge branc h.

13
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

To add Compact984 Connection to your MBTCP hierarchy

1. Right -click on your ModbusBridge branch, and select Add Compact984 Connection from the
shortcut menu.
o A new Compact984 object is created as a node in the hierarchy tree.
o Default name is New_Compact984_000.

Note: You can add up to 247 objects of this type to the hierarchy.

2. Rename as appropriate.
o The New_Compact984_000 Parameters configuration view is dis played.

This configuration view has 11 configurable elements.

14
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

 Reply timeout (sec): Enter the amount of time the server will wait for an acknowledgment.
o The minimum value is 1 (one).
o The maximum value is 60.
o The default value is 3 (three).
 Use Concept data structure s (Longs): Select to read data from the PLC in concept dat a structure
format for Long item types. If checked, the DAServer will process the data in the same register order
as the Concept programming software.
o Checked – selected (Default)
o Not checked – not selected
 Use Concept data structure s (Reals): Select to read data from the PLC in concept data structure
format for Real item types. If checked, the DAServer will process the data in the same register order
as the Concept programming software.
o Checked – selected (Default)
o Not checked – not selected
 Bit order format: The format of the bit order entered int o the PLC. There are four bit order formats
available for selection.
o B1 B2 … B16: (Default) Bit order is left to right (MSB = Bit 1; LSB = Bit 16)
o B16 B15 … B1: Bit order is right to left (MSB = Bit 16; LSB = Bit 1)
o B0 B1 … B15: Bit order is left to right (MSB = Bit 0; LSB = Bit 15)
o B15 B14 … B0: Bit order is right to left (MSB = Bit 15; LSB = Bit 0)
 Register Order: The order of the PLC memory registers written to and read from, used to support
64-bit data types.
o Order 1: R1 R2 R3 R4 (Default)
o Order 2: R2 R1 R4 R3
o Order 3: R3 R4 R1 R2
o Order 4: R4 R3 R2 R1
where R1, R2, R3, and R4 are the relative register addresses in the PLC.
 Register size (digits): Select the correct register size for addressing the PLC.
o 5-digit register size (applies to 984-145 Compact PLCs).
o 6-digit register size (applies to 984-265 Compact PLCs).
o The default value is 5, for the 984-145 Compact PLCs.
 String variable style: PLC string-data format. Select the option for the style used by the device to
store strings in its registers.
o Full lengt h (space padded) (Default)
o C style (null terminated)
o Pascal style (includes length specifier)
 Register type: Select either Binary or BCD for the register type being used.
o Binary
o BCD
o The default register type is Binary.
15
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

 Maximum address range: There are five sub-elements in this Maximum addressable registers box.
The maximum addressable registers can be obtained from the Modicon Concept or Modsoft
configuration programs. The PLC will return an error if a register outside of this range is used to read
data. The MB TCP DAServer filters out registers outside of this range and logs error messages.

Element Description Minimum Value Maximum Value

Discrete input Enter the maximum number of addressable Min = 1 (one) For 984-145
discrete inputs (read coils) in the PLC compact PLCs:
Max = 9999
(Default)
For 984-265
compact PLCs:
Max = 65536
Coil Enter the maximum number of addressable Min = 1 (one) For 984-145
write coils in the PLC. compact PLCs:
Max = 9999
(Default)
For 984-265
compact PLCs:
Max = 65536
Input register Enter the maximum number of addressable Min = 1 (one) For 984-145
input registers in the PLC. compact PLCs:
Max = 9999
(Default)
For 984-265
compact PLCs:
Max = 65536
Holding register Enter the maximum number of addressable Min = 1 (one) For 984-145
holding registers in the PLC. compact PLCs:
Max = 9999
(Default)
For 984-265
compact PLCs:
Max = 65536
Extended Enter the maximum number of addressable Min = 1 (one) For 984-145
register extended registers in the PLC. compact PLCs:
Max = 9999
Note: This option is not available if you set
(Default)
Register size to 6.
For 984-265
compact PLCs:
Max = 65536
 Block I/O size: This Block I/O Sizes box contains seven sub-elements. The DAServer uses the
block I/O sizes to maximize data throughput. The MB TCP DAServer uses a 256 -byte buffer to read
or write dat a to the PLC. The maximum value is the maximum number of registers that can be read
or written from/to the PLC in one command.

16
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

Element Description Minimum Value Maximum Value

Discrete Enter the maximum number of discrete inputs or Min = 1 (one) Max = 1976
input/coil read coils to read at one time. (Default)

Coil write Enter the maximum number of coils to writ e at Min = 1 (one) Max = 800
one time. (Default)

Holding register Enter the maximum number of holding registers Min = 1 (one) Max = 123
read to read at one time. (Default)

Holding register Enter the maximum number of holding registers Min = 1 (one) Max = 100
write to write at one time. (Default)

Input register Enter the maximum number of input registers to Min = 1 (one) Max = 123
read read at one time. (Default)

Extended Enter the maximum number of extended Min = 1 (one) Max = 122
register read registers to read at one time. (Default)

Extended Enter the maximum number of extended Min = 1 (one) Max = 120
register write registers to write at one time. (Default)
Note: This option is unavailable if you set
Register size to 6.

ModiconMicro Connection
From the ModbusBridge branch of the Communic ation Driver hierarchy, the ModiconMicro connection
can be created.
To add ModiconMicro Connection to your MBTCP hierarchy
1. Right -click on your ModbusBridge branch, and select Add ModiconMi cro Connection from the
shortcut menu.
o A new ModiconMicro object is created as a node in the hierarchy tree.
o Default name is New_ModiconMicro_000.

Note: You can add up to 247 objects of this type to the hierarchy.

2. Rename as appropriate.

17
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

o The New_ModiconMicro_000 Parameters configuration view is displayed.

This configuration view has 10 elements that are configurable.

 PLC unit ID: Enter the PLC unit ID.
The Bridge's internal configuration contains a Unit ID parameter which can be set to override the
Unit_ID address received in the message from the server. In other words, when the Unit_ID box is 0
(zero) the bridge routes the message to its configured Slave device. If the server's Unit_ID is set to 0
(zero), the message will be delivered to the Slave devic e whos e address is defined in the UnitID box
of the Bridge. If the server's Unit _ID is set to a non-zero value (range 1…255), the message will be
delivered to the Slave device at that numerical address, regardless of the contents of the Unit ID box
in the Bridge.
o The minimum value is 0 (zero).
o The maximum value is 255.
o The default value is 1 (one).
 Reply timeout (sec): Enter the amount of time the server will wait for an acknowledgment.
o The minimum value is 1 (one).
o The maximum value is 60.
o The default value is 3 (three).
 Use Concept data structure s (Longs): Select to read data from the PLC in concept dat a structure
format for Long item types. If checked, the Communication Driver will process the data in the same
register order as the Concept programming software.

18
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

o Checked – selected (Default)

o Not checked – not selected
 Use Concept data structure s (Reals): Select to read data from the PLC in concept data structure
format for Real item types. If checked, the Communication Driver will process the data in the same
register order as the Concept programming software.
o Checked – selected (Default)
o Not checked – not selected
 Bit order format: The format of the bit order entered int o the PLC. There are four bit order formats
available for selection.
o B1 B2 … B16: (Default) Bit order is left to right (MSB = Bit 1; LSB = Bit 16)
o B16 B15 … B1: Bit order is right to left (MSB = Bit 16; LSB = Bit 1)
o B0 B1 … B15: Bit order is left to right (MSB = Bit 0; LSB = Bit 15)
o B15 B14 … B0: Bit order is right to left (MSB = Bit 15; LSB = Bit 0)
 Register Order: The order of the PLC memory registers written to and read from, used to support
64-bit data types.
o Order 1: R1 R2 R3 R4 (Default)
o Order 2: R2 R1 R4 R3
o Order 3: R3 R4 R1 R2
o Order 4: R4 R3 R2 R1
where R1, R2, R3, and R4 are the relative register addresses in the PLC.
 String variable style: PLC string-data format. Select the option for the style used by the device to
store strings in its registers.
o Full lengt h (space padded) (Default)
o C style (null terminated)
o Pascal style (includes length specifier)
 Register type: Select either Binary or BCD for the register type being used.
o Binary (Default)
o BCD
 Maximum address range: There are four sub-elements in this Maximum addressable registers box.
The maximum addressable registers can be obtained from the Modicon Concept or Modsoft
configuration programs. The PLC will return an error if a register outside of this range is used to read
data. The MB TCP Communication Driver filters out registers outside of this range and logs error
messages.

Element Description Minimum Value Maximum Value

Discrete input Enter the maximum number of addressable Min = 1 (one) Max = 9999
discrete inputs/read coils in the PLC (Default)

Coil Enter the maximum number of addressable Min = 1 (one) Max = 9999
write coils in the PLC. (Default)

19
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

Input register Enter the maximum number of addressable Min = 1 (one) Max = 9999
input registers in the PLC. (Default)

Holding register Enter the maximum number of addressable Min = 1 (one) Max = 9999
holding registers in the PLC. (Default)

 Block I/O size: This Block I/O Sizes box contains five sub-elements. The Communication Driver
uses the Block I/O sizes to maximize data throughput. The MB TCP Communication Driver uses a
256-byte buffer to read or write data to the PLC. The maximum value is the maximum number of
registers that can be read or written from/to the PLC in one command.

Element Description Minimum Value Maximum Value

Discrete Enter the maximum number of discrete inputs or Min = 1 (one) Max = 1976
input/coil read coils to read at one time. (Default)

Coil write Enter the maximum number of coils to writ e at Min = 1 (one) Max = 800
one time. (Default)

Holding register Enter the maximum number of holding registers Min = 1 (one) Max = 123
read to read at one time. (Default)

Holding register Enter the maximum number of holding registers Min = 1 (one) Max = 100
write to write at one time. (Default)

Input register Enter the maximum number of input registers to Min = 1 (one) Max = 123
read read at one time. (Default)

TSXMomentumRS Connection
The TS XMomentumRS connection is created from the ModbusBridge branch of the OI Server Manager
hierarchy.
To add TSXMomentumRS Connection to your MBTCP hierarchy
1. Right -click on your ModbusBridge branch, and select Add TSXMomentumRS Connection from the
shortcut menu.
o A new TS XMomentumRS object is created as a node in the hierarchy tree.
o Default name is New_TS XMomentumRS_000.

Note: You can add up to 247 objects of this type to the hierarchy.

2. Rename as appropriate.

20
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

o The New_TS XMomentumRS_000 Parameters configuration view is displayed.

This configuration view has 10 elements that are configurable.

21
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

o Checked – selected (Default)

o Not checked – not selected
 Use Concept data structure s (Reals): Select to read data from the PLC in concept data structure
format for Real item types. If checked, the Communication Driver will process the data in the same
register order as the Concept programming software.
o Checked – selected (Default)
o Not checked – not selected
 Bit order format: The format of the bit order entered int o the PLC. There are four bit order formats
available for selection.
o B1 B2 … B16: (Default) Bit order is left to right (MSB = Bit 1; LSB = Bit 16)
o B16 B15 … B1: Bit order is right to left (MSB = Bit 16; LSB = Bit 1)
o B0 B1 … B15: Bit order is left to right (MSB = Bit 0; LSB = Bit 15)
o B15 B14 … B0: Bit order is right to left (MSB = Bit 15; LSB = Bit 0)
 Register Order: The order of the PLC memory registers written to and read from, used to support
64-bit data types.
o Order 1: R1 R2 R3 R4 (Default)
o Order 2: R2 R1 R4 R3
o Order 3: R3 R4 R1 R2
o Order 4: R4 R3 R2 R1
where R1, R2, R3, and R4 are the relative register addresses in the PLC.
 String variable style: PLC string-data format. Select the option for the style used by the device to
store strings in its registers.
o Full lengt h (space padded) (Default)
o C style (null terminated)
o Pascal style (includes length specifier)
 Register type: Select either Binary or BCD for the register type being used.
o Binary (Default)
o BCD
 Maximum address range: There are five sub-elements in this Maximum addressable registers box.
The maximum addressable registers can be obtained from the Modicon Concept or Modsoft
configuration programs. The PLC will return an error if a register outside of this range is used to read
data. The MB TCP Communication Driver filters out registers outside of this range and logs error
messages.

Element Description Minimum Value Maximum Value

Discrete input Enter the maximum number of addressable Min = 1 (one) Max = 65536
discrete inputs or read coils in the PLC (Default)

Coil Enter the maximum number of addressable Min = 1 (one) Max = 65536
write coils in the PLC. (Default)

22
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

Input register Enter the maximum number of addressable Min = 1 (one) Max = 65536
input registers in the PLC. (Default)

Holding register Enter the maximum number of addressable Min = 1 (one) Max = 65536
holding registers in the PLC. (Default)

Extended Enter the maximum number of addressable Min = 1 (one) Max = 98303
register extended registers in the PLC. (Default)
Note: This option is not available if you set
Register size to 6.
 Block I/O size: The Block I/O Sizes box contains seven sub -elements. The Communication Driver
uses Block I/O Sizes to maximize data throughput. The MB TCP Communication Driver uses a
256-byte buffer to read or write data to the PLC. The maximum value is the maximum number of
registers that can be read or written from/to the PLC in one command.

Element Description Minimum Value Maximum Value

Discrete Enter the maximum number of discrete inputs Min = 1 (one) Max = 1976
input/coil read or coils to read at one time. (Default)

Coil write Enter the maximum number of coils to writ e at Min = 1 (one) Max = 800
one time. (Default)

Holding register Enter the maximum number of holding Min = 1 (one) Max = 123
read registers to read at one time. (Default)

Holding register Enter the maximum number of holding Min = 1 (one) Max = 100
write registers to write at one time. (Default)

Input register Enter the maximum number of input registers Min = 1 (one) Max = 123
read to read at one time. (Default)

Extended Enter the maximum number of extended Min = 1 (one) Max = 122
register read registers to read at one time. (Default)
Note: This option is unavailable if you set
Register size to 6.
Extended Enter the maximum number of extended Min = 1 (one) Max = 120
register write registers to write at one time. (Default)
Note: This option is unavailable if you set
Register size to 6.

ModbusPLCRS Connection
The ModbusPLCRS connection is added to t he Communication Driver hierarchy from the ModbusBridge
branch.
To add ModbusPLCRS Connection to your MBTCP hierarchy
1. Right -click on your ModbusBridge branch, and select Add ModbusPLCRS Connection from the
shortcut menu.
o A new ModbusPLCRS object is created as a node in the hierarchy tree.

23
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

o Default name is New_ModbusPLCRS_000.

Note: You can add up to 247 objects of this type to the hierarchy.

2. Rename as appropriate.
o The New_ModbusPLCRS_000 Parameters configuration view is displayed.

This configuration view has 13 configurable elements.

24
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

o The default value is 3 (three).

Note: When the Support Multiple Register Write Parameter is not selected in the Generic PLC
configuration, it implies that the PLC does not support multiple register writes and the server will only
write single registers to the PLC.
This means that items that contain more than one register cannot be written either. For example,
items such as 4xxxxx L, 4xxxxx I, 4xxxxx U, 4xxxxx F, 4xxxxx -4xxxxx M, 5 HRL, 5 HRF, 5 PV, 5
HRU, and 4xxxxx-4xxxxx cannot be written. When you try to write to the PLC with this parameter not
selected, the following error message will be logged to the logger, "Cannot write to multiple register
item: 4xxxxx L on Node: TCPPort.GenPLC. The PLC configurable paramet er Support Multiple
Register Write is not checked."

 Use Zero Ba sed Addressing: Select to choose 0-based addressing.

o Checked – selected, use 0-bas ed addressing
o Unchecked – not selected, use 1-based addressing (Default)
 Swap bytes: Select to swap bytes on data read and data poked.
o Checked - selected (Default)
o Not checked - not selected
 Bit order format: The format of the bit order entered int o the PLC. There are four bit order formats
available for selection.
o B1 B2 … B16: (Default) Bit order is left to right (MSB = Bit 1; LSB = Bit 16)
o B16 B15 … B1: Bit order is right to left (MSB = Bit 16; LSB = Bit 1)
o B0 B1 … B15: Bit order is left to right (MSB = Bit 0; LSB = Bit 15)
o B15 B14 … B0: Bit order is right to left (MSB = Bit 15; LSB = Bit 0)
 Register Order: The order of the PLC memory registers written to and read from, used to support
64-bit data types.

25
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

o Order 1: R1 R2 R3 R4 (Default)
o Order 2: R2 R1 R4 R3
o Order 3: R3 R4 R1 R2
o Order 4: R4 R3 R2 R1
where R1, R2, R3, and R4 are the relative register addresses in the PLC.
 Register size (digits): Select the correct register size for addressing the PLC.
o 4-digit is used for addressing the Modbus Generic 4-Digit PLCs.
o 5-digit applies to the Modbus Generic 5 -Digit PLCs.
o 6-digit is used for addressing the Modbus Generic 6-Digit PLCs (default ).

Note: The selection for the Register size determines the maximum address range. They are
changeable as in other support ed PLCs listed in Supported MBTCP OI Server Hardware and
Firmware on page 57.
For 4-digit, the maximum value is 999; for 5-digit, the maximum value is 9999; for 6 -digit, the
maximum value is 65536 (default).

 String variable style: PLC string-data format. Select the option for the style used by the device to
store strings in its registers.
o Full lengt h (space padded) (Default)
o C style (null terminated)
o Pascal style (includes length specifier)
 Register type: Select either Binary or BCD for the register type being used.
o Binary (Default)
o BCD
 Block I/O size: This Block I/O Sizes box contains four sub-elements. The Communication Driver
uses Block I/O Sizes to maximize data throughput. The MB TCP Communication Driver uses a
256-byte buffer to read or write data to the PLC. The maximum value is the maximum number of
registers that can be read or written from/to the PLC in one command.

Element Description Minimum Value Maximum Value

Discrete Enter the maximum number of discrete inputs or Min = 1 (one) Max = 1976
input/coil read coils to read at one time. (Default)

Coil write Enter the maximum number of coils to writ e at Min = 1 (one) Max = 800
one time. (Default)

The logic al endpoint for each branch of the MB TCP hierarchy tree is a hardware device (PLC).

Note: In order to use the Communication Driver, you must activate it. See the OI S erver Manager
documentation for information about how to activate and deactivate the Communication Driver.

26
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

TSXQuantum Connection
To add TSXQuantum Connection to your MBTCP hierarchy
1. Right -click on the TCPIP _PORT branch, and select Add TSXQuantum Connection from the
shortcut menu.
o A new TS XQuantum object is created as a node in the hierarchy tree.
o Default name is New_TSXQuantum_000.
2. Rename as appropriate.
o The New_TS XQuantum_000 Parameters configuration view is displayed.

This configuration view has 11 elements that are configurable:

 Network address: Enter the host name or the IP address of the PLC.
o The number of characters cannot be more than 255.
o The field cannot be blank (the number of characters cannot be zero).
o The default value is 1.0.0.0.
 Reply timeout (sec): Enter the amount of time the server will wait for an acknowledgment.
o The minimum value is 1 (one).
o The maximum value is 60.
o The default value is 3 (three).

27
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

 Maximum outstanding message s: Enter the maximum number of messages allowed in the queue.
o The minimum value is 1 (one).
o The maximum value is 20.
o The default value is 4 (four).
 Use Concept data structure s (Longs): Select to read data from the PLC in concept dat a structure
format for Long item types. If checked, the Communication Driver will process the data in the same
register order as the Concept programming software.
o Checked – selected (Default)
o Not checked – not selected
 Use Concept data structure s (Reals): Select to read data from the PLC in concept data structure
format for Real item types. If checked, the Communication Driver will process the data in the same
register order as the Concept programming software.
o Checked – selected (Default)
o Not checked – not selected
 Bit order format: The format of the bit order entered into the PLC. There are four bit order formats
available for selection.
o B1 B2 … B16: (Default) Bit order is left to right (MSB = Bit 1; LSB = Bit 16)
o B16 B15 … B1: Bit order is right to left (MSB = Bit 16; LSB = Bit 1)
o B0 B1 … B15: Bit order is left to right (MSB = Bit 0; LSB = Bit 15)
o B15 B14 … B0: Bit order is right to left (MSB = Bit 15; LSB = Bit 0)
 Register Order: The order of the PLC memory registers written to and read from, used to support
64-bit data types.
o Order 1: R1 R2 R3 R4 (Default)
o Order 2: R2 R1 R4 R3
o Order 3: R3 R4 R1 R2
o Order 4: R4 R3 R2 R1
where R1, R2, R3, and R4 are the relative register addresses in the PLC.
 String variable style: PLC string-data format. Select the option for the style used by the device to
store strings in its registers.
o Full lengt h (space padded) (Default)
o C style (null terminated)
o Pascal style (includes length specifier)
 Register type: Select either Binary or BCD for the register type being used.
o Binary (Default)
o BCD
 Maximum address range: There are five sub-elements in this Maximum addressable registers box.
The maximum addressable registers can be obtained from the Modicon Concept or Modsoft
configuration programs. The PLC will ret urn an error if a register within the configured range is used
to read data but does not exist in the PLC. The MB TCP Communication Driver filters out registers
outside of this range and logs error messages.

28
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

Element Description Minimum Value Maximum Value

Discrete input Enter the maximum number of addressable Min = 1 (one) Max = 65536
discrete inputs (read coils) in the PLC (Default)

Coil Enter the maximum number of addressable Min = 1 (one) Max = 65536
write coils in the PLC. (Default)

Input register Enter the maximum number of addressable Min = 1 (one) Max = 65536
input registers in the PLC. (Default)

Holding register Enter the maximum number of addressable Min = 1 (one) Max = 65536
holding registers in the PLC. (Default)

Extended register Enter the maximum number of addressable Min = 1 (one) Max = 98303
extended registers in the PLC. (Default)

Block I/O size: The Block I/O Sizes box contains seven sub-elements. The Communication Driver uses
the Block I/O sizes to maximize data t hroughput. The MB TCP uses a 256 -byte buffer to read or writ e data
to the PLC. The maximum value is the maximum number of registers that can be read or written from/to
the PLC in one command.

Element Description Minimum Value Maximum Value

Discrete input/coil Enter the maximum number of discrete inputs Min = 1 (one) Max = 1976
read or coils to read at one time. (Default)

Coil write Enter the maximum number of coils to write at Min = 1 (one) Max = 800
one time. (Default)

Holding register Enter the maximum number of holding Min = 1 (one) Max = 123
read registers to read at one time. (Default)

Holding register Enter the maximum number of holding Min = 1 (one) Max = 100
write registers to write at one time. (Default)

Input register read Enter the maximum number of input registers Min = 1 (one) Max = 123
to read at one time. (Default)

Extended register Enter the maximum number of extended Min = 1 (one) Max = 122
read registers to read at one time. (Default)

Extended register Enter the maximum number of extended Min = 1 (one) Max = 120
write registers to write at one time. (Default)

TSXMomentum Connection
From the TCPIP _PORT branch of the Communication Driver hierarchy, you can also create a
TS XMoment um Connection.
To add TSXMomentum Connection to your MBTCP hierarchy
1. Right -click on your TCP IP_PORT branch, and select Add TSXMomentum Connection.

29
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

o A new TS XMomentum object is created as a node in the hierarchy tree.

o Default name is New_TS XMomentum_000.
2. Rename as appropriate.
o The New_TS XMomentum_000 Parameters configuration view is displayed.

This configuration view has 11 elements that are configurable.

 Network address: Enter the host name or IP address of the PLC.
o The number of characters cannot be more than 255.
o The field cannot be blank. (The number of characters cannot be zero (0).
o The default value is 1.0.0.0.
 Reply timeout (sec): Enter the amount of time the server will wait for an acknowledgment.
o The minimum value is 1 (one).
o The maximum value is 60.
o The default value is 3 (three).
 Maximum outstanding message s: Enter the maximum number of outstanding messages that can
be in the queue for the PLC.
o The minimum value is 1 (one).
o The maximum value is 20.
o The default value is 4 (four).

30
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

 Use Concept data structure s (Longs): Select to read data from the PLC in concept dat a structure
format for Long item types. If checked, the Communication Driver will process the data in the same
register order as the Concept programming software.
o Checked – selected (Default)
o Not checked – not selected
 Use Concept data structure s (Reals): Select to read data from the PLC in concept data structure
format for Real item types. If checked, the Communication Driver will process the data in the same
register order as the Concept programming software.
o Checked – selected (Default)
o Not checked – not selected
 Bit order format: The format of the bit order entered int o the PLC. There are four bit order formats
available for selection.
o B1 B2 … B16: (Default) Bit order is left to right (MSB = Bit 1; LSB = Bit 16)
o B16 B15 … B1: Bit order is right to left (MSB = Bit 16; LSB = Bit 1)
o B0 B1 … B15: Bit order is left to right (MSB = Bit 0; LSB = Bit 15)
o B15 B14 … B0: Bit order is right to left (MSB = Bit 15; LSB = Bit 0)
 Register Order: The order of the PLC memory registers written to and read from, used to support
64-bit data types.
o Order 1: R1 R2 R3 R4 (Default)
o Order 2: R2 R1 R4 R3
o Order 3: R3 R4 R1 R2
o Order 4: R4 R3 R2 R1
where R1, R2, R3, and R4 are the relative register addresses in the PLC.
 String variable style: PLC string-data format. Select the option for the style used by the device to
store strings in its registers.
o Full lengt h (space padded) (Default)
o C style (null terminated)
o Pascal style (includes length specifier)
 Register type: Select either Binary or BCD for the register type being used.
o Binary (Default)
o BCD
 Maximum address range: There are five sub-elements in this Maximum addressable registers box.
The maximum addressable registers can be obtained from the Modicon Concept or Modsoft
configuration programs. The PLC will return an error if a register outside of this range is used to read
data. The MB TCP Communication Driver filters out registers outside of this range and logs error
messages.

Element Description Minimum Value Maximum Value

Discrete input Enter the maximum number of addressable Min = 1 (one) Max = 65536
discrete inputs (read coils) in the PLC (Default)

31
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

Coil Enter the maximum number of addressable Min = 1 (one) Max = 65536
write coils in the PLC. (Default)

Input register Enter the maximum number of addressable Min = 1 (one) Max = 65536
input registers in the PLC. (Default)

Holding register Enter the maximum number of addressable Min = 1 (one) Max = 65536
holding registers in the PLC. (Default)

Extended register Enter the maximum number of addressable Min = 1 (one) Max = 98303
extended registers in the PLC. (Default)

 Block I/O size: This Block I/O Sizes box contains seven sub-elements. The Communication Driver
uses the block I/O sizes to maximize data throughput. The MB TCP Communication Driver us es a
256-byte buffer to read or write data to the PLC. The maximum value is the maximum number of
registers that can be read or written from/to the PLC in one command.

Element Description Minimum Value Maximum Value

Discrete input/coil Enter the maximum number of discrete Min = 1 (one) Max = 1976
read inputs or coils to read at one time. (Default)

Coil write Enter the maximum number of coils to writ e Min = 1 (one) Max = 800
at one time. (Default)

Holding register Enter the maximum number of holding Min = 1 (one) Max = 123
read registers to read at one time. (Default)

Holding register Enter the maximum number of holding Min = 1 (one) Max = 100
write registers to write at one time. (Default)

Input register read Enter the maximum number of input Min = 1 (one) Max = 123
registers to read at one time. (Default)

Extended register Enter the maximum number of extended Min = 1 (one) Max = 122
read registers to read at one time. (Default)

Extended register Enter the maximum number of extended Min = 1 (one) Max = 120
write registers to write at one time. (Default)

TSXPremium Connection
From the TCPIP _PORT branch of the Communication Driver hierarchy, you can also create a
TS XPremium Connection.
To add TSXPremium objecConnection ts to your MBTCP hierarchy
1. Right -click on your TCP IP_PORT branch, and select Add TSXPremium Connection.
o A new TS XPremium object is created as a node in the hierarchy tree.
o Default name is New_TS XP remium_000.

Note: You can add up to 1024 objects of this type to the hierarchy.

2. Rename as appropriate.

32
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

o The New_TS XPremium_000 Parameters configuration view is displayed.

This configuration view has 12 elements that are configurable.

 Network address: Enter the host name or IP address of the PLC.
o The number of characters cannot be more than 255.
o The field cannot be blank. (The number of characters cannot be zero (0).
o The default value is 1.0.0.0.
 Reply timeout (sec): Enter the amount of time the server will wait for an acknowledgment.
o The minimum value is 1 (one).
o The maximum value is 60.
o The default value is 3 (three).
 Maximum outstanding message s: Enter the maximum number of outstanding messages in the
queue for the PLC.
o The minimum value is 1 (one).
o The maximum value is 20.
o The default value is 4 (four).
 Use Concept data structure s (Longs): Select to read data from the PLC in concept dat a struc ture
format for Long item types. If checked, the Communication Driver will process the data in the same
register order as the Concept programming software.

33
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

o Checked – selected (Default)

o Not checked – not selected
 Use Concept data structure s (Reals): Select to read data from the PLC in concept data structure
format for Real item types. If checked, the Communication Driver will process the data in the same
register order as the Concept programming software.
o Checked – selected (Default)
o Not checked – not selected
 Use Zero Ba sed Addressing: Select to choose 0-based addressing.
o Checked – selected, use 0-bas ed addressing
o Unchecked – not selected, use 1-based addressing (Default)
 Bit order format: The format of the bit order entered int o the PLC. There are four bit order formats
available for selection.
o B1 B2 … B16: (Default) Bit order is left to right (MSB = Bit 1; LSB = Bit 16)
o B16 B15 … B1: Bit order is right to left (MSB = Bit 16; LSB = Bit 1)
o B0 B1 … B15: Bit order is left to right (MSB = Bit 0; LSB = Bit 15)
o B15 B14 … B0: Bit order is right to left (MSB = Bit 15; LSB = Bit 0)
 Register Order: The order of the PLC memory registers written to and read from, used to support
64-bit data types.
o Order 1: R1 R2 R3 R4 (Default)
o Order 2: R2 R1 R4 R3
o Order 3: R3 R4 R1 R2
o Order 4: R4 R3 R2 R1
where R1, R2, R3, and R4 are the relative register addresses in the PLC.
 String variable style: PLC string-data format. Select the option for the style used by the devic e to
store strings in its registers.
o Full lengt h (space padded) (Default)
o C style (null terminated)
o Pascal style (includes length specifier)
 Register type: Select either Binary or BCD for the register type being used.
o Binary (Default)
o BCD
 Maximum address range: There are four sub-elements in this Maximum addressable registers box.
The maximum addressable registers can be obtained from the Modicon Concept or Modsoft
configuration programs. The PLC will return an error if a register outside o f this range is used to read
data. The MB TCP Communication Driver filters out registers outside of this range and logs error
messages.

34
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

Element Description 1-ba sed (Default) Zero-ba sed

Addre ssing Addre ssing

Discrete input Enter the maximum number of addressable Min = 1 (Default) Min = 0
discrete inputs (read coils) in the PLC Max = 65536 Max = 65535

Coil Enter the maximum number of addressable Min = 1 (Default) Min = 0

write coils in the PLC. Max = 65536 Max = 65535

Input register Enter the maximum number of addressable Min = 1 (Default) Min = 0
input registers in the PLC. Max = 65536 Max = 65535

Holding register Enter the maximum number of addressable Min = 1 (Default) Min = 0
holding registers in the PLC. Max = 65536 Max = 65535

 Block I/O size: The Block I/O Sizes box contains five sub-elements. The Communication Driver
uses the block I/O sizes to maximize data throughput. The MB TCP Communication Driver us es a
256-byte buffer to read or write data to the PLC. The maximum value is the maximum number of
registers that can be read or written from/to the PLC in one command.

Element Description Minimum Value Maximum

Value

Discrete Enter the maximum number of discrete inputs Min = 1 (one) Max = 1000
input/coil read or coils to read at one time. (Default)

Coil write Enter the maximum number of coils to writ e at Min = 1 (one) Max = 800
one time. (Default)

Holding register Enter the maximum number of holding Min = 1 (one) Max = 123
read registers to read at one time. (Default)

Holding register Enter the maximum number of holding Min = 1 (one) Max = 100
write registers to write at one time. (Default)

Input register Enter the maximum number of input registers Min = 1 (one) Max = 123
read to read at one time. (Default)

ModbusPLC Connection
The ModbusPLC connection is created from the TCP IP_PORT branch of the Communication Driver
hierarchy. It is intended for PLCs/controllers that use the Modbus protocol but not in the list of Supported
MBTCP OI Server Hardware and Firmware on page 57. However, the PLCs/controllers need to conform
to and comply with the Modbus specifications as listed in Controller Function Codes on page 58, Modbus
Exception Codes on page 59, Controller Function Codes on page 58, and Data Types on page 49.
To add ModbusPLC Connection to your MBTCP hierarchy
1. Right -click on your TCP IP_PORT branch, and select Add ModbusPLC Connection.
o A new ModbusPLC object is created as a node in the hierarc hy tree.
o It is named New_ModbusPLC_000 by default.
2. Rename as appropriate.

35
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

o The New_ModbusPLC_000 Parameters configuration view is displayed.

This configuration view has 17 elements that are configurable.

Note: The MB TCP Communication Driver uses port 502 as the default port number to contact the PLC.
The port number is configurable in this object. This will override the port setting in the parent
TCPIP _PORT object for this connectivity.

 Reply timeout (sec): Enter the amount of time the server will wait for an ac knowledgment.
o The minimum value is 1 (one).
o The maximum value is 60.
o The default value is 3 (three).
 Maximum outstanding message s: Enter the maximum number of outstanding messages in the
queue for the PLC.
o The minimum value is 1 (one).
o The maximum value is 20.

36
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

o The default value is 1 (one).

Note: When the Support Multiple Register Write Parameter is not selected in the Generic PLC
configuration, it implies that the PLC does not support multiple register writes and the server will only
write single registers to the PLC.
This means items that contain more than one register cannot be written either. For ex ample, items such
as 4xxxxx L, 4xxxxx I, 4xxxxx U, 4xxxxx F, 4xxxxx -4xxxxx M, 5 HRL, 5 HRF, 5 PV, 5 HRU, and
4xxxxx-4xxxxx cannot be written. When you try to write to the PLC with this parameter not selected, the
following error message will be logged to the logger, "Cannot write to multiple register item: 4xxxxx L on
Node: TCPPort.GenP LC. The PLC configurable parameter Support Multiple Register Write is not
checked."

 Use Zero Ba sed Addressing: Select to choose 0-based addressing.

o Checked – selected, use 0-bas ed addressing
o Unchecked – not selected, use 1-based addressing (Default)
 Swap bytes: Select to swap bytes on data read and data poked.
o Checked - selected (Default)
o Not checked - not selected
 Close Ethernet connection when no activity: Select this option to close the socket connection if
no item is advised to the device (Hierarchy). This can happen when the client has removed all items
advis ed to the hierarchy.
 Bit order format: The format of the bit order entered int o the PLC. There are four bit order formats
available for selection.
o B1 B2 … B16: (Default) Bit order is left to right (MSB = Bit 1; LSB = Bit 16)
o B16 B15 … B1: Bit order is right to left (MSB = Bit 16; LSB = Bit 1)

37
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

o B0 B1 … B15: Bit order is left to right (MSB = Bit 0; LSB = Bit 15)
o B15 B14 … B0: Bit order is right to left (MSB = Bit 15; LSB = Bit 0)
 Register Order: The order of the PLC memory registers written to and read from, used to support
64-bit data types.
o Order 1: R1 R2 R3 R4 (Default)
o Order 2: R2 R1 R4 R3
o Order 3: R3 R4 R1 R2
o Order 4: R4 R3 R2 R1
where R1, R2, R3, and R4 are the relative register addresses in the PLC.
 Register size (digits): Select the correct register size for addressing the PLC.
o 4-digit is used for addressing the Modbus Generic 4-Digit PLCs.
o 5-digit applies to the Modbus Generic 5 -Digit PLCs.
o 6-digit is used for addressing the Modbus Generic 6-Digit PLCs. (Default )

Note: The selection for the Register size determines the maximum address range. They are changeable
as in other supported PLCs listed in Supported MBTCP OI Server Hardware and Firmware on page 57.
For 4-digit, the maximum value is 999; for 5-digit, the maximum value is 9999; for 6 -digit, the maximum
value is 65536.

 String variable style: PLC string-data format. Select the option for the style used by the device to
store strings in its registers.
o Full lengt h ( space padded) (Default )
o C style (null terminated)
o Pascal style (includes length specifier)
 Register type: Select either Binary or BCD for the register type being used.
o Binary (Default)
o BCD
 Block I/O size: This Block I/O Sizes box contains four sub-elements. The Communication Driver
uses the block I/O sizes to maximize data throughput. The MB TCP Communicati on Driver us es a
256 byte buffer to read or write data to the PLC. The maximum value is the maximum number of
registers that can be read or written from/to the PLC in one command.

Element Description Minimum Value Maximum Value

Discrete input/coil Enter the maximum number of discrete inputs Min = 1 (one) Max = 1976
read or coils to read at one time. (Default)

Coil write Enter the maximum number of coils to write at Min = 1 (one) Max = 800
one time. (Default)

Holding register Enter the maximum number of holding Min = 1 (one) Max = 123
read registers to read at one time. (Default)

Holding register Enter the maximum number of holding Min = 1 (one) Max = 100
write registers to write at one time. (Default)

38
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

String-Data Handling
The MB TCP Communication Driver can process three different configurable string variable styles:
 Full Length
 C Style
 Pascal
Depending on what string style the PLC is using, you can configure the server using the user interface in
the PLC configuration view in order to use the appropriate string variable style.

Full Length Style

If strings are read using the Full Length Style, each string always uses all of the registers alloc ated. The
PLC string is stored in the server string as is.
If a string is written and the string is shorter than the allocation of registers, it is padded with ASCII space
characters (hex 20).
For example:
If the string "Communications" is stored in the string item "400001-400010 m," registers 400001 through
400005 contain the string "Communications" and registers 400006 through 400010 contain spac es.
If the string "Communications" is stored in the string item "400001-400005 m," registers 400001 through
400005 contain the string "Communications" and no spaces are stored.
If the string "Communications" is stored in the string item "400001-400005 m," registers 400001 through
400005 contain the string "Communications" and no spaces are stored.
A message is placed in the logger indicating that the string was truncated.

C Style
If a string is read using the C Style, the string always uses all of the registers allocated. The PLC stri ng is
stored in the server string as is, except that the last character contained in the last register of the string is
replaced with a null character (hex 00).
If a string is written and the string is shorter than the allocation of registers, it is padded with ASCII null
characters (hex 00).
For example:
If the string "Communications" is stored in the string item "400001-400010 m," registers 400001 through
400005 contain the string "Communications" and registers 400006 through 400010 contain nulls.
If the string "Communications" is stored in the string item "400001-400005 m," registers 400001 through
400005 contain the truncated string "Wonderwar0" with a null character replacing the last character "e."
A message is placed in the logger indicating that the string was truncated.

Pascal Style
If strings are read using the Pascal Style, each string uses a length obtained from the first byte of the
string to store data in the server. The PLC string is stored in the server string as is, up to the length
obtained from the first byte of the string. If the lengt h is greater than the number of registers defined in the
item, then the PLC string is stored in the server string as is, up to the maximum number of registers.
The first byte written of any string of this style contains the character count. The string being written starts
in the second byte. If a string is written and the string plus the character count are shorter than the
allocation of registers, it is padded with ASCII null characters (hex 00).
For example:

39
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

If the string "Communications" is stored in the string item "400001-400010 m," registers 400001 through
400006 contain the string "(10)Communications0" and registers 400007 through 400010 contain nulls.
The (10) in the string implies one byte cont aining the character count.
If the string "Communications" is stored in the string item "400001-400005 m," registers 400001 through
400005 contain the truncated string "(9)Communication."
A message is placed in the logger indicating that the string was truncated.

Message Optimization
The MB TCP Communication Driver uses Multi read and write commands to optimize PLC read/ write
messages. The MB TCP Communication Driver optimizes the reading and writing of data by grouping
points that are in consecutive registers. The Block I/O sizes parameters control the buffer size. The
default is to maximize the buffer size.

Note: The number of bytes for the query and response buffers must not exceed the Modbus maximum
buffer size of 256 bytes.

Configuring Device Redundancy

The OI Server Manager provides the ability to assign redundant device for fail -over protection in the
event of device failure. Two device must be configured in the same Communication Driver having
identical item syntax.
Primary and secondary devices will be setup in the REDUNDA NT_DEV ICE object in the SMC, along
with a common item name (ping item) shared by each device to determine device status.
To setup up a REDUNDANT_DEVICE from the configuration branch:
1. Set-up a primary device and hierarchy in the OI Server Manager in the SMC.
2. Create at least one device item that can be shared between the primary and secondary devices to
determine devic e status.
3. Set up a secondary device on the same Communication Driver. Once again, create an identical
devic e item within the secondary device so that device status can be determined.
4. Right -click on Configuration, and select Add REDUNDANT_DEVICE Connection. An object
called New_RE DUNDANT_DEV ICE_000 is created.

5. Rename the newly created object as appropriate. The New_REDUNDA NT_DEVICE_000

configuration view is displayed in the Configuration branch of the hierarchy.

40
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

6. Enter or use the device browser to select the primary and secondary devices. Save the hierarchy
node configuration by clicking on the save icon.

Note: The primary device and secondary device must be a PLC object, and not the Port or Bridge
objects.

Note: Unsolicited message configuration is not supported from the device redundant hierarchy.

Important: A Ping item must be specified and be a valid tag in both the primary and secondary
controllers to determine the connection status for $SYS$Status. The Ping item can be a static item in the
devic e such as a firmware version or proc essor type. If the Ping item is invalid or does not exist in the
controller, the failover operation may not work correctly as the value of $SYS$Status may continue to
stay as FALSE in the standby device.

Device Group Definitions

The Device Groups tab in the OI Server Manager user interface is used to create new, modify, or dele te
devic e group definitions for an object. For DDE/SuiteLink communications, one or more device group
definitions must exist for each PLC that the Communication Driver will communicat e with.

Important: For DDE/SuiteLink, it is strongly recommended that eac h device group (topic) definition
contain a unique name for the PLC associated with it. The OPC, however, has the flexibility to use any
names, including duplicate names, for the device group definitions.

Each device group (topic) definition should contain a unique name for the PLC associated with it.
The Device Groups dialog box, which is displayed by clicking the Device Groups tab in the
New_< Name>P LC_000 Parameters configuration view, is used to perform the following activities:
 Adding, defining, and deleting device groups.

41
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

Note: When you add a new device group, ent er a unique name.

 Configuring the Communication Driver to receive unsolicited messages.

 Configuring default update intervals.
Editing update int ervals for the device groups.

Note: When you select another part of the Communication Driver tree hierarchy, you are prompt ed to
save the modifications to the configuration set.

To create or add device groups

1. Right -click in the Device Groups dialog box.
2. Select the Add command from the shortcut menu.
o When you add a new device group, enter a unique name (up to 32 characters long).
To make changes on device groups’ names
Change a device group’s name for an object as follows:
 In the Name column, double-click on the device group’s name to be modified and make the change.
To delete device groups
Deleting a device group from the list can be performed as follows:
1. Right -click on the devic e group to be deleted.
2. Select the Delet e command from the shortcut menu.

Note: When you select another part of the MB TCP Communication Driver tree hierarchy, you are
prompted to save the modifications to the configuration set.

To configure the MBTCP Communication Driver to receive unsolicited messages

This option is available only to the PLC nodes that are directly connected to the TCP IP_P ort node. PLC
nodes that are connected underneath the ModbusBridge node do not have this capability.
Some PLCs, for example the TS X Premium PLC, can send Holding Register and Coil unsolicited data to
the MBTCP DASever, while other PLCs, for example the TS X Quantum PLC, can send the Holding
Register unsolicited data only to the Communication Driver.
Note: If you have globally disabled unsolicited messages using the DASMB TCP.aarul file, configuring
Device Group paramet ers to support unsolicited messages will have no effect. For more information
about enabling and disabling unsolicited messages, see Unsolicited Message Handling on page 47.

1. Click on the PLC’s name in the PLC branc h of the Communic ation Driver hierarchy.
2. Select the Device Group tab of the configuration view pane at right.
3. Add a new device group or select an existing device group.
4. Right -click on the devic e group name, then select Edit from the shortcut menu.

42
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

o The Device Group Parameters dialog box is displayed.

5. In the Device Group Parameters dialog box, select the Support Unsolicited Messages check box.
6. Click the OK button to close the dialog box.

Note: Since the status of Support Unsolicited Messag es check box cannot be readily viewed from the
Device Groups tab, proper naming of device groups which support unsolicited messages is strongly
recommended. Unsolicited messages are only supported in the base instance of the Communication
Driver (the instance of the Communication Driver without the custom name).

7. Save the configuration change by clicking the Save icon located at the upper-right corner of the
configuration view pane.

Note: For more information on unsolicited messages, see Unsolicited Message Handling on page 47.

To configure default update intervals

1. To configure a default updat e interval for the object, right-click in the Device Groups dialog box.
2. Select Config Default Update Interval from the shortcut menu.
To make changes on update intervals
A change on an update interval for an object can be made as follows:
 Double-click on the value to be modified in the Updat e Int erval column and make the change.
o Update Interval is the frequency (in milliseconds) that the Communication Driver acquires data
from the topics associated with that device group.
o Different topics can be polled at different rates in a PLC by defining multiple device-group names
for the same PLC and setting a different Updat e Interval for each device group.
o If you also select the "Support Unsolicited Message" checkbox as described ab ove, duplicat e
updates could be received by the items associated with the device group. To avoid duplicate
updates, set the Update Int erval to 0 (zero).

Note: When you select another part of the MB TCP Communication Driver tree hierarchy, you are
prompted to save the modifications to the configuration set.

Each configuration view associated with nodes/objects in the Communication Driver hierarchy tree has a
common feat ure, the Save button.

43
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

1. When you modify any parameters in the Device Gro ups dialog box, click Save to save and
implement the new modifications.
o If you do not click Save, the configuration is reset to its original condition (since the last save).
2. After all modifications, you must save when prompted for the new data t o be saved to the
configuration set.

Device Item Definitions

The Device Items tab in the New_< Name>PLC_000 Paramet ers configuration view is used to define
aliases to actual PLC items. The Device Items dialog box is the place where the foll owing activities are
performed:
 Creating new device item definitions for PLC items.
 Modifying the existing devic e items.
 Deleting device items.
 Archiving the created list of device items to a .csv file, a file with values separated by commas.
 Importing a .csv file into the Device Items tab.
Each device item definition should contain a unique name for the PLC associated with it.
The Device Items dialog box has the following two columns:
 Name: This column defines the alias names to actual PLC it ems.
 Item Reference: The actual PLC item names, linked to the created aliases, are defined in this
column.
For example:
For Modicon holding registers 400001 and 400010, the following entries can be created.

Name Item Reference

Holding1 400001
Holding10F 400010 F

Note: When you create or add a new device item, a unique name needs to be entered for it.

Once the Device Items feature is utilized to configure item names, the Communication Driver gains the
capability to browse OP C Items. When the Communication Driver is running and an OP C client requests
item information, the configured items will show up under the PLC hierarchy node.
To create or add device items
1. Right -click in the Device Items dialog box.
2. Select the Add command from the shortcut menu.
o A device item is created in the Name column, and it is numerically named by default.
For example, Item_0, It em_1, and so on.
3. Change the default name by double -clicking on it and entering the new name.
o Enter a unique name for the new device item.
For example, "Holding1."
To add item references
Item references for eac h of the device items that have been created can be added as follows:

44
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

1. In the Item Reference column, double -click on the area in the same horizontal line as the selected
devic e item.
2. Type in the actual PLC item name in the frame that appears.
o For example, "400001."
3. Click anywhere in the dialog box or press the ENTER key to have the change take effect.

Note: System items are not valid item references, but Communication Driver -specific system items are
valid.

To rename a device item from the list

1. Right -click on the devic e item to be renamed.
2. Select the Rename command from the shortcut menu and enter the new device item name.
3. Click anywhere in the dialog box or press the ENTER key to apply t he change.
To delete a device item from the list
1. Right -click on the devic e item to be deleted.
2. Select the Delet e command from the shortcut menu.
o The device item and its corres ponding actual P LC item name will be deleted from the dialog box.

Note: When you select another part of the MB TCP Communication Driver tree hierarchy, you are
prompted to save the modifications to the configuration set.

To clear all device items

1. Right -click anywhere in the Device Items dialog box.
2. Select the Clear All command from the shortcut menu.
o All the device items listed in the dialog box, including their corres ponding actual PLC item
names, will be delet ed.Related Topics

Exporting and Importing Communication Driver Item Data

The Export and Import commands on the shortcut menu enable you to export and import the
Communication Driver item dat a to and from a CSV file, after the configuration of the Device Items has
been completed. These commands will allow you to perform an off-line, large-scale edit on the item data
configured for a controller, and import what has been edited back into the controller configuration. Import
what has been edited back into the PLC configuration.
The Export and Import features on the shortcut menu of t he Device It ems dialog box enable you to export
and import the Communication Driver device item data to and from a CSV file, after the configuration of
the Device It ems has been completed. These featu res provide you with the following capabilities:
 Archive lists of device items.
 Import an archived list of devic e items into the Device Items dialog box when you need to utilize or
reconfigure any of the device items on the archived list.
 Perform an off-line, large-scale edit on the item data configured for a device item list.
 Import what has been edited back into the Device Items configuration.
To export device items
1. Right -click anywhere in the Device Items dialog box.
2. Select the Export command from the shortcut menu.
o The standard Save As dialog box appears.

45
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

o The file name has defaulted into "PLC Hierarchyname.cs v," within the
current-system-configured default directory.
3. Accept the defaults to save the file.
o The file is saved as New_<PLC Name>_000.cs v.
o It is editable in Microsoft Excel.
However, if you prefer to save the list someplace else and rename it, perform the following steps
after step 2.
4. Select the folder int o which the list is to be saved.
5. Name the list to be archived.
6. Click the Save button.
o The whole list will be saved as a .csv file in Excel.
The file can now be edited off-line. It contains one row for each item configured with two
columns, Name and Item Referenc e, respectively.
To import device items
1. To import the list, right-click anywhere in the Device Items dialog box.
2. Select the Import command from the shortcut menu.
3. Select the archived list (.csv file) to be imported from the folder in which it is saved.
4. Click the Open button.
o The whole list will be brought into the Device Items dialog box.

Note: When the list to be imported contains duplicate names as found in the current list but the Item
Referenc es are different, a dialog box will appear to prompt you to make a selection.

To import device item data that has been edited off-line

1. Right -click anywhere in the Device Items dialog box.
2. Clear all the item data you wish to replace with the edited .cs v file by s electing the Clear All
command.
o The data will be cleared after you click on Yes to confirm the deletion.
3. Select the Import command from the shortcut menu.
o The standard Open dialog box appears.
o It defaults to the .csv file extension within the current -system-configured default directory.
4. Browse for the specific CSV file you want to import, select it, then click on the Open button.
o The OI Server Manager will import the edited file and deposit it in the Device It ems dialog box.

o While imported files are processed, new item references will be added, based on unique names.

46
Configuring the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

If there are duplicat e names, you will be provided with the option to replace the existing entry with the
new entry, or ignore the new entry.

Scan-Based Message Handling

The Communication Drivers are based on the concept of polling a hard ware device for information. This
polling is driven by a need which is expressed in the form of requests from one or more clients. Once a
particular piece of information has been requested by a client, the Communication Driver formulates its
own request and sends that request to the hardware device. The Communication Driver then waits for a
response to its request. Once the information has been received, the Communication Driver passes that
information back to the client, and repeats the process until all c lients have ceased requesting
information.
The rate at which the Communication Driver will poll a particular device for a s pecific piece of information
is defined in the device group (topic definition) inside the Communication Driver, using a parameter
called the Update Interval. When setting this parameter, there is always a trade -off bet ween the updat e
speed of the device group and the resulting dec rease in system responsiveness.
Since a fast response is generally wanted, you may be tempted to set the Update Interval to a value
close to 0 (zero) seconds. However, if every point is polled at this rate, the entire system will slow down.
Therefore, it is recommended that you set the U pdate Interval to a more reasonable value. You could
also create multiple device groups for each device, setting the Updat e Int erval to different values, then
assigning different items to different device groups depending on how quickly the values change a nd
how quickly you want to see an update of those changes.
Some items, like alarms, change very infrequently but because of their importance require very fast
updates. For these items, set the Update Interval at a very small value. For an immediate respons e, set
the Update Interval at 1 (one).

Unsolicited Message Handling

A PLC typically registers a critical event before the Communication Driver has had a chance to poll for
that data. To mitigate the potential information lag, the PLC shoul d have the capability to inform the
Communication Driver immediately, without having to wait for the Communication Driver to poll it.
This is the role of an unsolicited message. Once a PLC has determined that a critical condition (such as
an alarm event) exists, it can generate a message that is immediately sent to the Communication Driver
without a prior request from the Communication Driver. Compared to polling the PLC for an irregular
event at fixed intervals, sending unsolicited messages from the PLC to the Communication Driver when
the event occurs not only reduces net work traffic, but may also get the data to the server more promptly.

Unsolicited Message Behavior

The unsolicited messaging feature is available only to controllers that a re directly connected to the
TCPIP _PORT. Controllers under the ModbusBridge Object hierarchy cannot use this feature.
In accordance with the prot ocol, the receiver of unsolicited messages must acknowledge the receipt of
unsolicited messages.

Unsolicited Message Configuration

In order to support unsolicited messages from the devices, the MBTCP Communication Driver by default
listens on Ethernet port 502.
To facilitate testing wit h soft ware simulat ors residing on the same machine, listening on this Ethernet port
can be disabled by setting the EnableListeningPort property in the TCP IP_PORT hierarchy of the
MBTCP Communication Driver rule file (DASMB TCP.aarul).

47
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideConfiguring the MBTCP Communication Driver

With unsolicited messaging enabled (the default), you can use the Device Groups dialog to configure
unsolicited messaging as a Device Group parameter for the PLC nodes directly connected to the
TCPIP _Port node.
For the step-by-step procedure to configure the Device Group to rec eive unsolicited messages, see
Device Group Definitions on page 41.

48
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

C HAPTER 3
MBTCP OI Reference

Data Types
The MB TCP Communication Driver supports the following generic data types:
 Boolean
 16-bit signed int eger
 16-bit unsigned integer
 32-bit signed int eger
 32-bit unsigned integer
 ASCII string
 32-bit single precision floating point
 64-bit floating point
 64-bit unsigned integer
 64-bit signed int eger

Support for 64-bit Data Types

The MB TCP Communication Driver supports the following 64 -bit dat a types:

Data Type Variant Type

64-bit floating point VT_R8

(double)
64-bit signed int eger VT_I8
(long long)
64-bit unsigned integer VT_UI8
(unsigned long long)

Clients advising data values from the MB TCP Communication Driver can subscribe to tags in these
64-bit data-types using specific item syntax. The MBTCP Communication Driver reads four cons ecutive
registers in the P LC to get a 64-bit value. Thes e registers are read in four register orders:
o Order 1: R1 R2 R3 R4 (Default)
o Order 2: R2 R1 R4 R3
o Order 3: R3 R4 R1 R2
o Order 4: R4 R3 R2 R1
where R1, R2, R3, R4 are the registers. You can select the order in which the registers are to be read.
Comparison examples of zero- and one-based addressing:

49
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide MBTCP OI Reference

Addre ssing Item Name Register Addre ss

0-Based 400000 00000

400001 00001

1-Based 400000 Invalid item

400001 00000

400002 00001

Data and Register Types

When a client sends a read/writ e request to the MB TCP Communication Driver, the Communication
Driver needs to know its data type and size. In order to determine this information, the MB TCP
Communication Driver parses the item name to get the register number, data type, and size. The
Communication Driver builds messages with items sorted by PLC, register type, register number, and
topic name, allowing the Communication Driver to optimize the number of registers that can be read in
one scan command.
The following table cont ains the types of data for the Modicon controllers, TS X Quantum, TS X
Moment um, TS X Premium, Generic Modbus (4-Digit, 5-Digit, and 6-Digit), Compact 984, and Modicon
Micro, supported by the MB TCP Communication Driver.

TSX Quantum/ TSX Momentum/

TSX Premium/ Generic Modbus/
Compact 984/ Modicon Micro Data Type Range

Discrete (bit/Boolean) 0 (zero), 1 (one)

Signed Short Integer -32768 to 32767

(signed 16-bit integer)
Unsigned Short Integer 0 (zero) to 65535
(unsigned 16-bit integer)
Signed Long Integer -2147483648 to
(signed 32-bit integer) 2147483647
Unsigned Long Integer 0 (zero) to
(unsigned 32-bit integer) 4294967295
REAL (32-bit float) 32-bit IEEE
LONG REAL (64 bit float ) 64-bit IEEE
Unsigned Long Long Integer 0 to
(unsigned 64-bit integer) 18,446,744,073,709,551,615

Signed Long Long Integer (signed 64-bit integer) -9,223,372,036,854,775,808 to

9,223, 372,036,854,775,807
String (ASCII) 246 characters (Read)
200 characters (Write)

50
MBTCP OI Reference AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

Note: The unsigned integer data type "U" has a valid range of 0 (zero) to 2147483647 when accessed
through DDE/SL client; for OP C clients the valid range is from 0 to 4294967295. System -defined types
are not supported as block reads. A read on any of these dat a types returns only the first element.

The following table lists the PLC register types, the data types contained in the registers, and what each
is processed as.

PLC Regi ster Type Data Type Contained in the Register Processed As

Discrete Out put (Coil) Discrete Real Time Data

Discrete Input Discrete Real Time Data
Holding Register Discrete, Int eger, Float, and String Real Time Data
Input Register Discrete, Int eger, Float, and String Real Time Data
Extended Register Discrete, Int eger, Float, and String Real Time Data

Modbus Item Naming

The Modbus -family controllers store data in the Registers. The MB TCP Communication Driver supports
item names that are consistent with the point naming conventions used by the Modicon PLCs.

The following item naming conventions are described in this section:

 Register-Number Item Names
 Item Names Using the Modicon PLC Register Addresses
 Item Names Using the Absolut e Naming Convention
 Item Names Using the Modulo-10000 Naming Convention
 Modulo-10000 Items, BCD Register Ty pe, and Concept Data Structures

Note: The tag-name length with SuiteLink is limited to 32 characters.

Register-Number Item Names

The register number, which is consistent with the point naming convention used by Modicon PLCs, is
used as the item name. The Modbus-family PLC address ranges, supported by the Communication
Driver, for the TS X Quantum, TS X Momentum, TS X Premium, Generic Modbus (4 -Digit, 5-Digit, and
6-Digit), Compact 984, and Modicon Micro PLCs are shown in the following tables.
The MB TCP Communication Driver will adhere to this address range for native mode.

Register TSX Quantum/ Modicon Compact Compact Tag

Type TSX Momentum Micro 984-265 984-145 Type Acce ss

Output 1-65536 1-9999 1-65536 1-9999 Discrete Read

Coils Write
Cont acts 100001-165536 10001-19999 100001-165536 10001-19999 Discrete Read-
Only

51
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide MBTCP OI Reference

Register TSX Quantum/ Modicon Compact Compact Tag

Type TSX Momentum Micro 984-265 984-145 Type Acce ss

Input 300001-365536 30001-39999 300001-365536 30001-39999 Analog Read-

Only
Holding 400001-465536 40001-49999 400001-465536 40001-49999 Analog Read
Write
Extended 6x0001-6x9998 6x000-6x999 Analog Read
Write

TSX Premium
(1-ba sed TSX Premium
Register addressing) (0-ba sed
Type [Default] addressing) Tag Type Acce ss

Output 1-65536 0-65535 Discrete Read/Write. Mapped to %M PLC object;

Coils that is, Output Coils and Contacts Registers
are the same.
Cont acts 100001-165536 100000-16553 Discrete Read-Only. Mapped to %I P LC object; that
5 is, Output Coils and Contacts Registers are
the same.

Input 300001-365536 300000-36553 Analog Read-Only. Mapped to %IW PLC object;

5 that is, Input Registers and Holding
Registers are the same.
Holding 400001-465536 400000-46553 Analog Read/Write. Mapped to %MW PLC object;
5 that is, Input Registers and Holding
Registers are the same.
Poking a value to a particular bit in the
Holding register in this TS X P remium PLC
is not support ed.

Register Generic Modbus Generic Modbus Generic Modbus

Type (6-Digit) (5-Digit) (4-Digit) Tag Type Acce ss

Output 1-65536 [Default] 1-9999 [Default] 1-999 [Default] Discrete Read

Coils with 1-based with 1-based with 1-based Write
addressing addressing addressing
0-65535 0-9998 0-998
if 0-based if 0-based addressing if 0-based addressing
addressing selected selected
selected

52
MBTCP OI Reference AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

Register Generic Modbus Generic Modbus Generic Modbus

Type (6-Digit) (5-Digit) (4-Digit) Tag Type Acce ss

Cont acts 100001-165536 10001-19999 1001-1999 [Default] Discrete Read-

[Default] [Default] with 1-based Only
with 1-based with 1-based addressing
addressing addressing
1000-1998
100000-165535 10000-19998 if 0-based addressing
if 0-based if 0-based addressing is selected
addressing is is selected
selected
Input 300001-365536 30001-39999 3001-3999 [Default] Analog Read-
[Default] [Default] with 1-based Only
with 1-based with 1-based addressing
addressing addressing
300000-365535 30000-39998 3000-3998
if 0-based if 0-based addressing if 0-based addressing
addressing is is selected is selected
selected
Holding 400001-465536 40001-49999 4001-4999 [Default] Analog Read
[Default] [Default] with 1-based Write
with 1-based with 1-based addressing
addressing addressing
4000-4998
400000-465535 40000-49998 if 0-based addressing
if 0-based if 0-based addressing is selected
addressing is is selected
selected
Extended 6x0001-6x9999 6x001-6x999 [Default] Not supported Analog Read
[Default] with 1-based Write
with 1-based addressing
addressing
0-based addressing is
0-based not supported for
addressing is not this Register Type.
supported for this
Register Type.

Note: The x in the Extended register number indicates the file number, where x = 0 implies file number 1,
x = 1 implies file number 2, up to x = 9 implies file number 10. The extended memory size in the PLC
determines how many extended memory files exist. Each file contains up to 10000 registers. The last file
in the PLC will always contain less than 10000 registers.

For example:
A 24K-extended-memory-size PLC contains three (3) files, where the last file cont ains 4576
registers.
A 72K-extended-memory-size PLC contains eight (8) files, where the last file contains 3728
registers.
A 96K-extended-memory-size PLC contains 10 files, where the last file contains 8304 registers.
1K is 1024 registers.

53
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide MBTCP OI Reference

Item Names Using the Modicon PLC Register Addresses

The following table lists other item name formats that are consistent with the point naming convention
with the MB TCP Communication Driver suffix.

Item Name Description

400001 When no spaces and no letters follow the register number, the register cont ents
are treated as a 16-bit unsigned quantity.
400001 S When a space and the letter "S" follow the register number, the register contents
are treated as a 16-bit signed quantity.
400001 I When a space and the letter "I" follow the register number, the register contents
are treated as a 32-bit signed quantity.
This takes up two consecutive registers.
400001 L When a space and the letter "L" follow the register number, the register contents
are treated as a 32-bit signed quantity.
This takes up two consecutive registers.
400001 F When a space and the letter "F" follow the register number, the register contents
are treated as a floating-point quantity.
This takes up two consecutive registers.
400001 U When a space and the letter "U" follow the register number, the register contents
are treated as a 32-bit unsigned quantity.
This takes up two consecutive registers.
400001 LF When a space and the letter "LF", follows the register number, the register
contents are treated as a 64-bit floating-point quantity. This takes up four
consecutive registers.
400001 LL When a space and the letter "LL", follows the register number, the register
contents are treated as a 64-bit signed quantity. This takes up four consecutive
registers.
400001 UL When a space and the letter "UL", follows the register number, the register
contents are treated as a 64-bit unsigned quantity. This takes up four consecutive
registers.
400001-400003 When a space and the letter "M" follow the register number or register number
M pair separated by a dash, the register contents are treated as ASCII data.
Each register contains up to two (2) ASCII characters.
This example represents six (6) ASCII characters.

300001:10 When a colon and a number from 1 (one) to 16 follow the register number, the
register contents are treated as discrete data.
This example represents bit 10 of the input register 300001.

Absolute Notation Item Names

The MB TCP Communication Driver also uses anoth er naming convention called the Absolute Notation.
This naming convention is independent of the PLC model numbers.
The Absolut e naming convention allows access to the four Modbus data types, each with an address
from 0 to 65535. The dat a types are indicated by the item name suffix characters.

54
MBTCP OI Reference AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

Item Name Description Range

nnnnn DO Discrete Out put 0 (zero) DO through 65535 DO

Refers to the same data Modbus calls "coils."

nnnnn DI Discrete Input 0 (zero) DI through 65535 DI

Refers to the same data called "contacts" by
Modbus.
nnnnn IR Input Register (zero) IR through 65535 IR
Refers to the same data called "input
register."
nnnnn HR Holding Register 0 (zero) HR through 65535 HR
Refers to the same data Modbus calls
"holding register."
nnnnn PV Process Variable 0 (zero) PV through 65535 PV
Refers to holding register, but treated as
floating points and assumes two (2) registers
per floating-point number.

The IR and HR absolute notation can also be combined with the following conversions: L (long), F
(floating), S (signed), or U (unsigned).
For example:
 219 HRS 16-bit signed int eger
 000 HRL 32-bit signed int eger
 100 HRF 32-bit floating point
 000 HRU 32-bit unsigned integer
 100 HRLF 64-bit floating point
 000 HRLL 64-bit signed int eger
 000 HRUL 64-bit unsigned integer

Modulo-10000 Point Item Names

The MB TCP OI Server uses the Modulo-10000 Points naming convention, where the item name is two
registers separated by a dash, with no spaces and no letters following the registers.
Two or three consecutive registers may be int erpreted as a single numeric quantity, and each of the
component registers must be in the range of 0 -9999.

Item Name Description

400001-400002 Can represent numbers between 0 and 99,999,999.

400005-400007 Can represent numbers between 0 and 2, 147, 483, 646.

55
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide MBTCP OI Reference

 When grouping three consecutive registers for interpretation as a single numeric quantity, overflow
becomes a possibility.
 The largest number that may be represent ed in the PLC with three consecutive Modulo -10000
registers is 999, 999, 999, 999; however, the largest number that can be contained in an integer -type
variable is 2,147,483,647. The latter number is used by the OI Server to represent an overflow
condition.
 Therefore, the maximum us able value represented in three Modulo -10000 registers is
2,147, 483,646 or (<21><4748><3646>). Any number larger than this will be clamped at
2,147, 483,647.

Modulo-10000 Items, BCD Register Type, and Concept Data Structures

All the integer holding registers, 16 - and 32-bit, signed and unsigned, and Modulo-10000 item types
honor the configuration paramet ers Register type and Concept data structures.
When the Register type parameter is BCD and the Use Concept data structures (Longs) parameter is
selected, the data is displayed in BCD and written to the PLC in the BCD format. In addition, data that
takes up two registers (Longs), except Reals, is displayed and written in the Concept-data-structure
format.
The same applies when the Register type paramet er is Binary and the Use Concept dat a structures
(Longs) parameter is selected; the data is displayed in Binary and written to the PLC in t he Binary format.
In addition, data that takes up two registers (Longs), except Reals, are displayed and written in the
Conc ept-data-structure format.
When the Register type parameter is BCD and t he Use Concept data structures (Longs) parameter is not
selected, the data is displayed in BCD and written to the PLC in the BCD format. In addition, data that
takes up two registers (Longs), except Reals, is displayed and written in the non-Conc ept-data-structure
format.
The same applies when the Register type paramet er is Binary and the Use Concept dat a structures
(Longs) parameter is not selected; the data is displayed in Binary and written to the PLC in the B inary
format. In addition, data that takes up two registers (Longs), except Reals, is displayed and written in the
non-Concept-data-structure format.
The Concept-data-structure format implies that data is displayed and written the same way that the
Conc ept program handles data.
Conc ept-data-structure format is where the data is displayed and written in the
last-register-to-first-register order.
For example:
When writing the value 2147483646 to the Modulo -10000 item 400001-400003, the value 21 is written
first to register 400003, then the value 4748 is written to register 400002, and then the value 3646 is
written to register 400001.
The non-Concept -data-structure format is the opposite of the Concept-data-structure format.
The value 21 is written first to register 400001, then the value 4748 is written to register 400002, and t hen
the value 3646 is written to register 400003.
Modulo-10000 items can be displayed and written in the BCD and Binary formats. When the
Modulo-10000 item occupies two registers, the maximum value that can be displayed and written is
99999999. When the Modulo-10000 item occupies three registers, the maximum value that can be
displayed and written is 2147483646.
Warning messages are logged and the client value status is updated when data is clamped high when
reading or writing data. Warning messages will also be displayed when t he PLC data does not convert to
BCD correctly.

56
MBTCP OI Reference AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

Zero- and One-Based Addressing

PLCs in whic h the address of the register is equivalent to the subsc ribed tag address are known as
zero-based PLCs (also written as "0-based"). In zero-based PLCs, the tag 400000 corresponds to the
holding register address 00000 in the PLC. In one-based PLCs, the tag 400001 corresponds to the
holding register address 00000 in the PLC. The TS X Premium model PLC is zero-based.
To support zero-based PLCs, the MBTCP OI Server has implement ed a configurable zero -bas ed and
one-based addressing scheme. The TS X P remium, Generic ModbusPLC, and the ModbusPLCRS PLC
hierarchies have the zero-based addressing option.
The default addressing scheme in the MB TCP OI Server is one-based.

Generic OPC Syntax

A OI Server serves as a container for the OPC Groups, which provide the mechanism for containing and
logically organizing OPC items. Within each OP C Group, an OPC-compliant client can register OP C
items, which represent connections to devices in the field device. In other words, all access to OP C items
is maintained through the OPC Group.
The fully qualified name for an OP C item is called the Item ID (equivalent to Item Name). The syntax for
specifying a unique Item ID is OI Server-dependent. In OPC data acquisition OI Servers, the syntax can
be as follows:
AREA10.VESSEL1.TIC1.PLC.400001
where each component (delimited by a period) repres ents a branch or leaf of the field device’s hierarchy.
In this example:
 AREA10.VESSEL1. TIC1 is the link name for a OI Server.
 PLC is the name of the target PLC.
 400001 is the specific data point (It em) desired.
 An item is typically a single value such as an analog, digital, or string value.
Where Item ID describes the syntax for defining the desired data point, OPC provides for another
parameter, called Access Path, that defines optional specifications for obtaining that data.
In OI Servers, Access Paths are equivalent to Device Groups; it is this parameter that is used to define
the update interval between the OI Server and the field devic e for accessing the values of data points in
the PLC.

Supported MBTCP OI Server Hardware and Firmware

The following table lists the Modbus hardware and firmware supported by the MBTCP OI Server.

Legend Model Description Firmware

TS X Quantum 140 CPU 21304 Cont roller Exec ID 0871 HID 0405 Rev
02.10

140 NOE 771 00 Ethernet TCP/IP Option

Module
140 NOE 21100 Ethernet TCP/IP Module

TS X Momentum Cont roller

57
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide MBTCP OI Reference

Legend Model Description Firmware

170 ENT 110 01 Ethernet TCP/IP Module

TS X Premium TS X P57 402 Cont roller

TS X P57 4823 Cont roller

TS X E TY 110 EtherNet TCP/IP Module

TS X Momentum Cont roller

(RS232)
171 CCC 980 20 Ethernet TCP/IP Module
and Modbus Ports

TS X Momentum Cont roller

(RS485)
171 CCC 980 20 Ethernet TCP/IP Module
and Modbus Ports
Compact 984 PC-A984-145 Cont roller Exec ID 084E Model A145
(RS232, 5-Digit
Addressing)
Compact 984 PC-E984-265 Cont roller
(RS232, 6-Digit
Addressing)
Modicon Micro 110 CPU 311 01 Cont roller Exec ID 0863 HID 0701 Rev
(RS232) 01.10 Model 311/ 01

Generic Modbus Generic Modbus The Generic Modbus

Cont roller Cont roller. Controller controller will be simulated
(4-Digit, 5-Digit, must conform to the with the Modbus Simulator
6-Digit) Modbus "Application version 1.05 developed by
Protocol specific ations." Wingpath Lt d.

NR& D Bridge Pen-T Ethernet-to-S erial Bridge

Modbus Bridge Power Logic EGX Bridge

100
TS X E TG 100

Controller Function Codes

The MB TCP Communication Driver uses function codes to communicat e with the various controllers
supporting the Modbus protocol. The implementation for the MB TCP Communication Driver uses the
document, " Open Modbus/TCP Specification," Release 1.1, dated December 6, 2002 as a referenc e.
These function codes and their descriptions are listed in the following table.

58
MBTCP OI Reference AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

Note: In communicating with the Generic Modbus PLCs, the MB TCP Communication Driver acts as a
master and sends out the function codes to the PLCs.

Code Name Description

01 (0x01) Read Coils Reads the ON/OFF status of discrete outputs (0X references, coils) in
the slave.
02 (0x02) Read Discret e Reads the ON/OFF status of discrete inputs (1XXXXX references) in
Inputs the slave.
03 (0x03) Read Holding Reads the binary contents of holding registers (4XXXXX referenc es)
Registers in the slave.

04 (0x04) Read Input Reads the binary contents of input registers (3XXXXX references ) in
Registers the slave.
05 (0x05) Write Single Forces a single coil (0X reference) to either ON or OFF.
Coil
06 (0x06) Write Single Presets a value into a single holding register (4XXXXX reference).
Register
15 (0x0F) Write Multiple Forces each coil (0XXXXX reference) in a sequence of coils to either
Coils ON or OFF.

16 (0x10) Write Multiple Presets values into a sequence of holding registers (4XXXXX
Registers references).

20 (0x14) Read General Returns the contents of registers in the Extended Memory file
Referenc e (6XXXXX) references.
21 (0x15) Write General Writes the contents of registers in the Extended Memory file
Referenc e (6XXXXX) references.
22 (0x16) Mask Write Modifies the contents of a specified (4XXXXX reference) holding
Holding register using a combination of an AND mask, an OR mask, and the
Register register’s current contents. The function can be used to set or clear
individual bits in the register.

Modbus Exception Codes

Additionally, there are exception codes generat ed by Modbus. The accompanying table shows thes e
exceptions and their explanations.

Exception
Code
(Hex) Name Explanation

01 ILLEGAL The function code received in the query is not an allowable action for the
FUNCTION slave. This may be bec ause the function code is only applicable to newer
controllers, and was not implement ed in the unit selected. It could als o
indicate that the slave is in the wrong state to process a request of this
type; for example, because it is unconfigured and is being asked to return
register values.

59
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide MBTCP OI Reference

Exception
Code
(Hex) Name Explanation

02 ILLEGAL DA TA The data address received in the query is not an allowable address for
ADDRESS the slave. More specifically, the combination of reference number and
transfer length is invalid. For a controller with 100 registers, a request
with offset 96 and lengt h 4 would succee d, a request with offset 96 and
length 5 will generate exception 02.
03 ILLEGAL DA TA A value contained in the query data field is not an allowable value for the
VALUE slave. This indicates a fault in the structure of the remainder of a complex
request, such as that the implied length is incorrect. It specifically does
NOT mean that a data item submitted for storage in a register has a
value outside the expectation of the application program, since the
MODB US protocol is unaware of the significance of any particular value
of any particular register.
04 ILLEGAL Indicates that the request as framed would generate a res ponse whose
RESPONSE size exceeds the available MODBUS data size. Used only by functions
LENGTH generating a multi-part response, such as functions 20 and 21.
05 ACKNOWLE DGE Specialized use in conjunction with programming commands.

06 SLAVE DEVICE Specialized use in conjunction with programming commands.

BUSY
07 NEGA TIVE Specialized use in conjunction with programming commands.
ACKNOWLE DGE
08 MEMORY Specialized use in conjunction with function codes 20 and 21 to indicate
PARITY ERROR that the extended file area failed to pass a consistency check.

0A GATEWAY PATH Specialized use in conjunction with gateways; it indicates that the
UNAVA ILABLE gateway was unable to allocate a Modbus Plus PATH to use to proc ess
the request. It usually means that the gateway is misconfigured.

0B GATEWAY Specialized use in conjunction with gateways; it indicates that no

TA RGE T response was obtained from the target device. It usually means that the
DEVICE FAILED devic e is not present on the network.
TO RESPOND

TCP Port
The MB TCP Communication Driver uses port 502 as the default to contact all PLCs. This includes the
port used for unsolicited messages from the PLCs that are programmed to provide unsolicited data (that
is, the PLCs that are directly connected to the TCPIP _PORT; controllers under the ModbusBridge Object
hierarchy cannot utilize this unsolicited messaging feature).
However, you have the option to configure the actual port to be used through the ModbusPLC object.
When a non-502 port is used by the Generic Modbus PLC to communicate with the MB TCP
Communication Driver, it will not be able to send unsolicited data to the Communication Driver.

60
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

C HAPTER 4
Troubleshooting the MBTCP
Communication Driver

Error Messages and Codes

Generic Communication Driver error messages and MB TCP -OI Server-specific messages are
supported. Use the Log Flag data to customize the messages logged to the Log Vie wer. See the Log
Viewer online documentation for more information about using log flags.
To troubleshoot Communication Driver problems, use the following error messages toget her with the OI
Server Manager Diagnostics root data.
In the following Communication Driver Error Messages table:
 <Message ID> corresponds to the message ID displayed in the Communication Driver’s Diagnostics
root in the OI Server Manager.
 <Devic e> refers to the node name of the device.

Communication Driver Error Messages

The following table lists all the generic-Communication Driver and MBTCP--specific error messages that
are logged to the Log Viewer.

Error Message Explanation Probable Cause Solution Log Flag

"CoilRead" is The mandat ory The entry is Use the OI DASProtFail

missing from the <CoilRead> field is deleted from the Server
DASMB TCP.AAcfg absent from the file manually. Manager to
file under <PLC DeviceNode named rebuild the file.
name>. <PLC Name> in the
configuration file.
"CoilWrite" is The mandat ory The entry is Use the OI DASProtFail
missing from the <CoilWrite> field is deleted from the Server
DASMB TCP.AAcfg absent from the file manually. Manager to
file under <PLC DeviceNode named rebuild the file.
name>. <PLC Name> in the
configuration file.
"ExtendedRegisterR The mandat ory The entry is Use the OI DASProtFail
ead" is missing from <ExtendedRegisterRe deleted from the Server
the ad> field is absent from file manually. Manager to
DASMB TCP.AAcfg the DeviceNode rebuild the file.
file under <PLC named <PLC Name>
name>. in the configuration file.

61
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideTroubleshooting the MBTCP Communication Driver

Error Message Explanation Probable Cause Solution Log Flag

"ExtendedRegisterW The mandat ory The entry is Use the OI DASProtFail

rite" is missing from <ExtendedRegisterWri deleted from the Server
the te> field is absent from file manually. Manager to
DASMB TCP.AAcfg the DeviceNode rebuild the file.
file under <PLC named <PLC Name>
name>. in the configuration file.
"HoldingRegisterRe The mandat ory The entry is Use the OI DASProtFail
ad" is missing from <HoldingRegisterRead deleted from the Server
the > field is absent from file manually. Manager to
DASMB TCP.AAcfg the DeviceNode rebuild the file.
file under <PLC named <PLC Name>
name>. in the configuration file.
"HoldingRegisterWrit The mandat ory The entry is Use the OI DASProtFail
e" is missing from <HoldingRegisterWrite deleted from the Server
the > field is absent from file manually. Manager to
DASMB TCP.AAcfg the DeviceNode rebuild the file.
file under <PLC named <PLC Name>
name>. in the configuration file.
"InputRegisterRead" The mandat ory The entry is Use the OI DASProtFail
is missing from the <InputRegisterRead> deleted from the Server
DASMB TCP.AAcfg field is absent from the file manually. Manager to
file under <PLC DeviceNode named rebuild the file.
name>. <PLC Name> in the
configuration file.
"IPAddress" is The mandat ory The entry is Use the OI DASProtFail
missing from the <IPAddress> field is deleted from the Server
DASMB TCP.AAcfg absent from the file manually. Manager to
file under <PLC DeviceNode named build the file.
name>. <PLC Name> in the
Configuration file.
"MaxAddrExtended The mandat ory The entry is Use the OI DASProtFail
Registers" is missing <MaxAddrExtendedRe deleted from the Server
from the gisters> field is absent file manually. Manager to
DASMB TCP.AAcfg from the DeviceNode rebuild the file.
file under <PLC named <PLC Name>
name>. in the configuration file.
"MaxAddrHoldingRe The mandat ory The entry is Use the OI DASProtFail
gisters" is missing <MaxAddrHoldingRegi deleted from the Server
from the sters> field is absent file manually. Manager to
DASMB TCP.AAcfg from the DeviceNode rebuild the file.
file under <PLC named <PLC Name>
name>. in the configuration file.
"MaxAddrInputRegis The mandat ory The entry is Use the OI DASProtFail
ters" is missing from <MaxAddrInputRegist deleted from the Server
the ers> field is absent file manually. Manager to
DASMB TCP.AAcfg from the DeviceNode rebuild the file.
file under <PLC named <PLC Name>
name>. in the configuration file.

62
Troubleshooting the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

Error Message Explanation Probable Cause Solution Log Flag

"MaxAddrReadCoils The mandat ory The entry is Use the OI DASProtFail

" is missing from the <MaxAddrReadCoils> deleted from the Server
DASMB TCP.AAcfg field is absent from the file manually. Manager to
file under <PLC DeviceNode named rebuild the file.
name>. <PLC Name> in the
configuration file.
"MaxAddrWriteCoils" The mandat ory The entry is Use the OI DASProtFail
is missing from the <MaxAddrWriteCoils> deleted from the Server
DASMB TCP.AAcfg field is absent from the file manually. Manager to
file under <PLC DeviceNode named rebuild the file.
name>. <PLC Name> in the
configuration file.
"MaxQueuedMsgs" The mandat ory The entry is Use the OI DASProtFail
is missing from the <MaxQueuedMsgs> deleted from the Server
DASMB TCP.AAcfg field is absent from the file manually. Manager to
file under <PLC DeviceNode named rebuild the file.
name>. <PLC Name> in the
configuration file.
"RegisterSize" is The mandat ory The entry is Use the OI DASProtFail
missing from the <RegisterSize> field is deleted from the Server
DASMB TCP.AAcfg absent from the file manually. Manager to
file under <PLC DeviceNode named rebuild the file.
name>. <PLC Name> in the
configuration file.
"RegisterTy pe" is The mandat ory The entry is Use the OI DASProtFail
missing from the <RegisterTy pe> field is deleted from the Server
DASMB TCP.AAcfg absent from the file manually. Manager to
file under <PLC DeviceNode named rebuild the file.
name>. <PLC Name> in the
configuration file.
"Reply Timeout" is The mandat ory The entry is Use the OI DASProtFail
missing from the <Reply Timeout> field deleted from the Server
DASMB TCP.AAcfg is absent from the file manually. Manager to
file under <PLC DeviceNode named build the file.
name>." <PLC Name> in the
Configuration file.
"StringVariableStyle" The mandat ory The entry is Use the OI DASProtFail
is missing from the <StringVariableStyle> deleted from the Server
DASMB TCP.AAcfg field is absent from the file manually. Manager to
file under <PLC DeviceNode named rebuild the file.
name>. <PLC Name> in the
configuration file.
"UnitID" is missing The mandat ory The entry is Use the OI DASProtFail
from the <UnitID> field is absent deleted from the Server
DASMB TCP.AAcfg from the DeviceNode file manually. Manager to
file under <PLC named <PLC Name> build the file.
name>. in the Configuration
file.

63
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideTroubleshooting the MBTCP Communication Driver

Error Message Explanation Probable Cause Solution Log Flag

"UseLongConceptD The mandat ory The entry is Use the OI DASProtFail

ataStruct" is missing <UseLongConcept Dat deleted from the Server
from the aStruct> field is absent file manually. Manager to
DASMB TCP.AAcfg from the DeviceNode rebuild the file.
file under <PLC named <PLC Name>
name>. in the configuration file.

"UseRealConceptDa The mandat ory The entry is Use the OI DASProtFail

taStruct" is missing <UseRealConc eptDat deleted from the Server
from the aStruct> field is absent file manually. Manager to
DASMB TCP.AAcfg from the DeviceNode rebuild the file.
file under <PLC named <PLC Name>
name>. in the configuration file.
<PLC Name> does The PLC does support The client defined Remove DASProtFail
not allow extended extended registers. an extended extended
register < Item register and it is register from
name>. not supported. client.
<PLC Name>: The client wrote a The client wrote The client must DASProtWar
Clamping a write to value that exceeded an invalid value. write a smaller n
<Item Name> - the item limits. value.
Received <client
value>, writing
<clamped value>.
An invalid floating Invalid floating-point The values read Check the PLC DASProtFail
point value was number (Negative from the PLC for the value in
returned by the PLC Infinity). Set the item registers cannot the registers.
for item name <PLC value to Negative be converted to a
Name>.<Item Infinity 3.4e+38. valid float
Name>. The value number.
was convert ed to a
negative 3.4e38.
An invalid floating Invalid floating-point The values read Check the PLC DASProtFail
point value was number (P ositive from the PLC for the value in
returned by the PLC Infinity). Set the item registers cannot the registers.
for item name <PLC value to Positive be converted to a
Name>.<Item Infinity 3.4e+38. valid float
Name>. The value number.
was convert ed to a
positive 3.4e38.
Connection to PLC The PLC closed the The PLC may be Check the PLC. DASProtFail
<PLC name> at IP connection. having problems.
Address <Host
name> closed, error
code = <Error code>.
CreateItem failed The server An invalid item Correct the item DASProtFail
<PLC name>.<Item encountered an invalid name was name defined
Name>. item name. defined by the by the client.
client.

64
Troubleshooting the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

Error Message Explanation Probable Cause Solution Log Flag

CreateItem failed The server The client defined The client must DASProtFail
due to invalid item encountered an invalid an invalid item define a valid
name <PLC item name. name. item name.
name>.<Item
Name>.
DASMB TCP failed to The server could not Too many items Stop unwant ed DASProtFail
allocate memory. allocate memory to have been programs,
continue operating. defined by client define less
or too many points by client,
programs are or add more
running in this memory to the
PC. PC.
DASMB TCPPLCSoc The PLC returned an The PLC may be Check the PLC. DASProtFail
ket::OnSocketRead( error code on a request having problems.
1) failed with for data.
errorcode <Error
code>.
DASMB TCPPLCSoc The PLC returned an The PLC may be Check the PLC. DASProtFail
ket::OnSocketRead( error code on a request having problems.
2) failed with for data.
errorcode <Error
code>.
DASMB TCPPLCSoc The PLC returned an The PLC may be Check the PLC. DASProtFail
ket::OnSocketRead( error code on a request having problems.
3) failed with for data.
errorcode <Error
code>.
DASMB TCPPLCSoc The PLC returned an The PLC may be Check the PLC. DASProtFail
ket::OnSocketWrite error code on a write to having problems.
failed with errorcode PLC command.
<Error code>.
Error in Reading The PLC returned an The PLC may be Check the PLC. DASProtFail
from PLC for item exception. having problems.
<PLC name>.<Item
Name>.
Error in Writing to The PLC returned an The PLC may be Check the PLC. DASProtFail
PLC for item <PLC exception. having problems.
name>.<Item
Name>.
Fail to Connect to The host name used in Invalid IP A valid host DASProtFail
PLC <PLC name> at the IP Address field is Address was name or IP
IP Address <Host invalid. configured. Address must
name>, error code = be configured.
<Error code>.
Failed to retrieve The host name used in Invalid IP A valid host DASProtFail
host information from the IP Address field is Address was name or IP
a host database. invalid. configured. Address must
Error code = <Error be configured.

65
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideTroubleshooting the MBTCP Communication Driver

Error Message Explanation Probable Cause Solution Log Flag

number>.

Failed to split the A message returned by The message Increase the DASProtFail
message from the PLC was not found may have timed Reply Timeout
ReceiveB uffer for in the requested out and was timer.
Sequence Number messages queue. removed from the
<Sequence queue.
Number>, message
possibly revoked.
Invalid value read for The Modulo-10000 The maximum Check the PLC DASProtWar
Mod 10000 register: point value overflows. usable value for the value in n
<Item Name> on The value is clamped represented in the registers.
Node: <PLC Name>. to 2147483647 to three
Not a valid indicate overflow Modulo-10000
BCD-value. condition. registers is
Convert to 2,147, 483,646.
2147483647.
Read value beyond The Modulo-10000 The maximum Check the PLC DASProtWar
limits for Mod 10000 point value overflows. usable value for the value in n
register: <It em The value is clamped represented in the registers.
Name> on Node: to 9999. one
<PLC Name>. Value Modulo-10000
clamped to 9999. registers is 9999.

rec v() failed with The PLC responded The PLC may be Check the PLC DASProtFail
errorcode <Error with an error. down or there is a and the
Code>. communications communication
problem. s link.

Register Type is The Modulo-10000 The The client must DASProtWar

’BCD’. Value point out put value Modulo-10000 write a smaller n
clamped to 9999. overflows. The value is value written to value.
clamped. the PLC
exceeded the
max limit.

Register Type is The Register Type The user modified The Register DASProtWar
hot-configured to parameter was the Register Type Type parameter n
<Register type>. modified at run time. parameter while can be modified
the server was at run time.
running.
Reply Timeout is The Reply Timeout The user modified The Reply DASProtWar
hot-configured to parameter was the Reply Timeout n
<Reply timeout modified at run time. Timeout parameter can
value>. parameter while be modified at
the server was run time.
running.

66
Troubleshooting the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

Error Message Explanation Probable Cause Solution Log Flag

String Variable Style The String Variable The user modified The String DASProtWar
is hot-configured to Style parameter was the String Variable Style n
<String variable modified at run time. Variable Style parameter can
style>. parameter while be modified at
the server was run time.
running.
The item name The item name is A non-numeric Make register a DASProtFail
<PLC Name>.<Item invalid. register was numeric
Name> is Invalid. It defined where register.
is non-numeric. numeric was
required.

The item name The item name has an The client defined The item bit DASProtFail
<PLC Name>.<Item invalid bit number. an item with an number must
Name> is invalid. invalid bit be bet ween 1
The bit number is number. (one) and 16.
invalid.
The item name The item name has an The client defined The item bit DASProtFail
<PLC Name>.<Item invalid bit number. an item with an number must
Name> is invalid. invalid bit be bet ween 1
The bit number is out number. (one) and 16.
of range.
The item name The server The client defined The client must DASProtFail
<PLC Name>.<Item encountered an invalid a data type not use a valid data
Name> is invalid. data type. supported by the type.
The data type is server.
invalid.
The item name The Modulo-10000 The client defined The client must DASProtFail
<PLC Name>.<Item item defined by the an invalid item use two or three
Name> is invalid. client exceeds the 3 name. registers when
The register range is register limit. defining
invalid. Modulo-10000
item names.
The item name The server trunc ated Not enough Add more DASProtFail
<PLC Name>.<Item the string being written registers were registers or
Name> written string to the PLC. defined by the write less data.
value <String Value> client to hold the
was trunc ated to string data being
<Truncated String written.
Value>. Not enough
registers were
defined to hold the
string value.

67
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideTroubleshooting the MBTCP Communication Driver

Error Message Explanation Probable Cause Solution Log Flag

The PLC <PLC The server did not get The PLC is offline Check PLC's DASProtFail
Name> message a response from the or the data network
timed out PLC in the request has an connection or
(OnP LCReceiverTim <Reply Timeout> invalid register configuration
eout), revoking allotted time. number obtained file.
message <Message from the
ID>. configuration file.

The PLC <PLC The function code This may be Check the item DASProtFail
name> reported received in the query is because the definition and
receiving an not an allowable action function code is PLC
ILLEGAL for the slave. only applicable to configuration.
FUNCTION code newer controllers,
from the OI Server. and was not
PLC errorcode 01. implemented in
the unit selected.
It could also
indicate that the
slave is in the
wrong state to
process a request
of this type; for
example,
because it is
unconfigured and
is being asked to
return register
values.
The PLC <PLC The data address The item address Check the item DASProtFail
name> reported received in the query is is out of the definition and
receiving an not an allowable configured-slave PLC
ILLEGAL DA TA address for the slave. address range, or configuration.
ADDRESS from the the combination
OI Server. PLC of reference
errorcode 02. number and
transfer length is
invalid. For a
controller with
100 registers, a
request with
offset 96 and
length 4 would
succeed, a
request with
offset 96 and
length 5 will
generate
exception 02.
The PLC <PLC A value contained in This indicates a Check the data DASProtFail
name> reported the query data field is fault in the value sent to
receiving an not an allowable value structure of the the PLC.
ILLEGAL DA TA for the slave. remainder of a

68
Troubleshooting the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

Error Message Explanation Probable Cause Solution Log Flag

VALUE from the OI complex request.
Server. PLC For example, the
errorcode 03. implied length is
incorrect.

The PLC <PLC An unrecoverable error Indicates that the Check the PLC. DASProtFail
name> reported occurred while the request as
ILLEGAL slave was attempting framed would
RESPONSE to perform the generate a
LENGTH while requested action. response whose
working on the size exceeds the
current request. PLC available
errorcode 04. MODB US data
size.
The PLC <PLC The slave has This response is Check the PLC. DASProtFail
name> reported accepted the request returned to
ACKNOWLE DGE and is processing it, prevent a timeout
while working on the but a long duration of error from
current request. PLC time will be required to occurring in the
errorcode 05. do so. client (or master).

The PLC <PLC The slave is engaged The PLC program Check the PLC. DASProtFail
name> reported in processing a is taking too long
SLAVE DEVICE long-duration program to respond to the
BUSY and cannot command. OI Server.
process the current
request. PLC
errorcode 06.

The PLC <PLC The slave cannot The Check the PLC. DASProtFail
name> reported perform the program communications
NEGA TIVE function received in the data is corrupted
ACKNOWLE DGE query. or a OI Server
and cannot process problem is
the current request. encountered.
PLC errorcode 07.
The PLC <PLC The slave attempted to The PLC may Check the DASProtFail
name> reported read extended need to be PLC's extended
MEMORY PARITY memory, but detected serviced. memory.
ERROR while a parity error in the
attempting to read memory.
extended memory.
PLC errorcode 08.
The PLC <PLC Specialized use in It usually means Check the DASProtFail
name> reported conjunction with that the gateway Bridge
GATEWAY PATH gateways; it indicates is misconfigured. connected to
UNAVA ILABLE that the gateway was the PLC.
while attempting to unable to allocat e a
read extended Modbus Plus PATH to
memory. PLC use to process the

69
AVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User GuideTroubleshooting the MBTCP Communication Driver

Error Message Explanation Probable Cause Solution Log Flag

errorcode 0A. request.

The PLC <PLC Specialized use in It usually means Check the DASProtFail
name> reported conjunction with that the device is Bridge
GATEWAY TARGE T gateways; it indicates not present on the connected to
DEVICE FAILED TO that no response was network. the PLC.
RESPOND while obtained from the
attempting to read target device.
extended memory.
PLC errorcode 0B.
The PLC <PLC The PLC returned an The Check the PLC. DASProtFail
name> reported unknown error code. communications
unknown exception data is corrupted.
code. PLC errorcode
<Error Number>.
The property The RegisterSize The entry in the Use the OI DASProtFail
RegisterSize value value in the file was modified Server
<Value> is invalid for configuration file is manually. Manager to
PLC <PLC Name>. invalid. rebuild the file.
The register number The register defined by The client defined Client must use DASProtFail
for the item name the client is out of an invalid register a register
<PLC name>.<Item range compared to the number. number less
Name> exceeds the maximum addressable than or equal to
configured PLC register number. the configured
Maximum maximum
Addressable addressable
Registers. register.
The socket is The connection to the The PLC or the Check the PLC DASProtFail
marked as PLC failed. network may be or the network.
nonblocking and the having problems.
connection cannot
be completed
immediat ely for host
<Host name>.
The write Item <Item The register being The client is Select a DASProtFail
Name> is invalid. written t o is a read-only writing to a different
The item is a read register. read-only register.
only item. register.
Write attempt The output value was The client wrote a The client must DASProtFail
beyond limits for clamped to a value to the PLC write a smaller
Mod 10000 register: predefined value that was too large value.
<Item Name> on because the output for the register.
Node: <PLC Name>. value exceeded certain
Value clamped to limits.
<new value>.

70
Troubleshooting the MBTCP Communication DriverAVEVA™ Communication Drivers Pack – Modicon - MBTCP Driver User Guide

Server-Specific Error Codes

There are two server-specific error codes, shown in the following table, that augment those provided by
the Toolkit.

Error Code Logger Message Log Flag

-10001 PLC not connected DASProtFail

-10002 PLC timeout DASProtFail

Network Admin Final Exam
94% (16)
Network Admin Final Exam
2 pages
Sequence Control - LC64
100% (2)
Sequence Control - LC64
34 pages
Sequence Control - LC64
100% (2)
Sequence Control - LC64
34 pages
CH 11 Organization
100% (1)
CH 11 Organization
1 page
Elster Instromet Q.sonic
No ratings yet
Elster Instromet Q.sonic
2 pages
DS - EnCal - 3000 - EN - 2012.04.30
No ratings yet
DS - EnCal - 3000 - EN - 2012.04.30
4 pages
IoT Wireless IO Solution
No ratings yet
IoT Wireless IO Solution
16 pages
Configure DHCP and DNS Using Packet Tracer: Practical No.7
No ratings yet
Configure DHCP and DNS Using Packet Tracer: Practical No.7
9 pages
IECEP Cagayan Valley - Structured Cabling
No ratings yet
IECEP Cagayan Valley - Structured Cabling
46 pages
NSE5 - FMG-7.0 whatsAPP 0021655255099
No ratings yet
NSE5 - FMG-7.0 whatsAPP 0021655255099
37 pages
Controller - PM866
No ratings yet
Controller - PM866
4 pages
Installation Guide
No ratings yet
Installation Guide
159 pages
GD32F103C8T6 CoreBoard (New Version)
No ratings yet
GD32F103C8T6 CoreBoard (New Version)
1 page
SG900 Specific Gravity
100% (1)
SG900 Specific Gravity
2 pages
Cooperative's Equipment Transition
No ratings yet
Cooperative's Equipment Transition
1 page
570 Data Sheet
No ratings yet
570 Data Sheet
2 pages
ID900 Density Meter
No ratings yet
ID900 Density Meter
2 pages
ID900 Density Meter
No ratings yet
ID900 Density Meter
2 pages
FD960 Density Meter
No ratings yet
FD960 Density Meter
2 pages
Newcamd
No ratings yet
Newcamd
5 pages
Elster-Instromet Encal3000 GC
No ratings yet
Elster-Instromet Encal3000 GC
0 pages
ISM - Guidelines For Email (December 2023)
No ratings yet
ISM - Guidelines For Email (December 2023)
5 pages
Unit-Iii-C N-R18
No ratings yet
Unit-Iii-C N-R18
38 pages
Elster-Instromet M2000 FC
No ratings yet
Elster-Instromet M2000 FC
0 pages
Config Et Use Rslogix500
No ratings yet
Config Et Use Rslogix500
76 pages
Cable Catalogue and Specifications
100% (1)
Cable Catalogue and Specifications
88 pages
Modicon Communication Server User Guide
No ratings yet
Modicon Communication Server User Guide
86 pages
Bangalore Institute of Technology K. R. Road, V. V. Pura, Bangalore - 560004
No ratings yet
Bangalore Institute of Technology K. R. Road, V. V. Pura, Bangalore - 560004
16 pages
TM-2222 AVEVA Marine (12.1) Cable Tray Modelling Rev 4.0
No ratings yet
TM-2222 AVEVA Marine (12.1) Cable Tray Modelling Rev 4.0
112 pages
Atoll
No ratings yet
Atoll
168 pages
Instrument Optic
No ratings yet
Instrument Optic
19 pages
General Configuration For Liquid Flow Calculation
No ratings yet
General Configuration For Liquid Flow Calculation
3 pages
Ca'e 'Ate' L ! I I: Ilv I LL - Uge
No ratings yet
Ca'e 'Ate' L ! I I: Ilv I LL - Uge
5 pages
Aveva™ Plant Scada What's New in Plant Scada 2025-07-01-16-07-33
No ratings yet
Aveva™ Plant Scada What's New in Plant Scada 2025-07-01-16-07-33
121 pages
BioEngineering - Comp
No ratings yet
BioEngineering - Comp
2 pages
PLC - Schneider Electric - Quantum TCP-IP Ethernet Module User Guide V4.0
No ratings yet
PLC - Schneider Electric - Quantum TCP-IP Ethernet Module User Guide V4.0
146 pages
OISIDIR
No ratings yet
OISIDIR
139 pages
Modbus TCP UserGuide
No ratings yet
Modbus TCP UserGuide
132 pages
QMS250 I
100% (1)
QMS250 I
2 pages
OIABCIP
No ratings yet
OIABCIP
117 pages
Network+ Guide To Networks 5 Edition
No ratings yet
Network+ Guide To Networks 5 Edition
87 pages
Nve24232 06
No ratings yet
Nve24232 06
412 pages
Eio0000001584 10
No ratings yet
Eio0000001584 10
158 pages
CCNA Exploration 1 - Network Fundamentals - Final Exam - Cisco CCNA Exploration 4.0 Questions - Answers Test Blog
No ratings yet
CCNA Exploration 1 - Network Fundamentals - Final Exam - Cisco CCNA Exploration 4.0 Questions - Answers Test Blog
15 pages
ASBCE Appnotes SIPTrunking AsteriskServer ASBCE SIPTrunk 1.1
No ratings yet
ASBCE Appnotes SIPTrunking AsteriskServer ASBCE SIPTrunk 1.1
47 pages
Compal Electronics Schematics
No ratings yet
Compal Electronics Schematics
39 pages
OIABCIP OIServer Userguide
No ratings yet
OIABCIP OIServer Userguide
117 pages
Ahmad MSC Thesis
No ratings yet
Ahmad MSC Thesis
116 pages
ABB FENA 01 11 Ethernet Manual
100% (1)
ABB FENA 01 11 Ethernet Manual
358 pages
MCode V2.06 NOVA
No ratings yet
MCode V2.06 NOVA
190 pages
ETSI TS 102 226: Smart Cards Remote APDU Structure For UICC Based Applications (Release 11)
No ratings yet
ETSI TS 102 226: Smart Cards Remote APDU Structure For UICC Based Applications (Release 11)
45 pages
ClearSCADA Getting Started
No ratings yet
ClearSCADA Getting Started
25 pages
Semindia Adsl 2+ Modem/Router
No ratings yet
Semindia Adsl 2+ Modem/Router
51 pages
Comparative Analysis of Performance of Hub With Switch Local Area Network (LAN) Using Riverbed in University of Technology (Utech), Jamaica
No ratings yet
Comparative Analysis of Performance of Hub With Switch Local Area Network (LAN) Using Riverbed in University of Technology (Utech), Jamaica
23 pages
Getting Started
No ratings yet
Getting Started
98 pages
Virus Detection Project Synopsis
No ratings yet
Virus Detection Project Synopsis
5 pages
OIABTCP OIABCIP OIServer Userguide
No ratings yet
OIABTCP OIABCIP OIServer Userguide
60 pages
Emacs Dired Quick Reference
No ratings yet
Emacs Dired Quick Reference
1 page
Network Trunking and GoS Analysis
No ratings yet
Network Trunking and GoS Analysis
6 pages
Modicon M340 For Ethernet: Communications Modules and Processors User Manual
No ratings yet
Modicon M340 For Ethernet: Communications Modules and Processors User Manual
398 pages
GS 25
No ratings yet
GS 25
4 pages
OITWINCAT
No ratings yet
OITWINCAT
20 pages
TM-1204 AVEVA Plant (12.1) Cable Catalogue and Specifications Rev 2.0
No ratings yet
TM-1204 AVEVA Plant (12.1) Cable Catalogue and Specifications Rev 2.0
88 pages
T2000 Firmware Upgrade
No ratings yet
T2000 Firmware Upgrade
2 pages
Amit Jain
No ratings yet
Amit Jain
2 pages
Desktop Support Engineer Resume
No ratings yet
Desktop Support Engineer Resume
2 pages
REX610 Modbusprot 2NGA000822 ENa
No ratings yet
REX610 Modbusprot 2NGA000822 ENa
84 pages
MBX Install Note
No ratings yet
MBX Install Note
29 pages
Tee054673 Notice 5
No ratings yet
Tee054673 Notice 5
124 pages
Security Hardening Guide
No ratings yet
Security Hardening Guide
64 pages
ATV71 - EtherCAT通讯手册（英文） (1.0)
No ratings yet
ATV71 - EtherCAT通讯手册（英文） (1.0)
60 pages
IOSrv MBENET
No ratings yet
IOSrv MBENET
42 pages
Oasys SCADA HMI Supported Configurations Guide
No ratings yet
Oasys SCADA HMI Supported Configurations Guide
12 pages
3BUR002417-600 B en 800xa For MOD 300 6.0 Configuration PDF
No ratings yet
3BUR002417-600 B en 800xa For MOD 300 6.0 Configuration PDF
172 pages
Modbus Driver Guide: M Mo Od DB Bu Uss D Drriiv Ve Err G Gu Uiid de e
No ratings yet
Modbus Driver Guide: M Mo Od DB Bu Uss D Drriiv Ve Err G Gu Uiid de e
102 pages
Motcp
No ratings yet
Motcp
37 pages
Manual Modbus para Atv32 Variador de Frecuencia
No ratings yet
Manual Modbus para Atv32 Variador de Frecuencia
65 pages
ABB ACS850 ACSM1 FENA 01 Ethernet Manual
No ratings yet
ABB ACS850 ACSM1 FENA 01 Ethernet Manual
52 pages
Mbenet
No ratings yet
Mbenet
42 pages
BMENOC301 User Manual
No ratings yet
BMENOC301 User Manual
364 pages
MBXsuite
No ratings yet
MBXsuite
29 pages
Modicon M340 For Ethernet: Communications Modules and Processors User Manual
No ratings yet
Modicon M340 For Ethernet: Communications Modules and Processors User Manual
396 pages
FENA-01 - 11 - 21 - Ethernet Adapter - User's Manual - Rev B
No ratings yet
FENA-01 - 11 - 21 - Ethernet Adapter - User's Manual - Rev B
388 pages
Firmware Compatibility Rules: Modicon M580, Modicon Momentum, Modicon MC80, and Modicon X80 I/O Modules
No ratings yet
Firmware Compatibility Rules: Modicon M580, Modicon Momentum, Modicon MC80, and Modicon X80 I/O Modules
13 pages
ABB FENA 01 11 Ethernet Manual
No ratings yet
ABB FENA 01 11 Ethernet Manual
358 pages
ATV32 DeviceNet Manual
No ratings yet
ATV32 DeviceNet Manual
88 pages
Mvi69E-Mbtcp: User Manual
No ratings yet
Mvi69E-Mbtcp: User Manual
150 pages
ATV32 Modbus Manual S1A28698 02
No ratings yet
ATV32 Modbus Manual S1A28698 02
65 pages
Schneider Communication Drivers 2016
No ratings yet
Schneider Communication Drivers 2016
126 pages
Protocol
No ratings yet
Protocol
10 pages
Datasheet AVEVA CommunicationDrivers 23-11.pdf - Coredownload.inline
No ratings yet
Datasheet AVEVA CommunicationDrivers 23-11.pdf - Coredownload.inline
3 pages
Eng Setup DRV
No ratings yet
Eng Setup DRV
132 pages
IOSrv MBENET
No ratings yet
IOSrv MBENET
42 pages
Advantech Webaccess Device Driver Guide Wago 750 Ethernet Tcp/Ip Modbus
No ratings yet
Advantech Webaccess Device Driver Guide Wago 750 Ethernet Tcp/Ip Modbus
46 pages
Motcp
No ratings yet
Motcp
26 pages
Dasmbtcp 3.0 PDF
No ratings yet
Dasmbtcp 3.0 PDF
130 pages
Driver
No ratings yet
Driver
53 pages
AVEVA Message Bus Install Guide21
No ratings yet
AVEVA Message Bus Install Guide21
47 pages
ATV32 Modbus TCP EtherNet IP Manual S1A28701 02
No ratings yet
ATV32 Modbus TCP EtherNet IP Manual S1A28701 02
146 pages
Advantis
No ratings yet
Advantis
126 pages
Brocade XMRMLX 05200 Diagnostic Guide
No ratings yet
Brocade XMRMLX 05200 Diagnostic Guide
368 pages
Mod Bus Ascii
No ratings yet
Mod Bus Ascii
16 pages