Current Version: 4.5
LoggerNet Admin builds on the foundations of LoggerNet, providing additional clients, capabilities, and tools that are useful when managing a large datalogger network.Read More
LoggerNet Admin, a more advanced software package than the standard LoggerNet, has tools that are useful for those with large datalogger networks. It provides all the functionality of LoggerNet including the ability to program the datalogger, collect data, monitor and troubleshoot the network, manage the dataloggers 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 dataloggers in the same or a different network).
|Operating System||Windows 10, 8, or 7 (Both 32- and 64-bit operating systems are supported.)|
LoggerNet Admin runs on a PC, using serial ports, telephony drivers, and Ethernet hardware to communicate with dataloggers 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.
*For our CR510, CR10X, and CR23X dataloggers, LoggerNet Admin is compatible with the mixed array, PakBus®, and TD operating systems.
**The 21X requires three PROMs; two PROM 21X Microloggers are not compatible.
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.
Number of FAQs related to LOGGERNETADM: 22
Expand AllCollapse All
LoggerNet doesn’t know which tables are available in mixed-array dataloggers 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 datalogger in LoggerNet. This can be done on the Program tab of the LoggerNet Setup screen. Also, verify these two things:
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.
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.
Deselect Run as Service from Start Menu | Programs | Campbell Scientific | LoggerNet | LoggerNet Service Manager.
Select the Backup menu item from the LoggerNet Setup screen. The choice can be made to set up automatic network backups or to perform a manual backup. This procedure creates a BKP file that can be copied to the new computer and imported using Restore Network.
It may be helpful to include the data cache (the binary database of collected data, which is twice the size of the table in the datalogger), as well as the initialization files. Files such as data files, program files, etc., can also be added.
There is a free trial version of LoggerNet, but there is not one for LoggerNet Admin.
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.
Yes, unless a Windows task is set up to launch LoggerNet. This task method, however, is not supported by Campbell Scientific.
To connect to a remote computer, either LoggerNet Remote or another copy of LoggerNet Admin is needed. The standard LoggerNet software does not have the ability to log in to a server other than localhost.
Yes. LoggerNet Admin allows for opening multiple instances of the Connect screen and connecting to multiple dataloggers, as long as there is no conflict between the communications devices.