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
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
Please note: The following shows notable compatibility information. It is not a comprehensive list of all compatible products.
Data Loggers
| 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) | ||
| 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) |
Distributed Data Acquisition
| 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.
Related Documents
Product Brochures
Videos & Tutorials
Downloads
LoggerNet Patch v.4.7 (343 MB) 16-03-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 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, 10, 8.1, 8 or 7.
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.
LoggerNet Trial v.4.7 (351 MB) 16-03-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.
Articles and Press Releases
Newsletter Articles
- Case Study: Webcams in New Hampshire Forest 15-10-2015
- Case Study: South Africa Solar Prospecting 14-04-2015
- Case Study: Solar-Energy Assessment in Chile 20-10-2014
- Case Study: Florida Endangered Species 30-07-2014
- Case Study: South Dakota Irrigation Update 30-07-2014
- Case Study: Flood Warning in Arkansas 15-10-2013
- New LoggerNet Release Coming Soon! 09-05-2013
- Case Study: Preventing Road Damage from Freezing Conditions in South Korea 09-05-2013
- Case Study: North Carolina “Green” Hotel 18-10-2012
- Case Study: Water-Supply SCADA System 15-03-2012
- Introducing LoggerNet 4 16-10-2009
Listed Under
FAQs for
Number of FAQs related to LoggerNet: 131
Expand AllCollapse All
-
The Retrieve button, used to retrieve a program from a data logger, is found on the LoggerNet Connect screen. Note that some data loggers, such as the CR200X-series, do not store the program in a retrievable format, and the Retrieve button will be disabled.
There is also a File Retrieval tab in LoggerNet on the Setup screen that can be used to retrieve files stored on the data logger.
-
Using the LoggerNet Connect screen, check the data logger Status table.
-
In the LoggerNet Setup screen, on the Data Files tab, there are these Collect Mode options:
- Data Logged Since Last Collection
- Most Recently Logged Records
- Collect At Most
-
LoggerNet collects data from the data logger first. If there is additional data on a CompactFlash card, LoggerNet collects that also. Nothing special needs to be set up in LoggerNet to have this occur.
-
It is certainly possible for two instances of LoggerNet to communicate with the data logger. Depending on the link type and capability of the data logger, 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 data logger 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 data logger. 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.
-
A program snippet, such as the one below, would work for this purpose. The Boolean variable can be toggled from the Ports & Flags screen in LoggerNet (accessed via the Connect screen), through the Numeric Display (also accessed via the Connect screen), or under program control.
public StoreDataFlag as boolean
DataTable (ConditionalTable,StoreDataFlag,100)
Sample (1,counter,Long)
EndTable
When storing data conditionally, be sure to allocate a specific number of records in the size parameter of the DataTable() instruction. For more information, see the Data Table Memory Allocation Tutorial.
-
LoggerNet can be configured to have two paths to a data logger, simply by entering the data logger 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 data logger. Then, if the main link to the data logger goes down, simply drag-and-drop the data logger to the backup route. After the main link is working again, the data logger can be moved again. This keeps data collection pointers for that data logger intact.
-
No. For the current licensing information, refer to the LoggerNet Instruction Manual.