FS-8700-47 DNP 3.0 Driver Manual
Page 50 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
Error Message
Explanation
DNP3:#70 Err No COV
DeadBand for DA=%s Off=%d
The Server has been configured to serve ‘changed’ data only. In
reviewing the data, the driver could not find the dead band needed
to make a decision about whether the data has changed or not.
Refer to Section 5.3.10 for an example showing configuration
requirements.
10
"DNP3:#71 FYI. Client observes:
Server rqsts time synch
Each time that the Server sets bit 4 of byte 1 of the internal
indication field in the response message the Client driver will print
this message. It alerts you to the fact that the Server device
expects to be sent the time and to have the master reset the flag.
Refer to Appendix A.18 for more information on how to configure
the master to respond to this request. If you don’t care about the
Server’s time then ignore this message without consequence.
DNP3:#72 Err. Heading not equal
to keywords
The driver attempted to auto-create a Map Descriptor to send the
time to a Server device that has requested a Real Time Clock
Update. The attempt failed and the time was not sent. To resolve
this error refer to Appendix A.18 and review your configuration. If
you cannot see a problem, capture a log and send the log with the
configuration to FieldServer Tech Support.
DNP3:#73 FYI. Time Synch MD
Created
You can safely ignore this message. It confirms that the Client side
of the driver, saw a request for a time update and auto-created a
MD to send the time to the Server device. Read Appendix A.19 for
more information.
DNP3:#74 Err. Ana Output Blk.
No Operate because no select.
Obj=%d"
DNP3:#75 FYI. Relay Output. No
place to store select. Obj=%d"
DNP3:#76 Err. Relay Output. No
Operate because no select.
Obj=%d
DNP3:#77 FYI. Ana Output Blk.
No place to store select. Obj=%d"
Analog Output Blocks and Relay Blocks must be selected before
they can be operated. The driver needs a place to store the select
flag. This is done using a Secondary Data Array specified with the
DA_Bit_Name parameter. If not specified then the point is
assumed to be selected all the time. Errors #75 and #77 can safely
be ignored. If a point has secondary storage defined to store the
select flag then the driver checks the select flag has been set when
an operate command has been received. If not set then the
message #74 or #76 is printed. These errors can be avoided by
having the remote master send a select command first. Refer to
Appendix A.19 for more information.
DNP3:#78 Err. Node_ID=%d II
Array=%s doesn’t exist.
The configuration contains the Node parameter ‘Server_II_Array’
but when the driver looked for the Data Array specified it could not
find it. The Data Array must be defined before this parameter is
used. If the Data Array cannot be found then the driver responds
as if it had not been specified at all.
DNP3:#79 FYI. Node=%d Using
DA=%s for II
The driver prints this message once and then suppresses it. It
draws your attention to the fact that one or more Server nodes has
the node parameter ‘Server_II_Array’ specified and that the
Internal Indications bytes in the response will not be built by the
driver but will rather be extracted from two consecutive data array
elements. Offsets 0 and 1 are always used. If this message is
consistent with your expectations then ignore it otherwise review
your configuration
DNP3:#80
FYI.
Time
Synch
requires DA=%s
To auto-create a Map Descriptor to send the time to the Server
device the driver required the configuration to have a Data Array
called ‘DNP3_RTC_NODEx’ where x is the Server device station
address. Refer to Appendix A.18 for more information
10
10
Edit the CSV file, download to the FieldServer and reset the FieldServer.
