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

NL100/105 Network Link Interface
2.4.9 Serial Server Watchdog
If no communication is detected for a specified number of minutes, the
NL100/105 will drop the communications link. This feature is called a
"watchdog". The watchdog alleviates the problem of a communications port
being held open, thus rendering the device inaccessible, if the NL100/105 and
the remote device failed to terminate the communications link in a "normal"
manner. The NL100/105 will wait two minutes for activity on a port before
timing out. This affects all communication modes, including when the
NL100/105 is configured as a PakBus based or TCP/IP based serial server, and
when communicating with the NL100/105 during a Telnet session.
3. Connecting the NL100/105 to a Network
3.1 Network to NL100 Connection
The connection from the computer network to the NL100/105 10 Base-T port
should be a twisted pair cable. A male RJ-45 plug connector should be on the
cable end going into the 10 Base-T port.
If the cable is to be run directly from the computer to the NL100/105, a
crossover cable is required. If the cable will be run from a hub to the
NL100/105, a straight through cable should be used. Appendix C shows the
pin-outs for these two cable types.
3.2 Typical Configurations
The cases below assume the NL100/105 is being connected to a mixed array
datalogger using the datalogger's CS I/O port (CR10X, CR510 CR23X) or RS-
232 port (CR23X). TD-based dataloggers (CR10X-TD, CR510-TD, and
CR23X-TD) are configured similarly. In these instances, the communication
port(s) being used on the NL100/105 should be set up as TcpSer (TCP/IP
based serial server). When communicating with PakBus devices (CR1000,
CR3000, CR800/850, CR200, CR10XPB, CR510PB, or CR23XPB), the
communication port on the NL100/105 can be configured for PakBus or
TcpSer, depending upon the role the NL100/105 is to play in the network. In
many cases, the TcpSer option can be selected.
For mixed array and TD dataloggers, the network map for the LoggerNet
software should depict an IPPort root device with the datalogger attached
directly to the IPPort (see Figure 3) unless otherwise noted. For PakBus
dataloggers, a PakBus Port must first be added to the IP Port in the network
map, and then the PakBus datalogger attached to the PakBus Port. In instances
where the NL100/105 is to be a PakBus router, a pbRouter must be added after
the PakBus Port and before the PakBus datalogger. In some instances, extra
response time (3 to 4 seconds) may need to be added to the IPPort and/or the
datalogger to account for network traffic delays over a TCP/IP connection.
The IP Address entered in the software for the NL100/105
should not contain leading zeros. If leading zeros are used, the
communications attempts will fail. NOTE
19