Current Version: 4.7
LoggerNet Admin builds on the foundations of LoggerNet, providing additional clients, capabilities, and tools that are useful when managing a large data logger network.Read More
LoggerNet Admin, a more advanced software package than the standard LoggerNet, has tools that are useful for those with large data logger networks. It provides all the functionality of LoggerNet including the ability to program the data logger, collect data, monitor and troubleshoot the network, manage the data loggers in your network, create graphical data displays that update when data is collected, create automated tasks, and view or post-process the data. (See LoggerNet.)
LoggerNet Admin also provides the ability to enable security, manage the server from a remote PC, run LoggerNet as a Windows service, export data to third-party applications, and launch multiple instances of the same client (for instance, opening two Connect windows to communicate simultaneously with two different data loggers in the same or a different network). In addition, you can use LoggerNet Admin to set up subnets of the network map.
|Operating System||Windows 10, 8, or 7 (Both 32- and 64-bit operating systems are supported.)|
|Server||Windows Server versions 2012 R2, 2016, and 2019|
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)||For our CR10X datalogger, LoggerNet Admin is compatible with the mixed array, PakBus, and TD operating systems.|
|CR23X (retired)||For our CR23X data logger, LoggerNet Admin is compatible with the mixed array, PakBus, and TD operating systems.|
|CR510 (retired)||For our CR510 datalogger, LoggerNet Admin is compatible with the mixed array, PakBus, and TD operating systems.|
LoggerNet Admin 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 Admin 4. An upgrade for RTMC Pro must be purchased separately.
LoggerNet Admin 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 Admin is Windows 7. LoggerNet Admin also runs on Windows 8 and Windows 10. LoggerNet Admin 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.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 10, 8.1, 8 or 7.
Number of FAQs related to LoggerNet Admin: 22
Expand AllCollapse All
LoggerNet doesn’t know which tables are available in mixed-array data loggers unless the program is identified by associating it. If no tables show up in the Data Filer table selection window, check that there is a program associated with the data logger in LoggerNet. This can be done on the Program tab of the LoggerNet Setup screen. Also, verify these two things:
When LoggerNet Admin is set up, the user is asked to enter a user name. The user can enter something that is recognizable by a corporate network.
Yes. The patch should update the install to version 4.1 Admin, as long as the previous installation was installed as Admin with the correct license key.
All data and settings should remain following the upgrade from LoggerNet to LoggerNet Admin. The file formats and locations are exactly the same between the two products. No information in the configuration should be lost or reset.
The LoggerNet revision history information can be found through the “Software and OS Revision Histories” web page. Revision history information is available for LoggerNet patches and upgrades, as well as for the trial versions of the software.
The server/client architecture of LoggerNet allows for multiple clients to access the LoggerNet server.
Yes. LoggerNet Admin allows for opening multiple instances of the Connect screen and connecting to multiple data loggers, as long as there is no conflict between the communications devices.
LoggerNet Admin contains all of the capabilities of LoggerNet Remote. Additional copies of LoggerNet Remote are purchased separately. Because using different versions of LoggerNet and LoggerNet Remote can result in issues, Campbell Scientific recommends purchasing the LoggerNet Admin Upgrade.
Yes. To install LoggerNet on a centralized server and run it as a service, LoggerNet Admin needs to be installed on the server. Assuming there are open communications paths, LoggerNet Admin can be set up to control/access two or more data logger networks. However, if users would like to control two networks on separate PCs, a copy of LoggerNet Remote is needed for each PC accessing LoggerNet Admin on the servers.
To upgrade from LoggerNet to LoggerNet Admin, the correct upgrade path is to order the LoggerNet Admin Upgrade (LOGGERNETADM/U), which allows one copy of LoggerNet or LoggerNet Admin to be upgraded to the current version of LoggerNet Admin.