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 data logger network.Read More
|Operating System||Windows 10, 8, or 7 (Both 32- and 64-bit operating systems are supported.)|
Please note: The following shows notable compatibility information. It is not a comprehensive list of all compatible products.
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.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 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:
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.
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.
Deselect Run as Service from Start Menu | Programs | Campbell Scientific | LoggerNet | LoggerNet Service Manager.
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.
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 data logger), as well as the initialization files. Files such as data files, program files, etc., can also be added.
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.
No. LoggerNet Admin is installed on a single computer. To run clients or remote portions on another PC, it is necessary to purchase an additional LoggerNet Admin or LoggerNet Remote license.
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.