CR6 OS 6.02
Updated: 17-03-2017

  1. (CRITICAL) Upgrading the Operating System could reset all the CR6’s settings back to the factory defaults. Sending this OS remotely is not recommended but is possible. To restore settings after the update, it is recommended that a backup be made of the current logger settings or take programmatic measures to ensure your settings can be restored. This can be done using the DevConfig backup utility or CRBasic instruction SetSetting. Watch the Video Tutorial: Sending an OS to a Local Datalogger.
  2. (WARNING) After upgrading the CR6-WiFi and CR6-RF451 to this version of the operating system, it is recommended that the user also update the operating system in the radio daughter boards. This version of the CR6 operating system has been tested with version 3.0 of the Wifi daughter board and version 3.0 of the RF-451 daughter board. These operating systems have a *.iobj extension and are placed in the same directory as the CR6 operating system. Use the same procedure to load the Wifi or RF operating systems using the Device Configuration Utility, select Daughter Card Operating System Files (*iobj) from Files of type drop down.
  3. (WARNING) This operating system version, and all versions moving forward, will disable the datalogger FTP, Telnet, and Ping servers by default. Updating the operating system using the Send OS tab of Device Configuration Utility will revert all datalogger settings to factory defaults and these services will be disabled. Sending the operating system as a program or by way of File Control will update the operating system but leave the FTP, Telnet, and Ping enabled settings intact. Note that disabling the FTP, Telnet, and Ping servers does not prevent the datalogger from acting as a client; the datalogger will continue to be able to use instructions such as FTPClient() and PingIP().
  4. Resolved an issue with the datalogger HTTP server that would cause the datalogger to lose memory due to a failure in one of the TCP timers.
  5. Fixed an issue that would cause a TCP timer to reset when http packets were not complete. This would cause the pbufs to never close, and the datalogger would lose pbuf memory.
  6. CR6-Wifi daughter board operating system - Fixed a memory leak that caused the Wi-Fi module to lock up under heavy load.