154 Practical Modern SCADA Protocols: DNP3, 60870.5 and Related Systems The device profile document also lists many configuration details including default configurations for confirmations, retries and other details. All of these need to be checked for compatibility with the planned implementation. Confirming interoperability: • Determine DNP3 polling mode to be used • Determine range of slave devices • Assemble device profile documents for range of slave devices • Determine minimum required DNP3 level • Determine functions above this level that will require support • Determine data objects above selected base level that will require support • Examine device profiles for RTUs and establish compatibility with IEDs • Examine device profiles for master station and establish compatibility with RTUs 6.3 Implementation rules and recommendations The following sub-sections summarize rules and recommendations that appear in the subset definition document DNP3 Subset Definitions, Version 2, Nov 1995. These rules and recommendations provide information that extends and clarifies that contained in the Basic Four documents. 6.3.1 Error responses Error responses are defined to cope with side-effects of having levels. These are the possibility that a device of one level will be polled for data objects that it cannot provide. Types: • Request not valid for its level • Request not valid for the particular device These are reported by the internal indications bits 0–2. Event objects are also a special case, because although they are not tied to a physical device and they may not exist at a given time, because there may be no new events to report. In this case the device must provide a null response rather than a ‘requested objects unknown’ response.
6.3.2 Data classes and events Advanced considerations of distributed network protocol 155 The simplest method of referencing data in requests in DNP3 is to call for objects by class. This in fact is a fundamental assumption behind the minimum implementation subsets, which at their lowest level depend on the use of calls by class to obtain many objects. This is provided for by requiring that all devices have their static data objects assigned to class 0, and all event objects assigned to one of the other classes. The sub-set document defines a relationship between event type object variations and class. Event type object variations are required to be assigned by default as class 1, 2 or 3, but not class 0. Class 0 is to be assigned by default to static data points only. Level 3 devices must allow a master to enable or disable event reporting for a point. To enable event reporting the master would assign the point to required data class 1, 2 or 3. To disable event reporting the master would assign the point to class 0. Level 1 or 2 devices do not need to support enabling or disabling of event reporting by the master. For these devices, default assignments are required to be in-built. Rules: 6.3.3 Default variation • All static objects are by definition class 0 • Event objects are by definition in class 1, 2 or 3 (may be configurable) • All event objects must be assigned by default to class 1, 2 or 3 • Level 3 slave devices must allow disabling of event reporting If a master request does not specify a particular variation for a point, then the slave must send the default variation. This may be configurable. This occurs when the master requests by class, or uses object variation zero. 6.3.4 Order of responses A slave must preserve the sequence of event order when responding requests for data by class. In particular, when a read request calls for multiple classes, the event data must not be returned in class groups, but rather in sequence of occurrence. 6.3.5 Actions on slave device startup The following actions must occur on startup of a slave device: • The device restart IIN bit must be set • If configured for unsolicited responses, it must send one on startup • This response must contain either no data, or all static data • This response may also contain unreported event data. If provided, these must be included in the message prior to the static data It is recommended that if a device does not report all of its static data on startup, the master should immediately poll for all static and event data.
Practical Modern SCADA Protocols: D
Practical Modern SCADA Protocols: D
Contents Preface ..................
Contents vii 12.6 Frame reception .
Preface ix Chapter 3: Open SCADA pr
1 Introduction Objectives When you
Introduction 3 Figure 1.2 PC to IED
Introduction 5 The interconnection
Introduction 7 a number of sub-path
Introduction 9 The Internet protoco
Introduction 11 Outside the utiliti
Fundamentals of SCADA communication
Fundamentals of SCADA communication
Key features of SCADA software incl
Fundamentals of SCADA communication
2.2.2 Control processor unit (or CP
Fundamentals of SCADA communication
Fundamentals of SCADA communication
Fundamentals of SCADA communication
2.5.2 Multi-point architecture (Mul
2.6 Communication philosophies Fund
Fundamentals of SCADA communication
Fundamentals of SCADA communication
Fundamentals of SCADA communication
Pin 8 - Data carrier detect (DCD) F
2.7.6 Synchronous communications 2.
The two most common modes of operat
2.8.3 Error control/flow control Fu
Fundamentals of SCADA communication
Fundamentals of SCADA communication
Fundamentals of SCADA communication
Fundamentals of SCADA communication
Fundamentals of SCADA communication
Fundamentals of SCADA communication
Fundamentals of SCADA communication
Fundamentals of SCADA communication
3 Open SCADA protocols DNP3 and IEC
3.2.2 DNP 3.0 and IEC 60870 protoco
4.2 Interoperability and open stand
Preview of DNP3 69 The DNP3 User Gr
Preview of DNP3 71 The capability t
5 Fundamentals of distributed netwo
Fundamentals of distributed network
Fundamentals of distributed network
Fundamentals of distributed network
Fundamentals of distributed network
5.3.6 Full-duplex procedures Fundam
Fundamentals of distributed network
Fundamentals of distributed network
Fundamentals of distributed network
Fundamentals of distributed network
Fundamentals of distributed network
Fundamentals of distributed network
Fundamentals of distributed network
Fundamentals of distributed network
The message sequences are shown in
Fundamentals of distributed network
Fundamentals of distributed network
Fundamentals of distributed network
The following notes apply to these
Fundamentals of IEC 60870-5 207 Typ
Fundamentals of IEC 60870-5 209 Typ
Fundamentals of IEC 60870-5 211 Whe
Fundamentals of IEC 60870-5 213 8.5
Fundamentals of IEC 60870-5 215 to
Fundamentals of IEC 60870-5 217 Mas
Fundamentals of IEC 60870-5 219 Qua
Fundamentals of IEC 60870-5 221 Key
Fundamentals of IEC 60870-5 223 SVA
Fundamentals of IEC 60870-5 225 Key
Fundamentals of IEC 60870-5 227 DCO
8.6.4 Qualifier information element
Key - QOC Qualifier of command QU Q
Fundamentals of IEC 60870-5 233 SCQ
Fundamentals of IEC 60870-5 235 LOF
Fundamentals of IEC 60870-5 237 FBP
Fundamentals of IEC 60870-5 239 In
Fundamentals of IEC 60870-5 241 Typ
Fundamentals of IEC 60870-5 243 Typ
Fundamentals of IEC 60870-5 245 Typ
Fundamentals of IEC 60870-5 247 Val
Type 11 Measured, scaled value Fund
Fundamentals of IEC 60870-5 251 Typ
Fundamentals of IEC 60870-5 253 Typ
Fundamentals of IEC 60870-5 255 Val
Type 20 Packed single-point with st
Fundamentals of IEC 60870-5 259 Pro
Fundamentals of IEC 60870-5 261 Typ
Fundamentals of IEC 60870-5 263 Typ
Fundamentals of IEC 60870-5 265 Typ
Fundamentals of IEC 60870-5 267 8.7
Fundamentals of IEC 60870-5 269 Typ
Fundamentals of IEC 60870-5 271 Typ
Fundamentals of IEC 60870-5 273 Typ
Fundamentals of IEC 60870-5 275 Typ
Fundamentals of IEC 60870-5 277 Typ
Fundamentals of IEC 60870-5 279 Typ
Fundamentals of IEC 60870-5 281 Typ
Fundamentals of IEC 60870-5 283 Typ
Fundamentals of IEC 60870-5 285 Val
9.1.1 Station initialization Advanc
9.1.2 Data acquisition Advanced con
Advanced considerations of IEC 6087
Advanced considerations of IEC 6087
In Figure 9.4 the following time sy
Advanced considerations of IEC 6087
Basic application functions: 9.2.3
Advanced considerations of IEC 6087
Advanced considerations of IEC 6087
Advanced considerations of IEC 6087
10 Differences between DNP3 and IEC
Data objects: Differences between D
10.2 Which one will win? Difference
Intelligent electronic devices (IED
11.2.5 Communications Intelligent e
Ethernet and TCP/IP networks 317 tr
Ethernet and TCP/IP networks 319 Th
Ethernet and TCP/IP networks 321 Fi
12.2.5 10Broad36 12.2.6 1Base5 Ethe
Ethernet and TCP/IP networks 325 si
Ethernet and TCP/IP networks 327 As
12.8.4 Length Ethernet and TCP/IP n
Ethernet and TCP/IP networks 331 To
12.11.8 Fast Ethernet Ethernet and
12.12 TCP/IP Ethernet and TCP/IP ne
Ethernet and TCP/IP networks 337
Ethernet and TCP/IP networks 339 Fi
Here follows a brief description of
Unicast addresses Ethernet and TCP/
The three common fields are: Ethern
Ethernet and TCP/IP networks 347 Th
13 Fieldbus and SCADA communication
Fieldbus and SCADA communications s
Fieldbus and SCADA communications s
• Programmable logic controllers
Fieldbus and SCADA communications s
Three such ‘services’ are readi
Figure 13.9 High speed Ethernet and
14.2 UCA development UCA protocol 3
14.3.1 Uniform communications infra
UCA protocol 367 14.3.4 Uniform app
14.3.5 Uniform data model UCA proto
Figure 14.6 Device object model ove
UCA protocol 373 An excellent refer
Applications of DNP3 and SCADA prot
Applications of DNP3 and SCADA prot
Applications of DNP3 and SCADA prot
PDS 500 Data Map Applications of DN
Applications of DNP3 and SCADA prot
Applications of DNP3 and SCADA prot
Applications of DNP3 and SCADA prot
Applications of DNP3 and SCADA prot
16 Future developments Objectives W
Appendix A Glossary 3GPP 10Base2 10
Appendix A: Glossary 395 ATM Attenu
Appendix A: Glossary 397 Capacitanc
Appendix A: Glossary 399 Decibel (d
Appendix A: Glossary 401 ESS Etherl
Appendix A: Glossary 403 I/O addres
Manchester encoding Appendix A: Glo
Appendix A: Glossary 407 Packet PAD
Appendix A: Glossary 409 RFI Ring R
Appendix A: Glossary 411 TDMA TDR T
Appendix A: Glossary 413 X.25 CCITT
Appendix B: Implementers of DNP3 41
Appendix B: Implementers of DNP3 41
DNP3 device profile Appendix C: Sam
Appendix C: Sample device profile d
Appendix C: Sample device profile d
Appendix C: Sample device profile d
Appendix C: Sample device profile d
Software setup Appendix D: Practica
Appendix D: Practicals 431 1. Set u
Objectives • To show how a basic
Implementation/setting up TCP/IP Cl
Appendix D: Practicals 437 Click on
Appendix D: Practicals 439 Click on
Appendix D: Practicals 441 Now rese
Appendix D: Practicals 443 Practica
Appendix D: Practicals 445 This sho
Appendix D: Practicals 447 Once you
IMPORTANT NOTICE: Appendix D: Pract
Appendix D: Practicals 451 (This is
Appendix D: Practicals 453 PRACTICA
Click on the Diags button and the f
Appendix D: Practicals 457 The scre
Appendix D: Practicals 459 Assume t
Appendix D: Practicals 461 Problem
Network Loading Assumptions Item Da
2. IEC 60870-5-101 Packet Analysis
3.1.1.1.1 Appendix D: Practicals 46
Appendix D: Practicals 469 Valid Ca
3.1.1.1.7 Type 14 INFORMATION OBJEC
Appendix D: Practicals 473 3.1.1.1.
Appendix D: Practicals 475 QDS Qual
Appendix D: Practicals 477 7 6 5 4
3.1.1.1.11 Communication 1 Appendix
Communication 1 Answer Appendix D:
CITECT PRACTICAL For Citect Version
Appendix D: Practicals 485 Next cli
Appendix D: Practicals 487 (3) Defi
Appendix D: Practicals 489
Appendix D: Practicals 491 (4) Crea
Appendix D: Practicals 493 Use the
Appendix D: Practicals 495 Click on
Appendix D: Practicals 497 When fin
Appendix D: Practicals 499 What is
Communication 2 05640DC405001A00637
05640DC405001A006378C6C601010200003
Appendix D: Practicals 505 What are
Appendix D: Practicals 507 01 01 01
Appendix D: Practicals 509 E2 81 00
Appendix D: Practicals 511 At fist
Appendix D: Practicals 513 Then rem
Appendix D: Practicals 515 The next
Packet Interpretation Practical App
056408C40300A200EA80C5C5171E4405641
Appendix D: Practicals 521 Communic
05640DC405001A006378C6C601010200003
Appendix D: Practicals 525 What is
01 01 01 01 01 01 01 crc:BB crc:C3
Appendix D: Practicals 529 Read Dat
Index 531 Carrier sense with multip
Index 533 support for protocol, 310
Index 535 process related, 220 bina
Index 537 signal quality detector,