1. Trang chủ
  2. » Kỹ Thuật - Công Nghệ

PCS 9705s x communication protocol manual EN overseas general x r1 10

145 16 0

Đang tải... (xem toàn văn)

Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống

THÔNG TIN TÀI LIỆU

Thông tin cơ bản

Tiêu đề PCS 9705s X Communication Protocol Manual
Trường học NR Electric Co., Ltd.
Chuyên ngành Communication Protocol
Thể loại manual
Năm xuất bản 2019
Thành phố N/A
Định dạng
Số trang 145
Dung lượng 4,88 MB

Các công cụ chuyển đổi và chỉnh sửa cho tài liệu này

Cấu trúc

  • Preface

    • About This Document

    • Safety Information

    • Instructions and Warnings

    • Document Conventions

    • Warranty

    • Document Structure

    • Document Revision History

  • 1 Communication Modules

    • 1.1 CPU Module

    • 1.2 Communication Applications

    • 1.3 Ethernet Network Structures

      • 1.3.1 Standardized Ethernet Cable

      • 1.3.2 Relevant Settings

      • 1.3.3 Ethernet Interface Setup

      • 1.3.4 Port Bonding Operation

      • 1.3.5 Star-shaped

      • 1.3.6 PRP Structure

      • 1.3.7 HSR Structure

      • 1.3.8 RSTP Ring Structure

    • 1.4 Serial Connection

      • 1.4.1 Relevant Settings

      • 1.4.2 EIA-485 Interface

        • 1.4.2.1 Bus Termination

        • 1.4.2.2 Connection Topology

        • 1.4.2.3 Biasing

  • 2 IEC 61850

    • 2.1 Relevant Settings

    • 2.2 Communication Profiles

    • 2.3 MMS Communication Network Deployment

      • 2.3.1 SingleNet: Single Network Mode

      • 2.3.2 HotStdby: Hot Standby Mode

      • 2.3.3 ColdStdby: Cold Standby Mode

    • 2.4 Server Data Organization

      • 2.4.1 Digital Status Values

      • 2.4.2 Analog Values

      • 2.4.3 Protection Logical Nodes

      • 2.4.4 LLN0 and Other Logical Nodes

    • 2.5 Protocol Properties and Services

      • 2.5.1 Timestamps

      • 2.5.2 Logical Node Name Prefixes

      • 2.5.3 Reporting

      • 2.5.4 File Transfer

      • 2.5.5 Setting Group

      • 2.5.6 Log

      • 2.5.7 Generic Object Oriented Substation Events

        • 2.5.7.4 Sending

        • 2.5.7.5 Receiving

      • 2.5.8 Sampled Value

    • 2.6 Invalid Data and Link Failure

    • 2.7 Processing Mechanism During Network Storm

    • 2.8 Maintenance Mechanism

    • 2.9 Protocol Implementation Conformance Statement (PICS)

    • 2.10 Model Implementation Conformance Statement (MICS)

    • 2.11 TIssues Conformance Statement (TICS)

    • 2.12 Protocol Implementation eXtra Information for Testing (PIXIT)

  • 3 DNP3

    • 3.1 Relevant Settings

    • 3.2 Application Layer Functions

      • 3.2.1 Function Code

      • 3.2.2 Supported Object List

      • 3.2.3 Communication Table Configuration

      • 3.2.4 Analog Input and Output Configuration

      • 3.2.5 Binary Output Configuration

      • 3.2.6 Unsolicited Messages

      • 3.2.7 Class Configuration

  • 4 IEC 60870-5-103

    • 4.1 Relevant Settings

    • 4.2 Physical Layer and Link Layer

    • 4.3 Initialization

    • 4.4 Time Synchronization

    • 4.5 Spontaneous Events

    • 4.6 General Interrogation

    • 4.7 General Service

    • 4.8 Disturbance Records

  • 5 Modbus

    • 5.1 Relevant Settings

    • 5.2 Binary State Communication

    • 5.3 Analog Data Communication

    • 5.4 Settings Communication

    • 5.5 Remote Control

    • 5.6 Remote Regulation

    • 5.7 Diagnostics Information

    • 5.8 Download Settings

    • 5.9 Abnormal Information

  • ANNEX A PICS

    • A.1 Introduction

    • A.2 For IEC 61850 Edition 1

      • A.1.1 ACSI Basic Conformance Statement

      • A.1.2 ACSI Models Conformance Statement

      • A.1.3 ACSI Services Conformance Statement

    • A.2 For IEC 61850 Edition 2

      • A.2.1 ACSI Basic Conformance Statement

      • A.2.2 ACSI Models Conformance Statement

      • A.2.3 ACSI Services Conformance Statement

  • ANNEX B MICS

    • B.1 Introduction

    • B.2 For IEC 61850 Edition 1

      • B.2.1 Logical Nodes List

      • B.2.2 Logical Node Extensions

      • B.2.3 New Logical Nodes

      • B.2.4 Extended Logical Nodes

        • B.2.4.1 LLN0: Logical node zero

        • B.2.4.2 LPHD: Physical device information

        • B.2.4.3 CILO: Interlocking

        • B.2.4.4 GGIO_SPC: Generic process I/O

        • B.2.4.5 GGIO_SG: Generic process I/O

        • B.2.4.6 MMXU: Measurement

        • B.2.4.7 PTRC: Protection trip conditioning

        • B.2.4.8 RDRE: Disturbance recorder function

        • B.2.4.9 RSYN: Synchronism-check

    • B.3 For IEC 61850 Edition 2

      • B.3.1 Logical Nodes List

      • B.3.2 Logical Node Extensions

      • B.3.3 New Logical Nodes

      • B.3.4 Extended Logical Nodes

        • B.3.4.1 LLN0: Logical node zero

        • B.3.4.2 LPHD: Physical device information

        • B.3.4.3 CILO: Interlocking

        • B.3.4.4 GGIO_SPC: Generic process I/O

        • B.3.4.5 GGIO_SG: Generic process I/O

        • B.3.4.6 MMXU: Measurement

        • B.3.4.7 PTRC: Protection trip conditioning

        • B.3.4.8 RDRE: Disturbance recorder function

        • B.3.4.9 RSYN: Synchronism-check

  • ANNEX C TICS

    • C.1 Introduction

    • C.2 Part 6

    • C.3 Part 7-1

    • C.4 Part 7-2

    • C.5 Part 7-3

    • C.6 Part 7-4

    • C.7 Part 8-1

  • ANNEX D PIXIT

    • D.1 Introduction

    • D.2 For Documentation

    • D.3 For Association Model

    • D.4 For Server Model

    • D.5 For Data Set Model

    • D.6 For Substitution Model

    • D.7 For Setting Group Control Model

    • D.8 For Reporting Model

    • D.9 For Logging Model

    • D.10 For GOOSE Publish Model

    • D.11 For GOOSE Subscribe Model

    • D.12 For GOOSE Performance

    • D.13 For Control Model

    • D.14 For Time Synchronisation Model

    • D.15 For File Transfer Model

    • D.16 For Service Tracking Model

Nội dung

Introduction

This document specifies the Protocol Implementation eXtra Information for Testing (PIXIT) of the

The IEC 61850 interface in this device, along with the PICS and MICS specifications, establishes the foundation for conformance testing as outlined in IEC 61850-10 The PIXIT entries provide essential information that is not included in the PICS, MICS, TICS documents, or the SCL file.

For Documentation

ID Ed Description Value / Clarification

Do1 2 How to expose required firmware versions not present in the datamodel The versions will be displayed on LCD

For Association Model

ID Ed Description Value / Clarification

As1 1 Maximum number of clients that can set-up an association simultaneously 16

As2 1,2 TCP_KEEPALIVE value The recommended range is 1.20s

As3 1,2 Lost connection detection time 42 seconds

As4 - Authentication is not supported yet

As5 1,2 What association parameters are necessary for successful association

Transport selector Calling: N Called: Y Session selector Calling: N Called: Y Presentation selector Calling: N Called: Y

As6 1,2 If association parameters are necessary for association, describe the correct values e.g

Transport selector 0001 Session selector 0001 Presentation selector 00000001

As7 1,2 What is the maximum and minimum MMS PDU size Max MMS PDU size 65k bytes

Min MMS PDU size 1024 bytes As8 1,2 What is the maximum start up time after a power supply interrupt 60 seconds

ID Ed Description Value / Clarification

Does this device function only as test equipment?

(test equipment need not have a non-volatile configuration; but it cannot be part of the substation automation system)

For Server Model

Sr1 1,2 Which analogue value (MX) quality bits are supported (can be set by server)

Sr2 1,2 Which status value (ST) quality bits are supported

(can be set by server)

Sr3 - What is the maximum number of data object references in one GetDataValues request Deprecated

Sr4 - What is the maximum number of data object references in one SetDataValues request Deprecated

Sr5 1 Which Mode values are supported

For Data Set Model

ID Ed Description Value / Clarification

Ds1 1 What is the maximum number of data elements in one data set (compare ICD setting) 256

How many persistent data sets can be created by one or more clients

(this number includes predefined datasets)

Ds3 1 How many non-persistent data sets can be created by one or more clients Not Supported

For Substitution Model

ID Ed Description Value / Clarification

Sb1 1 Are substituted values stored in volatile memory Y

For Setting Group Control Model

ID Ed Description Value / Clarification

Sg1 1 What is the number of supported setting groups for each logical device See SGCB value

What is the effect of when and how the non-volatile storage is updated

The value is stored into NOR FLASH in IED, and after storage is completed the value CnfEdit is set to FALSE

Sg3 1 Can multiple clients edit the same setting group Y

Sg4 1 What happens if the association is lost while editing a setting group

The SE values changes are lost, the EditSG is reset to 0

Sg5 1 Is EditSG value 0 allowed Y

ID Ed Description Value / Clarification

Sg6 2 When ResvTms is not present how long is an edit setting group locked

Keep the state before the association is lost

For Reporting Model

ID Ed Description Value / Clarification

Rp1 1 The supported trigger conditions are

(compare PICS) integrity Y data change Y quality change Y data update Y general interrogation Y

Rp2 1 The supported optional fields are sequence-number Y report-time-stamp Y reason-for-inclusion Y data-set-name Y data-reference Y buffer-overflow Y entryID Y conf-rev Y segmentation Y

Can the server send segmented reports (when not supported the device shall refuse an association request with a smaller than minimum PDU size)

Mechanism on second internal data change notification of the same analogue data value within buffer period (Compare IEC 61850-7-2 §14.2.2.9) Send report immediately

Rp5 1 Multi client URCB approach

(compare IEC 61850-7-2:2003 §14.2.1) Each URCB is visible to all clients

Rp6 - What is the format of EntryID Deprecated

Rp7 1,2 What is the buffer size for each BRCB or how many reports can be buffered 200 reports and less than50k bytes storage memory

Rp8 - Pre-configured RCB attributes that are dynamic, compare SCL report settings Deprecated

May the reported data set contain:

Rp10 1,2 What is the scan cycle for binary events

ID Ed Description Value / Clarification

Rp11 1 Does the device support to pre-assign a RCB to a specific client in the SCL N

After restart of the server is the value of ConfRev restored from the original configuration or retained prior to restart Restored from original configuration

Does the server accept any client to configure / enable a BRCB with

What fields are used to do the identification?

What is default value for BRCB.ResvTms if client does not write or ResvTms not exposed in the control block (must be >= 0)

0 milliseconds BRCB ResvTms not supported

For Logging Model

ID Ed Description Value / Clarification

What is the default value of LogEna

(Compare IEC 61850-8-1 §17.3.3.2.1, the default value should be FALSE)

Lg2 - What is the format of EntryID Deprecated

Are there multiple Log Control Blocks that specify the Journaling of the same MMS NamedVariable and TrgOps and the Event Condition

Single Journal Entry (specify the event condition)

Lg4 1 Pre-configured LCB attributes that cannot be changed online Y

For GOOSE Publish Model

ID Ed Description Value / Clarification

Gp1 1,2 Can the test (Ed1) / simulation (Ed2) flag in the published GOOSE be set Y

Gp2 1 What is the behaviour when the GOOSE publish configuration is incorrect

Gp3 1,2 Published FCD supported common data classes are SPS

Gp4 1,2 What is the maximum value of TAL (maxTime)

Is it fixed or configurable Configured by GoCB MaxTime

ID Ed Description Value / Clarification

Gp5 1,2 What is the fastest retransmission time Configured by GoCBMinTime

Gp6 - Can the GOOSE publish be turned on / off by using

Deprecated See PICS - SetGoCBValues Gp7 1,2 What is the initial GOOSE sqNum after restart sqNum = 1

May the GOOSE data set contain:

Gp9 1,2 Does Server or ICT refuse GOOSE payload dataset length greater than SCSM supports? Y

For GOOSE Subscribe Model

ID Ed Description Value / Clarification

What elements of a subscribed GOOSE message are checked to decide the message is valid and the allData values are accepted? If yes, describe the conditions

• the VLAN tag may be removed by an Ethernet switch and shall not be checked

• the simulation flag shall always be checked (Ed2)

Y out-of-order dataset members Note1:See Gs_EX1 for checking rules

Note2:GoID only checked if different from SCL An Empty GoID(GoID entry absent) is not recognized as invalid GOOSE

When is a subscribed GOOSE marked as lost

If a new GOOSE message is not received within twice the time allowed to live (TAL) value, a 'link_err' warning will be triggered However, once a new message is received, data changes can resume, and the warning will be cleared.

What is the behaviour when one or more subscribed GOOSE messages is not received or syntactically incorrect (missing GOOSE)

A warning(Entry Gs_EX1 link_err)is activated by report message, which indicates that the message is not received

ID Ed Description Value / Clarification

Gs4 1,2 What is the behaviour when a subscribed GOOSE message is out-of-order Not checked

Gs5 1,2 What is the behaviour when a subscribed GOOSE message is duplicated Discarded

Gs6 1 Does the device subscribe to GOOSE messages with/without the VLAN tag

May the GOOSE data set contain:

Gs8 1,2 Subscribed FCD supported common data classes are SPS

Gs9 1,2 Are subscribed GOOSE with test=T (Ed1) / simulation=T (Ed2) accepted in test/simulation mode Y

Gs10 1,2 Max number of dataset members 256

Gs11 1 Is Fixed-length encoded GOOSE supported Not supported

When subscribed GOOSE messages have incorrect information:

When subscribed GOOSE messages have another incorrect information:

- alldata (subscribed member data type mismathed)

The messages will be discarded and the 'link_err' warning will be activated after 2*TAL

All data of the messages will not be accessed and the ‘cfg_err’ warning will be activated immediately.

For GOOSE Performance

ID Ed Description Value / Clarification

Gf1 1,2 Performance class P1(Ed2) P2/P3(Ed1)

Gf2 1,2 GOOSE ping-pong processing method Scan cycle based

Gf3 1,2 Application logic scan cycle (ms)

ID Ed Description Value / Clarification

Maximum number of data attributes in GOOSE dataset (value and quality has to be counted as separate attributes)

For Control Model

ID Ed Description Value / Clarification

Ct1 1 What control models are supported

(compare PICSICD file enums for Ed2)

Ct2 1,2 Is the control model fixed, configurable and/or dynamic Dynamic

Ct3 - Is TimeActivatedOperate supported (compare PICS or SCL) Deprecated

Ct4 - Is “operate-many” supported (compare sboClass) Deprecated, see sboClass in datamodel (ICD)

Will the DUT activate the control output when the test attribute is set in the SelectWithValue and/or Operate request (when N test procedure Ctl2 is applicable) N

Ct6 - What are the conditions for the time (T) attribute in the

SelectWithValue and/or Operate request Deprecated

Ct7 - Is pulse configuration supported (compare pulseConfig) Deprecated

What is the behaviour of the DUT when the check conditions are set

Is this behaviour fixed, configurable, online changeable

DUT uses the check value to perform the check (Ed2)

ID Ed Description Value / Clarification

Ct9 1,2 Which additional cause diagnosis are supported

N Parameter-change-in-execution ( Ed1 semantics)

N Parameter-change-in-execution (Ed2 semantics)

Ct10 1,2 How to force a “test-not-ok” respond with

SelectWithValue request e.g invalid orCat value

Ct11 1,2 How to force a “test-not-ok” respond with Select request e.g.object already seletected by another client

Ct12 1,2 How to force a “test-not-ok” respond with Operate request

DOns: e.g invalid orCat value SBOns: e.g invalid orCat value DOes: e.g invalid orCat value SBOes: e.g invalid orCat value

ID Ed Description Value / Clarification

Ct13 1,2 Which origin categories are supported / accepted

Ct14 1,2 What happens if the orCat value is not supported or invalid

DOns: Negative response SBOns: Negative response DOes: Negative response SBOes: Negative response

Does the IED accept a SelectWithValue / Operate with the same control value as the current status value

DOes: N Position-reached SBOes: N Position-reached Configurable N

Ct16 1 Does the IED accept a select/operate on the same control object from 2 different clients at the same time

Does the IED accept a Select/SelectWithValue from the same client when the control object is already selected (TIssue #334)

Ct19 - Can a control operation be blocked by Mod=Off or

[On-]Blocked (Compare PIXIT-Sr5) Deprecated Ct20 1,2 Does the IED support local / remote operation Y

Does the IED send an InformationReport with LastApplError as part of the Operate response- for control with normal security

Ct22 2 How to force a “parameter-change-in-execution” SBOns: Not supported

Ct23 1,2 How many SBOns/SBOes control objects can be selected at the same time?

Can a controllable object be forced to keep its old state e.g Internal Controllable Objects may not be accessible to force this, whereas a switch like Circuit Breaker outside the DUT can?

ID Ed Description Value / Clarification

When CDC=DPC is supported, is it possible to have DPC (Controllable Double Point) go to the intermediate state? (00)

Name an enhanced security point (if any) with a finite operate timeout specify the timeout (in milliseconds)

No DOes points have timeout

Ct27 2 Does the IED support control objects with external signals?

For Time Synchronisation Model

ID Ed Description Value / Clarification

Tm1 1 What time quality bits are supported (may be set by the IED)

Describe the behaviour when all time server(s) cease to respond

What is the time server lost detection time

Assert CNS after lost detection time

Tm3 1,2 How long does it take to take over the new time from time server 35 seconds

Tm4 1,2 When is the time quality bit “ClockFailure” set Cannot be tested

Tm5 1 When is the time quality bit “Clock not Synchronized” set

CNS is set according to PIXIT Tm2

When connection to all time servers is lost (see PIXIT-Tm2)

Tm6 - Is the timestamp of a binary event adjusted to the configured scan cycle Deprecated

Tm7 1 Does the device support time zone and daylight saving Y

ID Ed Description Value / Clarification

Tm8 1,2 Which attributes of the SNTP response packet are validated

Y Leap indicator not equal to 3

Y Mode is equal to SERVER

N OriginateTimestamp is equal to value sent by the SNTP client as Transmit Timestamp

N RX/TX timestamp fields are checked for reasonableness

Tm9 1,2 Do the COMTRADE files have local time or UTC time and is this configurable

For File Transfer Model

ID Ed Description Value / Clarification

What is the structure of files and directories

Where are the COMTRADE files stored

Are COMTRADE files zipped and what files are included in each zip file

Not zipped, files with suffix:.hdr,.cfg and dat Ft2 1,2 Directory names are separated from the file name by “/”

Ft3 1 The maximum file name size including path

Ft4 1,2 Are directory/file name case sensitive Case sensitive

Ft5 1,2 Maximum file size for SetFile Not supported

Ft6 1 Is the requested file path included in the MMS fileDirectory respond file name

Ft7 1 Is the wild card supported in the MMS fileDirectory request

Ft8 1,2 Is it allowed that 2 clients get a file at the same time Y same file

Y different files Ft9 1,2 Which files can be deleted The files in the directory: COMTRADE

For Service Tracking Model

ID Ed Description Value / Clarification

Tr1 2 Which ACSI services are tracked by LTRK.GenTrk SetEditSGValue

Ngày đăng: 13/07/2021, 10:51

TỪ KHÓA LIÊN QUAN

🧩 Sản phẩm bạn có thể quan tâm