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.
A copy of the current software license agreement (end-user license agreement) for LoggerNet is available in the LoggerNet Instruction Manual.
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:
The client applications included in the standard LoggerNet software package are the following:
Version History
|
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 |
|
Please note: The following shows notable compatibility information. It is not a comprehensive list of all compatible products.
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) | ||
CR211X (retired) | ||
CR216X (retired) | ||
CR23X (retired) | LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems. | |
CR300 (retired) | ||
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) | ||
CR800 (retired) | ||
CR850 (retired) | ||
CR9000 (retired) | ||
CR9000X (retired) |
Product | Compatible | Note |
---|---|---|
KonectPBRouter |
Product | Compatible | Note |
---|---|---|
GRANITE 10 | ||
GRANITE6 | ||
GRANITE 9 |
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.
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.
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.
LoggerNet supports most commercially available sensors, SDM devices, multiplexers, relays, vibrating-wire interfaces, ET107, CompactFlash cards, microSD cards, and PC cards.
This patch will upgrade LoggerNet, LoggerNet Remote or LoggerNet Admin version 4.0 and newer to 4.9. 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 v5.0.1.
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.
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.
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.
Number of FAQs related to LoggerNet: 127
Expand AllCollapse All
There are several approaches you can try:
Network Planner is new to LoggerNet 4.0. It was specifically designed to help set up data loggers 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.
Using the LoggerNet Connect screen, check the data logger Status table.
LoggerNet can be set to use GMT, regardless of the PC system clock, by using the LoggerNet Setup screen: Tools | LoggerNet Server Settings | LoggerNet Settings.
An offset to the PC clock can be set for the data logger. Follow these steps:
For the CR1000 datalogger, the Status table, accessed from the CR1000KD or LoggerNet (version 4) Connect screen, Station Status button, has some statistics that may be useful. Refer to “ProcessTime,” “MaxProcTime,” “MeasureTime,” and “MeasureOps” in Appendix B of the CR1000 Operator’s Manual.
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.
LoggerNet does not do a clock check unless there is another reason to contact the data logger, such as for scheduled collection.
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.
Yes, but only if the communications links to the data loggers allow simultaneous communication. For example, two mixed-array data loggers can be contacted simultaneously using two different COM ports; however, if they are accessed via the same COM port, LoggerNet can connect to only one at a time.
First, make sure the most recent version of LoggerNet is being used. (Improvements were made between versions 4.0 and 4.1 that resolved some issues with LoggerNet and some USB-to-serial cable drivers.) Next, ensure that the most recent drivers from the cable manufacturer are being used. Often, newer drivers are developed for devices after they are released, and the software shipped with those devices is not updated. The drivers can be downloaded from the manufacturer's website.
We've updated our privacy policy. Learn More