Victron System Commissioning: A Practical Workflow for Standard Systems

Victron System Commissioning: A Practical Workflow for Standard Systems

This quick guide outlines a practical commissioning workflow for standard Victron energy systems. It focuses on configuration and setup — not system design or physical wiring.

It is intended as a fast reference for common scenarios, with the primary use case being off-grid residential systems, and notes included where on-grid or ESS systems differ.

It applies to systems using:

  • Victron MultiPlus or Quattro inverters
  • Victron MPPT solar chargers
  • SmartShunt or BMV battery monitoring
  • Cerbo GX (or equivalent GX devices)
  • Common managed batteries such as Discover, PowerPlus, Pylontech, and similar

1. Commission Battery Monitoring (SmartShunt / BMV)

If using a managed battery (e.g. Discover, Pylontech), state of charge (SOC) is provided by the BMS and a shunt is not required.

1.1 Connect to the SmartShunt

  • Use VictronConnect
  • Connect via:
    • Bluetooth (phone or tablet), or
    • VE.Direct cable (laptop)

1.2 Set Core Battery Parameters

Navigate to Settings → Battery.

Set the following:

  • Battery capacity

Enter the exact Ah value (e.g. Discover Helios = 314 Ah)

  • Charged voltage
    • 12 V system: 13.5 V
    • 24 V system: 27.0 V
    • 48 V system: 54.0 V

Do not set this to absorption voltage

  • Charged detection time

Default: 3 minutes

  • Tail current

Default: 4% of battery capacity

This allows SOC to reset correctly under real solar conditions and prevents drift. 

1.3 Set Discharge Floor (Important)

  • Set a discharge floor (typically 10–50%)
  • This:
    • Hides unsafe capacity from end users
    • Prevents misuse and deep discharge

1.4 Leave Advanced Values Unchanged

Do not change the following unless instructed by the manufacturer:

  • Charge efficiency factor
  • Peukert exponent

2. Commission MPPT Solar Chargers

2.1 Connect via VictronConnect

  • Phone / tablet: Bluetooth
  • Laptop: VE.Direct to USB

2.2 Set Battery Voltage (Critical)

Before energising the solar array:

  • Power the battery first
  • Manually set the correct battery voltage (12 / 24 / 48 V)

This prevents MPPT lock-out conditions.

2.3 Set Battery Profile

  • Select Lithium preset
  • Edit values to match manufacturer specifications:
    • Absorption voltage
    • Float voltage
    • Absorption time
    • Tail current (if specified)

Even in closed-loop systems, these open-loop values must be entered as a fallback.

2.4 Expert Settings (Only If Provided)

Only adjust if the battery manufacturer explicitly provides values:

  • Rebulk offset
  • Absorption duration

Follow documentation exactly (e.g. PowerPlus, Discover).

2.5 Notes

  • Ignore Load Output on larger MPPTs
  • Smart Networking is not required when using a Cerbo GX

3. Commission the Inverter (MultiPlus / Quattro)

Use VE.Configure 3 (preferred over VictronConnect).

3.1 Connect

  • Use MK3 USB ↔ VE.Bus adapter
  • If not detected, go to Special in the menu and install USB drivers

3.2 General Settings

  • Frequency: 50 Hz
  • AC input current limit:
    • Set conservatively
    • Enable Override by remote

3.3 Grid Code (On-Grid / ESS Only)

Select:

  • Australia A
  • Neutral bypass
  • AS/NZS 4777.2:2020

3.4 Battery Settings

  • Enable charger
  • Battery type: Lithium Iron Phosphate
  • Enter manufacturer charge parameters
  • Disable Storage Mode for off-grid systems

3.5 Low-Voltage Protection

Set:

  • DC low shutdown
  • Restart voltage
  • Alarm voltage

Avoid values that cause nuisance alarms.

4. AC-Coupled Solar (If Used)

4.1 Disable Virtual Switch

Required before adding any assistants.

4.2 Add Assistant

  • Off-grid: PV Inverter Support
  • On-grid: ESS Assistant

4.3 Frequency Control

  • Leave default values unless coordinating with the inverter manufacturer
  • Victron uses frequency ramping to throttle AC-coupled inverters
  • Settings must align with inverter behaviour (e.g. Fronius)

4.4 One-to-One Rule

AC-coupled inverter capacity must not exceed Victron inverter rating

This prevents over-power during load drop events.

5. Commission Cerbo GX (GX Device)

5.1 Physical Checks

  • VE.Bus ports → inverter
  • Ethernet port ≠ VE.Bus (common mistake)
  • CANbus termination resistors only on CAN ports

5.2 Firmware

  • Update GX firmware first
  • Set updates to Check only

5.3 Access & Security

  • Use Installer mode during commissioning
  • Enable Remote Support

5.4 Network

  • Connect via Ethernet or Wi-Fi

6. CANbus Configuration (Managed Batteries)

Navigate to Settings → Connectivity → CANbus.

Set:

  • Profile: CAN-bus BMS
  • Baud rate: 500 kbps (most systems — confirm via battery documentation)

Use Victron Type-A BMS cables.

Avoid custom cables due to high failure rates.

7. Battery & Charge Control (DVCC)

  • Enable DVCC
  • Use manufacturer-recommended values

Typically:

  • Shared voltage sense: OFF
  • Shared current sense: OFF

8. VRM Portal Setup

  • Create or log into VRM account
  • Add installation using VRM ID
  • Set:
    • Access level: Full
    • Log interval: 1 minute
  • Install SD card or USB storage for offline logging

9. ESS-Specific Settings (On-Grid Only)

  • Operating mode: Optimized with battery life (typical)
  • Set minimum SOC reserve
  • Configure grid meter position
  • Ensure zero-export compliance (Australia)

10. AC-Coupled Inverter Integration (Fronius Example)

  • Enable Modbus TCP
  • Set Sunspec model: INT.SF
  • Enable inverter control via Modbus
  • Configure dynamic power reduction
  • Confirm Feed-in limiting active = YES on GX

Follow the Victron ESS manual exactly for Fronius integration.

11. Final Validation 

Confirm:

  • SOC tracking is correct
  • MPPT charge states are sensible
  • No inverter errors present
  • Frequency ramping operates correctly (if AC-coupled)
  • VRM logging is active

12. Best-Practice Notes

  • Always enter open-loop values, even in closed-loop systems
  • Use SD card storage in GX devices
  • Photograph the installation and upload images to VRM
  • Avoid remote inverter firmware updates unless absolutely necessary

 

Back to blog