ADC01-DOC-210 MITS Protocol Technical Manual

Download as pdf or txt
Download as pdf or txt
You are on page 1of 17

MITS Telemetry Protocol Technical

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.

Document Part No: ADC01-DOC-210


Document Revision Level: 09

Copyright © Schneider Electric (Australia) Pty Limited 2009


MITS Telemetry Protocol Technical Manual

Schneider Electric (Australia) Pty Limited.

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.

Source: \VSS2_Products\Documentation\Advanced Controller\ADC01-DOC-210.doc


Public Access: \stdprod\N00\ADC01-DOC-210Rev09.pdf

ADC01-DOC-210 09 ii
MITS Telemetry Protocol Technical Manual

Revision Control

Revision Author Date Comment


R00 LM 21/05/04 Preliminary. Forked from N00-463.doc
R01 CR 2/10/04 Updated for initial ADVC implementation
R02 DPC 28-Apr-2005 Reviewed with LM.
R03 DPC 27-May-2005 Reviewed with LM.
R04 DPC 2-Jun-2005 Limit range of daylight saving.
R05 DPC 7-Sep-2005 Adjust default GMT offset
R06 RDM 20-Mar-2006 GMT Offset now a generic controller setting.
Add footnotes to implementation table.
R07 GC 11-Apr-2006 Factory default daylight saving time is 0.0hrs
R08 RDM 22-Aug-2006 Minor corrections.
R09 NCD 8-July-2009 Updated company name, address and phone numbers.

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.

MITS protocol abbreviations:


COS Change Of State
DCP Digital Change Pending
RSF Remote Status Flag
SPU System Powered Up
STI System Time Incorrect

1.3 Password Protection


All MITS Telemetry protocol panel settings require password entry unless described as ‘Display
only’ or otherwise stated.
For more information on operator control panel usage refer to the equipment manual.

1.4 Control Cubicle Software


This document applies to pole top reclosers using an advanced controller with software version of
form A42-01.xx.
To find these pages refer to the main equipment manual.

ADC01-DOC-210 09 1
MITS Telemetry Protocol Technical Manual

1.5 MITS Telemetry Protocol


The version of the MITS Telemetry protocol implemented is described in the following
documents: -
• “MITS Limited Telemetry Format – Technical Manual”, Version R12.
Document No “DM3-FUN-110”, 1990

See also Appendix B MITS Telemetry Implementation Statement


and Appendix C Protocol Implementation Detail.

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.

2.2 MITS Communications


The communications page gives information on the port selected, the state of the protocol and the
particular map used. To get to this page, go to the “Communications Setup” page and select the
MITS protocol. Pressing the Enter key will take you to this page.

-------- MITS COMMUNICATIONS -------S


Port RS232-C RUNNING
MITS Standard ACR

Display Setting Description


Port RS232-C Port Selection
The communication port that the protocol handler is assigned to use.
Range: Protocol NONE, RS232-A, RS232-B, RS232-C, RS232-D, RS-
485, V23
Factory default is RS232-C

ADC01-DOC-210 09 2
MITS Telemetry Protocol Technical Manual

Display Setting Description


INACTIVE Protocol Handler Status
RUNNING Indication of the protocol status.
• INACTIVE means that the protocol handler is either configured as
Protocol NONE or the protocol handler has been assigned to a port
that has already been assigned exclusive use by another application
in the controller or the protocol IO map is invalid.
• RUNNING means that the protocol handler has a valid IO map, has
successfully attached itself to a port and is running normally.
Range: INACTIVE/RUNNING
Display only.
MITS Standard MITS Input/Output Map
ACR Displays the name of the currently loaded protocol configurable
input/output map.
Different IO maps can be created using Configurable Protocol Tool via
WSOS5 and loaded into the controller. If there is no map loaded or the
map is corrupt then an “Invalid Map” message is displayed, load/reload
a valid configurable protocol IO map. Contact the
manufacturer/distributor if “Invalid Map” message persists.
Display only.
Factory default is MITS Standard ACR

See User Manual – Communications Setup.

2.3 MITS Communication Statistics


The communication statistics give communication information, such as bytes being sent and
received. The communication statistics page appears as below:

---- MITS Communication Statistics --S


Tx Count 0 Rx Count 0
Rx CRC Error 0 Rx TO Err 0

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

All of the above counters are zeroed when:


• the controller is reset.
• By pressing Selecting and going to the “Reset Communications Statistics” screen and then
pressing Select again.
• the ‘Reset All’ button is selected in Windows SOS.

2.4 MITS Transmission Data


This page allows the SCADA engineer to determine how the MITS Telemetry protocol handler
transmits/receives the user configurable MITS Telemetry message settings.

------- MITS Transmission Data --------S


Station Addr 5 Addr Mode Normal
COS Scan ON COS Retries 4
Retry Delay 500s Frame TO 5000ms

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”.

2.5 Time Set configuration


The MITS Telemetry protocol handler has provision for converting the Greenwich Mean Time
(GMT) from the master station into local time. The handler will adjust the time the master station
sends if the controllers “GMT Offset” setting has a non-zero value (refer: to the ADVC operations
Manual for further details).

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.

-------- MITS Time Configuration -------S


Daylight Save +1.0hr
Start Day 1 End Day 1
Start Month 10 End Month 3

ADC01-DOC-210 09 6
MITS Telemetry Protocol Technical Manual

Display Setting Description


Daylight Save Daylight Saving
This setting is conditionally added to the time (after GMT offset has
been added) if the incoming Local time is between 00:00:00 on the
start day of the start month and 23:59:59 of the end day of the end
month.
Range: –9.5 hours to 9.5 hours in ½ hour steps.
The factory default is 0 hour.
Start Day 1st Day of Daylight Savings
This setting shows the day of the start month that daylight savings
correction will be applied.
Range: 1 to Max. day of Start Month).
The factory default is 1.
End Day Last Day of Daylight Savings
This setting shows the day of the end month that daylight savings
correction will cease to be applied.
Range: 1 to Max. day of End Month.
The factory default is 1
Start Month Month in Which Daylight Savings Starts
This setting shows the number of the month that daylight savings
correction will be applied.
Range is 1 to 12.
The factory default is 10.
End Month Month in Which Daylight Savings Ends
This setting shows the number of the end month that daylight savings
correction will cease to be applied.
Range: 1 to 12.
The factory default is 3.

ADC01-DOC-210 09 7
MITS Telemetry Protocol Technical Manual

2.6 Database IO Points Map


The controller has a default database of MITS IO points called “MITS Standard ACR” map. If the
user wishes to change the selection of points and/or attributes of a point there is a Protocol I/O
Configuration Tool available.

Figure 1 - WSOS IO ConfigurationTool

Examples of configuration that can be performed per MITS datatype are:


• Digital Information – point selection, enable/disable, and invert logic.
• Analog Information – point selection, scaling, enable/disable, and deadband.
• Digital Output Control - point selection.

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

Appendix A Protocol Timings


Initialisation Time
The protocol handler will not respond to master station requests for several seconds after power
up whilst it waits for the controller database to be initialised and for high priority boot up tasks to
be completed.
Turnaround Time
The turnaround time for the protocol, from the end of receiving a message until the start of the
pre-transmission time, is typically < 30 milliseconds with a range of 5 to 100 milliseconds.

ADC01-DOC-210 09 9
MITS Telemetry Protocol Technical Manual

Appendix BMITS Telemetry Implementation Statement


The subset of the MITS Telemetry implemented in the Advanced Controller is described below.

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.

Data Link Layer


No leading SYN is sent, however the physical layer can be configured to provide pre-amble characters.

Network Layer
MITS Telemetry network layer is fully supported.

Functional Layer

Function
Code Description Support Comment

5 Analogue Unconditional YES Flag support:


• APL = 0 (Not supported)
• RSF=Yes (As required, refer function 52) 1
• HRP=0 (Not supported)
• DCP=Yes (As required) 2
6 Analogue Delta Scan YES Flag support:
• APL = 0 (Not supported)
• RSF=Yes (As required, refer function 52)
• HRP=0 (Not supported)
• DCP=Yes (As required)
7 Digital Unconditional NO
8 Digital Change Only NO
9 High Resolution Event Recording List NO
Scan
10 Digital Change of State Scan NO
11 Digital COS/Time-tagged Scan YES Only “normal digital status module” scanning supported
(ie no time-tagged events)
12 Digital Unconditional YES
13 Analogue No Change Reply YES Flag support:
• APL = 0 (Not supported)
• RSF=Yes (As required, refer function 52)
• HRP=0 (Not supported)
• DCP=Yes (As required)
14 Digital No Change Reply YES Flag support:
• APL = 0 (Not supported)
• RSF=Yes (As required, refer function 52)
• HRP=0 (Not supported)
• DCP=Yes (As required)
15 Control Request Okay YES
16 Freeze/Reset NO
17 POM Type Control YES Module: C1…C5 3

19 DOM Type Control NO


20 Input Point Control NO
21 Raise Lower Type NO

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

23 AOM Type Control NO


27 Change of State Report YES Sending of COS messages only occurs if the master has
not polled (FC 11 or 12) for 10 seconds.
Refer to section 2.4 for enable/disable + number of retries
configuration.
MODULE is always 0.
Flag support:
• APL = 0 (Not supported)
• RSF=Yes (As required, refer function 52) 1
• HRP=0 (Not supported)
• DCP=Yes (As required) 2
30 Control or Scan Request Rejected YES Flag support:
• APL = 0 (Not supported)
• RSF=Yes (As required, refer function 52)
• HRP=0 (Not supported)
• DCP=Yes (As required)
31 Counter Scan NO
35,36,37 Floating Point Scans NO
38 Floating Point O/P Command NO
39 Floating Point COS/Time-tagged Scan NO
40 System SIGNON Control NO
41 System SIGNOFF Control NO
42 System RESTART Control NO
43 System SET DATE and TIME Control YES
50 File Download NO
51 File Upload NO
52 Remote Status Flags Scan YES Supported flags:
• SPU Set on restart, Cleared by a function 52 scan 3
• STI Set on restart, Cleared by a function 43 time
setting
All other flags are zero
60 Low Resolution Event Recording List NO
Scan

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

Appendix CProtocol Implementation Detail

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

Station Modules Point


0x10
Reserved for
0
Broadcast
16 Digital
DIM Status per
Module
1
0x1F
0x20
2

AIM 8 Analog
Channels
3 per Module

: 0xBF
:
0xC0

Limit for Normal


126
Addressing
POM 16 Digital
Controls per
Limit for Extended Module
32767
Addressing

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.

Change of State Processing


The RTU supports the MITS ‘change of state’ as follows:
On setting of the ‘Digital COS Pending’ (DCP) or ‘System Powered Up’ (SPU) flags a COS
message (function 27) is queued for transmission to the master station. The sending of the COS
message is delayed until there has been no master station scan for ten (10) seconds. The message
is further delayed by an additional number of seconds equal to the least significant decimal digit
of the RTU address, this is to reduce collisions between stations.

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

You might also like