how does the 58.8 compare with your expected and current Max battery Voltage? CCL is set to zero, so the BMS is telling the system not to charge.
The Cerbo output looks ok, you can find yhe contents of /dev/root with the ls command., however, it it the contents of /data you need to look at. I would have a look at your BMS configuration, as it looks like that needs updating.
Your MP2 charge voltage settings should be the same or higher than the maximum battery voltage desired, as otherwise as you have found, this will limit the charging. With old lead batteries, the charge current is often very limited due to sulphation. This does not mean that the charger is faulty.Similarly when discharged the voltage also drops rapidly.
So you need to set the Abs voltage in the MP2 to 58.8V, Float to 54.6V. Also set these value in any MPPT on the system.
Your MP2 charge voltage settings should be the same or higher than the maximum battery voltage desired, as otherwise as you have found, this will limit the charging.
Fully right, when the system was running a second Battery (LiFePo4 (Pytes E-Box)) has been connected in parallel, that’s why the MP2 voltage settings are currently lower - but it doesn’t explain the behaviour.
With respect to aging of LA I disagree. Normally they consume more power and turn them into losses (heating). And the sharp voltage drop can’t result from the battery, even when old, unless internally broken.
Today I realized with some further testing, that it takes “hours” for the MP 2 >charger< to sync and start-up. Our (home) grid is stable and it’s makes me wondering, too.
Anyhow, tomorrow the unit goes to service and I’ll gona report.
My personal guess, an internal “fuse” or “semiconductor” got blown up - for what reason whatsoever.
Thanks for trying to following me, good to know someone is out there