(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 (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().
Fixed the HTTPGet() instruction when neither Content-Length: nor Transfer-Encoding: chunked existed in the returned header. Chunked encoding is now assumed when the header is missing these two items in the returned header.
Improved checking for sufficient buffers in pipeline mode.
Changed waking a waiting task from another. It will only wake the waiting task if it is in the correct wait queue.
Modified the SlowMeas task to wake from scan tasks if it is waiting for the periodic event SLOW_MEAS. Unconditionally waking the task when the other scans started was causing the wait for slow sliced measurements to end early and possibly cause measurement watchdogs.
Fixed loading encrypted programs when using and changing the Constant Table values. This was failing in previous versions of the operating system and would produce a compile error when the program tried to start with the new settings.
Fixed a case where subroutine or function containing a measurement instruction was called from a slow sequence in sequential mode. This had the possibility of a deadlock condition where the slow sequence would stop running.
NL115/NL121 low level Ethernet driver was fixed to handle multiple buffers combined together when one of those buffers contains an odd number of bytes. Previously, this would result in a malformed TCP/IP packet, which caused connection problems.