Remote Automation Solutions Bristol ACCOL II Custom Protocols Owner's manual

www.EmersonProcess.com/Bristol

Reference Manual

D4066

May 2006

ACCOL II Software

ACCOL II Custom Protocols Manual

For use with DPC 3330, DPC 3335, RTU 3305, RTU 3310, and

3530-xx series units

BLANK PAGE

SECTION 2 – ODD HEADER

5/2006

i

Getting Additional Information

In addition to the information contained in this manual, you may receive additional assistance in

using this product from the following sources:

Help Files / Release Notes

Many Bristol software products incorporate help screens. In addition, the software typically

includes a ‘read me’ release notes file detailing new features in the product, as well as other

information which was available too late for inclusion in the manual.

Contacting Bristol Directly

The address for our world headquarters is:

Bristol, Inc.

a division of Emerson Process Management

1100 Buckingham Street

Watertown, Connecticut 06795 USA

Our main phone numbers are:

(860) 945-2200

(860) 945-2213 (FAX)

Regular office hours are Monday through Friday, 8:00AM to 4:30PM Eastern Time, excluding

holidays, and scheduled factory shutdowns. During other hours, callers may leave messages

using Bristol's voice mail system.

Telephone / E-Mail Support - Technical Questions

During regular business hours, Bristol's Application Support Group can provide telephone/e-mail

support for your technical questions.

SECTION 2 – EVEN HEADER

5/2006

ii

Please refer to the table, below, for a list of products, and their associated technical support

contact information:

Product Support Phone

Number(s):

E-Mail Address:

ControlWave series (hardware and

software)

(860) 945-2394

(860) 945-2286

[email protected]

Network 3000 hardware except for

TeleFlow series

(860) 945-2502 [email protected]

TeleFlow series (3530-xx)

(860) 945-8604. [email protected]

ACCOL, Open BSI, UOI, all other

software except for ControlWave and

OE.

(860) 945-2286 [email protected]

OpenEnterprise (OE) software

(860) 945-3865 [email protected]

Radio telemetry services (interfacing

Bristol hardware to radios)

(407) 629-9463

(407) 629-9464.

[email protected]

Non-Technical Questions, Product Orders, etc.

Questions of a non-technical nature (product orders, literature requests, price and delivery

information, etc.) should be directed to the nearest Bristol sales office or to your Bristol-

authorized sales representative. Please call the main Bristol number (860-945-2200) or visit our

web site, listed below, if you are unsure which office covers your particular area.

Visit our Site on the World Wide Web

For general information about Bristol, Inc. and its products, please visit our site on the World

Wide Web at: www.EmersonProcess.com/Bristol

Training Courses

Bristol's Training Department offers a wide variety of courses in Bristol hardware and software

at our Watertown, Connecticut headquarters, and at selected Bristol regional offices, throughout

the year. Contact our Training Department at (860) 945-2343 for course information, enrollment,

pricing, and schedules.

Who Should Read This Manual?

This manual is intended to be used by a System Engineer, or other

individual, who will be configuring a Bristol Network 3000-series controller

to communicate with a foreign device or network.

It assumes familiarity with the following subjects:

• Use of personal computers.

• Configuration and use of the foreign device or network.

• Use of ACCOL software tools, and ACCOL structures such as signals,

signal lists, and data arrays.

• Configuration of Bristol communication ports. This subject is discussed

in the ACCOL II Reference Manual (document# D4044).•

• Local addressing of Bristol Network 3000 hardware devices. See the

manuals accompanying the Bristol hardware devices.

• Installation of protocols. The method for installing custom protocol

system firmware varies depending upon the type of controller you

have. For 186-based units other than the RTU 3305, custom firmware

is installed by inserting the proper custom EPROM in a socket. For

386-based units, as well as the RTU 3305, custom system firmware is

downloaded into the unit using the FLASH program. See the

FLASH.TXT file on the flash diskette for details on this procedure.

BLANK

v

Table of Contents

Introduction .............................................. Introduction-1

Allen-Bradley PLC2/5 Master Interface ................Allen-Bradley Master-1

Allen-Bradley PLC2 Slave Interface ...............Allen-Bradley PLC2 Slave-1

CNGMaster ............................... Columbia Natural Gas Master-1

CNGSlave ..................................Columbia Natural Gas Slave-1

Enron Modbus / Open Modbus Interface ............................ Enron-1

Gould Modbus / Open Modbus Interface .............................Gould-1

Hewlett Packard HP48000 Interface ........................HP48000 Slave-1

Netprobe ................................................... Netprobe-1

TANO Slave Interface (CIM) ................................ TANO Slave-1

Teledyne Geotech Slave Interface ............................... Teledyne-1

BLANK PAGE

ACCOL II Custom Protocols Manual

Page Introduction-1

Introduction

Introduction to Network 3000 Custom Protocols

Bristol's Network 3000-series of remote process controllers supports

several custom communication protocols. These protocols allow the

Network 3000 controller to communicate with foreign devices and

networks, by translating ACCOL signal, array, and/or audit trail data,

into a format which may be understood by the foreign device or net-

work.





Installation of Protocols

The method for installing custom protocol system firmware varies

depending upon the type of controller you have. For 186-based units

other than the RTU 3305, custom firmware is installed by inserting

the proper custom EPROM in a socket. For 386-based units, as well as

the RTU 3305, custom system firmware is downloaded into the unit

using the FLASH program and FLASH cable. See the FLASH.TXT file

on the FLASH diskette for details of this procedure.





ACCOL Configuration

The level of ACCOL configuration varies depending upon which

protocol is chosen. Most (though not all) protocols require that the

ACCOL load include the Custom Module, and a Custom Port.

Details on configuring the Custom Module and communication port for

a particular protocol are included in the descriptions of each protocol

either in this manual, or in special documentation provided by the

Bristol Application Support Group. General information about Custom

Modules and Custom Ports is included in the 'Custom Module' and

'Communication Ports' sections of the ACCOL II Reference Manual

(document# D4044). Additional ACCOL structures such as data

arrays, signal lists, and formats may need to be configured, as well.

These are also discussed in the ACCOL II Reference Manual, (docu-

ment# D4044).

Certain protocols require dedicated ACCOL Modules and communica-

ACCOL II Custom Protocols Manual

Page Introduction-2

Introduction

Introduction to Network 3000 Custom Protocols

tion ports instead of the 'Custom Module' and 'Custom Port'. These

are:

Protocol Module Port

Columbia Natual Gas Master CNGMaster Columbia Natural Gas Master

Columbia Natural Gas Slave CNGSlave Columbia Natural Gas Slave

TANO Slave Protocol CIM Optional Comm



 List of Available Protocols

Protocol Name Where can I get information on this protocol?

ADEPT Contact Bristol Application Support for info.

Allen-Bradley PLC-2 Slave See section in this manual (D4066).

Allen-Bradley PLC-2 Master See section in this manual (D4066).

Allen-Bradley PLC-5 Master See section in this manual (D4066).

BRITE Slave Contact Bristol Application Support for info.

Brooklyn Union Protocol Set Contact Bristol Application Support for info.

****Columbia Natural Gas MasterSee section in this manual (D4066).

****Columbia Natural Gas Slave See section in this manual (D4066).

El Paso Natural Gas Master See El Paso Natural Gas Protocols Manual (D4086).

El Paso Natural Gas Slave See El Paso Natural Gas Protocols Manual (D4086).

ENRAF 854 (Tank Gauge) Master See Application notes on User Documentation CD.

Enron Modbus Slave See section in this manual (D4066).

Gould Modbus Master See section in this manual (D4066).

Gould Modbus Slave See section in this manual (D4066).

HART Master See HART Master Protocol Manual (D4068).

**

Hewlett-Packard HP48000 Slave See section in this manual (D4066).

MTS DDA Gauge Master See Application notes on User Documentation CD.

***NETPROBE See section in this manual (D4066).

Pignone P6008 See Application notes on User Documentation CD.

QSonic SPU See Application notes on User Documentation CD.

RTU 500/700 Master See Application notes on User Documentation CD.

RTU 700 Slave See Application notes on User Documentation CD.

**RTU 3301 Master See manual 3301 Cust. Module Inter. (CI-3301-5).

Series V Valmet Master Contact Bristol Application Support for info.

Series V Valmet Slave Contact Bristol Application Support for info.

*TANO Slave See section in this manual (D4066).

Teledyne Geotech Slave See section in this manual (D4066).

NOTES:

*TANO Slave Protocol is NOT available for the 386EX Protected Mode platform, or the

GFC 3308-xx controllers.

**The HP48000 and RTU 3301 protocols are NOT available for the GFC 3308-xx.

***NETPROBE was only available for AE thru AJ firmware for the 3310/3330/3335.

****Columbia Natural Gas protocols are NOT available for 386EX Protected Mode

controllers prior to PCP03.

ACCOL II Custom Protocols Manual

Page Introduction-3

Introduction

Introduction to Network 3000 Custom Protocols

There may be other restrictions for specific protocols. SOME PROTO-

COLS ARE NOT AVAILABLE FOR CERTAIN TARGET NODE

TYPES. Contact Bristol Application Support for details.

IMPORTANT

This manual assumes the user is familiar with the

configuration details of the foreign device with

which the Network 3000 controller will communi-

cate. This manual discusses Network 3000 configu-

ration ONLY; not the characteristics of the foreign

device or network.





Standard Protocol Suite For Real

Mode Users ONLY (STP.xx)

Beginnning with ACCOL Version AH.00 firmware, a standard protocol

suite is available for 186 and 386EX Real Mode units. The protocols in

this suite are:

z Allen-Bradley PLC 2 Master Interface

z Allen-Bradley PLC 2 Slave Interface

z Allen-Bradley PLC 5 Master Interface

z Enron Modbus Slave Interface

z Gould Modbus Master and Slave Interface

z Hart Master Interface

z Hewlett-Packard HP48000 Slave Interface

z RTU 3301 Master Interface

z Teledyne Geotech Slave Interface

These protocols are combined into a single standard protocol file on the

FLASH diskette called STPxx.BIN where xx is the current version

number. If your controller does NOT support FLASH this protocol suite

is available as a single EPROM.

ACCOL II Custom Protocols Manual

Page Introduction-4

Introduction

Introduction to Network 3000 Custom Protocols





Special Protocol Sets For Real

Mode Users ONLY

If the standard STP suite is NOT installed, there are several other

sets of special protocols available. Any single set may be used instead

of (but not in addition to) the standard STP suite. These special

protocol sets typically include individual elements from the STP.xx

suite, such as Modbus protocols, as well as one or more additional

protocols, requested by specific customers.

If your controller does NOT support FLASH, these special protocol sets

are available only by special order.The desired protocol should be

requested when the Network 3000-series controller is ordered from

Bristol; this allows the special EPROM to be factory-installed.

A list of the major special protocol sets (and the contents of each set)

appears below:

Series V - Valmet Set (SVMBxx):

Series V Valmet Master Gould Modbus Slave Enron Modbus Slave

Series V Valmet Slave Gould Modbus Master

Tano Set (TMBxx):

TANO Slave Gould Modbus Slave Enron Modbus Slave

Gould Modbus Master

RTU 500/700 Set (AIMMxx):

RTU 500/700 Master Gould Modbus Slave Enron Modbus Slave

Gould Modbus Master

Las Vegas Valley Water Set (LVWxx):

BRITE Slave Enron Modbus Slave

Allen-Bradley PLC-2 Master Gould Modbus Slave

Allen-Bradley PLC-5 Master Gould Modbus Master

Allen-Bradley PLC-2 Slave RTU 3301 Master

Columbia Natural Gas Set (CMBxx):

Columbia Natural Gas Master Enron Modbus Slave

Columbia Natural Gas Slave Gould Modbus Slave

Gould Modbus Master

ACCOL II Custom Protocols Manual

Page Introduction-5

Introduction

Introduction to Network 3000 Custom Protocols

ENRAF 854 Set (ERMBxx):

ENRAF 854 (Tank Gauge) Master Enron Modbus Slave

Gould Modbus Master Gould Modbus Slave

MTS DDA Set (MTSMxx):

MTS DDA Gauge Master Enron Modbus Slave

Gould Modbus Master Gould Modbus Slave

El Paso Natural Gas Set (EPMBxx):

El Paso Natural Gas Master Enron Modbus Slave

El Paso Natural Gas Slave Gould Modbus Slave

Gould Modbus Master



 Protocol Suite For Protected Mode

Users ONLY

(PCP.xx)

Protected Mode users have a single standard protocol suite. The

Protected Mode protocol suite is named (PCP.xx) where xx is the

version number, and consists of the following protocols:

z Allen-Bradley PLC 2 Master Interface

z Allen-Bradley PLC 2 Slave Interface

z Allen-Bradley PLC 5 Master Interface

z BRITE Slave (Las Vegas Valley Water)

z Brooklyn Union Protocol Set

z ENRAF 854 (Tank Gauge) Master

z Enron Modbus Slave Interface

z Gould Modbus Master and Slave Interface

z Hart Master

z Hewlett-Packard HP48000 Slave Interface

z MTS DDA Gauge Master

z Pignone P6008

z QSonic SPU

z RTU 3301 Master Interface

z Teledyne Geotech Slave Interface

There are no alternate special protocol sets for Protected Mode users.

ACCOL II Custom Protocols Manual

Page Introduction-6

Introduction

Introduction to Network 3000 Custom Protocols



 3530-series Modbus Support ONLY

The 3530-series supports the Enron Modbus Slave protocol, as well as

the Gould Modbus Master and Slave protocols only on Ports B and C.



Determining Which Protocols Are Currently

Installed in a Network 3000-series Controller

The Open BSI Remote Communication Statistics Tool may be used to

determine which custom protocols are currently installed in a control-

ler. To find out, start the tool and establish communications. Next,

click on "Statistics" in the menu bar, and "Custom Prom" in the pull

down menu.

ACCOL II Custom Protocols Manual

Page Introduction-7

Introduction

Introduction to Network 3000 Custom Protocols

The Custom PROM Information window will appear with a list of the

protocols currently installed. If necessary, use the scroll bar to view

additional protocols, if they will not all fit in the window. For more

information, see the Open BSI Utilities Manual (document# D5081).

Notes For Toolkit Users:

NOTE: If you have a GFC 3308 or a 186 or 386 Real Mode version of

the DPC 3330, DPC 3335, RTU 3305 or RTU 3310 the Toolkit program

may be used to determine which custom protocols are currently in-

stalled in the Custom PROM area of a running Network 3000-series

controller. (Note: For AG.xx or earlier level PROMs, the protocols

included in the standard PROM set

.

will not be visible via this meth-

od.)

1. While the PC is connected to the running controller, call up the

Toolkit program. See the Toolkit User Manual, (document#

D4053) for instructions on how to do this.

2. Call up the Communications Line Statistics Menu (this is also

discussed in the aforementioned manual.)

3. Move the cursor to the 'Custom PROM Detail Information' poke

point and press [Enter]. A list of the protocols installed in this

particular controller will appear on the screen.

BLANK PAGE

ACCOL II Custom Protocols Manual

Page Allen-Bradley Master-1

Allen-Bradley PLC-2/-5 Master Interface

Custom Interface to allow 33XX to function as Allen-Bradley PLC-2/PLC-5 Master

The Custom Module can be configured to interface the Bristol Network

3000 series controller with an Allen-Bradley programmable controller

(PLC). The Bristol controller functions as the master station on a half

duplex communication link. It will periodically poll each slave PLC

station from which it expects a reply message.

Each port is associated with a separate PLC communication link and

the modules are associated with PLC stations on the link. Any number

of modules per port and any number of ports may be used concurrently

for communication with Allen-Bradley PLCs. Messages on a particular

port are sent in the same order as the execution of the Custom mod-

ules.

Messages to read and write PLC data table memory are supported by

the interface. The messages use logical addressing that is compatible

with the PLC, PLC-2, and PLC-5 family controllers. Both PLC-3 and

PLC-5 can also be used in PLC-2 compatibility mode.

The polling frequency and required PLC response time are configur-

able for each port. Messages with communication errors will be retried

up to two times before the attempt is aborted and the error is indi-

cated.

The full duplex link protocol is not supported, nor is peer-to-peer

communication among slave PLC stations over the asynchronous

interface.

ACCOL II Custom Protocols Manual

Page Allen-Bradley Master-2

Allen-Bradley PLC-2/-5 Master Interface

Custom Interface to allow 33XX to function as Allen-Bradley PLC-2/PLC-5 Master

Module Terminals

The following is a list of the terminal values for the Custom Module

when configured for Allen-Bradley mode.

MODE Default: None, entry required

Format: Analog signal or constant

Input/Output: Input

must be set to 2.0 for Allen-Bradley PLC-2 Master mode, or 200.0 for

Allen-Bradley PLC-5 Master mode.

LIST Default: None, entry required

Format: Analog signal or constant

Input/Output: Input

is the signal list that contains the signals used by this module to

control the Allen-Bradley interface. This signal list is referred to as the

Allen-Bradley signal list and is described later. Any valid list number

may be used.

STATUS Default: None, entry optional

Format: Analog signal

Input/Output: Output

is a status code which indicates various communication states and

error conditions of the module.

Communication and processing of PLC reply messages are aborted

when the status code value is negative. The following is a list of the

possible status code values and their definitions.

0 = Communication completed successfully.

1 = Communication requested, waiting to send.



ACCOL II Custom Protocols Manual

Page Allen-Bradley Master-3

Allen-Bradley PLC-2/-5 Master Interface

Custom Interface to allow 33XX to function as Allen-Bradley PLC-2/PLC-5 Master

2 = Command message sent, waiting for reply.

101 = An input signal was Control Inhibited.

102 = Attempt to store into a constant.

103 = An input string signal value was truncated.

104 = Attempt to store into Read Only Data Array.

-2 = Invalid Allen-Bradley Signal List number specified.

-3 = Invalid Port Number specified.

-4 = Invalid PLC Station Number specified.

-5 = Invalid Command Code specified.

-6 = Invalid Read/Write Address specified.

-7 = Invalid Read Size specified.

-8 = Invalid Reply Timeout specified.

-9 = Invalid I/O List number specified.

-10 = Invalid Format number specified.

-11 = Cannot broadcast a Read command.

-12 = Write command has zero length for data.

-13 = Read reply length different than requested.

-14 = Timed out waiting for command reply.

-15 = Receive character overrun detected.

-16 = Receive character parity error detected.

-17 = Receive character framing error detected.

-18 = Receive message security (CRC/BCC) failed.

-19 = Timed out waiting for PLC to respond.

-20 = Invalid PLC response message received.

-21 = Timed out waiting for Clear To Send.

-22 = Unexpected I/O failure.

-30 = Bad PLC-5 logical binary address.

-31 = Bad PLC-5 logical ASCII address.

-32 = String signal length too long.

-33 = PLC-5 command not allowed.

-34 = Bad TOTAL TRANS field.

-35 = Bad PACKET OFFSET field.

-36 = Bad address list for Read-Modify-Write.

-37 = Bad read list for General-Write-Read.

-38 = Bad read format for General-Write-Read.

-39 = Bad command code field for General-Write/Write-Read.

ACCOL II Custom Protocols Manual

Page Allen-Bradley Master-4

Allen-Bradley PLC-2/-5 Master Interface

Custom Interface to allow 33XX to function as Allen-Bradley PLC-2/PLC-5 Master

The following relate to message formatting errors.

-101 = Invalid Format field descriptor.

-102 = Attempt to use signal beyond end of I/O list.

-103 = Too many levels of parentheses.

-104 = Unmatched right parenthesis.

-105 = Invalid Sub Format number specified.

-106 = Too many levels of Sub Formats.

-107 = Invalid Data Array number specified.

-108 = Attempt to use undefined Data Array.

-109 = Attempt to use cell beyond end of Data Array.

-110 = Signal or Data Array cell must be analog.

-111 = Must use a string signal.

-112 = Signal or cell must be analog or logical.

-113 = Invalid BCD input digit.

-114 = Invalid analog value for BCD output.

-115 = Unexpected Input signal store failure.

-116 = Attempt to put/get data beyond end of message.

The following are errors reported via the STS byte of a reply message.

They are the value of the STS byte biased by -1000. These errors are

described in detail in Appendix A of Allen-Bradley publication 1771-

811.

-1016 = Invalid command due to content or size.

-1048 = Processor fault or disconnection.

-1064 = Comm interface could not talk to processor.

-1080 = Access denied for requested address.

-1096 = Command disabled by switch settings.

-1112 = PLC processor in program mode or downloading.

-1128 = Station in error shutdown mode.

-1144 = Interface module out of buffer space.

-1176 = Station in download mode.

The following errors apply only to the PLC-5. They are reported by the

EXT STS field of a reply message (when the STS byte is returned as

0F0 hex). These errors are described in detail in the Allen-Bradley

Data Highway/Data Highway Plus Reference Manual , Allen-Bradley

Page is loading ...

Remote Automation Solutions Bristol ACCOL II Custom Protocols Owner's manual

Related papers

Other documents