Source: https://it.scribd.com/document/413626357/How-to-blue-in-red
Timestamp: 2020-06-02 03:08:56
Document Index: 736662477

Matched Legal Cases: ['art 2', 'art 2', 'art 6', 'art 3', 'art 3', 'art 2', 'art 1', 'art 1', 'art 1', 'art 5', 'art 5', 'art 5', 'art 5', 'art 5', 'art 1', 'art 1', 'art 2', 'art 3', 'art 4', 'art 68', 'art 10']

How to blue in red | Scada | Osi Model
How to blue in red
How to blue on blue background and experience to blue on blue background and experience to be a good time to blue on blue background and experience to be a good time to be a good time to be
SalvaSalva How to blue in red per dopo
Training Workshops Schedule on Automation Systems Field Instrumentation
Vijeo Training
AS 4418.2
Accessed by UNIVERSITY OF TECHNOLOGY SYDNEY on 11 Jun 2019 (Document currency not guaranteed when printed)
AS 4418.2—2000
Part 2: Fire alarm systems
acquisition (SCADA)—Generic telecommunications interface and protocol
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:
CIGRE AP35
This Standard was issued in draft form for comment as DR 99199.
AS 4418.2—2000 (Reconfirmed) 2016-07-08
Technical Committee EL-050 has reviewed the content of this publication and in
The following are represented on Technical Committee EL-050:
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
Originated as AS 4418.2—1996.
Published by Standards Australia International Ltd
ISBN 0 7337 3557 6
acquisition (SCADA)— Generic telecommunications interface and protocol
means, electronic or mechanical, including photocopying, without the written permission of the publisher.
GPO Box 5420, Sydney, NSW 2001, Australia
AS 4418.2 — 2000
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
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.
SELECTIONS FROM ISO AND ITU-T STANDARDS
TRANSMISSION FRAME FORMAT
DEFINITION AND CODING OF APPLICATION INFORMATION
TYPE IDENTIFICATION (Figure 6.1) 13
VARIABLE STRUCTURE QUALIFIER (Figure 6.2) 15
CAUSE OF TRANSMISSION (Figure 6.3)
ADDRESS OF ALARM SYSTEM DATA TERMINAL EQUIPMENT (Figure 6.4).18
INFORMATION OBJECT ADDRESS (Figure 6.5) 18
DEFINITION AND PRESENTATION OF SPECIFIC ASDUs
ASDUs FOR FILE TRANSFER
SELECTIONS FROM AS 60870.5.5
ALARM SYSTEM DATA TERMINAL EQUIPMENT (DTE)
REFERENCED AND RELATED DOCUMENTS DEFINITIONS 5
LINK TRANSMISSION PROCEDURES
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
Supervisory control and data acquisition (SCADA)—Generic
The purpose of this Standard is to standardize the monitoring of fire alarm systems installed
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,
Fire detection, warning, control and intercom systems—System design,
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
60870.1.3
60870.1.4
60870.5.1
60870.5.2
60870.5.3
Information technology—Telecommunications and information exchange
Rec.V.24
List of definitions for interchange circuits between data terminal equipment
Rec.V.28
Rec.X.400
Attention is drawn to the following related documents:
60870.1.1
60870.1.2
60870.3
60870.4
For the purpose of this Standard, the definitions in AS 60870.1.3, AS 60870.5.4, AS 2484.2
The main communication link between the controlled and the controlling stations. In single
The alternative communication link between the controlled and the controlling stations in
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.
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
Link (layer 2)
SELECTED STANDARDS FOR MONITORING FIRE ALARMS
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
The following fixed network configurations are supported:
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
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.
SELECTIONS FROM V.24/V.28
Interchange circuit name
Signal ground or common return
Data channel received line signal detector
May have constant potential.
Not mandatory. It may be used to supervise the transmission circuit.
Other compatible interfaces
Other interfaces such as ISO 8482 or interfaces to fibre optics and the like, shall be
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.
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.
Start 68 H
End 16 H
– Length field range:- 0
– Control field
– Address field (4 octets)
Start 10 H
(repeated identical octets)
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
BS8[1 8]<E5H>
BS8[1 8]<A2H>
control,Address,Link user data, Checksum,
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.
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
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
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
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.
LINK CONTROL FIELD
(PRM=1)
(PRM=0)
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
All ASDUs
Response ASDUs
Negative acknowledge of
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
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.
Direction (DIR) flag
The DIR flag shall be set by the message originating station. Station A to Station B
Initiating/responding (PRM) flag
The PRM flag shall be set to 1 in all messages transmitted by the station initiating the
Frame count bit (FCB)
The FCB flag shall be alternately set to 0 and 1 for each message transmitted by a station as
Frame count validity (FCV)
The FCV flag shall be used
in accordance with AS 60870.5.2 balanced transmission
The DFC flag shall be set by the receiving station in accordance with AS 60870.5.2
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
294 967 295>
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
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.
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.
The document AS 60870.5.3 describes the basic application data units in transmission
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:
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
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),
ADDRESS. In all cases, the COMMON ADDRESS OF ASDU together with the INFORMATION
distinguishes the complete SET OF INFORMATION ELEMENTs
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
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).
The SET OF INFORMATION ELEMENTs shall be either a SINGLE INFORMATION ELEMENT, a COMBINATION OF ELEMENTs or a SEQUENCE OF INFORMATION ELEMENTs.
COMMON ADDRESS OF ASDU
ADDRESS OF ALARM
INFORMATION OBJECT ADDRESS
INFORMATION OBJECT 1
SET OF INFORMATION ELEMENTS
TIME TAG OF
Variable parameter i
Variable parameter j
COMMON TIME TAG
OF ASDU
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
SYSTEM DTE
ms up to years (binary time ta)
ms up to years (binary time tb)
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
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.
TYPE IDENTIFICATION (Figure 6.1)
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
ASDUs with undefined values of TYPE IDENTIFICATION shall be acknowledged negatively
Definition of semantics of values of the type identification field
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
UI8[1 8]<0 255>
for standard definitions of this Standard (compatible range)
for special use (private range)
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.
SEMANTICS OF TYPE IDENTIFICATION — PROCESS INFORMATION IN MONITOR DIRECTION
<3 29>
Alarm system summary
Status of an actuating device
UI8[1 8]<0 29>
Reserved for further compatible definitions
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>
Local warning bell
Reset actuating devices
UI8[1 8]<30 39>
Isolate actuating devices in selected device range
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
SEMANTICS OF TYPE IDENTIFICATION—SYSTEM INFORMATION IN
<44 59>
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
M_EI_TA_1
P_MP_TA_1
M_TI_TA_1
M_IC_TA_1
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
SEMANTICS OF TYPE IDENTIFICATION — SYSTEM INFORMATION IN CONTROL DIRECTION
CON <65>
CON <66>
CON <67>
CON <68>
CON <69>
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
Terminate transactions
C_TI_NA_1
C_AS_NA_1
C_AS_NB_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.
SEMANTICS OF TYPE IDENTIFICATION - FILE TRANSFER
<97 127>
UI8[1 8]<90 127>
Call directory, select file, call file, call section
Last section, last segment
Ack file, ack section
VARIABLE STRUCTURE QUALIFIER (Figure 6.2)
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}
Definition of semantics of the values of the VARIABLE STRUCTURE QUALIFIER
CP8{number,SQ}
UI7[1 7]<0 127>
ASDU contains no information object
number of information objects or elements
SQ=Single/sequence
BS1[8]<0 1>
addressing of an individual element or combination of elements in a number of information objects of the same type
SQ<0>andN<0
addressing of a sequence of information elements in one object
number of information objects
SQ<1>andN<0
number of information elements of a single object per ASDU
The SQ bit specifies the method of addressing the following elements.
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.
Octet 3 of the DATA UNIT IDENTIFIER of the ASDU shall define the CAUSE OF TRANSMISSION field which is specified in the following:
Definition of semantics of values of the CAUSE OF TRANSMISSION field
CP8{Cause,P/N,T}
UI6[1 6]<0 63>
Number of cause
For standard definitions of this Standard (compatible range see Table 6.5)
BS1[7]<0 1>
Positive confirm
Negative confirm
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.
SEMANTICS OF CAUSE OF TRANSMISSION
<21 31>
<33 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)
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.
ADDRESS OF ALARM SYSTEM DTE
UI32[1
The address of the alarm system DTE is a COMMON ADDRESS which shall be associated
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
65535>
UI16[1 16]<0 65535>
information object is irrelevant
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.
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.
FAS connection fault
FAS isolated
BS2[7
CIE status
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>
BS1[2]<0 1>
BS1[3]<0 1>
BS1[4]<0 1>
BS1[5]
not FAS connection fault
BS1[6]
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}
not Configuration change
not Power fail
DTE isolate
Failure of primary link
Failure of secondary link
Alarm system DTE maintenance contractor
not Mains fail
BS1[5]<0 1>
not CPU fail
BS1[6]<0 1>
not DTE isolate
not Failure of primary link
not Failure of secondary link
registered maintenance contractor number defined by network provider
CP8{class, number of occupants}
UI5[1 5]<0 31>
Number of occupants = number of occupants normally in the building or on the site
UI3[6 8]
Field terminal session
1 up to 9
10 up to 99
100 up to 999
1000 up to 9999
10 000 up to 99 999
BS8{session request}
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
BS8{normal, alarm, fault, isolate, FAS
reserved for special use (private range).
station, including event history logs, for the purpose of post-event investigation and analysis.
connection fault, FAS isolated}
CIE device configuration
Status = current status of actuating device status
CP24+8l{device type, status, length, location}
Valve monitor device
Drenching sprinkler system
Chlorine alarm
Length = length of device location descriptor in octets
Location = location descriptor of actuating device location
Cause of initialization
UI7[1
Date of Standard
Month = month of issue of the specification of the Standard
Year = year of issue of the
UI8[33 40]<0 127>
Number of octets used to describe actuating device location
OS[0
127]<ASCII
8-bit code>
Number in length field
CP8{UI7[1 7],BS1[8]}
local power switch on
local manual reset
reserved for standard definitions of this Standard (compatible range)
initialization with unchanged local parameters
initialization after change of local parameters
CP8{month,year}
UI4[1 4]<1 12>
UI4[5 8]<0 9>
32]<ASCII
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.
delay acquisition time not obtained
delay acquisition time in ms
Mask for actuating device status requests
Mask for actuating device
BS2[5
6]<0
BS1[3]<0 17>
NOTE: Normal status is mutually exclusive with all the other states. Alarm, fault and isolate states may occur
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.
U17[1
File ready qualifier
Section ready qualifier
UI4[1
Select and call qualifier
UI4[5
CP8{U17[1 7],BS1[8]}
Reserved for standard definitions (compatible range)
Positive confirm of select, request, deactivate or delete
Negative confirm of select, request, deactivate or delete
section ready to load
section not ready to load
CP8{UI4[1 4],UI4[5 8]}
deactive file
deactivate section
requested memory space not available
unexpected communication service
unexpected name of file
unexpected name of section
Last section or segment qualifier
file transfer without deactivation
file transfer with deactivation
section transfer without deactivation