Back To Update List

CR300 Series OS 6.01
Updated: 10-18-2017

  1. (URGENT) An issue was found in CR3XX operating systems with a revision number less than 06.00 that could cause the datalogger to become unresponsive in some systems after 50 days. CR3XX operating system version 06.00 and greater resolve this issue. It is highly recommended that all CR300s and CR310s be upgraded to an operating system with a revision number that is 06.00 or greater.
  2. (WARNING) Upgrading the Operating System could reset all CR300 settings back to factory defaults when updating from an operating system prior to version 05. Sending this Operating System remotely can be done but is not recommended. To restore settings after the update, it is recommended that a backup be made of the current datalogger settings or take programmatic measures to ensure your settings can be restored. This can be done using Device Configuration Utility’s (DevConfig) backup utility or the CRBasic instruction SetSetting(). Watch the Video Tutorial: Sending an OS to a Local Datalogger.
  3. (NOTE) This operating system release is a bug fix release. There are no new enhancements or features added except for the items listed below.
  4. Updated the watchdog to verify that the run program tasks are always in a task queue. If the run program task fails to be in the task queue, the datalogger will now watchdog and increment the watchdog counter in the status table. This was done to ensure the datalogger run program task is always working correctly.
  5. Updated the datalogger operating system USB driver to detect transmission timeout errors.
  6. Modified the DHCP server startup when using RNDIS to check for a USB connection before starting. This prevents the DHCP server from incorrectly responding to DHCP requests on all Ethernet, Wi-Fi, and RNDIS interfaces at start up.
  7. Updated the AM25T() instruction to turn excitation off before starting AM25T measurements. Prior to this change excitation was left on. This would cause certain measurements that did not need excitation to be read incorrectly.
  8. Fixed an issue that caused the Ethernet connection to reset when the DHCP was not in a bound state.
  9. Updated the text for the default network so it is consistent with the text displayed by other Campbell Scientific dataloggers.
  10. Modified the operating system to disable all sleep modes when USB is connected.
  11. Fixed an issue when using SerialOpen() and SerialIn() with Format 0. If a PakBus sync byte was found, SerialIn() could drop into a PakBus mode sending all received data to the PakBus task, which caused SerialIn() to fail.
  12. Fixed an issue when using SerialOpen() on COM1 that could keep the logger awake for an extra 15 seconds after a SerialClose() was called.
  13. Changed the default username and password used by the datalogger FTP server. The new username and password are now both NULL. This change will require the user to set their own username and password (both required) in order to use the datalogger FTP server. Neither the username or the password can be blank. This was done to better secure the datalogger FTP server against malicious attacks. This change does not affect the FTPClient() instruction.
  14. Fixed an issue that caused the DHCP server to respond when Wi-Fi was configured to "Join a Network".
  15. Updated WebSockets to support the logon command that is used by the internal web pages.
  16. Fixed an issue when transmitting from RS232 that could cause delays between bytes and slow the task down.
  17. Fixed Files Manager when using option 3209. Note: Capture will alternate between writing to two files "_0" and "_1" to allow for wear leveling of the flash memory.
  18. Updated Files Manager to delete the file if open fails.
  19. Fixed a signature issue that prevented PreserveVariables() from working.
  20. Updated PreserveVariables() to store values before an operating system restart.
  21. Added Settings.PPPInfo and Status.PPPInfo.
  22. Updated Status.MemoryFree to reflect memory used for communication buffers.
  23. Updated table creation to always store a timestamp when using TrigVar parameter.
  24. Fixed a table timestamp issue that occurred when using tables that did not contain the DataInterval() instruction and the datalogger was waking up from a sleep state.
  25. Updated time of maximum and time of minimum to not inherit units in tables.
  26. Fixed an issue with table allocation when the table interval could not be determined which caused the requested number of records to be overwritten.