LoggerNet Datalogger Support Software

Expand AllCollapse All

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

2. Is there a tutorial available for RTMC?

   Yes. The “Getting Started with RTMC Tutorial” is available for download.

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

4. Is there any way to set a variable in the data logger using LoggerNet to gain manual control over when data is collected by the data logger?

   A program snippet, such as the one below, would work for this purpose. The Boolean variable can be toggled from the Ports & Flags screen in LoggerNet (accessed via the Connect screen), through the Numeric Display (also accessed via the Connect screen), or under program control.

   public StoreDataFlag as boolean

   DataTable (ConditionalTable,StoreDataFlag,100)

             Sample (1,counter,Long)

   EndTable

   When storing data conditionally, be sure to allocate a specific number of records in the size parameter of the DataTable() instruction. For more information, see the Data Table Memory Allocation Tutorial.

5. Is there a way to set LoggerNet to download only the last x number of hours of data?

   On table-based data loggers, in the LoggerNet Setup screen, on the Data Files tab, there is the Collect at Most option that can be used to indicate how many records to collect. Based on how often data is stored, a calculation can be made to determine how many records represent x hours of data.

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

7. Can the LoggerNet software used for a CR10X be used with a CR850 or CR800?

   LoggerNet version 3.3 and newer supports the CR10X, the CR800, and the CR850.
8. Can the CRBasic Editor be purchased without LoggerNet, or do they have to be purchased together?

   The CRBasic Editor is included with LoggerNet, PC400, and RTDAQ, which are software options available for purchase. The CRBasic Editor can also be purchased separately: www.campbellsci.com/crbasiceditor. 

   The CRBasic Editor has a number of features, such as syntax highlighting, context-sensitive help, a program precompiler, etc. However, the CRBasic Editor is not required to edit a data logger program. All data logger programs are simply text files that can be edited with any editor capable of handling plain text, such as Notepad, WordPad, vi, or Emacs. Caution should be used, however, editing a program in a text editor. Coding mistakes can make the data logger program run incorrectly or not at all.

9. How can the Record Number (RECNBR) be turned off in LoggerNet so that it is not saved with all the other values?

   In the LoggerNet Setup screen, on the Data Files tab, select the  button beside the Output Format field. This will open a dialog box that enables turning off Record Number. The option to not produce the record number was introduced in LoggerNet 4.0.

   In typical use, the data logger itself does not store the record number or timestamp with each individual record in its own memory. Those values are generated by calculation when the data is retrieved.

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.