mppt-error-codes
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
mppt-error-codes [2017-09-15 14:41] – [Err 114 - CPU temperature to high] edevries | mppt-error-codes [2019-07-05 06:43] – [Err 20 - Maximum Bulk-time exceeded] mvader | ||
---|---|---|---|
Line 33: | Line 33: | ||
==== Err 18 - Controller over-current ==== | ==== Err 18 - Controller over-current ==== | ||
This error will auto-reset. | This error will auto-reset. | ||
- | Disconnect | + | If the error does not auto-reset disconnect |
- | 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. |
==== Err 20 - Maximum Bulk-time exceeded ==== | ==== Err 20 - Maximum Bulk-time exceeded ==== | ||
- | This error can only occur when the maximun bulk-time protection is active. | ||
- | This error will not auto-reset. | ||
- | This error is generated when the battery-absorption-voltage is not reached after 10 hours of charging. | ||
- | This protection is default disabled | + | === Solar Chargers === |
+ | 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. | ||
- | It is default enabled on the Skylla-i and the Skylla IP44. | + | If you do see this error, then update to the latest firmware. |
- | Our advice is to not enable it on solar chargers. | + | If you then still have the error, perform a reset to factory defaults of the configuration, |
+ | |||
+ | === AC Chargers === | ||
+ | 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. | ||
==== Err 21 - Current sensor issue ==== | ==== Err 21 - Current sensor issue ==== | ||
Line 58: | Line 62: | ||
This error will auto-reset. | This error will auto-reset. | ||
+ | |||
+ | ==== Err 28 - Power stage issue ==== | ||
+ | |||
+ | This error will not auto-reset. | ||
+ | |||
+ | Disconnect all wires, and then reconnect all wires. If the error persists the charge controller is probably faulty. | ||
==== Err 33 - PV over-voltage ==== | ==== Err 33 - PV over-voltage ==== | ||
Line 65: | Line 75: | ||
==== Err 34 - PV over-current ==== | ==== Err 34 - PV over-current ==== | ||
The current from the solar-panel array has exceeded 75A. This error could be generated due to an internal system fault. | 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, | + | Disconnect the charger from all power-sources, |
- | This error will auto-reset. | + | |
- | ==== Err 38 - Input shutdown | + | ==== Err 38, Err 39 - PV Input shutdown ==== |
- | To protect the battery from over-charging the panel input is shut down. To recover from this condition first disconnect the solar panels and disconnect the battery. Wait for 3 minutes reconnect the battery first and next the panels. | + | To protect the battery from over-charging the panel input is shorted. |
- | A common reason | + | Possible reasons |
+ | * The Battery voltage (12/24/48V) is set, or auto-detected, | ||
+ | * There is another device connected to the battery, which is configured to a higher voltage. For example a MultiPlus, configured to equalise at 17 Volts, while in the MPPT this is not configured. | ||
+ | * The battery is disconnected using a manual switch. Ideally the charger should be switched off before disconnecting the battery, this avoids a voltage overshoot on the charger output. If necessary the voltage trip-level for the PV Short protection can be increased by raising the Equalization voltage set-point (note: equalization does not have to be enabled in this case). | ||
+ | * The battery is disconnected using a Lithium charge relay connected to the “allow-to-charge” output of a BMS. Consider wiring this signal to the Remote terminal of the charger instead. This shuts down the charger gracefully without creating a voltage overshoot. | ||
- | Use VictronConnect to disable auto-detect | + | Error recovery: |
+ | * Error 38: First disconnect the solar panels | ||
+ | * Error 39: The charger will automatically resume operation once the battery | ||
If the error persists the charge controller is probably faulty. | If the error persists the charge controller is probably faulty. | ||
+ | |||
==== Information 65 - Communication warning ==== | ==== Information 65 - Communication warning ==== | ||
Communication with one of the paralleled controllers was lost. To clear the warning, switch the controller off and back on | Communication with one of the paralleled controllers was lost. To clear the warning, switch the controller off and back on | ||
Line 98: | Line 114: | ||
Note that (solar-)chargers automatically configure themselves to be BMS-controlled when they are connected to one; either direct or via a Color Control GX or Venus GX. | Note that (solar-)chargers automatically configure themselves to be BMS-controlled when they are connected to one; either direct or via a Color Control GX or Venus GX. | ||
+ | |||
+ | ==== Err 68 - Network misconfigured ==== | ||
+ | |||
+ | The charger detects multiple conflicting network sources trying to take control of the charger. | ||
+ | |||
+ | Applies to SmartSolar MPPTs and SmartSolar MPPTs VE.Can. | ||
+ | |||
+ | The typical reason for the error to show is that the charger is configured to operate in parallel using our [[https:// | ||
+ | |||
+ | Resolution: disable the parallel operation by connecting VictronConnect, | ||
+ | |||
+ | For SmartSolar MPPT VE.Can only, also make sure its not connected to a [[https:// | ||
+ | |||
+ | Once the conflict is resolved the error will disappear and the charger will resume normal operation, usually within a minute. | ||
+ | |||
+ | |||
==== Err 114 - CPU temperature too high ==== | ==== Err 114 - CPU temperature too high ==== | ||
Line 105: | Line 137: | ||
==== Err 116 - Calibration data lost ==== | ==== Err 116 - Calibration data lost ==== | ||
- | The unit is faulty, contact your dealer for a replacement. | + | 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: | ||
+ | |||
+ | 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. | ||
==== Err 119 - Settings data lost ==== | ==== Err 119 - Settings data lost ==== | ||
The charger cannot read its configuration, | The charger cannot read its configuration, | ||
Line 115: | Line 150: | ||
- wait 3 minutes, and power up again. | - wait 3 minutes, and power up again. | ||
- Reconfigure the charger. | - Reconfigure the charger. | ||
+ | |||
===== DISQUS ===== | ===== DISQUS ===== | ||
~~DISQUS~~ | ~~DISQUS~~ | ||
+ |
mppt-error-codes.txt · Last modified: 2024-02-12 05:48 by guy_stewart