> For the complete documentation index, see [llms.txt](https://docs.efento.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.efento.io/nb-iot-loggers/operation/data-usage.md).

# Data usage

We have developed a [**data usage calculator**](https://toolkit.efento.io/battery-life-calculator/BatteryLifeCalculator.html) that can be used to estimate the amount of cellular data transferred by the logger based on selected configuration parameters.

{% hint style="warning" %}
The calculated result is only an **estimate** and may differ from the actual data usage. The calculator should therefore be treated as a **reference tool rather than an exact prediction of data consumption**.
{% endhint %}

## **Using the calculator**

{% stepper %}
{% step %}

### Select the logger model

Select a device from the list or search for it by name or EAN.

<figure><img src="https://740246929-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGPFUI36OraG706yJS7dJ%2Fuploads%2FJf4SMtIJXcugcJ289wkN%2Fbattery_life_data_usage_calculator.png?alt=media&amp;token=188c7282-9c62-46a2-9d5a-dfcac76b3706" alt="" width="369"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure the logger

Adjust the available configuration parameters to match the intended logger setup.
{% endstep %}

{% step %}

### Review the results

The calculator automatically updates the estimated monthly data usage based on the selected configuration. The results show the estimated amount of data uploaded by the logger and downloaded from the server.
{% endstep %}
{% endstepper %}

## **Calculator inputs**

The calculator uses the following configuration inputs for all logger models:

* Measurement interval
* NB-IoT transmission interval
* Bluetooth (BLE)

For **4–20 mA** and **0–10 V** loggers, an additional **measurement calibration** field is available to match the characteristics of the connected input.

<figure><img src="https://740246929-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGPFUI36OraG706yJS7dJ%2Fuploads%2FLoiNWShnQswLhtceFv4O%2Fdata_usage_calculations.png?alt=media&amp;token=f80746dc-1cde-436d-aa1f-613d59c19777" alt=""><figcaption></figcaption></figure>

## **Data usage considerations**

The amount of data sent and received by the logger depends on its configuration and on the conditions at the installation site. The main factors are:

* **Transmission interval** – each transmission contains a fixed part (e.g. logger identification and timestamps) and is usually confirmed by the server. The more often the logger sends the data, the higher the data usage.
* **Measurement interval** – the shorter the measurement interval, the more measurements are sent in each transmission.
* **Number of measurement channels** – each measurement channel adds its measurements to every transmission. Loggers with more channels (e.g. a 3-channel pulse counter) use more data than single-channel loggers with the same settings.
* **Rules** – each transmission triggered by a rule is an additional transmission, sent outside the regular transmission interval.
* **ACK interval** – by default, the server confirms every transmission. Confirmations increase data usage slightly, but they ensure that no data is lost. We recommend keeping the default setting.
* **Transfer limit** – limits the number of transmissions in a set period of time and helps to keep the data usage under control, e.g. when rules are triggered frequently.
* **Network coverage** – in places with poor NB-IoT coverage, the logger may need to repeat transmissions, which increases data usage.
* **Server responses** – configuration changes, time synchronization and other requests sent by the server increase data usage. If the logger sends the data to the customer's server, send the configuration to the logger only when it needs to be changed.
* **Other transmissions** – transmissions triggered by the user (button or Bluetooth), restarts of the logger, the troubleshooting mode and firmware updates also use data.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.efento.io/nb-iot-loggers/operation/data-usage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.