LoggerNet Patch 4.4.1
Updated: 07-21-2016

  1. Toolbar Bug Fix - Fixed an issue with a hard-coded file path of C:\Campbellsci. With certain video settings, the toolbar would sometimes create files in this directory. This would cause the toolbar to fail, if LoggerNet was installed on a different drive such as the D:\ drive.
  2. Setup Screen Bug Fix - Fixed a problem where the Setup Screen would be slow to start after launch from toolbar.
  3. Setup Screen Bug Fix - File Retrieval Tab: Fixed an issue where if a datalogger file was successfully retrieved but could not be stored in the specified location (i.e. network drive) and the file was marked for deletion after retrieval, the file would be deleted from the datalogger but not stored on unavailable drive.
  4. Connect Screen Bug Fix - Fixed a problem where occasionally array elements were not displayed correctly and incorrect values would be shown.
  5. Connect Screen Bug Fix - Fixed an issue where you could not send a NAN value to a datalogger.
  6. Short Cut Enhancement - Added sensor file support for the optional FillNaN parameter in an SDI-12 measurement for dataloggers that support it.
  7. Short Cut Bug Fix - Fixed a bug where a compile could fail if extended (non-ASCII) characters were in the file path.
  8. Short Cut Bug Fix - Improved manual moving of wires for some sensors.
  9. CRBasic Editor Bug Fix - Fixed a bug where a compile could fail if extended (non-ASCII) characters were in the file path.
  10. RTMC Enhancement - Warning icons are now suspended for 10 seconds to allow normal data flow to occur without reporting an error.
  11. RTMC Enhancement - Changed the library used for the TLS stack from axTLS to mbedTLS.
  12. RTMC Bug Fix - Fixed renaming issue reported with some components.
  13. View Pro Bug Fix - Fixed a bug where Histogram, FFT, and Rainflow data could fail when graphed.
  14. LoggerNet Server Bug Fix - Fixed an issue where if a datalogger file was successfully retrieved but could not be stored in the specified location (i.e. network drive) and the file was marked for deletion after retrieval, the file would be deleted from the datalogger but not stored on unavailable drive.
Baidu