LOGGERNET Datalogger Support Software

Expand AllCollapse All

1. Why might the numeric and graph displays (accessed from the LoggerNet Connect screen) no longer update?

   If communication is interrupted or intermittent, LoggerNet may stop updating the Table Monitor, Numeric Display, and Graphs. When this occurs, a button on the display that is normally titled Stop (to stop the update) changes to Start, and the button must be pressed to resume the update. Also, check the update interval on the display, as it may be set to a higher value than expected.

2. How can data during a certain duration be erased without erasing the configuration and the program?

   There is no mechanism to selectively erase data from the data logger for a given date range. However, the data tables in the data logger can be reset, which effectively erases the data.

   Note: Following these steps will cause the loss of all data:

   1. In the LoggerNet Connect screen, click the Station Status button.
   2. When the dialog box opens, select the Table Fill Times tab, which shows the data tables in the data logger and their sizes.
   3. Either select individual tables, or select the Select All checkbox.
   4. Click the Reset Tables button. This will erase all data in the tables.
3. What would cause a message from LoggerNet that the settings are locked by a user?

   A client lock is automatically created by the Setup screen when a user begins to make changes. This lock will remain until the changes have been committed or cancelled, or until the connection between the Setup screen and the LoggerNet server is severed.

4. After installing an upgrade to the current version of LoggerNet, why does the Toolbar no longer show all the buttons?

   There is a difference between the Toolbar initialization files used in earlier 3.x versions of the software and more recent versions.

   To resolve this, close LoggerNet. Go to C:\Campbellsci\LoggerNet\sys\inifiles and delete the Toolbar.ini file. When LoggerNet is reopened, the Toolbar should display the default buttons.

5. Does the LoggerNet server have a specific limit on the length of a generic modem script?

   The LoggerNet server imposes no specific limits on the lengths of the generic modem scripts.

6. What might cause Windows to display a "Blue Screen of Death" when LoggerNet is running?

   Typically, blue screens are the result of bad device drivers. The Internet can be very helpful in tracking down the cause of blue screens. Copy down the codes displayed. Search the Internet for “blue screen” and the code to see what device is causing the crash. Often, an updated device driver will resolve the issue.

7. Can backups from older versions of LoggerNet work on newer versions?

   Typically, a backup from an older version of LoggerNet will work on a newer version, but there will be issues trying to go from a newer version back to an older version.

8. How long does it take to install LoggerNet?

   The LoggerNet application is distributed on CD media and can be installed in minutes.

9. What is the station name?

   There are two station names associated with a data logger. One name is the Station Name used in the LoggerNet network map. The other name is the Station Name field in the data logger Status table. Almost all data file formats work in LoggerNet include a station name in the header of the data file. By default, the network map station name is used. However, a checkbox in the LoggerNet Setup window, Data Files tab, allows choosing the data logger Status table station name instead.

10. Would there be any major problems with moving a data logger to another communications path while someone is using the LoggerNet software?

    As long as the same device is being moved from one communications route to another, all data collection pointers, filenames, etc., will be maintained with that data logger as it is moved.