LOGGERNET Datalogger Support Software

Expand AllCollapse All

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

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

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

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

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

7. Is there a possibility to auto-update the graphs in View Pro or other functions inside LoggerNet 4 without pushing the Refresh button in View Pro?

   View Pro is meant to be a file viewer, so there is no automatic update capability.

   To view graphs in real time, there are graphs that can be launched from the numeric monitor. For fully customizable displays, RTMC can be used. RTMC uses the LoggerNet server for its data source, but RTMC Pro (purchased separately from LoggerNet 4) can also use a DAT file.

8. How can LoggerNet be programmed to download data only from the last download and not data that were previously downloaded?

   In the LoggerNet Setup screen, on the Data Files tab, there are these Collect Mode options:

   • Data Logged Since Last Collection
   • Most Recently Logged Records
   • Collect At Most
9. Does the license for LoggerNet include the application in a virtualized form (App-V sequencing)?

   No. For the current licensing information, refer to the LoggerNet Instruction Manual.

10. Does LoggerNet stay connected to the data logger after the scheduled collection is finished?

    If only scheduled collection is running, LoggerNet will connect to the data logger, collect the data, and then disconnect automatically.