
Ultimately, I've also learned about the "BEM code" batteries, and I may possibly go for one of them next time, since they are properly "accepted" by the BCM (they are "pre-set" models). Just out of my curiosity: is SOC working on your Golf, and which year is your car, if I'm allowed to ask? but I don't know how reliable is that piece of info.and honestly doesn't make much sense to me: the module J367 is there anyway in my start/stop car, so I can't see any cost saving in 'blocking a feature', when the associated hardware is already there, and I guess it's main function is exactly to monitor the state of charge of the starter battery. There is also another possibility: browsing around the forums, I've read that the 'SOC' feature has been 'killed' by VW on Golf MY2016 (from May 2015 to May 2016.mine was 1st registered on March 2016). Also if apparently it's ininfluent, I may have to recode the manufacturer value, and change the serial again to tell the BCM: "start from scratch".

Obviously Yuasa hasn't got a vendor code in the BCM of VW, and therefore it's adviced to leave it on VA0 (or VAO), since apparently that setting always returns a "battery OK" status in the OEM log.


After a weekend driving (50 miles and 80 minutes), the SOC indicator is still on "-".ĭuring the weekend I've also been browsing the forums for info, and I've found that the manufacturer coding I've made is wrong.as a matter of fact, the only 'accepted' values are the following:
