ADC01-DOC-210 MITS Protocol Technical Manual
ADC01-DOC-210 MITS Protocol Technical Manual
ADC01-DOC-210 MITS Protocol Technical Manual
Manual
For Automatic Circuit Reclosers
With
ADVC Controller Range
Document Status
Preliminary
Subject to Change
Scope
This document describes the MITS Telemetry protocol and Database Implementation on
Schneider Electric (Australia) Pty Limited Automatic Circuit Reclosers utilising Advanced
controllers.
80 Schneider Road
Eagle Farm 4009
Queensland
Australia.
Tel +61 7 3635 7500
Fax +61 7 3635 7560
LIMITATIONS
This document is copyright and is provided solely for the use of the recipient. It is not to be
copied in any way, nor its contents divulged to any third party, nor to be used as the basis of a
tender or specification without the express written permission of Schneider Electric (Australia)
Pty Limited.
This document discloses confidential intellectual property that belongs to Schneider Electric
(Australia) Pty Limited. This document does not invest any rights to Schneider Electric
(Australia) Pty Limited intellectual property in the recipient. Moreover the recipient is required
not to disclose any of the intellectual property contained in this document to any other party
unless authorised in writing by Schneider Electric (Australia) Pty Limited.
ADC01-DOC-210 09 ii
MITS Telemetry Protocol Technical Manual
Revision Control
ADC01-DOC-210 09 iii
MITS Telemetry Protocol Technical Manual
Contents
1 Introduction..............................................................................................................................1
1.1 Overview......................................................................................................................1
1.2 Terminology.................................................................................................................1
1.3 Password Protection.....................................................................................................1
1.4 Control Cubicle Software ............................................................................................1
1.5 MITS Telemetry Protocol ............................................................................................2
2 Protocol Configuration.............................................................................................................2
2.1 Enabling MITS.............................................................................................................2
2.2 MITS Communications................................................................................................2
2.3 MITS Communication Statistics..................................................................................3
2.4 MITS Transmission Data.............................................................................................5
2.5 Time Set configuration ................................................................................................6
2.6 Database IO Points Map ..............................................................................................8
Appendix A Protocol Timings .............................................................................................................9
Appendix B MITS Telemetry Implementation Statement.................................................................10
Appendix C Protocol Implementation Detail ....................................................................................12
Module Numbering................................................................................................................12
Controls..................................................................................................................................12
Change of State Processing....................................................................................................13
ADC01-DOC-210 09 iv
MITS Telemetry Protocol Technical Manual
1 Introduction
This document describes the MITS Telemetry protocol implementation for the Advanced
Controllers (ADVC). It describes the MITS implementation within the controller and its panel
interface.
For more information about MITS input/output point map, point descriptions and attributes per
point refer to the WSOS5 IO configuration tool and its documentation.
1.1 Overview
The Advanced Controller combines the functions of protection relay and switchgear controller
into a single intelligent electronic device (IED).
The controller provides a user friendly operator interface on a four line LCD control panel that
allows configuration and control of the switchgear.
Electricity supply utilities frequently link the controller into their SCADA systems as a Remote
Terminal Unit (RTU).
To make this simple the controller provides:
• Mounting room for a radio or modem in the control cubicle.
• Power supply for the radio or modem in the control cubicle.
• Embedded protocol handler for the required SCADA protocol in the controller firmware.
1.2 Terminology
The terminology used in this document is that Earth Fault or Ground Fault is described as Earth /
Ground Fault and Sensitive Earth Fault (SEF) or Sensitive Ground Fault (SGF) is described as
SEF/SGF.
Also note that the phase terminology is ABC and refers always to the phase set by the Terminal
Designation or “Phasing” option, never to the physical bushing or terminal on the switchgear.
ADC01-DOC-210 09 1
MITS Telemetry Protocol Technical Manual
2 Protocol Configuration
The MITS Telemetry protocol handler adds several pages to the “MITS Configuration” menus.
The additional pages fall into the following groups:
• Enabling MITS (refer section 2.1)
• MITS Communications (refer section 2.2)
• MITS Communication Statistics (refer section 2.3)
• MITS Transmission Data (refer section 2.4)
• Time Set configuration (refer section 2.5)
All protocol configuration parameters can be viewed, modified and stored on a personal
computer with the WSOS utility.
2.1 Enabling MITS
To use MITS, it must be made available. This can be done in the panel “Options -
Communications” pages, or via WSOS5’s Configuration => Feature Selection.
ADC01-DOC-210 09 2
MITS Telemetry Protocol Technical Manual
Statistic Description
Tx Count Transmission Message Count
The number of messages transmitted from this controller into the
communication link.
Range: 0 to 32768
Rx Count Receive Message Count
The number of messages received by this controller from the
communication link with valid MITS Telemetry encoding and BCH
codes. This includes all messages with incorrect station/group
addressing.
Range: 0 to 32768
Rx CRC Error Receive Message CRC Error Count
The number of message packets received with a CRC error
Range: 0 to 32768
ADC01-DOC-210 09 3
MITS Telemetry Protocol Technical Manual
Statistic Description
Rx TO Error Receive Message Time Out Error Count
The number of messages received which have exceeded the Frame TO
period.
Range: 0 to 32768
ADC01-DOC-210 09 4
MITS Telemetry Protocol Technical Manual
Parameter Description
Station Addr Station Address
Sets the address that is used in all protocol messages to identify the
controller
Range: 1 to 126 (normal addressing)
Or 1 to 32767 (extended addressing)
Factory default is 5
Addr Mode Enable / Disable Extended Addressing
Normal If Normal is set then the address range available to the controller is from 1 to
126.
Extended If Extended is set then the address range available to the controller is 1 to
32767.
Range: Normal, Extended
Factory default is Normal
COS Scan Enable/Disable Change of State Scanning
ON When ON the controller conforms to the Change of State (Func Code 27)
OFF reporting.
When OFF no COS messages are generated.
Range: ON, OFF
Note 1 Factory default is ON
COS Retries Number of attempts for a COS message
Sets the maximum number of times a COS message will be tried. If this count
is exceeded no more COS messages will be sent until the master has scanned
the changes out of the controller. An attempt fails if there is no Master scan
before the COS Retry Delay time expires.
Note 1 Range: 1 to 100
Factory default is 4
ADC01-DOC-210 09 5
MITS Telemetry Protocol Technical Manual
Parameter Description
Retry Delay Time between COS attempts
This is the time that must expire before another attempt to send a COS
message is made. If this time expires then another COS attempt will be
made if all configured attempts have not been exhausted.
Note 1
Range: 1 to 500 seconds
Factory default is 500
Frame TO Frame Timeout
The maximum time after receiving the first byte that the ADVC will wait for
an entire frame from the master station before determining a communication
failure.
Range: 30 to 65535 milliseconds
Factory default is 5000 milliseconds
Note 1. See Appendix C Protocol Implementation Detail for more information on “Change
of State”.
A daylight savings time offset can also be configured to apply between a start and end date. If the
Local time contained in the message from the master station is between 00:00:00 on the start day
of the start month and 23:59:59 on the end day of the end month inclusive then the daylight
savings offset will also be added to the incoming GMT time. GMT offset has a range of +/– 15
hrs in 0.5 hour increments.
The daylight saving offset, start day, start month, end day, and end month can all be set from the
operator control panel.
The following page allows these time parameters be set.
ADC01-DOC-210 09 6
MITS Telemetry Protocol Technical Manual
ADC01-DOC-210 09 7
MITS Telemetry Protocol Technical Manual
For more information refer to the WSOS5 Protocol IO Configuration Tool manual.
For a listing of all controller’s IO that can be mapped, use the Help menu of the WSOS5 Protocol
IO Configuration tool to refer to the ADVC-PTCL-331.html points.
For a listing of the controller’s default IO map refer to the “MITS Standard ACR” map available
with the tool. A legacy “MITS Legacy CAPM2” IO map is also available with the tool, and can be
loaded into the controller to make it look like a CAPM2.
The MITS Standard ACR map reflects points that are available with default settings in the
controller. If a feature is made available via controller configuration change then the user
is required to manually add any related points to the IO list as required.
ADC01-DOC-210 09 8
MITS Telemetry Protocol Technical Manual
ADC01-DOC-210 09 9
MITS Telemetry Protocol Technical Manual
Physical Layer
RS232, V23, and RS485 are supported.
Pre-amble characters, pre transmission and post transmission are configurable.
Address
Both extended and normal address forms are supported.
Network Layer
MITS Telemetry network layer is fully supported.
Functional Layer
Function
Code Description Support Comment
1
RSF Remote Status Flags, when set indicates one of the remote status flags (refer: MITS Technical Manual) has
changed state since the Status Flags were previously scanned.
2
DCP Digital Change Pending, Indicates that a change of state has occurred on a digital module being scanned.
3
POM verification adheres to MITS Rev12 definition.
ADC01-DOC-210 09 10
MITS Telemetry Protocol Technical Manual
Function
Code Description Support Comment
1
RSF Remote Status Flags, when set indicates one of the remote status flags (refer: MITS Technical Manual) has
changed state since the Status Flags were previously scanned.
2
DCP Digital Change Pending, Indicates that a change of state has occurred on a digital module being scanned.
3
SPU System Powered Up, set upon an RTU restart and cleared by a Function-52 scan.
ADC01-DOC-210 09 11
MITS Telemetry Protocol Technical Manual
Module Numbering
The modules within MITS have been given predefined fixed module offsets/addresses.
• Digital Status Modules – start at 0x10, and can go up to 0x1F.
• Analog Modules – start at 0x20, and can go up to 0xBF.
• Digital Control Modules – start at 0xC0, and can go up to 0xFF.
The protocol IO configuration tool will only work within these predefined spaces.
MITS Addressing
AIM 8 Analog
Channels
3 per Module
: 0xBF
:
0xC0
0xFF
Controls
A list of the controls supported by the controller is detailed in the IO configuration tool.
All controls have a corresponding binary status point. The master station must use these status
points to verify that the control action has been successful. Sometimes a control will be rejected
because of an underlying controller condition preventing the action. These conditions are detailed
in the protocol IO configuration tool’s ADVC-PTCL-331.html point list.
The MITS Telemetry protocol handler can trigger two events to be recorded in the controller
event log - “MITS Trip Req” and “MITS Close Req”. This event log reporting indicates only that
the protocol handler has requested a trip or a close from the controller. It does not necessarily
ADC01-DOC-210 09 12
MITS Telemetry Protocol Technical Manual
mean that the action has been taken. As detailed above, the request may be over-ridden by
operational conditions.
The MITS Telemetry protocol handler is designated as a remote user. Refer to the equipment
manual for more information.
Some controls affect the currently active protection group. The change is put into effect
immediately and is permanent for that group. In other words, it is the equivalent to
selecting that protection group on the operator control panel, changing the setting and then
putting the change into service.
All binary/analog output points have a matching binary/analog input status point. It is
recommended that the master station use the control’s corresponding binary/analog input
status to verify the success of an action.
If the RTU receives a digital scan (function type 11 or 12) before the COS message is sent then it
is cleared from the queue and will never be sent.
If the master does NOT scan the RTU within ‘Retry Delay’ seconds of sending the message then
the message is queued for retransmission. In this case however the additional delay is equal to the
second least significant decimal digit of the RTU station address. This sequence is repeated a
maximum of ‘COS Retries’ times.
Reference:
• “MITS Limited Telemetry Format – Technical Manual”, Version R15. Document
“md3telm.doc”, 4th July 1998, section 8.18, page 37 for further ‘COS’ details.
ADC01-DOC-210 09 13