Filter
Top Products
FS-8700-47 DNP 3.0 Driver Manual Page 18 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
5.3.2. Driver Specific Map Descriptor Parameters
Column Title Function Legal Values
Node_Name Name of Node to fetch data from
A Node Name specified in
“Client Node
Descriptor”.
Special Map Descriptor’s
used by the DNP 3.0 Driver
are discussed in Error!
Reference source not
found..
Length
Length of Map Descriptor. If a request length
is too large the DNP 3.0 driver will produce a
message and a panic. The maximum length
is a function of the data object and data
variation being processed.
1 – 1000
Address Starting address of data element to be read 0, 1 , 2 etc
The following parameters apply only to the DNP 3.0 Driver
DnpDataType
Corresponds to the Data Object Types defined
in the DNP data object Library. Enter as
decimal number. Refer to Appendix A.9
1, 2, 10, 12, 30, 31, 32, 33,
40, 41, 20, 22, 23, 50,51, 52,
60, 80
DnpDataVari
Corresponds to the Data Object Variant
defined in the DNP data object Library. Enter
as decimal number.
When configured as a Server the driver can
respond to requests for the so called ‘Default’
variation. These are polls where the variation
is zero.
To configure the driver to be able to respond
to requests for the default variation then you
must create a MapDesc where the
DNPDataVari=0.
Note that the driver considers variation=1 as
the default in most case.
0,1,2,3 etc
Legal values are determined
by the value of dnpDataType.
Additional information is
provided in Appendix A.9
DnpQualifier*
This parameter is ignored by the driver acting
as a Server. The qualifier of the incoming poll
is used to form the response. If the poll
qualifier is not supported by the driver’s
response function then the driver responds
with Qualifier 1. The response function
supports the following qualifiers;
0,1,6,7,8,17,28,
DnpMultiMsg
Simply ensure that that there is a Server MD
for each object requested. No special actions
are required to configure the Server to
respond to requests for multiple object types.
Refer to Appendix A.20 for more information.
5.3.3. Timing Parameters
Column Title Function
Legal
Values
Scada_Hold_Timeout
Time Server side waits before notifying Client that node is
offline on FieldServer Client side.
>1.0s