User Tools

Site Tools


mppt-error-codes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
mppt-error-codes [2017-02-05 22:13] – [Err 67 - No BMS] mvadermppt-error-codes [2018-06-28 11:38] – [Err 18 - Controller over-current] rvanzundert
Line 1: Line 1:
 ====== MPPT Solar Charger Error Codes ====== ====== MPPT Solar Charger Error Codes ======
  
 +Solar Chargers indicate an error with their LEDs. See the [[https://www.victronenergy.com/support-and-downloads/software#victron-toolkit-app|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.
  
 ===== Error Codes ===== ===== Error Codes =====
Line 7: Line 10:
 This error will auto-reset after the battery voltage has dropped. 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 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 is set to a lower voltage than the actual battery voltage.
 ==== Err 3, Err 4 - Remote temperature sensor failure ==== ==== Err 3, Err 4 - Remote temperature sensor failure ====
 Check if the T-sense connector is properly connected to a remote temperature sensor. Check if the T-sense connector is properly connected to a remote temperature sensor.
Line 30: Line 33:
 ==== Err 18 - Controller over-current ==== ==== Err 18 - Controller over-current ====
 This error will auto-reset. This error will auto-reset.
-Disconnect the charge controller from all power-sources, wait 3 minutes, and power up again. +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
-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 ====
Line 45: Line 48:
  
 ==== Err 21 - Current sensor issue ==== ==== Err 21 - Current sensor issue ====
-The charge controller is probably faulty.+
 This error will not auto-reset. 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.
 ==== Err 26 - Terminal overheated ==== ==== Err 26 - Terminal overheated ====
 Power terminals overheated, check wiring, including the wiring type and type of strands, and/or fasten bolts if possible. Power terminals overheated, check wiring, including the wiring type and type of strands, and/or fasten bolts if possible.
Line 59: Line 65:
 ==== 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, wait 3 minutes, and power-up again. If the error persists the controller is probably faulty+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.
-This error will auto-reset.+
  
-==== Err 38 - Input shutdown due to battery over-voltage ==== +==== Err 38, Err 39 PV Input shutdown ==== 
-To protect the battery from over-charging the panel input is shut downTo 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. If the error persists the charge controller is probably faulty.+To protect the battery from over-charging the panel input is shorted 
 + 
 +Possible reasons for this error to occur: 
 + * The Battery voltage (12/24/48V) is set, or auto-detected, incorrectly. Use VictronConnect to disable auto-detect and set the Battery Voltage to a fixed voltage. 
 + * 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. 
 + 
 +Error recovery: 
 + * Error 38: First disconnect the solar panels and disconnect the battery. Wait for 3 minutes, then reconnect the battery first and next the panels. 
 + * Error 39: The charger will automatically resume operation once the battery voltage drops below the float level for 1 minute. 
 + 
 +If the error persists the charge controller is probably faulty.
  
 ==== Information 65 - Communication warning ==== ==== Information 65 - Communication warning ====
Line 74: Line 91:
  
  
-==== Err 67 - No BMS ==== +==== Err 67 - BMS Connection lost ==== 
-The charger is configured to be controlled by a BMS, but it does not receive any control messages from a BMS. The charger stopped charger, as a safety precaution.+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.
  
 Check the connection between the charger and the BMS. Check the connection between the charger and the BMS.
Line 86: Line 103:
   * VE.Direct solar chargers, reset the charger to factory defaults with VictronConnect, and then reconfigure it.   * VE.Direct solar chargers, reset the charger to factory defaults with VictronConnect, and then reconfigure it.
  
-Note that (solar-)chargers automatically configure themselves to be BMS-controlled when they are connected to one.+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 114 - CPU temperature to high ====+==== Err 114 - CPU temperature too high ====
 This error will reset after the CPU has cooled down. 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. If the error persists, check the ambient temperature and check for obstructions near the air inlet and outlet holes of the charger cabinet.
Line 94: Line 111:
  
 ==== Err 116 - Calibration data lost ==== ==== Err 116 - Calibration data lost ====
-The unit is faulty, contact Victron.+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. 
  
 ==== Err 119 - Settings data lost ==== ==== Err 119 - Settings data lost ====
mppt-error-codes.txt · Last modified: 2024-02-12 05:48 by guy_stewart

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki