Campbell Scientific NL100 Network Link Interface - Manual (Page 15)

NL100/105 Network Link Interface
CR10X, CR510, CR23X, 21X, and CR7 dataloggers ship with a
mixed array operating system. Mixed array dataloggers do not
support the PakBus communications protocol. Therefore, you
cannot communicate with them over a port configured for
PakBus. However, the CR10X, CR510, and CR23X dataloggers
can be special-ordered with a PakBus operating system. Check
with your technical support representative for details. NOTE
PakBus - This option is only used when setting up the NL100/105 to
communicate with other PakBus devices in the network. Packets transferred
over the CS I/O port in this mode are framed as PakBus packets; therefore, any
device attached to the port must be capable of PakBus communication. When a
port is configured for PakBus, the NL100/105’s “PakBus/Tcp Server Config”
option must be enabled (Section 2.4.3.7) or you will not be able to
communicate with TCP/IP through the NL100/105 to the PakBus devices on
that port.
When configured for PakBus, the NL100/105's CS I/O port has the following
settings:
CS I/O SdcAddr/bps - This option is used to set up the CS I/O port to
communicate with the datalogger as an addressable SDC device or a
modem enabled device. If SDC7 or SDC8 is chosen, the NL100/105 will
use that address to communicate with the datalogger in a synchronous
communication mode. If one of the baud rates is chosen, the NL100/105
will communicate with the datalogger as a modem enabled device using
the selected baud rate. If another SDC device is connected to the
NL100/105, the two devices must use different SDC addresses.
CS I/O Beacon Interval - The NL100/105 can be set to transmit a beacon
to a PakBus network via the selected port. The beacon allows the
NL100/105 to determine which devices in the PakBus network it can
communicate with. Note that because a beacon is broadcast to all devices,
it can interfere with other communication in the network (such as RF), so
a frequent beacon may not be desirable. If 0 is entered, no beacon will be
sent; the default beacon is 60 seconds.
CS I/O Verify Interval - This is the interval at which a PakBus
communication link will be verified over the CS I/O port. If
communication does not take place with a PakBus device within the
verify internal, a packet will be sent to test the communication link. In
most instances, this setting should be left at the default of 0, which will
set a verify interval of 2.5 times the Beacon Interval.
If both the beacon interval and verify interval are set to 0, a verify interval
of 5 minutes will be used.
A neighbor list is not specified because there is only one possible
neighbor. NOTE
TcpSer - This option configures the NL100 to act as a TCP/IP based serial
server when communicating with the datalogger over its CS I/O port.
11