Understand your system. Find the right setting.

Use this worksheet to gather the right information before entering values. It separates system facts, operating preferences and protective limits.

Start with an equipment list and the actual system drawing. For each item below, record the source of the value as well as the value itself: a product label, battery manual, approved design, supply rating or a live BMS message. Do not fill unknown fields with numbers taken from a similar forum installation.

Next identify who controls charging. A standalone charger follows its configured algorithm. A supported managed-battery system can receive changing instructions through the BMS and GX. In that case a setting on an individual charger may be an upper limit, inactive, or governed elsewhere. Check the relevant integration instructions before deciding which values to change.

Commission in a documented sequence: confirm the physical installation and protection, establish communication and correct measurements, configure the intended operating mode, then test ordinary charging, loads and supported backup behaviour. Enable additional optimisation only after basic operation is understood. Save the configuration and record what successful operation looked like.

Configuration details

Exact equipment models

Where it is used

System record

What to enter or collect

Full model and voltage variant of every inverter, charger, GX, meter, shunt and BMS.

Why it matters

A family name such as MultiPlus or SmartSolar does not identify every capability.

Firmware and software

Where it is used

System record / product information

What to enter or collect

Versions on the GX and connected products, plus VictronConnect or configuration-tool version.

Why it matters

Menu paths and supported integrations change with firmware.

System application

Where it is used

Design / GX system setup

What to enter or collect

Home ESS, off-grid, boat, vehicle or other intended use; identify grid, generator and shore-power inputs.

Why it matters

An ESS recipe is not a universal configuration for every installation.

Battery chemistry and model

Where it is used

All charging devices / BMS

What to enter or collect

Exact battery manufacturer, chemistry, model and applicable integration instructions.

Why it matters

A generic lithium preset is not a substitute for battery-specific information.

Battery bank voltage

Where it is used

Chargers / inverter / monitor

What to enter or collect

Actual nominal bank voltage and the series/parallel arrangement.

Why it matters

The voltage class must match the equipment and bank.

Capacity in Ah

Where it is used

Battery monitor / relevant inverter settings

What to enter or collect

Total bank amp-hour capacity at the bank voltage, according to the installed configuration.

Why it matters

Series and parallel connections affect voltage and capacity differently.

Energy capacity in kWh

Where it is used

Dynamic ESS or energy calculations

What to enter or collect

The capacity definition requested by that screen, using the battery system’s documented energy.

Why it matters

Do not enter Ah in a field that requests kWh or confuse nominal with usable energy.

Battery charging values

Where it is used

Standalone charger settings

What to enter or collect

Approved absorption, float/storage, duration and temperature rules from the battery documentation.

Why it matters

These are battery-specific; maximum protection voltage is not automatically a charging target.

Managed battery limits

Where it is used

GX battery / DVCC

What to enter or collect

Confirm live CVL, CCL and DCL and which battery/BMS supplies them.

Why it matters

The active BMS request may be lower than a locally entered maximum.

Maximum charge current

Where it is used

Charger / DVCC

What to enter or collect

An appropriate current within battery, charger and installed DC-system limits; check whether the field is per device or system-wide.

Why it matters

A higher setting cannot create unavailable power or override a BMS safely.

AC input current limit

Where it is used

Inverter/charger input control

What to enter or collect

The permitted AC supply current for that input and installation, including shore or generator constraints.

Why it matters

This is AC current, not the battery’s DC charging current.

Grid code and AC system

Where it is used

Inverter configuration

What to enter or collect

Applicable country/grid requirements and approved single-phase, split-phase or three-phase design.

Why it matters

Have the installer establish legal and electrical requirements.

Meter position and role

Where it is used

Energy meter / GX

What to enter or collect

Exact meter model, location, Grid or other role, phase order and import/export direction.

Why it matters

Incorrect measurements can make the controller respond to the wrong power flow.

Battery monitor selection

Where it is used

GX system setup

What to enter or collect

The intended source of battery voltage, current and state of charge.

Why it matters

Multiple devices may report different estimates; select the supported system source.

ESS operating mode

Where it is used

GX ESS

What to enter or collect

The intended operating strategy and whether an external controller or Dynamic ESS is involved.

Why it matters

The mode determines why the battery charges, discharges or remains reserved.

Minimum state of charge

Where it is used

ESS / supported controller

What to enter or collect

The operating reserve required by the application, within the documented control behaviour.

Why it matters

An operating reserve and the BMS emergency cutoff are different layers.

Export permissions and limits

Where it is used

ESS / Dynamic ESS / PV controls

What to enter or collect

The permitted export arrangement, phase treatment and limits for the installation and contract.

Why it matters

A desired zero-export target is not a blanket guarantee of zero instantaneous export.

PV array data

Where it is used

MPPT design record

What to enter or collect

Module Voc, Isc and temperature coefficient, series/parallel counts and design minimum temperature.

Why it matters

The array must remain within the exact controller’s voltage and current limits.

MPPT charge control

Where it is used

VictronConnect / GX

What to enter or collect

Battery preset or managed-control mode, current limit and any documented remote/BMS control.

Why it matters

A locally visible setting may not be the active controller in a managed system.

Alternator and starter supply

Where it is used

Orion setup / installation record

What to enter or collect

Vehicle charging behaviour, available alternator capacity, input wiring and permitted input draw.

Why it matters

A charger rating does not establish the alternator’s safe spare capacity.

Engine detection and input lockout

Where it is used

Compatible Orion model

What to enter or collect

Model-specific engine detection, remote control and input voltage thresholds for the actual vehicle.

Why it matters

These determine whether charging starts, stops or protects the starter supply.

Charged voltage, tail current, time

Where it is used

SmartShunt / BMV

What to enter or collect

Full-charge detection values suitable for the battery and charging system, plus the stated units.

Why it matters

These detect a full battery; they do not command the charger’s absorption voltage.

Dynamic ESS commercial inputs

Where it is used

VRM Dynamic ESS

What to enter or collect

Supported tariff/price information, import/export permissions, capacity and realistic system capabilities.

Why it matters

A good schedule depends on accurate inputs and still remains subject to hardware and BMS limits.

Commissioning evidence

Where it is used

Handover record

What to enter or collect

Before/after settings, device list, normal-load readings, alarm history and relevant test results.

Why it matters

This makes later troubleshooting and rollback evidence-based.

What to check or record

1. Complete the equipment and battery sections before entering charging values.
2. Have the installer confirm AC, PV, cabling and protection data.
3. Keep monitoring thresholds separate from charging and shutdown limits.
4. After saving, reopen settings and compare the actual readings with expected behaviour.

Choose a profile for the exact battery chemistry and the battery maker’s charging specification, then check that the charger model supports it.

A familiar battery label is a starting point, not proof that every voltage and timing value is suitable. Compare the selected preset with the battery documentation. Blue Smart IP22, IP65 and IP67 are different ranges; menu options, output arrangements and ratings must be checked in the relevant manual.

What to check or record

1. Record the exact charger model, nominal battery voltage and battery chemistry.
2. Compare absorption, float or storage behaviour and permitted current with the battery specification.
3. Use a custom profile only when you have documented values and understand the effect of each changed field.

Recondition is a specific lead-acid treatment, not a general way to improve charging and not a lithium charging setting.

It raises the charging voltage and can be inappropriate for both the battery and equipment connected to it. The decision depends on the battery maker’s instructions and the exact charger. A disappointing runtime, a low percentage reading or a charging alarm is not, by itself, a reason to enable it.

What to check or record

1. Identify the chemistry and whether the manufacturer permits reconditioning.
2. Check connected equipment’s voltage limits before any approved treatment.
3. Investigate capacity, charging history and measurement accuracy rather than repeatedly applying a higher-voltage mode.

No. On the IP22 three-output range, the outputs share the charger’s total current capability and use a common charging algorithm.

Three connections do not turn one charger into three independently programmable chargers. If several batteries are connected, the total current is shared according to their condition. Batteries on those outputs need to be compatible with the same charge profile. Verify the exact product before applying this explanation to another charger family.

What to check or record

1. Read the total output rating on the specific charger.
2. Record every connected battery’s chemistry and charging requirements.
3. Do not assume that a three-output 30 A model can deliver 90 A or separately charge unrelated chemistries.

The rating is a capability; actual current also depends on the charge stage, selected limit, temperature and battery demand.

A charger can correctly reduce its current as the battery approaches its target voltage. Current consumed by connected equipment also makes charger output different from net battery charge current. Check the active mode before treating a lower reading as a fault. A quiet or reduced-current mode may deliberately limit output.

What to check or record

1. Record the charging stage, battery voltage and configured current limit at the same time.
2. Check whether a reduced-current mode is active on this model.
3. Compare charger output with battery-monitor current and the load demand.
4. If the battery remains undercharged, investigate the battery specification and installation rather than simply increasing voltage.

Do not use a Smart BatteryProtect to interrupt the main DC input of an inverter or inverter/charger.

Victron’s installation warning specifically excludes this arrangement. Capacitive input and reverse-current behaviour are important here; a suitable-looking current rating is not sufficient. Where the documented design uses BatteryProtect to control an inverter, it controls a compatible remote input rather than switching the inverter’s high-current DC supply.

What to check or record

1. Identify the exact BatteryProtect and inverter models.
2. Use the approved remote-control arrangement from the relevant manuals.
3. Have the installer specify the main DC fuse, isolation and switching equipment for the actual system.
4. Do not trial an unsupported connection to see whether it works.

No. They perform different jobs within a DC distribution system.

A busbar connection module, a fused distribution module and a battery-management module are not equivalent protection devices. A system drawing should identify what provides branch fusing, current measurement, battery protection and isolation. Physical compatibility is also model-dependent: check connection size and the complete arrangement instead of selecting modules only by appearance.

What to check or record

1. Write down the function required at each position in the DC system.
2. Check the exact Lynx model and connection variant.
3. Match the BMS to the battery family; a Lynx distribution module alone does not make a battery managed.
4. Confirm protection and current ratings with the installer.

Select the BMS for the exact Victron battery family; the Smart and NG names are not interchangeable.

A compatible physical connector or a similar nominal battery voltage does not establish compatibility. Victron documents separate battery/BMS combinations. More advanced arrangements can combine separately managed banks under specific conditions, but that is not permission to connect an unsupported battery directly to the wrong BMS.

What to check or record

1. Record the full battery model, family and nominal voltage.
2. Use the battery manual’s BMS selection guidance.
3. Check the complete design if separate battery banks or BMS units are paralleled.
4. Do not apply a Lithium Smart wiring or setup example to an NG system without checking it.

Use another installation to understand a setting, not as a ready-made configuration file for your own system.

Two systems can have similar-looking Victron equipment while using different batteries, AC supplies, grid rules, meters, firmware and control methods. A value that is correct for one can be misleading for the other. First identify what the setting controls, whether a BMS overrides it, and the source of the limit.

What to check or record

1. Match exact model numbers and firmware, not only product families.
2. Compare battery charging instructions and system wiring.
3. Separate monitoring thresholds, operating preferences and safety limits.
4. Save the existing configuration and change one understood item at a time.

No. Software can change system behaviour, but it cannot make an unsuitable electrical installation sound.

A voltage drop, hot connection or nuisance trip requires the underlying cause to be investigated. Increasing a voltage limit, disabling an alarm or raising a current setting may hide a symptom while increasing stress. Record the operating state and have a qualified installer examine the physical installation and its protection.

What to check or record

1. Record the load or charging current when the symptom occurs.
2. Note which device reports the voltage and where that voltage is measured.
3. Use the exact product’s cable, fuse, terminal and mounting requirements.
4. Escalate overheating, damaged insulation or unexpected trips for inspection before continued testing.

These are different quantities. Entering the right number in the wrong unit can make an otherwise correct setup behave incorrectly.

Voltage is measured in V; current in A; real power in W; apparent power in VA; charge capacity in Ah; and stored or transferred energy in kWh. AC input current and DC charging current refer to different sides of the inverter/charger. Battery capacity fields and energy-capacity fields therefore need different values.

What to check or record

1. Read the unit beside each field.
2. For a simple nominal-energy illustration, 51.2 V × 100 Ah ÷ 1000 = 5.12 kWh; usable energy is a separate matter.
3. Do not substitute a kVA product rating for measured continuous kW capability.
4. Use the documented battery-bank capacity and configuration, not the capacity of one module by habit.

Read the system from the battery and energy sources to the controllers, rather than assuming that the last setting you changed must be in charge.

First identify the measurement. A percentage on a SmartShunt or BMV is an estimate from measured current and synchronisation rules. It does not, by itself, order every connected charger to stop at that percentage. A battery BMS can provide a separate state of charge and impose protective limits.

Second identify the charging authority. A standalone charger typically uses its own profile. With supported managed control, a BMS and GX can communicate limits to compatible devices. A lower charge current can then be an intentional response to battery condition rather than a fault in the charger.

Third identify the operating strategy. ESS, Dynamic ESS, schedules, remote-control inputs and external automation can influence what the system is trying to do. Hardware limits and battery protection still constrain what it can achieve. Changing a preference should not be used to defeat a protective stop.

To diagnose a discrepancy, take a simultaneous snapshot: charger state, voltage, current, battery state of charge, BMS limits, AC and PV availability, loads, and any active controller. Compare a configured maximum with the current request and the actual measurement. Keep the exact firmware and model information with that snapshot.

What to check or record

1. Ask: is this a measured value, a target, a maximum or a protection threshold?
2. Identify the controlling device before changing the field.
3. Capture all relevant values at the same time.
4. Test one understood change and record the outcome.

Choose the operating purpose first; these configurations are not interchangeable.

A fixed home system operating alongside the grid differs from a camper using a removable shore lead. ESS is intended for the appropriate fixed grid-connected installation. MultiPlus and Quattro products also support other arrangements, but owning one does not mean the ESS Assistant is appropriate. Define operation with AC available, during an outage and after AC returns.

What to check or record

1. Record whether the installation is fixed, mobile, marine or permanently off-grid.
2. Identify the circuits requiring backup and their position in the approved design.
3. Confirm the exact product supports the proposed arrangement and regional requirements.
4. Do not copy a home ESS configuration into a vehicle.

Match the configuration tool and connection method to the exact product and task.

VEConfigure supports the relevant VE.Bus inverter/chargers; a wired computer connection normally uses an MK3-USB and a suitable straight RJ45 cable. VictronConnect can configure supported VE.Bus products, but functions and platform support vary. GX monitoring is not access to every inverter setting. Multi RS belongs to a different family: a MultiPlus procedure must not automatically be applied to it.

What to check or record

1. Record the complete model, firmware and communication interface.
2. Distinguish monitoring, operating controls, firmware, Assistants and system configuration.
3. Read and save a dated configuration backup before editing.
4. Use the exact product manual when menus differ from an online screenshot.

Prepare verified equipment, battery, AC, metering and operating information.

A setup sheet needs more than preferred voltages. Include inverter and GX models, firmware, unit count and phases, battery model and module count, approved BMS integration, nominal bank voltage, capacity and permitted currents. Add source ratings, grid requirements, meter location, PV location and the desired reserve. Unknown values should remain unresolved until checked, rather than borrowed from another system.

What to check or record

1. Separate manufacturer limits, installer design limits and owner preferences.
2. Record units: V, A AC, A DC, Ah, kW, kWh or percent.
3. Attach battery compatibility instructions and the installation single-line diagram.
4. Retain the original backup and a log of subsequent changes.

Enter permitted AC supply current, not battery charging current.

The limit concerns current at the inverter/charger AC input. Derive it from the actual shore, grid or generator supply and the approved installation limits. Charging shares that supply with pass-through loads and can fall as loads rise. Upstream parallel loads require separate consideration: the Multi input limit is not automatically a whole-building service limiter. A GX, remote panel or Assistant can influence the effective setting.

What to check or record

1. Confirm the active physical input, especially on a Quattro.
2. Use the supply rating and the installer’s permitted operating margin.
3. Compare the entered value with the live limit and remote controls.
4. Check AC amps and DC amps separately when diagnosing charging.

Battery and installation limits matter; the charger nameplate is only one constraint.

This setting is a battery-side current ceiling for the charger. Start with the battery’s permitted rate and the installed DC conductors, protection and distribution. Include other simultaneous chargers. A managed BMS can impose a lower live limit. Actual current may also fall because AC capacity is restricted, loads take priority, the battery reaches its voltage target or equipment temperature rises.

What to check or record

1. Document the bank-wide limit and each charging device’s limit.
2. Include MPPT, AC and DC-DC charging in simultaneous-source calculations.
3. Read the live BMS charge-current limit before increasing settings.
4. Compare power on both sides; equal AC and DC amp readings are not expected.

Use the exact battery specification and its Victron integration instructions.

A generic lithium preset or another owner’s screenshot does not establish the right profile. Voltages, time limits, temperature behavior and balancing needs depend on battery design. A supported managed battery can govern charging through live BMS commands instead of a standalone local curve. Keep fallback and maximum settings consistent with the approved integration; do not raise them merely because charging tapers before a displayed 100% SoC.

What to check or record

1. Identify the battery model and document revision, not just nominal voltage.
2. Confirm whether local settings or a BMS/GX manages charging.
3. Record approved voltages, times and temperature requirements.
4. Review equalisation separately: lead-acid defaults may be unsuitable for lithium.

It reserves energy during grid operation; it is not an absolute protection threshold.

Choose the reserve from critical-load needs and battery requirements. The phrase “unless grid fails” matters: islanded operation changes the control conditions, so discharge is not guaranteed to stop at that same percentage during an outage. Battery and inverter protection remain separate. Begin reserve planning with critical-load energy and desired outage duration, allowing for losses and conditions that reduce usable capacity.

What to check or record

1. Define critical-load energy instead of choosing a percentage by habit.
2. Confirm SoC comes from the intended, correctly configured monitor.
3. Compare the user minimum with BatteryLife’s active limit.
4. Have the installer validate protection and backup operation independently of this preference.

BatteryLife can retain more energy when recharge has been insufficient.

The configured minimum is an owner preference; the active limit shows what control currently applies. With BatteryLife, inadequate recharge can increase the effective reserve. This alone does not prove incorrect capacity or a defective battery. Examine charging history and ESS state before lowering settings. The appropriate BatteryLife choice depends on battery technology and approved integration, not simply the desire to discharge more deeply.

What to check or record

1. Read mode, BatteryLife state, configured minimum and active limit together.
2. Review several days of solar production, consumption and completed charging.
3. Check battery-specific balancing and full-charge requirements.
4. Keep a before-and-after record when operating preferences change.

Identify the reason for restricted discharge before changing limits.

Independent conditions can block support: the active SoC limit, BMS restrictions, operating mode, schedules or external control. A zero power limit can deliberately prevent discharge. Capture the state while the symptom occurs because a temporary battery limit may disappear later. Determine which controller requests the behavior, then compare that request with the intended design. Bypassing battery protection is not a diagnostic shortcut.

What to check or record

1. Check ESS mode, active reserve, alarms and live BMS discharge limit.
2. Inspect user limits and any Node-RED, Modbus or external automation.
3. Verify the physical switch and any Charger only selection.
4. Confirm meter direction and load location before interpreting power flows.

A schedule, reserve recovery or protective control may legitimately request charging.

Do not assume every nighttime charge is caused by Dynamic ESS. Keep batteries charged, scheduled charging, DESS or recovery of a depleted reserve can all produce grid-charge requests. Compare event time with configured schedules and battery history. Repeated charge/discharge near a threshold needs context: it may involve control hysteresis, inaccurate SoC, battery restrictions or competing automation rather than one universally wrong setting.

What to check or record

1. Record ESS state and charge power during the event.
2. Inspect scheduled charge levels, DESS controls and external automation.
3. Compare SoC with active reserve and recent battery events.
4. Keep protection intact while identifying the responsible controller.

ESS can remain synchronised with the grid while reducing net import.

A connected AC input does not mean the grid supplies all household energy. In grid-parallel ESS, power can be balanced while the connection remains available. Distinguish connection state from measured power direction and magnitude. This differs from an installation deliberately running as an island. Disconnecting AC merely to make a diagram appear “off-grid” changes the operating arrangement and is not an ordinary efficiency setting.

What to check or record

1. Read grid watts and energy, not just the connection indicator.
2. Check the intended setpoint and whether metering covers the site.
3. Compare steady operation with a load-change event.
4. Follow the approved application configuration rather than a legacy Hub example.

It depends on where loads and PV connect relative to the inverter/charger.

ESS needs trustworthy measurement of the power it must regulate. A system with every relevant load on AC-out differs from one with household loads or PV elsewhere. Draw the measurement boundary before choosing Inverter/charger or External meter. A PV production meter and grid meter serve different purposes; their roles cannot be swapped merely because both display watts. Use supported hardware and the appropriate Victron topology.

What to check or record

1. Mark all AC loads, PV inverters and meters on the diagram.
2. Verify grid metering includes every branch ESS must compensate.
3. Match each device role to its physical measurement location.
4. Check loss-of-meter behavior during commissioning.

Verify measurement roles, phase mapping and direction before adjusting energy management.

Some displayed flows are calculated from other measurements. An incorrect meter role or phase measurement can therefore distort several readings at once. Start with a known operating state and the installation diagram. Compare the meter display with GX readings and note each sign convention. Live electrical checks and corrections belong to the installer; software adjustments cannot safely compensate for an unverified measurement arrangement.

What to check or record

1. Record meter model, role, phase mode and installed location.
2. Compare readings when a known load is operated normally.
3. Compare phase totals and individual phases on the same basis.
4. Ask the installer to verify direction and phase mapping when evidence conflicts.

Total-of-phases regulation targets the sum, not zero on every phase.

Under a total target, opposite phase flows can coexist while net power remains close to the setpoint. That does not create unlimited power sharing during an outage: inverter ratings and the physical backup arrangement still matter. Confirm how the utility meter accounts for phase energy and select the approved strategy accordingly. A single inverter connected to one phase is also different from a coordinated three-phase inverter system.

What to check or record

1. Read L1, L2, L3 and their total over the same interval.
2. Document single-phase versus coordinated three-phase equipment.
3. Confirm the actual utility metering method rather than assuming billing behavior.
4. Evaluate backup capacity per phase separately from grid-connected net balancing.

A control target is not an instantaneous, universal export barrier.

A fast load change can happen before regulation adjusts output. Control capability also depends on PV equipment, measurements and supported interfaces. Distinguish a desired setpoint from grid-connection requirements. Strict export prevention requires an appropriately designed and verified installation. A large positive import target is not a substitute for correct metering or control, and monitoring a PV inverter does not necessarily mean the system can curtail it.

What to check or record

1. Identify whether surplus originates from DC solar, AC PV or the battery.
2. Check the supported curtailment method for each PV inverter.
3. Test steady conditions and sudden load removal during commissioning.
4. Have the installer confirm compliance rather than inferring it from one graph.

Use the code required for the exact installation and approved equipment.

This is an installer decision, not an optimisation preference. A country name may not uniquely determine the applicable standard. Requirements depend on the connection and product certification. An inappropriate None setting can prevent expected ESS operation; weakening loss-of-mains or other protection to force a connection can create an unsafe or non-compliant system. Record the selected code and its justification in the commissioning documentation.

What to check or record

1. Confirm local network requirements and exact product certification.
2. Have the authorised installer select and document the code.
3. Use an approved generator arrangement instead of weakening grid protection.
4. Escalate rejected supplies with measured evidence; do not disable protection as a workaround.

The ESS Assistant changes which discharge controls apply.

A standalone inverter shutdown field is not automatically the active threshold in ESS. Its control scheme uses dynamic cutoff and related behavior, alongside battery-integration constraints. Dynamic thresholds reflect the way terminal voltage changes under load. Editing a familiar field without identifying the active scheme can therefore accomplish nothing or miss the real problem. Use the relevant Assistant and battery instructions, not voltage examples from another chemistry or bank.

What to check or record

1. Confirm the ESS Assistant is installed and inspect its configuration.
2. Record voltage, current, SoC and the reason when discharge stops.
3. Separate manufacturer protection from the owner’s reserve preference.
4. Do not copy cutoff examples from a different battery or current capability.

AC-source management and battery assistance are related but different functions.

A limited shore supply may feed both household loads and the charger. Charging can reduce to leave capacity for loads. Where supported and configured, PowerAssist can supplement the source with battery power. It does not increase breaker ratings, transfer-switch capacity or continuous inverter capability. ESS applies its own control scheme, so a standalone PowerAssist checkbox is not an independent master switch for ESS behavior.

What to check or record

1. Identify whether the application is shore, generator-assisted or ESS.
2. Check the permitted input limit and product-specific assist minimum.
3. Consider available battery discharge power and equipment temperature.
4. Size loads and protection from the design, not optimistic nameplate addition.

A running engine does not prove its AC supply has been accepted.

The generator must maintain suitable voltage, frequency and waveform under actual demand. Trouble may occur only when charging starts or a large consumer switches. Compare continuous generator capability with loads plus charging, then capture the input state during failure. UPS behavior, Dynamic current limiter and WeakAC have trade-offs; they are not a universal fix. Diagnose with the installer and the generator’s operating requirements.

What to check or record

1. Confirm generator output is present and not in overload.
2. Record input acceptance, voltage and frequency during load changes.
3. Use source-current and charging demands suited to the generator.
4. Do not widen protection windows or alter earthing without qualified assessment.

Operating mode controls permitted functions; check the exact product behavior.

On permits normal inverter/charger operation: accepted AC can supply the output and charge the battery, while inversion is available when appropriate. On MultiPlus-II, Charger only allows charging and accepted AC pass-through, but does not start the inverter when AC fails. Where available, Inverter only permits inversion and disables charging; check the exact model’s AC-transfer behaviour.

The physical switch, GX/VRM mode and ESS energy-management mode are separate layers. Record all three when backup or charging is missing. Consider dependent loads before switching a system remotely.

What to check or record

1. Record the physical switch position and displayed software mode.
2. Check transfer and backup behavior in the exact product manual.
3. Look for BMS or remote commands requesting another state.
4. Restrict remote switching access appropriately for important loads.

Consider continuous watts, apparent power, starting demand, temperature and the DC supply.

The VA figure in a model name does not promise that every load with the same numerical wattage runs continuously. Motors and electronic loads may have high starting demand; heat and battery limitations also affect capability. DC voltage can fall under heavy current if the supply path is inadequate. Identify the actual alarm: low-voltage shutdown and AC overload require different investigations.

What to check or record

1. Check the exact model’s continuous and surge specifications.
2. List simultaneous loads and motor or compressor starting events.
3. Capture battery voltage/current and the actual alarm or LED code.
4. Have the installer assess DC connections and battery capability rather than forcing repeated restarts.

Expansion requires compatible hardware and coordinated system configuration.

A similar case or power rating does not establish compatibility. Check complete product numbers, firmware, phase arrangement and supported system size first. Certain large MultiPlus-II models require a specific external-transfer-switch arrangement, so generic parallel-unit counts cannot be applied indiscriminately. Combined units also need DC distribution, protection and battery capability designed for their total currents. The installation should be reviewed before another unit is purchased or connected.

What to check or record

1. Check current Victron parallel-system instructions for all proposed units.
2. Confirm required compatible variants and firmware.
3. Document the coordinated VE.Bus configuration and correct GX arrangement.
4. Reassess AC switching, DC distribution and battery capability before expanding.

Only circuits included in the designed backup arrangement receive inverter power.

An inverter and battery do not automatically back up every grid-side circuit. Identify which board and loads connect to the appropriate AC output, including any output available only while AC input is present. Battery and inverter capability must support the selected loads. PV operation depends on its connection and approved islanding design; grid-side solar cannot be assumed to remain available just because a battery exists.

What to check or record

1. Identify backed-up circuits and outputs on the installation diagram.
2. List critical loads, starting demands and their phases.
3. Confirm expected AC-coupled PV behavior without the grid.
4. Ask the installer to document a controlled backup and grid-restoration test.

Collect system capabilities, battery details and the actual purchase/export tariff rules.

The wizard needs realistic planning inputs: permitted import/export, conversion capability, total battery energy, sustained charging/discharging power, cycle-cost assumptions and export restrictions. Obtain purchase and sale formulas from the electricity contract. Keep a source beside every input. A supplier preset may resemble your tariff without matching the particular contract, fees or tax treatment. Establish ordinary ESS operation before adding economic scheduling.

What to check or record

1. Use kW for power and kWh for energy capacity.
2. Derive capability from battery, inverter and installation constraints together.
3. Distinguish permission to export solar from permission to sell battery energy.
4. Verify currency, timezone, price interval, fees and taxes against billing information.

Nominal voltage × ampere-hours ÷ 1,000 gives nominal energy in kWh.

An illustrative 51.2 V × 200 Ah bank has 10.24 kWh nominal energy. This does not establish usable capacity, discharge limits, losses or a charging profile. Series connection adds voltage while string Ah remains unchanged; appropriate parallel connection adds Ah at the same nominal voltage. Prefer the manufacturer’s installed-energy figure, and check whether a field expects total capacity rather than a value already reduced for reserve.

What to check or record

1. Confirm module count and series/parallel arrangement.
2. Distinguish battery-monitor Ah from planning-software kWh.
3. Keep minimum SoC reserve separate from total capacity.
4. Investigate persistent SoC/energy mismatch with history and supplier data.

No: planning capabilities and enforced operating limits serve different purposes.

The planner needs realistic capability to judge whether an energy target is achievable within a time interval. The installation still needs correctly commissioned electrical, inverter and battery limits. A low DESS input must not be the sole protection for cables, the grid connection or the battery. An optimistic input can instead produce an unattainable plan when loads or live BMS restrictions reduce available power.

What to check or record

1. Identify the approved control or hardware enforcing each actual limit.
2. Use realistic sustained capability rather than a surge rating.
3. Compare the plan with live battery limits and competing loads.
4. Explain capability inputs versus enforced constraints in the handover record.

Model the amount actually paid or received per kWh under the current contract.

Separate the energy-price component from per-kWh surcharges, taxes, VAT treatment and export deductions. Standing charges are a different cost from the marginal price of another kWh. Purchase and export formulas may differ. Before trusting a schedule, compare calculated prices for known intervals with the supplier’s displayed or billed figures. A tariff change requires another check even when the supplier name stays the same.

What to check or record

1. Record tariff version, currency and effective date.
2. Check kWh versus MWh units before converting.
3. Match actual hourly or 15-minute billing intervals where supported.
4. Do not assume a provider preset automatically matches every contract.

Final purchase and sale prices may differ substantially from the raw market price.

A negative wholesale component may be offset by fees and taxes; export deductions can differ again. Storage also involves losses and an assumed battery-use cost. Compare full marginal prices instead of the color of one market graph. Solar curtailment is a separate capability: support depends on equipment and software. Monitoring a third-party PV inverter does not mean it can necessarily be commanded to stop.

What to check or record

1. Compare full import and export prices for the same interval.
2. Check export permission and battery-to-grid restrictions.
3. Include realistic losses and battery-use assumptions.
4. Verify supported solar control before enabling price-based curtailment.

Check activation, communication, time and the reported error before repeating the wizard.

Configuration and active control are separate states. Completed settings do not prove the dashboard control is enabled or that the GX received a valid plan. Verify live communication and supported ESS operation. If a wizard loses values, capture the failing step and software context rather than inventing alternative technical specifications. Distinguish a current stable-version issue from a workaround posted for an older beta.

What to check or record

1. Check the DESS dashboard control as well as configuration.
2. Verify live data, connectivity, timezone and tariff interval.
3. Record the DESS error/status and when the issue began.
4. Consult current release information before applying forum workarounds.

Use documented assumptions, retain required reserve and evaluate measured results over time.

Cycle cost is a planning estimate, not a warranty prediction. A basic calculation divides battery cost by assumed equivalent full cycles and energy capacity. For illustration, €3,000 ÷ (6,000 × 10 kWh) equals €0.05/kWh. Conditions and cycle definitions matter. Plans can change with consumption, solar forecasts and operating constraints; judge several representative days rather than treating one revised interval as proof of failure.

What to check or record

1. Document the cycle-life assumption and its operating conditions.
2. Keep capacity and currency units consistent; returns are not guaranteed.
3. Compare planned and actual energy over representative days.
4. Check reserve changes, household demand and BMS restrictions when targets are missed.

A practical handover sequence for a qualified installer and the owner of a fixed home system.

Start with the intended outcome. Record whether the owner wants solar self-consumption, a protected backup reserve, scheduled charging or Dynamic ESS. Identify critical loads and the desired outage duration. This defines the information required; it does not provide electrical settings. Confirm the exact inverter, GX, battery and PV combination against current manuals and battery compatibility guidance.

Create a setup sheet before configuration. Record product identifiers, firmware, battery module count and arrangement, nominal voltage, energy and Ah capacity, approved charging parameters, BMS interface and permitted currents. Add source ratings, phases, meter role/location and PV position. Identify each entry as manufacturer guidance, installer design or owner preference.

Commission control layers in order. Establish the supported VE.Bus arrangement, required grid configuration and ESS Assistant where applicable. Configure GX measurement roles. Verify battery communication and the active charging/discharging restrictions. Finally set preferences such as reserve and schedules. Add DESS only after ordinary ESS behavior and measurements are trustworthy.

A successful Save is not the acceptance test. Observe known loads, solar surplus and intended charge/discharge behavior. The installer should verify the designed backup response, applicable feed-in behavior and recovery. Save the final configuration and relevant screenshots. Record which observations demonstrate each intended function. Hand over normal-state examples and a clear distinction between owner controls and installer settings.

What to check or record

1. Prepare: equipment list, diagram, source ratings, battery documents and intended behavior.
2. Configure: topology/protection first, measurement/control next, owner preferences last.
3. Verify: known loads, battery communication, grid readings and documented commissioning tests.
4. Handover: dated backup, setting sources, expected states and support evidence.

Collect the correct values without turning example numbers into installation defaults.

Identification and topology: record the full product designation, AC region, nominal battery voltage, firmware and coordinated unit count. Specify standalone, parallel or multiphase operation using supported system instructions. Establish physical design and compatibility before configuration; software cannot make an unsupported combination suitable.

AC source fields: identify each input as grid, shore or generator. Document permitted input current and its source. Check whether a GX, panel or Assistant overrides it. Grid-code and supply-acceptance settings require installer assessment; they must not be loosened simply to accept an unsuitable source. Document how loads should behave if AC disappears.

Battery and charger fields: collect approved capacity, maximum charging current, absorption/float parameters and time/temperature behavior. State whether a BMS manages charging or the charger uses local control. Include simultaneous charging sources. Keep AC input amps separate from charger DC amps: converting watts to amps depends on which side’s voltage is being used and on losses.

Inverter and control fields: record operating mode, the applicable low-battery scheme, assist behavior, remote controls and Assistants. ESS can change which standalone fields apply. Separate protection, installation ratings and preferences. Read and save the existing configuration before editing. After sending settings, read them back and verify behavior under controlled conditions. Keep a change log so future diagnostics can distinguish the original setup from experiments.

What to check or record

1. General: exact unit, topology, source current, remote overrides and monitor capacity.
2. Grid/inverter: approved code, source acceptance, mode and the correct discharge-control scheme.
3. Charger: approved profile, DC current ceiling, BMS authority and other charging sources.
4. Evidence: original/final backups, changed fields and observed acceptance tests.

Build planning settings from actual system capability and the current electricity contract.

First make ordinary ESS work correctly. Confirm sensible grid, solar, consumption and battery measurements, supported communication and trustworthy SoC. Agree the required reserve. DESS cannot repair reversed metering or an unsupported electrical arrangement.

System capability: document whether export is allowed, distinguishing solar export from battery export. Determine realistic import/export and conversion capability from installation constraints. Record what enforces the actual operating limits. Planning inputs do not replace those limits.

Battery inputs: use total installed energy and document any Ah-to-kWh conversion. Determine sustained charge/discharge capability considering battery, inverter, BMS and competing loads. Keep reserve separate from total capacity. For battery-use cost, document purchase/replacement cost, equivalent full-cycle assumption and its conditions. Treat the result as a reviewable estimate, not a guaranteed life or profit.

Tariff inputs: obtain purchase/export terms, energy units, fees, taxes and time-dependent rules. Match currency, timezone and billing interval. Compare calculated prices with known supplier prices before activation. Choose operating mode and restrictions that fit the contract and owner’s preference.

After activation, check the dashboard control and status, then compare planned and actual energy across representative days. Investigate errors using timestamps and current software versions. Forecasts change as information changes: improve inputs from evidence rather than continually overriding the plan. Retain the final values and their sources for future contract or equipment changes.

What to check or record

1. Before activation: ordinary ESS works, readings make sense and reserve is agreed.
2. Inputs: sustained kW, total kWh, documented costs and verified tariff formulas.
3. Restrictions: export permission and battery-to-grid rules are explicit.
4. After activation: confirm live status and compare the plan with actual behavior.

Start with the exact charger model, battery specification and control method. A chemistry name alone is not a complete charging specification.

Record nominal battery voltage, approved absorption and float settings, maximum charging current, temperature requirements and BMS control. Confirm whether the charger works independently, in VE.Smart Networking, or under GX/DVCC control. This explains whether local values are active targets or a fallback configuration. Save the original settings before editing.

What to check or record

1. Confirm detected voltage against the actual bank.
2. Use the battery manufacturer’s profile, including time and temperature limits.
3. Consider the combined current from every charging source.
4. Record model, firmware and the source of every value.

The displayed charge stage is only one clue. A controller can be ready while the battery path, available PV power or another controller prevents current flowing.

Capture PV voltage, battery voltage, PV power, charge current, off reason and error together. Voltage alone does not prove useful solar power is available. Compare the charger’s battery voltage with another trustworthy battery reading; a large discrepancy needs an installer to inspect the connection. Do not raise charging voltage simply to make current increase.

What to check or record

1. Read the charger-off explanation in VictronConnect.
2. Check enabled status, BMS permissions and external control.
3. Look for low light, shading or a full battery.
4. Provide simultaneous readings and a settings screenshot.

Use the exact controller’s start-up and operating requirements. Small VE.Direct MPPT rules must not be copied to MPPT RS products.

For the BlueSolar 75/10–100/20 family, the manual describes starting at battery voltage plus 5 V and continuing with at least 1 V of headroom. Other families can differ. A panel’s nominal label is not its usable operating voltage. Check hot-weather operating voltage and cold-weather maximum; both ends of the design matter.

What to check or record

1. Read the model’s start-up and operating ranges.
2. Compare live PV and battery readings simultaneously.
3. Use Vmp and its temperature behaviour for operating headroom.
4. Have a designer check strings before adding series modules.

No. Treat maximum PV open-circuit voltage as a design limit, including the coldest credible installation conditions.

Voltage measured while charging is usually below open-circuit voltage and cannot prove a string is safe. Use module Voc, its temperature coefficient, series-module count and design minimum temperature. Include relevant tolerances and the separate operating limit where specified. A design that relies on the charger quickly pulling voltage down is not acceptable.

What to check or record

1. Collect the exact panel datasheet, not just wattage.
2. Calculate cold-string Voc with the Victron sizing tool and specifications.
3. Check each tracker or input separately where applicable.
4. Change the design if any limit is exceeded.

They distinguish the PV voltage class and battery-side charge-current rating. The second number is not the allowed PV-array current.

Do not compare a string’s current with the 100 A label on a 250/100 and assume spare input capacity. A converter exchanges voltage and current while approximately conserving power, allowing for losses. PV short-circuit current, connector limits, maximum PV voltage and nominal PV power are separate checks. The same output-current rating represents different power at different battery voltages.

What to check or record

1. Identify PV-side and battery-side specifications.
2. Check maximum PV short-circuit current separately.
3. Use actual charging voltage when estimating output power.
4. Evaluate voltage, current and power before expanding.

A flat trace can be normal current limiting, but also a full battery, BMS restriction, temperature or system control.

Identify what is limited: PV watts, battery amps or net charge. Record charge stage and limits at the plateau. A larger array can collect more energy in weak sun without increasing the controller’s maximum battery current, but permitted oversizing still has to respect every electrical input limit. No universal safe percentage replaces the datasheet.

What to check or record

1. Compare output amps with configured and rated limits.
2. Check battery charge acceptance and BMS limits.
3. Check temperature and ventilation.
4. Use daily energy and time at the limit, not one midday screenshot, to assess sizing.

Nameplate power is a test-condition rating, not an all-day promise. Separate available sunlight from permission and ability to use it.

Compare similar weather and periods, then inspect history for peak power, yield and charge stages. A full battery with little load may deliberately leave solar potential unused. Shading, orientation and warm panels also change output. If performance suddenly changes under comparable conditions, collect evidence before replacing equipment or altering the battery profile.

What to check or record

1. Record weather, shading and orientation.
2. Check whether charging was restricted or the battery full.
3. Compare earlier similar days.
4. Ask an installer about a sudden unexplained drop, particularly with errors or damaged connectors.

They describe the charging process, not a precise battery percentage. Interpret the stage with voltage, current, elapsed time and control mode.

Bulk generally seeks the charging target with available current. Absorption holds a target while completion criteria are met; float uses a maintenance target if the profile provides it. A BMS or GX-controlled system may determine targets instead. Never translate Absorption into a fixed SoC for every chemistry, battery age or installation.

What to check or record

1. Read the selected profile and external-control status.
2. Compare trends through a complete cycle.
3. Match absorption duration to battery instructions.
4. Investigate a stage reached unusually early with little energy returned.

Use a preset as a starting point only when its complete profile matches the battery manufacturer’s requirements.

Two LiFePO4 batteries can need different limits, balancing conditions and low-temperature protection. Compare voltage, absorption time, current, temperature compensation and equalisation, not just chemistry. For a supported managed battery, consult compatibility instructions for BMS/DVCC operation. A BMS safety trip does not replace an appropriate charger configuration.

What to check or record

1. Obtain the exact battery’s charging instructions.
2. Compare every preset value before accepting it.
3. Keep equalisation disabled for lithium charging.
4. Confirm how low-temperature prevention is enforced.

Only if the protection has the required temperature information and control path. Entering a threshold does not create a sensor.

Check the model manual for its temperature source. On relevant VE.Direct solar chargers, the documented feature depends on battery temperature received through VE.Smart Networking. Controller temperature is not necessarily battery temperature. Managed batteries may supply charge permission through their BMS. Verify the intended path during commissioning rather than relying on a number alone.

What to check or record

1. Identify the real sensor and battery location.
2. Confirm temperature is received, not merely configured.
3. Use the battery manufacturer’s charging temperature limits.
4. Keep BMS protection active and investigate missing data.

Synchronising charge stages is different from imposing a shared current ceiling. Check the features of the exact devices and network.

VE.Smart can share selected measurements and coordinate compatible chargers. Each charger retains its own current limit; a network name does not automatically create a battery-wide current budget. GX/DVCC is a different arrangement. Document how combined output remains within battery and installation limits under the most favourable charging conditions.

What to check or record

1. Confirm device and firmware compatibility.
2. Use consistent settings where synchronised charging requires them.
3. Inspect the actual shared measurements.
4. Include AC and DC-DC chargers as well as solar in the current budget.

Do not assume small load terminals can supply an inverter. Their current and starting-surge limits differ from the charging rating.

Some MPPTs have physical load outputs; others offer virtual control. An inverter’s inrush demand can greatly exceed steady demand. Follow both manuals, with appropriate battery-side protection and supported remote control where applicable. A load-output setting does not replace correctly sized power cabling or protection.

What to check or record

1. Confirm physical terminals versus control signalling.
2. Check continuous and surge requirements.
3. Read the inverter’s supported remote arrangement.
4. Have power paths and fuse selection verified before connection.

They share a purpose but not every feature, menu or connection. Follow the exact product name and manual revision.

Record voltage class, isolated or non-isolated construction, rated current and firmware. Orion XS has features such as separate input/output current limits and GX integration that must not be presumed for every Orion-Tr Smart model. Firmware can add model-specific functions. A screenshot headed Orion is insufficient evidence that its settings or wiring apply.

What to check or record

1. Copy the full label designation.
2. Use its current manual and connection diagram.
3. Distinguish charger from power-supply mode.
4. Check feature availability before following another owner’s screenshots.

Read its off reason first. Engine running, remote permission, input voltage and battery permission are separate conditions.

Log input voltage at the Orion, output voltage, current and status when charging should occur. A smart alternator can produce voltage below the selected detection threshold while running. Alternatively, wiring voltage drop can make a healthy alternator look inadequate at the charger. The remedy must address the cause; disabling every protection can drain the starter battery.

What to check or record

1. Record lockout, engine-shutdown, remote or BMS messages exactly.
2. Compare thresholds with operating readings.
3. Check the vehicle-approved control arrangement with the installer.
4. Test engine-on charging and reliable engine-off stopping.

Engine detection judges whether conditions resemble a running engine. Lockout adds a separate minimum-voltage stop and restart condition.

The functions use different thresholds and timing: one can permit operation while the other blocks it. Current can also reduce while the charger tries to avoid pulling source voltage down. Read the status message together with measured voltage, and document the intended starter-battery protection before changing either function.

What to check or record

1. Record start, delayed-start, delay, shutdown, lockout and restart separately.
2. Use the vehicle and exact Orion manual to define behaviour.
3. Check cable drop under load.
4. Do not lower thresholds merely until the warning disappears.

The input limit protects the source’s available current; the output limit respects the receiving battery and downstream installation.

Alternator nameplate current is not automatically spare capacity: vehicle loads, idle operation and temperature matter. Battery charge limits may be below the Orion rating, especially during simultaneous solar or mains charging. Input and output amperes need not match because voltages and conversion losses differ. Document both limits and their evidence.

What to check or record

1. Obtain the vehicle or installer’s continuous source allowance.
2. Obtain the auxiliary battery’s charge limit.
3. Include all simultaneous charging sources.
4. Observe input voltage and temperature in a realistic operating test.

Rated output is a ceiling under suitable conditions. Low current can reflect a normal stage or a source, thermal, control or installation limit.

Check whether the unit is in bulk or holding a voltage target. Compare loaded input voltage with its detection threshold. A weak source or excessive voltage drop can reduce output before an off message appears. Compare output with net battery current: loads may use some output. Raising charging voltage is not a cure for unexplained low current.

What to check or record

1. Record input/output volts and amps together.
2. Check temperature and current limits.
3. Check BMS/DVCC restrictions where applicable.
4. Have a technician investigate large voltage losses or repeated cycling.

Voltage-based detection sees input voltage, not the engine. Other charging sources or the remote arrangement can affect permission.

Record whether shore power or solar maintains the starter battery. Compare the configuration with the exact manual’s normal remote and external-engine-signal arrangements. Some connections deliberately override detection, so do not copy a forum diagram without understanding its purpose. Commissioning must demonstrate what happens after shutdown and with other chargers present.

What to check or record

1. Record every source connected to the input battery.
2. Check mode, detection and remote wiring with the installer.
3. Observe stopping over the documented timing period.
4. Confirm starter-battery protection during parking.

Obtain the auxiliary battery’s chemistry, nominal voltage and complete charging specification. Starter-battery type does not define the output profile.

Record absorption, float and storage behaviour, charge-current limit, charging temperatures and BMS charge-disconnect requirements. Compare the entire preset. Keep inappropriate functions disabled; do not equalise lithium batteries. For GX-controlled Orion XS, record the targets supplied by DVCC or BMS so that a greyed-out local setting is not mistaken for a fault.

What to check or record

1. Match the profile to the output battery.
2. Check combined charge current from all sources.
3. Record temperature and BMS permission paths.
4. Save the approved profile and recheck it after commissioning.

Check the model’s permitted parallel arrangement and the complete source and battery current budgets before expanding.

Extra chargers can multiply alternator demand while vehicle loads remain. A system that works at speed may overload available power at idle or when hot. The battery must accept combined DC-DC, solar and mains current. More equipment cannot repair a poor input connection or incorrectly configured monitor.

What to check or record

1. Read model-specific parallel and isolation guidance.
2. Calculate simultaneous total input demand.
3. Confirm hot and idle alternator capability with a vehicle specialist.
4. Recommission control paths and combined battery-current limits after changes.

Enter the measured bank’s amp-hours at its bank voltage. Do not add every battery’s Ah regardless of its connection.

For identical series batteries, voltage adds but Ah remains unchanged. Parallel identical strings add Ah. Two 12 V 100 Ah batteries in series form 24 V 100 Ah; two such strings in parallel form 24 V 200 Ah. These are arithmetic examples, not a recommendation to combine batteries. Use approved configurations and a documented rating; check the discharge-rate basis for lead-acid.

What to check or record

1. Draw the actual series/parallel arrangement.
2. Confirm the shunt measures the intended bank.
3. Enter Ah, not Wh or kWh.
4. Review after bank changes or verified capacity loss.

SoC is calculated. Prove current and voltage readings first, then examine capacity, chemistry parameters and synchronisation.

A plausible percentage is not proof of correct setup. Bypassing currents, wrong capacity or premature full detection all cause drift. Compare simultaneous data, not screenshots from different times. Lithium’s flat voltage curve is a weak basis for an exact percentage. Record a complete charge/discharge period before concluding the monitor is defective.

What to check or record

1. Check current paths against the installation drawing.
2. Review capacity, Peukert and charge efficiency.
3. Inspect charged voltage, tail current and detection time.
4. Check when genuine full-charge synchronisation last occurred.

Together they tell the monitor when to recognise a full battery. They do not command charger voltage or current.

Charged voltage is a threshold, tail current is a percentage of configured capacity, and detection time is the qualifying period. An illustrative 200 Ah bank at 2% tail current has a 4 A threshold; that arithmetic does not prescribe the correct percentage. Choose criteria in relation to the battery and real charging process, then observe recognition.

What to check or record

1. Confirm capacity first because it changes the threshold.
2. Compare detection voltage with the charging profile.
3. Check all three conditions together.
4. Do not confuse monitor tail current with a charger’s absorption-end setting.

The full-charge detection conditions may be satisfied before the battery is actually full. Investigate them instead of repeatedly resetting SoC.

Clouds can reduce current while voltage remains above an unsuitable threshold. If conditions persist, the monitor can synchronise although little energy was restored. Verify measured current paths, then compare detection criteria with the profile and history. A100% display does not establish completion of the battery’s required charging cycle.

What to check or record

1. Find the exact jump in the trend.
2. Compare voltage and net current around it.
3. Review voltage, tail current and time together.
4. Validate changes through a genuine complete charge.

Only when the battery is independently confirmed full according to its requirements. Synchronising changes the estimate; it does not charge anything.

Use it to establish a sound reference after commissioning or a justified correction. Resolve failed automatic synchronisation rather than hiding it with repeated resets. An unexpected initial percentage can also follow a power interruption, depending on firmware and configured reset behaviour. Record why the manual action was justified.

What to check or record

1. Confirm the documented full-charge process completed.
2. Check measured current is credible.
3. Review reset and initial-SoC behaviour.
4. Observe the next automatic synchronisation to prove the underlying setup works.

Measurement direction must match the shunt orientation and supported configuration. Do not compensate by altering capacity or efficiency.

Use a known charge or load to confirm the sign. Have the installer compare battery and system sides with the model instructions. Some newer firmware supports a direction setting, but not every monitor does. All intended currents must still cross the measuring path; correcting polarity cannot fix a bypass.

What to check or record

1. Record what was happening when the sign was wrong.
2. Compare installation with the model diagram.
3. Check firmware support before using direction settings.
4. Verify known charge and discharge events after correction.

Usually not. It addresses a genuine offset when no current flows, not general SoC errors.

Standby electronics, heaters or an overlooked charger can make small current real. Calibrating during real current teaches an incorrect zero and creates drift. Establish the condition with a competent installer first. When current readings are credible, investigate capacity, synchronisation and unmeasured paths instead.

What to check or record

1. Identify every charge/load path, including standby devices.
2. Confirm that no actual current crosses the shunt.
3. Use the exact calibration procedure only when justified.
4. Recheck a known charge and load afterwards; do not assume a zero display proves the measurement is correct.

They affect estimated usable capacity and replenished charge, not the battery chemistry or charger output.

Peukert compensation considers discharge rate, generally more significant for lead-acid than lithium. Charge efficiency accounts for incoming charge not returned as stored capacity. Use battery data and current manual guidance; do not retain lead-acid assumptions merely because they were defaults. These factors explain why consumed Ah and SoC need not follow simple subtraction.

What to check or record

1. Record chemistry and capacity-rating basis.
2. Use manufacturer evidence where available.
3. Review after changing battery technology.
4. Evaluate a known full-charge-to-discharge cycle rather than adjusting values to fit one screenshot.

No. It affects time-remaining calculations and related alarm behaviour, not ESS minimum-SoC control or a BMS disconnect.

Time-to-go estimates how long the present consumption pattern can continue before the configured floor. It changes with load and is not guaranteed runtime. Protection and disconnection require appropriate separate devices and controls. Keep these concepts apart when evaluating a percentage suggested in a forum answer.

What to check or record

1. Identify whether the setting belongs to a monitor, ESS or BMS.
2. Set an appropriate operational warning reserve.
3. Check which equipment actually stops loads.
4. Use consumption trends as well as instantaneous time estimates.

They may use different measurement points, algorithms or selected sources. Confirm which monitor the GX overview uses first.

Compare device names and timestamps, and confirm the same bank is being described. Internal battery consumption may be invisible to an external shunt, while a BMS estimate has its own calibration behaviour. Disagreement does not automatically prove either is correct. Follow compatibility instructions for the required SoC source in managed systems.

What to check or record

1. Record simultaneous readings from individual device pages.
2. Confirm GX battery-monitor selection.
3. Check current coverage and genuine shunt synchronisation.
4. Use manufacturer integration guidance before changing the system source.

Use this worksheet after the electrical design and installation have been checked. It separates hardware limits, battery settings and proof of operation.

1. Identify the hardware. Record the full MPPT model and firmware, battery voltage and chemistry, battery model, panel model, series-module count and parallel-string count. Keep panel and battery datasheets. An array described only as “600 W” cannot be checked for voltage or current compatibility.

2. Confirm design limits. Have the installer verify cold open-circuit voltage, hot operating voltage, maximum PV short-circuit current, connector limits, protection and model-specific start-up requirements. Use the approved design minimum temperature. A sunny-day operating voltage cannot establish compliance with the cold-voltage limit.

3. Establish control. Record standalone operation, VE.Smart or GX/DVCC management. For managed batteries, retain compatibility instructions and identify which device provides charge permissions and targets. For standalone charging, obtain the complete approved profile before entering values.

4. Review settings. Check battery voltage, current limit, absorption/float behaviour, timing, temperature compensation and cold-charge prevention. Identify the real temperature source. Include other chargers when evaluating the combined current.

5. Prove operation. Save settings and capture status in available sunlight. Record stage, PV voltage/power, battery voltage/current and limiting reason. Verify that behaviour agrees with battery state and control mode. Retain these readings to distinguish later seasonal changes from faults.

What to check or record

1. Required evidence: battery and panel datasheets, string plan and exact charger model.
2. Required entries: approved profile, current limit, control and sensing configuration.
3. Required outcome: credible readings and no unresolved off reason or alarm.
4. Physical PV testing and protective-device selection belong with the installer.

A DC-DC installation needs an appropriate profile and dependable source protection. A short engine-on test alone demonstrates neither.

1. Identify equipment and vehicle. Record the exact Orion model, voltage conversion, isolation and firmware. Record both battery types, alternator type and vehicle-approved connection/control provisions. Distinguish a genuine engine-running signal from one merely live with the ignition.

2. Establish current budgets. Obtain continuous source capacity allowing for vehicle loads, idle running and temperature. Separately record the auxiliary battery charge limit and all other charging sources. On Orion XS, document input and output current limits individually; amperes on the two sides need not match.

3. Set the output profile. Select charger mode for battery charging. Compare all fields with the auxiliary battery instructions: voltage, duration, temperature and BMS permission. Record any GX/DVCC-controlled targets. Use the exact manual for remote and BMS arrangements.

4. Define control logic. Record start, delayed-start, delay and shutdown values plus separate lockout/restart settings where used. Base commissioning on actual input-voltage behaviour and the approved vehicle arrangement. Do not remove protection without establishing its required replacement.

5. Test representative conditions. Log input/output volts and amps at idle, in normal operation and after warming up. A passenger or technician should collect driving data. Confirm stopping after engine shutdown, including with shore or solar charging present. Save settings and explain normal tapering to the owner.

What to check or record

1. Use vehicle-specific guidance, not another owner’s thresholds.
2. Investigate voltage drop or insufficient source capacity before lowering protection settings.
3. Verify the approved BMS charge-disconnect control.
4. Include an engine-off parking check in handover.

A useful percentage begins with a correct measuring path and known reference, not the 100% button. Keep this record with the installation.

1. Define the bank. Record chemistry, model, bank voltage, series/parallel arrangement and rated Ah at the relevant discharge rate. Calculate Ah at bank voltage: two 12 V 100 Ah batteries in series give 24 V 100 Ah, not 24 V 200 Ah. This is an arithmetic example; use only manufacturer-approved battery combinations.

2. Confirm measurement. Have the installer check that intended charging and load currents pass through the shunt. Record any internal battery consumption or circuits outside its view. Verify direction with known charging and discharging. Correct voltage alone does not prove that all current is measured.

3. Configure the monitor. Set capacity, then chemistry-appropriate Peukert and efficiency parameters. Relate charged voltage, tail current and detection time to the real charging profile. Record reset behaviour, alarm reserve and auxiliary-input use. Charged voltage is a recognition threshold, not a charger setpoint.

4. Establish a full reference. Complete the battery’s documented charge process and inspect voltage/current. Confirm automatic synchronisation at the right time. Manually synchronise only when fullness is independently established. Zero calibration is separate and requires certainty that no real current flows.

5. Validate over time. Observe a realistic discharge/recharge cycle for premature jumps or missed synchronisation. If GX or BMS percentages disagree, identify the selected source first. Preserve settings and trends as the baseline for later diagnosis.

What to check or record

1. Capacity: Ah of the measured bank at its actual voltage.
2. Full recognition: voltage, percentage-based tail current and time together.
3. Protection: monitor alarms do not replace BMS or load-disconnect equipment.
4. Success: credible current and repeatable full-charge recognition.

A GX device brings compatible equipment together for monitoring and, when configured for it, coordinated system control.

Think of the GX as the point where device information meets system decisions. It can show battery data, inverter operation and solar production, and pass information to VRM. Its screen is not the charger itself. A healthy-looking dashboard does not prove every charger is connected, every measurement is correct or the battery protection has been commissioned. Start with an inventory of the real devices and compare it with the GX device list.

What to check or record

1. Record the GX model and Venus OS version.
2. Check that every expected device appears with live data.
3. Identify which device measures the battery and which BMS controls it.
4. Keep the power-equipment manuals alongside the GX manual.

Record the exact GX hardware revision, not just the name Cerbo, and list the interfaces your system needs.

Different generations can have different port capabilities. A photo from another installation may show a dedicated BMS port, a configurable CAN interface or a USB port with a different role. List the inverter connection, managed-battery connection, solar chargers, meters and display separately. Then match each one to the connection chapter for your GX model. This avoids buying a cable that fits physically but cannot carry the required protocol.

What to check or record

1. Copy the model and part number from the label.
2. Count separate CAN buses rather than only RJ45 sockets.
3. Check which USB sockets support data on that revision.
4. Reserve the Ethernet LAN port for the network connection.

Prepare a system inventory, network details, the intended battery-data source and the owner's VRM account.

A useful commissioning sheet has one row per device: exact model, firmware, connection type, system role and who supplies its settings. Add the operating goal, such as home ESS, off-grid or mobile backup. Keep network credentials in the owner's secure records, not a public worksheet. Enter descriptive device names so the main battery shunt cannot be confused with a DC-load meter later.

What to check or record

1. Know which battery monitor or managed BMS represents the complete bank.
2. Record the router connection method and whether DHCP is available.
3. Agree who owns the VRM installation and who needs access.
4. Record existing settings before making a change.

Basic local operation and cloud services are different. An internet outage is not the same as losing the local BMS connection.

A correctly commissioned system can perform its local control functions without continuous cloud access, but remote viewing, uploads and cloud-dependent functions need connectivity. Assess each feature separately instead of assuming that an offline VRM symbol means the inverter has stopped. Before an unattended installation is handed over, test the intended behaviour with internet unavailable and confirm the limits of any schedule or service that relies on online information.

What to check or record

1. Compare the local GX screen with the VRM last-contact time.
2. Check the actual inverter and BMS locally.
3. Document which optional services need the internet.
4. Do not bypass battery protection to recover a cloud connection.

These are different ways to reach information; success through one route does not prove that the others work.

Local Remote Console reaches the GX across the local network or its supported access-point connection. VRM reaches the installation through the internet. Bluetooth on a GX is mainly a route for supported discovery and initial network setup; do not assume it behaves like the full live interface of a Bluetooth solar charger. Name the route when reporting a problem: phone to GX access point, phone to home router, or remote VRM access.

What to check or record

1. Confirm which Wi-Fi network the phone has joined.
2. Try the GX address shown by its local network settings.
3. Check VRM logging separately from local access.
4. Record whether failure occurs locally, remotely or both.

Start at the GX: its last-contact time and connection error distinguish a network problem from a stale display.

Write down the error before rebooting. Confirm that the GX has connected to the intended router, rather than an installer's hotspot that is no longer present. Check whether other devices on that same network have internet access. A working phone on mobile data does not prove the GX network works. Compare the VRM last-contact timestamp with the logging interval and look for unsent stored records.

What to check or record

1. Check Ethernet link or Wi-Fi connection status.
2. Record IP address, gateway and DNS status without publishing credentials.
3. Read the exact connection error and timestamp.
4. Investigate the router path before changing inverter settings.

Historical logging and an interactive console are separate checks; a graph can remain visible without a working live connection.

Confirm that the data is current, then check the GX remote-access setting and the signed-in user's permissions. Note whether the classic or newer interface is involved. A slow connection, browser state, incompatible firmware combination or third-party software can affect the console differently from simple logging. Record the point at which opening fails instead of treating every console problem as an inverter fault.

What to check or record

1. Compare the current time with the last successful contact.
2. Check Remote Console is enabled for the intended access mode.
3. Try a supported, updated browser and record the result.
4. List custom Venus OS software in the support report.

Access may be read-only, the value may be externally controlled, or another control mechanism may be writing it.

Distinguish a setting that never saved from a live limit that is supposed to change. A BMS-reported charge limit is not a fixed user preference. For a genuine user setting, check both account permissions and the GX VRM access mode. If automation controls the same parameter, identify its owner and intended behaviour before making competing changes. Reopen the field after saving and verify the actual operating result.

What to check or record

1. Record the field, old value, attempted value and time.
2. Check whether the interface is read-only.
3. Identify BMS, ESS, Dynamic ESS or external control where relevant.
4. Change one documented parameter at a time and recheck it.

Use the source that represents the actual battery bank and is required by the documented system integration.

A system can contain a managed BMS, SmartShunt and VE.Bus estimate at once. They are not automatically interchangeable. Confirm which device measures all charge and discharge paths, and whether the battery integration requires its BMS data. A shunt configured as a DC-load meter is not the bank's state-of-charge monitor. Where separate monitor and controlling-BMS choices are supported, verify both rather than assuming one selection configures everything.

What to check or record

1. Identify the bank represented by each monitor.
2. Check the selected monitor in GX system setup.
3. Verify the controlling BMS separately where that choice is available.
4. Compare live values before relying on SoC-based automation.

Check measurement coverage and device roles first; a calculated system value is not necessarily a directly measured cable current.

A charger missing from the GX device list may still produce power. The dashboard then has an incomplete view of where energy enters the system. Likewise, a meter assigned to the wrong role can place a real measurement in the wrong part of the diagram. List every charging source and load, marking whether it is measured, reported by a device or calculated from other values.

What to check or record

1. Compare the expected device count with the live list.
2. Confirm battery, grid, PV-inverter and DC-meter roles.
3. Compare measurements from the same moment and with consistent units.
4. Investigate missing communications before assuming an unexplained battery fault.

Treat this as a communications commissioning problem before changing charge voltages.

Start with the integration guide for the exact battery model and revision. Confirm that it specifies a supported protocol, the required battery configuration and the correct cable. A cable that works for another battery brand may have different wiring. Check the GX port's profile and the battery-side master/address requirements. A displayed battery name is only the first success: limits and measurements must also remain live.

What to check or record

1. Record the battery model, BMS firmware and active protocol.
2. Match the cable part number and direction to the integration guide.
3. Check the assigned CAN profile and documented termination.
4. Confirm fresh SoC, voltage, CVL, CCL and DCL where provided.

Use the profile required by the exact battery integration; neither speed is a universal Victron battery setting.

The physical CAN connection and the selected protocol must agree. A system may need a VE.Can bus for Victron devices and a separate BMS-Can bus for its battery. Two sockets can belong to the same bus, so counting sockets is not enough. Check your GX revision and documentation before putting a battery and another device on the same network. Randomly trying speeds can obscure the original fault.

What to check or record

1. Read the battery's specified CAN profile and speed.
2. Identify which physical sockets belong to each GX CAN interface.
3. Keep incompatible bus profiles on separate interfaces.
4. Follow GX and battery-side termination instructions.

No. Matching RJ45 connectors do not mean matching electrical interfaces or protocols.

Ethernet LAN, VE.Bus and CAN are separate connections with different roles. The connector shape is not a compatibility test. Trace each cable between the labels on both devices and the relevant wiring diagram. Battery CAN cables may also require a particular pin assignment. Label the cable ends during commissioning so a later network change does not accidentally move a control cable to a router.

What to check or record

1. Use the Ethernet port only for the intended LAN connection.
2. Use the documented VE.Bus route for compatible inverter/chargers.
3. Use the specified cable for battery-to-GX CAN communication.
4. Have uncertain physical wiring checked before energising or reconnecting equipment.

DVCC is a control feature, so its use depends on battery compatibility, connected equipment and firmware.

Do not copy the setting solely because another system uses lithium batteries. Determine whether the system uses a managed communicating BMS, a Victron BMS arrangement or locally configured charging. Some integrations require or automatically enable DVCC; others need specific shared-sensing settings. Check compatibility before switching it, and confirm that every charger expected to follow the system is actually connected and supported.

What to check or record

1. Identify the exact battery and BMS integration.
2. Check DVCC requirements in its current integration guide.
3. Record firmware versions for GX, inverter/charger and solar chargers.
4. Verify the resulting control status and limits after commissioning.

They describe the battery's present permitted charging voltage, charging current and discharging current.

Read them alongside actual voltage, current, temperature and SoC. A limit is not a promise that the charger will deliver that amount, and a datasheet maximum is not a command to use it at every moment. The battery may lower its limits because of its internal operating conditions. Save a simultaneous snapshot when investigating a restriction; readings taken at different times can suggest a contradiction that never existed.

What to check or record

1. Record CVL in volts and CCL/DCL in amps.
2. Distinguish permitted current from measured current.
3. Check battery alarms, temperature and relevant cell information.
4. Escalate unexplained BMS restrictions through the battery supplier rather than overriding protection.

The system still has other limits. Raising one setting cannot remove a lower BMS, charger or source limit.

Compare the full chain: the battery's present permission, the user limit, each charger's local maximum, available solar or AC power, and the current operating state. For example, changing a system limit to a value above an individual charger's configured maximum does not increase that charger's capability. The useful question is which limit is currently active, not which field accepts the largest number.

What to check or record

1. Read the live BMS current limit first.
2. Check the affected charger's local current setting.
3. Check source availability and charging state at the same time.
4. Keep settings within the battery and installation design limits.

Chargers may supply active loads as well as the battery, so their total output is not always net battery charge current.

Compare measurement locations before calling a limit incorrect. A shunt or BMS may show the net current at the battery while the chargers report their individual outputs. Load compensation also depends on the system's supported and correctly configured measurements. In ESS, enabling DC-MPPT export changes how the DVCC current limit applies to those solar chargers; it must not be interpreted as a universal cap on every displayed output.

What to check or record

1. Capture charger outputs, battery current and loads together.
2. Identify whether DC-system current is actually measured.
3. Check the ESS DC-MPPT export setting where applicable.
4. Use the official DVCC explanation for the installed topology.

No. Physical connection to the same battery does not make a charger part of GX coordinated control.

Make a source inventory that includes alternators, external mains chargers and equipment without a supported GX control connection. Their output can still reach the battery even when a Victron device has reduced its own current. A battery monitor measuring the result does not by itself grant the GX control over an external charger. The installation must provide the required battery-protection and charging-control arrangement for each source.

What to check or record

1. List every source capable of charging the bank.
2. Mark whether each source is monitored, controlled, both or neither.
3. Check the documented treatment of any DC-system meter.
4. Have the installer verify the total allowed charging behaviour.

No. The current GX manual reserves this option for initial balancing of 15s Pylontech batteries; it is not a general charging adjustment or BMS override.

The current Cerbo GX configuration manual says Limit managed battery charge voltage is intended only for initial balancing of 15s Pylontech batteries and should not be used for other purposes. It limits voltage; it does not force a lower BMS request upward. If a battery stops below the voltage you expected, record its requested CVL and actual voltage, then follow the exact battery integration instructions. Investigate cell behaviour, temperature and alarms with the supplier instead of copying another battery’s voltage or disabling BMS control.

What to check or record

1. Confirm that the documented 15s Pylontech initial-balancing procedure applies.
2. Record the BMS CVL and any user-entered ceiling.
3. Use the exact battery’s supported commissioning and recovery instructions.
4. Do not disable BMS control or use this option as a general optimisation setting.

Shared voltage, temperature and current sensing have different jobs; the right combination depends on the battery and system.

Identify the source of each measurement before sharing it. A temperature measured at a charger is not necessarily the battery temperature. A current value from a load meter is not automatically suitable for battery charging decisions. The compatibility guidance may require a feature to be on, off or automatically managed. With shared voltage sensing, a charger's terminal reading can differ from the battery reading without proving that the battery is being overcharged.

What to check or record

1. Check the integration's SVS, STS and SCS recommendations individually.
2. Select the documented sensor or monitor source.
3. Compare battery and charger measurement locations.
4. Do not enable lead-acid temperature compensation assumptions for an unspecified lithium battery.

Choose the tool for the device and task, rather than treating every Victron screen as the same configuration interface.

VictronConnect handles supported product settings through supported local or remote connections. Remote Console exposes the GX system interface. VRM provides installation monitoring and supported remote services. VE.Bus inverter/charger configuration has its own supported workflow, including Remote VEConfigure where applicable. Being able to view a product in one app does not mean every setting can be edited through that connection.

What to check or record

1. Write down the exact product and setting you need to change.
2. Check the supported configuration method for that model.
3. Distinguish local Bluetooth, wired access and VRM remote access.
4. Use a settings backup before a significant configuration change.

Check product capability, power, range and phone permissions before assuming the device is faulty.

The product must support the connection method being used; not every Victron product has built-in Bluetooth. Look for the exact model in the compatibility guidance. A device can be visible at a distance yet fail to establish a stable connection. Another phone may already be connected. If the product was recently updated, also check its original name or serial identifier rather than searching only for a custom name.

What to check or record

1. Open the connection from inside VictronConnect.
2. Confirm Bluetooth and the required app permissions are enabled.
3. Move close to the equipment and disconnect another active phone session.
4. Record whether a supported wired connection works, if available.

Separate a pairing problem from a device-configuration problem, and preserve the working settings while investigating.

Confirm the correct device identity and whether its PIN was previously changed. Old pairing information on the phone can conflict with the current device credentials. Follow the app manual's pairing and authorised PIN-recovery procedure for that product instead of repeatedly resetting its charging configuration. If another phone connects successfully, record that comparison: it helps narrow the issue to the phone, app or stored pairing.

What to check or record

1. Record phone model, operating system and VictronConnect version.
2. Close other active sessions to the same product.
3. Follow the official procedure for removing stale pairing and reconnecting.
4. Keep PINs, PUKs and recovery information out of public screenshots.

Viewing a VE.Bus device through VictronConnect-Remote does not provide the same configuration access as a supported local connection.

The remote compatibility rules differ by interface and product family. For supported VE.Bus inverter/chargers, VictronConnect-Remote provides overview and details, while remote settings use the Remote VEConfigure workflow. This distinction can look like a missing feature after changing phone, app or connection route. Confirm which path worked previously before assuming a firmware regression. Other product families have their own remote-configuration requirements.

What to check or record

1. Identify whether the device is using VE.Bus, VE.Direct or VE.Can.
2. Check the current VictronConnect-Remote compatibility section.
3. Use the documented Remote VEConfigure route where applicable.
4. Arrange appropriate access and a recovery plan before remote changes.

Use a planned update strategy that considers compatibility, the reason for updating and the consequences of an interrupted system.

During new commissioning or fault investigation, check the supported firmware requirements and relevant release notes. For an established installation, record what the update is intended to fix or add. An app update, Venus OS update and inverter firmware update are different operations. A beta test result is not automatically applicable to a production release. Coordinate changes so that the complete system remains within its documented compatibility requirements.

What to check or record

1. Record all current versions before updating anything.
2. Read the release notes and battery-integration requirements.
3. Choose a suitable maintenance window with reliable power and access.
4. Recheck monitoring, control and alarms after the update.

Save the available product configuration files and a human-readable record of the whole installation.

A firmware backup and a settings backup serve different purposes. A GX's stored previous firmware provides a boot option; it is not a complete record of every connected product's configuration. Save supported VictronConnect settings files and the appropriate inverter configuration, and record battery, meter and system selections. Name each file with the device, date and version so it can be matched to the correct hardware later.

What to check or record

1. Capture the current device inventory and firmware versions.
2. Export settings using the supported tool for each product.
3. Record the intended change and how success will be checked.
4. Keep a tested recovery route and avoid importing another installation's settings blindly.

First compare the hardware, firmware and user-interface generation; a moved or renamed menu is not proof of a missing feature.

Older posts often use the classic GX menu layout. Current documentation groups settings differently, so a reference to Settings > DVCC may correspond to charge-control settings under system setup on a newer interface. Access level, connected equipment and enabled features can also affect what appears. Search by the function's name and check the manual for your device instead of copying a screenshot's position.

What to check or record

1. Record whether you are using the classic or newer GX interface.
2. Check the installed Venus OS version.
3. Confirm the relevant device is detected and supported.
4. Use the current manual's search for the setting name or abbreviation.

Look for a pattern and check the restart cause before treating rebooting as a permanent fix.

The GX can have an optional network watchdog that restarts it after prolonged loss of VRM contact. Power-supply problems, resource pressure or added software can also require investigation. Record the restart times and compare them with network failures and load changes. If the restart interval is regular, check whether it matches a configured no-contact delay. Avoid changing several unrelated settings at once, because that removes useful evidence.

What to check or record

1. Inspect the VRM no-contact reboot option and delay.
2. Record the GX supply arrangement for the installer.
3. List third-party packages and active integrations.
4. Capture any GX error code and contact the supplier if restarts persist.

Use a reset only as a deliberate recovery step with the correct procedure and a complete recommissioning plan.

A reset can remove the very settings needed to reconnect the system, and a Venus OS reinstall is a different operation again. Neither should be used to hide an unresolved electrical or battery alarm. First collect the error, versions, device list and timing. Check whether the official troubleshooting chapter identifies a specific recovery procedure or a hardware fault that needs service. Keep access to the original configuration and local assistance where required.

What to check or record

1. Save settings and screenshots before a supported reset.
2. Identify which device would be reset and what it will lose.
3. Plan how network, battery and control selections will be restored.
4. Verify the complete system after recovery, not only that the menu opens.

Provide a compact system inventory, a time-stamped symptom and the relevant settings and measurements from the same event.

'Latest firmware' and 'the battery is not charging' leave important questions unanswered. Give exact versions, the connection method, operating mode and the result you expected. Include what changed before the issue and whether it occurs locally, remotely or both. A simple labelled diagram is often more useful than a photograph of several similar blue boxes. Share service reports with the appropriate support recipient and remove private access information from public posts.

What to check or record

1. List device and battery models, firmware and system topology.
2. Include the exact alarm text and the time, date and time zone.
3. Capture relevant limits, actual values and device statuses together.
4. List attempted changes and their outcomes, including custom software.

Use this sequence to establish a reliable monitoring connection and record the information needed for later support.

Begin after the physical installation has been checked. Prepare the GX model and hardware revision, the expected device list, the installation's operating purpose and the owner's network and VRM arrangements. Keep passwords in secure owner records. The aim is to prove each connection in stages, so a later failure can be located without changing charging parameters.

Use the local interface as the starting point. Follow the hardware manual for access through a display, the local network or the supported access point. A phone connected to the GX access point may not be using its usual home network. Menu groupings vary with Venus OS and interface version; look for the named function rather than relying on a screenshot's location.

Finish with a short handover record showing the working device inventory, current firmware, selected battery monitor, controlling BMS where applicable, and successful VRM contact. Explain which features still work locally if internet access is lost. Test remote access from outside the local Wi-Fi so that a working local connection is not mistaken for proven remote operation.

What to check or record

1. Inventory: compare every installed device with the GX device list and give ambiguous devices descriptive names.
2. Network: use the intended Ethernet or Wi-Fi connection, normally with DHCP; confirm connected state, address, gateway and DNS before changing advanced network settings.
3. VRM: register the correct installation to the agreed owner account, verify its identity and set the access level needed for monitoring or authorised control.
4. Connection proof: record the last-contact timestamp, logging interval, connection status and any stored records; confirm that fresh measurements reach VRM.
5. Access: use supported VRM remote features rather than opening inbound router ports to the GX; give each person only the access needed and protect account credentials.
6. Handover: save screenshots and relevant configuration files, confirm a local recovery route, and document who may change settings.

Treat detection, measurements, limits and actual charger behaviour as four separate commissioning checks.

Start with the integration guide for the exact battery, BMS and revision. Record the required firmware, cable, protocol, CAN profile, master/module arrangement and any settings that are automatically managed. There is no safe generic voltage or current recipe for every lithium battery. A forum configuration can help identify a menu, but it cannot replace the supplier's values or the installation design.

After the qualified installer has confirmed wiring, check communication in the GX device list. Record live voltage, current, temperature and state of charge, plus CVL, CCL and DCL where the battery provides them. Verify that values continue to update. Merely seeing a battery name does not prove that all control data is valid or that every charger is listening.

Use the required DVCC and shared-sensing configuration for that integration. In newer GX interfaces, look under system setup and charge control; older manuals may refer directly to DVCC. Keep the purpose of each setting clear: the BMS communicates present permissions, user limits can impose additional restrictions, and local charger limits still matter. Any unsupported or unconnected source needs its own documented control arrangement.

Complete a controlled operating check and retain the results. Compare actual battery current with charger output and active loads at the same time. Investigate unexplained differences using the installed topology, including any DC-system measurements or ESS export settings. Do not defeat BMS protection to make the result resemble an example screenshot.

What to check or record

1. Confirm the exact integration, hardware revision and firmware combination.
2. Verify the specified cable, CAN profile and termination at both ends according to the relevant manuals.
3. Check battery-monitor and controlling-BMS selections where separately available.
4. Apply only documented DVCC, voltage-ceiling and shared-sensing settings.
5. Observe normal charge and discharge behaviour and record alarms, limits and measurements.
6. Save the commissioned configuration and escalate unresolved battery permissions to the appropriate supplier.

Replace a broad complaint with a reproducible event, a system map and evidence captured before the settings are changed.

Write one sentence describing the difference between expected and observed behaviour. For example: the GX remained accessible locally, but VRM stopped receiving new data at a stated time. Keep that observation separate from a theory about the cause. Record the time zone so a remote helper can compare the event with logs.

Build an inventory of the exact GX, inverter/charger, battery/BMS, solar chargers, meters and other charging sources. Include hardware revisions and actual firmware numbers, not just 'latest'. State the system type and topology: single or multiple units, grid-connected or off-grid, AC- or DC-coupled solar, and how the battery and each device communicate. A labelled sketch can make these relationships much clearer.

Attach a small, relevant evidence set. For charging issues, capture BMS permissions, actual battery voltage/current, charger status, active loads and any current or voltage ceilings from the same moment. For network issues, include GX connection status and VRM last contact. For app issues, include phone/computer model, operating system, app version and the exact local or remote connection route.

Finally, list changes made just before the issue and each test already performed. State whether the result is repeatable and what restores normal operation. Disclose custom Venus OS packages or automation because they may change control behaviour. The goal is a clear starting point for diagnosis, not a long unstructured history.

What to check or record

1. Save exact alarm text, screenshots and the time of the event before rebooting.
2. Include only configuration pages relevant to the symptom; keep the full backup privately.
3. Use the official VictronConnect service-report procedure when app support requests it.
4. Remove passwords, PINs, tokens, personal information and public access links from forum attachments.
5. Share installer access through the intended account controls rather than posting credentials.
6. After a change, report the observed result and recheck the original symptom.

The grid setpoint is a power-flow target in watts during self-consumption, not a battery voltage or an export protection device.

First establish the sign convention at the configured grid meter. A small positive target deliberately leaves a little import, giving the controller room to respond when loads change. The ESS manual documents a 50 W default; that is a product default to understand, not a universal recommendation for every installation. Larger or rapidly changing systems may need different commissioning decisions.

Compare the setpoint with simultaneous grid power, PV power, battery current and active control limits. A full battery, a BMS restriction, insufficient inverter capability or a different controller can prevent the requested flow. Repeatedly changing the target without identifying the limiting device can hide the real cause.

Inspect a short time series rather than one dashboard sample. A kettle switching off can create a brief export excursion even when the average target is import. Contractual export compliance must be addressed by the approved system design.

What to check or record

1. Record watts and sign, meter role, active ESS mode and any external controller.
2. Test a small normal load change and compare the measured settling behaviour.
3. Do not infer that a negative target permits export under the installation agreement.

Peak shaving manages an electrical demand constraint; a tariff may calculate demand over a different location, period or phase combination.

The relevant limit is the accepted AC-input current and the supported ESS peak-shaving behaviour. The ESS configuration distinguishes assistance above minimum SoC from assistance that may continue below it. This concerns critical loads on the inverter AC output; it must not be assumed to cap every load measured elsewhere at the grid connection.

Write down what the electricity bill actually measures: instantaneous current, an interval-average peak, the sum of phases or a specific phase. A setting in amperes per input is not automatically the same as a monthly billing limit in kilowatts. Large loads outside AC-out can remain outside the local input-current control.

After a peak, battery reserve may need replenishment. Include that recovery energy and the available reserve in the operating plan. The documented hysteresis means recharge and discharge need not switch at exactly the same displayed percentage.

What to check or record

1. Map the controlled loads and the billing measurement point on the drawing.
2. Record the permitted input current, reserve policy and expected peak duration.
3. Validate with recorded interval energy and power; do not promise a lower bill from one successful instantaneous test.

Reaching the charging target and allowing battery self-consumption during the remaining window are separate decisions.

A scheduled ESS window has a start day, start time, duration, SoC target and self-consumption behaviour. The target stops scheduled charging at the requested state of charge. It does not necessarily end the window or permit immediate discharge.

With the documented PV behaviour, available solar can feed loads while the battery remains reserved until the window finishes. With PV & Battery, self-consumption can use the battery above the scheduled SoC limit. This explains why a battery already above its target can coexist with grid import during a cheap-rate period.

Check the actual time and selected days as well as the target. An overnight period can cross a calendar boundary, and overlapping entries make visual interpretation harder. Test one clear window first, then add the remaining schedule. A schedule does not remove BMS, charger or supply limits.

What to check or record

1. Record the complete window, including the self-consumption option.
2. Observe power flows before the target, after the target and after the end time.
3. Keep a screenshot of the active schedule and the SoC source used by ESS.

Compare required battery energy with realistic net charging power and the available time, allowing for loads and charging taper.

As an illustrative calculation, raising a 10 kWh bank from 30% to 70% represents approximately 4 kWh of stored energy. At an average net battery charging power of 2 kW that requires about 2 hours. These figures explain the calculation; they are not settings for a particular battery. Conversion losses mean the imported energy will be greater.

Use net battery charging power, not the inverter nameplate or the total AC supply. Household demand, input-current restrictions, other phases, temperature and BMS limits can all reduce what reaches the battery. Charging near full may taper, so a constant-power estimate becomes optimistic.

If the target is repeatedly missed, compare actual battery energy added during the window with the forecast calculation. Extend the permitted window or revise the operational target within the intended reserve policy; do not raise protective limits merely to force completion.

What to check or record

1. Check capacity units and the reliability of the displayed SoC.
2. Record start/end SoC, battery power, charging restriction and normal load.
3. Separate insufficient time from a communications fault or disabled charging state.

A supported ESS self-consumption setting can distinguish critical AC-output loads from non-essential loads, but it depends on the physical layout.

First identify which circuits are actually connected to AC-out and which remain in parallel with the inverter on the grid side. A label in the software does not move a circuit into the backup distribution board. The system also needs the appropriate grid measurement to distinguish these power flows.

The ESS manual describes self-consumption for all system loads or only critical loads in the applicable configuration. The option is tied to use of the inverter AC output and the relevant metering/feed-in arrangement. If the option is absent, verify the configuration and firmware instead of assuming a hidden menu must be enabled.

Observe a load on each side separately. The expected outcome is that the chosen critical-load policy controls battery contribution while the non-essential circuit follows its designed source. During a grid outage, only the engineered backup circuits remain supplied, regardless of the daytime self-consumption label.

What to check or record

1. Mark critical and non-essential circuits on the installation drawing.
2. Record grid-meter selection and whether AC output is in use.
3. Test the policy and outage behaviour with the installer; retain the resulting power-flow record.

Exporting surplus DC solar and limiting battery charging are related but different control tasks; the ESS manual documents an important interaction.

In the relevant ESS feed-in arrangement, solar power serves loads, charges the battery and can then be exported. The manual warns that enabling feed-in of excess solar charger power changes the applicability of the GX DVCC charge-current limit for maximising solar output. Do not treat that single system field as the only protection of a small battery bank.

The installer must check each solar charger current limit, the supported battery/BMS integration and what happens when grid export suddenly disappears. The same installed solar array can produce a very different battery-side condition after an outage or a large load disconnects.

Before changing feed-in permission, save the existing configuration and identify which source supplies voltage and current limits. Verify live BMS requests and actual net battery current in the intended operating states. A maximum-output solar strategy is only appropriate when the complete installation remains within its documented limits.

What to check or record

1. Record feed-in switches and per-controller current limits.
2. Confirm the exact ESS/DVCC/battery integration instructions.
3. Have the installer validate export loss and restricted-charge scenarios.

The export target alone is insufficient: the PV inverter must support the required control path and have the correct communications settings.

For the documented Fronius integration, relevant checks include supported hardware and firmware, Modbus TCP data export, the specified SunSpec model and the priority of Modbus control. A device appearing in the GX overview proves monitoring, not necessarily that remote power limiting is active.

The active-status indicator describes current operation. It can remain inactive when there is no available PV or AC input is absent, as well as when communications or configuration are wrong. Interpret it alongside the actual operating state rather than treating every No indication as a fault.

Loss-of-communications behaviour is a separate design choice. The official integration explains the PV-side fallback configuration. Check this with the installer so loss of a network connection cannot silently leave an undesired unrestricted output. Do not generalise the Fronius procedure to another brand with similar-looking menus.

What to check or record

1. List exact PV inverter model, firmware, control method and network address.
2. Distinguish monitoring, active limiting and failure behaviour in the test record.
3. Use the linked integration instructions for the approved metering arrangement.

For AC PV on the inverter output, use the documented continuous inverter/charger power at 25 °C and the applicable available PV power—not a casual comparison of model names.

An AC-coupled PV inverter can continue supplying energy briefly after a large load disappears. The Victron inverter/charger must absorb and regulate that energy while frequency control reduces PV production. This transient, especially with a nearly full battery, explains why the sizing rule is important even when normal daily power looks acceptable.

The current official guidance defines the comparison using continuous output power at 25 °C. Check the exact datasheet: a model labelled in VA can have a lower continuous rating in watts. The guidance also explains how to treat an oversized or undersized panel array relative to the PV inverter.

Battery capacity, charge acceptance, correct frequency-response configuration and a recovery charging source remain separate requirements. A software export limit does not erase the physical AC-coupling limit. Document the calculation for each phase and applicable parallel group with the installer.

What to check or record

1. Record the exact continuous watt rating rather than only the VA model number.
2. Identify which PV is on AC-out and which is on the grid side.
3. Check battery sizing and AC-PV shutdown/recovery behaviour as well as the power ratio.

On relevant MultiPlus/Quattro models the auxiliary output has its own relay and default non-essential-load behaviour.

AC-in-2 and AC-out-2 are different terminals with different jobs. A second input is another source; the auxiliary output normally supplies loads that should not run from the battery. Its default relay behaviour can therefore remove that output immediately when the unit starts inverting.

The documented reconnection delay on applicable models allows the accepted source, particularly a generator, to stabilise. This can make AC-out-1 appear normal while AC-out-2 is still unavailable. Check the exact hardware manual because output ratings and programmable behaviour differ between models and revisions.

Existing Assistants or other control arrangements can modify the default behaviour on supported hardware. Before diagnosing a relay fault, retrieve the installed configuration and identify every rule that controls it. Do not assume the main transfer-switch current rating is also the auxiliary-output rating.

What to check or record

1. Record exact model, output-terminal labels and installed Assistants.
2. Check the designed rating and protection of each output separately.
3. Measure output behaviour through a controlled source-loss/return test performed by the installer.

The normal standalone inverter controls and ESS control logic do not use every checkbox in the same way.

The ESS configuration manual explicitly states that the ordinary VEConfigure PowerAssist and Dynamic Current Limiter settings are disabled and ignored when the ESS Assistant is installed. ESS has its own energy-management and peak-shaving behaviour. Advice from a standalone camper or generator installation may therefore be inappropriate for a home ESS.

Begin by identifying whether the ESS Assistant is present and which operating strategy is active. Then check the applicable ESS options, AC-input limit, battery restrictions and actual load position. A load outside the inverter AC output can be relevant to the grid meter while not being controlled by the same local current-limiting mechanism.

Keep generator testing separate from ordinary grid-connected operation. Grid code, source classification and protection requirements still apply; changing a checkbox to imitate a forum example can alter an unrelated function without solving the problem. Document the control context before making comparisons.

What to check or record

1. Save the Assistant list and relevant ESS settings.
2. Identify whether the symptom occurs on grid, generator or inverter operation.
3. Use the manual for that architecture instead of combining settings from different applications.

Treat the auxiliary starter charging connection as its documented limited function, not as another main charging output.

Check the exact model before looking for the terminal: the MultiPlus-II connection overview identifies a trickle-charge positive connection on relevant 12 V and 24 V models. Its availability cannot be inferred from a photograph of another MultiPlus. The main battery charger rating does not describe the small auxiliary output.

Confirm the permitted starter-battery voltage, chemistry, current and operating conditions in that product manual. A starter battery with different charging requirements may need a separate suitable charger. Do not assume that choosing a lithium profile for the main bank automatically creates an independent correct profile for the starter battery.

For troubleshooting, record whether the main charger is operating, the voltages at both batteries and the current actually delivered by the auxiliary path. A nearly full starter battery can accept little current normally; a substantial starter-side load can exceed what a maintenance output can replace.

What to check or record

1. Identify the exact auxiliary terminal and its rating from the model documentation.
2. Record both battery specifications and any continuously connected starter loads.
3. Use a properly specified independent charging solution when the auxiliary function does not match the requirement.

State of charge is an estimate; the inverter reacts to the voltage and permissions available at its own operating point.

A high displayed percentage does not prove that voltage remains sufficient during a load surge. A battery cell restriction, low temperature, ageing, a disconnected parallel module or voltage drop in the DC path can all change available power. Conversely, the percentage itself may be wrong because the selected monitor is not measuring the complete bank.

Capture battery voltage at the battery and inverter, battery current, minimum cell voltage where available and the BMS discharge limit at the same moment. A large difference between measurement points points towards the connection path; both readings collapsing together suggests the battery/source needs investigation. Electrical measurements belong with an appropriately equipped installer.

Use the exact alarm and the active architecture to identify the relevant threshold. In ESS, dynamic cut-off behaviour differs from ordinary standalone shutdown settings. Do not simply lower a protection threshold or reset SoC to make the warning disappear.

What to check or record

1. Keep the load event and alarm timestamp together with the measurements.
2. Check that all expected battery modules remain online.
3. Investigate monitor accuracy separately from voltage drop and battery protection.

Ripple is a changing component on the DC supply; its causes include the complete battery path and the way the system is loaded.

The inverter draws rapidly varying current, so it needs a sufficiently low-impedance DC supply. Cable length, cross-section, connectors, fuses, switches, busbars and battery capability all contribute. A single impressive cable size does not prove that every connection or protective component is suitable.

Record the exact alarm, when it occurs and which appliances were starting or changing power. Check whether it appears only on one unit of a parallel installation. The installer should compare the complete DC branches and measurements under representative load, using the model-specific installation requirements rather than replacing components at random.

A normal resting DC voltage cannot rule out a ripple problem. Likewise, lowering the AC load may stop the alarm without correcting the underlying installation. Preserve the configuration and measurement evidence before attempting a remedy; do not disable alarms or bypass fuses to obtain a successful test.

What to check or record

1. Document DC branch lengths, protection components and battery-module status.
2. Check connections and voltage behaviour using the prescribed isolated-work procedure.
3. Repeat a controlled representative load test after the physical cause is corrected.

Continuous output and charging capability depend on temperature and cooling conditions as well as battery state.

Read the continuous ratings at the relevant ambient temperatures in the exact datasheet. The large VA number in a product name is not a guarantee of identical continuous watts inside a warm cupboard. The inverter and charger also share thermal constraints, so a long charging session can change the conditions for a later load.

Check ventilation clearances, airflow paths and whether other equipment heats the enclosure. Record ambient temperature near the product, operating mode, sustained load and any temperature alarm. Fan operation alone does not prove adequate cooling, and a quiet fan does not justify overriding thermal protection.

Distinguish gradual temperature derating from a sudden starting-current overload or BMS restriction. Each requires different evidence. If the system must run a critical load for hours, the design needs the continuous capability under the actual installation conditions, not only a short demonstration while cold.

What to check or record

1. Compare ambient-temperature ratings and the exact product revision.
2. Record load duration and recent charging activity.
3. Have the installer correct cooling or capacity limitations rather than suppressing the alarm.

These controls address different source characteristics and can introduce different compromises; they are not a universal generator preset.

UPS behaviour concerns accepting and transferring a source while maintaining fast transition behaviour. WeakAC changes how the charger tolerates a poor waveform and can reduce charging capability or efficiency. Dynamic Current Limiter, where applicable, helps a small generator respond to changing demand. Their availability and interaction depend on model, firmware and whether ESS is installed.

Begin with measured source voltage/frequency, continuous generator capacity, AC-input current limit and the load profile. A generator engine that keeps running may still have stopped producing accepted AC. Source-quality settings cannot repair inadequate wiring, an overloaded generator or a mechanical fault.

Follow the official diagnostic sequence with the installer and change one variable at a time. Preserve the initial values and observe the effect under the same load. Broadening voltage or frequency acceptance can pass unsuitable power to connected equipment, so it is not a casual cure for disconnections.

What to check or record

1. Record source acceptance, waveform symptoms and firmware before changing settings.
2. Keep ESS and standalone generator advice separate.
3. Do not adjust BoostFactor without the qualified guidance specified in the manual.

Remote permission, input selection and the model’s supported range determine whether that value can be applied.

The GX limit applies to inputs where Overruled by remote is enabled in the inverter configuration. A Quattro can use different permissions for its two inputs, so a setting that worked on shore power may not control the generator input. Check which input is active before diagnosing the remote control.

Some models impose a minimum input-current setting when the relevant PowerAssist function is enabled. A value below the supported range can therefore be raised automatically. The available quick-select buttons are convenient values, not proof that the supply or installation can safely provide them.

For parallel or multiphase installations, interpret the limit using the documented per-phase/system rules. A stored local value is not automatically a protected upper ceiling once remote override is enabled. The approved source protection and operating limits still need to be established in the installation design.

What to check or record

1. Record the active input and each input’s remote-override checkbox.
2. Read back the applied limit after changing it.
3. Confirm supply rating and the meaning of the current value before testing a load.

Search mode deliberately tests for sufficient demand rather than maintaining the same continuous AC output at all times.

On supported standalone products, Search mode reduces idle consumption by briefly checking whether the load is above a configured threshold. Electronic loads with a small standby draw, delayed start or unusual input behaviour may not trigger it reliably. A router, charger or control circuit can therefore behave differently from a simple resistive lamp of similar rated power.

AES and Search mode are not interchangeable. The product manual describes their different methods and limits, including applicability to the system architecture. Do not carry a standalone economy setting into a parallel or ESS installation without checking support.

List the loads that require continuous power and measure their actual standby/start behaviour. Then compare normal inverter mode with the intended economy mode using the same equipment. The useful saving is the measured system saving after accounting for any extra load added merely to keep the inverter awake.

What to check or record

1. Record the configured shutdown/wake thresholds and exact inverter model.
2. Test each essential electronic load, including its recovery after an interruption.
3. Choose a mode that meets the load requirement instead of assuming every low-watt appliance is compatible.

Neutral-earth bonding and residual-current protection depend on the source and operating state, not just whether AC voltage is present.

The relevant inverter/charger models use a ground relay to establish the intended neutral-to-chassis relationship while operating without external AC, then change that relationship before connecting an accepted external source. The installation must provide the protective-earth path required by its fixed, mobile or marine design.

Turning the relay off to silence a nuisance trip can defeat the intended protection. Adding an extra neutral-earth link can also create a wrong arrangement. An autotransformer, external transfer switch, generator or shore supply may require a different documented design. Similar product names do not establish the correct bonding scheme.

Ask the installer to identify the active neutral-earth connection and verify the RCD/protective arrangement in each intended operating mode, including source transfer. Record the exact circuit diagram, protective devices and test results. A successful lamp test or a voltage reading alone does not establish electrical protection.

What to check or record

1. Use the exact model’s installation diagram and applicable local requirements.
2. Do not copy RCD ratings or bonding links from a forum photograph.
3. Have a qualified installer diagnose trips and verify protection after any change.

On the documented Quattro arrangement, accepted AC-in-1 has priority over AC-in-2; source labels and current limits must match the wiring.

A common design connects the generator to the priority input and shore/grid supply to the other input. Starting the generator can then deliberately select it even while the other source remains available. This is selection between sources, not combining their capacities into one larger supply.

Each input needs its own appropriate current limit and remote-control policy. The GX AC-input type should reflect what is actually connected. A generator mislabelled as grid can also confuse monitoring and the intended ESS generator behaviour. Check the exact model and any external switching before applying the common arrangement.

During commissioning, record the active input with only the first source present, only the second present, both present and after the preferred source stops. Include any acceptance delay and the resulting charge current. A priority setting cannot make an electrically unsuitable source acceptable.

What to check or record

1. Label the physical sources and both software input types consistently.
2. Set each limit from that source and the installed protection.
3. Verify safe transitions using the installer’s procedure; never connect two sources together manually.

Choose conditions from the application and measurement reliability, and design start and stop behaviour as a complete sequence.

State of charge is useful for energy reserve planning when the monitor is reliable. Voltage responds to the battery’s electrical condition but also changes with load and charging. A high-load start condition serves another purpose: reducing sustained inverter or battery demand. None of these is a substitute for the battery’s protective BMS.

Record the selected measurement source, threshold units, time delay, stop threshold, minimum run time and quiet-hour behaviour. A delay can prevent a short appliance start from needlessly starting the engine. Separate start and stop values provide hysteresis, preventing repeated cycling around one boundary.

Also define what happens if the selected measurement disappears, the generator fails to start, or the engine runs without accepted AC. Automatic control must suit the generator’s remote interface and installation. Keep manual emergency operation available according to the approved design, and test the complete sequence under supervision.

What to check or record

1. Use a supported generator interface and verify run/AC feedback.
2. Test a genuine low-reserve condition without defeating battery protection.
3. Record failure-to-start behaviour, service intervals and who receives alarms.

They describe different parts of the operating cycle and should match the generator’s own requirements.

Warm-up allows an engine to establish stable operation before the configured load-transfer sequence. Cool-down gives it the required unloaded or reduced-load period before stopping. Minimum run time prevents a brief start condition from creating an excessively short run. A large battery charger may otherwise apply a substantial demand immediately after the engine starts.

Write the intended sequence in plain language before entering times: start request, confirmed running, accepted AC, charging/load application, stop condition, unloading and engine stop. The supported GX and VE.Bus integration determines which parts can actually be coordinated. An ordinary run-contact relay alone does not prove AC was accepted.

After configuration, test the sequence and inspect timestamps rather than listening only for the engine. Include failure cases: no start, running without voltage, loss of run feedback and a manual stop. Changing timings should not conceal a generator that cannot hold the permitted voltage or frequency under the expected load.

What to check or record

1. Use the generator manufacturer’s timing and duty-cycle requirements.
2. Confirm which device controls transfer, run feedback and stopping.
3. Retain a commissioning log covering both a normal cycle and supported failure handling.

Treat the operating strategy and the explicit battery-to-grid restriction as different settings.

The documentation describes Green mode as prioritising local energy use and Trade mode as pursuing trading opportunities. A mode name is not a substitute for the export permissions and battery restrictions in the setup. Forecasts, surplus production and the evolving scheduler can make the actual plan less obvious than a simple solar-first slogan.

If battery export is not permitted or not wanted, configure the relevant supported battery-to-grid restriction and verify the resulting plan and real power flow. Also distinguish live PV export from energy leaving the battery: the grid meter alone shows their combined result.

When changing strategy, record the time and wait for a fresh valid schedule before comparing results. Capture the forecast and plan at the time, because later graphs may display actual operation instead. Judge the result over comparable conditions while preserving the required reserve, not only by a single unusual interval.

What to check or record

1. Record strategy, battery export restriction and system feed-in permissions separately.
2. Compare battery power, PV output and grid flow at the same timestamp.
3. Escalate a reproducible mismatch with the saved settings, schedule and firmware details.

The planner aims for an energy/SoC outcome over an interval while responding to forecasts, load and available capability.

A target is not necessarily an instruction to run the charger at its nameplate limit continuously. As actual load, PV and battery energy change, the control can adjust power to reach the planned state. Capacity errors can make the displayed correction particularly noticeable near an interval boundary.

Compare planned and actual end-of-interval SoC, the entered bank capacity and the observed net battery power. If charging is consistently too slow, distinguish a planner decision from a physical restriction such as a low BMS CCL, input-current limit, temperature or charging taper. Increasing the planner’s capability value cannot make hardware exceed those limits.

Keep the price interval and time zone in the record; do not assume every market or current software release always uses the same interval length. Save the plan before it is replaced by actual data. The useful question is whether the energy objective was achievable and achieved, not whether the graph was a flat maximum-power line.

What to check or record

1. Record capacity in kWh, actual SoC source and active BMS limits.
2. Compare interval energy rather than isolated power samples.
3. Check for a fresh schedule and investigate recurring misses with timed evidence.

Independent charging schedules can conflict with the plan that Dynamic ESS is trying to execute.

The official Dynamic ESS FAQ advises against combining ordinary scheduled charging with DESS because it interferes with the scheduler’s calculations. Before enabling DESS, review existing ESS charge windows, external control, Node-RED flows and other automation that changes charging or grid targets.

Choose one clear operating strategy for the period being tested. If a fixed overnight window is the requirement, ordinary ESS scheduling may be easier to explain and verify. If forecast and price optimisation is the requirement, let the supported DESS controller manage the plan while retaining the separate electrical and battery protections.

When an automation is paused, record what value it leaves behind; stopping a script does not always restore the intended normal setting. Make a controlled transition, verify the applied mode and inspect a complete operating cycle. An unexplained overnight charge often becomes understandable once every active command source is listed.

What to check or record

1. Inventory all schedules and services that write operating settings.
2. Save working values before selecting the intended control strategy.
3. Verify charge permission, reserve and the next planned interval after the transition.

Separate internet connectivity, the device clock, regional price delivery and the validity of the current schedule.

A working VRM graph does not prove that the price feed for the selected market is available. Conversely, missing prices do not prove a local network fault. Record the error wording, market, time zone, last successful update and whether a valid schedule covers the current time.

The DESS manual describes fallback to ordinary ESS when the stored schedule runs out; its documented disconnected horizon is 12 hours. Treat this as documented behaviour to verify against current software, not a reason to leave the fallback ESS configuration unreviewed. A wrong clock can make an otherwise downloaded plan fail to match the current interval.

If many users in the same region report the same timed symptom, a provider/backend issue is plausible. Preserve the error and timestamps before repeatedly restarting equipment or deleting the installation. A local reset cannot repair an unavailable upstream price source and can remove useful diagnostic evidence.

What to check or record

1. Check clock synchronisation, region and the actual schedule time range.
2. Confirm the fallback ESS reserve and export behaviour.
3. Collect a concise report with firmware, error text and dated screenshots; avoid sharing account secrets.

Validate the final buy and sell prices against the actual contract, using the same interval, currency and tax basis.

A market price may be quoted per MWh while the energy bill uses kWh; a display may use cents while a formula uses whole currency units. Those differences create large errors even when the digits look familiar. Buying and selling formulas often have different additions, deductions and tax treatment.

As a unit example, 100 currency units per MWh equals 0.10 per kWh, because 1 MWh is 1000 kWh. This is only a conversion example, not an electricity tariff recommendation. Check whether provider fees vary with time and whether the current portal supports the required price schedule; older forum posts can describe superseded limitations.

Choose several real intervals, including a low or negative market interval where available. Calculate the expected final buy/sell values from the contract and compare them with VRM. Do not tune battery costs to compensate for a wrong price formula: that conceals one input error by introducing another.

What to check or record

1. Write down currency, energy unit, tax basis and each fee separately.
2. Validate buying and selling independently.
3. Keep dated tariff evidence and repeat the comparison when the contract changes.

A periodic full-charge strategy can serve battery maintenance or SoC synchronisation, which is a different purpose from daily trading.

Check the exact battery manufacturer’s balancing and full-charge requirements before enabling or choosing an interval. Some managed batteries request their own behaviour through the BMS; a generic schedule must not be used to force incompatible voltage or temperature conditions. A displayed 100% also does not prove that the required balancing process has finished.

Record the feature setting, planned event, BMS limits and the charge stage during the event. A long taper can reflect low permitted current or balancing rather than a charger fault. If the battery cannot complete the event within the available time, investigate the documented conditions and available charging power instead of raising voltage beyond the integration instructions.

Keep maintenance objectives separate from backup reserve and the daily price strategy. If a new periodic charge appears after a configuration change, check this function before assuming that the price optimiser has failed. Menu availability and behaviour can vary with the installed version.

What to check or record

1. Use the battery’s documented full-charge/balancing procedure.
2. Record the configured interval and the observed completion criteria.
3. Compare SoC with BMS status and voltage/current evidence, not the percentage alone.

Curtailment can be an intentional configured action when the supported system and final price rules make production undesirable.

The current DESS documentation describes a setting to disable solar below a chosen buy-price threshold. This requires supported controllable equipment; monitoring a PV inverter does not automatically mean its output can be curtailed. Record which PV sources can actually receive the command.

Check the final price used by the controller, not just a headline market price. An export penalty, a buying-price threshold and the value of charging the battery are different quantities. If the rule is triggered unexpectedly, compare the entered formula, currency units, threshold and actual plan before changing the threshold.

After the condition ends, verify that production returns normally. Also distinguish deliberate curtailment from battery-full regulation, an MPPT fault or unavailable sunlight. Save the active control state alongside PV voltage/current and grid/battery flows. A missing yield peak alone is not enough to diagnose the cause.

What to check or record

1. Confirm support and control permissions for every affected PV source.
2. Record the exact threshold and final price at the event time.
3. Validate both curtailment and recovery while preserving the installation’s export limits.

The exact 2x120V architecture matters; passing two incoming legs is not the same as generating a 240V split-phase output in inverter mode.

The documented Quattro-II 2x120V uses a single internal inverter. With the relevant split-phase AC source accepted, a 240V load between L1 and L2 can receive the incoming split-phase supply. In battery operation the two 120V output legs are supplied from the one inverter, so the voltage between them is not the same 240V supply.

This distinction affects air conditioners, cooking equipment and other line-to-line loads. An appliance list must therefore include required voltage and connection, not only total watts. Do not apply a European 230V diagram or a true split-phase multi-unit configuration to a 2x120V product by analogy.

Use the exact model’s power-flow diagrams to list which loads operate on each source and during an outage. Where a load requires a different topology, have the installer design a supported solution rather than changing software labels or rearranging conductors experimentally.

What to check or record

1. Record the full product variant and each load’s line-to-neutral or line-to-line requirement.
2. Check operation with each permitted input source and during battery operation.
3. Keep topology, continuous power and transfer ratings as separate design checks.

Expansion changes compatibility, current paths, phase assignment and configuration; adding hardware is only one part of the job.

The VE.Bus parallel/multiphase manual requires matching unit type and firmware, including size, voltage and feature set. A similar case or power label is insufficient. Some large MultiPlus-II configurations require the separate external-transfer-switch application, with additional hardware and application-specific requirements.

Recheck battery discharge/charge capability, protection, busbar capacity, branch symmetry, AC input/output limits and the phase distribution of loads and PV. The GX meter and system configuration must describe the new installation. A former single-phase assumption can survive in a saved setting and produce misleading power-flow behaviour.

The installer should save the original configuration, establish the supported grouping, commission the complete system and verify each intended operating state. Retest backup capability, communications loss and the relevant BMS restrictions. Expansion is complete only after measured behaviour matches the revised drawing and settings, not when every unit appears online.

What to check or record

1. Confirm hardware compatibility with the supplier before purchasing additional units.
2. Record phase assignment, firmware, current-limit interpretation and battery capability.
3. Keep the final system configuration and commissioning evidence with the updated drawing.

A structured commissioning record for a fixed home ESS: define the reserve policy, identify the measurement boundary and verify the actual power flows.

1. Define the objective. Write which circuits must remain supplied during an outage, how long they must operate and which loads can be postponed. Record ordinary and starting demand separately. A backup requirement is an energy-and-power problem: having enough kWh does not prove that the inverter can start every appliance.

2. Draw the boundaries. Mark the grid connection, grid meter, inverter AC input, AC-out circuits, grid-side loads and every PV source. Identify the meter direction and phase assignment. The software can only regulate the measurements and devices that the supported design provides; a misleading diagram can lead to plausible-looking but incorrect settings.

3. Establish battery control. Record chemistry, exact bank configuration, capacity, supported integration and the selected SoC source. Confirm live battery voltage, current and BMS limits before selecting reserve values. The reserve should be an operating decision within the documented battery limits, not a substitute for emergency cell protection.

4. Select the appropriate ESS strategy. Record the mode, minimum SoC and applicable BatteryLife behaviour. If the battery should support only essential loads, verify that the physical AC-out arrangement and metering support that choice. Explain to the owner that the normal grid-connected minimum and the outage discharge behaviour are different layers.

5. Configure grid exchange. Establish permitted export and the applicable controls with the installer. Enter the grid setpoint in watts with the correct sign and record any feed-in limits. Distinguish the target from instantaneous protection. Check the control support of AC PV and the per-charger limits for DC PV; do not assume one export checkbox covers every source.

6. Test ordinary operation first. Use known small loads on each side of the inverter and compare grid, PV and battery readings. Observe the transition when solar falls or a load changes. Confirm that the intended battery contribution, meter signs and reserve policy are consistent before testing backup.

7. Perform the approved outage and return test. The installer verifies protection and isolation, then checks the intended backup loads, solar behaviour and source reconnection. Capture the sequence and any alarms. A successful transfer with a light load is not a full-capacity or long-duration demonstration.

8. Hand over a readable record. Keep the final drawing, settings, firmware, battery integration reference, commissioning measurements and owner instructions together. State which loads must be avoided during an outage and how to recognise a genuine fault. If later changing reserve or export policy, repeat the affected verification rather than assuming the original result still applies.

What to check or record

1. Example energy calculation: a measured 0.5 kW essential load for 6 hours needs 3 kWh delivered to loads, before allowing for conversion losses and reserve. This is a planning example only.
2. List each setting with its unit, source of value and reason; leave unknown limits for the installer to resolve.
3. Record the start and end SoC, net battery energy and actual load for any autonomy test.
4. Retain successful test evidence and a clear route back to the documented configuration.

Build a predictable charging schedule from the tariff and energy requirement, then test what happens before, during and after each window.

1. Gather the tariff facts. Record the cheap-rate days, start/end times, time zone, seasonal changes and the final import price. A time displayed by a market website is not necessarily the time used on the bill. Separate a fixed time-of-use requirement from a forecast-driven DESS objective.

2. Select a single strategy. The documented scheduled-charge function belongs to the applicable Optimised ESS modes. Review DESS and any external automation before configuring it; independent controllers should not compete for charging or grid targets. Save the working configuration and document which control mechanism is intentionally active.

3. Estimate required energy. Use reliable bank capacity and the intended start/target SoC. For example, a 12 kWh bank moving from 25% to 75% needs approximately 6 kWh stored. If only 3 hours are available, the average net battery charging power must be about 2 kW, before allowing for taper and limits. These are illustrative quantities, not recommended settings.

4. Check feasible charging power. The AC source must supply ordinary loads as well as charging. Compare permitted AC input, inverter charger capability, BMS CCL, temperature and the actual net battery power. A planner value or target percentage cannot remove a lower electrical or battery limit.

5. Enter one clear window. Record selected days, start time, duration, SoC target and the self-consumption-above-limit choice. Decide whether the battery should remain reserved for the entire window or may serve loads above its target. Explain that reaching the target does not necessarily end the window or change the load source.

6. Observe a complete cycle. Capture readings just before the start, during charging, after the target and after the end time. Confirm the active ESS state, battery current and grid use. If the battery starts above the target, verify that the configured self-consumption behaviour still matches the intended strategy.

7. Add further windows only after the first works. Consider weekday/weekend selection, cross-midnight periods and overlap. A second lower target after an earlier higher target can create a deliberate reserve transition, but it should be understandable from the written schedule. Avoid a collection of entries that nobody can explain.

8. Review measured results. Compare actual stored energy and cost across representative days, including low-PV weather. Revise the window or operational target when evidence warrants it. Keep a record of tariff changes and update the schedule deliberately; a clock or contract change can make an unchanged configuration behave unexpectedly.

What to check or record

1. Save start/end timestamps and the selected time zone with the commissioning record.
2. Record target attainment separately from self-consumption during the remainder of the window.
3. When a target is missed, inspect time, net charging power and active limits before increasing any setting.
4. Verify the intended backup reserve remains available after normal overnight use.

This walkthrough explains the decisions and evidence an installer needs; it is not a generic wiring plan or a substitute for the exact product design.

1. Identify PV placement. A grid-tied PV inverter on the grid side normally loses its grid reference during a public-grid outage. A compatible PV inverter on the backed-up AC output can operate in a deliberately designed microgrid. Record every PV source and its location before deciding which generation should remain available.

2. Verify model compatibility. The PV inverter must support the required frequency response and the applicable regional configuration. Monitoring support, grid-feed-in permission and islanded power control are separate capabilities. Use the specific Victron integration instructions and PV manufacturer documentation, not a successful installation using another product revision.

3. Check the power relationship. Apply the current Factor 1.0 guidance to the applicable PV power and the inverter/charger continuous watt rating at 25 °C. Do not substitute the model’s VA label. For oversizing or undersizing of the panel array, use the official definition of the PV quantity entering the calculation. Record the result by phase and parallel group.

4. Check the battery independently. The bank needs the documented capacity and ability to absorb the changing energy flow. Review charge acceptance near full, low-temperature restrictions and what happens when a BMS requests little or no charge current. A software limit does not remove the energy that can appear during a sudden load rejection.

5. Plan recovery from a flat-bank shutdown. AC PV needs an AC reference to start. If the battery cannot start the inverter, an AC-only arrangement can become unable to recharge itself. The official guidance requires appropriate DC-coupled charging for off-grid and extended-backup applications; record how the actual installation recovers safely.

6. Configure the correct architecture. Grid-connected ESS and standalone off-grid arrangements use their respective documented Assistant/control approach. Do not stack unrelated Assistants because both contain the word PV. Record installed Assistants, frequency-control settings, PV limits, metering roles and supported communications.

7. Commission progressively. Verify normal grid-connected measurements and export control first. The installer then carries out the designed islanding, load-change, high-SoC and source-return tests under appropriate conditions. Record PV output, AC frequency, battery voltage/current and BMS limits together. Do not deliberately create an unsafe full-power event to prove a point.

8. Explain the limits to the owner. State which solar sources remain available during a cut, which appliances are backed up, what can curtail PV and how recovery works. Keep the exact manuals and the design calculations with the final configuration so future panel, inverter or battery expansion can be assessed against the same requirements.

What to check or record

1. List inverter/charger and PV inverter exact models, firmware and continuous ratings.
2. Keep grid-connected export control separate from islanded frequency control in the test plan.
3. Verify the battery and DC recovery path, not only the AC power ratio.
4. Reassess the complete design whenever AC PV capacity or battery configuration changes.

Separate source acceptance, current demand, control mode and electrical quality before changing multiple settings.

1. Describe the symptom precisely. Record whether the generator fails to start, starts without accepted AC, connects then disconnects, charges too slowly or fails only during a particular appliance start. These are different problems. Capture the exact alarms and the generator, inverter/charger and GX model/firmware details.

2. Verify the source specification. Use continuous output, voltage, frequency, duty cycle and environmental derating from the generator documentation. A peak marketing rating is not continuous battery-charging capability. Include other loads and any external transfer equipment in the drawing. The installer confirms wiring, protection, grounding and source compatibility.

3. Establish conservative demand within the approved design. Set the appropriate AC-input current for that source and check the DC charging limit. Record whether remote override applies and which Quattro input is active. A low battery-side charging limit alone does not constrain all AC loads passing through the unit.

4. Observe source quality under comparable conditions. Record generator voltage/frequency and accepted AC state at no load, during charging and during a representative load change. An engine that continues running may have an electronically tripped output. Use suitable instruments and qualified measurement procedures for waveform or electrical-quality investigation.

5. Review control settings in context. UPS mode, WeakAC and Dynamic Current Limiter serve different purposes and may introduce compromises. ESS changes which ordinary settings apply. Follow the current manual and firmware guidance, changing one relevant setting at a time. Never use broad acceptance windows to hide an unsuitable supply.

6. Test the start and stop sequence. Where automatic control is used, verify warm-up, run feedback, AC acceptance, minimum run time, unloading and cool-down. Include the intended response to failure-to-start or loss of AC. A correct relay command is only one step in successful generator operation.

7. Compare results objectively. Use the same battery state range and similar load so charging taper or changing demand does not distort the comparison. Record net battery energy added as well as the instantaneous charger current. A smoother display does not necessarily prove that more useful charging occurred.

8. Escalate with evidence. Provide the installer or support channel with the equipment list, configuration export, a single timed failure sequence and relevant measurements. State which changes were tested and restore the documented safe configuration after an unsuccessful experiment. Mechanical servicing or a different source may be necessary when settings cannot resolve the cause.

What to check or record

1. Use a table with test time, AC input V/Hz/A, battery V/A, active limits, load and exact alarm.
2. Separate generator continuous capacity from the inverter’s advertised power.
3. Do not change grid anti-islanding protection on a grid-connected input to imitate generator advice.
4. Have the installer approve the final source-loss and return behaviour for connected equipment.

Use a documented compatibility and measurement checklist so the extra units become one supported system.

1. Inventory the existing installation. Save the present VE.Bus configuration, Assistant list, GX settings, battery integration and electrical drawing. Record exact product codes, firmware identifiers and serial/revision information. Describe what the upgrade must achieve: additional continuous power, support for another phase or a specific backup load.

2. Obtain compatibility confirmation. The parallel/multiphase manual requires the appropriate matching unit type and firmware. Similar nameplate power does not prove identical feature sets. Check whether the planned model and size require the external-transfer-switch application or another special configuration before ordering or wiring equipment.

3. Recalculate the DC system. More inverters can demand more battery current even if daily energy consumption is unchanged. Review the BMS discharge and charge capability, module count, busbars, individual branch protection, cabling and connection symmetry. A large bank capacity in kWh alone does not establish sufficient instantaneous current.

4. Recalculate the AC system. Map input sources, output loads, phase sequence, expected imbalance and PV placement. Distinguish the total power objective from the limit on each phase. Review transfer ratings and the behaviour of loads that need multiple phases or line-to-line voltage during an outage.

5. Configure grouping using the supported tools. The installer establishes the intended parallel and phase relationships, then applies the correct Assistant and grid/battery configuration. Record which unit has each role. A collection of individually configured standalone units is not the same as a commissioned VE.Bus system.

6. Update monitoring and control interpretation. Confirm meter phase mapping, selected battery monitor, current-limit units and which physical inputs can be remotely overruled. Check that a saved single-phase assumption is not still controlling the expanded system. Verify all expected devices and BMS limits before applying substantial load.

7. Commission in stages. The installer validates protection and wiring, then checks ordinary charging, representative loads, phase behaviour and the intended source-loss/return sequence. Compare individual branches and phases, not only the total VRM number. Investigate one unit carrying an implausible share rather than accepting the aggregate as proof.

8. Complete the handover. Store the new configuration, compatibility confirmation, drawings and test results together. Retain the previous configuration as a historical record, but do not present it as a safe automatic rollback for physically changed wiring. Explain the new limits and the intended response to unit, battery or communications faults.

What to check or record

1. Verify the exact supported hardware/firmware grouping and application manual.
2. Document battery-current capability and per-phase AC constraints separately.
3. Record measured load sharing, phase assignment, meter signs and protective test results.
4. Recheck AC-coupled PV sizing and recovery behaviour if the upgrade changes the backup arrangement.

Use this review after the basic ESS installation works correctly; the objective is to distinguish wrong inputs from normal optimisation and hardware constraints.

1. Establish the baseline. Confirm reliable grid, PV, load and battery measurements, correct SoC selection and the required battery integration. Record the fallback ESS mode and reserve. DESS cannot make a wrong meter direction or an unavailable battery-control connection correct.

2. Verify physical capability inputs. Record nominal/usable capacity according to the field definition, realistic charge/discharge capability and export/import permissions. The scheduler uses these to judge what is achievable. The installed electrical limits, BMS requests and charging restrictions remain separate and must already be correct.

3. Validate price inputs independently. Choose several actual tariff intervals and calculate expected final buying and selling prices from the contract. Check currency, kWh versus MWh, cents versus whole currency units, fees and taxes. Confirm any time-varying rules in the current portal rather than relying on an old screenshot.

4. Review strategy and restrictions. Record Green or Trade mode, explicit battery-to-grid restrictions, minimum reserve and any supported periodic full-charge or low-price solar-control features. These are different decisions. A strategy name is not proof that export is forbidden, and a reserve target does not replace a BMS protection threshold.

5. Remove competing commands. Review ordinary ESS schedules, manual grid targets and external automation. Choose one intended planning mechanism. Record what remains active, including any service that can rewrite a setting. When switching strategy, verify the applied state and wait for a valid fresh plan before assessing the outcome.

6. Capture forecasts before the event. Save the price curve, consumption/PV forecast, planned battery trajectory and settings at the time. Later graphs may show actual data instead of the earlier plan. Include the interval length and time zone. Without the original forecast, a hindsight comparison can incorrectly attribute a weather miss to bad configuration.

7. Compare plan and reality. Examine end-of-interval SoC and energy, actual grid/battery power, BMS limits and unexpected loads. If the goal was impossible under actual restrictions, correct the capability assumptions or operating requirement. Do not raise physical limits merely to make the schedule look successful.

8. Review several representative days. Include low solar, high demand and unusual prices. Use measured import/export energy and the validated tariff to assess results, accounting for conversion losses and the chosen battery-cost assumption. Keep the required backup reserve and a clear fallback plan. Report reproducible deviations with dated evidence instead of repeatedly resetting the installation.

What to check or record

1. A calculation example: importing 5 kWh at 0.10 per kWh costs 0.50 before any additional charges; later usable energy is lower after losses. This illustrates arithmetic, not a savings promise.
2. Keep input validation separate from forecast accuracy and control-limit diagnosis.
3. Check missing-price or missing-schedule errors before interpreting an empty plan.
4. Retain configuration, forecast screenshots and actual interval measurements for a useful support report.

Compare voltage, current, temperature and shading together; panel wattage alone cannot identify a compatible arrangement.

Write down each module’s Voc, Vmp, Isc, Imp and Voc temperature coefficient. In a series string, voltages add while the string current is constrained by the modules; parallel strings share an operating voltage while their currents add. For an arithmetic example only, two identical modules with Voc 40 V and Isc 10 A make approximately 80 V and 10 A in series, or 40 V and 20 A in parallel at the stated test conditions.

The design must then pass separate checks for cold open-circuit voltage, hot-weather operating voltage, PV short-circuit current, connector limits and the controller’s supported battery voltage. A layout that stays below a voltage limit can still fail another check. Shade, unequal orientation and module mismatch change the practical result. Use the Victron sizing tool and the exact controller data sheet with the installation’s minimum temperature; retain the calculation instead of treating these example figures as a proposed array.

What to check or record

1. Record every module specification and the proposed series/parallel count.
2. Check each applicable input limit separately, including connectors.
3. Have string protection and isolation designed for the actual array.

A shared tracker chooses one operating point; matching total watts does not make different modules electrically equivalent.

Compare operating-voltage and operating-current curves, not just the “12 V” or “24 V” marketing description. Modules in series must carry the same string current; parallel strings work at a common voltage. A weaker current source or a mismatched voltage can therefore reduce usable output even when no absolute hardware limit is exceeded. Bypass-diode behaviour and shade make the result less predictable than adding the label wattages.

When extending an existing installation, record the old and new module specifications, orientation, shading and string arrangement. Evaluate the combined design in a suitable sizing tool. A separate MPPT for the new array can keep its operating point independent, but both controllers still need compatible battery profiles and an appropriate combined charging-current budget. Replacing the controller with a higher-current model does not remove a panel mismatch.

What to check or record

1. Keep photographs of the exact old and new module labels.
2. Compare Vmp for parallel strings and current compatibility for series strings.
3. Check cold Voc and total Isc after any rearrangement.
4. Verify the combined battery charging limits if adding another controller.

Treat the PV input and the battery output as different sides of the installation.

Two chargers connected to one battery can each have their own PV array. That does not mean their independently controlled PV inputs should be connected together. Each tracker changes the PV operating point to search for available power; sharing a source can make one controller’s measurement and control action interfere with the other. Communication between chargers for battery-charge synchronisation does not automatically create an approved shared PV input.

If one controller is too small, the normal design options are an appropriately rated replacement or a deliberate split into electrically independent arrays, each with its own controller. Check the exact product documentation for any explicitly supported exception. Trace both positive and negative PV conductors when investigating an unexplained interaction between controllers: a wiring drawing that shows separate arrays is not proof that the real installation is separate.

What to check or record

1. Give each independent tracker its intended PV source.
2. Do not confuse a shared battery bus with a shared PV bus.
3. Verify the actual PV wiring and isolation before modifying the system.
4. Recalculate protection, voltage and current for each new array.

Connector count and tracker count are different product specifications.

Some controllers provide multiple PV connector pairs that connect to one internal tracking input. Other products have genuinely independent trackers. Do not decide from the enclosure or the number of sockets. Read the exact model’s electrical diagram, tracker specification and connector-current limits before connecting differently oriented or electrically different arrays.

Where inputs are internally parallel, the attached strings must be evaluated as a parallel combination: they operate at a shared voltage and their input currents add. The fact that each connector is within its individual rating does not prove that the controller’s total short-circuit-current limit is respected. Conversely, a high total controller rating does not permit overloading one connector. Record both levels of limit in the design sheet and label the strings so subsequent additions cannot silently change the calculation.

What to check or record

1. Identify the full controller model, including terminal or MC4 variant.
2. Find the number of independent trackers in the official documentation.
3. Record connector limits and total PV input limits separately.
4. Do not copy an RS layout onto a single-tracker SmartSolar.

The decision depends on electrical compatibility and different operating conditions, not compass direction alone.

Arrays that receive sun at different times can have different optimal operating points. Separate trackers let each array work independently and provide clearer monitoring. Combining arrays may still be a valid design in some arrangements, but it requires checking the module characteristics, string voltages, shade pattern and the chosen controller’s topology. Never infer that two connector pairs provide two trackers.

Compare the options using expected daily energy, not only maximum midday watts. Two smaller independent arrays may reveal a shading problem that is hidden in one combined reading. They also add wiring, protection and another charge source to manage. If using separate controllers on one battery, align the documented battery settings or supported managed-control arrangement, and confirm that the sum of their possible output currents is acceptable.

What to check or record

1. Describe when each roof area is shaded and its orientation.
2. Calculate each array independently before considering a combination.
3. Check shared versus independent tracker inputs.
4. Compare daily yield after installation under comparable weather.

The controller must establish the correct battery reference; PV isolation is also a separate electrical task.

Follow the exact manual’s commissioning sequence. The referenced BlueSolar range requires the battery connection to be established before PV so that the charger can detect the battery voltage correctly. A controller that has lost its battery connection while PV remains present should not be diagnosed by changing charge voltages at random. Confirm supply, polarity, fuse condition and the configured voltage class first.

For maintenance, use the model’s documented shutdown procedure and correctly rated isolation devices. Disconnecting a solar connector under load can create an arc; the fact that the charger is “off” in an app is not a substitute for electrical isolation. Reconnection should include a deliberate check that the detected battery voltage and saved profile still match the bank. Record the original settings before a reset because a reset may discard an otherwise correct custom profile.

What to check or record

1. Read the startup and shutdown section for the exact controller.
2. Verify the battery reference and voltage class before admitting PV.
3. Use an installer for live isolation or connector work.
4. Recheck the saved profile and actual terminal readings after restart.

Automatic detection is a commissioning aid, not permission to omit the voltage check.

A very low battery, incorrect connection sequence or changed battery arrangement can undermine assumptions about what the controller has detected. Some voltage classes and controller models require manual configuration. Read the supported battery voltages on the exact product data sheet; a high PV input-voltage rating does not by itself mean the unit can charge every battery voltage.

Compare three things: the bank’s actual nominal series arrangement, voltage measured at the controller’s battery terminals, and the voltage class shown in VictronConnect. A disagreement is a reason to investigate wiring and configuration before charging. Changing the “charged voltage” in a SmartShunt is unrelated: that field controls full-charge detection, not the system voltage of an MPPT. After correcting the cause, recheck all voltage-dependent charging and load-output settings rather than assuming they have remained appropriate.

What to check or record

1. Record controller model and supported battery voltages.
2. Verify the bank arrangement and measured terminal voltage.
3. Confirm the detected or manually selected voltage class.
4. Check every voltage-dependent profile field after a system-voltage change.

Adaptive time, a configured maximum and a tail-current condition can play different roles.

On supported Victron chargers, the charging algorithm can adapt absorption duration according to the battery condition inferred earlier in the cycle. Expert settings can also define fixed timing or termination criteria. Therefore a shorter absorption phase is not automatically a fault, and extending the maximum time does not guarantee that the battery receives that full duration.

Log the morning battery condition, bulk duration, absorption start, voltage and current, and the reason the charger changes stage. Distinguish the charger’s own absorption tail-current setting from a battery monitor’s full-charge detection threshold. Where a BMS or external controller manages the charger, local timing may not be the active authority. Choose the algorithm from the battery manufacturer’s requirements and the integration manual, then validate a complete cycle; avoid tuning one cloudy afternoon in isolation.

What to check or record

1. Record whether absorption timing is adaptive or fixed.
2. Check maximum duration and any tail-current termination separately.
3. Identify external control before changing local settings.
4. Compare several complete charging days, including the battery’s initial condition.

Re-bulk determines when a new bulk cycle can begin after the battery voltage has fallen sufficiently.

A load can pull battery voltage down while the charger is in float. Depending on the model and configuration, the re-bulk condition may use an offset from a reference voltage and a time condition. It is not the same as the inverter’s low-voltage shutdown, the BMS discharge cutoff or the monitor’s low-state-of-charge alarm. Changing one of those other settings will not necessarily change when the charger starts a new cycle.

If the system repeatedly returns to bulk, compare battery-terminal voltage with charger voltage while the load starts. Examine the size and duration of the load, available charging power and voltage drop. A weak connection can imitate a low battery; a large legitimate load can also require a new cycle. Preserve the battery-approved charge profile and document the control reason before adjusting re-bulk parameters.

What to check or record

1. Read whether the field is an absolute voltage or an offset.
2. Record the preceding stage and the voltage during the load event.
3. Check voltage drop and charging capacity before changing thresholds.
4. Keep re-bulk separate from protective shutdown and monitoring alarms.

Treat a PV overvoltage indication as a design or measurement investigation, not a setting to suppress.

Capture the exact error, timestamp, maximum PV voltage in history, controller model, battery voltage class and every module label. Recalculate the complete string’s cold open-circuit voltage using the module’s temperature coefficient and the installation’s design minimum temperature. The panel’s operating voltage during an ordinary sunny measurement is not the worst-case open-circuit voltage.

If the documented calculation appears to leave adequate margin, have the real wiring checked against the drawing: unexpected series connections, crossed arrays or incorrect module specifications can invalidate the calculation. Do not repeatedly restart a controller while an excessive input remains possible. A different controller may be appropriate only after all voltage, current, connector and battery compatibility checks pass. The forum includes cases where the displayed model, drawing and installed hardware did not agree; photographs and measured evidence resolve that ambiguity.

What to check or record

1. Save the error and PV maximum before clearing history.
2. Use Voc and the correct temperature coefficient, not only Vmp.
3. Verify the physical string arrangement and exact controller.
4. Have the excessive-voltage condition resolved before resuming normal operation.

The charger can manage a small DC load separately from its battery-charge algorithm, where the model supports that function.

A physical load output, a virtual load-output signal and a programmable relay are different interfaces. Their ratings and wiring requirements are not interchangeable. On supported controllers, load logic may follow voltage thresholds, BatteryLife behaviour or a streetlight schedule. This changes whether an attached load is permitted to operate; it does not change the charger’s absorption voltage or create additional inverter power.

Before editing a schedule, identify the actual load-control interface and how the load is connected. Check the selected operating mode, voltage conditions, timers and any remote control. If the load remains off, compare the app’s stated reason with the wiring and rated current. A virtual signal may require another compatible switching device, and high-current or capacitive loads need the arrangement specified in the manual. Test the intended day/night sequence without defeating low-voltage protection.

What to check or record

1. Identify physical output, virtual signal or relay.
2. Record the load’s current and starting behaviour.
3. Separate load-control thresholds from charging values.
4. Test both the timed condition and the low-voltage response.

A source that produces DC is not automatically compatible with a PV tracking input.

A solar MPPT is designed around the behaviour of a photovoltaic array. A wind turbine has mechanical-speed and unloaded-voltage behaviour that a solar tracking algorithm is not designed to manage. When loading decreases during a scan or because the battery is full, the turbine may accelerate and its voltage may rise. Rectifying its output does not solve the control or overspeed-protection problem.

Use the turbine manufacturer’s dedicated control and protection arrangement, with a documented method for charging the battery and responding to battery charge restrictions. Integrating that separate charger on a Victron battery system requires checking its charging profile, maximum contribution, monitoring and BMS stop method. It does not justify routing an arbitrary regulated supply through the PV input. Ask for explicit compatibility documentation for any unusual source instead of adopting a forum experiment as a supported design.

What to check or record

1. Identify the source’s behaviour when unloaded or charging is blocked.
2. Use the source-specific controller and overspeed or energy-diversion protection.
3. Include its output in the total battery charging-current budget.
4. Confirm how the battery/BMS can stop that charger when required.

The converter transfers power, so the two currents need not be equal when voltages differ.

Estimate input power and output power separately using voltage × current. As a worked illustration, 40 A delivered at 14 V is 560 W. At a 13 V input and an assumed 95% efficiency, that requires approximately 560 ÷ 0.95 ÷ 13 = 45.3 A from the source. These figures demonstrate the calculation only; they are not recommended settings or a claim about every model’s efficiency.

This distinction matters when the alternator or input wiring is the limiting side. An output setting that appears modest can still demand substantial input current when input voltage is low. Record both configured limits and both live voltages and currents. If one side reaches its limit, the other side may remain below its selected maximum. Cable loss and the source’s own voltage regulation also affect the result, so compare simultaneous readings rather than screenshots taken at different times.

What to check or record

1. Keep input A, output A and power W in separate columns.
2. Identify whether the source or the battery is the limiting side.
3. Compare simultaneous input and output measurements.
4. Use documented system capability rather than this arithmetic example for settings.

A key-on signal can exist while the alternator is not producing power.

Identify what the vehicle or vessel signal actually means before using it to control charging. Ignition accessory mode, a dashboard indicator and a documented engine-running output may behave differently during starting, stop/start operation and shutdown. A signal that permits charging with the engine stopped can discharge the starter battery even though the control wiring appears to work.

For the current Orion XS 12/12-50A manual, an external engine-running signal forces charging on; the manual specifically requires engine shutdown detection to remain enabled when using that arrangement. Disabling detection makes charging continuous regardless of that signal. Do not transfer this instruction blindly to another Orion model or a different remote-control circuit. Record the exact terminals, firmware and control scheme, then test engine-off, cranking, normal running, stop/start and key-off states with the installer.

What to check or record

1. Use the vehicle maker’s documented signal and permitted interface.
2. Distinguish ignition-on from actual engine-running.
3. Read the exact Orion model’s remote-control and detection instructions together.
4. Verify the starter battery is protected in every engine state.

A regulated DC supply and a battery charging algorithm serve different purposes.

In charger mode, the supported Orion follows its battery charging logic or the documented external-control arrangement. In power-supply mode, the Orion XS maintains a configured output voltage within its operating capability. The current manual states that automatic engine shutdown detection is not active in power-supply mode; input-voltage lockout becomes especially relevant to deciding when output is allowed.

Before changing Function, write down the actual purpose: charging an auxiliary battery or supplying a compatible DC load. Record the required output voltage, input and output limits, source protection and remote control. A voltage that looks acceptable for a load does not by itself define a complete lithium charging strategy. Likewise, copying a charger-mode configuration into supply mode can change engine-off behaviour. After switching, confirm the mode icon, active limits and stop conditions under the real load.

What to check or record

1. Identify whether the output feeds a battery or a DC appliance.
2. Check the exact model’s available functions and voltage range.
3. Review input lockout and remote behaviour after changing mode.
4. Test source protection with the engine stopped and the load connected.

Compare the same electrical path while substantial current is flowing.

Record starter-battery voltage, Orion input voltage, Orion output voltage and house-battery voltage at the same time. A difference between source and input points to the input path; a difference between output and battery points to the output path. Include both positive and negative return paths, connectors, fuses and isolators. A no-load voltage check can look normal because the voltage drop grows with current.

For scale, a total path resistance of 0.01 ohm causes 0.5 V drop at 50 A and dissipates 25 W. This is a diagnostic arithmetic example, not an acceptable design limit. Excessive loss can make the charger reach its voltage target while the battery remains lower, or make input detection reduce charging. Raising a charging voltage or lowering a source-protection threshold can hide the symptom without correcting the connection. Have the path inspected and corrected, then repeat the same loaded comparison.

What to check or record

1. Capture simultaneous readings with the same load and engine condition.
2. Include the negative return path in the investigation.
3. Record connector and fuse-holder temperature observations.
4. Correct excessive resistance before retuning charging thresholds.

They are separate devices with different thermal limits and evidence.

Observe the system from a cold start through sustained operation. Record Orion status, input and output voltages and currents, engine speed, ambient conditions and any documented alternator-temperature information. A charger that reduces output as its own surroundings heat up is a different diagnosis from a source whose available voltage or current falls as the alternator warms. Both can occur in one installation.

The alternator’s nameplate current does not establish continuous spare capacity at idle with vehicle loads running. Do not adopt a universal percentage from a forum as a safe limit. Obtain the vehicle or alternator’s permitted operating information and use an appropriately commissioned input-current limit. The charger’s ventilation and mounting must also meet its manual. If the system only performs well for the first minutes of a drive, retain a time series rather than changing several limits until one screenshot looks better.

What to check or record

1. Compare cold and sustained hot operation at known engine conditions.
2. Separate charger derating from source voltage/current changes.
3. Include normal vehicle consumers in the source-load assessment.
4. Validate a sustained operating limit with the relevant installer or vehicle specialist.

A detachable charging path adds connector, return-path and operating-state questions.

Create a drawing that includes the towing vehicle source, input protection, both halves of the connector, cable lengths, return path, charger location and trailer battery. The battery can be close to the Orion while the input path is very long. That difference affects voltage drop and the source voltage the charger actually sees. A connector’s advertised rating does not verify the crimp, contact condition or installed wiring.

Confirm how charging is enabled, what happens when the engine stops and which parts remain energised after uncoupling. Protection must account for the sources that can energise the relevant cable; the charger is not a substitute for correctly designed cable protection. Commission the connected and disconnected states and compare input readings during realistic driving conditions. Intermittent charging that follows bumps or coupling changes warrants a connection investigation before changing engine-detection thresholds.

What to check or record

1. Document connector identity, cable paths and all possible power sources.
2. Measure input voltage under charging load at the trailer.
3. Test engine-off and uncoupled behaviour.
4. Have protection and mechanical strain relief checked for the installed arrangement.

The current Orion XS 12/12-50A manual describes a specific emergency reverse-charge feature with firmware requirements.

For this documented model, emergency reverse charge requires Orion XS firmware 1.15 and VictronConnect 6.43 or later. It temporarily transfers energy from the auxiliary battery toward the starter battery. The manual describes a 15-minute charging phase followed by a 5-minute settling period; Battery ready means that the sequence has reached that stage, not that a defective starter battery can necessarily crank the engine.

Check availability, start conditions and the voltage/current information shown by the app before using the feature. It is not a general instruction to reverse the cables or operate every Orion bidirectionally. In parallel installations, the manual requires all Orion XS units to reverse charge together or the other units to be switched off first: otherwise a unit charging normally can respond to the rising starter voltage and create circulating current. Follow the exact current manual and preserve the auxiliary battery’s reserve.

What to check or record

1. Verify exact model, firmware 1.15 and app 6.43 or later.
2. Read the app’s proposed reverse-charge conditions before starting.
3. Coordinate every parallel Orion unit as the manual specifies.
4. Investigate the cause of a repeatedly weak starter battery.

Engine detection is only one permission in the charging chain.

The output can still be disabled by a local switch, a remote terminal, a BMS charge permission, external control, an input lockout or another reported condition. Read the device’s actual status or “why off” information and identify which control applies. A correct source voltage does not prove that the battery currently permits charging.

Trace the intended control chain from the battery/BMS to the Orion and record the exact model and wiring scheme. Check whether the GX reports external control and whether the battery is requesting a low or zero charge-current limit. A detached control wire and a deliberate BMS stop can look similar from the battery-current graph. Do not bridge a remote input simply to make current appear: that may defeat the battery’s intended charge-stop path. Diagnose the reason, restore the approved control arrangement and verify that a requested stop actually stops charging.

What to check or record

1. Capture the exact off reason before changing settings.
2. Check all charge permissions, not only engine detection.
3. Compare BMS limits and local/remote enable states.
4. Verify normal charging and the documented stop response after correction.

Separate battery banks do not automatically share charging just because they belong to one vehicle.

Draw the actual energy path. Solar connected to the house bank normally charges that bank. An ordinary forward DC-DC charging arrangement is intended to transfer energy from the starter side toward the house side; it does not establish an always-on reverse maintenance charger. Some Victron products and system arrangements provide a documented starter-maintenance output or a specific reverse-charge function, but these are model-dependent capabilities.

First measure the starter battery’s parked consumption and confirm its condition. Then choose an explicitly supported maintenance arrangement for both battery chemistries, voltages and the vehicle’s requirements. Include all charging sources and the intended behaviour when the house battery is low, solar is absent or the vehicle is parked for weeks. A permanent cross-connection between banks can undermine isolation and source protection. Emergency reverse charge is not the same task as an unattended long-term maintenance strategy.

What to check or record

1. Identify which bank each charger actually reaches.
2. Measure or establish parked starter-battery consumption.
3. Use a documented maintenance arrangement for the exact equipment.
4. Test behaviour when the house bank is low and solar is unavailable.

A current can bypass the measuring element even when the voltage reading looks correct.

Trace every return path between the house battery and the rest of the system. A charger negative, chassis connection or common starter-bank return connected on the wrong side of the measurement can carry current without crossing the shunt. This is a recurring vehicle and boat issue: one load is measured correctly while another charge source is missed. Changing battery capacity, Peukert exponent or charge efficiency cannot correct a current that was never measured.

Use the exact shunt and battery/BMS installation diagrams to identify the battery side and system side. Include any external BMS in the drawing; the relevant battery-side arrangement depends on its design. Have the installer verify each source and load separately with independent measurements. Do not remove protective earthing or casually reroute grounding conductors to make the display agree. Correct the measurement topology while preserving the installation’s required bonding and protection.

What to check or record

1. Draw all negative returns, including chassis and starter-bank paths.
2. Test each charger and load separately under known conditions.
3. Compare shunt current with an independent suitable measurement.
4. Re-establish a valid full-charge reference only after the measurement path is correct.

The auxiliary connection does not add a second independent current-measurement channel.

The SmartShunt measures current through its main shunt element and estimates the state of charge of the bank represented by that path. Its auxiliary input can be configured for supported measurements such as a second battery’s voltage, midpoint voltage or an appropriate temperature sensor. A second voltage reading is not a second battery-capacity counter, and the auxiliary functions are alternatives rather than simultaneously available channels.

For two batteries in parallel that form one house bank, a correctly installed shunt can monitor the combined bank and use its total capacity. It does not reveal how current divides between the individual batteries. For electrically separate banks, separate current measurement and suitable monitoring may be needed if independent state-of-charge values are required. Decide the measurement objective first, select the correct auxiliary function and label the resulting display so voltage is not mistaken for a second SoC.

What to check or record

1. Distinguish one parallel bank from two independent banks.
2. Choose auxiliary voltage, midpoint or temperature according to the actual wiring.
3. Use total bank capacity only for the bank measured by the main shunt.
4. Do not interpret equal terminal voltages as equal individual battery condition.

Use the mode that matches what the shunt measures, rather than assigning battery state of charge to every cable.

A shunt in the whole battery-bank path can support battery monitoring. A shunt in a branch feeding a particular load, alternator or other DC circuit measures that branch, not the complete bank. The supported DC-meter configuration tells the system how to interpret that measurement. Its purpose is to account for power or current in the selected circuit, not to derive an independent whole-bank SoC from incomplete flows.

Before selecting a mode, mark the measurement location on the system diagram and identify every current that crosses it. In a GX installation, also check the intended DC-meter type or role so the same energy is not counted twice in system totals. A branch meter and a battery monitor can legitimately show different currents because they describe different boundaries. Verify the sign with a known source or load and compare the resulting GX display with the physical energy path.

What to check or record

1. State whether the shunt measures the whole bank or one branch.
2. Select the documented monitor mode and GX role.
3. Check current direction using a known operating condition.
4. Review energy accounting for duplicate or missing measurements.

The threshold treats sufficiently small measured currents as zero; it is not a battery-saving control.

The setting exists to avoid accumulating measurement noise or a small offset. Setting it too high can also suppress a genuine small load. For an arithmetic example, a continuous 0.2 A load consumes 4.8 Ah over 24 hours. If that current is treated as zero, the displayed state of charge can gradually diverge from the battery even though the device appears quiet and stable.

First establish whether a small reading is real: identify standby loads, compare an independent suitable meter and distinguish the current threshold from zero-current calibration. Calibration must not be performed with unknown real current flowing. Select a threshold appropriate for the measured installation rather than increasing it until the screen displays zero. After a change, check both the no-load baseline and a known small load, then monitor overnight behaviour. This verifies that the adjustment removes noise without making useful consumption disappear.

What to check or record

1. List continuously powered standby devices.
2. Confirm real zero current before any zero calibration.
3. Check a known small load before and after changing the threshold.
4. Compare overnight amp-hours with the expected consumption.

It is an estimate based on present or averaged use, not a forecast of tomorrow’s loads and solar weather.

The time-to-go calculation depends on the monitor’s battery assumptions, present state of charge, discharge floor and load behaviour. A kettle, compressor or inverter starting can change the estimate abruptly. The averaging-period setting smooths short-term changes; increasing it makes the display less reactive but does not improve an incorrect capacity value or repair a missed current path.

Interpret the number for the operating condition being observed. A fridge that cycles on and off and a heater that runs continuously have different future demand even if their current readings happen to match for a moment. The monitor cannot guarantee future sunshine or a later alternator charge. First validate state of charge and capacity, then choose an averaging interval that suits the use case. Keep a separate daily energy budget for planning autonomy, and compare measured daily consumption with that budget over realistic trips or outages.

What to check or record

1. Check capacity, SoC reference and the configured discharge floor.
2. Compare instantaneous and averaged load behaviour.
3. Do not use time-to-go as a guaranteed backup duration.
4. Use recorded daily energy for longer-term planning.

It reveals imbalance between measured parts of a bank; it is not a replacement for lithium cell monitoring.

A bank’s total voltage can look normal while its upper and lower sections differ. A midpoint measurement adds information about that balance. Before enabling it, confirm that the bank arrangement, measurement points and auxiliary configuration match the manual. Incorrect sense connections can make a wiring problem appear to be a battery imbalance.

If an alarm occurs, record whether it happened during charging, discharge or rest, plus total voltage and the relevant section voltages. Those conditions help distinguish a transient imbalance from a persistent problem. The alarm threshold and delay should follow the documented application rather than simply being widened until the warning disappears. On lithium systems, measuring the midpoint between complete batteries does not reveal every cell’s condition and does not replace the required BMS. Have differences investigated before adding balancing equipment or changing charging voltages.

What to check or record

1. Verify the exact midpoint wiring and auxiliary-input selection.
2. Record section voltages under the condition that triggers the alarm.
3. Separate bank-section imbalance from individual lithium cell monitoring.
4. Investigate the cause before widening an alarm threshold.

The IP22 range has a documented power-supply function; confirm the exact model and load requirements.

In Power supply mode, the Blue Smart IP22 disables its normal battery-charge logic and supplies a configured DC voltage within its current capability. The manual describes use with or without a connected battery. This is different from leaving the charger in a multistage charging mode and expecting a perfectly constant load-supply voltage.

Record the load’s allowed voltage range, continuous demand and starting current, then check the charger’s ratings and installation conditions. Select the Function deliberately, set a suitable voltage and current limit, and verify voltage at the actual load while it operates. A battery connected to that supply still needs a charging strategy appropriate for its chemistry; the presence of a charger-shaped product does not make an arbitrary fixed voltage suitable for indefinite charging. When returning to normal battery charging, select Charger again and recheck the saved profile and any low-current mode.

What to check or record

1. Confirm IP22 model capability and the load’s voltage/current requirements.
2. Check starting demand as well as steady current.
3. Verify the active Function and output at the load.
4. Restore and verify the battery charging profile when leaving supply mode.

Storage is part of the supported maintenance algorithm, not necessarily an indication that charging has failed.

The charger’s stages are designed for different parts of the charge and maintenance cycle. A storage stage can use a lower maintenance voltage than float, with the exact behaviour depending on profile and product. A voltage reduction after a successful charge should therefore be interpreted alongside the stage label and battery requirements, rather than judged against absorption voltage alone.

For a vehicle stored for a long period, record the battery chemistry, selected profile, background loads and whether AC remains continuously available. A battery that is being discharged by a substantial load may need a different investigation from a fully charged battery sitting in storage. Follow the manufacturer’s requirements for long-term charging and temperature conditions. Check the charger’s history and actual net battery current, and verify that any scheduled repeated absorption behaviour is appropriate. Do not raise storage voltage just to keep a monitor displaying a preferred number.

What to check or record

1. Compare the stage label with the selected profile’s maintenance behaviour.
2. Account for background loads during storage.
3. Check the battery maker’s long-term maintenance requirements.
4. Distinguish charger voltage from independently verified battery condition.

Reduced-current and quiet-operation options intentionally trade charging speed for lower heat or fan activity.

Check the active mode in VictronConnect and on the charger rather than relying on a button press made earlier. Night mode and reduced-current modes have model-specific duration and persistence. The IP22 documentation describes Night mode as a temporary reduced-current function; a separate low-current setting can remain the reason for a lower output. Not every Blue Smart model has the same fan or control features.

Estimate the practical effect using the battery’s missing charge, not only charger nameplate current. Replacing 30 Ah at a steady 5 A would require at least 6 hours before allowing for losses, load consumption and the absorption phase. This example explains duration, not a recommended current. If charging must finish before departure, verify the actual mode and net battery current well in advance. Maintain the required ventilation instead of selecting an unrestricted mode in a poorly ventilated enclosure.

What to check or record

1. Record exact model and active quiet or low-current mode.
2. Check whether the chosen mode is temporary or persistent.
3. Include simultaneous loads in the charging-time estimate.
4. Keep installation ventilation within the manual’s requirements.

Charger output includes power going to loads, so it may not equal the current actually entering the battery.

When a charger supplies a fridge, electronics or other DC consumers, part of its output serves those loads. A battery monitor in the correct whole-bank path measures the net battery current instead. Compare both readings at the same time before concluding that the battery is accepting the full displayed charger current. A load can also influence voltage and any current-based charge-stage decisions.

Confirm the exact charger’s supported algorithm and sensing options. Where a documented VE.Smart arrangement shares relevant measurements, verify that the expected source is actually connected and being used; a network name alone does not prove successful sensing. If charging never appears to complete, log the load, charger stage, charger current, battery current and voltage over the event. Avoid changing absorption duration solely to overcome a load that consumes most available power. The daily energy balance may simply require more charging time or less consumption.

What to check or record

1. Record charger output and net battery current simultaneously.
2. Test with a known load state to isolate its effect.
3. Verify supported shared sensing and the selected measurement source.
4. Separate energy shortage from a charging-profile problem.

This has attracted substantial forum discussion, but a similar graph does not establish the same cause or remedy.

Record the exact IP22 model, firmware, selected charging profile, active current mode, charge stage and connected loads. Capture voltage and current trends with timestamps, including whether the battery’s own BMS is permitting charge. A changing current can result from a load cycling, a charger control transition, source interruption, battery protection or product-specific behaviour. The large forum discussion is useful for identifying what to record and which release information to check; it is not proof that every fluctuating charger is defective.

Compare the observed pattern with the current official manual and the release information applicable to that exact firmware. If the behaviour is repeatable, provide the supplier with a concise trace and system drawing before trying multiple experimental settings. Do not disable battery protection or repeatedly force recovery modes to keep current flowing. After an advised firmware or configuration correction, reproduce the same battery and load conditions to verify the actual result.

What to check or record

1. Save model, firmware and profile before making changes.
2. Capture stage, voltage, current and load state on one timeline.
3. Check official release information for the exact product.
4. Repeat the original test conditions after an advised correction.

A worked design worksheet that separates voltage, current, operating range and practical yield.

1. Establish the actual equipment. Collect the complete module data sheet and the exact controller data sheet, including the connector variant. Photograph existing module labels when expanding an installation. Record the battery bank’s nominal voltage and the controller’s supported battery voltages. The “12 V panel” description and the controller’s wattage recommendation are not substitutes for these electrical specifications.

2. Describe the site. Record the lowest design temperature, likely module temperature during hot operation, orientation, shade and cable route. Cold modules increase open-circuit voltage; hot modules reduce their useful operating voltage. A layout must leave the controller within its permitted input range in both conditions. For a vehicle, consider the conditions encountered on trips, not only the climate at home.

3. Calculate candidate series strings. As an illustration only, a module with Voc 40 V at 25°C and a Voc coefficient of -0.30%/°C increases by 13.5% when evaluated at -20°C. That gives approximately 45.4 V per module, or 136.2 V for three in series. This is a simplified calculation to demonstrate the method, not approval for a particular controller or temperature margin. Use the module’s actual coefficient, tolerances and the applicable design method.

4. Calculate parallel current separately. Three identical parallel strings with Isc 10 A each produce a nominal combined Isc of 30 A before applying the relevant design conditions and margins. Check the controller’s input short-circuit-current limit, each connector’s limit and the array protection requirements independently. Output charging-current rating is a different quantity and must not replace the PV input-current check.

5. Check operation, not only survival. The hot-weather string operating voltage must allow the specified controller to start and charge the bank. Compare possible clipping, shading and mismatch losses over a day. If roof sections or module types differ materially, assess separate trackers. Confirm whether multiple connector pairs are one shared tracker or genuinely independent inputs.

6. Complete the installation design. Have the installer specify conductor sizes, overcurrent protection, isolation, earthing/bonding and connector compatibility. The software sizing result does not inspect a real connector or determine whether a routed cable is protected correctly. Retain the model numbers and calculations in the handover record.

7. Verify after commissioning. Compare the actual string arrangement with the drawing, check detected battery voltage and profile, then record PV voltage, battery voltage, charging current and stage under known conditions. Review maximum PV voltage and daily yield over representative weather. If the result differs, investigate the design assumptions and measured conditions before changing charge settings.

What to check or record

1. Record module Voc, Vmp, Isc, Imp and temperature coefficient with their source.
2. Keep cold-voltage, hot-operating-voltage and current calculations separate.
3. Document controller, connector and battery compatibility.
4. Have protection and isolation checked for the final arrangement.
5. Save the actual commissioning readings alongside the design.

A practical field-by-field review for a standalone or externally managed solar charger.

1. Identify the control arrangement before entering values. Write down the exact charger, battery chemistry, battery model, BMS and any GX or VE.Smart network. State whether the MPPT is a standalone charger using a local profile or participates in a documented managed-battery system. A visible local field can be inactive, an upper bound or subordinate to an external request.

2. Confirm battery voltage and current capability. Compare the actual bank arrangement and measured battery terminals with the voltage class selected in VictronConnect. Record the maximum charging current that the battery and installed DC system permit. If several sources can charge simultaneously, calculate the combined possible contribution and establish how that combined limit is respected.

3. Fill the battery-profile fields from the battery documentation. Record absorption voltage, float or storage requirements, absorption timing, re-bulk behaviour and temperature rules. Note whether the field expects an absolute voltage, a percentage, a time or an offset. Keep the source beside the value. A BMS emergency overvoltage threshold is not automatically the normal absorption target.

4. Review the charging algorithm. On a supported charger, adaptive absorption, fixed duration, maximum duration and tail-current termination are separate choices. Establish which combination is required for the battery and which is actually active. The SmartShunt’s Charged voltage and Tail current fields are monitoring settings; they should not be mistaken for the MPPT’s own charge-stage controls.

5. Review sensing and external permissions. Verify the selected voltage and temperature measurement sources, their plausible live values and communication status. Check the documented BMS/remote stop path. A Bluetooth network name alone does not establish successful shared sensing, and shared sensing does not automatically create a system-wide current limit. Use the exact integration instructions for these relationships.

6. Observe a complete useful charging cycle. Log starting battery condition, PV availability, major loads, stage transitions and actual terminal voltage/current. A cloudy interruption, a battery-full condition and a BMS restriction can all reduce output for different reasons. Record the charger’s stated status alongside the numbers so a low-current screenshot can be interpreted later.

7. Change only a justified variable and verify persistence. Save the previous profile, make the documented change, reopen the setting and repeat comparable observations. Confirm that the battery receives the intended charging behaviour and that the supported stop condition remains effective. Do not declare a profile correct merely because the app accepts its values or because the displayed state of charge reaches 100%.

What to check or record

1. Keep a settings record with value, unit, source and controlling device.
2. Verify voltage class before the charging-voltage fields.
3. Separate charger termination from monitor synchronisation.
4. Check sensing and BMS permissions with live evidence.
5. Compare complete cycles under recorded conditions after any change.

A measurement plan for reliable charging and starter-battery protection, rather than one copied threshold.

1. Define the source and destination. Record vehicle or vessel, alternator arrangement, starter battery, house battery, Orion model and firmware. Include any external regulator, BMS, GX and engine-running control signal. Obtain the permitted spare source capability under the relevant operating conditions. An alternator’s headline current rating is not a continuous idle-current allowance for an added charger.

2. Document the electrical path. Mark input and output protection, cable lengths, connector types, chassis/common returns and the Orion’s position. Have the installation checked against the exact manual, including mounting and ventilation. A long input path can make the charger see a different voltage from the starter battery even when the house battery is very close to its output.

3. Prepare the charge and control settings. Use the house battery’s approved charging requirements and a current limit within the source, battery and wiring constraints. Record input and output current limits separately. Select the intended function and the model-specific engine-detection or remote-control arrangement. For the current Orion XS external-engine-signal arrangement, the manual says to leave engine shutdown detection enabled; verify this against the exact current manual rather than applying a generic workaround.

4. Establish the engine-off baseline. Record starter and house voltages, charger status, input and output current, active permissions and major loads. Test the key-off and ignition-accessory states. The expected result must come from the designed control scheme: merely seeing an ignition signal does not prove that the alternator is supplying power.

5. Observe starting and running. Have the installer record cranking, initial running, idle, normal driving or cruising, and any stop/start event. Compare simultaneous source voltage, Orion input voltage, output voltage and house-battery voltage. Note whether the charger is waiting, limited, externally controlled, charging normally or off. This separates a control decision from a cable or source-capability problem.

6. Repeat after the system is warm. Include ordinary vehicle consumers and realistic ambient conditions. Check for charger thermal derating, alternator voltage changes and excessive connection losses. Do not increase input demand simply because the battery could accept more current. Agree a sustained operating limit that the source and installation can support.

7. Verify stopping and handover. Confirm the intended response when the engine stops, the control signal changes, the house battery becomes full or the documented BMS stop request occurs. Retain before/after settings and the test log. If charging remains intermittent, report one reproducible event with all simultaneous measurements; changing several thresholds without that record makes the diagnosis harder.

What to check or record

1. Record exact model, firmware and the intended control signal.
2. Check key-off, accessory, cranking, running and stopping states.
3. Measure both ends of each charging path under load.
4. Repeat tests after sustained warm operation.
5. Verify the documented battery-stop path and starter protection.

A structured way to prove measurement before tuning state-of-charge settings.

1. Define the measurement boundary. Draw the house battery bank, any external BMS, the shunt and the system bus. Mark every charger, inverter, DC load, chassis return and connection to another bank. State which complete battery bank the shunt is intended to monitor. A shunt measuring one branch cannot be expected to represent all bank currents.

2. Verify the approved topology. Have the installer compare the real wiring with the exact battery/BMS and shunt diagrams, including the battery-side and system-side terminals. Pay particular attention to alternator and chassis returns in boats and vehicles. Do not remove protective earth or change required bonding as a shortcut. The objective is a complete measurement path that also preserves electrical protection.

3. Establish a trustworthy baseline. With the installation in a known state, identify which standby currents remain. Compare a small reading with an independent suitable instrument before assuming it is offset. Zero-current calibration belongs only to a confirmed zero-current condition. A high current threshold can conceal genuine consumption, so it must not be used to make an unexplained reading disappear.

4. Test loads individually. Operate a known load and confirm current direction and approximate magnitude. For a simple arithmetic check, 10 A for 15 minutes corresponds to 2.5 Ah. This is an ideal integration example, not a battery-capacity test or a requirement to create a particular load. Use appropriate equipment and record other active consumers so the comparison is meaningful.

5. Test charge sources individually where the installation permits it. Compare alternator/DC-DC, solar and AC-charger operation with the shunt and independent measurements. If one source changes battery voltage but contributes no measured current, investigate bypass paths before altering capacity or efficiency. Compare net battery current with charger output: connected loads can legitimately account for the difference.

6. Configure the monitor from the verified bank. Enter total bank capacity at its actual voltage, the battery-appropriate estimation parameters and full-charge detection conditions that match the charging system. Choose the intended auxiliary-input function and, on GX systems, the supported battery-monitor source. Distinguish battery-monitor mode from a branch DC-meter role.

7. Establish and validate the charge reference. Synchronise only after full charge has been independently established according to the battery requirements. Observe a realistic discharge and recharge cycle, preserving history rather than repeatedly resetting it. A correct current path plus a credible reference is stronger evidence than an attractive 100% display immediately after configuration.

What to check or record

1. Keep the full return-path drawing with the installation.
2. Verify direction and magnitude for separate sources and loads.
3. Distinguish net battery current from charger output.
4. Tune estimation settings only after measurements are correct.
5. Validate SoC over real cycles rather than repeated manual resets.

Choose the operating job first, then verify profile, current mode and real battery behaviour.

1. Identify the charger and the job. Record the complete IP22 model, output arrangement, firmware, AC supply and battery or load connected. State whether the purpose is routine battery charging, long-term maintenance or supplying a DC appliance. These jobs do not all use the same Function or voltage behaviour. A three-output charger’s total current capability is shared; it is not multiplied by the number of terminals.

2. Record the battery requirements. Obtain the battery maker’s charging-voltage, timing, current and temperature instructions. Choose a compatible standard profile only when its actual values meet those requirements. Otherwise use a documented custom configuration where supported. Keep reconditioning and equalisation decisions separate; they are not general remedies for a lithium battery that appears difficult to charge.

3. Set the current deliberately. Consider battery limits, connected loads, the installed DC path and the desired completion time. Check whether low-current or Night mode is active. Estimate an ideal lower bound for charging time, then allow for losses, loads and absorption. For example, replacing 30 Ah at a net 5 A cannot take less than 6 hours; a load consuming part of the output extends that time.

4. Review maintenance behaviour. If the battery will remain connected for storage, record what float, storage and any repeated absorption stages do in the chosen profile. Compare this with the battery’s long-term requirements and actual temperature conditions. A lower storage-stage voltage should not be mistaken for failure merely because it differs from absorption voltage. Account for standby consumers that continue to discharge the battery.

5. Verify sensing and control. If using supported VE.Smart sensing or synchronisation, check the actual connected devices and live measurements. Distinguish charger output from net battery current. Confirm the temperature information is suitable for the intended feature; an internally measured charger temperature and the battery’s cell temperature are not interchangeable.

6. If supplying a DC appliance, use the documented Power supply function. Verify the load’s allowed voltage range, starting demand and continuous current before choosing output values. Confirm the voltage at the load during operation. If a battery is also connected, its charging requirements still matter. Return to Charger function and verify the intended profile when resuming normal battery charging.

7. Prove the result under repeatable conditions. Save the initial settings, record charging stage and voltage/current trends, and include load state. For unexplained pulsing, retain model and firmware information and check the relevant official release guidance with the supplier. After an advised correction, reproduce the original conditions. A one-minute successful connection is not evidence of correct overnight maintenance or completed charging.

What to check or record

1. Record exact model, output arrangement, firmware and intended job.
2. Keep every custom value linked to the battery or load specification.
3. Check quiet/low-current modes when charging takes too long.
4. Verify maintenance and supply modes separately.
5. Save comparable trend data before and after troubleshooting changes.

A practical configuration and energy-budget review for several sources charging the same house bank.

1. Map the whole system. List the house battery bank, BMS, solar controllers, Orion, AC charger, battery monitor and any GX device. Record exact models, firmware, communication links and independent stop/enable paths. Several devices on one battery bus are not automatically one coordinated controller. State which devices are managed together and which remain standalone.

2. Create a source-limit table. For each charger, record the applicable current limit, voltage profile, input-source restriction and BMS permission. Then assess the maximum combined contribution. As an illustration, possible outputs of 60 A, 30 A and 20 A add to 110 A before considering loads or active regulation. This is arithmetic, not a proposed combination or a safe battery current. The documented battery and installed DC-system limits determine what may actually be permitted.

3. Align the charging requirements. Use the same battery manufacturer’s requirements across the relevant standalone profiles, allowing for the different functions and integration instructions of each device. Confirm any managed-battery voltage/current requests and which chargers can obey them. VE.Smart synchronisation can coordinate supported charging behaviour, but it does not automatically impose one total current budget across every source.

4. Prove the measurement boundary. Ensure the battery monitor captures all source and load currents through its intended path. Charger output is not necessarily net battery current when the fridge, inverter or other loads are operating. Compare both when judging whether charging is slow. A missed alternator return path can make the SoC estimate drift even while the battery receives energy.

5. Build a daily energy budget. Record load power and realistic operating hours, then compare the resulting Wh with measured usable battery energy and likely replenishment. For a capacity illustration, a 300 Ah bank needing 40% of its charge replaced is missing approximately 120 Ah. A constant net 20 A would need at least 6 hours; if a 5 A load leaves only 15 A net, the ideal minimum becomes 8 hours. Real stage changes and losses extend these simple estimates.

6. Test operating combinations. Record solar alone, driving charge, shore charging and the combinations that can occur in normal use. Check battery limits, current distribution, stage behaviour and source-specific stop conditions. Confirm what happens when one source disappears or the BMS requests charge to stop. Do not assume a protection request reaching one charger reaches the others.

7. Handover a settings and evidence pack. Keep the energy-path drawing, source-limit table, battery profile sources and representative logs. Explain which display is the system SoC reference and which readings are individual source outputs. Revisit this record whenever a panel, charger, battery or major load is added; an unchanged setting can become inappropriate after the rest of the system changes.

What to check or record

1. List all possible simultaneous charging sources and their control methods.
2. Verify the combined battery limit rather than only individual nameplates.
3. Measure net battery current and account for active loads.
4. Test source combinations and documented stop conditions.
5. Update the configuration record after every material system expansion.

Choose a network addressing method you can maintain; a fixed-looking address alone does not prove internet access.

DHCP supplies the address, network mask, gateway and DNS information automatically. A reservation in the router can keep that address predictable while leaving the GX on automatic configuration. Manual addressing requires all of those fields to be correct and must avoid addresses assigned to another device. Record the network owner and the intended recovery method before changing anything remotely.

An address identifies the GX on its local network. The gateway provides a route beyond it; DNS translates service names. A local console can therefore work while VRM fails because the gateway or DNS is missing. Conversely, a changed DHCP lease can make an old browser bookmark fail even though VRM still works.

What to check or record

1. Record the active interface, address, mask, gateway and DNS.
2. Reserve an address outside conflicting leases using the router’s supported procedure.
3. Test local access and VRM last-contact time separately after a change.
4. Keep an on-site recovery route when modifying a remote installation.

Separate physical links do not automatically create the routing policy you expect.

A boat may use Ethernet for a marine display and Wi-Fi for internet access. This is different from connecting both links to the same home network. Write down the subnet and gateway offered by each network, the GX addresses, and which path each client uses. Check the specific marine integration instructions before adding a router or changing addressing.

If one service works through one address and not another, test the route and service access rules before blaming the battery or inverter. Do not copy shell-based routing changes from a forum into a production GX: they may be unsupported, lost on an update, or disconnect remote access. Simplifying to a documented topology is usually easier to maintain than adding custom routing.

What to check or record

1. Draw Ethernet, Wi-Fi, router and MFD connections.
2. Check for overlapping subnet ranges and duplicate addresses.
3. Identify the intended internet connection and local service address.
4. Use the current GX and MFD manuals to validate the topology.

The GX access point is primarily a local access route; joining it is not proof that the GX or phone has internet service.

A GX can offer a local wireless network for configuration while using a separate connection for internet access. Your phone may warn that the selected Wi-Fi network has no internet and prefer mobile data or another saved network. That can make discovery seem inconsistent even though the GX is operating normally.

First decide whether you are trying to reach the local GX interface or the cloud-based VRM portal. Verify the model supports the access-point feature and use the connection details supplied for that device. Then configure the GX’s intended Ethernet, Wi-Fi-client or supported cellular connection independently. Avoid changing battery settings while troubleshooting a phone’s network selection.

What to check or record

1. Confirm the phone remains connected to the intended GX network.
2. Use the local interface address shown by the device instructions.
3. Check GX internet status separately from access-point status.
4. Return the phone to its normal network when local commissioning is complete.

Access depends on both the installation’s GX access mode and the permissions assigned to the signed-in user.

The GX’s VRM mode determines whether cloud access is off, read-only or full. A user account’s installation access is another layer. A full-access owner cannot assume that an invited viewer has the same controls, and enabling full access on the GX does not turn every invited account into an administrator.

When a control is absent, first record the account used, its installation permissions and the GX VRM mode. Also distinguish monitoring access from product-specific configuration support: a visible device is not necessarily remotely configurable through every application. Give each person the access needed for their role and keep the installation attached to the intended owner’s account rather than sharing an installer’s password.

What to check or record

1. Check that the correct VRM installation is open.
2. Compare GX VRM mode with the user’s assigned role.
3. Use a separate invited account for each responsible person.
4. Verify viewing and an authorized reversible control separately.

Choose the warning interval around the expected reporting pattern and the importance of losing visibility.

A no-data alarm detects missing communication; it does not identify whether the cause is a power outage, router failure, mobile coverage, GX restart or an intentional shutdown. The GX log interval and VRM’s allowed interval without received data must make sense together. An alarm shorter than a deliberately slow reporting pattern produces avoidable notifications.

Start by observing normal reporting over the actual connection. Decide who should respond and how they will check the site without relying on the failed connection. Test notification delivery using the available test function and a planned communication interruption when appropriate. A communication alarm complements local protection; it cannot replace a BMS, fuse or protective shutdown.

What to check or record

1. Record the GX log interval and normal last-contact behaviour.
2. Set VRM communication monitoring and its notify-after allowance.
3. Confirm the responsible users’ email or push preferences.
4. Document expected behaviour during planned site shutdowns.

They may represent different sampling times, aggregation periods or measurement sources.

A live screen describes the current device state, whereas a historical graph represents stored observations over a selected interval. A short load spike may be visible locally but not appear as the same peak in an averaged graph. Power in watts and accumulated energy in kilowatt-hours are also different quantities; a power reading cannot be compared directly with a daily energy total.

When investigating a mismatch, use the same device, parameter, units and time window. Note whether the widget shows a live value, a latest sample, an average or a total. Then compare nearby samples rather than two screenshots captured minutes apart. If values remain inconsistent under a stable load, investigate device roles, measurement coverage and data freshness.

What to check or record

1. Record timestamps and the graph’s selected time range.
2. Match device identity and units before comparing numbers.
3. Repeat the comparison during a steady operating condition.
4. Export relevant data when a brief event needs closer analysis.

It depends on whether the GX retained the data and can upload its backlog; a gap is not always permanent.

The GX can buffer measurements while its internet connection is unavailable, within its storage capabilities. Supported external storage can extend logging capacity on applicable devices. This does not preserve data that was never measured because the GX itself had no power or the connected product was absent.

After connectivity returns, inspect the GX’s logging status, stored-record backlog and last successful contact rather than repeatedly restarting it. Backfilling may take time on a weak connection. Confirm the storage medium and file-system requirements in the exact GX manual before fitting a card or USB drive. Treat a logging medium as operational storage, not as a complete configuration backup.

What to check or record

1. Distinguish internet loss from GX power loss.
2. Check storage detection, free capacity and logging errors.
3. Allow the backlog to upload and compare the affected period again.
4. Keep a separate backup of settings and automation flows.

An instance identifies a device within a service type; it is not the same as a product serial number or Modbus register.

A system can contain several solar chargers or battery measurements. Software needs a stable way to distinguish them, especially in VRM widgets and integrations. The GX device-instance view groups devices by service type. The same number on two different service types is not automatically a conflict; uniqueness matters within the relevant type.

Before changing an instance, record the product model, serial number, connection and existing graph or integration references. A changed identifier can affect how a client finds its data or how historical data is presented. Do not renumber every visible device merely to make the list look tidy. Correct a demonstrated collision and verify the affected monitoring or client configuration afterwards.

What to check or record

1. Identify the service type as well as the instance number.
2. Map each instance to a real labelled device.
3. Check existing VRM widgets and external integrations before renumbering.
4. Verify continuity and correct device selection after the change.

Check time synchronisation and display timezone before changing an energy-management schedule.

The GX clock, the timezone used by a web interface, and the timestamp convention in exported data are related but different. Daylight-saving changes can make a fixed UTC time appear at a different local hour. An automation imported from another country may also contain a hard-coded timezone or clock assumption.

Choose one observed event, such as a known load switching on, and compare its local time with the GX, VRM graph and automation log. Check that the network permits the device’s documented time-synchronisation method. Do not move an entire charging schedule to compensate for a display-only timezone difference; that may shift actual operation once the clock issue is corrected.

What to check or record

1. Record the intended site timezone and daylight-saving behaviour.
2. Check clock synchronisation after prolonged loss of internet or power.
3. Label exported evidence with timezone or UTC explicitly.
4. Test the next scheduled event after correcting the time configuration.

A working cloud connection suggests the GX is running; investigate display power, video and display settings separately.

A display problem does not automatically mean the power system or GX controller has stopped. Depending on the display model, video and power use separate connections. A loose cable, unsupported extension, screen timeout or brightness setting can produce a blank screen while device logging continues normally.

Check the exact display and GX compatibility, then inspect accessible connections with the installation in a safe state. Use a functioning local or remote interface to confirm display settings and whether the GX has restarted. Do not factory-reset a working GX simply because its screen is dark: that introduces a second problem and may remove useful configuration evidence.

What to check or record

1. Verify VRM last-contact time is current rather than a cached graph.
2. Check display model, power connection and video cable separately.
3. Review brightness, blanking and touch settings through another interface.
4. Record whether the problem follows the display or the GX before replacing hardware.

Use the documented DC supply arrangement so monitoring does not disappear when the inverter stops.

Powering a GX through an AC adapter connected to the inverter output can create an avoidable dependency: an inverter shutdown removes the monitoring device precisely when diagnostic information is most useful. The Cerbo manual recommends powering the GX directly from the battery using the specified protected supply arrangement. The exact input-voltage range and connection requirements depend on the GX model.

The supply must still respect the battery system’s protection and shutdown design. Direct battery supply does not mean leaving an unprotected cable connected or bypassing a BMS requirement. Ask the installer to document the fuse, disconnect path and behaviour at low battery voltage. Verify that communication and diagnostic access remain available during the intended operating transitions.

What to check or record

1. Record where GX positive and negative supply conductors connect.
2. Confirm model voltage range and the correct supply protection.
3. Check whether inverter Off also removes GX power.
4. Test the documented shutdown and recovery sequence without defeating battery protection.

Use supported VE.Direct-to-USB interfaces and account for the GX’s total device and USB power limits.

VE.Direct is a point-to-point connection; a passive splitter is not a supported way to add several products to one socket. The documented expansion route is a VE.Direct-to-USB interface for each additional product, with a suitable USB hub when more USB ports are needed. The practical device limit depends on the GX model and total system workload, not just the number of connectors.

Check whether a particular USB socket on the exact GX revision is available for data and whether the hub needs its own power. Keep a port map so the battery monitor and solar chargers remain identifiable. For longer runs, follow the manual’s cable and active-USB-extension guidance rather than splicing VE.Direct wires. Add devices one at a time and confirm stable recognition.

What to check or record

1. Count all existing and planned VE.Direct products.
2. Check the model-specific maximum and system complexity.
3. Use supported interfaces and a quality powered hub where required.
4. Verify every product after a restart and under normal load.

Check the physical bus, termination and profile together; a matching plug is not sufficient.

A CAN network needs the topology, cable wiring, bus speed and termination required by the connected products. Adding a device may move the physical end of the bus without moving its terminator. A battery may also contain internal termination, so blindly fitting extra plugs can be as unhelpful as leaving an end unterminated.

Use the exact battery or product integration drawing to identify the two bus ends and any internal termination. Confirm the chosen GX port and CAN profile match the integration. Then inspect network diagnostics and connector seating. Do not change charge voltages to hide intermittent loss of battery communication; the control system cannot reliably follow BMS limits it is not receiving.

What to check or record

1. Draw every CAN device and both physical bus ends.
2. Record the required cable pinout and internal terminators.
3. Check the GX port profile and supported bit rate.
4. Log communication errors before and after one controlled wiring correction.

Seeing two battery measurements does not create two independent coordinated charging systems.

A GX can display several measurements, but its system battery and controlling BMS selection serve specific control functions. A starter battery, house battery and auxiliary bank may need different chargers and protection. Do not assume that selecting another battery widget automatically redirects DVCC control or makes incompatible banks safe to parallel.

Draw which battery each charger and inverter actually connects to. Identify which BMS owns the limits for that electrical bank and which measurements are monitoring-only. Multi-bank or multiple-GX designs require the documented architecture and compatible integration; use a qualified system designer when independent control domains are needed. The important question is which physical battery receives current, not how many icons appear on screen.

What to check or record

1. Map every battery bank to its loads and charging sources.
2. Record the selected system battery and controlling BMS.
3. Separate starter-battery monitoring from house-bank control.
4. Validate simultaneous operating conditions before enabling automation.

No. First determine why the battery is withholding charge permission and follow its integration instructions.

A zero charge-current limit can be an intentional response to a full cell, temperature, internal protection or another battery condition. Pack state of charge alone does not explain it. Record the live CCL, CVL, temperature, cell extremes if available, module status and alarm history at the same moment. A high cell can constrain charging even when the pack’s displayed SoC is below full.

Contact the battery supplier with that evidence if the behaviour is unexpected. Cell-balancing procedures and firmware remedies are battery-specific. Disabling BMS control, forcing a higher voltage or copying a forum’s prolonged charging recipe can remove the very limit preventing damage. A software setting cannot repair a defective cell or unreliable communication link.

What to check or record

1. Capture the battery’s requested limits before changing anything.
2. Check temperature and module/cell information, not only pack voltage.
3. Confirm the documented battery integration and firmware combination.
4. Use the supplier’s supported recovery or balancing procedure.

These temperatures can differ significantly, so choose the source required by the charging and battery integration.

A sensor on a terminal or in an electrical cupboard is not automatically measuring the coldest battery cell. A battery with an internal BMS may use cell sensors for protection while a GX displays an external sensor. That external value can be useful for observation but should not silently replace the battery’s required protective measurement.

Check the exact role of shared temperature sense and any low-temperature charging rule in the connected charger. Record the chosen sensor, its physical location and which devices consume that reading. For lithium systems, do not import lead-acid temperature-compensation behaviour without the battery’s instructions. If heating is added, the heater controller, charge permission and actual cell temperature must be considered together.

What to check or record

1. Label each temperature sensor by location and purpose.
2. Confirm whether the BMS transmits usable cell-temperature data.
3. Check charger and battery requirements before selecting STS.
4. Test sensor-loss behaviour and keep independent protection active.

The bank’s available capability may fall when fewer modules are available, even if the total voltage remains normal.

Compatible managed battery systems may report aggregate limits based on the modules currently online. If a module shuts down, loses communication or reaches a protective condition, the effective charge or discharge capability can change. Equal pack voltage does not prove every module is participating or sharing current correctly.

Compare the reported module count, alarms and current limits before and after the event. Check the manufacturer’s minimum-module requirements for the inverter power and the supported parallel wiring. Do not multiply a single-module current rating by the number of boxes unless the documented system can actually provide that aggregate capability. Module additions may require addressing, firmware matching and a prescribed commissioning sequence.

What to check or record

1. Record installed, detected and available module counts separately.
2. Check the current limit reported by the controlling battery.
3. Inspect whether a particular module repeatedly drops out.
4. Have wiring, current sharing and expansion compatibility checked against the battery manual.

The fuse-monitoring electronics need their own documented power connection; the main bus voltage is not that supply.

The Lynx Distributor does not internally power its fuse-monitoring circuit from the main busbar. The RJ10 connection normally supplies the electronics from a compatible Lynx device. Consequently, unlit LEDs can mean the monitoring circuit is unpowered, rather than proving that all fuses are healthy or that the busbar is safe to touch.

Check the exact Distributor revision and the supported RJ10 arrangement. A standalone supply must follow the manual’s pinout and voltage requirements; reverse polarity can damage the electronics. Also distinguish local indication from remote reporting: a Lynx Shunt VE.Can can provide power but does not provide the same Distributor fuse-status communication as a compatible Lynx Smart BMS.

What to check or record

1. Identify the monitoring power source and RJ10 cable path.
2. Check the revision-specific LED sequence in the manual.
3. Verify busbar voltage using the installer’s safe measurement procedure.
4. Confirm whether the selected Lynx combination supports remote fuse-status reporting.

A fuse also needs suitable voltage, interrupting capacity, operating characteristics and a compatible holder.

The current rating describes only one aspect of a fuse. The device must interrupt the prospective fault current at the maximum circuit voltage. A high-capacity lithium bank can supply a very large short-circuit current, so a fuse that fits mechanically and has the expected amperes may still be unsuitable. AC and DC interruption ratings are not interchangeable.

Protection selection also depends on cable ampacity, installation conditions, the equipment manual and the fuse’s time-current behaviour. The correct design coordinates battery-side and branch protection; it is not a choice made from a forum brand preference alone. Record the complete fuse part number and the assumptions used by the system designer, including the holder’s rating.

What to check or record

1. Check maximum DC voltage as well as nominal battery voltage.
2. Establish the required interrupting capacity from the system design.
3. Match cable, holder and equipment protection requirements.
4. Do not increase fuse current to mask repeated unexplained operation.

Use the termination method specified for the exact terminal, conductor and product; one rule does not fit every connector.

A ferrule can help retain fine strands in an appropriate clamp, but an incorrect size, length or crimp can reduce contact quality. A lug, screw clamp and spring terminal are different connection systems. The product’s wiring instructions and terminal rating decide which conductor preparation is acceptable.

Prepare a termination schedule listing cable cross-section, conductor type, stripping length, terminal type, tool and specified torque where relevant. The installer should inspect full insertion, retained insulation and strain relief. Do not tin stranded cable with solder as an improvised substitute where the connection specification does not permit it. A neat-looking connection is not evidence of correct contact pressure or current capacity.

What to check or record

1. Read the exact product’s terminal instructions before selecting ferrules.
2. Use the correct ferrule and calibrated or suitable crimping tool.
3. Check for loose strands, partial insertion and insulation under the contact.
4. Verify specified tightening and inspect for heating during commissioning.

They describe contact connections; a potential-free relay does not supply power to the controlled appliance.

COM is the common contact. NO and NC describe the normal contact relationship, but the software polarity and the device’s powered state also matter in the actual installation. A relay output can provide a control signal to suitable equipment; it is not a general-purpose high-power supply. Check the exact GX relay voltage and current ratings, including whether the load is AC or DC.

An appliance that exceeds the contact rating may need an appropriately designed external interface or contactor. Inductive loads also need consideration. Have the installer define what happens if GX power is lost, a cable breaks or the controller restarts. A screen saying On is not proof that the physical appliance is energised or that a generator accepted its start request.

What to check or record

1. Record the controlled device’s required signal and electrical rating.
2. Check COM/NO/NC wiring against the intended resting state.
3. Test actual output behaviour and loss-of-power behaviour.
4. Label the relay function and any external interface clearly.

The activation and release thresholds may be too close, or the sensor may not represent the controlled equipment.

Hysteresis creates a gap between switching on and switching off. Without a suitable gap, small temperature fluctuations around one threshold can cause rapid switching. A delay may help with brief changes, but it cannot correct a sensor installed in the wrong place or an incorrectly sized heater or fan.

For an explanatory example, a cooling function could switch on above one temperature and release only after a lower temperature is reached. Those numbers must come from the actual equipment and application; they are not universal battery limits. Review all enabled sensor rules because more than one sensor can affect the same relay. Keep battery protection separate from comfort or enclosure-temperature control.

What to check or record

1. Identify whether the function is heating or cooling.
2. Record activation, release, delay and sensor location.
3. Check for multiple rules requesting the same relay.
4. Verify normal cycling and behaviour when the sensor is unavailable.

Sensor resistance, tank geometry and configured capacity must agree before the displayed volume is meaningful.

A resistive sender describes its position through resistance; the GX converts that into level and volume using the selected sender range and tank configuration. European and US sender conventions differ, and a non-rectangular tank may not contain half its total volume at half its measured height. Built-in GX tank inputs are not universal voltage or current inputs.

Record the sender specification, tank capacity, fluid type and geometry. Choose the supported interface for the sensor, then calibrate using known safe reference points rather than guessing from the gauge. Custom tank-shape calibration can account for a nonlinear relationship between level and volume. Check the chosen litres or gallon convention before interpreting a numerical discrepancy.

What to check or record

1. Verify resistive, voltage or current sender type before connecting.
2. Set the correct resistance range and direction.
3. Enter capacity and volume units from the tank documentation.
4. Check several known levels and set appropriate alarm thresholds.

Only use the signal type and voltage allowed by the exact GX input specification.

A dry contact merely opens or closes a circuit; a powered output applies voltage. They are not interchangeable. Generator-running contacts, door switches and bilge alarms may look similar in a menu while having different electrical outputs. Check the GX model’s input wiring instructions and the external device’s output specification before connecting them.

Configure the input’s function and polarity so the displayed state matches the real event. Then test both normal and alarm states, including an unplugged sensor where relevant. If the external output is incompatible, the installer must select a suitable interface rather than treating a software inversion option as electrical protection. A digital input used for observation does not itself provide an emergency shutdown circuit.

What to check or record

1. Identify dry-contact versus powered output.
2. Verify allowed input voltage and common/reference connections.
3. Name the input by its real location or device.
4. Test state changes, polarity and any VRM alarm rule end to end.

Large adds Node-RED and Signal K; ordinary GX monitoring and many built-in controls do not require it.

Choose the image because an identified function needs it, not because the name suggests better inverter performance. The exact GX hardware must support the image, and additional services use processor, memory and storage resources. A complex automation workload can affect responsiveness even when the electrical equipment is healthy.

Before changing image type, record firmware, available storage and existing configuration. After installation, enable only the services you intend to use and confirm basic monitoring still works. Node-RED flows and added modules need their own maintenance and backups. If a flow causes excessive activity, use the documented recovery or safe-mode process instead of repeatedly rebooting the whole installation.

What to check or record

1. Check GX compatibility with the current Large image.
2. List the exact Node-RED or Signal K requirement.
3. Back up flows and related configuration before updates.
4. Observe processor load, free storage and device communication afterwards.

Another controller may be writing the same value, or the flow may be reacting to its own output.

ESS, Dynamic ESS, a BMS, schedules, a third-party integration and a custom flow can all influence system behaviour. A Node-RED write does not automatically become the highest-priority command. Repeatedly forcing a value can create an oscillating loop or obscure a legitimate protection limit.

Create a list of every possible writer for the affected setting. Temporarily observe the flow’s proposed decisions without sending commands, and compare them with the native controller’s actions. The final design should assign clear ownership, use bounded values and define what happens with stale data, missing devices or a restarted flow. A watchdog is useful only if its fallback is appropriate for the actual installation.

What to check or record

1. Record the exact device/path and every controller that may write it.
2. Log input values, timestamps, decisions and acknowledged state.
3. Add suitable hysteresis, rate limits and stale-data handling.
4. Prove a manual override and a safe fallback before unattended use.

The client may be using the wrong register, unit ID, scaling factor or signed interpretation.

A Modbus Unit-ID selects a connected service; the register selects a parameter inside it. The current register list defines data type, scale, units and whether writing is supported. Copying a register number from a different product or an old integration can produce a believable but incorrect number.

For an arithmetic example, if the documented scale is 10, a raw value of 523 represents 52.3 in the specified unit. This is an illustration of scaling, not a battery-voltage target or a promise about a particular register. Start with read-only access and compare several known values with the GX screen. Do not enable writes until the addressing and interpretation are proven.

What to check or record

1. Use the current official register list for the connected service.
2. Record Unit-ID, register, type, scale and physical unit together.
3. Check signed values and unsupported/invalid-value conventions.
4. Verify at least two operating states before trusting an automation.

A successful broker connection does not prove that the client subscribed to valid data and maintains the required update flow.

Check the current Victron MQTT implementation, portal identifier, service instance and topic spelling. Recent dbus-flashmq behaviour differs from older retained-message assumptions; the official documentation describes requesting a refresh and maintaining updates. A missing or null value can also mean the device does not provide that parameter, rather than a network failure.

Keep the connection within the documented network security profile and use supported authentication and transport. Do not weaken the GX’s security simply to reproduce an old forum example using an unencrypted port. Compare one known live value with the GX interface, then test reconnection and stale-data detection before using MQTT values to control equipment.

What to check or record

1. Confirm the exact broker route, security mode and topic structure.
2. Use the current keep-alive/refresh behaviour from Victron’s documentation.
3. Distinguish zero, null, absent and stale values in the client.
4. Do not treat the last received value as current indefinitely.

A virtual device needs the correct role, supported data fields and accurate measurements; its presence does not certify compatibility.

Virtual devices can expose measurements from an external source to the GX environment, but the software representation must match what the physical device actually measures. A grid meter and a load meter are not interchangeable roles. Duplicating a measurement already supplied elsewhere can distort totals and control decisions.

Record the source device, units, sign convention, phase mapping and update rate. Check which virtual-device types are supported by the installed Venus OS release and Victron nodes. Begin with monitoring-only use. If the device will influence ESS or another controller, validate its loss-of-data behaviour and control suitability against the relevant integration documentation rather than assuming that a visible tile is sufficient.

What to check or record

1. Map every published field to a real measurement.
2. Use a unique identity and the correct service role.
3. Check for double counting in system totals.
4. Test missing, stale and reversed-sign data before enabling control.

Compare independent evidence before resetting working equipment or changing network settings.

If the local GX interface and its connected devices behave normally while the portal is unavailable, check whether the issue affects one account, one installation or several locations. A browser problem, local internet failure and wider cloud incident can produce similar symptoms. Public outage discussions can provide context, but an old high-view thread is not proof of a current outage.

Record the exact time, GX last-contact status, local internet condition and any portal error. Preserve logs and let a healthy GX buffer data as documented. Avoid repeated factory resets or network rewrites during an external incident. After service returns, confirm data upload, alarm delivery and any cloud-dependent features separately; restored graphs do not prove every remote control path has recovered.

What to check or record

1. Check the local GX and one unrelated internet service.
2. Compare the same installation from another browser or permitted network.
3. Consult current official service communications or support information.
4. Confirm backlog recovery and scheduled cloud functions afterwards.

Build a documented path for local access, internet service and recovery before adding integrations.

Step 1 — Draw the network. List the GX model, Ethernet connection, Wi-Fi client connection, access point if used, router, marine display and any external monitoring computer. Write the purpose of every connection beside it. A line labelled Ethernet is insufficient: note which subnet it belongs to, who supplies addresses and whether it is intended to carry internet traffic.

Step 2 — Record addressing. Start with the supported automatic configuration unless the network design requires otherwise. If predictable local access is needed, a router reservation can keep a known address without manually duplicating the gateway and DNS configuration on the GX. For a manual configuration, record address, mask, gateway and DNS together and verify that the address is not in use.

Step 3 — Separate local and cloud checks. Open the local GX interface and verify a current measurement. Then check GX internet status and the VRM last-contact timestamp. A local page can work without a valid internet route. VRM can also work while an old local bookmark points to a previous address. Write the result of each test, rather than recording only “network OK”.

Step 4 — Add required services deliberately. MQTT, Modbus and Node-RED are separate services with their own access requirements. Enable only the integration needed, keep the current security profile, and use the documented client settings. Do not expose an unprotected local control interface through internet port forwarding as a shortcut to remote access.

Step 5 — Test recovery at a suitable time. Restart the router or reconnect a link using a planned procedure while someone can recover local access if needed. Confirm that the GX reacquires its expected address, reconnects to VRM and resumes any external integration. If Ethernet and Wi-Fi serve different networks, test both paths independently and record which one provides internet connectivity. Retain both the planned configuration and the measured commissioning result so later changes have a reliable reference.

What to check or record

1. Record model, firmware, MAC addresses and network owner.
2. Save the local address or hostname and the intended remote access method.
3. Verify address, subnet, gateway and DNS as a complete set.
4. Check local live data and cloud last-contact time separately.
5. Confirm each required integration after a restart.
6. Keep recovery instructions and credentials in the owner’s secure records.
7. Document the outcome before changing another network setting.

Configure meaningful events, recovery thresholds and notification delivery instead of enabling every possible alarm.

Step 1 — Define responsibilities. List the events that require action: loss of communication, a product alarm, low operating reserve, an unusual temperature or a relevant tank level. For each one, record who receives it, how quickly they should respond and what they can safely check. An alarm with no responsible person and no response procedure is easy to ignore.

Step 2 — Confirm the measurement. Identify the exact device and parameter behind each rule. Compare the value with the local GX screen and verify units and freshness. A sensor named Battery may actually be measuring a terminal or cupboard; a generic power value may be a calculated total. Correct the source before choosing thresholds.

Step 3 — Configure the layers. Communication monitoring detects missing uploads. Automatic monitoring reports supported product alarms and optionally warnings. User-defined rules add application-specific conditions. Set notification delay and hysteresis to reflect the process, so a brief transient does not create repeated messages. Do not use notification delays to conceal a genuine protective alarm.

Step 4 — Verify the recipient path. User access and notification preferences are separate from the rule itself. Use the provided test notification for each intended delivery channel. Check email or app delivery on the actual recipient device. A successful local alarm icon does not demonstrate that a remote person will receive the message.

Step 5 — Test and document. Use a safe simulation or planned condition appropriate to the sensor; do not create a battery fault to test a message. Confirm activation, the recorded timestamp, delivery, acknowledgement expectations and recovery notification. Check the alarm log for repeated triggering. If a rate limiter is active, investigate the noisy rule before merely resetting the limiter.

At handover, keep a short alarm matrix with device, parameter, units, trigger, release threshold, delay, recipients and action. Review it after equipment changes or a different operating strategy. Communication alarms and cloud notifications complement local protective functions; they do not become the electrical or battery protection system.

What to check or record

1. Choose actionable events and named responders.
2. Verify the source device, unit and timestamp.
3. Record trigger, recovery threshold and delay separately.
4. Test email or push delivery using the supported test function.
5. Check activation and recovery without creating a hazardous condition.
6. Retain the alarm matrix and a record of the test.

Establish a reliable read-only measurement path before allowing an external system to send commands.

Step 1 — Define the data requirement. Write down what the dashboard needs: battery state of charge, grid power, solar yield, individual phase values or device status. For each item, identify the physical measurement and whether it is instantaneous power, energy accumulated over time, a state or an alarm. Avoid importing every available field before understanding the important ones.

Step 2 — Select a supported interface. Use the current official integration instructions for the GX firmware and chosen client. Modbus, MQTT and cloud APIs have different addressing, security and update behaviour. Keep local network access limited to intended clients and avoid copying obsolete port or password advice from an old forum post.

Step 3 — Build an address and unit map. For Modbus, record service/Unit-ID, register, data type, scale and unit. For MQTT, record portal identifier, service instance, topic and the current refresh/keep-alive behaviour. Store access tokens or credentials securely and omit them from screenshots, exported flows and public support posts.

Step 4 — Validate values. Compare several parameters with the live GX interface at the same time. Use a controlled change in an ordinary load to confirm direction and response. A sign error can make import look like export; a scaling error can make 52.3 appear as 523. These are interpretation examples, not recommended system settings.

Step 5 — Handle unavailable data. The dashboard must distinguish a real zero from missing, null or stale information. Record the last update time and show an unavailable state after an appropriate timeout. Disconnect and reconnect the client during a planned test to confirm that old values do not remain indefinitely labelled as live.

Only after the read-only path is proven should a separate control design be considered. That design needs clear ownership of each setting, bounded outputs, a manual override and a defined fallback. A third-party dashboard displaying the right numbers is not, by itself, evidence that it can safely control charging or grid power. Retain both the planned configuration and the measured commissioning result so later changes have a reliable reference.

What to check or record

1. List required data and its physical source.
2. Use current official interface and client instructions.
3. Keep write permission disabled during initial validation.
4. Check addressing, scale, units and sign convention.
5. Verify at least two operating states and a reconnect.
6. Record stale-data timeout and recovery behaviour.

Treat an automation as a controller with inputs, outputs and failure states, not just a diagram that deploys successfully.

Step 1 — State the purpose and boundary. Specify the intended behaviour in ordinary language, such as requesting a flexible load only when verified surplus is available. List the equipment it can command and the settings it must never override. Battery protection, inverter protection and applicable grid constraints remain outside a custom flow’s authority.

Step 2 — Inventory the environment. Record GX hardware, Venus OS image and version, installed nodes, external APIs and any credentials. Export the existing flows and document the additional configuration required to restore them. An exported flow may depend on nodes or credentials that are not included in that file; prove that the recovery record is complete.

Step 3 — Observe before writing. Run the decision logic with outputs disconnected or directed to diagnostic logging. Capture input values, freshness, the proposed action and the reason. Compare this with native ESS, Dynamic ESS, BMS and schedule behaviour. Resolve overlapping writers before allowing the flow to change the system.

Step 4 — Add control limits. Validate data types and units, reject missing values, constrain the output range and avoid rapid repeated writes. Use hysteresis or minimum on/off times where the physical process needs them. Define what happens if the GX restarts, a sensor disappears, internet prices are stale or an external service returns an error.

Step 5 — Test a limited scope. Start with one reversible action during an attended operating period. Confirm the real equipment state, not only the message sent by the flow. Exercise the manual override and the documented fallback. For a troublesome flow, the supported Node-RED safe mode can open the editor without starting flows; deploying changes starts them again.

Step 6 — Handover and maintain. Label the flow, its owner, affected settings and recovery procedure. Keep a changelog and revisit the tests after firmware or node changes. An automation that worked once under ideal conditions has not yet demonstrated reliable behaviour during a cold battery, communications loss, restart or changed operating mode. Retain both the planned configuration and the measured commissioning result so later changes have a reliable reference.

What to check or record

1. Write the intended behaviour and prohibited overrides.
2. Back up flows, dependencies and required configuration.
3. Log proposed actions before enabling commands.
4. Assign one owner to each controlled setting.
5. Test stale inputs, restart, manual override and fallback.
6. Verify actual device response and record the result.

Compare requests, measurements and actual charger response before changing any battery-related value.

Step 1 — Confirm the integration. Record the exact battery model, module count, BMS version, communication cable, GX port/profile and the approved Victron integration instructions. Check that the GX sees the intended controlling battery. A successful device name on screen is only the beginning; measurements and limits must also be plausible and current.

Step 2 — Capture one event. Choose a clear symptom, such as charge current falling while solar power is available. Record the timestamp and capture battery voltage, net battery current, state of charge, CCL, CVL, DCL, temperature, alarms and cell/module information where available. Capture charger output and active DC loads at the same time.

Step 3 — Follow the controlling limit. If CCL falls before charger current falls, investigate the battery’s reason. If CCL remains generous but the charger output falls, inspect available source power, charger limits, temperature and other control requests. If charger output exceeds net battery current, account for simultaneous DC loads before concluding that a limit is ignored.

Step 4 — Examine the battery evidence. A high cell, cold cell, unavailable module or internal protection may explain a changing request even when pack voltage and SoC appear normal. Compare trends rather than a single screenshot. The battery manufacturer determines acceptable cell behaviour and any supported balancing procedure; a community example is not a substitute.

Step 5 — Change only an identified cause. Do not disable BMS control or force a higher charging voltage simply to make a graph look better. If wiring, communication or firmware is the identified issue, follow the approved repair or update process and retain the before/after record. If the cause remains inside the battery, supply the evidence to its vendor.

The completed record should explain which value changed first, which controller reacted and whether the resulting current matched the request. This separates expected protective control from a measurement problem or an actual charging fault, and makes a support discussion much more useful than a general report that the battery will not reach full charge.

What to check or record

1. Verify battery identity, module count and controlling-BMS selection.
2. Capture requests and measurements at the same timestamp.
3. Include charger current and DC loads as well as net battery current.
4. Compare several moments around the event.
5. Use model-specific guidance for balancing or recovery.
6. Keep protection active and record the effect of each justified change.

Turn the system drawing into a checkable record of conductors, protective devices, measurement paths and control connections.

Step 1 — Draw the actual installation. Include every battery module, busbar, isolator, fuse, inverter/charger, solar charger, DC-DC charger and DC load. Distinguish power conductors from communication and control cables. Mark the battery-side and system-side of the shunt so that unmeasured return paths are visible. A generic manufacturer example is a reference, not proof that the installed wiring matches it.

Step 2 — Label each circuit. Record cable material and cross-section, total current path length, expected continuous current, relevant starting demand and installation conditions. Include positive and return paths. The installer must establish suitable cable sizing and voltage drop for the actual route; a nominal inverter wattage alone is not enough to select a cable.

Step 3 — Record complete protection details. List each fuse or breaker’s part number, current rating, DC voltage rating, interrupting capacity and holder. Identify what conductor or equipment it protects and where it is installed. Coordinate battery-side and branch protection with the prospective fault current and applicable equipment instructions. A larger replacement fuse is not a repair for an unexplained trip.

Step 4 — Check terminations and modules. Identify terminal type, permitted conductor preparation, ferrule or lug details and specified torque. Verify the exact Lynx module and joint size rather than assuming all versions are mechanically identical. Check monitoring-power and communication connections separately from the high-current busbars.

Step 5 — Verify measurement and control paths. Confirm that relevant current passes through the intended shunt, that BMS disconnect/control signals reach the documented equipment and that GX power behaves correctly during shutdown. Label every CAN bus end and terminator, every VE.Direct product and each relay or digital input by its function.

Step 6 — Commission with evidence. A qualified installer should inspect, measure and test the system using the appropriate procedure, including voltage drop and abnormal heating under representative load where applicable. Record readings, settings, photographs and test conditions. Update the drawing after any correction. The owner should receive a version that describes the system that was actually tested.

What to check or record

1. Use an installation-specific drawing with labelled circuits.
2. Record cable, fuse, breaker and holder specifications completely.
3. Check terminal preparation and specified tightening.
4. Verify shunt coverage, BMS paths and GX supply.
5. Record representative-load measurements and inspection results.
6. Retain the final drawing and commissioning evidence together.

Choose the operating purpose before changing current or solar thresholds.

Manual mode lets you start or stop a connected vehicle and select the permitted current. Scheduled mode follows enabled time windows, with the current defined in each schedule. Auto mode uses information from a communicating GX system to follow available surplus and the configured battery conditions. A saved schedule does not take control while another mode is selected.

For diagnosis, record the mode, the displayed reason for waiting and the vehicle’s own charging restrictions. A departure timer or charge target in the car can prevent demand even when the station is ready. Change one control layer at a time: first establish that the vehicle and station can charge in an appropriately limited manual test, then verify the intended automation. A successful manual session proves neither surplus detection nor scheduled operation.

What to check or record

1. Confirm the selected mode and whether the vehicle requests charging.
2. For Auto, verify GX communication and live system measurements.
3. For Scheduled, check both the scene’s enabled state and the station’s operating mode.
4. Record the actual current after each controlled test.

The station’s rating is one limit; the supply, phase arrangement, configured current and vehicle also matter.

An AC station makes an allowed current available; the vehicle’s onboard charger determines what it can accept. Record the actual number of charging phases and the current on each phase before comparing a power reading with the station’s headline rating. A vehicle capable of less power will not become a higher-power charger because the station limit is raised.

For a simple illustration at 230 V and near-unity power factor, 6 A on one phase is about 1.38 kW; three equally loaded phases at the same current total about 4.14 kW. These are arithmetic examples, not recommended installation settings. The maximum-current field must stay within the approved circuit and installation limits. Do not infer automatic switching between single-phase and three-phase operation from a product’s ability to support either connection; verify the exact hardware and documented feature.

What to check or record

1. Record installed phases, permitted current and the car’s AC charging capability.
2. Compare measured current and total power during the same stable interval.
3. Check whether Scheduled mode is imposing its own current value.
4. Have the installer establish the allowable circuit limit.

PV production is not the same as surplus; minimum current and optional top-up settings affect the result.

First subtract other loads from generation and check the EVCS start condition for the home battery. A bright day can still leave too little surplus for the minimum charging current accepted by the station and vehicle. If the configured minimum is increased, the power needed to start increases too. Check the actual charging phases instead of treating a single-phase example as the requirement for every installation.

The low-surplus option can supplement available solar power to meet the minimum charging requirement. The separate battery/grid continuation option and its timeout can keep a session running through a temporary shortfall. These options deliberately change the meaning of solar-only behaviour. The EVCS cannot independently choose whether the additional energy comes from the grid or the home battery; the inverter’s energy management determines that flow. Compare charger settings with simultaneous PV, load, grid and battery readings before changing thresholds.

What to check or record

1. Check available surplus, not just total PV power.
2. Verify home-battery SoC start and off-grid stop conditions.
3. Inspect low-surplus permission, battery/grid continuation and its timeout separately.
4. Observe a surplus increase and decrease and record start/stop behaviour.

The configured position must match the actual AC wiring, and Auto requires a working GX link.

The position setting distinguishes a station connected on the inverter’s AC-input side from one supplied by its AC output. Read the installation drawing or ask the installer; do not select the position that produces the most attractive diagram. This distinction affects how the system interprets charging in relation to its supply and loads.

For GX communication, follow the documented discovery and pairing procedure, verify the intended GX identity and use the communication check. Relevant service settings on the GX must allow the supported connection. A station and GX can both have internet access while local communication between them is blocked. If multiple GX devices share the network, use the documented EVCS whitelist arrangement to restrict the intended controller and remove unintended duplicate registrations. Keep an address reservation or documented network configuration so a router change does not silently break the link.

What to check or record

1. Confirm AC-in or AC-out placement from the real wiring.
2. Verify the correct GX device and VRM installation identity.
3. Test local communication after network changes.
4. Check unintended discovery when several GX devices are present.

Separate wireless connection, address assignment and GX communication before resetting the charger.

The documented EVCS wireless connection uses the 2.4 GHz network. Check signal quality at the installed station, router logs and whether the network credentials or address have changed. A nearby phone working well does not prove the station has the same radio conditions. Access-point mode creates the station’s own setup network; station mode joins the local network. Confusing those modes can make local access appear intermittent.

Record firmware, connection mode, signal reading and failure times, then compare them with router restarts, roaming or coverage changes. The manual provides a background scan-period option: its suggested configuration differs between a single intended network and multiple networks. Apply that guidance to the real topology instead of copying an unexplained forum value. After any change, verify both stable wireless association and the GX communication check. A factory reset discards useful configuration and should not be the first diagnostic step.

What to check or record

1. Record exact model, firmware and wireless mode.
2. Check the intended 2.4 GHz network and signal at the station.
3. Distinguish an IP-address change from a lost wireless connection.
4. Recheck charging control as well as web-page access.

A schedule needs the correct mode, enabled scene, local time and vehicle demand.

Check Scheduled mode first, then inspect the individual scene’s start time, end time, repeat pattern, enabled state and current. The current in the active scene governs scheduled charging; the manual-mode slider is not a second independent scheduled limit. A saved but disabled scene will not run. Confirm that the intended weekday and time zone match the displayed local time, especially after a move or seasonal clock change.

Also inspect the vehicle’s own schedule, departure target and maximum charge target. Two valid schedules can have no overlapping charging window. Use a short, supervised test window with an appropriate current and a vehicle requesting energy. Record whether the scene becomes active, whether the station offers current and whether the vehicle accepts it. That separates a clock or configuration problem from a car-side restriction without repeatedly rewriting all settings.

What to check or record

1. Check station mode and scene enable state.
2. Verify time zone, weekday and start/end times.
3. Read the current value inside the active scene.
4. Compare the vehicle’s timer and target with the station schedule.

Vehicle-account integration and the physical charging station are separate connections.

The station reports and controls its own charging operation through the supported GX and VRM connection. A vehicle integration links an account or manufacturer service so VRM can receive additional car information, such as its reported battery state. Seeing the station in VRM does not prove that a vehicle account is linked, and seeing a vehicle’s state does not prove that the station’s current limits or solar mode are correct.

The official vehicle-integration page is marked as a working draft and the related forum topic describes a beta. Requirements, supported vehicle capabilities and commercial terms can change. Check the current integration screen and documentation when setting it up; do not reuse an old beta payment example or assume all brands expose the same controls. Review what vehicle data is shared with other installation users. Community integrations or OCPP projects must also be distinguished from documented support in the exact Victron product and firmware.

What to check or record

1. Commission the physical EVCS before adding optional account integration.
2. Check current vehicle support, requirements and terms in the official setup flow.
3. Verify data-sharing choices for installation users.
4. Keep vehicle permissions separate from station and GX configuration.

The station can react to system limits; the setting is not necessarily being lost.

Check the station’s status together with the inverter’s overload state, AC-input limit and current system load. The documented overload function can reduce charging and stop it if the limiting condition persists. Repeated events can produce a further reduction. Simply restoring a larger charging current can recreate the same conflict rather than solve it.

Record what else switched on and which supply was active. A system on inverter backup or generator power can have different available headroom from normal grid operation. Several chargers or other large loads also share the installation’s finite capacity. Compare the approved electrical limit with actual phase currents and the energy-management configuration. First establish why the controller is limiting the station; change permitted priorities or schedules within the installation design instead of disabling protection to preserve charging speed.

What to check or record

1. Capture EVCS warning, inverter state and phase currents at the same time.
2. Compare grid, generator and backup operation separately.
3. Check active schedules and concurrent large loads.
4. Have the installer assess capacity if normal loads repeatedly trigger limits.

Use a staged test so each configuration layer has a known working result.

1. Record the installation. Identify the exact station model and firmware, vehicle, supplied phases, permitted circuit current, GX device and AC-in or AC-out position. Obtain those electrical details from the installation record. Note which functions are required: manual charging, fixed schedules, solar-surplus charging or optional vehicle-account integration. Do not begin by enabling every available option.

2. Establish access and identity. Configure the documented local connection, owner credentials and intended network. Record the local address or reservation, time zone and clear device name. Verify access after a reconnect. For GX-connected operation, pair the intended device and run the communication check. Confirm that the station appears in the correct VRM installation, and resolve duplicate discovery before relying on remote control.

3. Set the current envelope. Enter the installation-approved maximum, and a minimum compatible with the vehicle and intended operating method. Record whether the power reading represents one or multiple phases. Carry out a controlled manual charge and compare the requested current, measured current, total power and vehicle status. Check stopping from the normal interface. This is a functional test after electrical commissioning, not a substitute for protection tests.

4. Configure solar behaviour. For Auto mode, establish valid GX power and home-battery data first. Set the home-battery start condition and any applicable off-grid stopping reserve. Decide explicitly whether low-surplus top-up or battery/grid continuation is allowed, and record its timeout. Observe operation when surplus rises and falls. A setting intended to avoid repeated starts can legitimately draw energy from another source; verify that this matches the owner’s expectation.

5. Test the schedule separately. Select Scheduled mode, enable a short test scene and check its local start/end time, repeat days and current. Align or temporarily avoid conflicting vehicle timers using the owner’s normal controls. Observe the scene becoming active and the vehicle accepting energy. Then restore the intended operating schedule and verify its next occurrence.

6. Hand over evidence and recovery. Save the available configuration backup, successful test readings and the owner’s access method. Explain which screen changes the operating mode, where scheduled current is set, what Auto may draw from the battery or grid, and how to identify a network or vehicle-side restriction. If optional vehicle integration is added later, check its current requirements and sharing permissions independently. Retain a working baseline before changing automation.

Configuration details

Operating mode

Where it is used

EVCS operating controls

What to enter or collect

Select Manual, Auto or Scheduled for the intended charging method.

Why it matters

The selected mode determines which control path is active; saving a schedule alone does not activate it.

AC connection position

Where it is used

EVCS setup / GX communication

What to enter or collect

Select AC input side or AC output side according to the installation drawing.

Why it matters

The system must interpret vehicle charging on the correct side of the inverter.

Maximum charging current (A)

Where it is used

EVCS current-limit settings

What to enter or collect

Enter the installer-approved limit within the exact station and circuit ratings.

Why it matters

This bounds charging demand; it does not replace the installation’s electrical protection.

Minimum charging current (A)

Where it is used

EVCS current-limit settings

What to enter or collect

Use a minimum supported by the vehicle and the documented operating method.

Why it matters

A higher minimum requires more available power before solar-surplus charging can start.

Auto battery conditions and continuation

Where it is used

EVCS Auto-mode settings

What to enter or collect

Record battery start SoC (%), applicable off-grid stop condition, top-up permissions and continuation timeout.

Why it matters

These choices determine reserve protection and whether a solar shortfall may be supplemented by battery or grid energy.

Scheduled scene

Where it is used

EVCS scheduler

What to enter or collect

Enter enabled state, repeat days, local start/end times and scene current (A); select Scheduled mode.

Why it matters

The active scene’s current and timing must agree with the vehicle’s own timer and demand.

What to check or record

1. Electrical installation and protection commissioned by the installer.
2. Correct station identity, network, clock and GX pairing verified.
3. Manual charging and stopping observed within the permitted current.
4. Auto start/stop and optional top-up behaviour demonstrated.
5. Schedule tested with the vehicle’s own timer taken into account.
6. Backup and owner operating instructions saved.

Separate lost monitoring, competing Modbus clients and firmware behaviour from an actual loss of solar production.

First check the inverter’s own status: a missing GX tile does not by itself prove that generation stopped. Record both device models and firmware, local addresses, the enabled Modbus TCP port and device identity. Follow the exact integration instructions and document address reservations. Do not overwrite an existing meter’s communication setup merely to copy a screenshot.

The SolarEdge SunSpec technical note describes support for a single TCP connection. Another monitoring client, such as a home-automation integration, can compete for that connection. Investigate the client list and arrange a controlled test with the intended monitoring path. Stable Ethernet does not rule out a protocol or firmware problem.

The popular forum discussion covers different firmware combinations and dated fixes. An old bug report or another owner’s rollback is not a universal remedy. Compare current vendor guidance and provide timed disconnect/reconnect evidence. Monitoring visibility also does not prove that islanded frequency control or zero-export configuration is correct; those require their own integration checks.

What to check or record

1. Record GX and SolarEdge versions together with the first failure time.
2. Check network identity, Modbus settings and additional clients separately.
3. Use vendor-supported update or recovery guidance; preserve configuration before changes.