FieldServer FS-8700-47 instruction manual Appendix A.9. DNP 3.0 Data Objects

Page 33

FS-8700-47 DNP 3.0 Driver Manual

Page 33 of 51

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Array

 

Contents

 

 

 

Element

 

 

 

 

 

 

 

 

 

30

 

DNP_NOT_OK

 

 

 

31

 

DNP_UPD_RESET_RQD

 

 

 

32

 

DNP_UPD_CANT_RESET

 

 

 

33

 

DNP_UPD_NO_NODES

 

 

 

34

 

DNP_UPD_RESET_FAILED

 

 

 

35

 

DNP_UPD_MAST_DEBUG_MSG

 

 

 

36

 

DNP_UPD_MAST_PARSE_ERR

 

 

 

37

 

DNP_UPD_SLAVE_PARSE_ERR

 

 

 

38

 

DNP_UPD_MAPD_TOO_SHORT

 

 

 

39

 

DNP_UPD_TOO_MANY_BYTES3

 

 

 

40

 

DNP_DIAGNOTIC_GENERATOR

 

 

 

41

 

DNP_UPD_LINK_RESET_DONE

 

 

 

42

 

DNP_UPD_LINK_RESET_DONE_BY_MST

 

 

 

 

Increments once each time a link reset ack is sent by a master

 

 

 

 

 

 

 

 

43

 

DNP_UPD_LINK_RESET_DONE_BY_SRV

 

 

 

 

Increments once each time a link reset ack is sent by a slave.

 

 

 

 

 

 

 

 

 

 

DNP_UPD_LINK_STATUS_STATE

 

 

 

44

 

Result of most recent link status poll are stored here. 1=Busy, 2=Available, 0=Not

 

 

 

 

Update

 

 

Appendix A.9. DNP 3.0 Data Objects

The DNP 3.0 Driver acting as a Client will produce a single message fragment. A message fragment may contain a maximum of 249 bytes, some of which constitute overhead. The DNP 3.0 driver will panic if the message fragment is too long. Reduce the length and add another Map Descriptor to poll additional items. This limitation does not apply when the DNP 3.0 driver processes a response from a query as the driver can process multi fragment responses.

The list of data objects supported and the functions used to access the objects is defined on the Driver Fact Sheet which may be obtained from FieldServer Technologies. The table is known as a DNP 3.0 Implementation Table.

The table below lists the objects and variations that be used in the Map Descriptors. The DNP 3.0 Driver supports all the objects with some exceptions. The exceptions are noted by indicating the revision number of the driver prior to them being supported or by indicating that the object is not supported with the NS annotation.

Default Variations are designated with a *. Not all Data Types have a default variation. The default variation will be returned when a Client polls for variation zero (default). Server configurations require a Map Descriptor with variation zero to be defined in the CSV file before the driver can respond with the default variation data.

Object

Variation.

Ex

Description

1

0

 

Binary Input - All Variations

1

1*

 

Binary Input

1

2

 

Binary Input with Status

2

0

 

Binary Input Change - All Variations

2

1*

 

Binary Input Change without Time

2

2

 

Binary Input Change with Time

2

3

 

Binary Input Change with Relative Time

3Increments by one each time a response message isn’t sent because the number of elements to respond with requires too many bytes to fit in a message.

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

Page 32 Page 34
Image 33
Page 32 Page 34
Contents Driver Manual FS-8700-47 DNP Table of Contents FS-8700-47 DNP 3.0 Driver Manual Table of Contents DNP 3.0 Driver Description Page FS-8700-47 DNP 3.0 Driver Manual Connection Notes Hardware ConnectionsData Arrays Configuring the FieldServer as a DNP 3.0 Driver ClientClient Side Node Descriptors Client Side Connection DescriptorsDriver Specific Map Descriptor Parameters Timing Parameters Map Descriptor Example 1 Simple Read Map Descriptor Example 3 Simple Read Extract Value & Status Map Descriptor Example 4 Reading Class Data Map Descriptor Example 6 Read an unknown variation Server Side Connection Descriptors Configuring the FieldServer as a DNP 3.0 Driver ServerServer Side Node Descriptors Driver Specific Map Descriptor Parameters Map Descriptor Example 2 Class Data Map Descriptor Example 1 Discrete DataRTU Map Descriptor Example 3 Class Data another exampleMap Descriptor Example 4 Default Variation Variation zero Map Descriptor Example 5 ClassDataServingCtrl AnaInputs Map Descriptor Example 6 Unsolicited Messages Server Side Limitations Appendix A.2. DNP Driver Functionality Appendix A. Advanced Topics Appendix A.1. DNP 3.0 ProtocolAppendix A.3. DNP Objects mapped to FieldServer Data Arrays Appendix A.4. Channel Idle, Master & Slave IdleAppendix A.6. App Layer Functionality in the Master Appendix A.5. DLL Layer Functionality in the MasterIncoming Internal Indications Bytes Appendix A.7. Internal Indications, Object 80 and DnpiiPage ServerIIArray Internal Indications reported in ResponsesResponses to Polls for Object 80 Internal Indications Dnpstats Appendix A.8. DNPStatsAppendix A.9. DNP 3.0 Data Objects Counter Change Event All Variations See notes in Appendix A.10 for function code FS-8700-47 DNP 3.0 Driver Manual Appendix A.12. FieldServer DNP Node Number Appendix A.11. Controlling the DNP 3.0 Driver’s QualifierAppendix A.15. Link Reset Appendix A.13. DnpSubTypeAppendix A.14. Communication Stats Appendix A.17. dnpIndexStyle Appendix A.16. Controlling DA OffsetsDatime Appendix A.18. Real Time Clock SynchronizationPage Appendix A.19. Select and Operate Page Page Appendix A.20. Multiple requests in a single poll Appendix B. Driver Error Messages Page Page Page FYI
Top Page Image Contents