Current Version: 4.5
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.
Version 4.5 adds 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 MoreThe 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.5 |
Operating System | Windows 10, 8, or 7 (Both 32- and 64-bit operating systems are supported.) |
Military Certificate of Networthiness (CoN) |
|
-NOTE- | Expires 1/13/2020. |
Certifications | LoggerNet 4.x is certified as Cert #201416752. |
Note: The following shows notable compatibility information. It is not a comprehensive list of all compatible or incompatible products.
Product | Compatible | Note |
---|---|---|
21X (retired) | The 21X requires three PROMs; two PROM 21X Microloggers are not compatible. | |
CR10 (retired) | ||
CR1000 | ||
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 |
Product | Compatible | Note |
---|---|---|
KonectPBRouter |
Product | Compatible | Note |
---|---|---|
Konect GDS |
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. 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.
This patch will upgrade LoggerNet, LoggerNet Remote or LoggerNet Admin version 4.0 and newer to 4.5. 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.
Supported Operating Systems: (32 and 64 bit) Windows 10, 8.1, 8 or 7.
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 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.
Adds Chinese language support for version 4.5 of LoggerNet, PC400, PC200W and the Device Configuation Utility version 2.16.
Note: Language support for the above listed versions only.
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.
Supported Operating Systems: (32 and 64 bit) Windows 10, 8.1, 8 or 7.
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.
Number of FAQs related to LOGGERNET: 132
Expand AllCollapse All
A client lock is automatically created by the Setup screen when a user begins to make changes. This lock will remain until the changes have been committed or cancelled, or until the connection between the Setup screen and the LoggerNet server is severed.
There is a difference between the Toolbar initialization files used in earlier 3.x versions of the software and more recent versions.
To resolve this, close LoggerNet. Go to C:\Campbellsci\LoggerNet\sys\inifiles and delete the Toolbar.ini file. When LoggerNet is reopened, the Toolbar should display the default buttons.
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:
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.
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.
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.
View Pro is meant to be a file viewer, so there is no automatic update capability.
To view graphs in real time, there are graphs that can be launched from the numeric monitor. For fully customizable displays, RTMC can be used. RTMC uses the LoggerNet server for its data source, but RTMC Pro (purchased separately from LoggerNet 4) can also use a DAT file.
In the LoggerNet Setup screen, on the Data Files tab, there are these Collect Mode options:
No. For the current licensing information, refer to the LoggerNet Instruction Manual.
If only scheduled collection is running, LoggerNet will connect to the data logger, collect the data, and then disconnect automatically.
We've updated our privacy policy. Learn More