Datenlogger-Software / LoggerNet
LoggerNet Datenlogger Support-Software
Für Logger-Netzwerke
erweiterte Kommunikations- und Programmiermöglichkeiten
wetter wasser energie gas flux and turbulence bauwerke boden

Überblick

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.

Download Demo-Version

Die aktuellen Lizenzbedingungen (end-user license agreement) für LoggerNet finden Sie im LoggerNet Handbuch.

Lesen Sie mehr

Funktionen und Vorteile

  • Creates custom data logger programs using Edlog or CRBasic
  • Displays or graphs real-time or historic data
  • Builds custom display screens to view data or control flags/ports
  • Retrieves data using any of our telecommunication options
  • Processes data files using Split
  • Saves data in formats (including CSV and XML) that can be imported into third-party analysis packages

Bilder

Technische Beschreibung

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:

  • Configure the server to communicate with multiple data loggers via a variety of communications hardware
  • Create custom data logger programs using Short Cut, Edlog, or the CRBasic Editor
  • Connect to a data logger to check or set the clock, send programs, or perform other administrative functions
  • Collect data on demand or schedule
  • Monitor and troubleshoot the network
  • Display real-time data in a numeric display or graph
  • View and graph data files
  • Create graphical data displays that update when data is collected and allow you to control flags, ports, and variables
  • Create automated tasks
  • Process data files using Split
  • Save data in formats (including CSV and XML) that can be imported into third-party analysis packages.

The client applications included in the standard LoggerNet software package are the following:

  • Setup
  • Connect
  • Status Monitor
  • Task Master
  • Short Cut
  • CRBasic Editor
  • Edlog
  • Transformer
  • RTMC Development
  • RTMC Run-Time
  • View Pro
  • Split
  • CardConvert
  • Troubleshooter
  • Network Planner
  • PakBus Graph
  • LogTool
  • Device Configuration Utility
  • CoraScript
Version History
  • LoggerNet 4.x series replaced LoggerNet 3.x series on August 28, 2009.
  • LoggerNet 3.x series replaced LoggerNet 2.x series on 24 November, 2004.
  • LoggerNet 2.x series replaced PC208W on January 1, 2003.

Spezifikationen

Current Version 4.7
Operating System Windows 11 or 10 (Both 32- and 64-bit operating systems are supported.)
Requirement .NET 4.6.2
Purchased Separately Yes
Software Level Intermediate to advanced
Communications Supported 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 Yes
Data Display Supported Numeric, graphical, Boolean data objects

Military Certificate of Networthiness (CoN)
Certifications
  • LoggerNet 4.x is certified as Cert #201416752.
  • LoggerNet 4.x is certified as an upgrade to 4.0 and has ASC CoN ID 12274.

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
CR3000
CR310
CR350
CR5000 (retired)
CR6
CR800 (retired)
CR850 (retired)
CR9000X (retired)

Kommunikation

Product Compatible Note
KonectPBRouter

Miscellaneous

Product Compatible Note
GRANITE 10
GRANITE 6
GRANITE 9
KonectGDS

Additional Compatibility Information

Communications

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.

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 4. An upgrade for RTMC Pro must be purchased separately.

Computer

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.

Other Products

LoggerNet supports most commercially available sensors, SDM devices, multiplexers, relays, vibrating-wire interfaces, ET107, CompactFlash cards, microSD cards, and PC cards.

Downloads

LoggerNet Patch v.4.8.1 (399 MB) 16-04-2024

This patch will upgrade LoggerNet, LoggerNet Remote or LoggerNet Admin version 4.0 and newer to 4.8.1. 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 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.

Liste der Änderungen

What's new in LoggerNet 4 Tutorial (exe format) v.- (12.9 MB) 14-09-2009

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.

LoggerNet Trial v.4.8.1 (387 MB) 16-04-2024

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.

FAQs für

Number of FAQs related to LoggerNet: 132

Alle anzeigenWenige anzeigen

  1. How do you pull data from LoggerNet into a database, another application, or a website?

    There are several approaches you can try:

    1. 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.
    2. 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.
    3. 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.
    4. 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. 
  2. How can data from LoggerNet be added into the SCADA software OSIsoft PI?

    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.

  3. Where are skipped records for the datalogger reported?

    Using the LoggerNet Connect screen, check the datalogger Status table.

  4. Why might the numeric and graph displays (accessed from the LoggerNet Connect screen) no longer update?

    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.

  5. What would cause a message from LoggerNet that the settings are locked by a user?

    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.

  6. Can two instances of LoggerNet communicate at the same time with one datalogger?

    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.

  7. Is there a document that fully explains the various commands used in data logger programs, such as parameters, parameter ranges, and default values?

    No, but the Help in the Edlog and CRBasic editors is complete with all of this information. The CRBasic Editor Help also includes extensive examples.

  8. Does LoggerNet anywhere indicate the battery level of the connected datalogger?

    For PakBus dataloggers, the battery voltage is found on the Station Status screen. (The Station Status screen is accessed from the LoggerNet Connect screen.) For mixed-array dataloggers, Station Status will display the lithium battery and the number of times the 12 V supply has dropped below an acceptable level. If the battery voltage is being read by the program, it may be available from the public table.

  9. How can a datalogger be switched out (for example, from a CR800 to a CR1000) in LoggerNet?

    Follow these steps:

    1. In the Setup screen, record the pertinent data from the Schedule and Data Files tabs. 
    2. Delete the listed datalogger.
    3. Add the new datalogger. 
    4. Adjust the settings on the Schedule and Data Files tabs to match what was being done previously.
      • If the settings are complicated, review the Help menu from the Setup screen to learn more about the option in LoggerNet 4.2 to Copy Device Settings in the Tools menu.
  10. Can a datalogger be configured to place a call to a PC running LoggerNet?

    Yes. If the datalogger has a phone modem connected, there are Edlog and CRBasic commands that can be used to initiate calls. For example, in CRBasic a call can be made with SerialOpen(), SendVariables(), and SerialClose() instructions.

Gehen Sie zumVerzeichnis der FAQs

Anwendungsbeispiele

moldova: disaster risk mitigation
Moldova: Disaster Risk Mitigation
Due to its geographical position close to the Black Sea, the local climate in Moldova......lesen Sie mehr
italy: cs725 swe sensor field test
Italy: CS725 SWE Sensor Field Test
System integrator Hortus Srl installed a Campbell Scientific CS725 SWE sensor (Snow Water Equivalent) in......lesen Sie mehr
new hampshire: webcams in forest
New Hampshire: Webcams in Forest
The Hubbard Brook Experimental Forest (HBEF), located in the White Mountain National Forest of central......lesen Sie mehr
Spain: Oil Pier Met-Ocean Monitoring Station
Pont del Petroli was built in the 1960s to enable the transfer of oil from......lesen Sie mehr
south africa: solar prospecting
South Africa: Solar Prospecting
Historically, the South African energy sector had been monopolized by a single state-owned utility company......lesen Sie mehr
utah: data management for a rural irrigation system
Utah: Data Management for a Rural Irrigation System
Horseshoe Irrigation is a small rural irrigation company in central Utah, managing approximately 15,000 water shares......lesen Sie mehr
chile: solar-energy assessment
Chile: Solar-Energy Assessment
Solar energy resource assessment projects are critical to the successful siting of solar thermal power......lesen Sie mehr
utah: lightning warning at schools
Utah: Lightning Warning at Schools
Lightning strikes are a serious concern for school officials who are responsible for protecting the......lesen Sie mehr
Alle Projektberichte ansehen