Document Number : 61850C-CG Version : 1.00 Revision : 001 Date : 12.07.05 Classification: General Release
NOTICE OF COPYRIGHT & PROPRIETARY RIGHTS
2012, ASAT Solutions Inc. All rights reserved.
The contents of this manual are the property of ASAT Solutions Inc. No part of this work may be reproduced or transmitted in any form or by any means, except as permitted in written license agreement with ASAT Solutions Inc. The information contained in this document is subject to change without notice.
Any attached hardware schematics and technical descriptions, or software listings that disclose source code, are for information purposes only. Reproduction in whole or in part to create working hardware or software for other than ASAT Solutions Inc. products is strictly prohibited except as permitted by written license agreement with ASAT Solutions Inc.
TRADEMARK NOTICES
ASAT, DAP, VPort and are trademarks and service marks of ASAT Solutions Inc.
Microsoft Visio is a trademark of Microsoft Corporation. All other brand and product names mentioned in this document are trademarks or registered trademarks of their respective companies.
MODIFICATION RECORD VERSION REV. DATE INITIALS COMMENT 1.00 1 7 Jun 12 LG Create 1.00 1.1 3 Jul 12 BE Update
<This page is intentionally left blank>
Table of Contents About This Document Purpose of this Document ........................................................................................................ 1-3 Additional Documentation ........................................................................................................ 1-3 Chapter 1: Application Overview 1.1 Application Overview................................................................................................... 1-5 1.2 Core Functions ............................................................................................................ 1-5 1.3 Configuration Basic ..................................................................................................... 1-6 Chapter 2: Create and Modify Configuration 2.1 Set Up Procedures...................................................................................................... 2-7 2.1.1 Stage 1 Prepare DAP Environment ..................................................................... 2-7 2.1.2 Stage 2 Create a Client Connection .................................................................... 2-7 2.2 Data Report Configuration ........................................................................................ 2-10 2.2.1 Device or Logic Device Scan................................................................................ 2-10 2.2.2 Buffered Report Control Block .............................................................................. 2-10 2.2.3 Unbuffered Report Control Block.......................................................................... 2-11 2.2.4 GOOSE Receiver.................................................................................................. 2-11 2.3 CPU Redundant and Port Bridging ........................................................................... 2-12 2.3.1 CPU Redundant .................................................................................................... 2-12 2.3.2 Port Bridging ......................................................................................................... 2-12 2.4 Edit an Existing Client ............................................................................................... 2-13 Chapter 3: Configuration Tables and Parameters 3.1 Device Information and Property Window................................................................. 3-14 3.2 IEC 61850 Connection Property ............................................................................... 3-16 3.3 IEC 61850 Server IP and Port Configuration ............................................................ 3-16 3.4 OSI Component Settings .......................................................................................... 3-16 3.5 Client Device or Logic Device Settings ..................................................................... 3-17 Chapter 4: Errors and Troubleshooting F1: Device Off-line with Cross sign...................................................................................... 4-19 F2: Device off-line and device icon without flashing .............................................................. 4-19 F3: Device icon is flashing but points are off-line, not updating values/states ...................... 4-20 F4: RCB does not report object values/states ....................................................................... 4-20 F5: In Redundant system the RCB works on one of CPU only ............................................. 4-21 F6: GOOSE message does not report object values/states .................................................. 4-21 Appendix A: Abbreviations IEC 61850 Client Configuration Guilde 61850C-CG Version 1.00 Revision 001 Release: General 1-1
List of Figures Figure 1 Sample of IEC 61850 SCL Editor ...................................................................................2-8 Figure 2 Sample of Pre-configured Device Loader.......................................................................2-9
ASAT Solutions Inc. 1-2 61850C-CG Version 1.00 Revision 001 Release: General
List of Tables Table 1 Core Functions Supported by DAP IEC-61850 Client ....................................................1-5
IEC 61850 Client Configuration Guilde 61850C-CG Version 1.00 Revision 001 Release: General 1-3
About This Document Purpose of this Document This document explains how to configure IEC 61850 client service under ASAT Solutions Inc. Digital Automation Platform (DAP) environment.
Additional Documentation If you require more details than this document provides, several supporting documents are available. They are:
IEC 61850-1 Introduction and overview
IEC 61850-2 Glossary
IEC 61850-3 General requirements
IEC 61850-4 System and project management
IEC 61850-5 Communication requirements for functions and device models
IEC 61850-6 Configuration description language for communication in electrical substations related to IEDs
IEC 61850-7-1 Basic communication structure for substation and feeder equipment Principles and models
IEC 61850-7-2 Basic communication structure for substation and feeder equipment Abstract communication service interface (ACSI)
IEC 61850-7-3 Basic communication structure for substation and feeder equipment Common data classes
ASAT Solutions Inc. 1-4 61850C-CG Version 1.00 Revision 001 Release: General
IEC 61850-7-4 Basic communication structure for substation and feeder equipment Compatible logical node classes and data classes
IEC 61850-8-1 Specific communication service mapping (SCSM) Mappings to MMS (ISO/IEC 9506-1 and ISO/IEC 9506-2) and to ISO/IEC 8802-3
IEC 61850-9-1 Specific communication service mapping (SCSM) Sampled values over serial unidirectional multi-drop point-to-point link
IEC 61850-9-2 Specific communication service mapping (SCSM) Sampled values over ISO/IEC 8802-3 2
IEC 61850-10 Conformance testing
IEC 61850-80-1 Ed. 1.0 Communication networks and systems for power utility automation Part 80-1: Guideline to exchange information from a CDC based data model using IEC 60870-5-101/104
ASAT Application Note << AN-12-05-001-DAP RS485 and LAN and Port Bridging Redundancy Overview R1.1>>
IEC 61850 Client Configuration Guilde 61850C-CG Version 1.00 Revision 001 Release: General 1-5
Chapter 1: Application Overview 1.1 Application Overview The IEC 61850 Client application is configured with DAPstudio and runs under the ASAT DAP Linux based embedded system to provide an interface to one or more remote IED units using the IEC 61850 communications protocol suite. The IEC 61850 Client acts as a master or client communication device, initiating data exchanges with remote devices (IEC 61850 Servers). The application is also capable of sending control commands to remote devices.
1.2 Core Functions The IEC 61850 client supports the flowing functions and commands: Test Group Note Conversion ICD and CID file into DAP 61850 Client configuration Two party application association (TPAA) Reporting data from server with periodic scan at logic device level Reporting unsolicited data with buffered report block Reporting unsolicited real-time data with un-buffered report block Execute Digital and Analog Controls command with Direct, SBO, Enhanced Direct and Enhanced SBO
Report GOOSE data NTP Time Sync Table 1 Core Functions Supported by DAP IEC-61850 Client
ASAT Solutions Inc. 1-6 61850C-CG Version 1.00 Revision 001 Release: General
1.3 Configuration Basic The DAP IEC 61850 client is designed to support data access from multiple remote devices (IEC 61850 Servers), with each remote device being configured individually (and possibly independently) to satisfy its own application requirements. Thus the configuration information for the remote devices must be completed and available to DAPstudio before starting the Client configuration process. This remote device configuration information can be loaded into DAPstudio from Substation Configuration Language (SCL) files. The SCL is specifically-formatted XML. The current version of DAPstudio only takes SCL file with ICD or CID extension. The definition for the ICD and CID file as below: ICD File - IED Capability Description: xml format file which gives complete description of the functions and features supported by the IED. Every IEC61850 supported IED will have the specific ICD file for every model which will be given by the manufacturer. In simple terms, ICD file is a biodata of the IED. ICD file is normally given by the IED manufacturer. CID File - Configured IED Description: describes an instantiated IED with all configuration parameters relevant for the IED. This file will be the final file generated from SCD file to download into the IED. CID file is final file to be extracted out from SCD. Typically, an IEC 61850 Client may only need to access a subset of the total data available from each of its associated remote devices. Using DAPstudio, a user will identify this subset of data and import the data into the configuration.
IEC 61850 Client Configuration Guilde 61850C-CG Version 1.00 Revision 001 Release: General 2-7
Chapter 2: Create and Modify Configuration This chapter outlines the sequence of steps needed to configure the IEC 61850 Client using the ASAT DAPstudio software. 2.1 Set Up Procedures 2.1.1 Stage 1 Prepare DAP Environment 1. Launch the DAPstudio and follow pop up dialog boxes to create a project. 2. In Device Information open the Property Window and: a. Set Redundant System to Enable if the configuration is going to be a redundant system; or set to Disable if not a redundant system. b. Select device type in Model drop down list to match to your hardware. c. Leave other parameters as default, and update them if necessary. 2.1.2 Stage 2 Create a Client Connection 2.1.2.1 Create a client by Import SCL file 3. After following step 2 above, open the Client Application window and press the <Create New> button to open Select Protocol dialog and highlight IEC61850, then <Next> button to bring up dialog to import SCL file. 4. Press the <Browse> to find ICD or CID file location, and press <Next> button to open IEC 61850 SCL Editor box. 5. Browse the tree structure of relay configuration information in the SCL Editor and select any number of items and configuration needed under each leaf of the tree structure, then press the <Finish> button to import objects needed for the client configuration. ASAT Solutions Inc. 2-8 61850C-CG Version 1.00 Revision 001 Release: General
Figure 1 Sample of IEC 61850 SCL Editor NOTE: In many cases the Data Set, Report Control Block or GOOSE definitions are not defined in the same Logic Device or Logic Node where the actual data objects need to be reported. When this happens, it is recommended to import the associated Logic Device/Logic Node. For example, in a SEL751A relay, all Data Sets, RCBs and GOOSE are defined under Logic Device CFG; Logic Node LLN0, it is recommended to import CFG$LLN0 also, even though there is no SCADA data that needs to be reported under this logic device. 6. Verify that an IEC 61850 connection was added into the DAP Client application window, and modify the connection IP address, if necessary, then the configuration is ready to download and run. 2.1.2.2 Create a Client by Loading from Device Library User can also load pre-configured IEC 61850 client from Device Library. To do that: 7. After following step 2 above, open the Client Application window, mark the Load from Device Library radio button and press the <Next> to open Define Device Information dialog box as shown in Figure 2 below. IEC 61850 Client Configuration Guilde 61850C-CG Version 1.00 Revision 001 Release: General 2-9
Figure 2 Sample of Pre-configured Device Loader 8. Select available Vendor and Device Model from drop down list and then press <Next> button twice, verify that a new client connection will be added in. Modify the connection IP address if necessary, then the configuration is ready to download and run. NOTE: If an IEC 61850 client configuration is created from the device library, the configuration can NOT be modified by re-loading ICD/CID file. Please do not use this function if you feel the configuration will be modified in the future.
ASAT Solutions Inc. 2-10 61850C-CG Version 1.00 Revision 001 Release: General
2.2 Data Report Configuration In the current version there are four ways to get IEC 61850 data reported with DAP studio: 1) Report by device or logic device level periodic scanning. 2) Report by buffered Report Control Block. 2) Report by Unbuffered Report Control Block. 3) Report by GOOSE subscript. ASAT will also implement Data Set polling report in the near future. 2.2.1 Device or Logic Device Scan The data scanning is a function that the client sends a read comment to target IEC 61850 server device with non-zero Polling Period in the logic device property window. It will obtain values for all data objects updated once every poll, no matter if an IED has a new event or not. The data scanning is most popular data polling function in IEC 61850, it uses less system resources, communication bandwidth and CPU time compared to other data report schemes. 2.2.2 Buffered Report Control Block The Buffered Report Control Block (BRCB) is an unsolicited, unconfirmed message, which is enabled by the client during the initialization and sent by a server when new events occur in the IED. The BRCB normally issues immediate reporting whenever events occur; it may also be buffered if there is a higher priority processor running, then the events will be buffered for transmission, such that data object values are not lost due to transport flow control constraints and loss of connection. To get BRCB reported properly, four important elements need to be configured in DAP: A server should have a predefined data set that is imported into the client properly. A BRCB that is associated with the data set above must be enabled. A Field option which associated with the BRCB above should be configured properly, e.g. for each RCB, the Reason Code must be enabled; for BRCB, the Entry ID must be enabled too. At least one of items for RBCB above should be enabled in Trigger Option table when BRCB is enabled, in most cases it should be Data Change. IEC 61850 Client Configuration Guilde 61850C-CG Version 1.00 Revision 001 Release: General 2-11
The BRCB provides SOE report function, and it can also provide COS reporting when the Integrity Poll or/and General Interrogation option is used. 2.2.3 Unbuffered Report Control Block The Unbuffered Report Control Block (URCB) is an unsolicited, unconfirmed message, which is enabled by the client during the initialization and sent by a server when new events occur in the IED. The URCB issues immediately for reporting whenever events occur, if no association exists, or if the transport data flow is not fast enough to support URCB, the events may be lost. To get URCB reported properly, four important elements need to be configured in DAP: A server should have a predefined data set and be imported into client properly; A URCB that is associated with the data set above must be Enabled; A Field option which associated with the URCB above should be configured properly, e.g. for each RCB, the Reason Code must be enabled, but the Entry ID is not necessary. At least one of items for URCB above should be enabled in Trigger Option table when URCB is enabled, in most cases it should be Data Change. The URCB provides SOE report too, and it can also provide COS reporting when the Integrity Poll or/and General Interrogation option is used. 2.2.4 GOOSE Receiver The GOOSE receiver in DAP IEC61850 client is a control model which provides a fast and reliable mechanism for receiving event data over a substation network with multicast MAC addressing. To receive a GOOSE message the DAP should have: A GOOSE associated data set imported. GOOSE report enabled in GOOSE Control table. A valid multicast MAC address should be entered in GSE Address sub- table and the address should match up with the destination MAC address that is configured on server side. NOTE: the valid GOOSE Multicast MAC address must be in range of 01 0C CD 01 00 00 to 01 0C CD 01 01 FF. ASAT Solutions Inc. 2-12 61850C-CG Version 1.00 Revision 001 Release: General
2.3 CPU Redundant and Port Bridging 2.3.1 CPU Redundant See <<AN-12-05-001-DAP RS485 and LAN and Port Bridging Redundancy Overview R1.1>> for detail. 2.3.2 Port Bridging See document above for more details, the document above will be integrated in the next document release.
IEC 61850 Client Configuration Guilde 61850C-CG Version 1.00 Revision 001 Release: General 2-13
2.4 Edit an Existing Client If a client configuration was created by importing from a SCL file, it can be modified at any level with the original SCL file. A user has no need to find or save the SCL file during the creation or modification, the DAP will automatically store the file into configuration. To modify the existing configuration do the following steps: 1. Open an existing project (or upload a configuration from DAP), highlight an IEC 61850 client logic device, right click the mouse button and then select Edit item from drop down menu to display a SCL Editor as shown in Figure 1. 2. Then repeat steps in Section 2.1.2.1 to modify the client configuration.
ASAT Solutions Inc. 3-14 61850C-CG Version 1.00 Revision 001 Release: General
Chapter 3: Configuration Tables and Parameters This chapter describes the purpose, possible values, and the recommended and default values for each of the fields within the Configurable IEC 61850 Client. The maximum number of records permitted for each configuration table is dependent on the system resources. In the following tables default values denoted as (blank) indicate that the default is an empty text string. 3.1 Device Information and Property Window The device information section is located at Device Information Properties. It is used for configuring the DAP device environment at the system level. For IEC61850 client configuration, there are some specific settings that need to be set in this section; please check on-screen messages for detail function and description on each field.
Field Name Descriptions Default Redundant System Disable/Enable option field for redundant system setting. If it is enabled, two LAN based DAP device are needed. Disable Max. Event Records Specify the maximum number of event records to be saved to historical database follow FIFO rules. 1000 Max. Fault Records Specify the maximum number of fault records to be saved to historical database follow FIFO rules. 1000 Max. Days of Historic Data Specify the maximum number of days that analog data is saved. When reach this number, the records will be deleted follow FIFO rules. 365 Max. Disk Usage (%) Specify the maximum number of days that analog data is saved. When reach this number, the records will be deleted follow FIFO rules. 85 Records Per Delete (%) Specify the percentage of records or days will be deleted once the records/days above reach Max. 10 IEC 61850 Client Configuration Guilde 61850C-CG Version 1.00 Revision 001 Release: General 3-15
Watchdog Enabled/Disable hardware watchdog. Enabled Console Hotkey The hotkey to login VT100 F1 Logout Delay Delay to trigger console mode auto logout after no keyboard input in seconds 300 Hardware Model Options for available hardware list. DAPMini Time Sync Standby CPU Enable/Disable time sync to standby CPU, when enabled the active CPU will send T-sync command to standby CPU once every 30 seconds Enabled RTDB Sync Period(min) Time interval in minutes to sync real time database on redundant CPUs 10 Timeout for all IED offline Time delay between a CPU becomes active and declares all IED offline. After this waiting period an all- IED-failed condition will set the current CPU to standby. -1 means function disabled. Note: for redundant IEC 61850 system this field should always be disabled. 60 Interval to monitor client poll Specify a time interval in seconds to monitor client channels of an active CPU. 0 or -1 means disabled. 0 Interval for checking Network Interval in seconds for redundant LAN activity checking. If there is no activity within this period the CPU will set the partner CPU to offline. 15 Substation name Specify substation name for system management Substation Redundant IP Not in use Disabled First Online CPU Active When enabled the first online CPU will be the active one; When disabled the CPU A will be always active once it is online. Note: for IEC 61850 redundant systems with RCB or GOOSE enabled data reports, it is recommended to set this field to Enabled.
ASAT Solutions Inc. 3-16 61850C-CG Version 1.00 Revision 001 Release: General
3.2 IEC 61850 Connection Property The IEC 61850 Connection Property is located at: Client Application LINKx Property Window. It is used to define IEC61850 connection information. Field Name Descriptions Default Object Name Define a connection name IEC61850 Comm Statistic Interval (s) Interval to calculate ratio of frame errors and frame flow speed to measure the communication channel health 60 Threshold of comm. error (%) Max number of communication errors allowed to calculate communication channel health. 1 Device Version IEC61850 driver version 1.0
3.3 IEC 61850 Server IP and Port Configuration The IEC 61850 Server IP and Port configuration table is located at: Client Application LINKx Port Group Window. It is used to define IEC61850 server (IED) IP address and Port information. Field Name Descriptions Default Driver Name Function is not used for IEC 61850 CDPPPort Server IP Server, IED, destination relays IP address Server Port Server, IED, destination relays Port number 102 Client IP Client IP address used for monitoring system
3.4 OSI Component Settings The IEC 61850 OSI component setting table is located at: Client Application LINKx Protocol Parameter. This section is selected automatically by the system, some of the items are not implemented in the current version there is no need to change any settings in this section. Field Name Descriptions Default
IEC 61850 Client Configuration Guilde 61850C-CG Version 1.00 Revision 001 Release: General 3-17
3.5 Client Device or Logic Device Settings The IEC 61850 client has limited user setting requirements, but most items required to be configured are located at this section. To launch the configuration table, go to: Client Application LINKx Device Bus Device Property Window. Field Name Descriptions Default LDInst Defined device or logic device name. In most of cases this name is imported from SCL file, no need to be changed. Note: that the LD name MUST be same as what is on the destination server, otherwise the communication will fail.
IED Name Defined physical IED device name. It is imported from SCL file, cannot be changed by a user. Note: that the name MUST be same as what on destination IED, otherwise the communication will fail.
IED Type IED type information. It is imported from SCL file, cannot be changed by a user.
Manufacturer IED vendor name. It is imported from SCL file, cannot be changed by a user.
Configuration Version IED version and firmware information, imported from SCL file, cannot be changed by a user.
Polling Period MMS message scanning interval in milliseconds. Note: for multiple connections or multiple logic device configurations, only one of the devices is being scanned at a time, the actual polling rate on each device could be much lower than what is configured. 5000 Query Timeout The wait period for query response in milliseconds. 10000 Connect Retry Interval Retry interval when network is dropped. 5000 Datasets An available pre-defined data set list, and objects under each data set. It is imported from SCL file, no deeds to be changed by a user.
Report Control A list of pre-defined BRCB and URCB. Four items need to be configured here; Enable/Disable a RCB. Set the Buffer Time (for future use). Set Integrity reporting period for selected RCB, if needed. Define RCB to CPU A or CPU B for
ASAT Solutions Inc. 3-18 61850C-CG Version 1.00 Revision 001 Release: General
redundant CPU configuration. RCB Field Option Field options for each RCB; Note: Each RCB must have Reason Code enabled. BRCB type must have Entry ID enabled. Buffer Overflow is not needed for URCB.
RCB Trigger Option Setting option to trigger unsolicited data report. In most cases the Data Change option should be enabled, others may be optional.
GOOSE Control Enable/Disable GOOSE report. Note: must have valid multicast MAC address in GSE Address sub-table.
IEC 61850 Client Configuration Guilde 61850C-CG Version 1.00 Revision 001 Release: General 4-19
Chapter 4: Errors and Troubleshooting This chapter describes errors that most often occur during configuration or communication and simple troubleshooting tips for these errors.
F1: Device Off-line with Cross sign.
Cause: Incorrect DAP hardware model is selected. Configuration is not downloaded properly. Remedy: Select correct DAP model, if your hardware is not listed please contact ASAT for further information. Save and re-download the configuration. F2: Device off-line and device icon without flashing
Cause: DAPstudio is not connected Destination IED unreachable or non-existent. Server IP address is wrong. ASAT Solutions Inc. 4-20 61850C-CG Version 1.00 Revision 001 Release: General
Server TCP Port is wrong. Remedy: Make sure the DAPstudio is connected, do Clear Saved Login Info and re- connect to DAP. Make sure the server IED is powered on and on a reachable network. Set the server IP address and Port properly, save and re-download the configuration.
F3: Device icon is flashing but points are off-line, not updating values/states
Cause: SCL file doesnt match with what actually is running in relay (IED). LDInst name does not match with actual name inside relay. IED Name does not match with actual name inside relay. Polling Period, RCB and GOOSE, none of them are enabled. Remedy: Make sure the SCL file matches the configuration information in the IED and re-create client configuration with suitable SCL file, if necessary. It is recommended to use proper tools to upload and save the SCL file direct from relay (IED), then create IEC 61850 client with this SCL file. Enable at least one of the data report scheme.
F4: RCB does not report object values/states Cause: Enable RCB requests failed to write during system start up (in Wireshark capture, it may show Object-Temporary-Unavailable). IEC 61850 Client Configuration Guilde 61850C-CG Version 1.00 Revision 001 Release: General 4-21
Required point(s) is(are) not included in the associated Data Set (in Wireshark capture, it may show Object-non-existent). RCB is not enabled. Field Option and Trigger options are not set properly. Remedy: May have multiple clients connected to an IED with same RCB name, disconnect other clients and try again. Add point(s) into associated Data Set. Make sure RCB set to Enabled. Make sure Field Options and Trigger Options are set properly.
F5: In Redundant system the RCB works on one of CPU only Cause: Most of IEDs do not accept write command from multiple clients, for instance, if a RCB is enabled by CPU A, it cannot be enabled by CPU B at same time. It will show Object-Temporary-Unavailable. Remedy: Set the IED report control block with multi-instance, if possible. Enable RCB on CPU A and CPU B with different RCB names but map each RCB to the same Data Set or objects.
F6: GOOSE message does not report object values/states Cause: Enabled GOOSE requests failed to write during system start up (in Wireshark capture, it may show Object-Temporary-Unavailable). Required point(s) is(are) not included in associated Data Set (in Wireshark capture, it may show Object-non-existent). GOOSE is not enabled. Multicast address is not set or not same as GOOSE transmission. Remedy: ASAT Solutions Inc. 4-22 61850C-CG Version 1.00 Revision 001 Release: General
May have multiple clients connected to IED with same GOOSE, disconnect other clients try again. Add point(s) into associated Data Set. Make sure GOOSE is set to Enabled. Make sure GSE address is set properly. Make sure the MAC address matchs up with the GOOSE transmission side. IEC 61850 Client Configuration Guilde 61850C-CG Version 1.00 Revision 001 Release: General 4-23
Appendix A: Abbreviations Code Point Type Notes ACSI abstract communication service interface
ASDU application service data unit
BRCB BUFFERED-REPORT-CONTROL-BLOCK
CDC common data class
FC Function Constrains Doc 7-2, table 18 GI general interrogation
PIXIT protocol implementation extra Information for Testing
SAV sampled analogue value (IEC 61850-9)
SCD substation configuration description.
SCL substation configuration language
SCSM specific communication service mapping
ASAT Solutions Inc. 4-24 61850C-CG Version 1.00 Revision 001 Release: General
SGCB SETTING-GROUP-CONTROL-BLOCK
SoE sequence-of-events
SSD system specification description.
SV sampled values
SVC sampled value control
TPAA TWO-PARTY-APPLICATION-ASSOCIATION
URCB UNBUFFERED-REPORT-CONTROL-BLOCK
USVCB UNICAST-SAMPLED-VALUE-CONTROL-BLOCK
CODED ENUM Coded Enumeration; Ordered set of values, defined where type is used. Note that custom extensions shall not be allowed. Type shall be mapped tp an efficient encoding in a SCSM.
4.1 Write HTML Code That Displays Three Hyperlinks To Different Websites. The Websites Should Open in A New Window When The User Clicks On The Hyperlinks