(CRITICAL) Upgrading the Operating System could reset all CR6 settings back to the factory defaults. Sending this OS remotely is possible, but 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 the Device Configuration Utility Backup utility or the CRBasic instruction SetSetting(). Watch the Video Tutorial: Sending an OS to a Local Datalogger.
(WARNING) If updating the dataloggers operating system from a version prior to 7.0, the user will need to install updated USB drivers for the CR6. Those new drivers are available in Device Configuration Utility version 2.16 (or greater). This software is available on the Campbell Scientific website.
(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 card. This version of the CR6 operating system has been tested with version 4.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 Device Configuration Utility. Select Daughter Card Operating System Files (*iobj) from Files of type drop down. If the version of the WiFi OS is older than 3.01 you need to install 3.01(included) prior to installing 4.0.
(WARNING) This operating system version (starting with operating system version 06.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().
IMPORTANT: Resolved an issue with PPP connections that timed out or were closed with the PPPClose() instruction and then reopened with the PPPOpen() instruction. This type of connection is often used with cellular modems. A flag that tells the datalogger that the network is online was not being reset correctly, resulting in an unresponsive PPP network interface.
Fixed terminal W mode so the terminal will not exit when receiving a character on another comport unless CR (carriage return), or ESC (escape) is received.
Fixed terminal mode monitoring via W command when a new connection is made. The datalogger now ignores a new connection unless it is via PakBus or Telnet. The datalogger recognizes a connection when a CR (carriage return) or ESC (escape) character is received from the new connection.
Fixed Tablename.Fieldname when sampled into another table when a record did not exist in the source table. The operation now returns a NAN when this condition occurs.
Fixed GoesTable() to output commas instead of spaces.