Bp Solar Inverter Error Codes
Brinda
This error will auto-reset after the battery temperature has dropped.The charger will stop charging to prevent damaging the battery.The battery temperature can be received by an external sensor (like Smart Battery Sense or BMV), or measured by the charger when this feature is available.
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.
Disconnect all wires, and then reconnect all wires, to make restart the charger. Also, make sure the minus on the MPPT charge controller (PV minus/Battery minus) is not bypassing the charge controller.
This condition indicates an over-current condition on the battery side. It can occur when a battery is attached to the unit using a contactor. Or in case the charger starts up without a battery connected but connected to an inverter that has a large input capacitance.
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.
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 the rated current limit. 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.
If you are using firmware v1.08 or newer this error indicates that the internal dc voltage is too high. 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.
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.
Some loads like motors or pumps draw large inrush currents in a start-up situation. In such circumstances, it is possible that the start-up current exceeds the over current trip level of the inverter. In this case the output voltage will quickly decrease to limit the output current of the inverter. If the over current trip level is continuously exceeded, the inverter will shut down: wait 30 seconds and then restart.
A high ambient temperature or enduring high load may result in shut down to over temperature.Reduce load and/or move inverter to better ventilated area and check for obstructions near the fan outlets.
If the battery voltage is getting low and a large load is applied to the AC output the inverter is unable to maintain the proper output voltage.Re-charge the battery or reduce the AC loads to continue operation.
This error shows when the charger is configured to be controlled by a BMS, but does not receive any BMS control messages. In that situation, the charger stops charging by reducing its output voltage to the battery base voltage (12V/24V/36V/48V). This is a safety mechanism, the reason to still enable the output is to allow a system to self-recover from a battery low situation.
Solar Chargers only show this error when there is solar power available and thus the device 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.
Our Chargers and Solar Chargers 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.
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.
There are units present with incompatible firmware on the can bus. Make sure that all units are updated to the same firmware version.All units will remain off until the until the firmwares are updated, after which the units will resume operation.
The number of inverters in parallel doesn't match with the transfer capabilities of the ac input relay of the Multi RS or Transfer switch.Firmware v1.12 does not support parallel units and a grid connection, so any combination of a Multi RS with a grid connection with more than one unit in parallel will trigger this error code on the Multi RS. The Multi RS only supports 3 units in 3-phase configuration at the moment.
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 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.
This error indicates that a firmware update did not complete, so the device is only partially updated.Possible causes are: device out of range when updating over the air, a cable got disconnected or power was lost during the update session.
When your GX device is connected to VRM, you can do a remote firmware update using this firmware file. You can do this via the VRM website or using the VRM tab in VictronConnect. VictronConnect can also be used together with the firmware file to update using a Bluetooth connection.
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).
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 powers up for the very first time in the factory, it does not have calibration data and an error 121 is logged. Obviously this should have been cleared, but in the beginning units left the factory with this message still in the history data.
First, make sure to update the firmware to v1.08 or later. The limits were too strict in earlier versions. And it could trigger falsely during MPPT start-up in the morning and MPPT shutdown in the evening.
This error will not auto-reset. Check the installation and restart the unit using the power-switch. If the error persists, even after above mentioned firmware update, the unit is most likely faulty and must be sent in for repair/replacement.
When your solar inverter starts to play up it will display an error code that can help you troubleshoot the problem. In this guide we discuss solar inverter error codes for all the major solar brands & provide troubleshooting to help you fix the problem.
A great thing about Fronius inverters is that they perform self-diagnosis which automatically informs the owner about the problem immediately. Fronius inverter models have different fault and error codes. These codes are categorized as:
Error Code 314 on a Fronius inverter means that there is a current sensor calibration timeout or there is an internal system error. Usually, this problem just fixes itself as the inverter repeats its startup routine. If the problem persists, you should contact us on (08) 7078-7620 to investigate the issue.
Whenever a Growatt solar inverter experiences faults, it will display the fault or error code. These codes indicate a particular problem or fault that the inverter is in. Listed below are some common error and fault codes that Growatt inverter users may face in the future and how it can be fixed:
64591212e2