EV Battery Health

OBD2 battery-health diagnostics — paid, ad-free edition.

Get it on Google Play Privacy Policy Community Profiles

BATTERY HEALTH DIAGNOSTICS FOR ELECTRIFIED VEHICLES

EV Battery Health is a read-only, profile-based OBD2 diagnostic tool designed to obtain the maximum battery-health information that a supported vehicle makes available through ordinary compatible OBD2 adapters.

The app does not assume that one universal SOH PID exists for every EV. Each vehicle profile defines the addressing, requests, validation rules, formulas and supported measurements for that vehicle family.

CORE PRINCIPLE

Available data depends on the vehicle. A profile may expose only SOH, while another vehicle may also provide odometer, cell/module voltage difference, individual cell voltages, battery temperatures, capacity-related values or BMS diagnostic information. The user interface should show only the capabilities that are actually supported by the selected profile.

CORE FEATURES

Battery SOH: reads or calculates State of Health from vehicle-specific OBD/UDS data where supported.
Capacity context: shows battery capacity together with the profile's declared basis (gross, net, nominal, published or usable where known).
Optional measurements: ODO, Delta, temperatures, cell voltages and other values only when the selected vehicle/profile supports them.
Vehicle profiles: built-in and USER/custom imported profiles with strict read-only validation.
Profile revisions: USER profile revisions can be preserved instead of overwriting the previous diagnostic configuration.
Technical diagnostics: local diagnostic sessions, raw responses and troubleshooting information.
Local processing: normal vehicle diagnostic data is processed on the Android device.

84 BUILT-IN EV PROFILES

The current catalog contains 84 built-in vehicle/battery diagnostic profiles. A different battery capacity or diagnostic variant may be represented by a separate profile even when the make and model name are the same.

The built-in catalog follows a conservative read-only, SOH-first strategy.
Built-in profiles focus first on a defined SOH diagnostic path, response structure and formula.
ODO, Delta and other optional measurements are enabled only when vehicle-specific evidence supports them.
A built-in profile is not automatically the same thing as a fully verified profile; a profile may remain experimental until sufficient real-vehicle validation has been completed.

USER PROFILES & REVISION HISTORY

Custom profiles created, edited or imported by the user remain USER profiles. They do not automatically become built-in or verified.

Editing a USER profile can create a new revision rather than silently overwriting the previous revision.
Profile revision information is preserved during supported import/export workflows.
This allows earlier and later diagnostic configurations to be compared during real-vehicle testing.

NEW VEHICLE — PROFILE HELP & MULTI-STAGE CONVERGENCE

If a suitable built-in profile does not exist, New Vehicle – Profile Help can collect a read-only diagnostic evidence package for profile development.

TYPICAL CONVERGENCE WORKFLOWRun New Vehicle – Profile Help and export the Help Request / diagnostic evidence.
The user may optionally upload the exported data to an AI assistant such as ChatGPT, Claude or Gemini.
Create an initial USER v1 diagnostic profile and import it into the app.
Test the profile on the real vehicle and save the Technical Diagnostic Report / raw evidence.
Analyse the new evidence and refine the profile into USER v2 or a later revision when necessary.
Import the revised profile and repeat the real-vehicle test.
Continue only when each revision is supported by new real diagnostic evidence, until the result is stable and reproducible.

No diagnostic package is automatically uploaded to ChatGPT, Claude, Gemini or any other AI service. Export and sharing are initiated by the user.

SAFETY BOUNDARY FOR PROFILE CONVERGENCE:

The workflow is intended only for ordinary compatible read-only OBD2/ELM access.
Do not use profiles that require SecurityAccess, seed/key procedures, ECU coding, write services, gateway unlocking, encryption bypass, actuator control or manufacturer-only service authorization.
If a supported result cannot be reached without such procedures, the convergence process should stop rather than bypass vehicle security.

COMMUNITY PROFILES

EV Battery Health Community Profiles is intended for sharing USER profiles, test evidence and profile-development information. Community or imported profiles should be treated as user-provided diagnostic configurations until they have been independently validated on the exact vehicle/battery variant.

Open EV Battery Health Community Profiles

COMPATIBILITY & CONNECTION

Compatible ELM327/ELM329/STN-style OBD2 Bluetooth adapters are required for actual vehicle diagnostics.
Bluetooth Classic / RFCOMM and Bluetooth LE / GATT are supported where the adapter and Android device support the required transport.
Vehicle-specific 11-bit or 29-bit CAN addressing and manufacturer-specific read-only UDS requests may be used by profiles.
Recommended / well-suited examples: Vgate vLinker MC+, Vgate vLinker FS, Vgate iCar Pro BLE 4.0 and Veepeak BLE.
A genuine or well-implemented ELM327 Classic adapter can work, but compatibility depends on firmware quality and command support.
Avoid very cheap unbranded clone adapters when possible. Some may reject commands, truncate long or multi-frame responses, freeze during larger transfers or implement only part of the ELM command set correctly.
If connection quality is uncertain, run Adapter Compatibility before relying on diagnostic results.

HOW IT WORKS

Select a built-in or custom vehicle profile.
Select a compatible OBD2 adapter.
Confirm the vehicle state when requested.
The app initializes the adapter and sends read-only diagnostic requests.
Responses are validated, parsed and converted using the profile rules.
Supported results are displayed together with diagnostic status.
Technical session data can be retained locally and exported by the user.

IMPORTANT LIMITATIONS:

Not every vehicle exposes SOH or the same supporting battery data through OBD2.
Protocols can vary by model year, battery version, ECU software and market.
Custom/community profiles may be experimental or incorrect until validated on real vehicles.
Displayed values are informational and are not a replacement for professional high-voltage battery inspection.
The intended workflow is read-only; the app is not intended for ECU flashing, coding, DTC clearing or repair procedures.