CR3000 OS 31.03
Updated: 04-28-2017

  1. (CRITICAL) Upgrading from versions prior to version 28 of the Operating System will reset the datalogger’s CPU drive. This is due to a change in the format of the file system from FAT16 to FAT32. In order for the datalogger to operate correctly, as part of the upgrade, the CPU drive is formatted to FAT32. Any programs stored and running from the CPU drive will be lost. It is not recommended to update the datalogger’s Operating System over a remote connection where program control regulates the communication equipment (turning it on or off, etc.). In these cases, an on-site visit and a backup using DevConfig’s backup utility is necessary to update the datalogger’s Operating System. In all cases where the datalogger is being updated with an Operating System prior to 28, the use of DevConfig’s backup utility is recommended due to the fact that the CPU drive is formatted using the new FAT32 format. Watch the Video Tutorial: Sending an OS to a Local Datalogger.
  2. (WARNING) This operating system version (starting with operating system version 31.02), 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().
  3. Fixed a minor issue when the TCP/IP memory buffer was set to NULL. This condition would mainly occur when set up to listen on TCP/IP ports.
  4. Changed SetSetting() reference from "UTC Offset" to "UTCOffset". The syntax is now SetSetting("UTCOffset",value). This is consistent with the TableName.Fieldname syntax of Status.UTCOffset used to read the setting.
  5. Fixed a Declaration bug that occurred when whitespace (spaces and tabs) were used.
  6. Fixed an issue when pulling data via LoggerNet when certain table conditions were present. (auto-allocated, interval driven tables that resulted in only one frame of data).
  7. Fixed response of ModBusSlave() when a packet comes in that is not addressed to the datalogger.
  8. Adjusted the maximum transmission unit (MTU) size of TCP/IP packets to 1380 from 1460. It was found that certain cellular networks reduce the size of the MTU, causing the packets from the datalogger to be fragmented. This specifically affected the use of TCP/IP instructions such as EmailRelay() and FTPClient().