Überblick
Aktuelle Version: 4.7
LoggerNet Admin erweitert die Funktionen von LoggerNet und enthält zusätzliche Clients und Werkzeuge zur Verwaltung großer Logger-Netzwerke.
Lesen Sie mehrFunktionen und Vorteile
- Includes all LoggerNet functions
- Provides a client for enabling security
- LoggerNet Admin can be managed from a remote PC using LoggerNet Remote, or it can be used to manage another LoggerNet server
- Provides the ability to run LoggerNet Admin as a service
- Exports data to third-party applications
- Launches multiple instances of the same client
- Provides the ability to set up subnets of the network map
Bilder
Technische Beschreibung
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).
Spezifikationen
| Current Version | 4.7 |
| Operating System | Windows 11 or 10 (Both 32- and 64-bit operating systems are supported.) |
| Server | Windows Server versions 2012 R2, 2016, 2019, and 2022 |
| Requirement | .NET 4.6.2 |
Kompatibel mit
Please note: The following shows notable compatibility information. It is not a comprehensive list of all compatible products.
Datenlogger
| Product | Compatible | Note |
|---|---|---|
| CR1000 (retired) | ||
| CR1000X | ||
| CR200X (retired) | ||
| CR216X (retired) | ||
| CR300 (retired) | ||
| CR3000 | ||
| CR310 | ||
| CR350 | ||
| CR5000 (retired) | ||
| CR6 | ||
| CR800 (retired) | ||
| CR850 (retired) | ||
| CR9000X (retired) |
Additional Compatibility Information
Communications
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.
Software
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.
Computer
LoggerNet Admin is a collection of 32-bit programs designed to run on Intel-based computers running Microsoft Windows operating systems. LoggerNet Admin runs on Windows 10 and Windows 11. LoggerNet Admin runs on both 32-bit and 64-bit versions of these operating systems.
Dokumente
Broschüren Produkte
Handbücher
Realisierte Projekte
Downloads
LoggerNet Patch v.4.9 (419 MB) 02-10-2024
This patch will upgrade LoggerNet, LoggerNet Remote or LoggerNet Admin version 4.0 and newer to 4.9. 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.1. If you are using RTMC Pro 4.3.3 or older or CSI Web Server 1.6 or older and plan to continue creating RTMC projects, we recommend that you opt out on updating RTMC during the install or upgrade to RTMC Pro v5.0.1.
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 or 10.
FAQs für
Number of FAQs related to LoggerNet Admin: 23
Alle anzeigenWenige anzeigen
-
There are several approaches you can try:
- The LNDB Interface can pull data from LoggerNet and insert it into a database instance. Supported database platforms are as follows: Microsoft SQL; MySQL; unofficially, MariaDB as it is open source MySQL, PostGRESQL, and Oracle. The database table structure and metadata will match the structure of the station’s program and the station name used in LoggerNet exactly. You cannot customize the structure. Refer to the setup documentation.
- Read or parse data from LoggerNet .dat files. The files are CSV formatted and can be parsed in using most any programming language. Files by default are stored on the LoggerNet computer in the following path: C:\Campbellsci\LoggerNet.
- LDMP Server, a LoggerNet Admin component, offers a listening socket for data to be pulled directly from the LoggerNet cache over the LoggerNet Service listening port 6789. Complete documentation in LoggerNet Admin is stored in the following path: C:\Program Files (x86)\Campbellsci\LoggerNet\ldmp_server2.pdf.
- Read in data using the CSI web server’s built in Web API. The webAPI accepts queries in the same format as the data logger’s built-in webAPI. Refer to the data logger webAPI documentation.
-
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:
- Scheduled collection is enabled (on the Schedule tab of the LoggerNet Setup screen).
- FS Area 1 is enabled (and FS Area2 if memory is being specifically allocated to it) for collection. This information is found on the respective tabs in the LoggerNet Setup Screen.
-
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.
-
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.
-
There is a free trial version of LoggerNet, but there is not one for LoggerNet Admin.
-
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.
-
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 datalogger 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.
-
Yes, unless a Windows task is set up to launch LoggerNet. This task method, however, is not supported by Campbell Scientific.
Anwendungsbeispiele
Cofely Fabricom NV/SA (GDFSuez) has utilized Campbell Scientific equipment on numerous projects in both the......lesen Sie mehr
The goal of the Department of Resource Management is to ensure the sustainable use and......lesen Sie mehr