Campbell NL200, Instruction Manual

Page: 53 / 61

Appendix C. NL200/201 Settings
C-8
detected for the timeout period. Set to 0 for no time-out (not recommended).
(range 0..999)
CS I/O PakBus Beacon Interval
This setting, in units of seconds, governs the rate at which the NL200/201 will
broadcast PakBus® messages on the associated port in order to discover any
new PakBus neighboring nodes. It will also govern the default verification
interval if the value of the Verify Interval setting for the associated port is zero.
CS I/O PakBus Verify Interval
This setting specifies the interval, in units of seconds, that will be reported as
the link verification interval in the PakBus® hello-transaction messages. It
will indirectly govern the rate at which the NL200/201 will attempt to start a
hello transaction with a neighbor if no other communication has taken place
within the interval.
CS I/O Modbus Timeout
This setting determines how long the MODBUS/TCP to MODBUS/RTU
gateway will wait for an answer from the MODBUS slave device(s) attached to
the CS I/O port. If no answer is received within the timeout period, the
MODBUS/TCP server will reply to the MODBUS/TCP client with error code
0x0B(Target Device Failed to Respond). (milliseconds)
C.4 Net Services Tab
Telnet
Enables/Disables the telnet service.
Telnet Port Number
The default TCP port number for the configuration monitor telnet session is 23.
This entry makes it possible for the user to change the telnet session port
number if desired. Typically, it is not necessary to change this entry from its
default. (range 1..65535)
Telnet Timeout
This setting, in units of seconds, will determine how fast the configuration
monitor telnet session will time out if no activity is detected. Set to 0 for no
time-out (not recommended). (range 0..999)
Ping (ICMP)
The NL200/201 will not respond to “Ping” requests if this setting is disabled.
PakBus Address
This setting specifies the PakBus® address for this device. The value for this
setting must be chosen such that the address of the device will be unique in the
scope of the datalogger network. Duplication of PakBus addresses in two or
more devices can lead to failures and unpredictable behavior in the PakBus