(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.
(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().
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.
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.
Fixed the Ethernet driver for smsc9221 (NL116 and NL121). When getting bombarded with packets the receive overflow interrupt was occurring faster than could be dealt with. This caused task stacks to fill up with interrupt context and eventually crash. The fix was to disable the interrupt which is later enabled by the task when the next packets are read.
Fixed the Ethernet output driver used in the NL121 and NL116 when sending more than 1500 bytes, such as with HTTP output packets.