Page 49 of 51 |
| ||
|
|
|
|
|
|
|
|
| Error Message | Explanation |
|
|
| Some DNP messages contain too much data to be sent in one |
|
|
| message. Such messages are split into multiple frames and |
|
|
| reassembled on the receiving side. Each frame has a sequence |
|
| DNP3:#60 Msg Frame | number. If frames are received out of sequence this message is |
|
| printed. Typically, once one frame is found out of sequence the |
| |
| abandoned. Frames out of seq. |
| |
| remaining frames may be flagged as errors too. A consequence of |
| |
| Exp=%d Rcvd=%d. TP=%#d |
| |
| this message is the loss of the complete message. If this message |
| |
|
|
| |
|
| is printed rarely, you could assume that it is a consequence of |
|
|
| occasional corruption. If it is printed often then take a log and call |
|
|
| Tech support. |
|
|
| When the DNPfunction parameter is omitted on a Map Descriptor |
|
|
| used to read data the driver assumes that the intended |
|
| DNP3:#61 FYI. Read func | DNPfunction is ‘read’. However in some case the driver knows that |
|
| changed Now=%s. MD=<%s> | for certain Objects the function must be changed and does this |
|
|
| automatically. This message gives a heads. No action is required |
|
|
| from you. |
|
|
| The Server side of the driver can only process messages which poll |
|
| DNP3:#62 Err. Rejected msg with | for one class of data at a time. |
|
| multiple polls. | again. This message is obsolete. Only driver version 1.03i and |
|
|
| older produce the message. Read Appendix A.20 for more info. |
|
| DNP3:#64 Err. To serve class | To serve class data the parameter dnpAssociate must be specified |
|
| data set the DNPAssoc value | on all associated Map Descriptors and the value of the parameter |
|
| must be |
| |
| DNP3:#65 Err. There are no MD | Refer to Section 5.3.5. 9 |
|
| associated with the class MD=%s |
|
|
| DNP3:#63a Err. Cant open %s for | If any of these messages are printed call tech support. An internal |
|
| poll from log | diagnostic specific to QA testing has been activated. It is possible |
|
| DNP3:#63b Err. Cant read 1st | for the driver to send a message that is found in a log file instead of |
|
| line of %s | the configured poll to test the Server side of the driver. Script S4085 |
|
|
| provides an example. The Client side MD name must have '.log in |
|
| DNP3:#63c FYI. Sending | the name and the driver opens that file and sends the 1st line (only) |
|
| message from log file=%s | as a single message. The line is expected to have hex bytes |
|
|
| delimited by space or square brackets. |
|
| DNP3:#66 Err. Index Style=%d | The Server side of the driver does not support the indicated |
|
| index_style. Refer to Appendix A.17. Reconfigure your Client to |
| |
| not supported. |
| |
| use a different qualifier and try again9 |
| |
|
| This message confirms that the Server has been configured to |
|
| DNP3:#67 FYI Serve 'changed' | serve ‘changed’ data only. Thus, only data whose value has |
|
| changed by some dead band since the last poll for class data will |
| |
| data only. Class=%d |
| |
| be served. You can safely ignore this message if it confirms your |
| |
|
|
| |
|
| expectations. If not then review your configuration. |
|
|
| When the Server serves class data and when configured to serve |
|
|
| only ‘changed’ data then the Server may change the qualifier of the |
|
| DNP3:#68 FYI. Class Data | response from the default or configured qualifier because the points |
|
| being served in the response may not be sequential. You may |
| |
| Served with Qualifier=%#x |
| |
| ignore this message as it does not report an error. It is printed to |
| |
|
|
| |
|
| draw your attention to the fact that the master should be configured |
|
|
| to receive a response that uses a different qualifier. |
|
|
| Each time that the Server sets the internal indication bit to signal |
|
| DNP3:#69 FYI. Server signals | the master station that a time update is required this message is |
|
| Client=%d to time synch | printed. You can safely ignore it if it confirms your expectations. |
|
|
| Refer to Appendix A.18. |
|
9Edit the CSV file, download to the FieldServer and reset the FieldServer.
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
