Page 25 of | Page 25 of 29 |
Appendix C. Advanced Topics
Appendix C.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 do so by sending the name of the Node it wishes to connect to or by sending a Null Node name.
If the Client 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. In such a case the Node must be connected to a port (This is not always common with FieldServer Server configurations).
Example: Client uses Null name connection. In this case Node must be connected to the Client’s port; the Node name is ignored and only one SNP Node per port.
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 |
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldServer.com Tel: (408)