Aktuelle Version: 4.7
Mit LoggerNet hat man die Software, um Datenlogger von Campbell Scientific zu programmieren, um Loggernetzwerke aufzubauen und um automatisch Daten abzufragen.
LoggerNet besteht aus einer Server Applikation und mehreren Clients integriert in einem Produkt. Vor allem zur Verwaltung von Loggernetzwerken und zur automatischen Datenfernabfrage ist Loggernet notwendig.
Die aktuellen Lizenzbedingungen (end-user license agreement) für LoggerNet finden Sie im LoggerNet Handbuch.Lesen Sie mehr
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:
|Windows 11 or 10 (Both 32- and 64-bit operating systems are supported.)
|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
|Data Display Supported
|Numeric, graphical, Boolean data objects
Military Certificate of Networthiness (CoN)
Please note: The following shows notable compatibility information. It is not a comprehensive list of all compatible products.
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. LoggerNet runs on 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 or CSI Web Server 1.6 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 or 10.
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. This is a trial only and can not be activated as a full version with a license key. (Network setup and data is preserved from the trial when installing the full version.)
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 or 10.
Number of FAQs related to LoggerNet: 131
Alle anzeigenWenige anzeigen
OSIsoft sells a PI interface for LoggerNet. The OSIsoft part number is PI-IN-CS-LN-NTI. Please direct all inquiries for sales and support of the interface to OSIsoft.
Using the LoggerNet Connect screen, check the datalogger Status table.
If communication is interrupted or intermittent, LoggerNet may stop updating the Table Monitor, Numeric Display, and Graphs. When this occurs, a button on the display that is normally titled Stop (to stop the update) changes to Start, and the button must be pressed to resume the update. Also, check the update interval on the display, as it may be set to a higher value than expected.
A client lock is automatically created by the Setup screen when a user begins to make changes. This lock will remain until the changes have been committed or cancelled, or until the connection between the Setup screen and the LoggerNet server is severed.
There are two station names associated with a data logger. One name is the Station Name used in the LoggerNet network map. The other name is the Station Name field in the data logger Status table. Almost all data file formats work in LoggerNet include a station name in the header of the data file. By default, the network map station name is used. However, a checkbox in the LoggerNet Setup window, Data Files tab, allows choosing the data logger Status table station name instead.
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.
Campbell Scientific does not replace lost or damaged disks. Customers are urged to create a backup copy of the CD and record the product key for safe keeping.
It is certainly possible for two instances of LoggerNet to communicate with the datalogger. Depending on the link type and capability of the datalogger, they may be able to do so simultaneously. However, it is important to ensure that each of the PakBusPort devices in each LoggerNet instance has a unique PakBus address.
All devices in a PakBus network, including computers, must have unique PakBus addresses. (The datalogger becomes confused when several devices connect to it with the same PakBus address.) Make sure all the copies of LoggerNet on different PCs have different PakBus addresses for the PakBus ports used to connect to the same datalogger. Configure the address to something other than the default of 4094 from the Setup window: Tools | LoggerNet Server Settings | PakBus Settings. If this is not done, the connections will be intermittent, as each new connection will cause any existing connection to be lost.
LoggerNet and VisualWeather are the only datalogger support software packages, offered by Campbell Scientific, that perform scheduled data collection.