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.
A copy of the current software license agreement (end-user license agreement) for LoggerNet is available in the LoggerNet Instruction Manual.Read More
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:
|Operating System||Windows 11, 10, 8, or 7 (Both 32- and 64-bit operating systems are supported.)|
|Software Level||Intermediate to advanced|
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)
Note: The following shows notable compatibility information. It is not a comprehensive list of all compatible or incompatible products.
|21X (retired)||The 21X requires three PROMs; two PROM 21X Microloggers are not compatible.|
|CR10X (retired)||LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems.|
|CR23X (retired)||LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems.|
|CR510 (retired)||LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems.|
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, 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.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.
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.
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.
Number of FAQs related to LoggerNet: 132
Expand AllCollapse All
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.
In the LoggerNet Setup screen, use the Schedule tab.
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.
Yes. If the data logger has a phone modem connected, there are Edlog and CRBasic commands that can be used to initiate calls. For example, in CRBasic a call can be made with SerialOpen(), SendVariables(), and SerialClose() instructions.
Typically, a backup from an older version of LoggerNet will work on a newer version, but there will be issues trying to go from a newer version back to an older version.
If only scheduled collection is running, LoggerNet will connect to the data logger, collect the data, and then disconnect automatically.
LoggerNet does not do a clock check unless there is another reason to contact the data logger, such as for scheduled collection.
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
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.
Follow these steps:
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: