Here is the configuration:
Two SmartSolar 150/35 loading a 48 V LiFePO4 Battery disconnecting without error at around 30A load. New system running two 150/35 on two identic pv strings. The webpage https://www.victronenergy.com/live/ba... is known to me.
Nevertheless, I have no DX-device installed and the chargers have no bus connection with the BMS of the battery.
All three Victron MPPTs I have installed are charging bulk until a voltage level of 52.3V until Absorption and 51.00V Float.
This results in: At 97% battery charge status, both of the 150/35 are into Absorption and end up at 99% in Float mode. On lower currents than about 30A, everything works fine..
Again, I stress: The Victron chargers do not "know" anything from the battery. No bus connection beetween Victron chargers and battery BMS at all. I know, that Victron recommends using a DX-device in combination with Pylontech batteries, however, the Solar MPPTs of Victron are universal chargers, that are described in the manual as for universal use. Therefore I claim that these controllers in the present configuration should basically work, even without BMS bus control.
The controllers are intentionally undersized regarding battery charging current. The manual and the Victron layout software say, that this is possible in my configuration and the particular chargers will limit charging currents higher than 35A each. I've already checked that and it works without any overtemparature problem for a while.
Here is the error description: Both controllers sometimes switch off at battery charging currents above 30A, regardless of the battery's state of charge, and independently from each other. At the same time there is no error message. Not in the csv sheet, the LED still shows blue, as if the bulk load would run normally. After about 20 minutes, the charge current is switched on again and the controller charges the battery normally. If the charge current of 30A and above continues, the cycle repeats after about 15 minutes.
For demonstration, I have uploaded a video to https://youtu.be/XXRgIShPb9g
I have never watched such a behaviour on these usually very reliable devices and hope, that someone can point me in the right direction.
Thank you very much!