Remerciez-le!

Remerciez @Admin pour avoir partagé cet document gratuitement, de la manière la plus simple, en partageant sur les réseaux sociaux.

CitectSCADA DNPr Driver Page 1 of 85 DNPr Driver User Information and Design Ci

CitectSCADA DNPr Driver Page 1 of 85 DNPr Driver User Information and Design Citect Pty Ltd ABN 88 001 158 854 3 Fitzsimons Lane Gordon 2072 NSW Australia PO Box 174 Pymble 2073 NSW Australia Tel 61 2 9496 7300 Fax 61 2 9496 7399 www.citect.com Citect Pty Ltd Driver User Guide CitectSCADA DNPr Driver 18/08/2005 Page 2 of 85 Revision History Date Comment 3/3/97 As per first Beta (to be extended) 19/4/98 25/5/98 27/05/98 Removed need to specify number of IO points 17/06/98 Mods as per Beta8 07/10/98 Mods for Beta9 25/11/98 As per Beta9 14/04/99 As per Beta10 09/06/99 As per Beta11 20/07/99 As per Release V1.2 (V1.02) 08/11/99 As per Release V1.03 15/02/00 Testing for Remote I/O 02/06/00 Updates due to additional functionality 26/11/02 Updates for V2.0 of driver – redundancy support 09/12/02 Update DnpR to as-built status, and again 12/12/02 08/01/03 Updates for new ini parameters 13/02/03 Add new option to UnitUsurpMode[Default] parameters 25/02/03 Added new INI PollPeriodOffset. For Build 183 on. 14/03/03 Added new mode to UseFeedBackPoll 19/03/03 Added retry to peer coms for 187 build 22/07/03 Updated to as built status for version 192 24/07/03 Megawatt updates. Calculated Variables and new tag types. Updates to as-built status v3.00.00.003 B1 27/08/03 Adding missing data types 24/10/03 To as built status for version v3.00.01.01 B1, features : 17/11/03 Update to version 3.00.02.06 status 03/12/03 Update to version 3.01.00.006 – DNP changed to DNPR 22/01/04 Update to version 3.01.05.001 – Time updates, new tags 17/05/04 Update to version 3.01.07.xxxx – Mainly event related Citect Pty Ltd Driver User Guide CitectSCADA DNPr Driver 18/08/2005 Page 3 of 85 Contents 1. INTRODUCTION 6 1.1 Scope. 6 1.2 Outline. 6 1.3 Terms 7 2. TARGET DEVICE(S) AND PROTOCOL 8 2.1 Introduction 8 2.2 Device Manufacturer 8 2.3 Device Definition 8 2.4 Communications Method 8 2.5 Communications/Hardware Configuration 8 2.5.1 I/O Device Settings 9 2.5.2 Software Setup 9 2.6 Redundancy Features of DNP-R 9 2.6.1 Redundancy level 10 2.6.2 Enabling redundancy 10 2.6.3 Peer Driver Settings 10 2.6.4 Active driver state 10 2.6.5 Off-line Standby 10 2.6.6 User control of redundancy 10 2.6.7 Level of redundancy 11 2.6.8 Port level redundancy 11 2.6.9 Driver cache replication 11 2.6.10 Trend and alarm backfilling 11 2.6.11 Value writes 12 2.6.12 Action on becoming active (usurp) 12 2.6.13 Virtual Units 12 2.6.14 SELECT and OPERATE 12 2.7 Calculated Variables 13 2.7.1 Configuring Calculated Variable CSV Files 13 2.8 Event Polls 14 2.9 Special Requirements 14 2.10 Maximum Request Length 14 3. USER INTERFACE 15 3.1 Introduction 15 Citect Pty Ltd Driver User Guide CitectSCADA DNPr Driver 18/08/2005 Page 4 of 85 3.2 Driver Name 15 3.3 Boards Form 15 3.4 Ports Form 15 3.5 IO Devices Form 16 3.5.1 Address 16 3.6 Pulldown lists Help 17 3.7 IO Device Variable Types 18 3.7.1 Formats and types 18 3.7.2 driver.dbf Entries 44 3.8 PROTDIR.DBF 45 3.9 Parameters and INI options 45 3.9.1 General Parameters 45 3.9.2 Standard Driver Parameters 45 3.9.3 Driver Specific Parameters 46 3.10 Driver Specific Errors 60 3.11 Driver Error Help 63 3.12 Debug Messages 65 3.12.1 SCADA Debugging 65 3.12.2 Protocol Debugging 66 3.12.3 Peer State Machine Debugging 67 3.12.4 Useful Debugging Tips 67 3.13 Stats Special Counters 68 3.14 Processing of Timestamped Event Data 69 3.14.1 Driver Ordinals 71 3.14.2 DNPR_LOGGER.TXT Format 72 3.15 Hints and Tips 73 3.15.1 DNP Protocol 73 3.15.2 Data Acquisition within DNP 73 3.15.3 Blocking Issues 74 3.15.4 Citect forms and Citect tag databases 76 3.15.5 Startup considerations 76 3.15.6 Useful INI parameters for debugging 76 4. PROTOCOL REQUIREMENTS 77 4.1 Introduction 77 4.2 Initialising the Board 77 4.3 Initialising the Port 77 4.4 Initialising the IO Device 77 4.5 IO Device Online Test 77 4.6 State Flow Description 78 4.7 Message Structure 78 Citect Pty Ltd Driver User Guide CitectSCADA DNPr Driver 18/08/2005 Page 5 of 85 4.8 Data Format 78 4.9 Check Sum 78 4.10 Error Handling 78 4.11 Special Citect.INI Values 79 5. DESIGN 80 5.1 Active Arbitration 80 6. BASIC TESTING 82 6.1 Introduction 82 6.2 Procedure 82 6.3 Start of Testing 82 6.3.1 Test 1: Basic Communication Test 82 6.3.2 Test 2: Read/Write of each data type 82 6.3.3 Test 3: Break in communication and recovery 82 6.3.4 Test 4: Bulk Test 82 6.3.5 Test 5: Check all types read/write to the correct address 82 6.3.6 Test 6: Test all Parameters and INI options. 82 6.3.7 Test 6: Basic Remote I/O testing. 82 6.4 Faults Found. 82 7. PERFORMANCE TESTINGINTRODUCTION 83 7.1 Calculating the Blocking Constant 83 8. REFERENCES AND CONTACTS 84 8.1 References 84 8.2 Contacts 84 9. QA 85 9.1 Developers Guidelines 85 9.1.1 Accredited Drivers. 85 9.1.2 Independent Drivers. 85 9.2 Accreditation process 85 Citect Pty Ltd Driver User Guide CitectSCADA DNPr Driver 18/08/2005 Page 6 of 85 1. Introduction 1.1 Scope. This document follows the development of the new driver. It serves as a functional specification, design specification and test specification. 1.2 Outline. The specification is broken down into the following sections: Section 1 – Introduction. This section defines the scope of a board driver specification and outlines the items addressed by the specification. Section 2 – Physical Communication Method. The Physical Communication Method section defines the physical communication method supported, hardware/software suppliers, how the method is setup, any wiring diagrams involved etc. Section 3 – Protocol Requirements. The Protocol Requirements section details the technical considerations required or incorporated by the driver. Section 4 – User Interface. The User Interface section defines how the user will see and setup the driver in Citect. Section 5 – Basic Testing. The Basic Testing section defines the items which should be addressed in Basic testing by the developer. Section 6 – Performance Testing. The Performance Testing section is used in full testing of the driver by the Citect Testing Department of CiT. Once complete, this will provide details on the reliability and stability of the driver, and point out where the driver needs to be improved. Section 7 – References and Contacts. The References and Contacts section should be used as a record of reference materials and contacts used in developing this driver. Section 8 – Quality Assurance. The QA section defines the requirements and procedures for Quality Assurance Accreditation. It is important you read this if you want your driver integrated into Citect. Citect Pty Ltd Driver User Guide CitectSCADA DNPr Driver 18/08/2005 Page 7 of 85 1.3 Terms Term Definition Active unit The ONLINE unit which is actively being used for Reads and Writes Class 0 Data All objects defined in the device Class 1,2,3 Data Optional classes a data object can be associated with, this is used to restrict the traffic volume for these polls to specific items. Event Poll A poll to the device from the driver to return and new events (data changes) since the last poll (for the class) Inactive unit The ONLINE unit which is not being used for Reads and Writes. However, this unit is available for these if the IOServer choses. Integrity Poll A poll to the device from the driver to return the status of all data points (for the class), OFFLINE Offline means the unit cannot talk to the device. ONLINE Online means we can communicate to the device. PRIMARY unit The unit is configured to be the primary or master unit for use STANDBY unit The unit is configured to be the unit to use when the PRIMARY is not available USURP When a unit is forced offline to allow its peer driver unit to take over Citect Pty Ltd Driver User Guide CitectSCADA DNPr Driver 18/08/2005 Page 8 of 85 2. Target Device(s) and Protocol 2.1 Introduction This section defines the types of I/O Devices that are targeted by this driver. This specification covers the scope of version 3.0 of the driver which supports redundancy of driver information (data values, events) at a per unit level,calculated varaiables, dial up support, and new data types. It is strongly recommended that the reader study Section 3.15 Hints and Tips, to gain an overview of the protocol and driver, before reading the remainder of this specification. It is assumed the reader is familiar with the terms and issues involved with configuring RTU type devices using the DNP3 protocol. . The term DNP3 is referring to the commonly known protocol name used in the Citect DNPr driver. This spec has been updated to functionality in v3.01.07.029 of the driver. Prior to this the driver has the DNPr driver. 2.2 Device Manufacturer As this is an open protocol, acting as a pseudo standard for the utility industries, there are numerous vendors manufacturing devices that support this protocol. Many device manufacturers are also modifying their existing devices to support the DNP protocol. 2.3 Device Definition Any device that supports the DNP3 protocol subsets Level 1 or Level 2. Devices that support DNP Level 3 will be partially supported by the driver. 2.4 Communications Method The communication methods are RS-232, TCP/IP or UDP. uploads/Litterature/ dnpr-users-guide.pdf