The following changes have been released in Kooltrak v1.11.21
| Change | Reason | |||
| 1 | Support for "high resolution" loggers added to all program types. | New logger types 212101, 212201, 213101 & 213201 have been released. | ||
| 2 | There is a minor change in all types relating to the summer/winter time change. | Corrects problem reported by user. | ||
| 3 | In Professional type, support for networks of loggers included. | Additional feature. Can be used to download historical data from all network connected loggers. Useful stand-alone and in conjunction with Koolprobe. Note that this does not provide real-time data collection, which contimues to require Koolprobe |
||
| 4 | In Professional type, support added for temperature data correction from calibration files. | Additional feature. Kooltrak will ship calibration files on floppy disk with calibrated loggers. |
||
Kooltrak v1.11.21 supports new "high resolution" loggers, and this code has been added to all "types" of Kooltrak because the requirement for these products exists with all users.
There is a minor change in all versions of Kooltrak related to a problem discovered recently with the winter/summer time change.
For information we point out that when a temperature display covers a time range that includes a clock time change as for summer time, there is a problem in deciding how to display data across this boundary. There is either a "missing" hour, or two "overlapping" hours, and a decision about how to display the data must be made. Our choice is to display all data using the "current" time zone, ie the time zone applying at the time when the display is produced. This avoids the missing or overlappinhg hour problem but means the data from an earlier time zone is displayed with an incorrect local clock time. If that is a problem the only reasonable solution seems to be to display all data using UTC, which can be done by setting the time offset to zero in the display options. Sorry about that, but it isn't a problem created by Kooltrak!