> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/user/fr/guide/devices-and-settings/device-specific-controls/power-management/battery-charge-mode.md).

# Mode de charge de batterie

Choisissez quand la batterie de secours d'un appareil GPS se charge dans Navixy, avec les options de charge automatique, uniquement contact mis, ou contact mis avec repli en cas de batterie faible.

Contrôle le moment où la batterie de secours de l’appareil se charge.

## Paramètres

* **Mode de charge** : choisissez quand la charge a lieu :
  * **Automatiquement lorsque nécessaire** : l’appareil se charge selon les besoins.
  * **Uniquement lorsque le Contact est activé** : charge uniquement lorsque le véhicule est en marche.
  * **Lorsque le Contact est activé ou que la batterie est faible** : se charge lorsque le Contact est activé, ou automatiquement à tout moment dès que le niveau de batterie descend sous 30 %.

## Disponibilité

Apparaît sur les modèles d’appareils alimentés par batterie qui exposent un mode de charge.

## Voir aussi

* [Mode "veille"](/docs/user/fr/guide/devices-and-settings/device-specific-controls/power-management/sleep-mode.md) : configurez les conditions de veille d’économie d’énergie.


---

# 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://navixy.com/docs/user/fr/guide/devices-and-settings/device-specific-controls/power-management/battery-charge-mode.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.