LoggerNet/U Actualización a última versión de LoggerNet

Expandir todoDesplegar todo

1. What's new in 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 while scrolling through columns of data. 
   • The Device Configuration Utility has a new off-line mode which allows viewing 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 provides the ability to open multiple copies of a program and examine multiple areas of a very large program at the same time. In addition, an instruction can be continued onto multiple lines by placing the line continuation indicator (a single space followed by an underscore “_”) at the end of 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), it is now possible to click on a potential problem to bring up a menu that enables the user to go to 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.
   • Statistics (average, minimum, maximum, and number of data points) can now be viewed for each data value being displayed in a Connect Screen graph. All of the Connect Screen’s displays (table monitor, numeric displays, and graphs) 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.

2. After upgrading to the newest LoggerNet version, will the new software run old programs?

   We strive to make sure that all files associated with LoggerNet are forward compatible so that the software continues to work as it had before the upgrade. In some instances, however, the files are not backward compatible. For example, a file created using version 1.2 of SCWin may not be compatible with version 1.0 of the program.

3. When an upgrade from one version of LoggerNet to another is purchased, can both versions be used at the same time by the same user?

   No. An upgrade to the software is an upgrade to the current license. When the upgrade is installed, it installs new versions of any files that have changed. The user still has only one valid license for the software. To run the software on two separate computers, a second license must be purchased at the full price.

4. ¿Que es nuevo en LoggerNet 4.2?

   • LoggerNet now supports IPv6 addresses.
     • Note: Although LoggerNet now supports IPv6 addresses that can be used to specify servers, CR1000, CR3000, and CR800-series dataloggers will not support IPv6 until a future OS release. Check the OS Revision History to determine when IPv6 support is added to the OS.
   • LoggerNet now supports display and input of Unicode characters and strings in many areas of the product.
   • The ability to set up subnets of the network map has been added to LoggerNet Admin. After subnets have been configured, the choice can be made to view a subnet rather than the entire network in the Setup Screen, Connect Screen, and Status Monitor.
   • Defaults can be set up 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.
   • PakBus Encryption is now supported for communication between LoggerNet and CR1000, CR3000, and CR800-series dataloggers. AES-128 encryption is used.
     • Note: The datalogger must be running OS 26 or later for PakBus Encryption to be used.
   • Two new root devices (SerialPortPool and TerminalServerPool) have been added to allow for modem pooling. Pooled devices may be useful in cases where LoggerNet is used to call, by phone, multiple remote dataloggers, and more than one modem and phone line is available to make the connections.
   • A datalogger’s Settings Editor can now be accessed from the Connect Screen either by right-clicking the datalogger or from the Datalogger menu. The datalogger’s clock can be manually set 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 toggling.
   • Additional statistics can now be viewed in the Status Monitor for table-based dataloggers, including watchdog errors, skipped scans, and battery errors.
   • The Task Master has been integrated into the LoggerNet server. This allows for remote administration of the Task Master.
   • Calendar-based scheduling has been added to the Task Master. This allows for non-interval task execution (including data collection).
   • A Constant Customization feature has been added to the CRBasic Editor. This allows the definition of 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 or entering a value, or a list box.
   • The CRBasic Editor now offers the ability to save fonts, background colors, and syntax highlighting format options to a file that can be reloaded.
   • 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.
5. If the LoggerNet upgrade is purchased for the current version license, how does the upgrade work? What is the process for upgrading?

   The installation for the upgrade can be run without uninstalling the existing version of LoggerNet. Existing configuration, data, and other files (such as CRBasic program files) are maintained so that the next time LoggerNet is opened after an upgrade, it is easy to resume work where the user left off.

6. Is it possible to upgrade from PC200W to the current version of LoggerNet?

   There is no upgrade path from PC200W to LoggerNet. Only licensed copies of LoggerNet qualify for upgrade pricing to the current version.

7. Where is there information about the revisions to the LoggerNet software?

   The LoggerNet revision history information can be found through the “Software and OS Revision Histories” web page. Revision history information is available for LoggerNet patches and upgrades, as well as for the trial versions of the software.

8. After purchasing a LoggerNet upgrade license, can the license key be entered into the current installation, or does LoggerNet need to be reinstalled from the CD?

   A LoggerNet upgrade must be installed by running the installation from the CD. The new license key is entered during this installation.

9. Are LoggerNet upgrades free?

   Within a version, such as an upgrade from a version 1.0 to a version 1.1, upgrade patches are available for download, free of charge, from our website. A link to the patch can be found in the Downloads area of the LoggerNet product page.

   To upgrade from one major version to the latest version (for example, version 1.3 to 2.0), the purchase of LOGGERNET/U (Upgrade to Current Version of LoggerNet) is required.

10. Which software updates are free?

    The blog article "How to Navigate the World of Software Upgrades, Patches, and Trials" explains the difference between patches (free of charge) and upgrades (for a fee). This example quickly shows the difference between an upgrade and a patch:

    Upgrade	Patch
    Major version change, such as 1.3 to 2.0	Minor version change, such as 1.3 to 1.4
    Typically requires purchase for a fee	Free of charge