Inverter and JKBMS SOC Readings Do Not Match? How to Troubleshoot and Resolve It
Estimated reading time: 6 minutes
Distribuie
When the SOC (State of Charge) shown by an inverter system differs from the SOC in the JKBMS app, first establish which device supplies each reading. A mismatch does not, by itself, prove that the inverter or the protection board is faulty.
This guide uses a 16S 304 Ah LiFePO₄ battery connected by CAN to a Victron GX in a MultiPlus-II ESS, operating in parallel with two other batteries. It explains how to separate a difference in SOC sources from a battery-monitor synchronization issue and how to investigate charging settings before considering firmware updates.
The Case: JKBMS Shows 52%, While the SmartShunt Shows 100%
During a charging test on 20 November 2026, the pack reached approximately 55.0 V, with individual cell voltages of 3.435–3.441 V and a reported end-of-charge current of approximately 2 A. JKBMS remained at 52% SOC, while the Victron SmartShunt indicated 100%.
The reported 100% value came from the SmartShunt. The information supplied does not separately establish which SOC source the GX system was displaying or using. That distinction is the first troubleshooting step.
The relevant BMS settings were:
- SOC-100% Volt: 3.410 V, reduced from 3.450 V before charging
- Cell Overvoltage Protection (OVP): 3.620 V
- Cell Overvoltage Protection Recovery (OVPR): 3.400 V
- Cell RCV: 3.460 V
- SOC-0% Volt: 2.900 V
- Balancing: enabled, starting at 3.400 V with a 0.010 V voltage difference
- Charger voltage limit: 55.0 V
1. Identify the Source of Each SOC Reading
Compare the JKBMS app reading, the battery data received through CAN, the SmartShunt reading, and the SOC shown on the inverter or GX system at the same time. Check the configured battery-monitor source using the instructions for the installed Victron system.
Also establish whether each reading represents one battery pack or the complete parallel battery bank. A single pack’s SOC should not automatically be treated as the SOC of all three packs.
If the inverter system is displaying a separate monitor’s estimate, the investigation should focus on the monitors’ measurement coverage, capacity settings, and synchronization conditions. If the displayed value is intended to come from JKBMS but does not match the relevant transmitted value, investigate communication configuration and data selection before changing battery charging parameters.
2. Check CAN Communication and Parallel Configuration
Confirm the selected CAN protocol, the communication wiring, and the parallel configuration against the documentation for the exact JKBMS model and inverter system. Check for communication alarms and verify that the displayed battery data is updating.
Record the SOC, voltage, and current of all three packs. Do not assume that a value from one pack is a combined bank value or that current divides equally between parallel batteries.
A working CAN connection does not establish that two independently calculated SOC estimates will be identical. First determine whether the difference is in data transmission or in SOC estimation.
3. Check Whether Charging Can Reach the BMS Synchronization Conditions
In this case, the clearest charging-setting mismatch is between the 55.0 V charger limit and the configured 3.460 V Cell RCV:
3.460 V × 16 cells = 55.36 V
At a pack voltage of 55.0 V, the average cell voltage is:
55.0 V ÷ 16 = 3.4375 V per cell
The reported cell voltages of 3.435–3.441 V exceeded SOC-100% Volt at 3.410 V, but remained below RCV at 3.460 V.
If the installed firmware requires RCV to be reached before starting its full-charge synchronization sequence, that condition was not met. Lowering SOC-100% Volt alone does not demonstrate that every synchronization requirement has been satisfied.
Check both the charger settings and the Victron GX charge-control settings, including any applicable DVCC voltage limit, to identify the source of the 55.0 V ceiling.
The exact roles of RCV, RCV Time, RFV, cell voltage, and charging current must be confirmed for the installed firmware. Do not assume that all JKBMS versions use the same timer trigger, hold SOC at 99%, or require the same tail-current condition.
4. Check Current Measurement and Capacity Settings
SOC estimates can diverge when devices measure different current paths, use different capacity settings, or synchronize under different conditions. A small current-measurement offset may also accumulate over time.
Confirm whether the reported 2 A is the total bank current or the current through the affected pack. If it is the total for three batteries, each pack may receive only part of it, and the split will not necessarily be equal.
Check each pack’s current reading and whether an unexpected non-zero current remains when that pack is genuinely at rest. Perform current-zero calibration only according to the model-specific procedure.
Verify that each BMS capacity setting corresponds to its own battery and that the external monitor’s capacity setting corresponds to the batteries it actually measures. Check the external monitor’s synchronization settings as well. A SmartShunt reading of 100% is comparison data, not independent proof that every parallel pack is fully charged.
5. Align Settings and Perform a Monitored Charge
- Record the existing BMS, charger, inverter, and external monitor settings.
- Confirm the exact BMS hardware and firmware and its documented full-charge synchronization requirements.
- Resolve the SOC source or communication configuration issue, if one is identified.
- Where charging settings prevent synchronization, align the charging target and BMS settings within the battery manufacturer’s permitted limits.
- Monitor each pack’s cell voltages, current, charging state, and SOC, alongside the inverter-system and external-monitor readings.
- After the supported synchronization process completes, compare the readings again and monitor their behavior during subsequent normal use.
For reference, an RCV of 3.430 V corresponds to 54.88 V for 16 cells; an RCV of 3.460 V corresponds to 55.36 V. These calculations explain the voltage relationship, not universal recommended settings.
Do not deliberately trigger cell overvoltage protection to force calibration. Do not change the configured battery capacity merely to make the displayed percentage jump. A forced 100% display does not establish that the battery is physically full.
Manual SOC adjustment and calibration functions depend on the exact app, model, and firmware. Use only the supported procedure for the installed unit.
6. Consider Firmware Only After Configuration Checks
A firmware update cannot, by itself, resolve a charging target that remains below a threshold required by the synchronization logic, nor can it correct a comparison between different SOC sources.
If the mismatch persists after configuration and measurement checks, collect screenshots and logs showing the readings at the same time. Include the exact model, hardware version, firmware version, CAN protocol, and parallel configuration of all three batteries.
The app device identifier alone is not sufficient to select firmware. Use only a package confirmed for the specific hardware. Different hardware branches may need different compatible releases, not identical version numbers.
For PC diagnostics, PB units use a USB-to-RS485 adapter connected to the interface board’s RS485 port. B/BD units use a USB-to-TTL adapter connected to the BMS GPS port. These connections are not interchangeable.
Conclusion
To resolve an inverter-system and JKBMS SOC mismatch, first identify the source and scope of each reading. Then check communication, current measurement, capacity settings, and full-charge synchronization conditions.
In this example, JKBMS showed 52% while the SmartShunt showed 100%, and the reported cell voltages remained below the configured RCV. That charging mismatch is an important lead, but its effect must be confirmed against the installed firmware’s synchronization logic.
The goal is not simply to make two percentages match. It is to ensure that the system uses the intended SOC source and that each monitor is correctly configured and synchronized.