Filter
Top Products
FS-8700-47 DNP 3.0 Driver Manual Page 33 of 51
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
Array
Element
Contents
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_BYTES
3
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.
44
DNP_UPD_LINK_STATUS_STATE
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
3
Increments 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.