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

Overview

Current Version: 4.6.2

LoggerNet is our main data logger support software package. It supports programming, communication, and data retrieval between data loggers 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 data logger, but it is especially adept in applications that require telecommunications or scheduled data retrieval used in large data logger networks.

Download the Trial

Version 4.6.1 added support for the CR1000X datalogger.

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

Detailed Description

The standard LoggerNet software package is recommended for those who have data logger 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 data loggers via a variety of communications hardware
  • Create custom data logger programs using Short Cut, Edlog, or the CRBasic Editor
  • Connect to a data logger 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

Current Version 4.6.2
Operating System Windows 10, 8, or 7 (Both 32- and 64-bit operating systems are supported.)
Requirement .NET 4.6.2
Purchased Separately Yes
Software Level Intermediate to advanced
Communications Supported Direct connect, Ethernet, short-haul, phone modems (land-line, cellular, voice synthesized), RF transceivers (UHF, VHF, and spread spectrum), multidrop modems

Combinations of communication devices supported.
Scheduled Data Collection Supported Yes
Data Display Supported Numeric, graphical, Boolean data objects

Military Certificate of Networthiness (CoN)

Certifications
  • LoggerNet 4.x is certified as Cert #201416752.
  • LoggerNet 4.x is certified as an upgrade to 4.0 and has ASC CoN ID 12274.

Compatibility

Note: The following shows notable compatibility information. It is not a comprehensive list of all compatible or incompatible products.

Data Loggers

Product Compatible Note
21X (retired) The 21X requires three PROMs; two PROM 21X Microloggers are not compatible.
CR10 (retired)
CR1000 (retired)
CR1000X
CR10X (retired) LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems.
CR200X (retired)
CR206X (retired)
CR211X (retired)
CR216X (retired)
CR23X (retired) LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems.
CR295X (retired)
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 (retired)

Communication Devices

Product Compatible Note
KonectPBRouter

Software

Product Compatible Note
KonectGDS

Distributed Data Acquisition

Product Compatible Note
GRANITE 10
GRANITE 6
GRANITE 9

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.

Other Products

LoggerNet supports most commercially available sensors, SDM devices, multiplexers, relays, vibrating-wire interfaces, ET107, CompactFlash cards, microSD cards, and PC cards.

Downloads

LoggerNet Patch v.4.6.2 (337 MB) 03-26-2020

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

LoggerNet Admin and Remote:

A change was made in the way the LoggerNet 4.6 Server performs "Custom Data Collection". A corresponding change was made in the Connect Screen 4.6 client "Custom Data Collection" functionality.

If you require "Custom Data Collection" functionality with the Connect Screen client, assure that the LoggerNet Servers and Connect Screen clients are 4.6 or higher.

Note: This application requires the Microsoft .Net 4.6.2 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 Update History

What's new in LoggerNet 4 Tutorial (exe format) v.- (12.9 MB) 09-14-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.


LoggerNet Trial v.4.6.2 (345 MB) 03-26-2020

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

Frequently Asked Questions

Number of FAQs related to LoggerNet: 133

Expand AllCollapse All

  1. OSIsoft sells a PI interface for LoggerNet. The OSIsoft part number is PI-IN-CS-LN-NTI. Please direct all inquiries for sales and support of the interface to OSIsoft.

  2. Before it appends to a TOA5, TOB1, or TOACI1 data file, LoggerNet first scans the header of that file and compares the information that it contains with the information reported in the data logger table definitions. For TOA5, the following conditions can result in errors that will cause LoggerNet to refuse to append to the file:

    • The table names do not match.
    • The number of columns does not match.
    • One or more column names do not match.
    • The number of units strings does not match the number of column names.
    • The number of process strings does not match the number of column names.

    There have been cases where, using the FieldNames() instruction, the data logger program specified a double quote character (") in the units string, and this character unbalanced the quote marks in the TOA5 format, which in turn threw off the TOA5 parser.

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

  4. For PakBus data loggers, the battery voltage is found on the Station Status screen. (The Station Status screen is accessed from the LoggerNet Connect screen.) For mixed-array data loggers, Station Status will display the lithium battery and the number of times the 12 V supply has dropped below an acceptable level. If the battery voltage is being read by the program, it may be available from the public table.

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

  6. LoggerNet collects data from the data logger first. If there is additional data on a CompactFlash card, LoggerNet collects that also. Nothing special needs to be set up in LoggerNet to have this occur.

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

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

  9. Follow these steps:

    1. Connect to the data logger using the LoggerNet Connect screen.
    2. Find the data logger in the Stations list, and right-click it.
    3. From the menu that is displayed, choose the Settings Editor.
  10. LoggerNet can be configured to have two paths to a data logger, simply by entering the data logger 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 data logger. Then, if the main link to the data logger goes down, simply drag-and-drop the data logger to the backup route. After the main link is working again, the data logger can be moved again. This keeps data collection pointers for that data logger intact.

Case Studies

Delaware: Urgent Action on Bridge
The Delaware Department of Transportation (DelDOT) notified Intelligent Infrastructure Systems (IIS) and Pennoni of the......read more
Delaware River: Bridge Health
Intelligent Infrastructure Systems, a Pennoni company, was contracted to design and install an efficient structural-health......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
Italy: CS725 SWE Sensor Field Test
System integrator Hortus Srl installed a Campbell Scientific CS725 SWE (snow water equivalent) sensor in......read more
New Hampshire: Webcams in Forest
The Hubbard Brook Experimental Forest (HBEF), located in the White Mountain National Forest of central......read more
Spain: Oil Pier Met-Ocean Monitoring Station
Pont del Petroli was built in the 1960s to enable the transfer of oil from......read more

Listed Under

Other Accessory for the following products:
Common Accessory for the following products:
This Product Replaced

Privacy Policy Update

We've updated our privacy policy.  Learn More