Troubleshooting

This section covers some common problems that might be encountered when using the NL200/201. This is not comprehensive but should provide some insight and guidance to correct simple errors yourself.

When your Campbell Scientific software cannot establish a link to a remote data logger that is connected to the NL200/201, do the following:

1. Check all the power connections.

   Your NL200/201 and any hub and/or router being used must be connected to power. Check power indicator lights to make sure your devices are powered.

2. Check all cables.

   Verify that your Ethernet cable is securely plugged in between your NL200/201 and your hub, router, or computer. The yellow Link/Act light on the NL200/201 should start flashing when it is connected to the Ethernet.

   If an Ethernet cable is connected but the Link/Act light is not flashing, try a new Ethernet cable. You can also try moving the existing Ethernet cable to a functioning system to determine if the cable is working.

3. Power cycle the NL200/201 and your hub/router/computer.

   Turn off or unplug your hub/router/computer and NL200/201. Wait 10 seconds and then plug them back in or turn them on. A full restart may take 30 to 60 seconds.

4. Check the settings of the NL200/201.

   1. Make sure the assigned NL200/201 IP address (DHCP or static) and the IP address of the computer you are trying to connect from are able to communicate with each other. (Your network administrator can help with this.)

      For example, the following addresses are able to communicate:

      NL200/201: IP address: 192.168.0.2, Network Mask: 255.255.255.0

      Computer: IP address: 192.168.0.3, Network Mask: 255.255.255.0

   2. If using DHCP to assign an IP address to the NL200/201, use Device Configuration Utility to read the IP address assigned to the NL200/201. This is done through a USB connection to the NL200/201 while the NL200/201 is connected to your network (if bridge mode is not being used).

   3. The IP address assigned to the NL200/201 must be unique on your network.

   4. When bridge mode is enabled, the data logger controls how the IP address is assigned. Make sure your data logger is connected correctly to the NL200/201 via the CS I/O port and SC12 cable.

5. Try to ping the NL200/201 from your computer. (From the Windows Start Menu, type command, and click Command Prompt. Then type ping xxx.xxx.xxx.xxx where xxx.xxx.xxx.xxx is the IP address of your NL200/201.) If no packets are returned, this indicates that there is no network connection to that IP address.

6. Make sure the IP address and port number entered in LoggerNet/RTDAQ/PC400 match the settings in the NL200/201.

   NOTE:

   PakBus and serial server communications use different port numbers. The default port number for PakBus communications is 6785. The default port number for CS I/O serial server communications is 6783. The default port number for RS-232 serial sever communications is 6784. The correct port number must follow the IP address of the NL200/201 in LoggerNet Setup in order for LoggerNet to communicate through the NL200/201. For example, if the NL200/201 is configured as a CS I/O serial server, in LoggerNet Setup, enter the correct IP address of your NL200/201 followed by :6783 (for example, 192.168.0.3:6783).

7. If you are unable to communicate with the NL200/201 via the USB cable, verify that the latest drivers for the NL200/201 have been installed. These can be downloaded from our website at www.campbellsci.com/downloads .

8. If the NL200/201 is configured as a CS I/O serial server, verify that any other SDC device attached to the data logger is using a different SDC address. For example, if the NL200/201 is configured for SDC7, any other device attached to the data logger cannot use SDC7.

9. If communicating over a slow or intermittent connection, it may be necessary to lower the Maximum Packet Size of the data logger in LoggerNet Setup and/or add Extra Response Time to the PakBus Port in LoggerNet Setup.

10. Reset the NL200/201 to its default settings.

    If none of the above steps correct your communications problems, reset the NL200/201 to its default settings. This can be done using the Factory Defaults button in Device Configuration Utility or by using the Defaults command in a Telnet session with the NL200/201.

11. Verify that the latest revision of firmware (operating system) is running. It is possible that an issue affecting your ability to communicate via the NL200/201 is resolved in the latest version. The latest firmware version and its revision history can be found at www.campbellsci.com/downloads . There is no charge for this download. See Sending a new OS to the NL200/201 for instructions on downloading the firmware revision to the NL200/201.

12. If the above steps do not resolve the issue, please call Campbell Scientific, for help. Before calling, it would be helpful to do the following:

    1. Obtain a detailed description of your network setup including TCP/IP address, port number, PakBus settings, and other pertinent information regarding all of the devices in the NL200/201 communications network.

    2. Save a copy of the NL200/201 settings (in XML format) using Device Configuration Utility.

    3. Save a copy of the NL200/201 event log. This is low-level code that can be used by Campbell Scientific technical support to help troubleshoot the NL200/201. To obtain the event log, the NL200/201 must not be in bridge mode. Telnet into the NL200/201 using your favorite Telnet program. Once logged in, type “eventlog” at the prompt. Record the date and time that you did this. Copy and paste the output into a text file.

    4. Once the eventlogs have been copied, type “eventlog erase” at the prompt to clear the log. To add a date to indicate when the logs were last cleared enter “eventlog erase date” where date is a string of up to 8 characters.

After calling Campbell Scientific for help, email your network description, the newly created text files, and the saved XML settings file to the person you are working with.