beautypg.com

Appendix b.4.5, Nodes – ProSoft Technology PS-QS-1x10-0781 User Manual

Page 78

background image

FieldServer Configuration Manual

Page 78 of 90

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: [email protected]

Appendix B.4.5.

Nodes

Section Title
Nodes
Column Title

Function

Legal Values

Node_Name
(Device_Name)

Provides name for Node

Up to 32 Alpha
Numeric Characters

Node_ID

Specifies Node ID Information

1-255

Protocol

Specifies Protocol used

Modbus/TCP etc..

IP_Address

IP address of Client PLC

Valid IP address

Retries*

Specifies how many sequential errors must occur before
marking a data buffer and poll block bad, and marking a device
offline. The FieldServer will poll the device and if it receives no
response will retry polling the device the number of times
specified by the retries parameter. The FieldServer will attempt
to recover the connection once the recovery interval has
elapsed

Count
Default 3

Retry_Interval

Interval between retries

Interval in Seconds

Srv_Offline_Method

A Server Node could send contradictory information if its data
comes from multiple Client Nodes, some of which are offline
and others online, causing it to respond differently depending
on what data is polled. This confuses some systems. This
setting allows the user to select whether the Server Node
should appear online or offline if there is a mix of Client Node
Statuses.
Ignore_Clients - causes the Server to behave explicitly – not to
depend on the status of the Client Node, but on the data
validity only. i.e. non-expired data will be served whether or
not the responsible Client Nodes are online.
Any_Offline - suppress a data response if ANY of the
responsible Client Nodes for the data range concerned are
offline
All_Offline - only suppress a data response if ALL of the
responsible Client Nodes for the data range concerned are
offline.
Always_Respond overrides the data validity as well. i.e. it
forces the Server Node to regard data as valid even if the Client
Node is offline or the data has expired.

Ignore_Clients
Any_Offline
All_Offline
Always_Respond

Write_Ack_Option*

Ack_Complete (default) - the Server waits for the Client Side
write transaction to complete before acknowledging the Write
request. This makes for good reliability but has a cost in terms
of throughput.
Ack_Immediate - fast, but less reliable. The Server immediately
acknowledges a Write request before queuing the Client Side
Write. The acknowledgement is thus not affected by the
success or failure of the Client Side Write. Only recommended if
the same points are updated regularly.
Ack_Verified - most reliable, and slowest. The Server waits for a

Ack_Complete,
Ack_Immediate,
Ack_Verified