> 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/astro/maintenance/standard-maintenance-procedures/sl8-astro-battery-connectors.md).

# SL8/Astro Battery Connectors

**We recommend all Astro pilots routinely check the aircraft and SL8 battery connectors for signs of damage, debris, or excessive wear.**

## Inspect Connectors

* Inspect the battery connectors on Astro for melted plastic and / or solder at the base of the power pins (they are located in the center).
  * **Do not fly Astro if the connector shows evidence of electrical damage** and contact Freefly Support for further guidance .
* Inspect all SL8 battery connectors for melted plastic, debris, or dirt.
  * **Do not fly any SL8 battery if the connector shows evidence of electrical damage** and contact Freefly Support for further guidance.
* Debris and dirt can be gently removed with compressed air from the SL8 connector
* Astro aircraft side connectors can be cleaned with compressesd air or with a toothbrush and 99% Isopropyl Alcohol

{% hint style="info" %}
Some wear is normal and expected, particularly where the Astro's ground pins make contact with the batteries.
{% endhint %}

{% hint style="danger" %}
Never remove debris from the battery with tweezers. If debris cannot be removed from the battery with compressed air, the battery may need to be returned to Freefly or disposed of.
{% endhint %}

<figure><img src="https://2177404587-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8dwrGJhxGd9cIvsStziq%2Fuploads%2F3ZsAsgXb8KuAe21DLipb%2Funknown.jpeg?alt=media&amp;token=fc3b6657-b533-4172-84ea-02cd361cb762" alt="Scorch marks on the power pin connectors" height="468" width="624"><figcaption><p>Evidence of electrical damage (scorch marks) on the center power connectors</p></figcaption></figure>

<img src="https://2177404587-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8dwrGJhxGd9cIvsStziq%2Fuploads%2FIfivk9IcySS7Fb02Z946%2Funknown.png?alt=media&amp;token=3aec28bc-2790-4ca2-aa38-9ae38a5378ac" alt="Eveidence of electrical damage (melted plastic) on the center power connectors and pins" height="264" width="625">


---

# 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/astro/maintenance/standard-maintenance-procedures/sl8-astro-battery-connectors.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.
