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

Overview

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.

Read More

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

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

Specifications

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

Compatibility

Communications

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.

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

Compatible Retired Dataloggers

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

Notes:
*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.

Downloads

LoggerNet Patch v.4.4 (239 MB) 11-03-2016

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

Known Windows XP Issue:

This software release includes Campbell Scientific USB drivers that will not install on Windows XP. To keep current with up and coming security requirements, the drivers have been signed with a SHA-256 encryption which is not supported by Windows XP. Windows XP users who have a need to install USB drivers for Campbell Scientific products can contact Campbell Scientific for an alternate solution.

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.4 (248 MB) 11-03-2016

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.

Known Windows XP Issue:

This software release includes Campbell Scientific USB drivers that will not install on Windows XP. To keep current with up and coming security requirements, the drivers have been signed with a SHA-256 encryption which is not supported by Windows XP. Windows XP users who have a need to install USB drivers for Campbell Scientific products can contact Campbell Scientific for an alternate solution.


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. In the LoggerNet Setup screen, use the Schedule tab.

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

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

  4. An RTMC Pro screen can be developed to monitor a value being returned from the datalogger and send an email alert if it exceeds certain parameters. Alternatively, a task could be set up in the Task Master to email an alert that is executed after a failed call or failed retries.

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

  6. 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.
  7. 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.
  8. LoggerNet can be configured to have two paths to a datalogger, simply by entering the datalogger twice in the network map with different comms links. LoggerNet, however, treats them as separate entities, so it will try to collect all the data twice via the two separate paths if both are enabled. Some users have set this up where they use one route most often, and manually enable collection to the backup route if the main link is lost.

    An alternative to this scheme is to set up the backup route but not add the datalogger. Then, if the main link to the datalogger goes down, simply drag-and-drop the datalogger to the backup route. After the main link is working again, the datalogger can be moved again. This keeps data collection pointers for that datalogger intact.

  9. Yes. Follow these steps:

    1. In the LoggerNet Setup screen, click the icon for the datalogger.
    2. Choose the Data Files tab.
    3. Deselect the Use Default File Name checkbox.
    4. In the menu for the File Output Option field, choose Create Unique File Name.

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. Rice......read 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 consisted......read more
Pennsylvania: Monitoring Landfills
Landfills present many environmental challenges, ranging from odor control to groundwater quality. Continuous, accurate monitoring of site conditions provides data......read 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 in......read 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 design......read more
Port of Tyne: Weather Monitoring
In order to gain access to more reliable weather information, the Port of Tyne added two new weather stations to......read more
Utah: Lightning Warning at Schools
Lightning strikes are a serious concern for school officials who are responsible for protecting the safety of everyone who uses......read 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 been......read more

Listed Under

Other Accessories for the following products: