XCell CONFIGURATION GUIDE DOCUMENT

CONITEL C300 SLAVE PROTOCOL

VERSION: 1.09
 C300 Slave Protocol
Configuration Guide Rev 1

Revision History

Date Rev Author Comments

19/03/2002 0.01 David M. Swain Draft Version For Review
22/07/02 1.0 A. Kearney Updated and released based on
review

Conitel C300 Slave Protocol Configuration Guide Page 2 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

Table Of Contents
1. INTRODUCTION................................................................................................5
1.1 PURPOSE AND S COPE OF THIS D OCUMENT ...................................................... 5
1.2 REFERENCES ................................................................................................... 5
2. THE PROTOCOL ...............................................................................................6
2.1 INTRODUCTION TO THE CONITEL C300 S LAVE P ROTOCOL .......................... 6
2.2 PHYSICAL LAYER............................................................................................ 6
2.3 LINK LAYER.................................................................................................... 6
2.3.1 Error Checking ......................................................................................7
2.3.2 BCH (Cyclic Code) for Conitel (C300).................................................7
2.4 APPLICATION L AYER ...................................................................................... 8
2.4.1 Conitel (C300) Data Typ es....................................................................8
2.4.1.1 Input Scan Data .................................................................................. 8
2.4.1.2 Analogue Input Block........................................................................ 9
2.4.1.3 Status Input Block.............................................................................. 9
2.4.1.4 MCD Input Block .............................................................................. 9
2.4.1.5 Counter Blocks ................................................................................. 10
2.4.1.6 Control Data ..................................................................................... 10
2.4.1.7 Trip/Close Digital Outputs............................................................... 11
2.4.1.8 Raise/Lower Control Outputs .......................................................... 11
2.4.1.9 Set-point Outputs ............................................................................. 11
2.4.2 Conitel (C300) Functions and Commands......................................... 11
3. THE PROTOCOL SLAVE CONFIGURATION .......................................... 13
3.1 OVERVIEW .................................................................................................... 13
3.2 CREATING T HE CONITEL C300 S LAVE P ROTOCOL C ONFIGURATION TABLES
13
3.2.1 Application Configuration Table Hierarchy....................................... 13
3.3 CONFIGURING THE CONITEL C300 S LAVE PROTOCOL GENERAL
CONFIGURATION T ABLE (CONGEN) ....................................................................... 15
3.3.1 CONGEN Quick Reference................................................................. 16
3.3.2 CONGEN Table Entries...................................................................... 17
3.3.2.1 Tag ................................................................................................... 17
3.3.2.2 Number of LRUs.............................................................................. 17
3.3.2.3 Port Number ..................................................................................... 17
3.3.2.4 Baud_Rate ........................................................................................ 17
3.3.2.5 RTS Keying...................................................................................... 17
3.3.2.6 RTS Key On Time ........................................................................... 18
3.3.2.7 RTS Key Off Time........................................................................... 18
3.3.2.8 LRU Table Start............................................................................... 18
3.4 CONFIGURING THE CONITEL C300 S LAVE PROTOCOL LOGICAL RTU
TABLE (CONLRU)................................................................................................... 19
3.4.1 Protocol Hierarchy............................................................................. 20
3.4.2 Quick Reference.................................................................................. 20
3.4.3 CONLRU Table Entry Fields.............................................................. 21
3.4.3.1 Tag ................................................................................................... 21

Conitel C300 Slave Protocol Configuration Guide Page 3 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

3.4.3.2 Num of Map Tables ......................................................................... 21

3.4.3.3 RTU_Address................................................................................... 21
3.4.3.4 Poll Word Group.............................................................................. 21
3.4.3.5 Map Table Start Record................................................................... 21
3.5 CONFIGURING THE CONITEL C300 S LAVE PROTOCOL P OINT MAPPING
TABLE (CONMAP).................................................................................................. 22
3.5.1 Quick Reference.................................................................................. 23
3.5.2 CONMAP Table Entries ..................................................................... 24
3.5.2.1 Tag ................................................................................................... 24
3.5.2.2 Group ............................................................................................... 24
3.5.2.3 Field ................................................................................................. 24
3.5.2.4 Block ................................................................................................ 24
3.5.2.5 Data Type ......................................................................................... 25
3.5.2.6 Map Range ....................................................................................... 25
3.5.2.7 Option 1............................................................................................ 25
3.5.2.8 Option 2............................................................................................ 26
3.5.2.9 RefTag.............................................................................................. 26
4. DOWNLOADING THE CONFIGURATION ............................................... 27

5. SAMPLE TABLES ........................................................................................... 28

5.1 SAMPLE CONGEN T ABLE ........................................................................... 28
5.2 SAMPLE CONLRU TABLE ............................................................................ 29
5.3 SAMPLE CONMAP TABLE ........................................................................... 30
6. APPENDIX A – CONITEL C300 SLAVE PROTOCOL ERROR CODES32

Conitel C300 Slave Protocol Configuration Guide Page 4 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

1. Introduction
This configuration guide is provided as a companion to the Microsol EXpert Plus
Configuration Tool Users Guide such that the two documents combined will provide
sufficient information for a technically competent user to configure the Microsol
implementation of the Conitel C300 Slave Protocol.

1.1 Purpose and Scope of this Document

This document is provided as a Guide to enable the user to configure the XCell
implementation of the Conitel C300 Slave Protocol interface using the EXpert Plus
Configuration Tool to transmit the required user data, either generated from local I/O or as
virtual data points generated internally, to a protocol compliant Master Control Station or Data
Concentrator (upstream device). In addition command and control data can be received via
the protocol from the ‘upstream’ device.
This guide will enable the user to configure the communications parameters for the protocol
and map specific XCell data points or events to Conitel C300 Addresses. The features and
commands available in the current Microsol implementation of the Conitel C300 Slave
[1]
Protocol are outlined in both the Microsol Conitel C300 Slave Interoperability Checklist
[2].
and the Microsol Conitel C300 Slave Functional Description.
The Microsol implementation of the Conitel C300 Slave Protocol application is under
continuous development to satisfy the evolving requirements of the market and all
efforts are made to maintain backwards -functional compatibility but note that this
guide is targeted at the Microsol Conitel C300 Slave Protocol Version 1.09 and later.
This Configuration Guide is written using Version 1.12 of the Microsol EXpert Plus
Configuration Tool, therefore screens may differ from those shown here if other
versions of the tool are used.

1.2 References
[1] Document Title: Microsol Conitel C300 Slave Interoperability Checklist.
Revision: 1.09
Author:
Source: Microsol Ltd.
[2] Document Title: Microsol Conitel C300 Slave Functional Description.
Revision: 1.09
Author:
Source: Microsol Ltd.
[3] Document Title: EXpert Plus Configuration Tool Users Guide.
Revision: 1.00
Author: Adrian Kearney
Source: Microsol Ltd.

Conitel C300 Slave Protocol Configuration Guide Page 5 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

2. The Protocol

2.1 Introduction to the Conitel C300 Slave Protocol

The Conitel C300 Slave Protocol is a serial bit oriented synchronous protocol that
comprises of a number of 32-bit frames that contain frame marker, data and error checking
components.
The Conitel C300 Slave Protocol is designed to communicate with existing protocol
compliant Master Stations.

2.2 Physical Layer

The Microsol implementation of the Conitel C300 Slave Protocol communicates over a
standard RS-232 half-duplex synchronous serial data-link at configurable standard baud rates
from 300 Bits per Second up to a maximum of 19.2k Bits per Second.
There are two possible modes of physical interfacing:

• Direct RS-232 point-to-point connection to Conitel C300 Protocol master station

• Connection to a Conitel C300 Protocol compatible master station via leased line
modem or radio with an RS-232 interface and synchronous data transfer.
Microsol’s configuration tool (eXpert Plus) supports a range of Conitel C300 Slave Protocol
configurations from a single Master Control Station. Additionally various configurations with
mixed XCell units (e.g. Conitel C300+Kbus+Modbus) on the same network are also
supported.

2.3 Link Layer

A Conitel C300 Slave Protocol message consists of one or more 32-bit words (data frames).
The master station initiates communications with a request message and the RTU (slave
device) will respond to the message if required. Each message is always prefixed by a pre-
transmission mark and start space. Each 32-bit word consists of 3 sections as shown below:

12 Bits 1 Bit 12 Bits 1 Bit 5 Bits 1 Bit

SECTION A A SECTION B B BCH EOM

SECTION C

MSB LSB
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

Due to the size limitations of the Conitel C300 Slave Protocol RTU, the Microsol XCell RTU
may be configured to represent a maximum 10 Conitel C300 Slave Protocol RTU’s, this
technique is called forming logical RTU’s or LRU’s.

Conitel C300 Slave Protocol Configuration Guide Page 6 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

Error Checking
Messages that contain communications errors are not accepted by the RTU. At the
communication port, messages are checked for the following errors:
Incorrect message sync bits

• A message containing a BCH error

• A message containing a incorrect number of bits

• A message containing an incorrect station address

Once the message is passed to the Logical RTU, additional checks are performed and
messages with the following problems are ignored:

• Messages containing invalid function codes

• Messages addressing an invalid group number

• Messages containing incorrect modifier data

BCH (Cyclic Code) for Conitel (C300)

BCH is an acronym, formed from the names of Messrs: Bose, Ray-Chaudhuri and
Hocquenghem, because of their contribution to error detecting cyclic codes. A cyclic code is
so described because of its property, which allows the bits of the code to be cyclically shifted
in some fashion without losing the identity or effectiveness of the code. A cyclic check code
(sometimes called a cyclic redundancy code) is used for message security to detect
transmission errors in master to RTU and RTU to master communications.
In Conitel C300 Slave Protocol transmission, error detection employs a BCH cyclic code
check utilising five parity check bits in each 31-bit message. The use of the BCH coding
provides error detection efficiencies as follows: -

• 100% detection of single and double bit errors

• 100% detection of burst-error patterns of ≤ 5 bits

• 94% detection of burst-error patterns of 6 bits

• 97% detection 0f burst-error patterns of ≥ 7 bits

A burst-error is defined as the number of binary bits between two error bits inclusive. All or
any number of bits in the burst may be in error.
5 2
The BCH code is generated by the polynomial P(X) = X + X + 1, checking on 31 bits. The
stop bit of the Conitel (C300) message structure is excluded. The method used to generate
the 31-bit coded message polynomial, F(X), is as follows:
5
The information polynomial, G(X), consisting of 26 bits (0-25) is multiplied by X to form
5
X G(X) i.e..
25 24 23 2 1
G(X) = A 25X + A24X + A23X + …….. + A2X + A1X + A0
X 5G(X) = A 25X 30 + A24X 29 + A23X 28 + …….. + A2X7 + A1X 6 + A0X5
5 5 2
X G(X) is divided by the generator polynomial P(X)=X + X + 1 to give a quotient Q(X) and
the remainder R(X).
5
The 31-bit coded message polynomial is the sum of X G(X) and R(X):
5
F(X) = X G(X) + R(X)

Conitel C300 Slave Protocol Configuration Guide Page 7 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

30 5
F(X) then has its higher order coefficients (X through X) identically equal to the coefficients
4 0
(X through X ) identically equal to the coefficients of R(X). The check symbols (26-30) then
4 0
are the R(X) coefficients (X through X ) respectively.
In checking, a received message is divided by the generator polynomial P(X). If the resulting
remainder is zero, then either no error or an undetectable error has occurred. If the
remainder is not zero, an error has been detected.

2.4 Application Layer

2.4.1 Conitel (C300) Data Types

The Conitel (C300) communications protocol consists of one or more fixed length 32-bit
message blocks, each of which contain two 12-bit information or data sections. Only these
two sections contain data transmitted between a master and an RTU; the other portions of the
blocks are overhead and communications security. The bits are numbered from one to 32
from left to right with the left-most bit being transmitted first as shown below: -
MSB LSB
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

Conitel (C300) protocol supports several functions. Analogue, counter, status, and
momentary change detection status (MCD) data can be acquired from an RTU. Select-
before-operate trip/close and setpoint outputs are supported along with raise/lower control
outputs. Functions such as counter (pulse accumulator) freeze; re-set of status flags and re-
set of alarm flags can be performed.

2.4.1.1 Input Scan Data

Conitel (C300) consists of five types of request data. These being:

• Analogue Inputs

• Status Inputs

• Momentary Change Detects (MCD’s)

• 12 bit MSB of 24-bit Counters

• 12 bit LSB of 24-bit Counters

Scan data is data returned by the RTU in respons e to a request for that data, arranged into
data sections. Each data section is 12 bits in length and is identified by a section number and
a section identifier (A or B). Scan data can be analogue, counter, status or change of status.
Status indications are grouped in 12-bit sections, which may define either 12 or six inputs.
Simple status data forms a section representing the current state of 12 input points. MCD
status data forms a section representing the current state of six input points paired with a
change flag for each point.
Status inputs (including MCD) can be defined as either FORM-A or FORM-B inputs presented
to the RTU. A ZERO (0) represents FORM-A inputs when the contact is in the OPEN state
and ONE (1) when the contact is in the CLOSED sta te. A ONE (1) represents FORM-B
inputs when the contact is in the OPEN state and ZERO (0) when the contact is in the
CLOSED state. This representation is shown below: -

Conitel C300 Slave Protocol Configuration Guide Page 8 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

FORM INPUT STATE BINARY VALUE

A OPEN 0
A CLOSED 1
B OPEN 1
B CLOSED 0

Analogue Input Block

Analogue inputs each occupy one data block of 12 bits. This analogue input value is
contained in eleven (11) bits for the absolute value of the point and the MSB of the 12 bits
contains the sign of the point, (1 = positive, 0 = negative). To convert the standard XCell
analogue input format into 11 bits plus sign, scaling and offset is used. This scaling and
offset is configurable on a per point basis.
Conitel (C300) Analogue data is a 12-bit two's complement binary value, with a range from
negative 2047 counts to positive 2047 counts for a positive or negative full-scale input
respectively. The most significant bit is the sign bit, with a 0 representing positive and a 1
representing negative values. There is one analogue data value per scan data section.

2.4.1.2 Status Input Block

A 12-bit status input block contains 12 single bit digital inputs. These digital inputs can come
from anywhere in the RTU and are mapped into the 12 bit blocks. On restart all status inputs
are set to the same as the field value.
The twelve status inputs, which can be stored in a data section, are arranged as twelve
adjacent data bits with each bit representing one status input. A ONE or a ZERO in the
format shown below represents the state of the bit: -
MSB LSB

1 2 3 4 5 6 7 8 9 10 11 12

2.4.1.3 MCD Input Block

A 12-bit MCD input block contains 12 single MCD’s. Each MCD must be related to a status
input, and for ease of configuration, a block of MCD’s will map directly to a block of status
inputs. MCD’s are generated from status inputs and are not directly related to any field I/O.
Usually MCD blocks are placed in the next addressable block after its associated status input
block. On power on and restart, all MCD’s are set to zero (0).
MCD’s are generated with their associated status input. They act similarly to a two-bit
counter, incrementing each time the digital input changes state. The status bit is the LSB and
the MCD is the MSB. The figure below shows how the MCD’s are generated.

STS=0 STS=1 STS=0 STS=1 STS=0

MCD=0 MCD=0 MCD=1 MCD=1 MCD=0

There is a facility to clear the MCD. This message type is called a Reset Change Detector
Execute message (explained in detail later in this document).
Momentary change detect status or MCD requires two bits of information to describe a digital
input. The six MCD status inputs, which can be stored in a data section, are arranged as
pairs of adjacent data bits with the most significant bit representing the momentary (M)

Conitel C300 Slave Protocol Configuration Guide Page 9 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

change flag or the history of changes of the digital input. The lesser significant bit of the pair
represents the state (S) of the input. The organisation of this data is described below: -
MSB LSB
M S M S M S M S M S M S
1 2 3 4 5 6 7 8 9 10 11 12
Three configurable formats are available to define when the history bit will be set for the
digital input. These are:

• An input change from logical 0 to logical 1,

• An input change from logical 1 to logical 0,

• Two input state changes after a master scan.

The MCD change flag is always reset after a scan of the MCD data by the master station.
Should the master not receive this transmitted data, it is available to the master through a
retransmit-last-response message.

2.4.1.4 Counter Blocks

All counters in this application are 24 bits in length. They can be configured to count either
pulses or transitions. There are 2 Conitel (C300) counter block types, the low 12 bits of a 24-
bit counter and the high 12 bits of a 24-bit counter.
Upon power up or restart, the running value of the counter is contained in the data reported to
the Conitel (C300) master station. If a freeze command is presented to the RTU, the value
returned to the master station will be the running value at the time of the last freeze
command.
Therefore if running counter values are required, just don’t send a freeze command to the
RTU, as once this occurs the RTU will only report the last frozen value until another freeze
command is issued.
Also, if only 12 bits are required for the counters, simply don’t configure the MS 12 bits of the
counter into any request blocks.
Counter data are 12 or 24-bit binary counters which increment to a maximum value and roll
over to zero. They may count contact transitions or full contact cycles, and may be either
FORM-A (single input) or FORM-C (paired input) types. A 12-bit counter is reported in one
data section. A 24-bit counter is reported in two data sections with the most significant 12 bits
in one data section and the least significant 12 bits in another data section. Note that the low
12 bits of a 24-bit counter are identical to a 12-bit counter. No distinction is made between
these formats. The most significant bit of each counter section is transmitted first.

2.4.1.5 Control Data

Control data in the Conitel (C300) application consist of 3 types of outputs, which are: -

• Trip/Close Digital Outputs

• Raise/Lower Control Output

• Set-point Output
Control output data is a request sent by the master to the RTU for an output by the RTU. The
request is contained in a data section of 12 bits in length and may be either a single bit
requesting a trip/close type of control, three separate fields of four bits each requesting up to
three raise/lower controls, or a 12-bit value requesting a set-point type output. The data
format is dependant upon the function code.

Conitel C300 Slave Protocol Configuration Guide Page 10 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

2.4.1.6 Trip/Close Digital Outputs

Trip/close control outputs are addressed in groups of 12 points each. Only one point of the
12 may be selected for a single control output operation. The function code defines whether
a trip or close operation is requested. The selected relay is activated after the select-before-
operate sequence has been successfully completed.
The format for the control output select message is shown at the start of this chapter. The
group number and the modifier contained in the message provide the control output number
to be selected. The following calculation provides the correct digital output number:
DO Number = (Group No. * 12) + (Modifier bit offset)
Therefore, if the modifier is set to 000000000100 (bit 14 through to bit 25) and the group
number is binary 010, then the DO point number would be (2*12)+3 = 27, with the first DO
point being 1. Only one bit can be set at any time in the message modifier from the master
station.

2.4.1.7 Raise/Lower Control Outputs

Raise/lower control outputs are addressed in groups of up to three points per group address
at an RTU. The 12-bit data section in the master message contains a four-bit instruction for
each of three points. The most significant bit in each field specifies a raise control if the bit is
ONE (1) and a lower control if the bit is ZERO (0). The remaining three bits of each field is a
multiplier, which is used to calculate the pulse width or contact closure for the output. A four-
bit field with a binary value of zero is a null command for that output and will have no effect
upon the output.

2.4.1.8 Set-point Outputs

Analogue Set-points are the only type of set-point supported in this application. Each
analogue set-point uses a 12-bit value, sent from the master station. Set-points are arranged
in two groups with 8 outputs per group, thus providing a total of 16 analogue outputs. The
first group is uses the Trip function number and the second group uses the Close function
number. The group number selects the point number within the group and the modifier
contains the actual data to be output.
The set-point outputs use the same station address (station base + 2) as the Data Request.
Set-point outputs are addressed in groups of one at the RTU. The master will transmit a
digital value, which will be converted by application dependant scaling to a value appropriate
to the output device. There are two set-point function codes (SETPOINT A and SETPOINT
B), which are functionally identical, but allow the master to address twice as many set-point
points at the RTU than would otherwise be available with a single set-point function code. An
execute command should be followed to operate set-point outputs.

2.4.2 Conitel (C300) Functions and Commands

When the RTU receives a message through the communications port from the master station,
the message is assumed to be free of errors. The RTU checks each message for errors
relating to h t e particular function code. Details of each of these checks are provided later in
this chapter.
The function codes supported by the Conitel (C300) communication protocol define the
supported messages of transmission of data between a master and an RTU. The table below
lists the function supported for each function code. All function code numbers are
hexadecimal.

Conitel C300 Slave Protocol Configuration Guide Page 11 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

Code (Hex) RTU Function

0 Scan Request Command
1 Execute Command
2 Trip (Check-Before-Operate) Command
3 Setpoint A Command
4 Close (Check-Before-Operate) Command
5 Setpoint B Command
6 Error Response from Remote
7 Not Used
8 Reset Control Command
9 Escape
A Scan SOE Buffer Command
B Retransmit Last Message
C Not Used
D Raise/Lower Control Command
E Freeze Counters Command

Each function code follows the basic format as described in chapter 2. The master request is
typically one block in length and the RTU response may be one to sixteen blocks in length.
The following sections describe each message and the format of the data in each of the
fields. When the value of a field is non-varying for the message, its value is included in the
diagram underneath the field label. When the field may have other than a specific value, the
field label is provided and the data is not specified. A typical case is the end-of-message bit,
which will be one (1) for the last message block. In the case of the SCAN DATA or FREEZE
COUNTER functions, the amount of data is variable and the end-of-message bit will only be
set in the last block.

Conitel C300 Slave Protocol Configuration Guide Page 12 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

3. The Protocol Slave Configuration

3.1 Overview
Three protocol tables (CONGEN, CONMAP and CONLRU) are used to configure this
implementation of the Conitel C300 Slave Protocol. These must be configured on the
Conitel C300 Slave Protocol interface unit. A brief description of these tables are given in
the sections following:

3.2 Creating The Conitel C300 Slave Protocol Configuration

Tables
This section briefly outlines how to set-up and configure the three configuration tables
(CONGEN, CONLRU and CONMAP) required by the Conitel C300 Slave Protocol in the
Microsol EXpert Plus Configuration Tool and a detailed description of each table and all of
the associated parameters, and where possible their rules, limits and effects.
To begin the definition of an XCell configuration for the Conitel C300 Slave Protocol it is first
necessary to create an XCell unit node beneath an appropriate Project node (Conitel C300
Test) and RTU node (RTU_01). Once this is done right-click on the XCell Unit node (Conitel
C300 Unit in the diagram) within the Project view, select New and then one of the Conitel
Slave tables (CONGEN, CONLRU or CONMAP) as shown in the diagram below.

The three possible

Conitel C300 Tables
in DMT, CONGEN,
CONLRU and
Conitel C300 Unit CONMAP. Only ONE
Node. table is allowed in
each Unit
Configuration.

Figure 1 - Conitel C300 Unit Node With Table Selection Box

3.2.1 Application Configuration Table Hierarchy

There is a definite hierarchy for the configuration tables. The General Configuration table
configures the COMMS layer for the system. This table references the LRU table, which

Conitel C300 Slave Protocol Configuration Guide Page 13 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

configures the LRU layer of the system, and the LRU tables reference the Mapping table for
the system. This mapping table defines how the XCell points are converted to Conitel C300
points for transmission to the master station.
Shown in the diagram below is an example of how the tables relate to one another:

CONGEN1 CONLRU1 CONMAP1

CONLRU2 CONMAP2

CONMAP3
CONMAP4

CONMAP5

CONMAP6

In the case above, one CONGEN record points to two LRU records. Each of these CONLRU
records uses three mapping records.

Conitel C300 Slave Protocol Configuration Guide Page 14 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

3.3 Configuring The Conitel C300 Slave Protocol General

Configuration Table (CONGEN)

Within the Grid View of eXpert Plus, one row corresponds to one instance of the Conitel
C300 Slave Protocol. The standard XCell system allows only one instance of Conitel C300
Slave Protocol per Cell and therefore only one row of the CONGEN Table should be defined.
Parameter configuration of the CONGEN table can be done via the Grid view or using the
Property menu on the Project view. To display the CONGEN in the Grid view right-click on
CONGEN node in the Project view and select Show in Grid. To display the Property window
right-click on the CONGEN node in the Project view and select Properties. Both display
options are shown simultaneously in the following diagram.

CONGEN Table
Properties Shown In Grid
View (Below) &
Properties View (Right)

Figure 2 - CONGEN Table Shown in Both Grid View & Properties View

Conitel C300 Slave Protocol Configuration Guide Page 15 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

3.3.1 CONGEN Quick Reference

This section provides a Quick Reference table that provides basic information for setting up
the Conitel C300 Slave Protocol CONGEN table; it contains enough information for a user
who is familiar with the Conitel C300 Slave Protocol and eXpert Plus to configure the
CONGEN Table for their particular system. For a more detailed explanation of the individual
fields see the paragraphs in the CONGEN Fields section of this document.

Table 1 – CONGEN Quick Reference Table

Field Name Limits Remarks/Default Value

Tag 15 Alpha-Numeric Conitel C300 Slave Protocol Identifier. Download with
Characters Tag’s greater than 16 characters is not possible.
Description 40 Characters Description of the Conitel C300 Slave Protocol.
Number of LRUs 1 to 255 Defines the number of contiguous records in the
CONLRU table (default value is 1).
It is vital for the correct operation of the unit that
this field is an accurate reflection of the number of
records in the CONLRU table.
Port Number COM1 or COM2 Defines the XCell Communications Port to use when
communicating with the Master Control Station (default
COM2).
Baud Rate 200, 300, 600, 1200, Communications speed to the Master Control Station in bits
2400, 4800, 9600, per second (default 1200bps).
19200
RTS_Keying Enabled/Disabled Enables/Disables RTS Keying, RTS Keying only needs to be
Enabled if a device requires time to prepare it’s
communications medium before receiving data from the
XCell unit (e.g. radio devices) (default ‘Disabled’).
RTS_Key_On_Time 0 to 65,535mS The time, in milliseconds, from asserting the RTS control
line to transmitting the first byte of data (default 0)
RTS_Key_Off_Time 0 to 65,535mS The time, in milliseconds, from transmitting the last byte
of data to de-asserting the RTS control line (default 0)
LRU Table Start 0 Defines the record number in the CONLRU table of the first
(DO NOT CHANGE) logical RTU that is attached to this Conitel C300 Slave
Protocol (default value is 0).
As eXpert Plus assigns the LRU records starting at 0
and there can only be one record in this the CONGEN
table the value in this field MUST NOT be changed.

Conitel C300 Slave Protocol Configuration Guide Page 16 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

3.3.2 CONGEN Table Entries

3.3.2.1 Tag
The ‘Tag’ field is a TEXT entry field
with a maximum length of 16
alphanumeric characters; it is only
used as an identifier for items in the
Project View. It has no other purpose
than an indicator and is not
downloaded to the Slave Protocol
RTU as part of the configuration
database.
NOTE: Tag entries longer than 16
characters will generate the error
“Download Failed” when the
configuration download is Figure 3 -CONGEN Table Property View
attempted.

3.3.2.2 Number of LRUs

The ‘Number of LRUs’ field is a NUMERIC field that defines the number of Logical RTU’s
attached to this Conitel C300 Slave Protocol and as such is simply a count of the number of
entries in the CONLRU table, see below. The range of this field is 1 to 255 and the default
value is 1. It is important that this value accurately reflects the count of LRU’s defined
in the CONLRU table.

3.3.2.3 Port Number

The ‘Port Number’ field is a PICK LIST field that allows the selection of the physical XCell
communications port that is to be used by the Slave protocol to communicate with the Master
Control Station. The default is COM2, which is the lower port on the XCell CPR front panel
leaving COM1 free for configuration downloading.

3.3.2.4 Baud_Rate
The ‘Baud Rate’ field is a PICK LIST field that allows the setting of the data rate to the
Master Control Station connected to the selected communications port. The setting of this
field must be made reflecting the quality of the communications links to the Master Control
Station. The default value is 1200bps (bits per second) with the available values being:
• 600
• 1200
• 2400
• 4800
• 9600
• 19200

3.3.2.5 RTS Keying

The ‘RTS Keying’ field is a PICK-LIST field used to Enable or Disable the RTS hardware
handshaking. This is normally ‘Disabled’ in the Conitel C300 Slave Protocol therefore the
following two fields ‘RTS Key OFF Time’ and ‘RTS Key ON Time’ are ignored, to enable
RTS Keying a value of ‘Enabled’ should be selected.

Conitel C300 Slave Protocol Configuration Guide Page 17 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

3.3.2.6 RTS Key On Time

The ‘RTS Key On Time’ field is a NUMERIC entry field that is used to define the time delay,
in milliseconds, between the XCell device asserting the RTS control line to the remote
communications device and sending the first character of the data transmission from the
selected serial port.
This is used where RTS is keying-on a transmission device (e.g. modem or radio) that takes a
non-zero time to prepare the data link so that data cannot be transmitted until the device is
ready. This value defaults to 0 milliseconds when RTS Keying is disabled, the required
values for this field should be taken from the communications device manufacturers
handbook.

3.3.2.7 RTS Key Off Time

The ‘RTS Key Off Time’ field is a NUMERIC entry field that is used to define the time delay,
in milliseconds, between the XCell device sending the last character of a data transmission
to the remote communications device and de-asserting the RTS control line.
This is used to allow sufficient time for the transmitting device to send the last character of
data before the RTS line being de-asserted disables the device. The default value is set to 0
milliseconds when RTS keying is disabled, values for this field should be taken from the
communication device manufacturers handbook.

3.3.2.8 LRU Table Start

The ‘LRU Table Start’ field is a NUMERIC field that defines the record number of the first
Logical RTU in the CONLRU Table that is attached to this CONGEN record. The default value
is 0. As it is only possible to have a single CONGEN record the default value should
NEVER be changed, as eXpert Plus will automatically assign record 0 to the first LRU
entry.

Conitel C300 Slave Protocol Configuration Guide Page 18 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

3.4 Configuring The Conitel C300 Slave P rotocol Logical RTU

Table (CONLRU)
As stated previously the Conitel C300 Slave Protocol configuration tables should be defined
under an XCell unit node. To define a CONLRU table right-click on the XCell Unit node within
the Project view, select New and then the CONLRU option. Only one CONLRU table can be
created.
After creating the CONLRU table, the individual Logical RTU entries must be added. Right
clicking on the CONLRU table selecting New and then the CONLRU node option does this.
Create as many entries as required. The parameters associated with each CONLRU may be
edited in the Grid View at the bottom of the display or in the Property View. Each of these
parameters will be described in the following sections giving their defaults and recommended
settings. A sample eXpert Plus configuration with a CONLRU entry selected in both the Grid
View and the Properties View is shown in the following diagram.

Sample configuration
with three CONLRU
nodes, one is shown in
the Property view (right)
and all three are shown
in the Grid view (below).

Figure 4 - Sample Configuration with 3 Logical RTU's Configured

Conitel C300 Slave Protocol Configuration Guide Page 19 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

3.4.1 Protocol Hierarchy

Each Conitel LRU supports up to 16 groups numbered 0 to 15. Each group or Scan Group
consists of up to 31 words (which are each 12 bits wide) numbered 0 to 30. Each one of
these words is referred to in the Protocol Qualifier by the Point number. The 31 words in
each Scan Group make up the total amount of memory available for configuration of the
following input types:
• Digital Input
• Momentary Change Detect (MCD - Type A)
• Momentary Change Detect (MCD - Type B)
• Momentary Change Detect (MCD - Type C)
• 12-Bit Accumulators
• 24-Bit Accumulators
• Analogue Input
Therefore the user must be careful not to overlap the memory areas used by the various input
data types within each LRU. The output data types do not have memory areas associated
with them and therefore have their own Point numbering range of values. The Protocol
Qualifier for this protocol consists of the following:
• Group - 0…. 15
• Point - 0…. 30
• Type - (Data Types see above)
• Option1 - Data Type Specific field (optional)
• Option2 - Data Type Specific field (optional)

3.4.2 Quick Reference

This section provides a Quick Reference table that provides basic information for setting up
the Conitel C300 Slave Protocol CONLRU table; it contains enough information for a user
who is familiar with the Conitel C300 Slave Protocol and eXpert Plus to configure the
CONLRU Table for their particular system. For a more detailed explanation of the individual
fields see the paragraphs in the CONLRU Entry Fields section of this document.

Table 2 - CONLRU Quick Reference Table

Field Limits Remarks/Default Value

Name
Tag 15 Alpha- Conitel C300 Slave Protocol Logical RTU Identifier. This field is used as the
Numeric ‘RefTag’ when selecting which LRU is associated with which MAP table entry.
Characters Download with Tag’s greater than 16 characters is not possible.
Description 40 Brief Description of this Conitel C300 Slave Protocol Logical RTU Identifier.
Characters
Num of Map 1 to 65535 Defines the number of contiguous Map table records that are associated
Tables with this Logical RTU. The set of Map table records assigned to this LRU do
not have to be unique (they can overlap or be a sub-set of another LRU) but
must be contiguous (default value 1).
RTU_Address 1 to 254 Defines the unique address of this Logical RTU (default value 1).
Poll Word 0 to 15 Defines the group number that the Conitel C300 Slave Protocol poll word is
Group returned in Scan data (default value 0).
Map Table 0 to 65535 Defines the first record number of the contiguous block of Map table records
Start Record associated with this Logical RTU. The set of Map table records assigned to this
LRU do not have to be unique (they can overlap or be a sub-set of another
LRU) but must be contiguous (default value 1). Note: However the Map table
records MUST be assigned to the same unit as the LRU.

Conitel C300 Slave Protocol Configuration Guide Page 20 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

3.4.3 CONLRU Table Entry Fields

3.4.3.1 Tag
The ‘Tag’ field is a TEXT entry field
with a maximum length of 16
alphanumeric characters; it is used as
an identifier for items in the Project.
NOTE: Tag entries longer than 16
characters will generate the error
“Download Failed” when the
configuration download is
Figure 5 - CONLRU Property Box
attempted.

3.4.3.2 Num of Map Tables

The ‘Num of Map Tables’ field is a NUMERIC field that defines the number of contiguous
map records in the CONMAP table that are associated with this Logical RTU. The Map table
records DO NOT have to be unique to this LRU but must be contiguous (i.e. they can overlap
the range of another LRU or may be a sub-set of another LRU mapping table). The default
value of this field is 1 with a range of 1 to 65535.

3.4.3.3 RTU_Address
The ‘RTU_Address’ field is a NUMERIC field that specifies the UNIQUE address within all of
the slave devices connected to the Master Control Station of this Logical RTU. The default
value of this field is 1 with a range of 1 to 254.

3.4.3.4 Poll Word Group

The ‘Poll Word Group’ field is a NUMERIC field that defines the Conitel C300 Slave
Protocol group in which the Poll Word is returned. The default value for this field is 0 with a
range of 0 to 15 (maximum number of groups allowable, Protocol Hierarchy section above).

3.4.3.5 Map Table Start Record

The ‘Map Table Start Record’ field is a NUMERIC field that defines the first record of the
contiguous block of map records in the CONMAP table that is associated with this LRU. The
default value for this field is 0 with a range of 0 to 65535.

Conitel C300 Slave Protocol Configuration Guide Page 21 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

3.5 Configuring The Conitel C300 Slave Protocol Point

Mapping Table (CONMAP)
As stated previously the Conitel C300 Slave Protocol configuration tables should be defined
under an XCell unit node. To define a CONMAP table right-click on the XCell Unit node within
the Project view, select New and then the CONMAP option. Only one CONMAP element can
be created.
After creating the CONMAP entry, the individual map entries must be added. Right clicking on
the CONMAP entry selecting New and then the CONMAP option does this. Create as many
entries as required. The parameters associated with each CONMAP entry may be edited in
the Grid View at the bottom of the display or in the Property View. Each of these parameters
will be described in the following sections giving their defaults and recommended settings. A
sample eXpert Plus configuration with a CONMAP entry selected in both the Grid View and
the Properties View is shown in the following diagram.

CONMAP Entry parameters

shown in Grid View (Below)
and Property Box (above)

Figure 6 - Sample Configuration With CONMAP Entry Shown In Grid and Property Views

Conitel C300 Slave Protocol Configuration Guide Page 22 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

3.5.1 Quick Reference

This section provides a Quick Reference table that provides basic information for setting up
the Conitel C300 Slave Protocol CONMAP table; it contains enough information for a user
who is familiar with the Conitel C300 Slave Protocol and eXpert Plus to configure the
CONMAP Table for their particular system. For a more detailed explanation of the individual
fields see the paragraphs in the CONMAP Entry Fields section of this document.

Table 3 – CONMAP Quick Reference Table

Field Limits Remarks/Default Value

Name
Tag 15 Alpha- Reference for this Conitel C300 Slave Protocol Map Table entry.
Numeric Download with Tag’s greater than 16 characters is not possible.
Characters
Description 40 Characters Brief textual description of this Conitel C300 Slave Protocol Map entry,
for use with eXpert Plus only.
Group 0 to 15 Defines the Conitel C300 Slave Protocol Group number to which this
map table entry is to be assigned (default is 0).
Field Pick List (See Defines the XCell Data type of RefTag (default Not selected), see
Table) below for available data types (default 1-bit Data).
Block 0 to 30 Defines the Conitel C300 Slave Protocol data position within the
Group, each Block is 12-bits wide and there are 31 available blocks per
group (default value is 0).
Data Type Pick List (See Defines the Conitel C300 Slave Protocol data type that maps to the
Table) ‘equivalent’ XCell data defined above (default Single State Monitor).
Map Range 1 to 255 Defines the number of sequential XCell data points selected for transfer
starting at ‘RefTag’ and continuing in a contiguous block for
‘Map_Range’ data points (default 1)
Option 1 Dependant on Defines any auxiliary data required by the selected point type, see the
Data Type detailed description below for possible values for this field (default value
is 0).
Option 2 Dependant on Defines any auxiliary data required by the selected point type, see the
Data Type detailed description below for possible values for this field (default value
is 0).
RefTag EXpert Plus Defines the data point that is to be mapped onto the Conitel C300
SELECT Slave Protocol (default value is <NULL>.
DIALOG

Conitel C300 Slave Protocol Configuration Guide Page 23 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

3.5.2 CONMAP Table Entries

3.5.2.1 Tag
The ‘Tag’ field is a TEXT entry
field with a maximum length of
16 alphanumeric characters; it
is only used as an identifier for
items in the Project View. It has
no other purpose than an
indicator and is not
downloaded to the RTU as part
of the configuration database.
NOTE: Tag entries longer
than 16 characters will
generate the error Figure 7 - Sample CONMAP Table In Property View
“Download Failed” when the
configuration download is
attempted.

3.5.2.2 Group
The ‘Group’ field is a NUMERIC entry field that defines the Conitel C300 Slave Protocol
Group to which this map record is to be assigned. There are 16 Groups possible in each
Logical RTU with each Group comprising 32 12-bit words of which 31 are available for data
storage. The combination of Map_Range and the size of the individual data type MUST not
exceed the maximum storage for the remaining unallocated storage for one Group. The
default value of this field is 0 with a range of 0 to 15.

3.5.2.3 Field
The ‘Field’ field is a PICK LIST field that defines the type of XCell data to which the Conitel
C300 Slave Protocol data value is to be mapped. The default value of this field is 1-nbit data
and the range of available XCell data types can be found in Table 4 below. If a block of
sequential points is being configured in a single entry in the CONMAP then the RefTag must
refer to the first point in the sequential block.

Table 4 - XCell Data Types Available

XCell Data Type

1-bit Data
2-bit Data
8-bit Data
16-bit Data
32-bit Data
Suppression
Not Selected

3.5.2.4 Block
The ‘Block’ field is a NUMERIC field that defines the Data Block within the Conitel C300
Slave Protocol Group to which the point selected by the RefTag is assigned. If the
combination of Data Type (Field) and Map_Range exceeds one Block (12-bits) then the
remaining data in the Map_Range is assigned contiguous block numbers within the Group

Conitel C300 Slave Protocol Configuration Guide Page 24 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

but will NOT exceed the single Group. The default value of this field is 0 with a range of 0 to
30.

3.5.2.5 Data Type

The ‘Data_Type ’ field is a PICK LIST field that defines the Conitel C300 Slave Protocol
data type associated with this mapping record. This field and the Field’
‘ above perform the
translation from XCell native data type to Conitel C300 Slave Protocol data type so that the
data point can be transmitted to the Master Control Station. The default value for this field is
Single State Monitor; the table below gives the complete range of available data types along
with their grouping as INPUT (Scan Data) or OUTPUT (Control Data).

Table 5 - Ferranti Mk2A Protocol (Northern Electric Version) Data Types

Conitel C300 Protocol Data Types

Digital Input [Scan Data]
Momentary Change Detect A [Scan Data]
Momentary Change Detect B [Scan Data]
Momentary Change Detect C [Scan Data]
12-bit Accums [Scan Data]
24-bit Accums [Scan Data]
Analogue Input [Scan Data]

Digital Output [Control Data]

Set Point [Control Data]
Raise/Lower [Scan Data]

3.5.2.6 Map Range

The ‘Map_Range’ field is a NUMERIC field that defines a range of sequential XCell data
points to transfer, commencing at the RefTag. All points defined by the ‘Map_Range’ will use
the same transfer parameters. The default value of this field is 1 with a range of 1 to 255, 0 is
invalid.

3.5.2.7 Option 1
The ‘Option 1’ field is a NUMERIC entry field that contains auxiliary data specific to certain
Conitel C300 Slave Protocol Data Types, the following list gives the ranges for each data
type. The default value of this field is 0 with a maximum permissible range of 0 to 65535.

3.5.2.7.1 Scan data

Digital Inputs: Value range of 0….11 (Specifies the point offset within the Scan Group
word. Each Scan Group word can support 12 Digital Inputs)
MCDs: Value range of 0….5 (Specifies the point offset within the Scan Group
word. Each Scan Group word can support 6 Momentary Change Detects)
Accumulators: Not Used.
Analogue Inputs: Not Used.

3.5.2.7.2 Controls
Digital Outputs: Control Output Pulse Duration in milliseconds

Conitel C300 Slave Protocol Configuration Guide Page 25 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

Setpoint: Not used

Raise/Lower: Base Value used in the calculation: Duration in ms = Base x (Offset +
Control Value) - Control Value is passed through the command

3.5.2.8 Option 2
The ‘Option 2’ field is a NUMERIC entry field that contains auxiliary data specific to certain
Conitel C300 Slave Protocol Data Types, the following list gives the ranges for each data
type. The default value of this field is 0 with a maximum permissible range of 0 to 65535.

3.5.2.8.1 Scan data

Digital Inputs: Value range of 0….127 (Specifies the starting SOE point number for the
range of Digital Inputs denoted by this Protocol Qualifier in this Scan
Group)
MCDs: Not Used
Accumulators: Not Used.
Analogue Inputs: Not used

3.5.2.8.2 Controls
Digital Outputs: Select-Execute Valid Duration in milliseconds
Setpoint: Not Used.
Raise/Lower: Offset Value used in the calculation: Duration in ms = Base x (Offset +
Control Value)- Control Value is passed through the command.

3.5.2.9 RefTag
The ‘RefTag’ field is an
EXPERT PLUS SELECT
DIALOG field that specifies the
XCell special point (RAWDI for
internal status mapping) or I/O
data point (SDI, DDI, AIN etc.)
That is to be mapped to the
Conitel C300 Slave Protocol
data point. This entry must be
selected from a list of
configured I/O points and
special points that can be
found in the Select Instance
dialog.

Figure 8 - Conitel C300 Slave Protocol RefTag Selection Dialog

Example

Conitel C300 Slave Protocol Configuration Guide Page 26 of 32

 C300 Slave Protocol
Configuration Guide Rev 1

4. Downloading The Configuration

When the configuration entry is complete it must then be compiled and finally downloaded
into the XCell Conitel C300 Slave Protocol unit. The Protocol tables should be downloaded
to the Conitel C300 Slave Protocol unit in a specific order to ensure correct operation; this
order is defined by the following sequence.
1. CONMAP
2. CONLRU
3. CONGEN (Loading this table will cause the XCell to reboot)

Conitel C300 Slave Protocol Configuration Guide Page 27 of 32

 The Conitel C300 Slave
Protocol
Configuration Guide Version 1.09

5. Sample Tables
The following table and associated notes present a representative sample of the parameters that are usable with the Conitel C300 Slave Protocol Tables in
eXpert Plus. These tables are derived from a working configuration where only minor differences exist to better display the options available within the table.
For additional explanation of the field contents see the footnotes at the end of each table.

5.1 Sample CONGEN Table

This is a sample Conitel C300 Slave Protocol General Configuration Table (CONGEN) it reflects the parameters used in the sample configuration
throughout this document, for any special notes see the footnotes against each applicable parameter.
Table 6 - Sample CONGEN Table

Tag Description Number of Port Baud RTS RTS Key Off Time RTS Key On Time LRU Table
LRUs Number Rate Keying Start
CONGEN Conitel Unit 1 31 COM2 9600 Disabled 0 0 02

1
The value in this field MUST accurately reflect the number of complete records in the CNLRU table
2
As DMT automatically assigns record 0 as the first LRU record this value should not be changed.

Conitel C300 Slave Protocol Configuration Guide (DMT V1.12) Page 28 of 32

 The Conitel C300 Slave
Protocol
Configuration Guide Version 1.09

5.2 Sample CONLRU Table

This is a sample Conitel C300 Slave Protocol LRU Table (CONLRU) it reflects the parameters used in the sample configuration throughout this document,
for any special notes see the footnotes against each applicable parameter.
Table 7 - Sample CONLRU Table with 3 Logical RTU's Configured

Tag Description Num of Map Tables RTU Address Poll Word Group Map Table Start Record
3
LRU_0 Unit 1 LRU 0 6 0 0 04
LRU_1 Unit 1 LRU 1 43 10 0 7
LRU_2 Unit 1 LRU 2 10 11 0 50

3
Address MUST be unique but does not have to be contiguous.
4
Map records used must be defined on this unit, and LRU blocks MUST be contiguous, here is a simple table with 59 consecutive and contiguous records but blocks can
overlap if required.

Conitel C300 Slave Protocol Configuration Guide (DMT V1.12) Page 29 of 32

 The Conitel C300 Slave
Protocol
Configuration Guide Version 1.09

5.3 Sample CONMAP Table

This is a sample Conitel C300 Slave Protocol Mapping Table (CONMAP) it reflects the parameters used in the sample configuration throughout this
document, for any special notes see the footnotes against each applicable parameter.
Table 8 - Sample CONMAP Table For LRU 1

Tag Description Group Field Block Data Type Map Range Option 1 Option 2 RefTag
FEEDER_1_I Feeder 1 05 8-bit data 06 Analogue Inputs 3 0 0 FDR_1_P1I
Currents
FEEDER_1_V Feeder 1 0 8-bit data 3 Analogue Inputs 3 0 0 FDR_1_P1V
Voltages
FEEDER_1_ETRP Feeder 1 Earth 0 1-bit data 67 Digital Inputs 3 08 09 FDR_1_TRP1
Trips
FEEDER_1_BRK Feeder 1 0 2-bit data 7 MCD-A 3 0 0 FDR_1_BRK1
Breaker Status
FEEDER_1_T0_OIL Feeder 1 0 8-bit data 8 Analogue Inputs 1 0 0 FDR_1_OILT
Transformer 0
Oil Temp

5
All Feeder 1 data can be packed into Group 0 as shown.
6
The three Current readings are returned as 8-bit values therefore use the first three blocks of Group 0 (12-bits per block).
7
Different types of data are kept to separate blocks even if data does not fill block.
8
As we are not optimally packing data trip status start at bit 0 in block.
9
Trip status for feeder 1 start at SOE record 0, overall feeder status would then be SOE record 3 (0,1,2 trip status and 3 is breaker status)

Conitel C300 Slave Protocol Configuration Guide (DMT V1.12) Page 30 of 32

 The Conitel C300 Slave
Protocol
Configuration Guide Version 1.09

Oil Temp
FEEDER_1_TCNT Feeder 1 Trip 0 32-bit data10 9 12-bit Accums 1 0 0 FDR_1_TCNT
Counter
FEEDER_1_OK Feeder 1 0 1-bit data 10 Digital Inputs 1 0 3 FDR_1_STAT
Status

10
Conitel 12-bit counters are directed to XCell 32-bit counter data.

Conitel C300 Slave Protocol Configuration Guide (DMT V1.12) Page 31 of 32

 The Conitel C300 Slave Protocol
Configuration Guide Version 1.09

6. Appendix A – Conitel C300 Slave Protocol Error

Codes
The following table defines all of the possible error codes that can be displayed on the XCell
unit front panel display that relate to the Conitel C300 Slave Protocol. The Front Panel
identifier error string ‘C30’ will precede these codes.

Warning Description
C30 001 Unable to Initialise Unit
C30 050 Unable to Lock Configuration
C30 051 Unable to Release Configuration From Lock
C30 062 Corrupt Data Frame (No EOM When Expected)
C30 063 Corrupt Data Frame (Badly Formed Reply)

Conitel C300 Slave Protocol Configuration Guide (DMT V1.12) Page 32 of 32