Contains advanced programming and communication capabilities
Overview
Current Version: 4.7
LoggerNet is our main data logger support software package. It supports programming, communication, and data retrieval between data loggers 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 data logger, but it is especially adept in applications that require telecommunications or scheduled data retrieval used in large data logger networks.
A copy of the current software license agreement (end-user license agreement) for LoggerNet is available in the LoggerNet Instruction Manual.
Read MoreBenefits and Features
- 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
Images
Similar Products
Detailed Description
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
|
Specifications
| Current Version | 4.7 |
| Operating System | Windows 11, 10, 8, or 7 (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 |
|
Compatibility
Note: The following shows notable compatibility information. It is not a comprehensive list of all compatible or incompatible products.
Data Loggers
| Product | Compatible | Note |
|---|---|---|
| 21X (retired) | The 21X requires three PROMs; two PROM 21X Microloggers are not compatible. | |
| CR10 (retired) | ||
| CR1000 (retired) | ||
| CR1000X | ||
| CR10X (retired) | LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems. | |
| CR200X (retired) | ||
| CR206X (retired) | ||
| CR211X (retired) | ||
| CR216X (retired) | ||
| CR23X (retired) | LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems. | |
| CR295X (retired) | ||
| CR300 | ||
| CR3000 (retired) | ||
| CR310 | ||
| CR350 | ||
| CR500 (retired) | ||
| CR5000 (retired) | ||
| CR510 (retired) | LoggerNet is compatible with the mixed array, PakBus®, and TD operating systems. | |
| CR6 | ||
| CR800 | ||
| CR850 | ||
| CR9000 (retired) | ||
| CR9000X (retired) |
Communication Devices
| Product | Compatible | Note |
|---|---|---|
| KonectPBRouter |
Software
| Product | Compatible | Note |
|---|---|---|
| KonectGDS |
Distributed Data Acquisition
| Product | Compatible | Note |
|---|---|---|
| GRANITE 10 | ||
| GRANITE 6 | ||
| GRANITE 9 |
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. The recommended minimum computer configuration for running LoggerNet is Windows 7. LoggerNet also runs on Windows 8, 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.
Documents
Miscellaneous
Videos & Tutorials
Downloads
LoggerNet Patch v.4.7 (343 MB) 03-16-2021
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 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, 10, 8.1, 8 or 7.
What's new in LoggerNet 4 Tutorial (exe format) v.- (12.9 MB) 09-14-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.7 (351 MB) 03-16-2021
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.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, 10, 8.1, 8 or 7.
Frequently Asked Questions
Number of FAQs related to LoggerNet: 132
Expand AllCollapse All
-
Follow these steps:
- Connect to the data logger using the LoggerNet Connect screen.
- Find the data logger in the Stations list, and right-click it.
- From the menu that is displayed, choose the Settings Editor.
-
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.
-
On table-based data loggers, in the LoggerNet Setup screen, on the Data Files tab, there is the Collect at Most option that can be used to indicate how many records to collect. Based on how often data is stored, a calculation can be made to determine how many records represent x hours of data.
-
Follow these steps:
- In the Setup screen, record the pertinent data from the Schedule and Data Files tabs.
- Delete the listed data logger.
- Add the new data logger.
- 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.
-
LoggerNet does not run as a service. Therefore, it needs to be running to do its data collection. LoggerNet Admin does have the capacity to run as a service, and it can collect data when no one is logged in to the computer.
-
LoggerNet does not do a clock check unless there is another reason to contact the data logger, such as for scheduled collection.
-
The LoggerNet server imposes no specific limits on the lengths of the generic modem scripts.
-
Yes. Follow these steps:
- In the LoggerNet Setup screen, click the icon for the data logger.
- Choose the Data Files tab.
- Deselect the Use Default File Name checkbox.
- In the menu for the File Output Option field, choose Create Unique File Name.
-
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.
-
Typically, blue screens are the result of bad device drivers. The Internet can be very helpful in tracking down the cause of blue screens. Copy down the codes displayed. Search the Internet for “blue screen” and the code to see what device is causing the crash. Often, an updated device driver will resolve the issue.
Case Studies
The Delaware Department of Transportation (DelDOT) notified Intelligent Infrastructure Systems (IIS) and Pennoni of the......read more
Intelligent Infrastructure Systems, a Pennoni company, was contracted to design and install an efficient structural-health......read more
In April of 2015, Sandia National Laboratories (SNL) contracted with Montrose Air Quality Services (MAQS)......read more
The cultivation of rice—the staple food for India, as well as for approximately half the......read more
Due to its geographical position close to the Black Sea, the local climate in Moldova......read more
System integrator Hortus Srl installed a Campbell Scientific CS725 SWE (snow water equivalent) sensor in......read more
The Hubbard Brook Experimental Forest (HBEF), located in the White Mountain National Forest of central......read more
Pont del Petroli was built in the 1960s to enable the transfer of oil from......read more
Articles and Press Releases
Blog Articles
-
Successfully Connect Your Retired Data Logger to a PC
12-19-2018 Author: Jacob Davis -
Changes to Microsoft Windows Operating System Support in Campbell Scientific Software
07-19-2017 Author: Dana Worley -
How to Use Call-back Capability so Your Data Logger Initiates Data Retrieval
02-22-2017 Author: Jacob Davis -
How to Replace “Undefined” or “N/A” with Your Real-Time Data Values
11-30-2016 Author: Janet Albers -
Handling New Device Drivers in a Changing Windows World
04-27-2016 Author: Dana Worley -
Using Internet Data to Promote Outdoor Safety
11-04-2015 Author: Barbra Utley -
How Safe Is Your LoggerNet Data?
05-29-2015 Author: Dana Worley
Newsletter Articles
- Case Study: Webcams in New Hampshire Forest 10-15-2015
- Case Study: South Africa Solar Prospecting 04-14-2015
- Case Study: Solar-Energy Assessment in Chile 10-20-2014
- Case Study: Florida Endangered Species 07-30-2014
- Case Study: South Dakota Irrigation Update 07-30-2014
- Case Study: Flood Warning in Arkansas 10-15-2013
- Case Study: Preventing Road Damage from Freezing Conditions in South Korea 05-09-2013
- New LoggerNet Release Coming Soon! 05-09-2013
- Case Study: North Carolina “Green” Hotel 10-18-2012
- Case Study: Water-Supply SCADA System 03-15-2012
- Introducing LoggerNet 4 10-16-2009
Listed Under
Privacy Policy Update
We've updated our privacy policy. Learn More