EV Battery Health Community Profiles
Open user-to-user exchange of vehicle-specific OBD2 battery diagnostic profiles and real-vehicle test information.
OPEN COMMUNITY EXCHANGE — NOT A PRE-APPROVED PROFILE CATALOG
Users may publish EV Battery Health profile JSON, Profile Help information, compatibility reports and real-vehicle test results directly in the comments. Posts are not routinely pre-reviewed or endorsed by Catalyst Fix Pro. Publication here does not make a profile FIELD_TESTED or VERIFIED.
Users may publish EV Battery Health profile JSON, Profile Help information, compatibility reports and real-vehicle test results directly in the comments. Posts are not routinely pre-reviewed or endorsed by Catalyst Fix Pro. Publication here does not make a profile FIELD_TESTED or VERIFIED.
Where to start: first check the app's built-in profile list. If no suitable profile exists, use New Vehicle – Profile Help. Use this Community Profiles page to share USER profiles, revisions and real-vehicle evidence — not to bypass the app's read-only safety checks.
84 BUILT-IN EV PROFILES — CURRENT STRATEGY
EV Battery Health and EV Battery Health Lite currently include 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 are included only when the SOH diagnostic path is sufficiently defined for ordinary compatible OBD2/ELM access.
- ODO, Delta and other optional values are enabled only when vehicle-specific evidence supports them.
- Built-in does not automatically mean VERIFIED. A built-in profile may remain EXPERIMENTAL until sufficient real-vehicle evidence has been collected.
- The same platform or model name does not automatically imply the same diagnostic profile. Battery capacity, generation, ECU software and market variant can matter.
WHY PROFILES ARE NEEDED
EV battery diagnostics are not universal. Different manufacturers, models, model years, battery versions and ECU software can use different CAN addressing, diagnostic requests, response layouts and formulas. A profile lets EV Battery Health use a vehicle-specific read-only method instead of assuming that one universal SOH PID exists for every EV.
CAPABILITIES VARY BY VEHICLE
A profile may support only some of the following:
- Battery SOH
- Capacity-related values
- Odometer (ODO)
- Cell/module voltage difference (Delta)
- Individual cell/module voltages
- Battery temperatures
- BMS diagnostic information
- Other read-only battery parameters exposed by the vehicle
Important: missing data does not automatically mean an app or adapter fault. Some vehicles simply do not expose the same parameters through OBD2.
PROFILE CLASSIFICATION USED BY EV BATTERY HEALTH
Origin, validation and derivation are separate. A profile's source does not determine its validation level.
| Origin | Meaning |
|---|---|
| BUILT-IN | Shipped with EV Battery Health and maintained as part of an app release. Built-in does not automatically mean verified. |
| COMMUNITY | Obtained or shared through Community Profiles or another identifiable community source. COMMUNITY is provenance, not an EVBH approval badge. |
| USER | Created locally, produced through Profile Help, or imported without identified community provenance. |
| Official validation | Meaning |
|---|---|
| EXPERIMENTAL | Technically plausible and accepted by the app's safety/schema checks, but the specific vehicle/battery variant does not yet have sufficient EVBH field evidence. |
| FIELD_TESTED | A successful EV Battery Health test exists for the specific vehicle/battery variant with usable evidence such as profile/version, addressing, TX/RX data, formula/result and diagnostic context. |
| VERIFIED | FIELD_TESTED requirements are met, the result has been repeated, and it has also been independently confirmed. This is EV Battery Health verification, not manufacturer certification. |
| Derivation | Meaning |
|---|---|
| DIRECT | The diagnostic configuration was created directly for the specific vehicle/model/variant. |
| FAMILY_DERIVED | The profile uses a diagnostic method already defined for the same technical/BMS family. |
| COMMUNITY_DERIVED | The original diagnostic configuration is based directly on community/public evidence. |
| UNKNOWN | The technical derivation cannot be established reliably. |
Official validation path: EXPERIMENTAL → FIELD_TESTED → VERIFIED. A user-posted JSON file or comment cannot grant itself an official FIELD_TESTED or VERIFIED status. Community publication does not change validation automatically.
NEW VEHICLE — PROFILE HELP & MULTI-STAGE CONVERGENCE
If EV Battery Health does not yet have a suitable profile for a vehicle, use New Vehicle – Profile Help in the app. The workflow can collect vehicle details, adapter/protocol information and an optional read-only discovery snapshot, then export a Help Request TXT/JSON package for analysis.
TYPICAL CONVERGENCE WORKFLOW
- Run 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 EV Battery Health.
- 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, when needed, a later USER revision.
- Import the revised profile and repeat the real-vehicle test.
- Continue only when each new revision is supported by new real diagnostic evidence, until the result is stable and reproducible.
No automatic AI upload: EV Battery Health does not automatically upload Profile Help or diagnostic packages to ChatGPT, Claude, Gemini or another AI service. Export and sharing are initiated by the user.
Do not invent missing technical data. If there is not enough evidence for a manufacturer-specific header, PID/DID, response layout or formula, it should remain unknown until better evidence is available.
Safety boundary: profile convergence is intended only for ordinary compatible read-only OBD2/ELM access. Stop if SecurityAccess, seed/key procedures, ECU coding, write services, gateway unlocking, encryption bypass, actuator control or manufacturer-only authorization would be required.
A newly created/imported candidate should be treated as EXPERIMENTAL until real-vehicle evidence supports a higher official validation level.
USER PROFILE REVISIONS
USER profiles have their own revision history. Editing a USER profile can create a new revision rather than overwriting the previous one.
- A built-in profile edited by the user becomes a separate USER v1 line; the built-in original remains unchanged.
- Editing USER v1 can create USER v2; editing USER v2 can create USER v3, and so on.
- profileVersion is a diagnostic-profile configuration revision. It is not a trust or verification level.
- Import/export preserves supported USER profile revision information.
- A USER profile never becomes BUILT-IN, FIELD_TESTED or VERIFIED merely because its version number increases.
ADAPTER GUIDANCE FOR COMMUNITY TESTING
Real-vehicle evidence is most useful when the exact OBD2 adapter is reported together with the vehicle and profile revision.
- 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 also work, depending on firmware quality and command support.
- Avoid very cheap unbranded ELM327 clones when possible. Some may reject commands, truncate long or multi-frame responses, freeze during larger transfers or implement only part of the expected ELM command set correctly.
- If adapter behavior is uncertain, run the app's Adapter Compatibility test before relying on vehicle-profile results.
READ-ONLY SAFETY PRINCIPLE
Community profiles must remain read-only. EV Battery Health validates imported profile content and is designed to reject commands outside its permitted read-only diagnostic policy. Publishing a JSON file on this blog does not bypass the application's own safety validation. An experimental profile must never be treated as a guarantee of battery-health accuracy.
WHAT MAY BE POSTED HERE
- EV Battery Health USER profile JSON, including a specific profile revision when relevant.
- New Vehicle / Profile Help information and convergence evidence.
- Real-vehicle test results, Technical Diagnostic Reports and other diagnostic evidence.
- Compatibility reports for a specific vehicle, battery variant or OBD2 adapter.
- Comparisons between USER v1, v2, v3 or later revisions when each revision is backed by new real evidence.
- Technical questions and discussion directly related to EV Battery Health profiles.
Open posting policy: Community Profiles is an open user-to-user exchange. Catalyst Fix Pro does not promise routine review, validation or replies to individual posts. Obvious spam, automated/bot posts, advertising, malicious or deceptive links, and discussion unrelated to EV Battery Health profiles may be removed when noticed. Removal for spam or off-topic content is moderation of the discussion space, not technical approval or rejection of a vehicle profile.
PRIVACY WHEN POSTING
Please do not publish full VIN numbers, registration numbers, personal addresses, passwords, account information, full Bluetooth/MAC addresses or other sensitive personal information. Review screenshots and exported files before posting them publicly.
HOW TO SHARE A PROFILE OR TEST RESULT
- Click “No comments” below this post, or open the post itself.
- Scroll to “Post a Comment”. This blog currently allows comments from users signed in with a Google account.
- Choose what you are sharing: Profile Help / new vehicle, profile JSON, or real-vehicle test result.
- Include vehicle make, model, model year/variant, battery capacity/version and the OBD2 adapter used when known.
- For a real-vehicle test, include the EV Battery Health profile/profile version and which values were read successfully (for example SOH, ODO, Delta or other supported values). Diagnostic evidence is especially useful when available.
- If sharing a revised USER profile, state what changed from the previous revision and what new real-vehicle evidence justified the change.
- To share a profile, paste the complete JSON content as plain text between the BEGIN and END markers below.
- Publish the comment. No separate Catalyst Fix Pro approval is required for the comment to be a community post.
If the comment form does not open: browser privacy settings or blocked third-party cookies may prevent Blogger/Google sign-in. Allow the required Blogger/Google cookies or try another browser.
PROFILE JSON STRUCTURE REFERENCE — EXAMPLE ONLY
EXAMPLE ONLY — NOT A REAL VEHICLE PROFILE.
This example shows the field structure of the current EV Battery Health schemaVersion 2 profile export. It intentionally contains placeholder or invalid values and must not be used for vehicle diagnostics. Replace placeholders only with documented, vehicle-specific evidence. Never invent PID/DID, ECU headers, expected response prefixes or formulas. The EV Battery Health importer performs the final schema and read-only safety validation.
This example shows the field structure of the current EV Battery Health schemaVersion 2 profile export. It intentionally contains placeholder or invalid values and must not be used for vehicle diagnostics. Replace placeholders only with documented, vehicle-specific evidence. Never invent PID/DID, ECU headers, expected response prefixes or formulas. The EV Battery Health importer performs the final schema and read-only safety validation.
{
"profile": {
"addressingType": "<ADDRESSING_TYPE>",
"canBitrate": "<CAN_BITRATE>",
"canIdType": "<CAN_ID_TYPE>",
"capacityBasis": "<CAPACITY_BASIS>",
"deltaEnabled": false,
"deltaOperation": "NONE",
"diagnosticFamily": "<TECHNICAL_FAMILY>",
"elmInitCommands": "<DOCUMENTED_READ_ONLY_ELM_INIT_COMMANDS>",
"headerStrategy": "<HEADER_STRATEGY>",
"id": 0,
"isBuiltIn": false,
"make": "<MAKE>",
"model": "<MODEL / BATTERY VARIANT>",
"nominalCapacityKwh": 0.0,
"odoEnabled": false,
"powertrainType": "<POWERTRAIN>",
"profileVersion": 1,
"sohEquation": "<DOCUMENTED_SOH_FORMULA>",
"sohExpectedPrefix": "<DOCUMENTED_EXPECTED_RESPONSE_PREFIX>",
"sohHeader": "<DOCUMENTED_TX_HEADER>",
"sohInitCommands": "<DOCUMENTED_READ_ONLY_ELM_INIT_COMMANDS>",
"sohMeasurementSource": "<SOH_MEASUREMENT_SOURCE>",
"sohMinPayloadBytes": 0,
"sohPid": "<DOCUMENTED_READ_ONLY_PID_OR_DID>",
"sohRxHeader": "<DOCUMENTED_RX_HEADER>",
"sohValidMax": 0.0,
"sohValidMin": 0.0,
"sourceLabel": "<SOURCE / EVIDENCE DESCRIPTION>",
"sourceUrl": "<OPTIONAL_PUBLIC_SOURCE_URL>",
"verificationStatus": "USER"
},
"schemaVersion": 2
}
profileVersion note: the JSON example uses
profileVersion: 1 only as a structure example. For a real USER profile, keep the revision value produced by EV Battery Health import/export. Do not change only the version number and call it a new technical revision; a real revision should be backed by a real configuration change and new evidence.Why the example is intentionally non-working: placeholder values such as
<DOCUMENTED_TX_HEADER>, <DOCUMENTED_READ_ONLY_PID_OR_DID> and <DOCUMENTED_SOH_FORMULA> are not real diagnostic data. A user should start from an actual EV Battery Health export/Profile Help result and documented evidence rather than turning this template into a guessed profile.Recommended profile/test comment format:
Type: Profile JSON / Profile Help / Real-vehicle test
Vehicle: <MAKE / MODEL / VARIANT>
Model year: <YEAR OR RANGE>
Battery: <BATTERY VARIANT / CAPACITY>
Adapter: <OBD2 ADAPTER>
Profile revision: <USER v1 / v2 / v3 / ...>
Previous revision: <OPTIONAL — IF THIS IS A REVISION>
What changed: <OPTIONAL — TX/RX/DID/PREFIX/FORMULA/ODO/DELTA/etc.>
New evidence: <WHAT NEW REAL-VEHICLE EVIDENCE JUSTIFIED THE REVISION>
Result: <WHAT WAS ACTUALLY READ OR WHAT FAILED>
Validation note: User-submitted result; publication here does not grant official FIELD_TESTED or VERIFIED status.
--- EV BATTERY HEALTH PROFILE JSON BEGIN ---
<PASTE THE COMPLETE EV BATTERY HEALTH EXPORTED PROFILE JSON HERE>
--- EV BATTERY HEALTH PROFILE JSON END ---
Phone copy tip: tap and hold inside the JSON text, expand the selection handles from the BEGIN marker through the END marker, then choose Copy. In EV Battery Health open Import Profile and choose Paste JSON from clipboard.
Important: whenever possible, share the complete JSON exported by EV Battery Health rather than manually constructing JSON from the structure example above. Do not intentionally alter technical fields when reposting another user's profile. If Blogger refuses a very long comment, a public link to the JSON file may be posted instead. Plain-text JSON is preferable to screenshots because it can be inspected and imported more reliably.
CONTACT
For app bugs, security concerns or issues that should not be posted publicly:
📧 catalystfixpro@gmail.com
TEST ONLY — COMMENT CHECK
ReplyDelete