> 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/device-settings/transfer-limit.md).

# Transfer limit

Efento NB-IoT logger allows you to limit the number of transmissions in a given period of time. For instance, you can set the device to be able to send the data maximum 5 times in a 30 minutes window. This feature allows you to control the battery life time in an environment, in which the small fluctuations of the measurements would trigger the transmission very often. By default this function is disabled (there is no transfer limit set).

You can set up two parameters of the transfer limit function: number of transmissions (N) and time period (T). After each successful transmission a transmission counter increments by 1. The counter decrements every time period (T). If a transmission is triggered, but the counter is equal or greater than the set number of transmissions (N), the communication with the server is blocked, until the counter decrements to a value below the number of transmissions (N). This applies only to regular transmissions and threshold triggered transmissions. Transmission triggered over Bluetooth will always be sent to the server.

{% hint style="info" %}
**If you enable the transfer limit, the device may not be able to send the data to the server, even if an alarm threshold has been exceeded!**
{% endhint %}

In order to set the transfer limit:

1. Connect to the logger, tap on the three dots in the upper right corner -> “Power user” -> “Network settings” -> “Transfer limit”
2. Enable the transfer limit and key in the number of transmissions and the time period for the transfer limit function


---

# 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/device-settings/transfer-limit.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.