Tinbum

Here you are... the latest I managed to find for both old and new chip. 
From the bin file for the new chip(v2.2), it just seems they refactored some code, so no major changes from v2.1.
 
I noticed there is also support for UP5000 as well on these versions. 
 
US_C_stV2.9_NTV2.2Crc.zip
 

For US3000C the highest/lowest voltage cell and highest/lowest temperature cell functions were implemented in 2.1ST firmware (see the table below). For a shame, with that bad sample bug.  Fix is in the 1.7NT and 2.8ST firmware.
So, your firmware is definitely able to report these.
AFAIK the reason why you are not seeing those CAN IDs is that you must "feed" the BMS with a proper "unlock" CAN message first, in order to start broadcasting them. Normally, Pylontech is broadcasting standard IDs only, but those details are considered diagnostic IDs.
Since I am not using this feature personally, I don't know what's the actual "unlock" message, but I would try plain 0x305 : 00-00-00-00-00-00-00-00 first. If that won't work, then you can sniff the CAN comm between Pylontech and Victron Venus OS (you can put Venus on a RPi with CAN HAT).
Anyway, if you discover a proper unlock message, let me know for sure, as I'd like to store it in my knowledgebase
 
 

LINK: https://www.victronenergy.com/live/battery_compatibility:pylontech_phantom
 
 

Ah, that's because the BMS is limiting it. In your first shot the battery is at 52% which is when you say it reaches its max SOC.
I'm pretty sure your problem is because you fitted the new batteries when they were at 52% SOC (or perhaps say 30% and SOC is average), as supplied by Pylontech and the older ones were 100% SOC ie fully charged. (Edit probably the opposite way round as the manual says they come at 100% soc unless otherwise requested by supplier.)

I'd say it doesn't really matter, both will work fine, but it would more depend on how you wish to fuse and if you want the ability to isolate if you have a problem.
 

Yes, it is an interesting story actually: Some time ago, Pylontech implemented 0x371 with couple of other IDs in order to report more detailed diagnostic data. Highest cell Voltage, Highest cell temperature etc. Victron happily grabbed that data with Venus, but also tied an alarm to it. So, once in a while, when Pylontech sent a bad cell voltage sample the Venus went into panic mode, alarms beeping, phones ringing, people scared to death...
Later on, this was fixed by Pylontech FW update - new code does not send cell measurement data that are obviously bad.
So yes, even such a simple information can cause a lot of chaos, if one party relies on it blindly while the other party does not really care a lot.

Have you looked at the data that Growatt send over the CAN bus? It's massive!!
Growatt BMS CAN-Bus-protocol-low-voltage-V1.08.pdf

That's a strange one to cause problems as it's only cell id's, isn't it..

@Shortcut Periodic keepalive frame (CAN 0x305) is normally NOT needed by Pylontech US baterries.
Some other, mainly high-voltage models, are using this technique. If the CAN 0x305 message will not be sent from the inverter every couple of minutes then these batteries will auto-shutdown.
If the support is saying that your brand new US5000 have this feature too, then this is really strange...or they are simply wrong, since their product portfolio is very broad as of today.
BTW: next time on the forum, I would suggest you to start a separate thread where you describe exactly what's the issue, what's the setup and how it behaves under various conditions. Because when "hijacking" some other's thread then your info ends up being mixed-up with the previous info, which makes things really messy.
Anyway, to some of your questions:
1) Yes, you can just bridge the internal fuses and rely on the external fuses or the DC breaker. But is it recommeded? Definitelly not. Those internal 4-pole fuses are being used for a reason.
2) If you start the battery and everything is green but there's no voltage on the terminals then the fuses are blown.
If you start the battery, everything is green and there IS voltage on the terminals but the battery is unable to power the loads and it's voltage is fluctuating then some other part of BMS board is fried. Mostly DFETs.
3) If you want to check what support is telling you about the keepalive, just setup Cerbo and connect it to the baterry via CAN cable. Cerbo is sending 0x305 regardless of battery needing it or not.
I'm really curious how this will end-up.
 
 
 
 
 

Leave them well alone if you want to claim.
They may reject a claim though because it's badly designed.

Yes, I use Eltek Flatpack Chargers but you do need a bit of programming / electronic ability.

Firstly that's not a report that I would accept. It says nothing at all about your battery other than it was swollen. Their is no data from your actual battery shown. It says possible faults including faulty bms - that is in the battery and therefor their responsibility. You need the actual data from the battery. You should also get the data from your good batteries using BatteryView to show what voltages etc were being reached.

You need to measure the voltage at the terminals

Yes, the Pylontech is compatible with Deye, thus always utilize the BMS communication. The BMS manages the battery system and communicates with the inverter. Why play around with voltages settings and risk voiding the warranty, when the solution is just as a click away?

Very interesting discussion here & we have had this discussion before. On the one hand Pylontech sits in China & sends these batteries globally. They then rely upon the main supplier to carry out any RMAs or repairs or investigations. They cover themselves with the BMS able to record logs of the operation of the battery & what it has been exposed to. 
The problem is that there are massive variations of quality in installers/ Owner installers & inverters. Some inverters support the Comms & others don't. If the inverter doesn't support the Comms then you rely on knowing what to do to setup the settings properly on the inverter. If there is Comms there is a Hit & miss chance whether the installer gets the Comms established & then also covers himself to get the user settings also setup just in case the Comms fails. 
In all these cases Pylontech has written the fine print very well & they request the Logs & if the battery tells a story that shows any of the above not followed, they refute your warranty. 
I have experience of a full bank of 20kWh of Pylontechs that have been warranty covered before the Logs showed that we were on point. The main BMU had a major fault & could not be repaired. They repaid in full after an investigation that lasted 3 weeks of back & forth checking logs & investigation of a repair. In the end they validated the warranty & a full refund was provided. 
We can argue over the quality of their BMS or we can start to realise that you need this installed by someone who knows what they are doing so that you are protected by the warranty. What I have seen in this business is that so many people get into this game & say it's so easy anyone can do this....
The end results usually dont turn out good. This is not cheap equipment, do your research & protect your investment. 
Massive take away of this thread & others like this on PYLONTECH: 
Pylontech have a very specific way they want you to install their battery. They also have a strict policy of Comms setup or manual settings setup. If you violate these, you on your own & you can't then go back & make comments on what the BMS must & must not do. Their design is not hidden nor is their policy. If you buy a Pylontech follow the rules of use. Otherwise you will end up out of warranty & then guys like @BritishRacingGreen or myself might be able to process a repair outside of warranty with a JBD BMS replacement. 
 

Will probably be disliked to death for this and I'm not defending Pylontech, they don't need it and it's actually in my best interests to bash them to hell...
BUT
From their side, the battery should have been configured correctly and not be allowed to overvolt, the installer should know what they are doing, if they don't it's not Pylontech's fault. They've given the guidelines to follow, if you don't, well...
Best analogy I heard was the charge limit voltage is like a car's rpm redline, it'll allow you to go over but you really shouldn't. Then you proceed to rev the engine above the redline constantly and say it's Ford's problem when it blows...
The reasoning for allowing it to go over volt and not shutdown is as far as I can tell a customer experience one. Pylon's were initially designed and sold in, let's say, more civilised parts of the world where the people installing actually were trained, accredited and therefore knew what they were doing. 99.9% of the time an OV was just a blip and if the battery cut off, the system goes down, customer has a bad day and Pylontech look bad. So they "ass"umed the same here.
Only now down the line once these things have been in the wild west are they seeing the results of cowboy installers. I could tell you some horror stories of electricians who think they know how to install inverters because they're legally allowed to issue a CoC (bonded input and output neutral as well as earth to the chassis anyone?).
OP is likely out 28k unfortunately unless they can make enough noise that CNBM, SolarWay or their installer replaces it. If anyone else has Pylons in their setup, put them at around 0.5V below the max charging voltage on the spec sheet and you'll be fine.

Not sure why you think you will get flack for this- sounds absolutely fine.

Clue is in the question! ;)

I'd swap the pace for a JK- pretty well direct swap they are very similar and JK is much better..

I'd swap the pace for a JK- pretty well direct swap they are very similar and JK is much better..

That's all very well while the batteries are ok, it's when you get problems with the batteries /cells that things will go wrong. You have an excellent monitoring system, that you use / monitor, so could probably see if their was a problem developing. Most do not.
Inverter control was ok for lead acid as they were forgiving,  Lithium are not. They don't just put inverter control in a BMS for the sake of it- their is a reason.
I've been running mine for over 12 years, first with lead acid and then started on Lithium about 10 years ago.
I'm not saying any more on the subject it's up to you what you do with your own system but giving advice on others is a different matter.
I'm trying to find the best solution to the OP's problem.

Yes the BMS will still control the battery but it's not being done in the ideal / safest way. Your example is relying on last ditch protection.
Where I live we get cold temperatures and many see their BMS request lower currents to help protect the battery, the same is true for high temps. This is especially important for those that only have one battery pack that is all too common. How will your system do that to prolong your battery life? Perhaps you dont need it where you are, but others do.
Also one BMS is not the same as the next.

That is not the inverter managing anything it's battery chemistry. Charge a battery with a dumb battery charger and you will see exactly the same.

And I'm the opposite. I'd advocate getting a decent inverter instead of making do with some of the rubbish on the market..

And I'm the opposite. I'd advocate getting a decent inverter instead of making do with some of the rubbish on the market..