> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/pricing/sensor-batteries.md).
# Sensor Batteries
3V lithium battery
The CR17450 3V lithium battery is a cylindrical primary (non-rechargeable) lithium battery commonly used in low-power industrial devices, including most MFC sensors (like the LHT65N model).
***
#### .png?alt=media\&token=d6f7c08b-7900-4e8b-839e-daf2fef2a56a)
#### CR17450 3V Lithium Battery – Overview
| Feature | Description |
| ----------------- | ---------------------------------------- |
| Type | Lithium Manganese Dioxide (Li-MnO2) |
| Nominal Voltage | 3V |
| Capacity | \~2400 to 2700 mAh |
| Size | 17 mm diameter × 45 mm height |
| Chemistry | Primary (non-rechargeable) |
| Temperature Range | -40°C to +85°C |
| Typical Use Case | LoRaWAN sensors, industrial meters, etc. |
***
#### Usage in Dragino Devices
* Compatible Models: Dragino LHT65N and some variants of the LHT65S-E3 series may use the CR17450.
* Not Compatible: The standard LHT65S model has a built-in non-replaceable battery and does not use a CR17450 or any user-replaceable cell.
***
#### When to Use This Battery
Use the CR17450 battery if:
* Your Dragino model is explicitly listed as battery-replaceable.
* Your model or enclosure has a battery slot designed for CR17450 size.
* You want longer operational life and ease of replacement in-field.
---
# 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.didge.io/home/pricing/sensor-batteries.md?ask=&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.