> For the complete documentation index, see [llms.txt](https://nxp.gitbook.io/rddrone-bms772/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nxp.gitbook.io/rddrone-bms772/software-guide-nuttx/first-time-software-configuration-of-the-bms.md).

# First time software configuration of the BMS

It is highly recommended that you check each parameters in [Parameters of the BMS](/rddrone-bms772/software-guide-nuttx/untitled-1.md) and make sure to configure each parameter. Use "bms get all" to get each parameter and it's value, so you could configure each one for your battery. \
\
Some parameters you would like to configure are:

* battery-type (Which battery type do you have? 0=LiPo, 1=LiFePO4, 2=LiFeYPO4, 3=NMC, 4=Sodium-ion)
  * This will change the under- and over-voltage, storage voltage, nominal voltage and the OCV curve it uses to correct the state of charge
* n-cells (the amount of cells of the battery) \[3 .. 6]
* sensor-enable (to enable the battery temperature sensor) \[0=disable, 1=enable]
* a-rem (the remaining capacity) \[Ah]
  *  the BMS does a guess on what the remaining charge is based on a OCV(open cell voltage)/SoC (state of charge) table from one specific battery, but every battery is different.
    * It is advisable to insert the correct OCV/SoC table for the battery.
* a-factory (the factory capacity of the battery) \[Ah]
  * What is the capacity stated on the battery?
* a-full (the full charge capacity of the battery) \[Ah]
  *  while charging, the BMS will calculate this based on a-rem
  * If unknown, set to the same value as factory capacity after the next step
* model-name (the name of the battery) 
* i-charge-full (the end of charge current of the battery (could be 10% from i-charge-max)) \[mA]
* i-charge-max (the maximum charge current) \[A]
* i-peak-max (the maximum peak current threshold \[A])


---

# 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://nxp.gitbook.io/rddrone-bms772/software-guide-nuttx/first-time-software-configuration-of-the-bms.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.