Appendix a. useful features, Appendix a.1. snp node names – FieldServer FS-8700-66 User Manual
Page 18
![background image](/manuals/100802/18/background.png)
FS-8700-66 GE-SNP Driver Manual
Page 18 of 28
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 A. Useful Features
Appendix A.1. SNP Node Names
The following notes describe how the Node_Name is used when the FieldServer is acting as a Server.
When a Client attempts to establish a connection it may send the name of the Node it wishes to connect to or a
Null Node name. If it sends a Null Node name then the FieldServer will connect if any SNP Nodes have been
defined for the same port as the Client using the Null name. The Node must be connected to a port. Only one SNP
node can be connected per port.
Example:
Ports
Port
, Baud
P1
, -
Nodes
Node_Name , Port
Node1
, P1
If the Client uses the Node name during a connection attempt then the FieldServer uses the name to find a
matching Node. The name must be an exact match. If a match is found then the connection can be established.
In this case the Node does not have to be tied to a particular port and thus one Node could respond to different
Clients polling it on different ports. If this method is used and the Node is tied to a port then the Client must poll
on the same port.
Example: Client uses a specific name to connect. In this case provided there is a Node with a matching name the
connection will be made
Ports
Port
, Baud ….
P1
, ….
Nodes
Node_Name , Protocol
Node1
, SNP
The Node must be connected to
the Client’s port P1. The Node
name is ignored and connection
is made to the Node through P1,
If there is a Node Called Node1
the connection will be made.