CR3000 OS 32.02
Aktualisiert: 21-12-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. 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.
  4. 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.
  5. 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.
  6. 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.
  7. Fixed GoesTable() to output commas instead of spaces.