Robust, Versatile
Contains advanced programming and communication capabilities
Related Documents WEATHER Related Documents WATER Related Documents ENERGY Related Documents MACHINES Related Documents STRUCTURES Related Documents EARTH


Current Version: 4.3

LoggerNet is our main datalogger support software package. It supports programming, communication, and data retrieval between dataloggers and a PC.

LoggerNet consists of a server application and several client applications integrated into a single product. It can support connection to a single datalogger, but it is especially adept in applications that require telecommunications or scheduled data retrieval used in large datalogger networks.

Version 4 is our most recent major upgrade to LoggerNet that features a new tool for designing and configuring PakBus® networks, a more powerful file viewer, an upgrade to RTMC, a redesigned toolbar, and many updates to existing clients. Learn more about the upgrade in the brochure and manual linked in the Related Documents section on this page.

Version 4.3 adds support for the CR6-series dataloggers.

A copy of the current software license agreement (end-user license agreement) for LoggerNet is available in the LoggerNet Instruction Manual.

Benefits and Features

  • Creates custom datalogger programs using Edlog or CRBasic
  • Displays or graphs real-time or historic data
  • Builds custom display screens to view data or control flags/ports
  • Retrieves data using any of our telecommunication options
  • Processes data files using Split
  • Saves data in formats (including CSV and XML) that can be imported into third-party analysis packages

Technical Description

The standard LoggerNet software package is recommended for those who have datalogger networks that do not require the more advanced features offered in LoggerNet Admin. It includes the LoggerNet server and client applications that allow you to program the datalogger, collect data, monitor and troubleshoot the network, manage the dataloggers in your network, create graphical data displays that update when data is collected, create automated tasks, and view or post-process the data.

The client applications included in the standard LoggerNet software package are the following:

  • Setup
  • Connect
  • Status Monitor
  • Task Master
  • Short Cut
  • CRBasic Editor
  • Edlog
  • Transformer
  • RTMC Development
  • RTMC Run-Time
  • View Pro
  • Split
  • CardConvert
  • Troubleshooter
  • Network Planner
  • PakBus Graph
  • LogTool
  • Device Configuration Utility
  • CoraScript
  • RWIS Administrator

The LoggerNet server stores the data in a cache and writes data to a variety of formats, including ASCII, binary, and XML.

LoggerNet allows you to:

  • Configure the server to communicate with multiple dataloggers via a variety of communications hardware
  • Create custom datalogger programs using Short Cut, Edlog, or the CRBasic Editor
  • Connect to a datalogger to check or set the clock, send programs, or perform other administrative functions
  • Display or graph data
  • Build a custom display screen to view data or control flags/ports
  • Collect data on demand or schedule
  • Process data files using Split
  • Save data in formats (including CSV and XML) that can be imported into third-party analysis packages.


Version History
  • LoggerNet 4.x series replaced LoggerNet 3.x series on August 28, 2009.
  • LoggerNet 3.x series replaced LoggerNet 2.x series on 24 November, 2004.
  • LoggerNet 2.x series replaced PC208W on January 1, 2003.


  • PC Operating System: Windows 8, 7 (32 and 64 bit), Vista, or XP
  • Current Version: 4.3
  • Military Certificate of Networthiness (CoN):  
    • LoggerNet 4.0 is certified as Cert #201004872.
    • LoggerNet 4.x is certified as an upgrade to 4.0 and has ASC CoN ID 12274.
    • Expires 1/13/2017.



LoggerNet runs on a PC, using serial ports, telephony drivers, and Ethernet hardware to communicate with dataloggers via phone modems, RF devices, and other peripherals.


The development tool of RTMC Pro 1.x and 2.x is not compatible with the RTMC run-time and the standard RTMC development tool in LoggerNet 4. An upgrade for RTMC Pro must be purchased separately.


LoggerNet is a collection of 32-bit programs designed to run on Intel-based computers running Microsoft Windows operating systems. The recommended minimum computer configuration for running LoggerNet is Windows XP. LoggerNet also runs on Windows Vista, Windows 7, and Windows 8. LoggerNet runs on both 32-bit and 64-bit versions of these operating systems.

Datalogger Considerations

Compatible Contemporary Dataloggers

CR200(X) Series CR800/CR850 CR1000 CR3000 CR6 CR7X CR9000X

Compatible Retired Dataloggers

CR500 CR510 CR10 CR10X 21X CR23X CR9000 CR5000
* * ** *

*For our CR510, CR10X, and CR23X dataloggers, LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems.
**The 21X requires three PROMs; two PROM 21X Microloggers are not compatible.


LoggerNet Patch v.4.3 (209 MB) 26-11-2014

This patch will upgrade LoggerNet, LoggerNet Remote or LoggerNet Admin version 4.0 and newer to 4.3. A version of LoggerNet 4.x must be installed on the computer. 

Note: This application requires the Microsoft .Net 4.0 Framework.  If it is not already installed on your computer,  it can be obtained from the Microsoft Download Center.

View Revision History

What's new in LoggerNet 4 Tutorial (exe format) v.- (12.9 MB) 14-09-2009

LoggerNet 4.0 was released in August of 2009. This tutorial demonstrates some of the new features and enhancements. Two new applications, View Pro and the Network Planner, are introduced.

What's new in LoggerNet 4 Tutorial (pdf format) v.- (8.46 MB) 14-09-2009

LoggerNet 4.0 was released in August of 2009. This tutorial demonstrates some of the new features and enhancements. Two new applications, View Pro and the Network Planner, are introduced.

Note: Adobe Reader 9 or later is needed to view this tutorial.

LoggerNet German v.4.0 (980 KB) 21-07-2010

German language files for LoggerNet 4.0.

LoggerNet Spanish v.4.1 (902 KB) 17-02-2012

Spanish language files for LoggerNet 4.1.

LoggerNet Trial v.4.3 (219 MB) 26-11-2014

This is a fully functional 30 day trial of the standard version of LoggerNet.

Current LoggerNet users: It is recommended that you install the trial on a computer other than the one running your existing LoggerNet. If that is not practical, we strongly recommend you back up the LoggerNet working directory to prevent backward compatibility issues if you revert to a previous version. To revert you must re-install LoggerNet using the original disk and software key.

Note: This application requires the Microsoft .Net 4.0 Framework.  If it is not already installed on your computer,  it can be obtained from the Microsoft Download Center.

View Revision History

LoggerNet Patch (Small) v.3.4.1 (68.7 MB) 22-10-2007

If you already have LoggerNet 3.2, 3.2.1, 3.2.2, 3.3, 3.3.1 or 3.4 installed you can download this smaller version of the patch. (Patches from 3.2, 3.2.1, 3.2.2, 3.3, 3.3.1 or 3.4 to 3.4.1 only.)

LoggerNet Patch (Large) v.3.4.1 (74.2 MB) 22-10-2007

This patch upgrades LoggerNet version 3.0 and newer to 3.4.1. A version of LoggerNet 3.x must be installed on the computer. If you are using a version of LoggerNet 2.x, you must purchase an upgrade.

Note: Starting with LoggerNet 3.2, the included RTMC data display client has moved from Version 1.x to 2.x. This will require you to also upgrade from RTMC Web Server 1.x or RTMC Run-time 1.x if you also use those products.

View Revision History

FAQs for

Number of FAQs related to LOGGERNET: 128

Expand AllCollapse All

  1. With newer dataloggers, such as the CR1000, the default output file format is TOA5. This format requires that a header be present that accurately describes the data that will follow. LoggerNet cannot append to this file format without first checking the header of the existing file. If that header disagrees with what LoggerNet knows about the table, it will back up the existing file and start a new one with the proper header.

    If it is not desired to have this checking take place, the format of the file can be modified in LoggerNet by specifying the Output Format field for the table as ASCII Table Data, No Header or Array Compatible CSV.

  2. The cache for a particular datalogger can be cleared by updating its table definitions in LoggerNet, but data cannot be imported into the cache from a data file, and the cache cannot be edited. To clear the cache, choose Reset instead of Merge when updating table definitions for the datalogger.

    If long-term storage in a database is required, consider purchasing LNDB (LoggerNet Database Software).

  3. The Retrieve button, used to retrieve a program from a datalogger, is found on the LoggerNet Connect screen. Note that some dataloggers, such as the CR200X-series, do not store the program in a retrievable format, and the Retrieve button will be disabled.

    There is also a File Retrieval tab in LoggerNet on the Setup screen that can be used to retrieve files stored on the datalogger.

  4. In the LoggerNet Setup screen, on the Data Files tab, select the browse 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 datalogger 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.

  5. LoggerNet does not do a clock check unless there is another reason to contact the datalogger, such as for scheduled collection.

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

  7. The security code is set up in the datalogger Hardware tab of the LoggerNet Setup screen. Unlike the Device Configuration Utility, LoggerNet will not prompt for the security code on connection, so the setting has to be in the setup information.

  8. Using the LoggerNet Connect screen, check the datalogger Status table.

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

  10. Check the trans*.log in the C:\Campbellsci\LoggerNet\Logs directory. When a clock set occurs, it will show up in the logs (for example, the words "Clock Set" with a date and time of the occurrence).

Case Studies

Chicago Botanic Gardens Green Roof
The 385-acre Chicago Botanic Garden welcomes more than 750,000 visitors each year. Its new Daniel F. and Ada L. more
Pennsylvania: Monitoring Landfills
Landfills present many environmental challenges, ranging from odor control to groundwater quality. Continuous, accurate monitoring of site conditions provides more
South Africa: Solar Prospecting
Historically, the South African energy sector had been monopolized by a single state-owned utility company (Eskom) whose generating capacity more
New Hampshire: Collecting Data from Experimental Forest
The Hubbard Brook Experimental Forest (HBEF), located in the White Mountain National Forest of central New Hampshire, was established more
Utah: Water-Supply SCADA System
In 2010, Trenton and Amalga, two northern Utah towns separated by only a few miles, created a plan to more
Korea: Damage from Freezing Roads
Korea Expressway Corporation (KEC) was established in 1969 to construct and manage expressways throughout South Korea. KEC’s goal has more

Listed Under

Other Accessories for the following products: