FieldServer FS-8700-47 instruction manual Fyi

Page 50

FS-8700-47 DNP 3.0 Driver Manual

 

Page 50 of 51

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Error Message

 

 

Explanation

 

 

 

 

 

 

 

The Server has been configured to serve ‘changed’ data only. In

 

 

DNP3:#70 Err No COV

 

reviewing the data, the driver could not find the dead band needed

 

 

 

to make a decision about whether the data has changed or not.

 

 

DeadBand for DA=%s Off=%d

 

 

Refer to Section 5.3.10 for an example showing configuration

 

 

 

 

 

 

 

 

 

 

 

 

requirements. 10

 

 

 

 

 

 

 

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

 

 

"DNP3:#71 FYI. Client observes:

this message. It alerts you

to the fact that the Server device

 

 

Server rqsts time synch

 

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.

 

 

 

 

 

 

The driver attempted to auto-create a Map Descriptor to send the

 

 

 

 

 

 

time to a Server device that has requested a Real Time Clock

 

 

DNP3:#72 Err. Heading not equal

Update. The attempt failed and the time was not sent. To resolve

 

 

to keywords

 

 

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.

 

 

 

 

 

 

You can safely ignore this message. It confirms that the Client side

 

 

DNP3:#73 FYI. Time Synch MD

of the driver, saw a request for a time update and auto-created a

 

 

Created

 

 

 

MD to send the time to the Server device. Read Appendix A.19 for

 

 

 

 

 

 

more information.

 

 

 

DNP3:#74 Err. Ana Output Blk.

Analog Output Blocks and Relay Blocks must be selected before

 

 

No Operate because no select.

they can be operated. The driver needs a place to store the select

 

 

Obj=%d"

 

 

 

flag. This is done using a Secondary Data Array specified with the

 

 

DNP3:#75 FYI. Relay Output. No

DA_Bit_Name parameter.

If not specified then the point is

 

 

place to store select. Obj=%d"

assumed to be selected all the time. Errors #75 and #77 can safely

 

 

DNP3:#76 Err. Relay Output. No

be ignored. If a point has secondary storage defined to store the

 

 

Operate because no select.

 

select flag then the driver checks the select flag has been set when

 

 

Obj=%d

 

 

 

an operate command has been received. If not set then the

 

 

DNP3:#77 FYI. Ana Output Blk.

message #74 or #76 is printed. These errors can be avoided by

 

 

having the remote master send a select command first. Refer to

 

 

No place to store select. Obj=%d"

 

 

Appendix A.19 for more information.

 

 

 

 

 

 

The configuration contains the Node parameter ‘Server_II_Array’

 

 

DNP3:#78

Err.

Node_ID=%d II

but when the driver looked for the Data Array specified it could not

 

 

Array=%s doesn’t exist.

 

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.

 

 

 

 

 

 

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

 

 

DNP3:#79

FYI. Node=%d

Using

Internal Indications bytes in the response will not be built by the

 

 

DA=%s for II

 

 

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

 

 

 

 

 

 

 

To auto-create a Map Descriptor to send the time to the Server

 

 

DNP3:#80

FYI.

Time

Synch

device the driver required the configuration to have a Data Array

 

 

requires DA=%s

 

 

called ‘DNP3_RTC_NODEx’ where x is the Server device station

 

 

 

 

 

 

address. Refer to Appendix A.18 for more information10

 

10Edit 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

Page 49 Page 51
Image 50
Page 49 Page 51
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 Hardware Connections Connection NotesConfiguring the FieldServer as a DNP 3.0 Driver Client Data ArraysClient Side Connection Descriptors Client Side Node 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 Configuring the FieldServer as a DNP 3.0 Driver Server Server Side Connection DescriptorsServer Side Node Descriptors Driver Specific Map Descriptor Parameters Map Descriptor Example 1 Discrete Data Map Descriptor Example 2 Class DataMap Descriptor Example 3 Class Data another example RTUMap Descriptor Example 4 Default Variation Variation zero Map Descriptor Example 5 ClassDataServingCtrl AnaInputs Map Descriptor Example 6 Unsolicited Messages Server Side Limitations Appendix A.3. DNP Objects mapped to FieldServer Data Arrays Appendix A. Advanced Topics Appendix A.1. DNP 3.0 ProtocolAppendix A.2. DNP Driver Functionality Appendix A.4. Channel Idle, Master & Slave IdleAppendix A.5. DLL Layer Functionality in the Master Appendix A.6. App Layer Functionality in the MasterAppendix A.7. Internal Indications, Object 80 and Dnpii Incoming Internal Indications BytesPage Internal Indications reported in Responses ServerIIArrayResponses to Polls for Object 80 Internal Indications Appendix A.8. DNPStats 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.11. Controlling the DNP 3.0 Driver’s Qualifier Appendix A.12. FieldServer DNP Node NumberAppendix A.14. Communication Stats Appendix A.15. Link ResetAppendix A.13. DnpSubType Appendix A.16. Controlling DA Offsets Appendix A.17. dnpIndexStyleAppendix A.18. Real Time Clock Synchronization DatimePage 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