Solar Chargers indicate an error with their LEDs. See the Toolkit App for the LED codes.
Detailed error codes can be read with a remote panel, such as the Color Control GX or the MPPT Control.
This error will auto-reset after the battery voltage has dropped. This error can be due to other charging equipment connected to the battery or a fault in the charge controller. This error can also occur if the battery voltage (12, 24 48V) is set to a lower voltage than the connected battery.
Check if the T-sense connector is properly connected to a remote temperature sensor. Most likely cause: the remote T-sense connector is connected to the BAT+ or BAT- terminal. This error will auto-reset after proper connection.
Check if the T-sense connector is properly connected to a remote temperature sensor. This error will not auto-reset.
Check if the V-sense connector is properly connected to the battery terminals. Most likely cause: the remote V-sense connector is connected in reverse polarity to the BAT+ or BAT- terminals.
Check if the V-sense connector is properly connected to the battery terminals.
This error will auto-reset after charger has cooled down. Check the ambient temperature and check for obstructions near the heatsink.
This error will auto-reset. If the error does not auto-reset disconnect the charge controller from all power-sources, wait 3 minutes, and power up again. If the error persists the charge controller is probably faulty. A cause for this error can be switching on a very large load on the battery side.
The maximum bulk time protection is a feature that was in the chargers when they were just released (2015 or earlier) and later the feature was removed.
If you do see this error, then update to the latest firmware.
If you then still have the error, perform a reset to factory defaults of the configuration, and reconfigure the solar charger.
This protection is default enabled on the Skylla-i and the Skylla IP44.
This error is generated when the battery-absorption-voltage is not reached after 10 hours of charging.
The feature of this safety protection is to detect a shorted cell; and stop charging.
This error will not auto-reset.
Disconnect all wires, and then reconnect all wires. Also, make sure the minus on the MPPT charge controller (PV minus/Battery minus) is not bypassing the charge controller.
If the error remains, please contact the dealer, there might be a hardware defect.
Power terminals overheated, check wiring, including the wiring type and type of strands, and/or fasten bolts if possible.
This error will auto-reset.
This error will not auto-reset.
Disconnect all wires, and then reconnect all wires. If the error persists the charge controller is probably faulty.
Note that this error was introduced in v1.36. So when doing an update, it might look like the firmware update caused this issue; but it doesn't. The Solar charger was then already not performing 100% before the update; updating to v1.36 or later merely made the issue more visible. The unit needs to be replaced.
This error will auto-reset after PV-voltage has dropped to safe limit. This error is an indication that the PV-array configuration with regard to open-circuit voltage is critical for this charger. Check configuration, and if required, re-organise panels.
The current from the solar-panel array has exceeded 75A. This error could be generated due to an internal system fault. Disconnect the charger from all power-sources, wait 3 minutes, and power-up again. If the error persists the controller is probably faulty, contact your dealer.
To protect the battery from over-charging the panel input is shorted.
Possible reasons for this error to occur:
If the error persists the charge controller is probably faulty.
If the charger is unable to turn off the PV input, it will go into a safe mode in order to protect the battery from over-charging or having a high voltage on the battery terminals. In order to do that, the charger will stop charging and disconnect its own output. The charger will become faulty.
Communication with one of the paralleled controllers was lost. To clear the warning, switch the controller off and back on
The controller is being paralleled to another controller that has different settings and/or a different charge algorithm.
Make sure all settings are the same and update firmware on all chargers to the latest version
The charger is configured to be controlled by a BMS, but it does not receive any control messages from a BMS. The charger stopped charging, as a safety precaution.
This Error only shows when there is solar power available and thus the Solarcharger is ready to initiate charging. It does not show at night. And in case there is a permanent problem, the error will raise in the morning and clear at night, and so forth.
Check the connection between the charger and the BMS.
How to reconfigure the charger to standalone mode
Our Chargers and Solarchargers automatically configure themselves to be BMS-controlled when they are connected to one; either direct or via a GX Device. And that setting is semi-permanent: power cycling the charger will not reset it.
Here is what needs to be done to make the charger operate in stand-alone mode again, ie. not controlled by a BMS:
Applies to SmartSolar/BlueSolar MPPTs VE.Can (FW version v1.04 or higher) and SmartSolar VE.Direct MPPTs (FW version v1.47).
To clear the error on the SmartSolar VE.Direct MPPTs update the FW version to v1.48 or higher.
To clear the error on the SmartSolar/BlueSolar MPPTs VE.Can, update the software. If the error persists, it will be because the charger is connected with both a VE.Direct cable and on VE.Can. That is not supported. Remove one of the two cables. The error will disappear and the charger will resume normal operation, within a minute.
Error 68 indicates that the charger detects multiple conflicting network sources, with the same priority, trying to send the same information to the charger. VE.Can and VE.Direct interfaces have both the same priority level, and BLE (using VE.Smart Networking) has a lower priority.
Having a higher priority level means that, if the same information (e.g. Battery voltage sense) is being received from both VE.Can and BLE (using VE.Smart Network) by the charger, the information on VE.Can will be used and the one coming from BLE will be ignored.
Now, if the same information is being received from two interfaces that have the same priority level (as VE.Can and VE.Direct), the charger does not know how to prioritize those, causing error 68 to be triggered.
This error will reset after the CPU has cooled down. If the error persists, check the ambient temperature and check for obstructions near the air inlet and outlet holes of the charger cabinet. Check manual for mounting instructions with regard to cooling. If error persists the controller is probably faulty.
If the unit does not work and error 116 pops up as the active error the unit is faulty, contact your dealer for a replacement.
If the error is only present in the history data and the unit operates normally this error can be ignored safely. Explanation: when the units power up for the very first time in the factory, it does not have calibration data and an error 116 is logged. Obviously this should have been cleared, but in the beginning units left the factory with this message still in the history data.
SmartSolar models (not the BlueSolar models): upgrading to v1.4x firmware is a one-way trip, you cannot go back to an older firmware version once you upgrade to v1.4x. Reverting to older firmware gives error 116 (calibration data lost), this can be fixed by re-installing the v1.4x firmware.
The charger cannot read its configuration, and stopped.
This error will not auto-reset. To get it working again:
Please do report this to your Victron dealer and ask him to escalate it to Victron; as this error should never happen. Preferably include firmware version and any other specifics (VRM URL, VictronConnect screenshots or similar).