(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.
Extended the .tdf close timeout from 1 minute to 5 minutes. This timeout is used when LoggerNet retrieves the table definition file (tdf) from the logger. In some RF networks, it was taking LoggerNet longer than 1 minute to acknowledge when it had received a packet containing tdf information due to network latency. Consequently, LoggerNet would never receive the complete tdf that is needed for scheduled collections.