Resumo do conteúdo contido na página número 1
-
A Sierra Monitor Company
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-47 DNP 3.0
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after December 2008
Driver Version: 1.03
Document Revision: 14
Resumo do conteúdo contido na página número 2
FS-8700-47 DNP 3.0 Driver Manual Table of Contents TABLE OF CONTENTS 1. DNP 3.0 Driver Description ................................................................................................................4 2. Driver Scope of Supply.......................................................................................................................6 2.1. Supplied by FieldServer Technologies for this driver.....................................................................6 3.
Resumo do conteúdo contido na página número 3
FS-8700-47 DNP 3.0 Driver Manual Table of Contents Appendix A.16. Controlling DA Offsets ................................................................................................39 Appendix A.17. dnpIndexStyle.............................................................................................................39 Appendix A.18. Real Time Clock Synchronization...............................................................................40 Appendix A.19. Select and Operate..
Resumo do conteúdo contido na página número 4
FS-8700-47 DNP 3.0 Driver Manual Page 4 of 51 1. DNP 3.0 Driver Description The DNP 3.0 Driver allows the FieldServer to transfer data to and from devices over RS-232 or RS-485 using DNP 3.0 Driver protocol. The FieldServer can emulate either a Server or Client. ∗ The following description of DNP is from the DNP User Group internet site. “The development of DNP was a comprehensive effort to achieve open, standards-based interoperability between substation computers, RTUs, IEDs
Resumo do conteúdo contido na página número 5
FS-8700-47 DNP 3.0 Driver Manual Page 5 of 51 • Shorter delivery schedules • Less testing, maintenance and training • Improved documentation • Independent conformance testing • Support by independent users group and third-party sources (e.g. test sets, source code). FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
Resumo do conteúdo contido na página número 6
FS-8700-47 DNP 3.0 Driver Manual Page 6 of 51 2. Driver Scope of Supply 2.1. Supplied by FieldServer Technologies for this driver. FieldServer Technologies Part# Description FS-8915-10 UTP cable (7 foot) for RS-232 use FS-8917-04 RJ45 to DB25M connection adapter FS-8700-47 Driver Manual. FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldser
Resumo do conteúdo contido na página número 7
FS-8700-47 DNP 3.0 Driver Manual Page 7 of 51 3. Hardware Connections The FieldServer is connected to the DNP-3.0 device as shown below. Configure the DNP-3.0 device according to manufacturer’s instructions DNP Device DB25F 8917-04 Connect to one of the RS-232 Ports on the FieldServer RJ45 8 1 P1 FieldServer FieldServer Function From Default Color Rx RJ45-01 DB25F-02 White CTS RJ45-02 DB25F-04 Brown DSR RJ45-03 Yellow GND RJ45-04 DB25F-07 Green GND RJ45-05 Red DTR RJ
Resumo do conteúdo contido na página número 8
FS-8700-47 DNP 3.0 Driver Manual Page 8 of 51 4. Configuring the FieldServer as a DNP 3.0 Driver Client For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration Manual. The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer (See “.csv” files supplied with the FieldServer). This section documents and describes the parameters necessary for configuring
Resumo do conteúdo contido na página número 9
FS-8700-47 DNP 3.0 Driver Manual Page 9 of 51 4.2. Client Side Connection Descriptors Section Title Connections Column Title Function Legal Values Specify which port the device is connected to the 1 Port P1-P8, R1-R2 FieldServer 110 – 115200, standard Baud* Specify baud rate baud rates only Even, Odd, None, Mark, Parity* Specify parity Space Data_Bits* Specify data bits 7, 8 Stop_Bits* Specify stop bits 1 Protocol Specify protocol used DNP Handshaking* Specify hardware
Resumo do conteúdo contido na página número 10
FS-8700-47 DNP 3.0 Driver Manual Page 10 of 51 4.4. Client Side Map Descriptors 4.4.1. FieldServer Specific Map Descriptor Parameters Column Title Function Legal Values Up to 32 alphanumeric Map_Descriptor_Name Name of this Map Descriptor characters Name of Data Array where One of the Data Array names data is to be stored in the from “Data Array” section Data_Array_Name FieldServer above 0 to maximum specified in Data_Array_Offset Starting location in Data Array “Data Array” s
Resumo do conteúdo contido na página número 11
FS-8700-47 DNP 3.0 Driver Manual Page 11 of 51 Column Title Function Legal Values When class data is requested the DNP device responds with data of multiple types and variations in one message. One Map DnpAssociate* Non-zero positive integers. Descriptor is used per data type - this parameter is used to link these Map Descriptors. This parameter is used to produce a single message with a request for multiple object types. Assign positive whole numbers to 0, positive whole num
Resumo do conteúdo contido na página número 12
FS-8700-47 DNP 3.0 Driver Manual Page 12 of 51 4.4.4. Map Descriptor Example 1 – Simple Read. In this example we read 10 Analog Inputs from a DNP device. The request is with respect to inputs 20 to 29 and we will place the results of the read in the data array called DA_AI3 in positions 20 to 29. In this example the dnpSubType is not specified so the driver will report the value of the object. // Client Side Map Descriptors Map_Descriptors Map_Descriptor_Na
Resumo do conteúdo contido na página número 13
FS-8700-47 DNP 3.0 Driver Manual Page 13 of 51 4.4.5. Map Descriptor Example 2 – Simple Read – Extract the Quality/Status In this example the status data rather than the input values are written to the data array specified. // Client Side Map Descriptors Map_Descriptors Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Address ,Length ,Scan_Interval ,dnpDataType ,dnpDataVari ,dnpSubType A1 ,DA_AI3STAT ,20 ,Rdbc ,Node_A ,20 ,1
Resumo do conteúdo contido na página número 14
FS-8700-47 DNP 3.0 Driver Manual Page 14 of 51 4.4.7. Map Descriptor Example 4 – Reading Class Data In this example we read class data. A class is a structure of different data types and variations. Vendors group data into classes based on the relationships and importance of the data. In this example you will see that only one of the Map Descriptors is active – the class data read. The remaining passive Map Descriptors are used to process the response from the class data read. The
Resumo do conteúdo contido na página número 15
FS-8700-47 DNP 3.0 Driver Manual Page 15 of 51 4.4.9. Map Descriptor Example 6 – Read an unknown variation If the DNP device does not document the object type variation that it serves, set the variation to zero. The remote device will respond with its default variation. The problem is that the response cannot be stored using this Map Descriptor because the response will have its variation non- zero. Thus you would need to make a Server Map Descriptor for each possible variation. A b
Resumo do conteúdo contido na página número 16
FS-8700-47 DNP 3.0 Driver Manual Page 16 of 51 5. Configuring the FieldServer as a DNP 3.0 Driver Server For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration Manual. The information that follows describes how to expand upon the factory defaults provided in the configuration files included with the FieldServer (See “.csv” files provided with the FieldServer.) This section documents and describes the parameters necessary for configurin
Resumo do conteúdo contido na página número 17
FS-8700-47 DNP 3.0 Driver Manual Page 17 of 51 5.2. Server Side Node Descriptors Section Title Nodes Column Title Function Legal Values Up to 32 Node_Name Provide name for node alphanumeric characters Node_ID DNP 3.0 station address of physical Server node 0-65535 Protocol Specify protocol used DNP This parameter can be specified to configure the Class0; Class1; Class_Data_Serving_Ctr*l Server to serve changed data only. Refer to Class2; Class3; Example 5.3.8 for more informat
Resumo do conteúdo contido na página número 18
FS-8700-47 DNP 3.0 Driver Manual Page 18 of 51 5.3.2. Driver Specific Map Descriptor Parameters Column Title Function Legal Values A Node Name specified in “Client Node Descriptor”. Special Map Descriptor’s Node_Name Name of Node to fetch data from used by the DNP 3.0 Driver are discussed in Error! Reference source not found.. Length of Map Descriptor. If a request length is too large the DNP 3.0 driver will produce a Length message and a panic. The maximum length 1 – 1000
Resumo do conteúdo contido na página número 19
FS-8700-47 DNP 3.0 Driver Manual Page 19 of 51 5.3.4. Map Descriptor Example 1 – Discrete Data. In this example the following Map Descriptor will be used allow a remote device to request discrete input data. // Server Side Map Descriptors Map_Descriptors Map_Descriptor_Name ,Data_Array_Name ,Data_Array_Offset ,Function ,Node_Name ,Address ,Length ,Scada_Hold_Timeout ,dnpDataType ,dnpDataVari A1 ,DA_DI1 ,0 ,Passive ,Node_A ,0 ,10 ,5 ,1 ,1 The DNP 3.0 T
Resumo do conteúdo contido na página número 20
FS-8700-47 DNP 3.0 Driver Manual Page 20 of 51 5.3.6. Map Descriptor Example 3 – Class Data (another example) In this example the Server responds with a number of non-consecutive binary points. All will work fine except when the Client polls for this data with qualifier 7. The default response will be qualifier 7 with implied index style 0. The problem is that qualifier 7 tells the Client the number of objects in the packet, but they are all assumed to be addressed sequentially from
