What's New in LoggerNet?
LoggerNet 4.9
Added support for the CR1000Xe datalogger.
LoggerNet 4.8
One of the main efforts in the development of LoggerNet 4.8 has been to add the CR350 Series datalogger as a unique device. Previously, the CR350 was included as part of the CR300 Series. Any existing CR350 Series dataloggers that were created using the CR300Series option can continue to be used as is.
Automatic software update checks are now a global feature across all Campbell Scientific applications that support this function. This means automatic software update checks may be activated or deactivated upon initial software installation and then the setting will be set the same (on or off) for all other Campbell Scientific software applications that support automatic updates. Automatic update checks may be turned on or off at any time using the Software Updater File menu.
NOTE: Starting with this version of LoggerNet, RTMC will no longer be updated if a version of RTMC Pro earlier than 5.0 is installed on the computer. This is to maintain full compatibility with the installed RTMC Pro package.
LoggerNet 4.7
One of the main efforts in the development of LoggerNet 4.7 has been support for the new CR350 Series datalogger.
An Allowed Neighbors tab has also been added to the
In addition, a Neighbor PakBus Address field has been added to the
Also, a TCP Password field has been added to the
In LoggerNet Admin, you can now add, delete, and edit stations while viewing a subnet. Previously, you had to change your view to the whole network before making station changes.
A Software Updater has been added to LoggerNet and Device Configuration Utility that can automatically notify you and update your software when a new release is available.
Users of Campbell Scientific's LNDB database software who are using a PostgreSQL or Oracle database can now access the data directly from the database with View Pro. In addition, View Pro now allows you to set graphs to start maximized, set default settings for all new line graphs, and jump to the beginning or end of a line graph.
RTMC and RTMC Run-Time have been updated to version 5.0.
NOTE: If you are using an older version of RTMC Pro and plan to continue creating RTMC projects, we recommend that you upgrade to RTMC Pro 5.0.
LoggerNet 4.6
One of the main efforts in the development of LoggerNet 4.6 has been support for the new GRANITE Data Logger Modules.
In addition, a Datalogger Network Communications Enabled check box has been added to LoggerNet Settings to enable/disable communications for the entire network. This option has also been added to Restore Network.
NOTE: The way custom data collection is performed changed in this version. The changes should be invisible to the user. However, custom collection will not work with the 4.6 LoggerNet server and a Connect screen from an older version of LoggerNet. Therefore, we recommend that LoggerNet Admin and LoggerNet Remote users update their clients and servers to the latest version.
LoggerNet 4.5
One of the main efforts in the development of LoggerNet 4.5 has been support for the new CR1000X datalogger.
In addition, the Short Cut user interface has been redesigned in an effort to make it more intuitive to users.
NOTE: Beginning with this version of LoggerNet, Windows XP and Windows Vista are no longer supported.
LoggerNet 4.4
The main effort in the development of LoggerNet 4.4 has been support for the new CR300 Series datalogger. Support was also added for the CDM-A108 and CDM-A116.
In addition, a basic security username/password was added to control access to the network when Allow Remote Connections is enabled.
A UDP Search button was added to the IPPort in the Setup screen to initiate a UDP discovery to search for PakBus dataloggers in the network. Also in the Setup screen, the ComPort now has an Install USB Driver button to allow you to install the USB drivers for our dataloggers and peripherals that require them.
The ability to display line numbers has been added to the CRBasic Editor.
LoggerNet 4.3
The main effort in the development of LoggerNet 4.3 has been support for the new CR6 Series datalogger. Support was also added for the CRS451 Series Water Level Recording Sensor and the CRVW Series Vibrating Wire Recording Interface.
LoggerNet 4.2
LoggerNet now supports IPv6 addresses. IPv6 addresses are written as eight two-byte address blocks separated by colons and surrounded by brackets (e.g., [2620:24:8080:8600:85a1:fcf2:2172:11bf]). Prior to LoggerNet 4.2, only IPv4 addresses were supported. IPv4 addresses are written in dotted decimal notation (e.g., 192.168.11.197). Leading zeroes are stripped for both IPv4 and IPv6 addresses. Note that while LoggerNet now supports IPv6 addresses and they can be used to specify servers, CR1000/CR3000/CR800 series dataloggers will not support IPv6 until a future OS release. Check the OS Revision History on our website to determine when IPv6 support is added to the OS. (Starting in LoggerNet 4.2.1, IPv6 connections are disabled by default. They can be enabled from LoggerNet’s Tools | Options menu item.)
LoggerNet now supports display and input of
The ability to set up subnets of the network map has been added to LoggerNet Admin. The Setup Screen’s View | Configure Subnets menu item is used to configure the subnets. Within each subnet, you can also specify groups of dataloggers. The datalogger groups create folders than can be collapsed or expanded when viewing the subnet. Once subnets have been configured, you can choose to view a subnet rather that the entire network in the Setup Screen, Connect Screen, and Status Monitor.
You can now set up defaults for the Setup Screen’s Schedule, Data Files, Clock, and File Retrieval tabs that will be used when new stations are added to the network. There is also the ability to copy these defaults to existing stations.
The ability to use 24:00 (rather than the default of 00:00) for the timestamp at midnight has been added. (This is accessed from the 
button next to the Output Format field on the datalogger’s Data Files tab in the Setup Screen. It is also available in the Connect Screen’s Custom Collection options.)
PakBus Encryption is now supported for communication between LoggerNet and CR1000, CR3000, and CR800 series dataloggers. Note that the datalogger must be running OS 26 or later in order for PakBus Encryption to be used. A
Two new root devices, SerialPortPool and TerminalServerPool, have been added to allow for
You can now access a datalogger’s Settings Editor from the Connect Screen either by right-clicking on the datalogger or from the Datalogger menu. You can also manually set the datalogger’s clock from the Connect Screen either by double-clicking in the Station Date/Time field or from the Datalogger menu. Boolean values displayed in the Connect Screen’s Numeric Display now have an LED icon next to them to allow for easy toggle.
You can now view additional statistics in the Status Monitor for table-based dataloggers including watchdog errors, skipped scans, and battery errors. (Note that there is a Poll for Statistics check box on the datalogger’s Schedule tab in the Setup Screen that must be enabled to poll for these statistics.)
The Task Master has been integrated into the LoggerNet server. This allows for remote administration of the Task Master. (See Select Server in the Task Master help for conditions that must be met for remote administration of the Task Master.)
NOTE: Integrating the Task Master into the server involved extensive changes. When upgrading to LoggerNet 4.2 from a previous version, an attempt will be made to import all previously-configured tasks. However, imports have only been tested back to LoggerNet 3.4.1. After upgrading (from any previous version of LoggerNet), you should verify that all of your tasks have imported correctly.
Calendar-based scheduling has been added to the Task Master. This allows for non-interval task execution (including data collection). See Example #3 in the Task Master help for an example of calendar-based data collection.
A Constant Customization feature has been added to the CRBasic Editor. This allows you to define values for one or more constants in a program prior to performing a conditional compile. The constants can be set up with an edit box, a spin box field for selecting/entering a value, or with a list box. A step increase/decrease can be defined for the spin box, as well as maximum and minimum values.
The CRBasic Editor now allows you to Save and Open Display Settings. Display settings affect the look and feel of the CRBasic Editor. This includes font and background, as well as syntax highlighting.
View Pro has a new View Record option in the right-click menu that can be used to view an entire record in a new window.
LoggerNet 4.1
One of the main efforts in the development of LoggerNet 4.1 has been the ability to use LNDB databases with View Pro. The ability to lock the timestamp column on the left of the data file has also been added to View Pro. This keeps the timestamp visible as you scroll through columns of data.
The Device Configuration Utility has a new off-line mode which allows you to look at the settings for a certain device type without actually being connected to a device.
The CRBasic Editor now has the capability to open a read-only copy of any file. This gives you the ability to open multiple copies of a program and examine multiple areas of a very large program at the same time. You can also now continue an instruction onto multiple lines by placing the line continuation indicator (a single space followed by an underscore “_”) at the end of the each line that is to be continued. Also, bookmarks in a CRBasic program are now persistent from session to session.
In the Troubleshooter and the Setup Screen (Standard View), you can now click on a potential problem to bring up a menu that allows you to go the Setup Screen or Status Monitor to fix the potential problem, bring up help describing the problem, or in some cases fix the problem directly.
Campbell Scientific’s new wireless sensors have been added to the Network Planner.
You can now view statistics (average, minimum, maximum, and number of data points) for each data value being displayed in a Connect Screen graph. All of the Connect Screen’s displays (table monitor, numeric displays, and graphs) can now show the units that have been assigned to the data values.
Split has a new “Time Sync to First Record” option that can be used with the time-sync function to avoid blank lines at the start of the output file. Also, a range of time values rather than a single time can now be entered in a Split Copy Condition.
CardConvert can now be run from a command line without user interaction.
An option to provide feedback on LoggerNet has been added to the LoggerNet Toolbar’s Help menu.
Miscellaneous other changes and bug fixes have also been implemented in this version.
NOTE: Beginning with this version of LoggerNet, Windows 2000 is no longer supported.
LoggerNet 4.0
LoggerNet 4.0 introduces a new look and feel to the Toolbar. Applications are divided into categories to make navigating the Toolbar easier. You can also organize a Favorites category for the applications that you use most often.
A new file viewing application, View Pro, is introduced in LoggerNet 4.0. View Pro allows you to have multiple data files open at one time. Multiple graphs can be created from the same file or from multiple files. There is no limit to the number of traces per graph. Data can be graphed in a variety of formats including a Line Graph, X-Y Plot, Histogram, Rainflow Histogram, or FFT (2D or 3D).
Another new application, the Network Planner, is included in LoggerNet 4.0. The Network Planner is a graphical application that assists the user in designing PakBus datalogger networks. It allows the development of a model of the PakBus network, proposes and verifies valid connections between devices, and allows integration of the model directly into LoggerNet 4.0.
A File Retrieval tab has been added to the Setup Screen for the CR1000, CR3000, and CR800 Series dataloggers. This tab provides an easy way to retrieve files from a datalogger on a specified interval. A Notes tab has been added to all devices to allow the user to keep notes about the device for future reference. This is purely for the user's convenience. (The information in a datalogger's Notes tab is displayed in the Connect Screen, when that datalogger is selected.)
A new menu item has been added to the Setup Screen to enable a Stations Only view. When this is enabled, only stations will be shown in the Network Map. This can be especially helpful, when working with a large network.
The Connect Screen has been reorganized with most of the buttons now residing on a toolbar at the top of the window. A Table Monitor has been added in the middle of the window that can be used to monitor the values for one entire table.
Notes On Updating From Earlier Versions of LoggerNet
You should be able to update from any 2.x or 3.x version of LoggerNet by simply installing over the existing LoggerNet. Our installation program should be able to find the program and working directories from the Windows registry. You may, alternatively, wish to uninstall the previous version before installing this newest version of LoggerNet. If so, you can enter the same working directory as before (default was c:\campbellsci\loggernet) to ensure the network is brought forward.
LoggerNet 4.x can readily use the network map from LoggerNet 2.x or 3.x. However, network maps are not backwards compatible. If you upgrade your existing version, once LoggerNet 4.x is opened, the network map will no longer be compatible with LoggerNet 2.x or 3.x. For this reason the upgrade installation will automatically make a copy of the <WorkingDirectory>\LoggerNet\sys directory and all of its contents. The copy will reside in <WorkingDirectory>\LoggerNet\NetworkMapBackup\<version>\sys. If it then becomes necessary to revert back to a previous version of LoggerNet, you will need to remove the <WorkingDirectory>\LoggerNet\sys directory and replace it with the <WorkingDirectory>\LoggerNet\NetworkMapBackup\<version>\sys directory.
If you are installing LoggerNet and LoggerNet Remote on the same computer (which then becomes LoggerNet Admin), LoggerNet must be installed before installing LoggerNet Remote. LoggerNet Remote can also be installed independently on a computer if you will be accessing a LoggerNet server running on a different computer across a network.