TL-407 Harris 5000-6000 Scan Task User's Guide

Document Number: TL-407
Windows SCADA
Harris 5000/6000 Scan Task
User’s Guide
____________________________________________
January 18, 2010
This manual describes the functionality and data entry requirements for
the Harris 5000/6000 scan task used in the Windows SCADA system.
Survalent Technology Corporation

Mississauga, Ontario
Copyright © 2007 – 2010 Survalent Technology Corporation
All rights reserved.
Harris 5000/6000 Scan Task User’s Guide
Survalent Technology Corp.

2600 Argentia Road
Mississauga, Ontario
L5N 5V4
TEL (905) 826 5000
FAX (905) 826 7144
The software described in this document is furnished under

license, and may only be used or copied in accordance with
the terms of such license.
The content of this manual has been carefully checked for accuracy. However, if you find
any errors, please notify Survalent Products Corporation.
Revisions
Date Description
August 23, 2005 Initial version.
April 11, 2006 Added RTU configuration switches to specify port counts.
September 7, 2006 Removed alarm when switching the communication port.
March 9, 2007 Added communication line switch /ForceCtl (section 3.1.5, Configuration Switches).
January 18, 2010 Added RTU configuration switch "StChgChk" (section 4.1.6, Switches).
Contents
1 Introduction 1-1
2 Operation of Scan Task 2-1

2.1 Introduction .................................................................................................................................... 2-1
2.2 Initialization.................................................................................................................................... 2-2
2.2.1 Time Synchronization ................................................................................................................. 2-2
2.2.2 All-Data Poll ............................................................................................................................... 2-2
2.3 Normal Polling ............................................................................................................................... 2-2
2.4 Status Changes................................................................................................................................ 2-3
2.5 Sequence Of Events........................................................................................................................ 2-3
2.6 All-Data Poll................................................................................................................................... 2-3
2.7 Accumulators.................................................................................................................................. 2-4
2.8 Time Synchronization..................................................................................................................... 2-4
2.9 Control ............................................................................................................................................ 2-4
2.10 Quality Codes.............................................................................................................................. 2-5
2.11 Communication Errors................................................................................................................ 2-5
2.12 Port Switching............................................................................................................................. 2-5
3 Communication Line 3-1

3.1 Communication Line Data Fields—General .................................................................................. 3-1
3.1.1 Protocol ....................................................................................................................................... 3-2
3.1.2 Auto Start .................................................................................................................................... 3-2
3.1.3 Associated Points ........................................................................................................................ 3-3
3.1.4 Polling Parameters ...................................................................................................................... 3-4
3.1.5 Configuration Switches............................................................................................................... 3-4
3.2 Communication Line Data Fields—Channel.................................................................................. 3-5
3.2.1 Network....................................................................................................................................... 3-5
3.2.2 Mode ........................................................................................................................................... 3-6
Harris 5000/6000 Scan Task User’s Guide Contents i

Windows SCADA
3.2.3 Time Between Scans................................................................................................................... 3-6
3.2.4 Short Response Timeout ............................................................................................................. 3-7
3.2.5 Long Response Timeout ............................................................................................................. 3-7
3.2.6 DLL Short Response Timeout .................................................................................................... 3-7
3.2.7 DLL Long Response Timeout .................................................................................................... 3-7
3.2.8 Error Recovery Time .................................................................................................................. 3-7
3.2.9 Idle Time..................................................................................................................................... 3-7
3.2.10 Poll Retry Count ......................................................................................................................... 3-7
3.2.11 Interleave Factor ......................................................................................................................... 3-7
3.2.12 Dial-Up ....................................................................................................................................... 3-7
3.2.13 Port Parameters ........................................................................................................................... 3-8
4 RTU 4-1
4.1 RTU Data Fields—General ............................................................................................................ 4-1
4.1.1 RTU Address .............................................................................................................................. 4-2
4.1.2 Network ...................................................................................................................................... 4-2
4.1.3 Scout ........................................................................................................................................... 4-2
4.1.4 Status Point ................................................................................................................................. 4-3
4.1.5 Fast Scan Point............................................................................................................................ 4-3
4.1.6 Switches ...................................................................................................................................... 4-3
4.2 RTU Data Fields—Connections..................................................................................................... 4-4
4.2.1 Host Name .................................................................................................................................. 4-5
4.2.2 Host Port ..................................................................................................................................... 4-5
4.2.3 Dial-up ........................................................................................................................................ 4-5
4.2.4 RTU Data Fields—Switches....................................................................................................... 4-5
4.2.5 Port Switch Point ........................................................................................................................ 4-6
4.2.6 Switch Port after ......................................................................................................................... 4-6
4.2.7 Channel Switch Point, Switch Channel after .............................................................................. 4-7
4.3 RTU Data Fields—Statistics .......................................................................................................... 4-7
4.3.1 Percentage Communication Point............................................................................................... 4-7
4.3.2 Total Message Count .................................................................................................................. 4-8
4.3.3 Good Message Count.................................................................................................................. 4-8
4.3.4 Bad Message Count .................................................................................................................... 4-8
4.3.5 Timeout Count ............................................................................................................................ 4-8
4.3.6 Send Message Count................................................................................................................... 4-8
4.3.7 Dial-up Override Interval............................................................................................................ 4-9
4.3.8 Dial-up Status ............................................................................................................................. 4-9
4.3.9 Time of Last Good Poll .............................................................................................................. 4-9
4.4 RTU Data Fields—Scout................................................................................................................ 4-9
5 Status Point 5-1

5.1 Telemetry........................................................................................................................................ 5-2
5.1.1 Telemetry Address ...................................................................................................................... 5-2
5.2 Input Format Code.......................................................................................................................... 5-3
5.3 Control............................................................................................................................................ 5-6
Harris 5000/6000 Scan Task User’s Guide Contents ii

Windows SCADA
5.3.1 Control–0, Control–1 .................................................................................................................. 5-6
6 Analog Point 6-1

6.1 Telemetry Address.......................................................................................................................... 6-2
6.2 Accumulators.................................................................................................................................. 6-3
6.2.1 Derived Accumulations............................................................................................................... 6-3
6.3 Input Format Code.......................................................................................................................... 6-3
6.4 Scale Factor and Offset................................................................................................................... 6-3
6.5 Zero Clamp Deadband.................................................................................................................... 6-4
6.6 Setpoints ......................................................................................................................................... 6-4
7 Monitoring Communication 7-7

7.1 Monitoring Harris 5000/6000 ......................................................................................................... 7-8
8 Device Profile Document 8-1
Harris 5000/6000 Scan Task User’s Guide Contents iii

Windows SCADA
1 Introduction
This document describes the operation and database requirements of the Harris 5000/6000 scan task in
the Windows SCADA system.
Chapter 2 describes the general operation of the scan task.
Chapters 3 to 6 describe how to define:
• Communication lines
• RTUs
• Status and controls
• Analog points
You can monitor communications between this scan task and your RTUs, using the ScanMon utility. This is
described in chapter 7.
The scan task described in this document conforms to the specifications described in the Harris
5000/6000 documents listed in Table 1-1. Chapter 8 contains a conformance profile for the Harris
5000/6000 scan task.
Table 1-1 Harris 5000/6000 Documents
Document No. Document
34389 XA/21 Harris RTU Communication Protocol Specification
34369 Harris 5000/5500/6000 Functional Interface Requirements Specification
This manual describes the creation of certain items in the Windows SCADA database, namely
communication lines, RTUs, analog and status points. It does so in a way that is specific to the Harris
5000/6000 communication protocol, as implemented by this scan task. For additional information
regarding these database items, and the Windows SCADA database in general, you should refer to the
Harris 5000/6000 Scan Task User’s Guide Introduction 1-1

Windows SCADA
series of documents described in Table 1-2, especially the Point Database Editing Guide. If you have
other scan tasks installed in your system, you should also consult the User’s Guides published for those
scan tasks.
Table 1-2 Windows SCADA Database Documentation

Document
Number Document Name
DB-400 Database Editing Overview
DB-401 Point Database Editing Guide
DB-402 Alarm Database Editing Guide
DB-403 Automation Database Editing Guide
DB-404 Historical Database Editing Guide
DB-405 Report Database Editing Guide
This document assumes you have some familiarity with the protocol involved. Terms specific to the Harris
5000/6000 protocol are used throughout, without defining them. If you need clarification, you may want to
read:
• Your RTU vendor’s protocol documentation
Harris 5000/6000 Scan Task User’s Guide Introduction 1-2

Windows SCADA
2 Operation of Scan Task
2.1 Introduction
The Harris 5000/6000 scan task consists of two layers within a single process:
• Data Transportation layer
This is the lower layer that provides protocol-specific-data transportation service to the application
layer.
• Application layer
This is the upper layer that schedules polling, parses responses from the RTUs, and interfaces to the
rest of the SCADA system.
All message transactions between the mater station and RTU through the scan task are based on a
“master-slave” relationship. This relationship states that RTUs respond to the master station only when
commanded by the master station. The master station will “stop-and-wait” for each RTU response
message or it will time-out before initiating another RTU message transaction. Any RTU command or
response message will be aborted if the RTU receives a new command.
Harris 5000/6000 Scan Task User’s Guide Operation of Scan Task 2-1
Windows SCADA
2.2 Initialization
At startup, and on detection of RTU restart, the scan task performs the following initialization functions:
• Port status poll

• Time synchronization if required
• Disable the automatic freeze operation of each RTU
• All-data poll
2.2.1 Time Synchronization
If the RTU is a Harris 6000 series RTU, the scan task uses the “SOE time synchronization” and “SOE
time adjustment” commands to synchronize the RTU time clock.
If the RTU is a Harris 5000 series RTU, the scan task uses the “Non-SOE time synchronization”
command.
2.2.2 All-Data Poll
To perform an all-data-poll, the scan task uses the “analog data dump” and “status data dump”
commands.
2.3 Normal Polling

The Harris 5000/6000 protocol does not support polling for analog exceptions. The scan task therefore
continuously polls for analog input data by using the analog data dump command. If the RTU has status
exceptions (including both status changes and SOEs) that it wishes to report, it will set flags in the
response messages to the analog data dump commands. The scan task will then poll for status changes
and/or SOEs accordingly, by using separate poll commands.
Periodically, the application level of the scan task:
• issues all-data polls (consisting of analog data dump and status data dump commands in
sequence)
• issues time sync commands (consisting of SOE time sync command plus time adjustment
command for Harris 6000 series RTU, or Non-SOE time sync command for Harris 5000/5500
series RTU)
• issues broadcast freeze commands followed by accumulator polls (i.e. accumulator data dump
commands)
In addition, on request from the operators and application programs, the scan task issues control and set
point commands.
Windows SCADA
2.4 Status Changes
The status changes in the RTU are acquired on an exception basis by use of the Status-Change-Dump
command, which is issued after the RTU reports non-zero number of status changes in response to an
Analog/Accumulator or Status Data Dump command. The status changes in the response message are in
the order of status change occurrence.
2.5 Sequence Of Events

SOE availability is determined by the SOE available indicator returned from performing a Status-Change-
Dump or Accumulator/Analog Data Dump command. The SOE available indicator is set to 1 if one or
more SOE events are available from the RTU. The scan task then acquires the SOE event data either on
a one-at-a-time basis or in sets.
The method of reading SOE data in sets provides a more efficient way to acquire SOE data if a lot of
SOE events happened in a short period of time. However, the RTU will reply null SOE information to a
“Send-Next-SOE-Set” command if the number of available SOE events in the RTU SOE buffer is less
than the SOE-set-size configured in the RTU.
To balance the methods of acquiring SOE data on one-at-a-time and in sets, a configurable parameter,
SOE-set-size (see section 4.1.6, Switches, for more details), is used in the master station to configure the
number of SOE events to be reported in each SOE data poll. This parameter has to be consistent with
that in the RTU.
If the RTU indicates that SOE events are available, the HARRIS 5000/6000 scan task will try “Send-Next-
SOE-Set” command first until all sets are read, and then followed by “Send-Next-SOE-Record” command
for the remaining of the SOE records.
SOE commands are supported only by the Harris 6000 series RTU.
2.6 All-Data Poll

The scan task issues an all-data poll command:
• to each RTU at startup
• to one RTU, in round-robin order, at every all-data poll interval. See section 3.1.4, Polling
Parameters.
• to any RTU that resets
• on request by the operator (via an Activate command directed to the RTU point).
When you trigger an all-data poll by Activating an RTU point, the scan task sets the condition code of all
of the analog and status points on the RTU to telemetry failed (indicated by the letter “F” displayed beside
each point). Then, as the requested values are returned by the RTU, the telemetry failed indicators clear.
Windows SCADA
2.7 Accumulators
At an interval specified by the ACCUMULATOR field of Polling Parameters on the SCADA Explorer, the
scan task broadcasts an “accumulator freeze” command to all RTUs. Because no response is expected
from the broadcast command, the command is broadcast three times to ensure that all RTUs hear the
command.
The accumulator Freeze command is supported only by the Harris 6000 series RTU.
Once the freeze broadcast is accepted (or if the RTU is Harris 5000/5500 series RTU), it is followed by an
accumulator poll. An accumulator poll consists of the accumulator data dump command.
For each accumulator value returned, the scan task computes and scales the delta, and either stores the
scaled delta into the assigned database point or adds it to the assigned database point, depending on the
point’s input format code.
Because of the required periodicity of the updates of these points, the scan task discards any values
received for these points in any messages other than these accumulator polls.
If an accumulator poll fails, the scan task updates the accumulator points on that RTU using a delta value
of zero.
2.8 Time Synchronization

If the communication line has been identified as having RTUs that require periodic time sync (see section
3.1.4, Polling Parameters), then depending upon the RTU type configured in the communication line, the
scan task periodically sends a SOE-time-sync-command together with a SOE-time-adjustment command
to each Harris 6000 series RTU, or it sends a Non-SOE-time sync command to each series 5000/5500
RTU. If both a primary and an alternate port are defined, the time sync is broadcast to the current active
port. Selecting of active port is done automatically. (See section 2.12, Port Switching.)
The interval at which time syncs are broadcast is specified by the TIME SYNC INTERVAL field of Polling
Parameters on the Scada Explorer. See section 2.7, Accumulators.
The present SOE-Time-Adjustment amount for Harris 5000/6000 scan task is the idle time (see section
3.2.9, Idle Time) plus 100ms of RTU response delay of SOE-Time-Sync command (see page 5 of
protocol document number 34389 for more details).
2.9 Control
On a control operation, the scan task first places the RTU on fast scan, which means that after every Nth
poll, the data link layer of the scan task will re-poll the RTU on fast scan. This is so that any status
changes as a result of the control about to be performed can be reported as quickly as possible. The
parameter N, called the interleave factor, can be set via the Channel Configuration editor. See section
3.2, Communication Line Data Fields—Channel.
Next, the appropriate sequence of control messages is transmitted to the RTU. The Harris 5000/6000
protocol only supports select-before-operate control for trip/close or setpoint control. The scan task first
issues a select request. On reception of the select checkback, the scan task then issues the execute
command and expects an execute checkback from the RTU.
Windows SCADA
If the scan task does not receive a select or execute checkback within a response timeout, it declares a
checkback timeout.
After the control is complete (meaning that the expected status change was either received or timed out),
the scan task takes the RTU off fast scan.
Besides, the Harris 5000/6000 protocol and therefore the scan task also only supports direct-control for
Raise/Lower control.
2.10 Quality Codes

Quality codes received from the RTU are processed as shown in Table 2-1. An alarm is raised and
cleared on each point of the port when the port status returned indicates that the port goes into or out of
the off-line or message-fail status.
Table 2-1 Processing of Quality Codes

Quality Code Processing
Off Line Point value is NOT updated.
Condition code is set to telemetry failed “F”.
Message Fail Point value is NOT updated.
Condition code is set to telemetry failed “F”.
2.11 Communication Errors

The scan task normally polls the RTUs in round-robin order.
On a poll error, such as a timeout or a message security error, the scan task places the RTU on “error
scan”. This means that it re-polls the RTU that had the communication error after every Nth normal poll,
where “N” is a user-settable interleave factor that is usually set to one or two (see section 3.2,
Communication Line Data Fields—Channel). The RTU is maintained on error scan until a good response
is received or until the retry count expires, whereupon the RTU is declared failed.
Failed RTUs continue to be polled, but less frequently. On each round-robin poll sequence, only one failed
RTU is polled.
2.12 Port Switching

Two communication ports may be specified in the definition of a communication line, or two connections
may be specified in the definition of an RTU. In either case, the scan task will switch to the alternate
connection whenever communication on the primary one fails. In such as case, an RTU will be marked as
Failed only if communication on both primary and alternate ports fails. A separate port switch status point
is used for each RTU, to indicate which port is currently in use when communicating with that RTU. See
section 3.1.3, Port Parameters, and section 4.2.5, Port Switch Point.
This feature may be used to make use of redundant terminal servers and/or redundant communication
lines, or to implement a fault-tolerant “looped” communication line. In the latter case, a break in the line
Windows SCADA
would cause the scan task to poll the RTUs on one side of the break using one port, and poll the RTUs on
the other side of the break using the other port. The advantage of such an arrangement is that a single
break in the communication line causes no loss of communication with any RTU.
Windows SCADA
3 Communication Line
This chapter describes how to define a communication line for the Harris 5000/6000 scan task. You
should be familiar with the discussion of communication lines in DB-401, Point Database Editing Guide
before proceeding. In this document, only the items that are specific to the Harris 5000/6000 scan task
are discussed in detail.
The SCADA Explorer is used to create or modify a communication line’s definition. The dialog box that
allows you to do that has several tabs, each of which includes different data. You will normally begin on
the General tab, which is illustrated in Figure 3-1.
3.1 Communication Line Data Fields—General

The discussion below contains information that is particular to the Harris 5000/6000 scan task. The fields
mentioned can be found on the General tab of the Edit Communication Line dialog that you call up using
the SCADA Explorer. For more information on fields
not detailed here, refer to DB-401, Point Database After creating or changing a communication
Editing Guide. If you need more information about the line definition, or editing the telemetry
SCADA Explorer, see DB-400, Database Editing address of any points on the
Overview. communication line, remember to come
back to this dialog to build the scan table.
Harris 5000/6000 Scan Task User’s Guide Communication Line 3-1

Windows SCADA
Figure 3-1 Edit Communication Line Dialog (General)
3.1.1 Protocol
This is the name that identifies the protocol to be used to communicate with the RTUs connected to this
communication line. For the Harris 5000/6000 scan task, choose the name Harris 5000/6000 from the
drop-down list.
3.1.2 Auto Start
Set this flag if you want the scan task to start automatically when the SCADA system starts up, either
initially, or as the result of a failover.

Windows SCADA
3.1.3 Associated Points
This area includes fields for the communication status point (which is required) and for six other points.
You must specify points that already exist in the database.
To create the points you could abandon the editing of this communication line, and go to the desired
station in the SCADA Explorer. But you may prefer to temporarily start a second copy of SCADA Explorer,
and use it to create the necessary points.
These associated points must not be telemetered. Their values will be written by the scan task.
Therefore they will not need telemetry addresses of their own. Since they are special in this regard, you
should consider designating separate User Types for these points.
Status Point
The first Associated Point is not optional, and must be a status point. This point will be used by the
scan task to indicate the Up or Down status of the communication line.
The scan task will set the point to its normal state when the communication line is working (i.e. there
is successful communication with at least one RTU), and to the abnormal state when it is failed.
Timeout Point
The Harris 5000/6000 scan task does not make use of this analog point to count timeouts. Instead, it
uses an analog point defined on each RTU to maintain a count of timeouts for each RTU. See
section 4.3.5, Timeout Count.
Bad Messages
The Harris 5000/6000 scan task does not make use of this analog point to count bad messages.
Instead, it uses an analog point defined on each RTU to maintain a count of bad messages for each
RTU. See section 4.3.4, Bad Message Count.
Unexpected Messages
The Harris 5000/6000 scan task does not make use of this analog point to count unexpected
messages.
Channel Switch
The Harris 5000/6000 scan task does not presently support a second communication channel
(although it will switch between two ports defined on a single channel—see below). Do not specify a
point in this field.
Port Switch
The Harris 5000/6000 scan task does not make use of this status point when switching between
ports. Instead, each RTU defines a status point to indicate which port is used to communicate with
that RTU. See 4.2.5, Port Switch Point.

Windows SCADA
Current RTU
The Harris 5000/6000 scan task does not make use of this analog point.
3.1.4 Polling Parameters
Various timers are specified to control the rate of certain events. Integrity (all-data) polls, accumulator
(integrated total) polls, and time synchronization commands are described in more detail in sections 2.6,
All-Data Poll, 2.7, Accumulators, and 2.8, Time Synchronization.
All Data
This is the field that specifies an all-data poll interval (in seconds). You should use this to specify how
frequently you want all-data polls on this communication line. Remember that only one RTU will
receive an all-data poll at each All Data poll interval.
Accumulator
This field specifies the interval between Accumulator Freeze commands (which precede each poll for
frozen data). If you want to retrieve frozen counters from any RTUs on this communication line, you
must define this interval.
Hourly Offset
You may offset the Accumulator polls (above) from the “top of the hour” by entering the desired
number of seconds here. Otherwise, an accumulator poll will be issued at the top of each hour, and at
the specified Accumulator interval thereafter.
Time Sync Interval

If any RTUs on this communication line require periodic synchronization of their clocks, you must
specify the TimeSync configuration switch (see section 3.1.5, Configuration Switches). Then you
must enter the desired period here. Otherwise, time sync commands will only be sent to RTUs that
request them.
In many instances, sending time sync messages to the RTUs as they request them will be sufficient.
No periodic “all stations” time sync messages will be needed, and you can leave this field blank.
Demand Averaging Interval

This field is not used by Harris 5000/6000 scan task.
3.1.5 Configuration Switches
This field allows you to specify certain “command line” switches to control the behavior of the scan task.
The switches supported by the Harris 5000/6000 scan task are described below. Specify each switch you
need by entering /name=value in this field. You do not need to add a space or punctuation (other than
the “/”) between switches.

Windows SCADA
/TMSYNC
This switch should be set to 1 if the periodic time sync is required, 0 if not.
/ForceCtl
This switch, when set to 1, causes a digital control command be sent to the RTU even when the RTU
is down. This is a useful feature for communication lines with poor communications.
• The select command is retried up to the user-defined number of retries. However, the operate
command is sent just once.
• If the RTU is manually set to down, the control is not issued even if the /ForceCtl switch is set to
1.
• The /ForceCtl switch does not apply to setpoint controls. Setpoints are not issued if the RTU is
down.
• The default value of this switch is 0 (i.e. don’t issue controls when the RTU is down).
/Log
The Log option specifies the scan task is to log communications to a file. The file will be created in the
folder specified when Windows SCADA was installed; the default folder is C:\Program
Files\Quindar\ScadaServer. The file name is comprised of the protocol name, the communication line
id and the current date. For example, a file from communication line 4 on May 18, 2005 would be
HARRIS4-2005-5-18.log.
The valid values for this option are:

• hex – Log all communication, including raw data in hexadecimal form
• errors – Log only communication errors
• debug – similar to “hex”, with additional details
• all – Log all communication
The logging that you will find in this file is the same as the logging that is displayed by the ScanMon
utility.
3.2 Communication Line Data Fields—Channel

The Channel tab on the Edit Communication Line dialog (see Figure 3-2) contains the data fields
discussed below. Fields that have a generic purpose, not specific to the Harris 5000/6000 protocol, are
not described in this document. Please refer to DB-401 Point Database Editing Guide.
3.2.1 Network
This specifies the type of communication network to be used. Choose COMM for communication lines
that will communicate directly through a serial port on the SCADA host (i.e. a COM port known to
Windows). Choose TCP/IP for all connections that rely on the TCP/IP network, such as serial ports on
terminal servers. Choose Use RTU only if you will be specifying the connection information individually for
each RTU (for example, if each RTU has its own IP address). Refer to DB-401 Point Database Editing
Guide for more detail.

Windows SCADA
3.2.2 Mode
This is a drop-down list that can be set to either Poll or Quiescent. If Poll is chosen, the scan task
performs regular round-robin exception polling. Quiescent means the scan task does not poll, but accepts
unsolicited messages from the RTUs.
The Harris 5000/6000 protocol does not support Quiescent mode. Therefore select Poll mode only.
3.2.3 Time Between Scans
This parameter specifies the time to wait (in milliseconds) between each poll, when operating in Poll
mode.
Figure 3-2 Edit Communication Line Dialog (Channel)

Windows SCADA
3.2.4 Short Response Timeout
This is not used by the Harris 5000/6000 scan task.
3.2.5 Long Response Timeout
This parameter specifies the time to wait, in milliseconds, for a complete response from the RTU. The
time includes the transmission time of the request itself.
3.2.6 DLL Short Response Timeout
3.2.7 DLL Long Response Timeout
3.2.8 Error Recovery Time
3.2.9 Idle Time
This specifies the minimum time delay, in milliseconds, that the scan task is to execute between all
transmissions on this communication line.
3.2.10 Poll Retry Count
This field contains the number of times the scan task is to retry polling an RTU that is not responding,
before giving up and declaring the RTU failed. If omitted, the scan task defaults to three retries.
3.2.11 Interleave Factor
This parameter specifies how often the scan task is to interrupt its normal round robin polling to perform a
fast-scan poll or a retry after error. If the interleave factor is 2, for example, then the scan task will check
for fast scan or error retry requirements after every 2 normal polls.
3.2.12 Dial-Up
Dial-up communication lines are not presently supported by the Harris 5000/6000 scan task.

Windows SCADA
3.2.13 Port Parameters
The communication channel provides for two communication ports. If information is provided for both
ports, the scan task can switch from one to the other if communication using the first port is not
successful. Normally, at least one port is required to create a functional communication line (except when
connections are defined for each RTU, as described in section 4.2, RTU Data Fields—Connections).
Each port corresponds to a physical or logical connection from the host computer to the communication
medium. The type of Network (see section 3.2.1, Network) determines how these fields are used. For
COMM networks, the port means a serial port attached to the host computer. For TCP/IP networks, a
port might mean a serial port on an external terminal server.
Refer to DB-401 for a detailed discussion of the Port Parameters that are not described here.
Host Name
For RS232 communication lines, this must be the name that identifies the serial port, in the form
COMn, where n is a unique number. This is the same name that Windows knows the port by.
For TCP/IP communication lines, this will usually be the name that identifies the other device that we
are communicating with over the network. It may be the RTU itself, or more commonly, a terminal
server. Alternatively, it may be a fixed IP address of the form nnn.nnn.nnn.nnn.
Host Port
For a TCP/IP connection, there will be a TCP/IP port number that must be entered here. For terminal
servers, the port number of the desired serial port should be entered. Consult the terminal server
documentation to determine which port numbers to use.
Baud Rate, Parity

Select from the available choices for baud rate and parity (this is not applicable to TCP/IP
connections or terminal server ports). Note that the hardware you are using (modem, radio, RTU,
etc.) must support the chosen speed as well.
Keying, Keyup Delay

The Harris 5000/6000 scan task does not presently support carrier keying, except by using an external
Port Transfer Module (PTM). The PTM must be configured to buffer the outgoing message and assert
RTS at the required time. This action is transparent to the scan task, so leave this field set to <None>.
Retry Count
This field contains the number of times the scan task is to retry polling an RTU that is not responding,
before switching to the other port (if one has been defined).
To set the number of tries the Harris 5000/6000 scan task makes before switching ports, specify a
value in the definition of each RTU on this communication line. See section 4.2.6, Switch Port after.

Windows SCADA
4 RTU
This chapter describes how to define an RTU for the Harris 5000/6000 scan task. Only the items that are
specific to the Harris 5000/6000 scan task are included in this discussion.
The SCADA Explorer is used to create or modify an RTU’s definition. The dialog box that allows you to do
that has several tabs, each of which includes different data. You will normally begin on the General tab,
which is illustrated in Figure 4-1.
4.1 RTU Data Fields—General

The data fields found on the General tab of the Edit RTU dialog are described below.
Harris 5000/6000 Scan Task User’s Guide RTU 4-1

Windows SCADA
Figure 4-1 Edit RTU Dialog (General)
4.1.1 RTU Address
Each RTU must have a unique address on the communication line. RTU addresses do not have to be
assigned sequentially. Enter the actual Harris 5000/6000 address of the RTU here. For the Harris
5000/6000 scan task, the valid range for individual RTU numbers is 1 to 63. The scan task uses RTU
number 0 for messages broadcast to all RTUs.
4.1.2 Network
If you have specified connection information on the communication line (in section 3.2, Communication
Line Data Fields—Channel), then you should set this to Use ComLine. But if your communication line is
set to Use RTU, then you must choose TCP/IP here. This makes the fields on the Connections page
available for you to specify individual connection information for this RTU (see section 4.2, RTU Data
Fields—Connections).
4.1.3 Scout
This field is not used by the Harris 5000/6000 scan task, so leave it unchecked.

Windows SCADA
4.1.4 Status Point
This is the name of a status point that exists in the database. This point will be used by the scan task to
indicate the communication status of the RTU. You must define this point. It is not optional.
4.1.5 Fast Scan Point
This is the name of a status point that can be used as a switch to speed up polling of the RTU. Setting
this point to a value of “1” causes the scan task to place this RTU on “fast scan” (i.e. poll this RTU more
frequently than others, based on the interleave factor). Setting this point to a value of “0” causes the scan
task to take the RTU off fast scan.
If this field is left blank, the RTU will still be fast scanned automatically during control operations, but you
will not be able to initiate fast scan yourself.
4.1.6 Switches
This field allows you to specify certain “command line” switches to control how the scan task deals with
this RTU. The switches that are supported by the Harris 5000/6000 scan task are described below.
Specify each switch you need by entering /name=value in this field. You do not need to add a space or
other punctuation between switches.
/Type
Set this switch to 5000 if the RTU is a Harris 5000 series RTU, or 6000 if it is a Harris 6000 series
RTU. If this switch is not set, the RTU is by default considered as a Harris 6000 series RTU. The scan
task uses this switch to determine which functions are to be supported by the RTU.
/Ports
This switch is used to specify to the scan task the total number of ports that are configured in the
RTU. Set it to the correct number. If this switch is not set, the scan task will not run.
/AnPorts
This switch is used to specify the start and end analog port numbers in the RTU. The format of this
switch is:
/AnPorts=X:Y
where X is the start port number and Y is the end number. X should never be greater than Y, and Y
should never be greater than the total number of the ports specified by the /Ports switch.
/StPorts
This switch is used to specify the start and end status port numbers in the RTU. The format of this
switch is:
/StPorts=X:Y

Windows SCADA
where X is the start port number and Y is the end port number. X should never be greater than Y, and
Y should never be greater than the total number of the ports specified by the /Ports switch.
/SetPointPorts
This switch is used to specify the start and end setpoint port numbers in the RTU. The format of this
switch is:
/SetPointPorts=X:Y
where X is the start port number and Y is the end number. X should never be greater than Y, and Y
should never be greater than the total number of the ports specified by the /Ports switch.
/SOESets
This switch is used to configure the number of SOE records to be returned on each SOE-set poll
request. It has to have the same value as that configured in the RTU.
Set this to n if n SOE events are to be reported from the RTU in one SOE-set poll. If this switch is not
set, the scan task uses 10 as its default value (the same default value as defined in the protocol
document). However, if this switch is set to 0, the scan task will not process SOE events. You can
use a 0 value of this switch to disable the SOE reporting.
/StChgChk
Setting this switch to a value of 1 causes the scan task to unconditionally follow each “Analog Data
Dump” poll by a “Status Change Check” poll. Use this only if the RTU is known to provide unreliable
status change counts in its replies to “Analog Data Dump” polls.
4.2 RTU Data Fields—Connections

This page (see Figure 4-2) provides for one or two communication connections for this RTU, as well as
the configuration of the dial-up modem, if any.
The dial-up parameters will only be available if you have selected a dial-up mode of Scheduled or On
Demand on the communication line that is connected to this RTU (in section 3.2.12, Dial-Up). Only these
modes allow a separate phone number for each RTU.
The connection information will only be available if you have set the Network type to TCP/IP (see section
4.1.2, Network).

Windows SCADA
Figure 4-2 Edit RTU Dialog (Connections)
4.2.1 Host Name
This is the name or IP address that identifies the device that we are communicating with over the network
(e.g. the terminal server or RTU network interface).
4.2.2 Host Port
For a TCP/IP connection, there will be a TCP/IP port number that must be entered here. In a terminal
server, it may correspond to the hardware port on the server (for example, port 2003 might correspond to
the 3rd terminal server port). Port numbers below 1024 are normally not used, since they are reserved for
other well-known protocols used on the network.
4.2.3 Dial-up
Refer to the discussion of Dial-up connection in DB-401, the Windows SCADA Point Database Editing
Guide, in the chapters covering communication lines and RTUs. For those cases where the RTU must
have individual dial-up parameters specified, enter them here.
4.2.4 RTU Data Fields—Switches
This page contains information related to the port-switching feature. You may use the Browse buttons
provided to select a status point for each switch discussed below.

Windows SCADA
Figure 4-3 Edit RTU Dialog (Switches)
4.2.5 Port Switch Point
If this RTU is on a communication line that has two ports defined (section 3.2.13, Port Parameters), or the
RTU is on a TCP/IP network and has two connections specified (section 4.2, RTU Data Fields—
Connections), this status point is required. The point is used to show which port the RTU is currently
being polled on. When the point’s value is 0, the scan task is using the first port. When the status point’s
value is 1, the scan task is using the second port.
Whenever it wants to poll an RTU, the scan task first tries the port currently indicated by the RTU’s port
switch status point. If the poll fails, the scan task places the RTU on “error scan” and retries. If the retry
count expires, the scan task switches to the other port (and sets the RTU’s port switch status point
accordingly). If polling fails there also, after its own retries, the scan task declares the RTU failed, but
continues to poll the RTU, flipping between both ports as described above. The retry count used for port
switching is specified by Poll Retry Count in the definition of the communication line. See section 3.2.10,
Poll Retry Count.
You can force the scan task to either port by manually setting the port switch status point.
The port switch status point may be defined as a non-alarm point if you don’t want to be bothered by
alarms on this point when the scan task is constantly switching ports hunting for a dead RTU.
While the scan task is using one particular port for an RTU, it does not check the other port for availability.
Such checks can be made manually by manually setting the port switch point. If you do this, don’t forget
to remove the manual set, or the scan task will not be able to switch and ports when it needs to. If you
define the port switch point as a control point associated with a dummy scan task, then you don’t have to
worry about manual set. Alternatively, you can automate the forced switching process via a command
sequence.
4.2.6 Switch Port after
Enter the number of consecutive error responses (timeouts, wrong replies, security errors, etc.) that will
be tolerated before the scan task switches from the current port to the other one (if one is defined for the
communication line the RTU is using).

Windows SCADA
4.2.7 Channel Switch Point, Switch Channel after
The Harris 5000/6000 scan task does not presently support channel switching, so leave these fields
blank.
4.3 RTU Data Fields—Statistics

Several point names may be specified on this page, using the browser buttons provided. The function of
these points is described below.
Figure 4-4 Edit RTU Dialog (Statistics)
4.3.1 Percentage Communication Point
This is an analog point to contain a percent active communication statistic (100% means no errors have
occurred). The statistic is calculated by passing 0s and 1s through a low-pass digital filter, where 0 is
input to the filter on a communication error and 1 is input on a communication success. Errors include
timeouts, security (Checksum) errors and wrong replies.
The digital filter consists of:
xi +1 = (K × xi ) + ((1 − K ) × ui )

Windows SCADA
where:
ui is the input to the filter
xi is the filtered output
K is the filter constant
The filter constant used is 0.5.
If this point is not specified, then no percent communication statistic is calculated for this RTU.
4.3.2 Total Message Count
This is an analog point to contain a count of all messages received from this RTU. You can use this, in
comparison with the three counters discussed below, to evaluate the communication with this RTU.
If this field is left blank, the statistic is not maintained.
4.3.3 Good Message Count
This is an analog point to contain a count of correct messages received from the RTU. It is incremented
whenever a correctly formed reply is received, and was expected.
If this field is left blank, this statistic is not maintained.
4.3.4 Bad Message Count
This is an analog point to contain a count of incorrect messages received from the RTU. The bad
message count is incremented whenever an incorrectly formed reply is received (including security
errors), or when the reply was not the one expected (either the RTU number or the function code in the
message was incorrect, for example).
4.3.5 Timeout Count
This is an analog point to contain a count of communication timeout errors (no response errors). The
timeout count is incremented once each time the number of bytes of data from the RTU falls short of the
expected number.
4.3.6 Send Message Count

Windows SCADA
This is an analog point to contain a count of all messages transmitted by the scan task. It is incremented
each time a message is successfully sent.
This will be the total of all polls, control commands, setpoint commands, and broadcasts sent to this RTU.
4.3.7 Dial-up Override Interval
This is not used by the Harris 5000/6000 scan task, so leave this field blank.
4.3.8 Dial-up Status
4.3.9 Time of Last Good Poll
4.4 RTU Data Fields—Scout

This page is available only when the Scout flag on the General page is checked (see section 4.1.3,
Scout). The Harris 5000/6000 scan task does not use the information contained in this tab.

Windows SCADA
5 Status Point
This chapter describes how to define status points on the Station Editor for the Harris 5000/6000 scan
task. The Edit Status Point dialog from the SCADA Explorer is illustrated in Figure 5-1.
A status point can be defined to be any one of:
• Indication only
• Control only
• Combined indication and control
depending on whether a telemetry address and any control addresses are specified for it.
Harris 5000/6000 Scan Task User’s Guide Status Point 5-1

Windows SCADA
Figure 5-1 Edit Status Point Dialog (Telemetry)
5.1 Telemetry
This page defines the telemetry address, the two control addresses, and related items. You should
consider the RTU to be part of the telemetry address too, since you may have another point with the
same address on this communication line, although it is on a different RTU.
Consult DB-401, Point Database Editing Guide, for a discussion of the fields not mentioned in this
document, including the External Name and Type.
Each of the three addresses specifies the location of an input or output within the RTU, and is made up of
four fields labeled A, B, C, and D. These fields represent different things in each type of address.
5.1.1 Telemetry Address
The telemetry address specifies the location of the status point within the RTU. The meaning of the parts
of the address is given in Table 5-1. If this point is to be a telemetered point, select the RTU that will
provide the data, tick the checkbox for Telemetry Address, and fill in the required A, B, C, and D fields.

Windows SCADA
Table 5-1 Status Telemetry Address Fields
Telemetry
Address
Field Meaning
A Port number (0 – 15)
B Point type
= 1 if 16 points on the port
C Point number
= 0 – 63 if ordinary point
= 100 if port-online/offline-indication point
= 101 if port-power-off-indication point
D 0 (not used)
5.2 Input Format Code

This field specifies how the scan task should process the status input data from the RTU.
Below, the formats are referred to by code (ID) number, but you will select them from a list of user-defined
names. If Harris 5000/6000 is the only scan task on your system, the formats can be given names that
describe their function. But if multiple scan tasks are being
used, they may use the same format numbers for different If you are in doubt about which
purposes, so you may not be able to come up with a better format code is which, look at their
name. In that case you may prefer to name them for the ID definitions using SCADA Explorer.
numbers listed here.
Format Code 1
Format code 1 specifies normal processing of single bits. That is, received bit values of 0 and 1 are
stored in the database as 0 and 1 respectively.
Format Code 2
Format code 2 specifies inverted single bit processing. That is, received bit values of 0 and 1 are
stored in the database as 1 and 0 respectively.
Format Codes 3, 4, 5 and 6
These format codes allow dual-bit status points from the RTU to be mapped in four different ways into
a consistent internal database representation. The internal representation is shown in the table
below:

Windows SCADA
Table 5-2 Standard Status Values
Status
Value State
0 Open
1 Closed
2 Transition
3 Error
Note that if any read response (whether exception or all-data) reports both bits of a dual-bit point as
changed, then there will be two transitions recorded for the point.
Format Code 3
This format code specifies “low bit on = open” and “high bit on = closed”. When both bits are off, the
point is in transition.
Table 5-3 Format Code 3 Raw Bits to Database Mapping

Binary
Value Value
From Stored in
RTU Database State
00 2 Transition
01 0 Open
10 1 Closed
11 3 Error
Format Code 4
This format code specifies “low bit on = closed” and “high bit on = open”. When both bits are off, the
point is in transition.

Binary
Value Value
From Stored in
RTU Database State
00 2 Transition
01 1 Closed
10 0 Open
11 3 Error

Windows SCADA
Format Code 5
This is equivalent to format 2 inverted. It specifies “low bit off = closed” and “high bit off = open”.
When both bits are on, the point is in transition.

Binary
Value Value
From Stored in
RTU Database State
00 3 Error
01 0 Open
10 1 Closed
11 2 Transition
Format Code 6
This is equivalent to format 4 inverted. It specifies “low bit off = open” and “high bit off = closed”.
When both bits are on, the point is in transition.

Binary
Value Value
From Stored in
RTU Database State
00 3 Error
01 1 Closed
10 0 Open
11 2 Transition
Format 7
Format 7 specifies pass-through processing for dual-bit points. Both bits received from the RTU are
stored into the database as is.

Binary
Value Value
From Stored in
RTU Database State
00 0 Open
01 1 Closed
10 2 Transition
11 3 Error

Windows SCADA
Format 8
Format 8 specifies inverted pass-through processing for dual-bit points. Both bits received from the
RTU are complemented and then stored into the database as is.

Binary
Value Value
From Stored in
RTU Database State
00 3 Error
01 2 Transition
10 1 Closed
11 0 Open
5.3 Control
5.3.1 Control–0, Control–1
The open (0) and close (1) control addresses that can be defined for each status point give the location of one
or two control relays in the RTU. The meaning of the parts of each address is given in Table 5-9. You must tick
the checkbox next to any address you intend to use.
Table 5-9 Control Address Fields

Telemetry
Address
Field Meaning
B Control type
= 1 if trip control
= 2 if close control
= 3 if raise/lower control
C Point number (0 – 31)
D Raise or lower duration if Raise/Lower control (see Table 5-10).
Otherwise, zero

Windows SCADA
Table 5-10 D Field – Raise/Lower Durations
D Field Value Duration D Field value Duration
0 No Operation 16 Lower 1.6 sec
1 Raise 0.1 sec 17 Lower 1.5 sec

Windows SCADA
6 Analog Point
This chapter describes how to define analog points for the Harris 5000/6000 scan task. The Edit Analog
Point dialog from the SCADA Explorer is illustrated in Figure 6-1.
Accumulators and setpoints (analog outputs) should be defined as analog points.
Figure 6-1 Edit Analog Point Dialog
Harris 5000/6000 Scan Task User’s Guide Analog Point 6-1

Windows SCADA
6.1 Telemetry Address
The telemetry address specifies the type and location of the point within the RTU. It is made up of four
fields labeled A, B, C, and D. You should consider the choice of RTU to be part of the telemetry address
as well, since you may have another point with the same address on this communication line, so long as
it is on a different RTU.
The meaning of the parts of the address is given in Table 6-1. If this point is to be a telemetered point,
tick the checkbox for Telemetry Address, select the RTU that will provide the data, and fill in the required
address.
Table 6-1 Analog Telemetry Address Fields

Telemetry
Address
Field Meaning
B Point type (see Table 6-2)
D 0
Table 6-2 Point Type Codes
Point Type Meaning

11 Analog point (12 bits)
12 12-bit accumulator point
15 Set-point
201 Total accumulation this hour so far
202 Total accumulation this day so far
203 Total accumulation this month so far
205 Total accumulation last hour
206 Total accumulation last day
207 Total accumulation last month

Windows SCADA
6.2 Accumulators
For each counter value returned by the RTU, the scan task computes the delta, scales it (using the scale
factor only), and depending on the point’s assigned input format code, either:
• stores the result directly into the database to produce a “rate”, or

• adds the result to the current value in the database to produce an “accumulation”.
See section 6.3, Input Format Code.
6.2.1 Derived Accumulations
The scan task has the ability to maintain hourly, daily and monthly accumulations. To obtain these
derived accumulations, six additional points can be defined for each accumulator point, with the same
telemetry address as the primary accumulator point but with different “B” (object type) values. See
section 6.1, Telemetry Address. Note that the primary accumulator point has a “B” address of 12, 13 or
14.
Derived accumulations are produced only if the primary accumulator point is assigned format code 1 or 3
(i.e. store rate in database). See section 6.3, Input Format Code.
If you want daily accumulations, both the hourly and daily accumulation points must be defined. Similarly,
if you want monthly accumulations, you must define hourly, daily and monthly accumulation points.
6.3 Input Format Code

This field specifies how the scan task should process the input data from the RTU. Valid format codes for
non-setpoints are listed in Table 6-3. Analog point values should be assigned format code 1 or 2.
Accumulators should be assigned format code 3 or 4.
Table 6-3 Input Format Codes for Analog Points
Code Meaning
1 Scale, clamp to zero if value is within zero-clamp deadband and store in database
2 Scale, clamp to zero if value is within zero-clamp deadband and add to database
3 Calculate delta, scale and store in database
4 Calculate delta, scale and add to database
6.4 Scale Factor and Offset

The scale factor and offset represent the conversion factors for a linear transformation of the RTU’s raw
input values to engineering units.
To determine the appropriate scale factor and offset, you can use the two formulas below:

Windows SCADA
Max engineering value - Min engineering value
(1) Scale Factor = ________________________________________
Max raw value - Min raw value
(2) Offset = Min engineering value - (Scale factor * Min raw value)
where the Max and Min engineering values are the values you want to see, and the Max and Min raw
values are the range of values obtained from the RTU.
Suppose, for example, that you are using a 4-20 ma transducer to measure water level in a reservoir, and
that the RTU’s D/A converter converts this to measured raw values in the range 400 to 2000. If the
minimum and maximum water levels are 100 and 200 meters respectively, then equations (1) and (2)
produce:
200 - 100
Scale Factor = _________ = 0.0625
2000 - 400
Offset = 100 - (0.0625 * 400) = 75.0
You can check your work by using the resulting scale factor and offset to convert a mid-point raw value.
In this case, a mid-point raw value of 1200 scales to the expected engineering value of 150 meters.
6.5 Zero Clamp Deadband

This defines a deadband range of engineering values inside of which an input will be clamped to an
engineering value of zero. This allows you to eliminate noisy readings around the zero mark of the
engineering scale.
The zero clamp deadband is specified in engineering units, and is applied to points with format code 1 or
2 only. See section 6.3, Input Format Code.
You can use this to eliminate the annoying couple of amps or volts that often show up on a dead line
because of sensor noise or slight miscalibration. Or in a pipeline application, you can eliminate extremely
low pressure or flow readings in an empty pipe. For example, if the zero clamp deadband is 3.0, then any
input value which converts to between +3.0 and -3.0 engineering units will be clamped to zero.
6.6 Setpoints
Setpoints are defined as analog points with device class = Set-Point and with the following telemetry
addressing:

Windows SCADA
Table 6-4 Setpoint Control Address Fields
Telemetry
Address
Field Meaning
B Point type =15
D 0

Windows SCADA
7 Monitoring Communication
A client program called ScanMon is provided, which allows you to monitor logging from various programs
within the SCADA system. ScanMon is discussed in detail in SM-400, Survalent SCADA System
Manager’s Guide for Windows.
Once ScanMon is connected to the Harris 5000/6000 scan task for your desired communication line, it
will log all communication with one or all of its RTUs. You can use the information shown in the log to
diagnose communication difficulties you may be having, or to confirm that the SCADA system is receiving
the expected data.
Harris 5000/6000 Scan Task User’s Guide Monitoring Communication 7-7

Windows SCADA
7.1 Monitoring Harris 5000/6000
To connect to the scan task you will need to enter its name when you start logging, as shown in Figure
7-1. Enter the name “Harris”, plus the ID number of the communication line. Both of these pieces of
information can be found on the communication line dialog in the SCADA Explorer.
For example, if your communication line has an internal ID number of 9, then the name you need is
Harris9.
Next, choose exactly what communication you want to monitor. You can specify which RTU you are
interested in, in the RTU Address field, and you can choose the type of information to include in the log
from the drop-down list Log Type.
Figure 7-1 "Start Logging" Dialog
The support for ScanMon built into the HARRIS 5000/6000 scan task includes the log types shown in
Table 7-1. The other choices you may find in the list are not intended for use with this scan task.
Table 7-1 ScanMon Log Types
Log Type ScanMon Function

Default Log each transmitted and received message, formatted for reading.
Hex Log as above, but include a listing of every byte sent or received, in
hexadecimal.
Debug Log as in Hex mode, but with additional decoded details of point values.
Errors Only Only log messages containing errors (e.g. timeouts or security errors).
A sample of typical ScanMon output is shown in Figure 7-2 using Debug logging. (Lines containing “... ...
...” indicate where sections of the log have been removed so that an example of an all-data poll could be
included.)

Windows SCADA
Figure 7-2 ScanMon Output
12:44:27.406 Harris9 <3172>Invalid accumulator interval
12:44:27.578 Harris9 <3172> P--> ["%NORMAL", 3] "Port Status Scan"

45 0C 09
RTU Addr:5 PAR:0 SOM:1
12:44:27.843 Harris9 <3172> P<-- [Success, 10] "Port Status Scan"
05 00 00 00 00 00 00 00 00 05
Port: 0 OL: 0 PF: 0 MF: 0 SOE: 0
12:44:28.359 Harris9 <3172> P--> ["%NORMAL", 8] "RTU Time Sync"

45 11 3A 2E 3E 15 07 2C
Time: 12:44:28:359
12:44:28.562 Harris9 <3172> P<-- [Success, 3] "RTU Time Sync"
05 00 05
OR: 0 LOT: 0
12:44:29.062 Harris9 <3172> P--> ["%NORMAL", 5] "RTU Time Adjustment"

45 13 02 16 02
Time adjustment: 150
12:44:29.265 Harris9 <3172> P<-- [Success, 2] "RTU Time Adjustment"
05 05
12:44:29.781 Harris9 <3172> P--> ["%NORMAL", 4] "Set Accum Frz Interval"

45 18 3F 22
Frz Interval: 63
12:44:29.968 Harris9 <3172> P<-- [Success, 3] "Set Accum Frz Interval"
05 3F 3A
Frz Interval: 63
…………….
12:44:32.031 Harris9 <3172> P--> ["%NORMAL", 3] "Port Status Scan"

4E 0C 02
12:44:32.218 Harris9 <3172> P<-- [Success, 10] "Port Status Scan"
0E 00 00 00 00 00 00 00 00 0E
12:44:32.765 Harris9 <3172> P--> ["%NORMAL", 8] "Non-Soe Time Sync"

4E 17 3A 2E 3F 19 3D 16
Windows SCADA
Time: 12:44:32:765
12:44:32.968 Harris9 <3172> P<-- [Success, 3] "Non-Soe Time Sync"
0E 00 0E
OR: 0 LOT: 0
12:44:33.500 Harris9 <3172> P--> ["%NORMAL", 5] "Data Dump"

4E 00 0A 25 21
Port: 5 Type: AI_12 Points: 10
Port: 6 Type: AI_12 Points: 37
12:44:33.765 Harris9 <3172> P<-- [Success, 100] "Data Dump"
0E 03 08 00 00 01 00 02 00 03 00 04 00 05 00 06 00 07 00 08
00 09 00 00 00 00 01 00 02 00 03 00 04 00 05 00 06 00 07 00
08 00 09 00 0A 00 0B 00 0C 00 0D 00 0E 00 0F 00 10 00 11 00
12 00 13 00 14 00 15 00 16 00 17 00 18 00 19 00 1A 00 1B 00
1C 00 1D 00 1E 00 1F 00 20 00 21 00 22 00 23 00 24 00 00 20
Status Changes: 3 PF:0 MF:0 SOE:1 SQW:0 LOT:0
Port: 5 Type:AI_12 OL:0 PF:0 MF:0
0= 0
1= 64
2= 128
3= 192
4= 256
5= 320
6= 384
7= 448
8= 512
9= 576
Port: 6 Type:AI_12 OL:0 PF:0 MF:0
0= 0
1= 64
2= 128
3= 192
4= 256
5= 320
6= 384
7= 448
8= 512
9= 576
10= 640
11= 704
12= 768
13= 832
14= 896
15= 960
16= 1024
17= 1088
18= 1152
19= 1216
20= 1280
21= 1344
22= 1408
23= 1472
24= 1536
25= 1600
26= 1664
27= 1728
28= 1792
29= 1856
30= 1920
31= 1984
32= 0
33= -64

Windows SCADA
34= -128
35= -192
36= -256
12:44:34.000 Harris9 <3172> P--> ["%NORMAL", 8] "Status Dump"

4E 05 20 00 20 20 20 0B
Port: 0 Type: DI_32 Points: 32
Port: 1 Type: Unknown Points: 0
12:44:34.453 Harris9 <3172> P<-- [Success, 30] "Status Dump"
0E 00 01 02 03 04 05 00 00 01 02 03 04 05 00 00 01 02 03 04
05 00 00 01 02 03 04 05 00 0E
Port: 0 Type:DI_32 OL:0 PF:0 MF:0 SOE:0
0= 0
1= 0
2= 0
3= 0
4= 0
5= 0
6= 1
7= 0
8= 0
9= 0
10= 0
11= 0
12= 0
13= 1
14= 0
15= 0
16= 0
17= 0
18= 1
19= 1
20= 0
21= 0
22= 0
23= 0
24= 0
25= 0
26= 1
27= 0
28= 0
29= 0
30= 1
31= 0
0= 0
1= 0
2= 0
3= 0
4= 0
5= 0
6= 1
7= 0
8= 0
9= 0
10= 0
11= 0
12= 0
13= 1
14= 0
15= 0

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

Windows SCADA
16= 0
17= 0
18= 1
19= 1
20= 0
21= 0
22= 0
23= 0
24= 0
25= 0
26= 1
27= 0
28= 0
29= 0
30= 1
31= 0

45 00 00 00 05
05 03 08 0E
12:44:35.718 Harris9 <3172> P--> ["%NORMAL", 8] "Status Dump"

45 05 20 00 00 00 00 20
12:44:36.390 Harris9 <3172> P<-- [Success, 9] "Status Dump"
05 00 01 02 03 04 05 00 04
0= 0
1= 0
2= 0
3= 0
4= 0
5= 0
6= 1
7= 0
8= 0
9= 0
10= 0
11= 0
12= 0
13= 1
14= 0
15= 0
16= 0
17= 0
18= 1
19= 1
20= 0
21= 0
22= 0
23= 0
24= 0
25= 0
26= 1

Windows SCADA
27= 0
28= 0
29= 0
30= 1
31= 0
…………………..
12:44:39.046 Harris9 <3172> P--> ["%NORMAL", 4] "Status Change Dump"

45 04 03 02
Num of transitions:3
12:44:39.250 Harris9 <3172> P<-- [Success, 9] "Status Change Dump"
05 07 13 07 14 07 15 00 10
Port: 3 Point:19 State: 1

4E 04 03 09
0E 06 13 06 14 06 15 00 1A
12:44:40.515 Harris9 <3172> P--> ["%NORMAL", 4] "SOE Data Acquisition"

45 12 00 17
ExtCode:Send Next SOE Record
12:44:40.718 Harris9 <3172> P<-- [Success, 10] "SOE Data Acquisition"
05 00 01 02 03 04 1D 0F 00 13
PF:0 MF:0 SOE:0 LOT:0
Port:14 Point:15 State:1 Time:0:4:30:532

45 00 00 00 05
05 03 08 0E

45 04 03 02
05 07 13 07 14 07 15 00 10
12:44:42.718 Harris9 <3172> P--> ["%NORMAL", 4] "SOE Data Acquisition"

45 12 00 17
ExtCode:Send Next SOE Record
12:44:42.906 Harris9 <3172> P<-- [Success, 10] "SOE Data Acquisition"

Windows SCADA
05 00 01 02 03 04 1F 10 00 0E
PF:0 MF:0 SOE:0 LOT:0
Port:15 Point:16 State:1 Time:0:4:30:532
…………………………………
12:44:51.937 Harris9 <3172> mail from TSTAT, request 1004 (Output status)
12:44:51.953 Harris9 <3172> P--> ["%NORMAL", 5] "Trip/Close Control Arm"

4E 06 00 25 2D
Port: 0 Point:18 State: Colse
12:44:52.578 Harris9 <3172> P<-- [Success, 4] "Trip/Close Control Arm"
0E 00 25 2B
12:44:52.609 Harris9 <3172> P--> ["%NORMAL", 5] "Trip/Close Control Operate"

4E 07 00 1A 13
12:44:53.281 Harris9 <3172> P<-- [Success, 2] "Trip/Close Control Operate"
0E 0E
12:44:53.296 Harris9 <3172> sent mail to TSTAT, request 1016 (Checkback success)
…………………………………..
12:44:58.953 Harris9 <3172> mail from TSTAT, request 1004 (Output status)
12:44:58.968 Harris9 <3172> P--> ["%NORMAL", 16] "Raise/Lower Control"

4E 08 02 00 00 00 00 00 00 00 00 06 00 00 00 02
Port: 2
Point: 0 Duration: 0
Point:10 Duration: 0
Point:11 Duration: 0
12:44:59.250 Harris9 <3172> P<-- [Success, 2] "Raise/Lower Control"
0E 0E
12:44:59.312 Harris9 <3172> sent mail to TSTAT, request 1016 (Checkback success)
……………………………
12:45:03.203 Harris9 <3172> P--> ["%NORMAL", 3] "Broadcast Accum Frz"
40 0F 0F

40 0F 0F

40 0F 0F

4E 04 03 09

Windows SCADA
0E 06 13 06 14 06 15 00 1A

45 00 00 00 05
05 03 08 0E
Notes:
• The scan tasks only log to the destination specified by the most recent ScanMon command. If
you, for example, start a ScanMon at your computer, and then someone else starts a ScanMon at
another computer, the output in your window will stop.
• On a scan table rebuild, the scan task process stops and restarts. Any ScanMon that was
previously going on will stop. If you wish to continue monitoring, you will need to start logging
again.

Windows SCADA
8 Device Profile Document
This chapter contains the conformance profile of the Windows SCADA implementation of the Harris
5000/6000 scan task.
In the conformance table that starts on the next page, each option that is supported by the present
implementation of the Harris 5000/6000 scan task is checked.
Harris 5000/6000 Scan Task User’s Guide Device Profile Document 8-1
Windows SCADA
1. NETWORK CONFIGURATION
Point-to-Point Multipoint-Partyline
Multiple Point-to-Point Multipoint-Star
2. PHYSICAL LAYER
Transmission Speed (Control direction)

2400 bit/s 56000 bit/s
4800 bit/s 64000 bit/s
9600 bit/s
19200 bit/s
38400 bit/s
Transmission Speed (Monitor direction)

2400 bit/s 56000 bit/s
4800 bit/s 64000 bit/s
9600 bit/s
19200 bit/s
38400 bit/s
Windows SCADA
3. APPLICATION LAYER
Selection of Standard Op-Code

Op-Code Defination Harris RTU Series
<00 hex> Analog/Accumulator Data Dump & Status Check 5000/5500/6000
<01 hex> Future Op-Code
<03 hex> Status Change Check 5000/5500/6000
<04 hex> Status Change Dump 5000/5500/6000
<05 hex> Status Dump 5000/5500/6000
<06 hex> Trip/Close Control Point Arm 5000/5500/6000
<07 hex> Trip/Close Control Point Operate 5000/5500/6000
<08 hex> Raise/Lower Control 5000/5500/6000
<09 hex> Set Point Control Arm 5000/5500/6000
<0A hex> Set Point Control Operate 5000/5500/6000
<0B hex> Power Fail Reset 5000/5500/6000
<0C hex> Port Status Scan 5000/5500/6000
<0D hex> Future Op-Code
<0E hex> Future Op-Code
<0F hex> Broadcast Accumulator Freeze 6000 Series Only
<10 hex> Select Data Freeze 6000 Series Only
<11 hex> RTU SOE Time Synchronization 6000 Series Only
<12 hex> SOE Data Acquisition & SOE Queue Control 6000 Series Only
<13 hex> RTU SOE Time Adjustment 6000 Series Only
<16 hex> RTU Data Message 6000 Series Only
<17 hex> RTU Non-SOE Time Synchronization 5000 Series Only
<18 hex> Set Accumlator Freeze Interval 6000 Series Only
... ............... ........................
<3F hex> Future Op-Code
Windows SCADA

TL-407 Harris 5000-6000 Scan Task User&#39;s Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TL-407 Harris 5000-6000 Scan Task User&#39;s Guide

Uploaded by

Copyright:

Available Formats

Document Number: TL-407

January 18, 2010

Survalent Technology Corporation

All rights reserved.

Harris 5000/6000 Scan Task User’s Guide

Survalent Technology Corp.

TEL (905) 826 5000

FAX (905) 826 7144

The software described in this document is furnished under

September 7, 2006 Removed alarm when switching the communication port.

2 Operation of Scan Task 2-1

3 Communication Line 3-1

Harris 5000/6000 Scan Task User’s Guide Contents i

5 Status Point 5-1

Harris 5000/6000 Scan Task User’s Guide Contents ii

6 Analog Point 6-1

7 Monitoring Communication 7-7

8 Device Profile Document 8-1

Harris 5000/6000 Scan Task User’s Guide Contents iii

Chapter 2 describes the general operation of the scan task.

Chapters 3 to 6 describe how to define:

Table 1-1 Harris 5000/6000 Documents

Document No. Document

34389 XA/21 Harris RTU Communication Protocol Specification

34369 Harris 5000/5500/6000 Functional Interface Requirements Specification

Harris 5000/6000 Scan Task User’s Guide Introduction 1-1

Table 1-2 Windows SCADA Database Documentation

• Your RTU vendor’s protocol documentation

Harris 5000/6000 Scan Task User’s Guide Introduction 1-2

• Data Transportation layer

• Port status poll

2.2.1 Time Synchronization

2.2.2 All-Data Poll

2.3 Normal Polling

Periodically, the application level of the scan task:

2.5 Sequence Of Events

2.6 All-Data Poll

• to each RTU at startup

• to any RTU that resets

2.8 Time Synchronization

2.10 Quality Codes

Table 2-1 Processing of Quality Codes

2.11 Communication Errors

2.12 Port Switching

3.1 Communication Line Data Fields—General

Harris 5000/6000 Scan Task User’s Guide Communication Line 3-1

3.1.2 Auto Start

Harris 5000/6000 Scan Task User’s Guide Communication Line 3-2

Harris 5000/6000 Scan Task User’s Guide Communication Line 3-3

3.1.4 Polling Parameters

Time Sync Interval

Demand Averaging Interval

3.1.5 Configuration Switches

Harris 5000/6000 Scan Task User’s Guide Communication Line 3-4

The valid values for this option are:

3.2 Communication Line Data Fields—Channel

Harris 5000/6000 Scan Task User’s Guide Communication Line 3-5

3.2.3 Time Between Scans

Figure 3-2 Edit Communication Line Dialog (Channel)

Harris 5000/6000 Scan Task User’s Guide Communication Line 3-6

This is not used by the Harris 5000/6000 scan task.

3.2.5 Long Response Timeout

3.2.6 DLL Short Response Timeout

This is not used by the Harris 5000/6000 scan task.

TL-407 Harris 5000-6000 Scan Task User's Guide

TL-407 Harris 5000-6000 Scan Task User's Guide