JK BMS and Victron: CAN Setup and Communication Troubleshooting
Follow a practical JK BMS–Victron communication check: identify the GX path, confirm the protocol and cable, then diagnose missing or incorrect battery data.
In this article
To connect a suitable JK BMS to a Victron MultiPlus-II system, first confirm the BMS hardware and firmware, then match its CAN profile, cable and GX port configuration. The battery communication link normally goes to a compatible GX device; it is not a CAN cable plugged into the MultiPlus-II VE.Bus socket.
This guide helps you identify the connection path and diagnose missing battery data. For the wider purchase decision, use our JK BMS inverter compatibility checklist.
Quick answer: what needs to match?
- A JK inverter BMS with a documented Victron CAN profile for its exact version.
- A compatible Victron inverter/charger and GX arrangement.
- The correct battery-to-GX cable, verified at both ends.
- A GX CAN profile matching the documented battery rate.
- Battery data and operating limits that can be checked during commissioning.
A protocol name in an app is a starting point for configuration, not proof that every battery, firmware and inverter combination has been tested.
Start with the communication path
JK BMS CAN → compatible GX CAN interface → Victron system control. For a MultiPlus-II arrangement, the inverter/charger also has its own documented connection to GX. Keep this communication path separate from the battery's DC power wiring.
Do not treat Ethernet, VE.Bus, RS485 and CAN sockets as interchangeable because they use similar connectors. Label the intended ports before choosing a cable. A MultiPlus-II model name alone does not establish which GX hardware or connection accessories are present.
What our supplier protocol reference establishes
Our supplier-provided protocol reference lists Victron MultiPLUS-II, CAN, 500K and Victron_CAN. It identifies a configuration to investigate; it does not record the complete BMS hardware, firmware, GX model, cable pinout or installation test.
| Item | Working reference | Check on your equipment |
|---|---|---|
| Inverter family | MultiPlus-II | Full model, battery-voltage range and GX arrangement |
| Battery interface | CAN | Exact JK board and communication-port definition |
| Protocol name | Victron_CAN | Matching profile in the installed firmware |
| CAN rate | 500 kbit/s in the supplier reference | Supported BMS-Can profile on the selected GX port |
| Menu number | Version-dependent | Use the profile name and applicable instructions |
Use Victron_CAN as the name to verify. Do not choose a profile just because an online tutorial uses a particular number. Request the profile mapping for your BMS version if the app labels differ.
Example: JK-PB2A16S20P, MultiPlus-II and Cerbo GX
This is an equipment-check example, not a claim that a particular firmware combination has been commissioned. If these are the devices in your build, prepare the following record before choosing the cable or profile.
| Equipment | Record and confirm |
|---|---|
| JK-PB2A16S20P | Board label, hardware/firmware, available Victron profile, CAN port definition and battery configuration |
| MultiPlus-II | Complete model, DC voltage range, firmware and documented connection to the GX system |
| Cerbo GX | Exact generation, Venus OS version, selected CAN port and available CAN profiles |
| Communication cable | Both-end pinout and cable identity matched to these exact devices; Type A/B is not assumed |
| Battery assembly | Cell count and model, current limits, protection settings and whether the bank contains multiple modules |
Compare the JK PB Series BMS options against this record. Send the board label, port photos and inverter/GX model to AmpBird if a required field is unknown, so the discussion addresses the actual configuration.
1. Record the equipment before changing settings
Save the BMS model, hardware revision, firmware and existing settings. Record the MultiPlus-II and GX models, Venus OS version, selected CAN interface and cable part number or wiring record. For a parallel bank, add each module's model and communication arrangement.
Ask the supplier to resolve missing port or protocol information before commissioning. Keep a copy of the starting configuration so a diagnosis does not depend on remembering which setting changed.
2. Verify the cable and GX CAN profile
Victron documents Type A, Type B and other cable arrangements in its CAN-bus BMS cable manual. Cable selection depends on the battery connection, so confirm the JK pin definition before ordering or making a lead. This guide does not assign a universal Type A or Type B cable to all JK boards.
The GX connection manual distinguishes normal VE.Can operation from BMS-Can profiles. For the supplier-listed 500 kbit/s combination, check the selected port's BMS-Can setting. Available ports and menus depend on the GX generation. Follow the applicable GX and battery instructions for termination; do not mix networks with incompatible profiles on one bus.
On GX versions with configurable VE.Can ports, use Remote Console: Settings → Connectivity → the selected VE.Can port → CAN-bus Profile. For the supplier-listed 500 kbit/s arrangement, confirm the matching BMS-Can profile on that port. Check the exact GX interface and Venus OS version; a rate in the supplier table alone is not a configuration instruction for every GX generation.
Use the equipment's isolation procedure before moving cables. Verify an unpowered cable against the documented pinout rather than testing guesses on live communication ports.
3. Select the documented JK profile
In the settings for the identified JK board, find the inverter communication profile and confirm the name matches the supplier's Victron reference. Apply any restart procedure required by that firmware. Change one setting at a time and record the result.
Do not change cell protection thresholds or disable alarms to make a communication link appear to work. Communication configuration and battery operating limits are separate checks.
4. Check more than the battery icon
Use the GX battery-device view to record voltage, current, SOC, alarms and available charge/discharge limits. Compare the readings with the BMS at the same time. Observe the system under an approved commissioning procedure, including a communication-loss test defined for that installation.
Victron's DVCC documentation explains charge-voltage, charge-current and discharge-current limits. A visible SOC value does not establish that these limits are valid or that every charger is controlled. Confirm DVCC requirements and control behavior for the exact system before loading it.
Record the expected result after each check
| Check | Expected observation | If it is missing or inconsistent |
|---|---|---|
| Device discovery | The intended battery device appears in the GX device list | Review BMS activation, CAN port, cable and profile |
| Battery readings | Voltage, current direction and SOC are available and plausible against simultaneous BMS readings | Check the profile mapping, selected SOC source and bank/module scope |
| Alarms and limits | Supported alarm status and CVL/CCL/DCL are available for the documented integration | Review firmware support and charge-control requirements before treating integration as complete |
| Result | Record device discovery separately from the installer's control verification | A battery icon or changing SOC alone does not verify every control function |
JK BMS not showing in GX: a diagnostic order
| Symptom | Check next |
|---|---|
| No battery device | BMS power/activation, correct CAN port, documented cable and matching GX profile |
| Battery appears but data is implausible | Selected profile, firmware mapping and comparison with BMS readings |
| Data disappears intermittently | Connectors, cable condition, termination and recorded communication alarms |
| SOC differs between screens | Selected SOC source, refresh timing and whether both displays represent the same bank |
| Battery visible but charging is restricted | BMS alarms, received operating limits and system charge-control settings |
Keep photographs and timestamps for each result. A repeatable symptom with unchanged settings is more useful than a series of resets that erase the starting condition.
Parallel batteries need their own connection plan
Do not copy a master address or daisy-chain layout from a different JK revision. Confirm addressing, inter-module ports, supported module count and how aggregate limits are calculated. Establish the documented single-module configuration first where the commissioning procedure permits, then validate the complete bank.
Before ordering a JK BMS or DIY kit
Review the JK PB Series BMS options and DIY battery kits against your cell count, current requirement and communication plan. A listed protocol does not establish the power rating of the complete battery.
For a configuration enquiry, send AmpBird the BMS model and versions, communication-port photos, inverter/GX model, cable details and the symptom or planned build. This allows the discussion to focus on the actual equipment.
Frequently asked questions
Does the supplier list mean Victron has certified this JK battery?
No. Supplier protocol support and Victron testing or approval are different claims. Consult Victron's battery compatibility guidance and the battery supplier's support scope.
Can I connect the BMS CAN lead to a VE.Bus socket?
No. Identify the GX CAN interface and the separate inverter connection from the applicable diagrams. Connector shape is not a wiring instruction.
Which numeric JK protocol should I select?
Select the documented Victron profile for the installed firmware. Verify its name and mapping rather than copying a number from another app version.
What if communication works but SOC still looks wrong?
Check the selected SOC source and battery measurement history. Follow our JK BMS SOC troubleshooting sequence for an unexpected percentage, or use the current-measurement guide for the monitoring layout.
