LoggerNet Datalogger Support Software

Expand AllCollapse All

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

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

4. 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.
5. Can multiple networked data loggers be time synchronized programmatically?

   If the data loggers are connected over some form of serial/PakBus link, they can be synchronized with each other using the ClockReport() and PakBusClock() instructions in the data loggers. Use the ClockReport() instruction in the master (time) data logger and the PakBusClock() instruction in the slave data loggers. The option to broadcast to all can be used (providing no routing is needed), which means that just one packet of information is sent.

   The ClockReport() instruction can be used as frequently as desired, although, for practical purposes, once or twice a day should be adequate for most applications. The clock should be set at a time that does not interfere with the timing of data loggers storing their data.

   If the data loggers are connected over an IP network, use the NetworkTimeProtocol() instruction so that one data logger acts as the time server.

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

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

9. Is there a tutorial available for RTMC?

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

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