> 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/power-saving-features.md).
# Power saving features
In order to ensure maximum battery saving, the logger is set to PSM = 0, eDRX = disabled. This means that the device will finish the transmission automatically after sending data to the server and (possibly) receiving a new configuration from it. The device does not stay awake waiting for additional transmission from the server. The only possible way to transfer data from the server to the logger is to send them in response to the data packet received from the logger.
The NB-IoT standard provides for the retry of data transmission, if it is impossible to send it correctly. The method of repeating the transmission is not configurable by the user, it is done automatically by the logger. The number of retries is determined by the ECL (Coverage Enhancement Level) parameter, which specifies the number of retries of failed transmission attempts defined as 2i (i = 1… 7). The parameter is set from 0 (normal operation) to 2 (bad signal quality / high noise, large number of retransmissions required). The higher the ECL value, the higher the energy cost of sending data, and therefore the shorter the battery life. When installing the NB-IoT logger, it is worth checking the ECL level in the place where it is to work (the issue is described in the "Device status" section).
NB-IoT devices should not move between base stations, as this results in the need to re-register to the network each time the base station changes. The registration process takes a relatively long time, therefore frequent relocation of the logger between base stations adversely affects the battery life.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.efento.io/nb-iot-loggers/power-saving-features.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.