Filter
Top Products
FS-8700-86 Carrier DataPort Page 11 of 32
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
5.2. Server Side Connections
Section Title
Connections
Column Title Function Legal Values
Port
Specify which port the device is connected to
the FieldServer
P1-P8, ( R1-R2 with converter)
4
Baud* Specify baud rate
300, 600 , 1200, 2400, 9600
(Vendor limitation)
Parity* Specify parity
None (Vendor limitation)
Data_Bits*
Specify data bits
8 (Vendor limitation)
Stop_Bits*
Specify stop bits
1 (Vendor limitation)
Protocol
Specify protocol used CarrierDP
Handshaking*
Specify hardware handshaking
None
Example
// Server Side Connections
Connections
Port, Baud,
Parity, Data_Bits,
Stop_Bits,
Protocol , Handshaking,
Poll_Delay
P8, 9600,
None,
8 , 1 , CarrierDP,
None , 0.100s
5.3. Server Side Node Descriptors
Section Title
Nodes
Column Title Function Legal Values
Node_Name Provide name for Node
Up to 32 alphanumeric
characters
Node_ID
DataPort station address of physical Server Node.
These correspond to the ‘devices’ configured in the
DTPConfig. Thus the Node_ID is not the address of
the final CCN device.
The DataPort DTPConfig table maps a device
number (1...15) to a bus number (0-239). Use the
Node_ID to tell the driver which device to use.
1-15
Protocol Specify protocol used CarrierDP
Example
// Server Side Nodes
Nodes
Node_Name, Node_ID, Protocol , Port
5
FAN1 , 1 , CarrierDP, P8
4
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction
manual for details of the ports available on specific hardware.
5
It is common to leave server nodes unconnected to a port. This means that the FieldServer can respond
with the Node’s data irrespective of which port the request is received on.