LoggerNet Clients / LOGGERNETREM
LOGGERNETREM Remote Datalogger Support Software
Remote Management
Manage existing datalogger network from remote location
weather applications water applications energy applications gas flux & turbulence applications infrastructure applications soil applications

Overview

Current Version: 4.5

LoggerNet Remote lets you manage an existing LoggerNet datalogger network from a remote location without investing in another complete LoggerNet Admin software package.

Read More

Benefits and Features

  • Allows you to manage an existing datalogger network from a remote location
  • Includes all of the LoggerNet Admin clients except for the Service Manager

Images

Detailed Description

LoggerNet Remote lets you manage an existing LoggerNet datalogger network from a remote location without investing in another complete LoggerNet Admin software package.

LoggerNet Remote includes only the LoggerNet Admin clients that are used to connect with an existing LoggerNet server on a remote PC. It does not include the LoggerNet server.

Specifications

Current Version 4.5
Operating System Windows 10, 8, or 7 (Both 32- and 64-bit operating systems are supported.)

Compatibility

Computer

LoggerNet Remote 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 Remote is Windows 7. LoggerNet Remote also runs on Windows 8 and Windows 10. LoggerNet Remote 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 CR300
Series
CR1000X

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 Remote Trial v.4.5 (320 MB) 08-18-2017

This is a fully functional 30 day trial of the remote 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.

Supported Operating Systems: (32 and 64 bit) Windows 10, 8.1, 8 or 7.

LoggerNet Patch v.4.5 (310 MB) 08-18-2017

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

Supported Operating Systems: (32 and 64 bit) Windows 10, 8.1, 8 or 7.

View Update History

Frequently Asked Questions

Number of FAQs related to LOGGERNETREM: 16

Expand AllCollapse All

  1. Yes. The download for the trial version is available in the Downloads section of the LoggerNet Remote Product Information page.

  2. No. However, LoggerNet can be upgraded to LoggerNet Admin, which has the same features as LoggerNet Remote.

  3. LoggerNet doesn’t know which tables are available in mixed-array dataloggers unless the program is identified by associating it. If no tables show up in the Data Filer table selection window, check that there is a program associated with the datalogger in LoggerNet. This can be done on the Program tab of the LoggerNet Setup screen. Also, verify these two things:

    1. Scheduled collection is enabled (on the Schedule tab of the LoggerNet Setup screen).
    2. FS Area 1 is enabled (and FS Area2 if memory is being specifically allocated to it) for collection. This information is found on the respective tabs in the LoggerNet Setup Screen.
  4. Yes. This combination will result in a LoggerNet Admin installation with all of its features. However, Campbell Scientific does not recommend this process because installing different versions of LoggerNet and LoggerNet Remote can result in inconsistent software behavior.

  5. On the LoggerNet Setup screen, on the Data Files tab, select Create Unique File Name as a File Output Option. The Create Unique File Name option is not available for storage modules or mixed-array dataloggers. In these situations, use Split or a batch file to accomplish the same results.

  6. LoggerNet Remote (LOGGERNETREM) is a separate product available for purchase.

  7. Yes. To install LoggerNet on a centralized server and run it as a service, LoggerNet Admin needs to be installed on the server. Assuming there are open communications paths, LoggerNet Admin can be set up to control/access two or more datalogger networks. However, if users would like to control two networks on separate PCs, a copy of LoggerNet Remote is needed for each PC accessing LoggerNet Admin on the servers.

  8. LoggerNet Admin contains all of the capabilities of LoggerNet Remote. Additional copies of LoggerNet Remote are purchased separately. Because using different versions of LoggerNet and LoggerNet Remote can result in issues, Campbell Scientific recommends purchasing the LoggerNet Admin Upgrade.

  9. No. LoggerNet Admin is installed on a single computer. To run clients or remote portions on another PC, it is necessary to purchase an additional LoggerNet Admin or LoggerNet Remote license.

  10. LoggerNet Remote does not include the LoggerNet communication server. It was designed to connect to a LoggerNet communication server that is running elsewhere and can be accessed over TCP/IP. LoggerNet Remote cannot be used to connect directly to a datalogger because there is no communication server running. LoggerNet Remote does not have the files necessary to connect to a datalogger directly.

Case Studies

New Mexico: SCADA System
In April of 2015, Sandia National Laboratories (SNL) contracted with Montrose Air Quality Services (MAQS)......read more
Utah: Rural Irrigation
Horseshoe Irrigation is a small, rural irrigation company in central Utah, managing around 15,000 water......read more