Sei sulla pagina 1di 61

AS 4418.2

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

Australian Standard

AS 4418.2—2000

Reconfirmed 2016

Supervisory control and data

Part 2: Fire alarm systems

acquisition (SCADA)—Generic telecommunications interface and protocol

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

This Australian Standard was prepared by Committee IT/24, Supervisory Control and Data Acquisition (SCADA). It was approved on behalf of the Council of Standards Australia on 17 July 2000 and published on 25 September 2000.

The following interests are represented on Committee IT/24:

Association of Consulting Engineers Australia

Australasian Fire Authorities Council

Australasian Railway Association

Australian Communications Authority

Australian Electrical and Electronic Manufacturers Association

Australian Gas Association

Australian Information Industry Association

Australian Pipeline Industry Association

Australian Security Industry Association Limited

Australian Telecommunications Users Group

AUSTROADS

Cable & Wireless Optus Limited

CIGRE AP35

Electricity Supply Association of Australia

Fire Protection Association Australia

Institution of Engineers Australia

Telstra Corporation Limited

Water Services Association of Australia

Keeping Standards up-to-date

This Standard was issued in draft form for comment as DR 99199.

Standards are living documents which reflect progress in science, technology and systems. To maintain their currency, all Standards are periodically reviewed, and new editions are published. Between editions, amendments may be issued. Standards may also be withdrawn. It is important that readers assure themselves they are using a current Standard, which should include any amendments which may have been published since the Standard was purchased. Detailed information about Standards can be found by visiting the Standards Australia web site at www.standards.com.au and looking up the relevant Standard in the on-line catalogue. Alternatively, the printed Catalogue provides information current at 1 January each year, and the monthly magazine, The Australian Standard, has a full listing of revisions and amendments published each month. We also welcome suggestions for improvement in our Standards, and especially encourage readers to notify us immediately of any apparent inaccuracies or ambiguities. Contact us via email at mail@standards.com.au, or write to the Chief Executive, Standards Australia International Ltd, GPO Box 5420, Sydney, NSW 2001.

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

AS 4418.2—2000 (Reconfirmed) 2016-07-08

STANDARDS AUSTRALIA

RECONFIRMATION

OF

RECONFIRMATION NOTICE

Technical Committee EL-050 has reviewed the content of this publication and in

Certain documents referenced in the publication may have been amended since the

Approved for reconfirmation in accordance with Standards Australia procedures for

The following are represented on Technical Committee EL-050:

Australian Industry Group

AS 4418.2—2000 Supervisory control and data acquisition (SCADA)—Generic telecommunications and interface protocol Part 2: Fire alarm systems

accordance with Standards Australia procedures for reconfirmation, it has been determined that the publication is still valid and does not require change.

original date of publication. Users are advised to ensure that they are using the latest versions of such documents as appropriate, unless advised otherwise in this Reconfirmation Notice.

reconfirmation on 16 June 2016.

Chamber of Commerce and Industry Queensland Energy Networks Association Victoria University

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

NOTES

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

AS 4418.2—2000

Australian Standard

Supervisory control and data

Part 2: Fire alarm systems

Originated as AS 4418.2—1996.

COPYRIGHT

© Standards Australia International

All rights are reserved. No part of this work may be reproduced or copied in any form or by any

Published by Standards Australia International Ltd

ISBN 0 7337 3557 6

acquisition (SCADA)— Generic telecommunications interface and protocol

Second edition 2000.

means, electronic or mechanical, including photocopying, without the written permission of the publisher.

GPO Box 5420, Sydney, NSW 2001, Australia

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

AS 4418.2 — 2000

2

PREFACE

This Standard was prepared by the Standards Australia Committee IT/24 on Supervisory

The objective of this Standard is to provide fire equipment manufacturers and fire alarm

This Standard is consistent with requirements developed by IEC and published in

Other applications which could form further Parts of this series of Standards could cover

Standards Australia/Standards New Zealand Committee FP/2 on Automatic Fire Detection,

The term 'informative' has been used in this Standard to define the application of the

appendix to which it applies.

An 'informative' appendix

is

only for

information and

Control and Data Acquisition as a revision to AS 4418.2 — 1996.

monitoring organizations with a telecommunications protocol for connecting fire alarm systems to monitoring centres, in order to achieve system and equipment interoperability. Other industry groups may also find the requirements applicable. The objective of this revision is to enhance interoperability and to add additional features based on practical implementation of the Standard.

IEC 60870, Telecontrol equipment and systems, the relevant Parts of which have been issued as Australian Standard, AS 60870 of the same name. This Part has been prepared as one of a possible series of Standards for SCADA applications. AS 4418.1 defines the general requirements, including security and addressing, for SCADA networks and this Part is a specific fire alarm monitoring application. The two Parts should be read in conjunction.

areas such as systems for service utilities, transport and security.

Warning and Intercom Systems has prepared a product Standard for alarm signalling equipment designed to utilize this telecommunications protocol, AS 4428.6 Fire detection, warning, control and intercom systems—Control and indicating equipment Part 6: Alarm signalling equipment. In addition, Committee FP/2 has prepared a Standard which specifies minimum alarm monitoring network performance parameters which network designers are able to use to ensure adequate performance of monitored fire alarm systems, AS 1670.3 Fire detection, warning, control and intercom systems — Control and indicating equipment System design, installation, and commissioning Part 3: Monitoring network performance.

guidance.

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

3

AS 4418.2 — 2000

CONTENTS

Page

SECTION 1

SCOPE AND GENERAL

1.1

1.2

1.3

1.4

SCOPE

4

APPLICATION 4

4

SECTION 2

PROTOCOL STRUCTURE

2.1

GENERAL

SECTION 3

PHYSICAL LAYER

3.1

SELECTIONS FROM ISO AND ITU-T STANDARDS

SECTION 4

LINK LAYER

4.1

TRANSMISSION FRAME FORMAT

4.2

SECTION 5

STRUCTURE OF APPLICATION DATA

5.1

GENERAL

SECTION 6

DEFINITION AND CODING OF APPLICATION INFORMATION

6

7

8

9

11

6.1

6.2

6.3

6.4

6.5

6.6

6.7

GENERAL

13

TYPE IDENTIFICATION (Figure 6.1) 13

VARIABLE STRUCTURE QUALIFIER (Figure 6.2) 15

CAUSE OF TRANSMISSION (Figure 6.3)

16

ADDRESS OF ALARM SYSTEM DATA TERMINAL EQUIPMENT (Figure 6.4).18

INFORMATION OBJECT ADDRESS (Figure 6.5) 18

SECTION 7

DEFINITION AND PRESENTATION OF SPECIFIC ASDUs

7.1

7.2

7.3

7.4

7.5

GENERAL

7.6

ASDUs FOR FILE TRANSFER

SECTION 8

BASIC APPLICATION FUNCTIONS

8.1

SELECTIONS FROM AS 60870.5.5

SECTION 9

TRANSMISSION PROCEDURES

9.1

9.2

9.3

9.4

9.5

9.6

GENERAL

APPENDIX A

ALARM SYSTEM DATA TERMINAL EQUIPMENT (DTE)

28

28

30

33

36

41

45

46

46

47

48

49

49

50

REFERENCED AND RELATED DOCUMENTS DEFINITIONS 5

LINK TRANSMISSION PROCEDURES

ELEMENTS

INFORMATION ELEMENTS 19

ASDUs FOR PROCESS INFORMATION IN MONITOR DIRECTION ASDUs FOR PROCESS INFORMATION IN CONTROL DIRECTION ASDUs FOR SYSTEM INFORMATION IN MONITOR DIRECTION ASDUs FOR SYSTEM INFORMATION IN CONTROL DIRECTION

FAS EVENT DTE POWER ON ASE EVENT LINK INTEGRITY CHECKING NOTIFICATION OF LINK FAILURE

FUNCTIONALITY

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

AS 4418.2 — 2000

4

STANDARDS AUSTRALIA

Australian Standard

Supervisory control and data acquisition (SCADA)—Generic

Part 2: Fire alarm systems

SECTION

1.1

SCOPE

1

SCOPE

AND

GENERAL

The purpose of this Standard is to standardize the monitoring of fire alarm systems installed

1.2

APPLICATION

The protocol defined in this Standard is for connection-oriented networks. If a

Whilst this Standard specifies many features and a high degree of functionality, smaller

NOTE: To assist manufacturers to detail the level of functionality available with individual alarm

Whilst this Standard may be more easily implemented using dedicated point-to-point links,

1.3

1.3.1

REFERENCED AND RELATED DOCUMENTS

Referenced documents

The following documents are referred to in this Standard:

AS

1670

1670.3

2484

2484.2

4418

Fire detection, warning, control and intercom systems—System design,

4418.1

© Standards Australia

telecommunications interface and protocol

in remote premises, and connected to a monitoring centre.

connectionless protocol is required, ITU-T Rec.X.400 addressing shall be used. Supervisory control and data acquisition (SCADA) networks for fire alarm monitoring applications shall comply with the relevant parts of AS 4418.1 and this Standard.

lower technology systems can still be accommodated. Most responses from a controlled station allow a particular message from an individual controlled station to not be implemented. This can be used by manufacturers to enable the production of partially functional, yet fully compliant, alarm system DTE. In addition, the text area available for the description of the location of the actuating devices may be used to describe the area of coverage of an individual alarm zone circuit, thus permitting the connection of collective control and indicating equipment (CIE). In this case, references to actuating devices should be read as alarm zone circuits.

systems DTEs, Appendix A provides a simple tick-the-box information supplement to enable monitoring network providers and end users to make direct comparisons between equipment suppliers.

it may also be implemented using switched or packet networks as allowed in AS 60870-1-4.

installation, and commissioning Part 3: Monitoring network performance Fire—Glossary of terms Part 2: Fire protection and fire fighting equipment Supervisory control and data acquisition (SCADA)—Generic telecommuni- cations interface and protocol Part 1: General

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

5

AS 4418.2 — 2000

AS

60870

60870.1.3

60870.1.4

60870.5.1

60870.5.2

60870.5.3

60870.5.4

60870.5.5

ISO

8482

Telecontrol equipment and systems

Information technology—Telecommunications and information exchange

ITU-T

Rec.V.24

List of definitions for interchange circuits between data terminal equipment

Rec.V.28

Electrical characteristics for unbalanced double-current interchange circuits

Rec.X.400

Message handling system and service overview

1.3.2

Related documents

Attention is drawn to the following related documents:

AS

60870

60870.1.1

60870.1.2

60870.2.1

60870.3

60870.4

Telecontrol equipment and systems

1.4 DEFINITIONS

For the purpose of this Standard, the definitions in AS 60870.1.3, AS 60870.5.4, AS 2484.2

1.4.1

Primary link

The main communication link between the controlled and the controlling stations. In single

1.4.2

Secondary link

The alternative communication link between the controlled and the controlling stations in

© Standards Australia

Part 1: General considerations—Section 3: Glossary Part 1: General considerations—Section 4: Basic aspects of telecontrol data transmission and organization of Standards AS 60870.5 and IEC 60870-6 Part 5: Transmission protocols—Section 1: Transmission frame formats Part 5: Transmission protocols—Section 2: Link transmission procedures Part 5: Transmission protocols—Section 3: General structure of application data Part 5: Transmission protocols—Section 4: Definition and coding of application information elements Part 5: Transmission protocols—Section 5: Basic application functions

between systems—Twisted pair multipoint interconnections

(DTE) and data circuit-terminating equipment (DCE)

Part 1: General considerations—Section 1: General principles Part 1: General considerations—Section 2: Guide for specifications Part 2: Operating conditions—Section 1: Power supply and electromagnetic compatibility Part 3: Interfaces (electrical characteristics) Part 4: Performance requirements

and those below apply.

path systems this would be the only link.

multipath systems.

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

AS 4418.2 — 2000

SECTION

2.1 GENERAL

2

6

PROTOCOL

STRUCTURE

The IEC 60870-5 protocol is based on the three layer reference model ENHANCED

The physical layer uses ITU-T recommendations that provide binary symmetric and

The link layer consists of a number of link transmission procedures using explicit L INK

The application user layer contains a number of 'application functions' that involve the

The application layer of this Standard does not use explicit APPLICATION PROTOCOL

Figure 2.1 shows the EPA model and the selected standard definitions for this Standard.

Selected application functions of

Selected application information elements

Selected application service data units

Selected link transmission procedures

Selected transmission frame formats

Selected ITU-T recommendations

User Process

Application (layer 7)

Link (layer 2)

Physical (layer 1)

FIGURE 2.1

SELECTED STANDARDS FOR MONITORING FIRE ALARMS

© Standards Australia

PERFORMANCE ARCHITECTURE (EPA), as specified in AS 60870.5.3.

memoryless transmission on the required medium, in order to preserve the high level of data integrity of the defined block encoding method in the link layer.

PROTOCOL CONTROL INFORMATION (LPCI) that are capable of carrying APPLICATION SERVICE DATA UNITS (ASDUs) as link-user data. The link layer uses a selected frame format to provide the required integrity, efficiency and convenience of transmission.

transmission of ASDUs between source and destination.

CONTROL INFORMATION (APCI). This is implicit in the contents of the ASDU DATA UNIT IDENTIFIER field and in the type of link service used.

AS 60870.5.5

of AS 60870.5.4

of AS 60870.5.3

of AS 60870.5.2

of AS 60870.5.1

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

3.1

3.1.1

SECTION

3

7

PHYSICAL

SELECTIONS FROM ISO AND ITU-T STANDARDS

General

LAYER

AS 4418.2 — 2000

The following fixed network configurations are supported:

(a)

(b)

(c)

Point-to-point.

Multiple point-to-point.

Dialled point-to-point.

The subset of the ITU-T Recs. V.24/V.28, defined in Clause 3.1.2, is valid.

NOTE: In this Standard the 'data circuit' is treated separately from the fire alarm system data

3.1.2

Asynchronous V.24/V.28 DTE/DCE interface

This Standard specifies a subset of the ITU-T Rec. V.24, using the signal levels specified

The minimum transmission speed shall be 2.4 kbit/s.

TABLE

3.1

SELECTIONS FROM V.24/V.28

*

Interchange

circuit number

Interchange circuit name

102

103

104

Signal ground or common return

Transmitted data

Received data

105*

106†

107†

108*

109†

Request to send

Ready for sending

Data set ready

Data terminal ready

Data channel received line signal detector

May have constant potential.

Not mandatory. It may be used to supervise the transmission circuit.

3.1.3

Other compatible interfaces

From

DCE

x

x

x

x

To

DCE

x

x

x

Other interfaces such as ISO 8482 or interfaces to fibre optics and the like, shall be

© Standards Australia

terminal equipment (DTE) because it may be implemented by separate hardware. Consequentially, this Standard includes a full specification of the DTE/DCE (data circuit- terminating equipment) interface, but, only a requirement specification for suitable DCEs is given.

by Rec. V.28, shown in Table 3.1.

permitted by agreement between vendor and user.

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

AS 4418.2 — 2000

4.1

SECTION

4

TRANSMISSION FRAME FORMAT

8

LINK

LAYER

This Standard admits exclusively frame format FT 1.2 that is defined in AS 60870.5.1. (see Figure 4.1). Formats with fixed and with variable block lengths shall be admitted. Also, the single characters I and II shall be admitted. As identified in AS 60870.5.1, the bit order format is such that the Least Significant Bit shall be transmitted to the line first. As identified in AS 60870.5.2, the first transmitted address octet contains the least significant address bits.

NOTE: Designers' attention is drawn to the rules defined in AS 60870.5.1.

L

C

A

User

Data

FRAME WITH

VARIABLE

LENGTH

Start 68 H

L

L

Start 68 H

C

A

Link User

Data

Checksum

End 16 H

– Length field range:- 0

– Control field

255

– Address field (4 octets)

FIGURE 4.1

FRAME WITH

FIXED LENGTH

Start 10 H

C

A

Checksum

End 16 H

(repeated identical octets)

SINGLE

CHARACTER

E5 H

A2 H

USED TRANSMISSION FRAME FORMAT (FT 1.2)

Frame with variable length

Frame with fixed length

This frame is without Link User Data.

:=

:=

CP48+8L{Start(=68H),Length,Start (=68H),

End(=16H)}

CP64{Start(=10H),Control,Address,Checks

um,End (=16H)}

L = Number of user data octets = 5 + Link user data octets

Single character I

Single character II

© Standards Australia

:=

:=

BS8[1 8]<E5H>

BS8[1 8]<A2H>

control,Address,Link user data, Checksum,

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

4.2

4.2.1

9

LINK TRANSMISSION PROCEDURES

General

AS 4418.2 — 2000

Only balanced transmission procedures as defined in AS 60870.5.2 shall be used. This means that the initiation of transmission procedures may be from either the controlling station or a controlled station.

The basic procedures use the SEND/CONFIRM service and the REQUEST/RESPOND service.

The interface between link layer and the service user is not defined in this Standard.

4.2.2

Link LENGTH-field (see AS 60870.5.2 and Figure 4.1)

The maximum length of link frames shall be set at 255 octets. If required the maximum

4.2.3

Link CONTROL-field (see AS 60870.5.2 and Figure 4.1)

The use of the single character ACK (E5), as allowed by AS 60870.5.1, is undefined by this

or NAK shall be used to avoid the possibility of data corruption or noise being mistaken for

AD0

3

is the address and SUM is the checksum of the control and address octets as

specified by AS 60870.5.1. Station A shall be defined as the CONTROLLING STATION and

12345678

1

0

LCT

AD0

AD1

AD2

AD3

SUM

1

6

As an example, an acknowledge message from controlling station to DTE with address 0

10 80 00 00 00 00 90 16

Control field flags as specified in Table 4.1 shall be used.

TABLE

4.1

LINK CONTROL FIELD

Source

Initiator

(PRM=1)

Responder

(PRM=0)

Function

code

0

1

2

3

4

9

0

8

1

11

14

15

Frame type and function

Send/Confirm: Reset of remote link

Send/Confirm: Reset of user process

Send/Confirm: Test function for link

Send/Confirm: User data

Send/no reply: User data

Request/respond: Request status of link

Confirm: ACK

Response: User data

Confirm: NAK

Respond: Status of link

Link service not functioning

Link service not implemented

Used by messages

Fixed length

Fixed length

Fixed length

All ASDUs

Not used

Fixed length

Acknowledge

Response ASDUs

Negative acknowledge of

Fixed length

Fixed length

Fixed length

© Standards Australia

Spontaneous transmissions have priority over cyclic transmissions.

length for each direction may be different.

Standard. For integrity purposes the fixed frame message with the control field set to ACK

an ACK as shown in the following frame construction where LCT is the link control byte,

station B as the CONTROLLED STATION or DTE as specified in AS 60870.5.2.

will have the following hexadecimal content where further messages are acceptable:

link message error

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

AS 4418.2 — 2000

10

Function codes that shall be used when sending an ASDU in the PRM=1 case are 3 and 4. Function code 3 shall be used for exchanges where there is no response required from the destination. Function code 4 shall be used for exchanges where a response of some kind is expected, for example a request ASDU and ASDUs that require an application layer acknowledge (ASDU 39).

For the responders, function codes 0, 1 and 8 shall be used.

4.2.3.1

Direction (DIR) flag

The DIR flag shall be set by the message originating station. Station A to Station B

4.2.3.2

Initiating/responding (PRM) flag

The PRM flag shall be set to 1 in all messages transmitted by the station initiating the

4.2.3.3

Frame count bit (FCB)

The FCB flag shall be alternately set to 0 and 1 for each message transmitted by a station as

4.2.3.4

Frame count validity (FCV)

The FCV flag shall be used

in accordance with AS 60870.5.2 balanced transmission

4.2.3.5

Data flow control (DFC)

The DFC flag shall be set by the receiving station in accordance with AS 60870.5.2

4.2.4

Link ADDRESS-field (see AS 60870.5.2 and Figure 4.1)

The address field A of the link shall be four octets as determined by a fixed system

Address A := UI32[1

32]<0

4

294 967 295>

4.2.5

Time out interval for repeated frame transmission

The matched time out interval as described in AS 60870.5.2 shall be used. The time out

© Standards Australia

transmission is defined as from the CMS to the ASE and for this the flag shall be set to 1. All transmissions from the ASE shall have the flag set to 0. The CMS may use this flag to determine that the transmission did come from an ASE and similarly the ASE may ignore transmission wrongly received from other ASE units.

message exchange and conversely to 0 by the responding station. This shall be checked by each station in accordance with AS 60870.5.2 balanced transmission procedures.

an indication of continuity. This shall be checked by each station in accordance with AS 60870.5.2 balanced transmission procedures to detect for lost message sequence.

procedures.

balanced transmission procedures when it is too busy to process more messages. The transmitting station shall handle this in accordance with AS 60870.5.2 balanced transmission procedures.

parameter. By default the link address shall be set to the DTE address. Different link addresses used shall be agreed between vendor and user.

interval (t o ) shall be constant for each defined combination of transmission speeds, and set by a parameter in 10ms steps.

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

SECTION

5.1

GENERAL

5

11

STRUCTURE

DATA

OF

AS 4418.2 — 2000

APPLICATION

The document AS 60870.5.3 describes the basic application data units in transmission

A

LINK PROTOCOL DATA UNIT (LPDU) of this Standard shall contain no more than one

APPLICATION SERVICE DATA UNIT (ASDU).

The ASDU shall be composed of a DATA UNIT IDENTIFIER and one, or more than one,

INFORMATION OBJECTs (see Figure 5.1).

The DATA UNIT IDENTIFIER shall have the same structure for all ASDUs. The INFORMATION

the TYPE IDENTIFICATION field.

The structure of the DATA UNIT IDENTIFIER shall be:

(a)

(b)

(c)

(d)

1 Octet

1 Octet

1 Octet

4 Octets

TYPE IDENTIFICATION.

VARIABLE STRUCTURE QUALIFIER.

CAUSE OF TRANSMISSION.

COMMON ADDRESS OF ASDU.

The size of the address of the controlled station data terminal equipment shall be

There shall be no data field LENGTH OF ASDU. Each frame shall have only a single ASDU

is

5 in the case of a four octet link address).

TIME TAGS (if present) shall belong either to a single information object (TIME TAG OF

INFORMATION OBJECT) or to the complete ASDU (COMMON TIME TAG OF ASDU).

Where the TIME TAG OF INFORMATION OBJECT is used,

the TIME TAG OF INFORMATION

OBJECT shall be set to the event time. Where the common time tag of ASDU is used, the

NOTE: The controlling station may use the COMMON TIME TAG OF ASDU to determine the current

The INFORMATION OBJECT shall consist of an INFORMATION OBJECT IDENTIFIER (if present),

The

INFORMATION

OBJECT

IDENTIFIER

shall

consist

only

of

the

INFORMATION

OBJECT

ADDRESS. In all cases, the COMMON ADDRESS OF ASDU together with the INFORMATION

OBJECT

ADDRESS

distinguishes the complete SET OF INFORMATION ELEMENTs

within a

specific system. The combination of both addresses shall be unambiguous per system. The

TYPE IDENTIFICATION shall not be part of a COMMON ADDRESS or an INFORMATION OBJECT

© Standards Australia

frames of telecontrol systems. This Clause selects specific field elements out of this basic Standard and defines APPLICATION SERVICE DATA UNITs used in this Standard.

OBJECTs of an ASDU shall be always of the same structure and type, which are defined in

determined by a fixed system parameter, in this case 4 octets. The address of the controlled station data terminal equipment shall be the station address.

available. The LENGTH OF ASDU shall be determined by the frame length (as announced in the link protocol length field) minus a fixed integer specified by a system parameter (which

COMMON TIME TAG OF ASDU shall be set to the time the ASDU is ready to be sent.

time stored in the controlled station. This may be used to determine if the controlling station should send a C_CS_NA_1 Clock Synch command to the controlled station to correct the controlled station’s clock.

a SET OF INFORMATION ELEMENTs and a TIME TAG OF INFORMATION OBJECT (if present).

ADDRESS.

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

AS 4418.2 — 2000

12

The SET OF INFORMATION ELEMENTs shall be either a SINGLE INFORMATION ELEMENT, a COMBINATION OF ELEMENTs or a SEQUENCE OF INFORMATION ELEMENTs.

APPLICATION

SERVICE

DATA UNIT

TYPE IDENTIFICATION

VARIABLE STRUCTURE

DATA UNIT

IDENTIFIER

CAUSE OF TRANSMISSION

COMMON ADDRESS OF ASDU

COMMON ADDRESS OF ASDU

DATA UNIT TYPE

ADDRESS OF ALARM

COMMON ADDRESS OF ASDU

COMMON ADDRESS OF ASDU

INFORMATION OBJECT ADDRESS

INFORMATION OBJECT ADDRESS

INFORMATION OBJECT 1

SET OF INFORMATION ELEMENTS

TIME TAG

TIME TAG OF

Data unit identifier

INFORMATION OBJECT

Variable parameter i

Variable parameter j

COMMON TIME TAG

OF ASDU

FIGURE 5.1

TIME TAG

TIME TAG

INFORMATION OBJECT n

TIME TAG OF

COMMON TIME TAG OF

STRUCTURE OF AN ASDU

:=

:=

:=

:=

:=

:=

:=

CP56{TYPE IDENTIFICATION,VARIABLE STRUCTURE

CP8i+8j+8ta{INFORMATION OBJECT ADDRESS, SET OF

2 if INFORMATION OBJECT ADDRESS is present, 0 if

number of octets of SET OF INFORMATION ELEMENTS

7 if TIME TAG OF INFORMATION OBJECT is present, 0 if

CP8tb{TIME TAG}

7 if COMMON TIME TAG OF ASDU is present, 0 if COMMON

TIME TAG OF ASDU is not present

© Standards Australia

QUALIFIER

SYSTEM DTE

ms up to years (binary time ta)

ms up to years (binary time ta)

ms up to years (binary time tb)

INFORMATION OBJECT 1

INFORMATION OBJECT n

ASDU

QUALIFIER,CAUSE OF TRANSMISSION,ADDRESS OF ALARM SYSTEM DTE}

INFORMATION ELEMENTS,TIME TAG(optional)}

INFORMATION OBJECT ADDRESS is not present

Variable parameter ta

TIME TAG OF INFORMATION OBJECT is not present

Variable parameter tb

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

6.1

13

SECTION

6

DEFINITION

AND

APPLICATION

INFORMATION

GENERAL

CODING

AS 4418.2 — 2000

OF

ELEMENTS

The sizes and contents of individual information fields of ASDUs shall be specified according to the declaration rules for information elements defined in AS 60870.5.4.

6.2

TYPE IDENTIFICATION (Figure 6.1)

6.2.1 General

Octet 1, TYPE IDENTIFICATION, shall define structure, type and format of the following

INFORMATION OBJECT(s):

TYPE IDENTIFICATION shall be defined as: TYPE IDENTIFICATION := UI8[1

8]<0

255>

ASDUs with undefined values of TYPE IDENTIFICATION shall be acknowledged negatively

Bit

6.2.2

87654

2 7

3

FIGURE 6.1

TYPE IDENTIFICATION

2

Definition of semantics of values of the type identification field

1

2 0

The value <0> shall not be used. The range of values (numbers) 1 to 127 shall be as

Tables 6.1 to 6.5 show the definition of TYPE IDENTIFICATION numbers for process and

TYPE

IDENTIFICATION

<0>

<1

127>

<128

255>

:=

:=

:=

:=

UI8[1 8]<0 255>

not used

for standard definitions of this Standard (compatible range)

for special use (private range)

© Standards Australia

and discarded by both controlling and controlled stations.

defined in this Standard. The range of numbers 128 to 255 are not defined by this Standard. TYPE IDENTIFICATION numbers 128 to 255 may be defined independently of each other by users of this Standard. However full interoperability would then be obtained only when using ASDUs having TYPE IDENTIFICATION in the range 1 to 127.

system information in monitor and control direction.

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

AS 4418.2 — 2000

14

TABLE

6.1

SEMANTICS OF TYPE IDENTIFICATION — PROCESS INFORMATION IN MONITOR DIRECTION

<0>

<1>

<2>

<3 29>

:=

:=

:=

:=

TYPE IDENTIFICATION

Not defined

Alarm system summary

Status of an actuating device

:=

UI8[1 8]<0 29>

Reserved for further compatible definitions

TABLE

6.2

M_AS_TA_1

M_AS_TB_1

SEMANTICS OF TYPE IDENTIFICATION — PROCESS INFORMATION IN

CON <30>

CON <31>

CON <32>

CON <33>

<34 38>

<39>

:=

:=

:=

:=

:=

:=

TYPE IDENTIFICATION

Local warning system

Local warning bell

Reset actuating devices

:=

UI8[1 8]<30 39>

Isolate actuating devices in selected device range

Reserved for further compatible definitions

ASDU Acknowledge

C_LW_NA_1

C_LW_NB_1

C_RP_NB_1

C_AS_ND_1

C_AK_NA_1

NOTE: ASDUs marked (CON) in control direction are confirmed application services and may be mirrored in

TABLE

6.3

SEMANTICS OF TYPE IDENTIFICATION—SYSTEM INFORMATION IN

<40>

<41>

<42>

<43>

<44 59>

:=

:=

:=

:=

:=

© Standards Australia

TYPE IDENTIFICATION

End of initialization

:=

UI8[1 8]<40 59>

Manufacturer and product specification of alarm system DTE

Current system time of alarm system DTE

Control and indicating equipment (CIE) device configuration

Reserved for further compatible definitions

M_EI_TA_1

P_MP_TA_1

M_TI_TA_1

M_IC_TA_1

CONTROL DIRECTION

monitor direction with different causes of transmission. These mirrored ASDUs are used for positive/negative acknowledgments (verifications). The causes of transmission are defined in Clause 6.4.

MONITOR DIRECTION

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

15

TABLE

6.4

AS 4418.2 — 2000

SEMANTICS OF TYPE IDENTIFICATION — SYSTEM INFORMATION IN CONTROL DIRECTION

CON <60>

CON <61>

CON <62>

CON <63>

CON <64>

CON <65>

CON <66>

CON <67>

CON <68>

CON <69>

<70

89>

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

TYPE IDENTIFICATION

:=

UI8[1 8]<60 89>

Read manufacturer and product specification

Read current time of alarm system DTE

Clock synchronization command

Delay acquisition time

Reboot controlled station

Read CIE device configuration

Read alarm system status

Read selected actuating device status in a selected device number range

Test command

Terminate transactions

reserved for further compatible definitions

C_RD_NA_1

C_TI_NA_1

C_CS_NA_1

C_CD_NA_1

C_RP_NA_1

C_IC_NA_1

C_AS_NA_1

C_AS_NB_1

C_TS_NA_1

C_AS_NC_1

NOTE: ASDUs marked (CON) in control direction are confirmed application services and may be mirrored in monitor direction with different causes of transmission. These mirrored ASDUs are used for positive/negative acknowledgments (verifications). The causes of transmission are defined in Clause 6.4.

TABLE

6.5

SEMANTICS OF TYPE IDENTIFICATION - FILE TRANSFER

<90>

<91>

<92>

<93>

<94>

<95>

<96>

<97 127>

:=

:=

:=

:=

:=

:=

:=

:=

TYPE IDENTIFICATION

File ready

Section ready

:=

UI8[1 8]<90 127>

Call directory, select file, call file, call section

Last section, last segment

Ack file, ack section

Segment

Directory

Reserved for further compatible definitions

6.3

6.3.1

VARIABLE STRUCTURE QUALIFIER (Figure 6.2)

General

F_FR_NA_1

F_SR_NA_1

F_SC_NA_1

F_LS_NA_1

F_AF_NA_1

F_SG_NA_1

F_DR_TA_1

Octet 2 of the DATA UNIT IDENTIFIER of the ASDU shall define the VARIABLE STRUCTURE

QUALIFIER which is specified in the following:

Variable structure qualifier shall be defined as —

Variable structure qualifier := CP8{number,SQ}

Bit

87654

SQ

2 6

3

2

FIGURE 6.2

VARIABLE STRUCTURE QUALIFIER

1

2 0

© Standards Australia

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

AS 4418.2 — 2000

16

6.3.2

field

Definition of semantics of the values of the VARIABLE STRUCTURE QUALIFIER

VARIABLE STRUCTURE QUALIFIER

:=

CP8{number,SQ}

Number=N

<0>

<1

127>

:=

:=

:=

UI7[1 7]<0 127>

ASDU contains no information object

number of information objects or elements

SQ=Single/sequence

<0>

:=

:=

BS1[8]<0 1>

addressing of an individual element or combination of elements in a number of information objects of the same type

<1>

SQ<0>andN<0

127>

:=

:=

addressing of a sequence of information elements in one object

number of information objects

SQ<1>andN<0

127>

:=

number of information elements of a single object per ASDU

The SQ bit specifies the method of addressing the following elements.

information

objects

or

SQ = 0: Each single element or a combination of elements shall be addressed by the information object address. The ASDU may consist of one or more than one equal information objects. The number N shall be binary-coded and shall define the number of information objects.

SQ = 1: A sequence of equal information elements shall be addressed (see AS 60870.5.3) by the information object address. The information object address shall specify the associated address of the first information element of the sequence. The following information elements shall be identified by numbers incrementing continuously by +1 from the offset. The number N shall be binary-coded and shall define the number of the information elements. In the case of a sequence of information elements only one information object per ASDU shall be allocated.

6.4

6.4.1

CAUSE OF TRANSMISSION (Figure 6.3)

General

Octet 3 of the DATA UNIT IDENTIFIER of the ASDU shall define the CAUSE OF TRANSMISSION field which is specified in the following:

Bit

© Standards Australia

87654

T

P/N

2 5

3

FIGURE 6.3

CAUSE OF TRANSMISSION

2

1

2 0

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

17

6.4.2

Definition of semantics of values of the CAUSE OF TRANSMISSION field

CAUSE OF TRANSMISSION

Cause

<0>

<1

<1

<32

P/N

<0>

<1>

63>

31>

63>

T=test

<0>

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

CP8{Cause,P/N,T}

UI6[1 6]<0 63>

Not defined

Number of cause

For standard definitions of this Standard (compatible range see Table 6.5)

For special use (private range)

BS1[7]<0 1>

Positive confirm

Negative confirm

BS1[8]<0 1>

No test

<1>

:=

Test

AS 4418.2 — 2000

The CAUSE OF TRANSMISSION shall direct the ASDU to a specific application task (program) for processing.

The P/N-bit shall indicate the positive or negative confirmation of activation requested by the primary application function. In the case of irrelevance the P/N-bit shall be zero.

In addition to the cause, the test-bit shall define ASDUs which were generated during test conditions. It is used, for example, to test transmission and equipment without controlling the process.

TABLE

6.6

SEMANTICS OF CAUSE OF TRANSMISSION

<0>

<1>

<2>

<3>

<4>

<5>

<6>

<7>

<8>

<9>

<10>

<11>

<12>

<13>

<14>

<15>

<16>

<17>

<18>

<19>

<20>

<21 31>

<32>

<33 63>

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

CAUSE

:=

UI6[1 6]<0 63>

Not used Initialized Cyclic Spontaneous Field terminal session Request or requested Activation or isolation Activation confirmation or test passed Deactivation or deisolation Deactivation confirmation or test failed Activation termination Primary link unavailable Time synchronization Requested data record not available Requested ASDU type not available Actuating device number in the ASDU sent by the controlling station is not known Address specification in the ASDU sent by the controlling station is not known Requested information object is not available Termination of CIE device configuration Local operation File transfer Reserved for further compatible definitions Application knowledge For special use (private range)

© Standards Australia

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

AS 4418.2 — 2000

18

6.5

ADDRESS OF ALARM SYSTEM DATA TERMINAL EQUIPMENT (Figure 6.4)

Octets 4 up to 7 of the DATA UNIT IDENTIFIER of the ASDU shall define the address of the alarm system DTE which is specified in the following. The length of the address of the alarm system DTE is a parameter which shall be fixed per system.

Bit

87654

2

7

2

15

2

2

23

31

3

2

FIGURE 6.4

ADDRESS OF ALARM SYSTEM DTE

ADDRESS OF ALARM

SYSTEM DTE

<0>

<1

4

294 967 295>

:=

:=

:=

UI32[1

32]<0

not used

station address

4

294 967 295>

1

2

0

2

8

2

2

16

24

The address of the alarm system DTE is a COMMON ADDRESS which shall be associated

6.6

INFORMATION OBJECT ADDRESS (Figure 6.5)

The INFORMATION OBJECT ADDRESS is the address of an information object within an

NOTE: This means that if a CIE configuration is changed to delete an actuating device, that

Bit

87654

2

7

2

15

3

2

INFORMATION

<0>

<1

65535>

FIGURE 6.5

INFORMATION OBJECT ADDRESS

:=

:=

:=

UI16[1 16]<0 65535>

information object is irrelevant

information object address

© Standards Australia

1

2

2

0

8

with all objects in an ASDU (see AS 60870.5.3). AS 60870.5.1 link address shall be set to the DTE address by default. The address of the alarm system DTE shall be fixed at manufacture and shall be allocated from a range supplied to the manufacturer by the recognized industry body, currently Fire Protection Association Australia.

ASDU. It shall consists of two octets. The INFORMATION OBJECT ADDRESS shall be used to identify individual actuating devices connected to CIE. Devices shall be numbered 1 up to n. When an address range of actuating devices is sent from the controlled station to the controlling station, only valid INFORMATION OBJECT ADDRESSes shall be sent.

INFORMATION OBJECT ADDRESS may no longer be valid and therefore no device status data is transmitted to the controlling station. The INFORMATION OBJECT ADDRESS is also used to uniquely identify individual actuating devices within the DTE.

OBJECT ADDRESS

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

6.7

6.7.1

INFORMATION ELEMENTS

General

19

AS 4418.2 — 2000

The following information elements shall be used in the ASDUs defined in this document. They shall be structured according to the definitions of AS 60870.5.4.

6.7.2

Alarm system summary

Alarm system status

:=

Actuating

change

Normal

<1>

<0>

Alarm

<1>

<0>

Fault

<1>

<0>

Isolate

<1>

<0>

device

status

FAS connection fault

<1>

<0>

FAS isolated

<1>

<0>

BS2[7

8]<0

3>

CIE status

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

Configuration change

<1>

<0>

Power fail

<1>

<0>

Low battery

:=

:=

:=

:=

:=

:=

:=

CP{actuating device status change, CIE status, alarm system DTE maintenance contractor, building data, field terminal}

BS8{normal, alarm, fault, isolate, FAS connection fault, FAS isolated}

BS1[1]<0 1>

Normal

not Normal

BS1[2]<0 1>

Alarm

not Alarm

BS1[3]<0 1>

Fault

not Fault

BS1[4]<0 1>

Isolate

not Isolate

BS1[5]

FAS connection fault

not FAS connection fault

BS1[6]

FAS isolated

not FAS isolated

reserved for special use (private range)

BS8{configuration change, power fail, low battery, mains fail, CPU fail, DTE isolate, failure of primary link, failure of secondary link}

BS1[1]<0 1>

Configuration change

not Configuration change

BS1[2]<0 1>

Power fail

not Power fail

BS1[3]<0 1>

© Standards Australia

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

AS 4418.2 — 2000

<1>

<0>

Mains fail

<1>

<0>

CPU fail

<1>

<0>

DTE isolate

<1>

<0>

Failure of primary link

<1>

<0>

Failure of secondary link

<1>

<0>

Alarm system DTE maintenance contractor

<0>

<1

65535>

Building data

Class

<0>

<1>

<2>

<3>

<4>

<5>

<6>

<7>

<8>

<9>

<10>

<11>

<12>

<13>

<14

31>

© Standards Australia

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

20

Low battery

not Low battery

BS1[4]<0 1>

Mains fail

not Mains fail

BS1[5]<0 1>

CPU fail

not CPU fail

BS1[6]<0 1>

DTE isolate

not DTE isolate

BS1[7]<0 1>

Failure of primary link

not Failure of primary link

BS1[8]<0 1>

Failure of secondary link

not Failure of secondary link

UI16[1 16]<0 65535>

not defined

registered maintenance contractor number defined by network provider

CP8{class, number of occupants}

UI5[1 5]<0 31>

not defined

Class 1a

Class 1b

Class 2

Class 3

Class 4

Class 5

Class 6

Class 7

Class 8

Class 9a

Class 9b

Class 10a

Class 10b

reserved for further compatible definitions

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

21

AS 4418.2 — 2000

Number of occupants = number of occupants normally in the building or on the site

Number of occupants

<0>

:=

:=

UI3[6 8]

0

<1>

<2>

<3>

<4>

<5>

<6

7>

Field terminal session

Request

<1>

<0>

NOTES:

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

1 up to 9

10 up to 99

100 up to 999

1000 up to 9999

10 000 up to 99 999

reserved for further compatible definitions

BS8{session request}

BS1[1]<0 1>

Request

not Request

1

2

The degree of access to the alarm network and data held is to be determined by the network controller.

Terminal sessions may use the file transfer commands to obtain copies of data held by the controlling

6.7.3

Status

device

Status of an actuating device

of

an

actuating

:=

BS8{normal, alarm, fault, isolate, FAS

Normal

<1>

<0>

Alarm

<1>

<0>

Fault

<1>

<0>

Isolate

<1>

<0>

FAS connection fault

<1>

<0>

FAS isolated

<1>

<0>

BS2[7

8]<0

3>

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

BS1[1]<0 1>

Normal

not Normal

BS1[2]<0 1>

Alarm

not Alarm

BS1[3]<0 1>

Fault

not Fault

BS1[4]<0 1>

Isolate

not Isolate

BS1[5]

FAS connection fault

not FAS connection fault

BS1[6]

FAS isolated

not FAS isolated

reserved for special use (private range).

© Standards Australia

station, including event history logs, for the purpose of post-event investigation and analysis.

connection fault, FAS isolated}

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

AS 4418.2 — 2000

6.7.4

CIE device configuration

CIE device configuration

Device type

<0>

:=

:=

:=

<1>

<2>

:=

:=

<3>

<4>

<5>

<6>

<7>

<8>

:=

:=

:=

:=

:=

:=

<9>

<10>

<11>

<12>

<13>

<14>

<15>

<16>

<14

<128

127>

255>

Status = current status of actuating device status

Normal

<1>

<0>

Alarm

<1>

<0>

Fault

<1>

<0>

Isolate

<1>

<0>

FAS connection fault

<1>

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

© Standards Australia

22

CP24+8l{device type, status, length, location}

UI8[1 8]<0 255>

not defined

Smoke detector

Heat detector

Smoke and heat detector

Flame detector

Manual call point

Valve monitor device

Wet sprinkler system

Dry sprinkler system

Drenching sprinkler system

Sprinkler flow switch

Foam system

Chlorine alarm

Gas discharge system

Contact input

Flammable gas detector

Carbon monoxide detector

Reserved for further compatible definitions

Reserved for special use (private range)

BS8{normal, alarm, fault, isolate, FAS connection fault, FAS isolated}

BS1[1]<0 1>

Normal

not Normal

BS1[2]<0 1>

Alarm

not Alarm

BS1[3]<0 1>

Fault

not Fault

BS1[4]<0 1>

Isolate

not Isolate

BS1[5]<0 1>

FAS connection fault

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

<0>

FAS isolated

<1>

<0>

BS2[7

8]<0

3>

Length = length of device location descriptor in octets

<0

127>

:=

:=

:=

:=

:=

:=

:=

<128

255>

:=

Location = location descriptor of actuating device location

:=

Variable parameter

:=

6.7.5

Cause of initialization

COI

UI7[1

<0>

<1>

7]

<2>

<3

31>

:=

:=

:=

:=

:=

:=

<32

127>

BS1[8]

<0>

<1>

6.7.6

Date of Standard

Date of Standard

Month = month of issue of the specification of the Standard

Year = year of issue of the

specification

Standard

of

the

:=

:=

:=

:=

:=

:=

:=

23

AS 4418.2 — 2000

not FAS connection fault

BS1[6]<0 1>

FAS isolated

not FAS isolated

Reserved for special use (private range)

UI8[33 40]<0 127>

Number of octets used to describe actuating device location

not defined

OS[0

127]<ASCII

8-bit code>

Number in length field

CP8{UI7[1 7],BS1[8]}

<0

127>

local power switch on

local manual reset

remote reset

reserved for standard definitions of this Standard (compatible range)

reserved for special use (private range)

<0 1>

initialization with unchanged local parameters

initialization after change of local parameters

CP8{month,year}

UI4[1 4]<1 12>

UI4[5 8]<0 9>

© Standards Australia

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

AS 4418.2 — 2000

6.7.7

Manufacturer

Manufacturer

6.7.8

Product code

Product code

6.7.9

Time information

:=

:=

OS[0

OS[0

24

32]<ASCII

32]<ASCII

8-bit code>

8-bit code>

Time information shall be structured in accordance with the definition of Binary Time 2a in AS 60870.5.4. In ASDUs sent by the controlling station, the IV bit is set to 0. The application shall be responsible for interpretation of the year field in Binary Time 2a. This shall be defined as the least significant two digits of the century.

6.7.10

Delay acquisition time

Delay acquisition time

Delay acquisition time

:=

:=

sum

of

transmission

internal delay

delay

and

UI16[1 16]<0 65535>

<0>

:=

delay acquisition time not obtained

<1

65535>

:=

delay acquisition time in ms

6.7.11

Mask for actuating device status requests

equipment

Mask for actuating device

:=

BS8{normal, alarm, fault, isolate, FAS

Normal

<1>

<0>

Alarm

<1>

<0>

Fault

<1>

<0>

Isolate

<1>

<0>

FAS connection fault

<1>

<0>

FAS isolated

<1>

<0>

BS2[5

BS2[7

6]<0

6]<0

3>

3>

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

:=

BS1[1]<0 1>

Positive request

Negative request

BS1[2]<0 1>

Positive request

Neutral request

BS1[3]<0 17>

Positive request

Neutral request

BS1[4]<0 1>

Positive request

Neutral request

BS1[5]<0 1>

Positive request

Neutral request

BS1[6]<0 1>

Positive request

Neutral request

Reserved for further compatible definitions

Reserved for special use (private range)

NOTE: Normal status is mutually exclusive with all the other states. Alarm, fault and isolate states may occur

© Standards Australia

status requests

connection fault, FAS isolated}

simultaneously. Accordingly, if a request is issued with bit 2 set, responses from the alarm system will include all actuating devices in alarm; alarm and fault; alarm and isolate; and alarm, fault and isolate.

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

6.7.12

FRQ

U17[1

<0>

File ready qualifier

7]

<1

63>

:=

:=

:=

:=

<64

127>

BS1[8]

<0>

:=

:=

:=

<1>

:=

6.7.13

SRQ

U17[1

<0>

Section ready qualifier

7]

:=

:=

:=

<1

63>

:=

<64

127>

BS1[8]

<0>

:=

:=

:=

<1>

6.7.14

SCQ

UI4[1

<0>

<1>

:=

Select and call qualifier

4]

:=

:=

:=

:=

<2>

<3>

<4>

:=

:=

:=

<5>

<6>

<7>

<8

10>

:=

:=

:=

:=

<11

15>

UI4[5

<0>

<1>

8]

:=

:=

:=

:=

25

CP8{U17[1 7],BS1[8]}

<0

127>

not used

AS 4418.2 — 2000

Reserved for standard definitions (compatible range)

Reserved for special use (private range)

<0 1>

Positive confirm of select, request, deactivate or delete

Negative confirm of select, request, deactivate or delete

CP8{UI7[1 7],BS1[8]}

<0

127>

not used

reserved for standard definitions (compatible range)

reserved for special use (private range)

<0 1>

section ready to load

section not ready to load

CP8{UI4[1 4],UI4[5 8]}

<0

15>

not used

select file

request file

deactive file

delete file

select section

request section

deactivate section

reserved for standard definitions (compatible range)

reserved for special use (private range)

<0

15>

default

requested memory space not available

© Standards Australia

Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)

AS 4418.2 — 2000

26

<2>

:=

checksum failed

<3>

<4>

<5>

<6

10>

:=

:=

:=

:=

unexpected communication service

unexpected name of file

unexpected name of section

reserved for standard definitions (compatible range)

<11

15>

:=

reserved for special use (private range)

6.7.15

Last section or segment qualifier

LSQ

<0>

:=

:=

UI8[1 8]<0 255>

not used

<1>

:=

file transfer without deactivation

<2>

:=

file transfer with deactivation

<3>

:=

section transfer without deactivation

<4>