So 120 equals 80 percent actual charge?Ok, after two 8.5 hour drives, setting SOC to 120 as per the referenced post makes the BMS stop charging at 80%. Probably don't want to go higher with an AGM, but the actual value can be set as high as 200% ?stays in conventional charging, never saw any refresh mode.
All I can say is that's what happened to me. I used OBD Fusion via CarPlay, connected to a VeePeak BT+ (BTLE) dongle. That way I could monitor continuously while driving. If I disconnect the battery and test it using an Ancel, it always tests good, 100% healthy, usually up around 100% SOC.
I just wished there was a way to disable bms all together with no faults in forscan like a fleet vehicle transit for exampleAll I can say is that's what happened to me. I used OBD Fusion via CarPlay, connected to a VeePeak BT+ (BTLE) dongle. That way I could monitor continuously while driving. If I disconnect the battery and test it using an Ancel, it always tests good, 100% healthy, usually up around 100% SOC.
Even after long drives, my dashcam powers down instead of going into parking mode when it supposedly "sees" 11.8V; this often happens also during a FORScan or FDRS session when they report 12.1V or sometimes even more. This could be the fault of the dashcam, but at these times the truck's modules are definitely not fully shut down; there's a lot of current draw within a few seconds of hitting the start button for ignition off.
There is also a BCM software update which is meant to improve charging strategy for the BMS that none of us except security-accredited people can do (the kind of people / businesses that can do PATS programming for keyfobs etc.). The only solution anyone has actually found for this mess is to put a bigger battery in the truck: H7 for powerboosts, H7 or H8 for non-PBs ?
