LoggerNet Datalogger Support Software

Expand AllCollapse All

1. If LoggerNet does not list the NL120, is that OK?

   Yes. The NL120 operates as transparent.

2. 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.

3. 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.

4. Why does LoggerNet create a backup data file every time data collection is triggered?

   Before it appends to a TOA5, TOB1, or TOACI1 data file, LoggerNet first scans the header of that file and compares the information that it contains with the information reported in the data logger table definitions. For TOA5, the following conditions can result in errors that will cause LoggerNet to refuse to append to the file:

   • The table names do not match.
   • The number of columns does not match.
   • One or more column names do not match.
   • The number of units strings does not match the number of column names.
   • The number of process strings does not match the number of column names.

   There have been cases where, using the FieldNames() instruction, the data logger program specified a double quote character (") in the units string, and this character unbalanced the quote marks in the TOA5 format, which in turn threw off the TOA5 parser.

5. How does LoggerNet handle data collection when the data logger stores data to a CompactFlash card?

   LoggerNet collects data from the data logger first. If there is additional data on a CompactFlash card, LoggerNet collects that also. Nothing special needs to be set up in LoggerNet to have this occur.

6. 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.

7. 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.
8. 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.

9. How can a data logger be switched out (for example, from a CR800 to a CR1000) in LoggerNet?

   Follow these steps:

   1. In the Setup screen, record the pertinent data from the Schedule and Data Files tabs. 
   2. Delete the listed data logger.
   3. Add the new data logger. 
   4. Adjust the settings on the Schedule and Data Files tabs to match what was being done previously.
      • If the settings are complicated, review the Help menu from the Setup screen to learn more about the option in LoggerNet 4.2 to Copy Device Settings in the Tools menu.
10. 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.