Robust, Versatile
Contains advanced programming and communication capabilities
Related Documents WEATHER Related Documents WATER Related Documents ENERGY Related Documents MACHINES Related Documents STRUCTURES Related Documents EARTH

Overview

Current Version: 4.4
LoggerNet is our main datalogger support software package. It supports programming, communication, and data retrieval between dataloggers and a PC.

LoggerNet consists of a server application and several client applications integrated into a single product. It can support connection to a single datalogger, but it is especially adept in applications that require telecommunications or scheduled data retrieval used in large datalogger networks.

Download the Trial

Version 4 is our most recent major upgrade to LoggerNet that features a new tool for designing and configuring PakBus® networks, a more powerful file viewer, an upgrade to RTMC, a redesigned toolbar, and many updates to existing clients. Learn more about the upgrade in the brochure and manual linked in the Related Documents section on this page.

Version 4.4 adds support for the CR6-series dataloggers.

A copy of the current software license agreement (end-user license agreement) for LoggerNet is available in the LoggerNet Instruction Manual.

Read More

Benefits and Features

  • Creates custom datalogger 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

Images

Robust, Versatile
Contains advanced programming and communication capabilities
Related Documents WEATHER Related Documents WATER Related Documents ENERGY Related Documents MACHINES Related Documents STRUCTURES Related Documents EARTH

Technical Description

The standard LoggerNet software package is recommended for those who have datalogger 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 dataloggers via a variety of communications hardware
  • Create custom datalogger programs using Short Cut, Edlog, or the CRBasic Editor
  • Connect to a datalogger 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
  • RWIS Administrator 
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.

Specifications

  • PC Operating System: Windows 8, 7 (32 and 64 bit), Vista, or XP
  • Current Version: 4.4
  • Military Certificate of Networthiness (CoN):  
    • LoggerNet 4.0 is certified as Cert #201004872.
    • LoggerNet 4.x is certified as an upgrade to 4.0 and has ASC CoN ID 12274.
    • Expires 1/13/2017.

Compatibility

Communications

LoggerNet runs on a PC, using serial ports, telephony drivers, and Ethernet hardware to communicate with dataloggers 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. The recommended minimum computer configuration for running LoggerNet is Windows XP. LoggerNet also runs on Windows Vista, Windows 7, and Windows 8. LoggerNet runs on both 32-bit and 64-bit versions of these operating systems.

Datalogger Considerations

Compatible Contemporary Dataloggers

CR200(X) Series CR800/CR850 CR1000 CR3000 CR6 CR9000X

Compatible Retired Dataloggers

CR500 CR510 CR10 CR10X 21X CR23X CR9000 CR5000 CR7X
* * ** *

Notes:
*For our CR510, CR10X, and CR23X dataloggers, LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems.
**The 21X requires three PROMs; two PROM 21X Microloggers are not compatible.

Downloads

LoggerNet Patch v.4.4.1 (251 MB) 21-07-2016

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

Known Windows XP Issue:

This software release includes Campbell Scientific USB drivers that will not install on Windows XP. To keep current with up and coming security requirements, the drivers have been signed with a SHA-256 encryption which is not supported by Windows XP. Windows XP users who have a need to install USB drivers for Campbell Scientific products can contact Campbell Scientific for an alternate solution.

View Revision History

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.


What's new in LoggerNet 4 Tutorial (pdf format) v.- (8.46 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.

Note: Adobe Reader 9 or later is needed to view this tutorial.


German Language Pack v.4.4 (741 KB) 17-08-2016

German language files for LoggerNet 4.4 and 4.4.1.

Note: Language support for the above listed versions only.


LoggerNet Trial v.4.4.1 (261 MB) 21-07-2016

This is a fully functional 30 day trial of the standard version of LoggerNet.

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.0 Framework.  If it is not already installed on your computer,  it can be obtained from the Microsoft Download Center.

Known Windows XP Issue:

This software release includes Campbell Scientific USB drivers that will not install on Windows XP. To keep current with up and coming security requirements, the drivers have been signed with a SHA-256 encryption which is not supported by Windows XP. Windows XP users who have a need to install USB drivers for Campbell Scientific products can contact Campbell Scientific for an alternate solution.


LoggerNet Patch (Large) v.3.4.1 (74.2 MB) 22-10-2007

This patch upgrades LoggerNet version 3.0 and newer to 3.4.1. A version of LoggerNet 3.x must be installed on the computer. If you are using a version of LoggerNet 2.x, you must purchase an upgrade.

Note: Starting with LoggerNet 3.2, the included RTMC data display client has moved from Version 1.x to 2.x. This will require you to also upgrade from RTMC Web Server 1.x or RTMC Run-time 1.x if you also use those products.

View Revision History

FAQs for

Number of FAQs related to LOGGERNET: 128

Expand AllCollapse All

  1. The port is set during the setup process in the modem and then in the Setup screen of LoggerNet. The port of 3001 is the default in the Raven templates supplied by Campbell Scientific.

  2. 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.

  3. A Raven cellular modem with a dynamic IP address can be addressed through the DDNS (Dynamic Domain Name System) offered as a free service by Sierra Wireless (AirLink). The service translates a dynamic IP address into a fully qualified domain name so that the modem can be contacted directly via the Internet as if it had a static IP.  Campbell Scientific recommends that customers set up their Raven modems with a modem name that is the cellular phone number and that they use a domain of eairlink.com.

  4. There are two station names associated with a datalogger. One name is the Station Name used in the LoggerNet network map. The other name is the Station Name field in the datalogger 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 datalogger Status table station name instead.

  5. In the LoggerNet Setup screen, on the Data Files tab, select the browse button beside the Output Format field. This will open a dialog box that enables turning off Record Number. The option to not produce the record number was introduced in LoggerNet 4.0.

    In typical use, the datalogger itself does not store the record number or timestamp with each individual record in its own memory. Those values are generated by calculation when the data is retrieved.

  6. 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. LoggerNet can be configured to have two paths to a datalogger, simply by entering the datalogger twice in the network map with different comms links. LoggerNet, however, treats them as separate entities, so it will try to collect all the data twice via the two separate paths if both are enabled. Some users have set this up where they use one route most often, and manually enable collection to the backup route if the main link is lost.

    An alternative to this scheme is to set up the backup route but not add the datalogger. Then, if the main link to the datalogger goes down, simply drag-and-drop the datalogger to the backup route. After the main link is working again, the datalogger can be moved again. This keeps data collection pointers for that datalogger intact.

  8. The station’s datalogger clock can be set from the Connect screen. It can also be set from the Clock tab in the Setup screen.

  9. 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.

  10. 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.

Case Studies

Chicago Botanic Gardens Green Roof
The 385-acre Chicago Botanic Garden welcomes more than 750,000 visitors each year. Its new Daniel F. and Ada L. Rice......read more
New Hampshire: Collecting Data from Experimental Forest
The Hubbard Brook Experimental Forest (HBEF), located in the White Mountain National Forest of central New Hampshire, was established in......read more
Pennsylvania: Monitoring Landfills
Landfills present many environmental challenges, ranging from odor control to groundwater quality. Continuous, accurate monitoring of site conditions provides data......read more
South Africa: Solar Prospecting
Historically, the South African energy sector had been monopolized by a single state-owned utility company (Eskom) whose generating capacity consisted......read more
Oklahoma Mesonet: Meteorological Network
The Oklahoma Mesonetwork is a statewide environmental monitoring network developed through the cooperative efforts of Oklahoma State University and the......read more
Utah: Water-Supply SCADA System
In 2010, Trenton and Amalga, two northern Utah towns separated by only a few miles, created a plan to design......read more
Port of Tyne: Weather Monitoring
In order to gain access to more reliable weather information, the Port of Tyne added two new weather stations to......read more
Korea: Damage from Freezing Roads
Korea Expressway Corporation (KEC) was established in 1969 to construct and manage expressways throughout South Korea. KEC’s goal has been......read more

Listed Under

Other Accessories for the following products: