Flybyglass
Member
I found it very helpful to install a battery monitor on my V4 to get the picture what the charging system was doing. Something like this:One of the problems appears to be that long before you get an error code, the operating system stops charging the ohmmu battery completely. Not sure what that's about, but the day I got my last error code and I swapped out my V2 for the new V4 plus with Bluetooth, I checked the battery and it was nearly completely dead. So it had not been getting charged for many days or even weeks prior to the VC front error code appearing. This means everybody with Ohmmu's battery should be trickle charging until they get the V4 replacement.
It ism also possible right now the charging routine is different for the FSDBeta people and the non FSD. I have 2022.20.x and the charge voltage is about 14.25. Some on here with 2022.28.x have shown a charge about 14.6 and that small difference may make the difference with errors messages. Your observation on content changing charging profiles is correct. My fully charged V4 when installed was about then same voltage and the charing system was putting out. After each battery install, I notice it is normal for the car to charge for 4-6 hours then start resting that is when I received multiple VCFront errors until the system locked out charging the battery. I can only guess that since the battery was at 14.25 volts, and the charging system was off and that moment it was looking for 13.x or less and concluded worthing else was charging the battery and isolated it. Just a guess based on observed behavior. Raising the charging voltage .2-.3 on the non FSDBeta branch of software raises this differential and may prevent error generation. My battery again is a V4 not the V4+ (not sure if the + has a different capacity). I did find it interesting when talking to Electrified Garage folks that heir first comment is "Tesla has been messing with the charging of these cars for years" implying going back to the early S.