Saga Logger release notes v2.4.x

Additional logger parameters reported for improved fleet visibility and monitoring

Logger not to show invalid temperature on display when powered up for the first time

Logger preserves button push wake-up schedule when firmware updated

Logger internal temperature measured on the hour

Minor processor timing issues fixed

Fixed a bug that caused some devices to miss the first wake-up after entering Low Power Mode

Potential charging event edge case addressed

Some minor edge cases in the code addressed

Loggers in production mode should not estimate 0% after cold start. Needs to be fixed to fix problems in the production lines for Saga.

Recalled status event ID (RS) was already reserved. New ID defined for this event (OS).

Manual USB data upload improvements for non-active mode. Fixed to avoid extra manual work in the unlikely scenario if USB data upload is needed for loggers that are in non-active mode.

To eliminate the risk of overcharging, improvements have been made to the end-of-charge detection process.

Additional logger parameters are reported for improved logger fleet visibility and monitoring.

Minor development improvements (unique version strings for local builds and logger memory management improvements).

An error message is deployed when an artificial temperature rise is measured by the PR-T80 probe when batteries are at depletion level. This helps Controlant and customers identify these anomalies. This is the first step to improving this issue. Later this year, Controlant will present a final solution where this artificial data will not be recorded at all.

Fixed the bug that, in some cases, if a logger is cooled down very fast, the logger screen freezes before showing the “display does not function in current temperature” screen.

Fixed a very rare bug that was identified in a limited number of loggers. These loggers reported two measurements per modem wake-up (i.e., cellular transmission) and temperature data gaps between them. The affected loggers were taken out of circulation, and measures have been implemented to prevent this bug from occurring again.

Fixing a bug: if the delivery method for a shipment is button, and the button is held down for too long (over 12 seconds) when stopping the shipment, the logger display got stuck in the stopping screen.

Fixed the bug where in the unlikely event that the logger receives the shipment after the shipment has been delivered, logger could trigger excursions after the delivery.

Fixing a bug relating to a rare timing issue could cause the accelerometer flight detection to fail.

After a logger becomes fully charged in a charging station, it will not start charging again unless unplugged and plugged in again. This fixes the bug, and the logger will now top off the battery if left in the charging station for a prolonged period.

Fixing a bug where, in rare cases, the logger would not wake up when plugged into a charging station.

Minor fixes that mainly affect logging of parameters, development, and logger production.