LOGGERNET Datalogger Support Software
Robust, Versatile
Contains advanced programming and communication capabilities
weather applications supported water applications supported energy applications supported gas flux & turbulence applications supported infrastructure applications supported soil applications supported

Overview

Current Version: 4.5

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.4 adds support for the CR300-series dataloggers.

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

Read More

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

Images

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

Specifications

Current Version 4.5
Operating System Windows 10, 8, or 7 (Both 32- and 64-bit operating systems are supported.)

Military Certificate of Networthiness (CoN)

-NOTE- Expires 1/13/2020.
Certifications LoggerNet 4.x is certified as Cert #201416752.

Compatibility

Please note: The following shows notable compatibility information. It is not a comprehensive list of all compatible products.

Dataloggers

Product Compatible Note
21X (retired) The 21X requires three PROMs; two PROM 21X Microloggers are not compatible.
CR10 (retired)
CR1000
CR1000X
CR10X (retired) LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems.
CR200X (retired)
CR211X (retired)
CR216X (retired)
CR23X (retired) LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems.
CR300
CR3000
CR310
CR500 (retired)
CR5000 (retired)
CR510 (retired) LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems.
CR6
CR800
CR850
CR9000 (retired)
CR9000X

Additional Compatibility Information

Communications

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

Software

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.

Computer

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 7. LoggerNet also runs on Windows 8 and Windows 10. LoggerNet runs on both 32-bit and 64-bit versions of these operating systems.

Downloads

LoggerNet Patch v.4.5 (310 MB) 18-08-2017

This patch will upgrade LoggerNet, LoggerNet Remote or LoggerNet Admin version 4.0 and newer to 4.5. 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.

Supported Operating Systems: (32 and 64 bit) Windows 10, 8.1, 8 or 7.

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.


German Language Pack v.4.4 (741 KB) 17-08-2016

German language files for LoggerNet 4.4 and 4.4.1.

Note: Language support for the above listed versions only.


LoggerNet Trial v.4.5 (314 MB) 18-08-2017

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.

Supported Operating Systems: (32 and 64 bit) Windows 10, 8.1, 8 or 7.


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

Related FAQs

Number of FAQs related to LOGGERNET: 127

Expand AllCollapse All

  1. 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. Follow these steps:

    1. Connect to the datalogger using the LoggerNet Connect screen.
    2. Find the datalogger in the Stations list, and right-click it.
    3. From the menu that is displayed, choose the Settings Editor.
  3. Network Planner is new to LoggerNet 4.0. It was specifically designed to help set up dataloggers in PakBus networks so that they can communicate with each other and the LoggerNet server.

    The Network Planner allows the graphical layout of devices and the specification of the links between the devices. It can then use that information to generate settings for all the devices and provide the means to program those settings into the devices and also to configure LoggerNet.

  4. There is no mechanism to selectively erase data from the datalogger for a given date range. However, the data tables in the datalogger 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 datalogger 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.
  5. 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.

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

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

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

  9. 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 datalogger as it is moved.

  10. It is certainly possible for two instances of LoggerNet to communicate with the datalogger. Depending on the link type and capability of the datalogger, they may be able to do so simultaneously. However, it is important to ensure that each of the PakBusPort devices in each LoggerNet instance has a unique PakBus address.

Case Studies

Delaware: Urgent Action on Bridge
The Delaware Department of Transportation (DelDOT) notified Intelligent Infrastructure Systems (IIS) and Pennoni of the......read more
New Mexico: SCADA System
In April of 2015, Sandia National Laboratories (SNL) contracted with Montrose Air Quality Services (MAQS)......read more
India: Rice-Field Greenhouse Gases
The cultivation of rice—the staple food for India, as well as for approximately half the......read more
Moldova: Disaster Risk Mitigation
Due to its geographical position close to the Black Sea, the local climate in Moldova......read more
Weather monitoring at Polish airfield
A Campbell Scientific weather station has recently been installed at the Olsztyn-Dajtki airport in Poland,......read more
Weather monitoring at Polish airfield
A Campbell Scientific weather station has recently been installed at the Olsztyn-Dajtki airport in Poland,......read more
New Hampshire: Collecting Data from Experimental Forest
The Hubbard Brook Experimental Forest (HBEF), located in the White Mountain National Forest of central......read more

Listed Under

Other Accessory for the following products:
Common Accessory for the following products: