> For the complete documentation index, see [llms.txt](https://emotiv.gitbook.io/mn8-user-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://emotiv.gitbook.io/mn8-user-manual/getting-started/charging-your-mn8.md).

# Charging Your MN8

Your MN8 is charged and tested before shipping — so you can start using it straight away.&#x20;

### Charging the battery

To optimize the use of your MN8, we recommend that you fully charge it before use.&#x20;

If the multifunctional LED does not glow when you turn your headset ON, it requires charging.

![](https://lh3.googleusercontent.com/U26VxZGx0dRor-XivvIZafjpnTcouUz22iNNXrC83QuxwD65h5DVoCGqtoI0jkI9itcMKFPyIh49Ntkq44aFqagV0aON6ZTMHNSyii0PZ3-WbuKFxlJdxKWsKaU4eA0rGwaxDT3BR-W0b0CXAvHWjTc)

To charge the battery:

1. Plug the USB-B charging cable into the USB port at the bottom (shown above) of your MN8.
2. Then, connect the other end of the USB charging cable to a power outlet or PC/Mac.&#x20;
3. Charging can take up to two hours (depending on the remaining capacity of the lithium polymer battery). &#x20;

If the headset is unused for a long period of time, the battery will become heavily depleted of charge. If this happens, you may need to charge your MN8 for 24-hours.&#x20;

If you have any issues charging your MN8, please contact the [EMOTIV Support team](https://www.emotiv.com/contact-support/).

### Charging behavior

| **Charging**                                                                                                                                                                                   | **Charging Complete**                                                                                                                                                                          |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ![](https://lh6.googleusercontent.com/UTodEZH_rAwDfIpmnx_ECAkt9XAijgw-tzh0ot-h6dT34hfK8y2ruc8fmQbNWYMH2mOmf4Ll1g87abLNACbQwg2_Cbu9jIhB_w8Wm_fllk4ObjntxTnYoiBJRj0xTd3MKHlB6Pmd0DTtxCpCwRUov30) | ![](https://lh5.googleusercontent.com/StZcZmi2_mlIhUhcmA6NjkxLRfik7mE5xpPM7gwW-q9qOHI6oOUuUXJ2hgI2ZKnYWwm4Z0utHYFr5JMctNczE4oVbIkCgf58Z7ytIRTkJKwp4QpS3yTGvViyc9uVPxHsk8y6pdi35i7MTRhoLLuz4b4) |
| When MN8 is charging the red LED is displayed.                                                                                                                                                 | When MN8 is fully charged the LED turns green.                                                                                                                                                 |


---

# 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://emotiv.gitbook.io/mn8-user-manual/getting-started/charging-your-mn8.md?ask=<question>&goal=<endgoal>
```

`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.
