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

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


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

Operating System Windows 11 or 10 (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.

Data Loggers

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)
CR23X (retired) LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems.
CR295X (retired)
CR300
CR3000 (retired)
CR310
CR350
CR500 (retired)
CR5000 (retired)
CR510 (retired) LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems.
CR6
CR800 (retired)
CR850 (retired)
CR9000 (retired)
CR9000X (retired)

Distributed Data Acquisition

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. LoggerNet runs on 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.8.1 (399 MB) 16-04-2024

Known Issue: For those using the Task Master to schedule tasks, there is an issue affecting proper execution. It is recommended that you wait to update until this has been resolved in the next release of LoggerNet.

This patch will upgrade LoggerNet, LoggerNet Remote or LoggerNet Admin version 4.0 and newer to 4.8.1. 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.1. If you are using RTMC Pro 4.3.3 or older or CSI Web Server 1.6 or older and plan to continue creating RTMC projects, we recommend that you opt out on updating RTMC during the install or 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 or 10.

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 Trial v.4.8.1 (387 MB) 16-04-2024

This is a fully functional 30 day trial of the standard version of LoggerNet. This is a trial only and can not be activated as a full version with a license key. (Network setup and data is preserved from the trial when installing the full version.)

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

Listed Under

Other Accessory for the following products:

FAQs for

Number of FAQs related to LoggerNet: 130

Expand AllCollapse All

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

  2. The Retrieve button, used to retrieve a program from a data logger, is found on the LoggerNet Connect screen. Note that some data loggers, such as the CR200X-series, do not store the program in a retrievable format, and the Retrieve button will be disabled.

    There is also a File Retrieval tab in LoggerNet on the Setup screen that can be used to retrieve files stored on the data logger.

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

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

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

  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. Using the LoggerNet Connect screen, check the data logger Status table.

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