MTTP 150/70 error code #38

is there any possible way to reset this error remotely?

No not according to the Manuel. See Error recovery below.

Err 38, Err 39 and Err 80 to Err 87 - PV Input shutdown

When these errors show, the PV Input is internally shorted in order to protect the battery from over-charging.

Prior to any other trouble shooting, make sure to update to the latest firmware version.

Possible reasons for this error to occur:

  • The Battery voltage (12/24/36/48V) is set incorrectly. Use VictronConnect to set the right Battery 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.

Error recovery:

  • Error 38 and Errors 84 to 87: 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 its maximum voltage setting (normally Equalisation or Absorption voltages). It can also takes a minute to reset the fault.

  • Errors 80 to 83: First disconnect the solar panels and disconnect the battery, then follow the reset procedure described here.

If the error persists the charge controller is probably faulty.

1 Like

ok here’s another question, i have 2 150/70 MTTP controllers with the exact same settings. the 150/70 controller that error has done it before sometime back and after resetting it it has been fine, both have the latest firmware except one is 3.16 and the other is something like 1.18 which doesn’t make any sense to me. one is a couple of years old and the other is only a few months old. (dont have my 5th wheel here, its at the dealership getting warranty work done) so i can only remote in to see it. wouldn’t both mttp error if i had the wrong settings in my multiplus 12 3000 2x120?

There can be a few triggers.

The real question is did the battery voltage rise above what was expected to trigger it - in other words is there a real reason why the protection activated?
Sometimes when a system gets shut down and restarted it happens.
The system is out of your physical control.

You can sometimes (firmware update) factory reset (sometimes repeat the process) and then re program and the error clears. But for the most part is needs a physical reset.

The error can sometimes be triggered falsely by using an incorrect battery profile and then setting the equalisation voltage close to absorption voltage. (Or by a live system battery disconnect during operation)

This is fine the firmware is very similar so that is not an issue (since victron connect would have loaded it.)

1 Like