> For the complete documentation index, see [llms.txt](https://docs.freeflysystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.freeflysystems.com/ecosystem/power/superlight-batteries.md).

# SuperLight Batteries

Freefly-designed smart batteries

![](https://2546427254-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWXREyAKYAeQJ4gfg2SPg%2Fuploads%2Fgit-blob-4ce62a628e031d4fbbe43a6d2d68a8a8355c118e%2Fsl4sl8-wiki-cropped.jpg?alt=media)

SuperLight Lithium-ion batteries are designed and manufactured by Freefly. They work with any device that uses the Freefly Open Battery Interface: Astro today, others coming soon.

Every pack has a built-in Battery Management System (BMS) and OLED screen. The BMS manages discharging and charging without balance leads, and applies many protections during charge and discharge to improve safety, diagnostics and performance. They also include a critical flight mode which limits protections in order to prevent false power cutoff while airborne. The OLED screen gives detailed information about pack status, like state of charge, voltage, current, temperature, life time statistics, etc. The USB-C port can charge devices (such as phones, computers such as MacBookPro, etc) that support USB Power Delivery from 5V up to 20V with 60W.


---

# 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.freeflysystems.com/ecosystem/power/superlight-batteries.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.
