Skip to main content

Why does my logger not upload data in real time?

In this section:

The logger uploads data every time it connects to the Controlant Cloud. An attempt to connect to the Cloud is called a wake-up.

When a logger is not in a shipment, it follows a standby wake-up schedule (standby mode has 12-hour wake-up intervals by default), and when in a shipment, the logger follows the wake-up interval (i.e., the frequency of wake-up) that was set for the respective shipment.

Note

The wake-up interval selected for the shipment takes priority over the internal wake-up schedule that the logger follows in standby mode. For example, in a shipment for which the wake-up interval was set to 1 hour, the logger will connect to the Controlant Cloud every hour and upload data when it does so.

Outside of the logger's scheduled wake-up, it will wake up when a button is pressed and when an alarm in a shipment is triggered, i.e., a temperature excursion. See also: Wake-up behavior

Some reasons why data is not showing immediately on SCM system can be:

Device is in Low Power Mode

The display indicates any battery charge below 10% (Low power mode or Hibernation Mode) with a full-screen service message:

Controlant Saga Logger displaying Low Power Mode. Text on the image: "Low power mode. The logger is now in low power mode. Please charge device."

Low Power Mode and Hibernation Mode affect the wake-up interval in different ways:

When the battery level goes below 10%, the device enters Low Power Mode:

  • The device switches to a 24-hour wake-up interval, whether in shipping mode or standby mode.

When the battery level goes below 5%, the device enters Hibernation Mode:

  • All non-essential functions—including wake-up—are suspended. Temperature data is collected and stored within the device every 10 minutes so that no data is lost.

Tip

To resume normal operation of the device, charge to at least 15%.

See also: What should I do when I receive a logger in Low power mode?

Device has poor signal strength

The logger uses 2G/3G and 4G (LTE) mobile networks to connect to the Controlant Cloud. Connectivity depends on several external factors, including:

  • Availability of cell towers (e.g., on the ocean, in a rural area, etc.)

  • Bandwidth limitations of the cellular network

  • Connectivity-blocking materials surrounding the logger (e.g., liquids, metals, and concrete)

Note

If the logger is unable to connect to the Controlant Cloud when it wakes up due to a poor cellular connection, it will save the data but won't be able to upload it. The logger will upload this saved data, along with any new data it records, the next time it successfully connects to the Controlant Cloud. This ensures that no information is lost.

Device is in Flight Mode

While they are in Flight Mode Flight headed east icon, loggers will not connect to the Controlant Cloud and upload data.

When a logger in a shipment detects a landing event, it will attempt to connect to the Controlant Cloud outside of the scheduled wake-up and upload data. From that moment, it will follow the shipment's wake-up schedule.

In case the logger does not detect the landing, it will remain in flight mode for 18 hours and attempt to connect at the next scheduled wake-up for the shipment.

Delay related to shipment creation flow

If a shipment is created and manually marked as shipped in the Supply Chain Monitoring (SCM) system or through integration, the logger will not be aware that it’s in a shipment and/or shipped until it connects to the Controlant Cloud and receives this information. The logger will attempt to connect to the Cloud within 12 hours, depending on the following conditions:

  • If the logger is in standby mode and no button has been pushed within 5 override intervals since the shipment was created, the logger will follow its internal wake-up schedule and will attempt to connect within 12 hours.

    Note

    If the logger is on a flight at the time of its scheduled wake-up, the delay will be extended.

  • If a button has been pushed within 5 override intervals before the shipment was created, the button push will trigger the logger to wake up hourly, and it will receive shipment information in the first wake-up after shipment creation.

If such a delay related to shipment creation flow occurs, the status of the logger in the shipment in SCM system will be Shipping with a syncing iconSL_icon_syncing_display. This means that although the status of the logger in the portal is set to Shipping, the logger has not yet synced this information.