Robust, Versatile
Contains advanced programming and communication capabilities
Documents WEATHER Documents WATER Documents ENERGY Documents MACHINES Documents STRUCTURES 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.

Download the Trial

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 data logger 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

Detailed 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. The LoggerNet server stores the data in a cache and writes data to a variety of formats, including ASCII, binary, and XML.

The LoggerNet server and client applications enable you to do the following:

  • 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
  • Collect data on demand or schedule
  • Monitor and troubleshoot the network
  • Display real-time data in a numeric display or graph
  • View and graph data files
  • Create graphical data displays that update when data is collected and allow you to control flags, ports, and variables
  • Create automated tasks
  • Process data files using Split
  • Save data in formats (including CSV and XML) that can be imported into third-party analysis packages.

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

Frequently Asked Questions

Number of FAQs related to LOGGERNET: 125

Expand AllCollapse All

  1. If the dataloggers are connected over some form of serial/PakBus link, they can be synchronized with each other using the ClockReport() and PakBusClock() instructions in the dataloggers. Use the ClockReport() instruction in the master (time) datalogger and the PakBusClock() instruction in the slave dataloggers. 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 dataloggers storing their data.

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

  2. Follow these steps:

    1. On the Windows computer, open the LoggerNet Setup screen.
    2. In the Backup menu, select the Manual Backup option to create a backup of the network.
    3. On the same or different Windows computer, use LoggerNet Remote software to connect the Setup screen to the LoggerNet for Linux server (File | Select Server).
    4. Restore the network backup (Backup | Restore Network).
    5. Review the restored settings in the Setup screen. Some settings (such as COM ports, modems, data file paths, etc.) may need to be adjusted.
  3. LoggerNet does not do a clock check unless there is another reason to contact the datalogger, such as for scheduled collection.

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

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

  6. Yes. LoggerNet can be configured to store data in a binary file format.

    Follow these steps:

    1. In the LoggerNet Setup screen, select the datalogger.
    2. Choose the Data Files tab.
    3. In the Output Format field, select Binary data.
  7. LoggerNet cannot do this directly via scheduled data collection, but there are a few ways to accomplish this:

    1. Use the LoggerNet Split application to parse the LoggerNet DAT file into a monthly summary file. Split can be triggered manually or set up as a calendar-based scheduled task in the Task Master that runs on the Last day of every month.
    2. Set up the datalogger as a different datalogger in the LoggerNet network map, and then set up a calendar-based scheduled task in the Task Master to collect data on the Last day of every month.
    3. To store data in a database, and manually query the data on a monthly basis, use LNDB (LoggerNet Database Software).
  8. The station’s datalogger clock can be set from the Connect screen. It can also be set from the Clock tab in the Setup screen.

  9. The LoggerNet Toolbar uses the TCP/IP protocol to communicate with the LoggerNet server. If two instances of LoggerNet are being run on the same computer, there would be a TCP/IP port conflict because they are both trying to use the same port.

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
Utah: Rural Irrigation
--> Horseshoe Irrigation is a small, rural irrigation company in central Utah, managing around 15,000 water shares for 640 shareholders. more
North Carolina: Monitoring “Green” Hotel
--> When Dennis Quaintance decided to build the Proximity Hotel in Greensboro, North Carolina, he knew he wanted the hotel’s more
New Hampshire: Webcams in Forest
--> The Hubbard Brook Experimental Forest (HBEF), located in the White Mountain National Forest of central New Hampshire, was established more
Pennsylvania: Monitoring Landfills
Landfills present many environmental challenges, ranging from odor control to groundwater quality. Continuous, accurate monitoring of site conditions provides more
Florida: Protecting an Endangered Species’ Habitat
The South Florida Water Management District (SFWMD) has a mission to manage and protect the region’s water source. One more
Chile: Solar-Energy Assessment
Solar energy resource assessment projects are critical to the successful siting of solar thermal power plants. Before a plant 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