BAT BMS App Manual: Read the Dashboard and Use Controls Safely

1. Connect BAT BMS to the correct battery

Install BAT BMS from Google Play or the App Store, enable Bluetooth, and stand close to the powered battery pack. Recent Android versions may request Nearby devices permission; older Android versions may connect Bluetooth scanning to location permission. On iPhone, allow Bluetooth access when prompted. The app cannot display meaningful data until compatible BMS hardware is awake and advertising a Bluetooth signal.

Open the device list, wait for scanning to finish, and choose the identifier that belongs to your pack. When several batteries are nearby, switch off or move away from the others if the names are unclear. After connecting, confirm that total voltage roughly matches a separate meter or the battery’s expected state. A plausible device name alone is not enough evidence that you selected the right pack.

Many Bluetooth BMS modules accept one active phone connection at a time. If BAT BMS stays on Not Connected, close other battery apps, disconnect the previous phone, wait several seconds, and scan again. Do not repeatedly toggle protection switches while the connection is unstable.

• Keep the phone within a few meters during the first connection.
• Wake the battery according to its hardware instructions.
• Confirm total voltage and temperature before opening controls.
• Take screenshots of original settings before any authorized change.

2. Read the RT dashboard without guessing

RT is the real-time monitoring screen. The exact labels vary by firmware, but the main job is consistent: show BMS measurements and operating states. Read several values together. A normal total voltage does not prove that every cell is healthy, and a 0 A current can mean the pack is idle rather than disconnected.

Watch trends instead of reacting to one refresh. Compare the highest and lowest cell voltage, temperature sensors, current direction, remaining capacity and protection indicators. If one value is impossible, refresh the connection and verify it with an independent meter before assuming the battery itself has failed.

3. Understand Charge, Discharge and AutoBalance controls

The Control screen can expose Charge Switch, Discharge Switch, AutoBalance and heating state. These are not decorative app toggles. Depending on the BMS firmware, changing them may enable or disable real power paths or balancing behavior. A disabled charge switch can prevent charging; a disabled discharge switch can remove output to a load. Never experiment while a vehicle, inverter, charger or other critical load is operating.

Before changing a switch, confirm why it is OFF. The BMS may have turned it off because of over-voltage, under-voltage, over-current, temperature or another protection. Turning it back on without correcting the cause can repeat the fault. AutoBalance depends on BMS design, thresholds and cell conditions; it is not a universal repair button for a damaged pack.

• Record the original switch state and active protection message.
• Stabilize chargers and loads when the hardware manual requires it.
• Do not override a protection repeatedly.
• If a switch immediately returns to OFF, investigate the measured condition.

4. Use the Parameter menu as a reference first

The Parameter screen can contain Basic Information, Origin Setting, Protect Param, Current Settings, Temperature Settings, Capacity Voltage and System Setting. Names may differ across firmware. Open these pages first to document what the BMS reports, not to copy values from a forum, another battery or a generic screenshot.

Protection thresholds depend on chemistry, series count, cell specification, current capability, sensor placement and the battery manufacturer’s design. A value that is reasonable for one LiFePO4 pack can be unsafe for another pack or chemistry. If the app asks for a password or confirmation, treat the change as intended for an installer, manufacturer or informed owner.

• Save screenshots of every original parameter page.
• Match chemistry and series count before reviewing voltage limits.
• Use manufacturer-approved charge, discharge and temperature limits.
• Change one documented value at a time and verify the result.
• Do not reset, calibrate or write firmware merely to clear a warning.

5. Fix common BAT BMS connection and reading problems

For a connection problem, work from simple causes to risky ones. Confirm battery power, phone Bluetooth, app permission and distance. Close other BMS apps and remove competing phone connections. Restart the app, then Bluetooth, before power-cycling battery hardware. If the device appears but fails to connect, wait for the previous session to time out and try from one phone only.

For unusual readings, separate app problems from battery problems. A stale screen may recover after reconnecting. A value that conflicts with a meter may point to calibration, wiring, sensor or firmware differences. Repeated over-temperature, cell-voltage or protection events require hardware investigation; reinstalling the app does not repair the pack.

• Not Connected: verify permission, distance, battery wake state and competing phones.
• Device visible but connection fails: close other apps and wait for the old session to release.
• 0 V or impossible values: reconnect and compare with an independent meter.
• Charge or discharge unavailable: inspect protection status, cells and temperature.
• Wrong battery selected: disconnect immediately and identify devices one at a time.

6. Follow a safe everyday BAT BMS workflow

A practical session starts with observation. Connect, confirm identity, review total voltage, cell spread, current, temperature and protections, then take a screenshot if you are tracking a change. Only open Control or Parameter pages when the monitoring data gives you a specific reason and you have the correct hardware documentation.

BAT BMS is useful for visibility, but it is not a substitute for a multimeter, insulation checks, load testing, battery service procedures or professional diagnosis. Stop using or charging a pack that is swollen, damaged, unusually hot, leaking, smelling abnormal or repeatedly entering protection. Software access should never bypass a physical safety warning.

Keep screenshots with dates when you are investigating an intermittent fault. A record of connection status, total voltage, cell spread, current, temperature and active protection can help a battery supplier understand what changed between sessions. Remove private device identifiers before sharing images publicly, and never post passwords, serial numbers or security information that could expose the hardware to unauthorized access.

• Observe before editing.
• Compare trends across several sessions.
• Keep a record of original settings and changes.
• Use independent tools for critical measurements.
• Escalate repeated protection events to the battery or BMS supplier.