Hello all. Got up this morning and see there has been a power outage during the night. It looks like the Quattro switched off because the BMS stopped responding (BMS lost). Anybody know what might cause this? There was an electrical storm.
BTW, the BMS is Pylontech
If your BMS/COMMs ports were damaged, this would happen.
You can try change masters, assuming the GX is working fine.
Thanks. It’s the first time it’s happened and was only off for a moment. I don’t know how to check it.
You can try power off and reset the whole battery bank, to see if that helps.
But a nearby strike can cook network ports easily, and hop across the other connections as well.
You will need a known working source to confirm if you have an issue on the GX, on the master BMS, or the broader pack.
Changing the battery master is easiest to start with, it is just re-ordering the CAN connections on the battery.
If you aren’t familiar with this, I suggest you find a professional to assist.
OK. So I power down and swap the connections so the physical “top” battery is no longer master. Or do I not need to power down for that?
iirc, you need to power them down then bring them back up, master first.
Makes sense. But if I’m not mistaken, I have to connect the top to the bottom, which will require a long lead. Knowing these things, I doubt an ethernet patch will work.
Yes, you need to change how the slave packs are connected as well to the new master as per the pylon guide. You will have to shuffle things around.
You could just try connect one battery as a new master just to confirm where the issue might be, and then get some new network cabling to reorder the stack.
Trouble is, currently there is no issue. All works fine. It was just a glitch. BTW, I was looking at what cables I have and reading the Pylontech book. It shows the 180mm connecting cables as pins 1-3 NC, but the supplied cables seem to be fully wired. I have some black cables with blue labels that look like they should work ie; 1-3 NA 4-8 pin-pin, so Maybe I could connect bottom to top with that.
I just checked the 180mm connector cables with a meter and they are 1-8 pin-pin.
Had the same Problem at 09:33 German time in the morning. Please Check my Post. Maybe there are other User affected.
“Please Check my Post.” Sorry, what post?
So it looks like it might be the CCGX at fault. Perhaps I should dig that Pi out of the cupboard…
Different issue and only relates to 3.60 which creates ongoing problems due to CPU overload, not purely a glitch.
CCGX’s have currently been limited to 3.55 while it is looked at.
I would downgrade as that is recommended, you can swap versions via the backup firmware menu on the GX.
Heh. 3.55 was marked as a “version upgrade”. I just hope it doesn’t revert when I’m not looking.
Disable the auto update option as well so long. That way you are in control of updates.
Currently 3.60 is hidden from CCGX’s so it cannot revert, but if 3.61 is released it would update if set to auto.
OK, thanks. Done that. How will I know when it’s safe to move on?
