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

Overview

Current Version: 4.7

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

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 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
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.7
Operating System Windows 11, 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

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

Dataloggers

Product Compatible Note
CR1000 (retired)
CR1000 (retired)
CR1000 (retired)
CR1000X
CR200X (retired)
CR216X (retired)
CR300
CR3000
CR310
CR350
CR5000 (retired)
CR6
CR800
CR850
CR9000X (retired)

Communication Devices

Product Compatible Note
KonectPBRouter

Software

Product Compatible Note
KonectGDS

Miscellaneous

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, Windows 10, and Windows 11. 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.7 (343 MB) 16-03-2021

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

Note: This patch includes RTMC Run-time and the RTMC Standard Development v5.0. If you are using RTMC Pro 4.3.3 or older and plan to continue creating RTMC projects, we recommend that you upgrade to RTMC Pro 5.0.

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.

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


LoggerNet Trial v.4.7 (351 MB) 16-03-2021

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 11, 10, 8.1, 8 or 7.

FAQs for

Number of FAQs related to LoggerNet: 132

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. Typically, blue screens are the result of bad device drivers. The Internet can be very helpful in tracking down the cause of blue screens. Copy down the codes displayed. Search the Internet for “blue screen” and the code to see what device is causing the crash. Often, an updated device driver will resolve the issue.

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

  4. Using the LoggerNet Connect screen, check the data logger Status table.

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

  7. There are two station names associated with a data logger. One name is the Station Name used in the LoggerNet network map. The other name is the Station Name field in the data logger Status table. Almost all data file formats work in LoggerNet include a station name in the header of the data file. By default, the network map station name is used. However, a checkbox in the LoggerNet Setup window, Data Files tab, allows choosing the data logger Status table station name instead.

  8. In the LoggerNet Setup screen, use the Schedule tab.

  9. It is certainly possible for two instances of LoggerNet to communicate with the data logger. Depending on the link type and capability of the data logger, 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.

  10. 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 data logger as a different data logger 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).

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

This Product Replaced