Jump to content

Battery Condition Monitor not communicating after new battery installed and coded


Jerram

Recommended Posts

Hi, 
New to the forum, and looking for some advice. Ive installed a new battery into my 2019 Golf-R estate, and coded it with OBDeleven pro. The new battery is an AGM096 from Halfrauds, with 70amp capacity. 
When the battery was installed, on first start the dash lit up like a christmas tree, with every conceivable fault (very stressful). A few YouTubes later it was all good, with just one remaining fault - the Battery Condition Monitoring control unit is not communicating. 

The car starts, stops and runs perfectly, and the battery seems to be charging well. But, I would like the BCM to function, and knowing I have a fault is irritating. 

Has anyone else experienced this fault - and is there a fix?  My local main dealer is Marshalls in Reading (UK), and I honestly do not want to go there ever again.  They are a shower of sh•t. 

Link to comment
Share on other sites

@Jerram: Hi.

 

Hmm......."a shower of sh*t"? I've not heard this simile before - what an impressive (and visually evocative) saying! May I add it to my lexicon, please - rest assured that I will quote your name whenever I use it?😜

 

OK, lets discuss the technical stuff and in true geek-speak, let's start in the best way possible - meaning a wiring diagram:

XW7JcFJ.png

 

Don't be intimidated by the picture - I just want you to focus on the bit of my diagram labelled  "J367", which is the name given to what you call the "Battery Condition Monitoring control unit".

 

It's probably too much information - but because I'm using the eloquent language of geek-speak,  J367 is a LIN slave module to the Gateway module

 

On MQB platform cars like your Golf R and as the module name implies, the life-purpose of J367 is to provide a continuous stream of real-time data about battery health to the Energy Management System (EMS). One of the many facilities in the car that uses this information is Start Stop (SS). So, while you say "the car starts, stops and runs perfectly" - I very much doubt that with J367 disconnected, the SS facility works!

 

The reason why I mention this is because disconnecting J367 is often done by misguided folk as an easy way of disabling SS. However, while It is indeed a very easy tweak - it has unintended and impactful consequences on the longevity of the battery in the longer term!

 

Of course I can't be certain that this is why J367 isn't communicating with the CAN network on this car - but it's a not uncommon reason for this error message!

 

So, as an early response to your post - I suggest that you eyeball the 2 x pin connector for j367 and confirm that the mating bit with the wiring loom is actually plugged-into (and seated properly with) the module socket.

 

J367 lives on the negative battery terminal as shown in my picture below (the plug/socket is item 2 )

f8Oe2FN.jpg

And to make it even easier,  here's a picture showing a real case of J367 (ignore the yellow-ish "shower of sh*t" - the gunk is an anti-frosting spray that we use down here in the Antipodes):

J5pbsSr.jpg?1

 

If the connector is correctly terminated to the car's wiring loom - please report back and we can discuss other possible remedies.

 

Don

 

Link to comment
Share on other sites

Hi Don,

Many thanks for your insightful reply.  The diagrams are very helpful.

I took the car to work today. It was a 2-hour round trip through traffic and on motorways. The start/stop function is still working (as are all other features that I could try, from heated seats through to lane assist). Nothing appears to be non-functional at the moment, from the drivers point of view. 

 

I did look at the connection to the battery condition unit (J367) on the negative terminal, and it was plugged in and seated correctly. I wonder if the J367 unit itself could be faulty - or more likely one of the relays (or even a fuse could be blown)? 

Link to comment
Share on other sites

@Jerram: Hmm.......... OK - as you probably already know, fault finding is a process of elimination!

 

Of course anything is possible and a forum like this is a terrible medium for conducting remote diagnostics - but I doubt that the fault is likely due to "one of the relays" because if you look at my wiring diagram, there ain't any relay in the J367 circuit!

 

However, I like you suggestion "or even a fuse could be blown"!  Again as shown in my diagram, J367 gets power from SB18 - maybe this is the culprit?

 

The location of the B fuse-block is shown below -maybe grab a multi-meter and check fuse #18. It's a 5 Amp fuse - so it doesn't need much electrical current to blow!

ln4FZ22.png?1

 

Don

Link to comment
Share on other sites

  • 6 months later...

Also want to join the conversation, and appreciate even the existence of this forum :)

 

We bought a Polo 6R and after taking delivery the battery was dead, "dealer" gave a new battery and I used my obd eleven to adapt it, think it was done right but might be worth reverting back to this point. Ever since I can remember the car has stated stop start error, if this is before or after the battery swop I don't know... I also have a standing P1B0200 Battery Monitoring Control module fault, checked the fuses and verified continuity between positive and one of the pins of the connector. 

 

Also when going into the settings of obd eleven, under gateway I cannot set the min/max temperatures of the stop start because it says module doesn't exist. 

 

Now... In a very dumbed down way, how do I fault find this issue? 

 

Doubt it has any relation but I changed the radio to an android unit, doubt any car functions reside in the radio but hey, everything is worth mentioning. 

 

I want to learn, but excuse if I sound dumb

Link to comment
Share on other sites

@Booysenc : Hi - it matters that you fill-in your location on your forum bio because the country determines the exact model Polo 6R

 

I don't have access to a wiring diagram for a 6R Polo with bluemotion. This limits my response - but I can't imagine that the set-up would be radically different from a wiring perspective to the arrangement in my initial diagram above.

 

As I hope that you can see - the battery monitor module (J367) has the following 2 x wires:

  • A +ve voltage supply from the fuse (which I understand that you have verified)  
  • A LIN wire - which is a single-wire, low-speed  protocol for communicating with the Gateway module (J533 in my diagram).

Is the 2 x wire connector actually physically plugged into the module housing that lives on negative battery terminal? If not, this will be the reason for the Start Stop (SS) error. 

 

I do not believe that a Polo 6R has the newer style UDS/ODX modules - so it won't have the "the min/max temperatures of the stop start" channels which are present in the later model Polo (like the 6C)

 

Don 

 

 

Link to comment
Share on other sites

Hi, 

 

Apologies, profile updated, I'm in the Netherlands.

 

Yes the connector is plugged in properly, one of the pins is connected to power as you stated, not sure where the gateway module J533 is located.

Is there a way to test the battery monitor module? Like if I read temps or current then I know that module is good?

 

I'll have a look if I can find wiring diagrams but agree, shouldnt be too different

Link to comment
Share on other sites

@Booysenc: Chaun - If you want notifications to be sent-out when you author a new post - you need to add my handle somewhere in your reply so that it appears as @dv52. To do this, start typing "@dv52" and click-on the auto generated text under your typing

 

OK- again, I don't have the wiring diagram for this car - but you won't find a physical, stand-alone J533 module on a Polo 6R  because J533 is physically integrated into J519 on this car. J519 is the module that OBD11 calls "central electrics" (or, "BCM" in VCDS speak - as you say in your first post).

 

If "the [J367] connector is plugged in properly" - does Start Stop (Bluemotion) work correctly on this car? If so, have you tried simply clearing the error with OBD11? If the error does not clear, please provide a OBD11 screenshot of the error message. To do this, load the picture on a third-party hosting site (like imgur, postimage etc.) and include the URL link on a new post.

 

To test J367 and because you have already confirmed volts to the module - I suggest that you test the LIN wire.  To properly test the LIN wire, you really need an oscilloscope, which I assume you don't have. However, it can be done (with less accuracy) using a multi-meter. To do this, set the multi-meter to measure DC voltage and check the voltage levels on the LIN pin with the cable connected; you should see a steady voltage of about 11-12 volts when the LIN bus is not communicating. If the bus is active as should be the case, the voltage will toggle rapidly between approximately 1 volt and 12 volts, indicating data transmission.

 

A better description of the test method is explained - HERE (note the bit about "recessive protocol")

 

Don

 

 

Link to comment
Share on other sites

@dv52, appreciate the help (both with the car and on the forum)

 

Here's the picture of the fault https://imgur.com/a/Hjas7JO

Also the wiring diagrams : https://imgur.com/xATsCtw

Start Stop does not work correctly, gives an error on the dashboard when I start the car.

 

Steps I've taken so far :

Cleared the fault a few times - returns immediately.

Disconnect cable from J367, this then changes the error to communication fault and not Faulty under the fault description

Disconnect cable from the alternator, still remains faulty.

using OBDeleven I changed the serial number of the battery, believe this is how the new battery is registered.

 

I don't yet have an oscilliscope, been wanting to buy one so might be a good idea, havent yet tested the communication with the multimeter - assuming the alternator needs to be unplugged to make sure comms is from J367 and not elsewhere.

 

I somewhat believe the connection to J367 is there since the error changed once it was no longer connected, just have no idea what to even test next.

 

Appreciate the help!

 

 

 

 

 

 

Link to comment
Share on other sites

@Booysenc Chaun: Excellent provision of information - well done!!!

 

So, stuff is much more clear-er with your wiring diagrams (WDs)-thanks for the pictures (one day - I must get myself a full copy to add to my database).

 

As I hope that you can see and as I said in my previous reply, the Gateway module on a Polo 6R is integrated into the BCM, which is called J519 in the WD. As shown in your pictures, the blue, LIN wire for J367 is connected to the J519 connector - specifically, pin #26, socket B. Other than this difference, the set-up for J367 is the same as on my original diagram which I posted early in this thread.

 

Note from the your WD that en-route from J367 to J519, the blue LIN wire terminates on pin #1 of TML. Whenever I see a coupling point intervention on a wire, it signals a possible cause for a non-functioning module - especially when the coupling point is located in the harsh environment of the engine bay (which is where TML lives). So, I suggest that you eyeball TML and also test the electrical integrity of the mating contact terminations on pins #1.

 

Have you had this car from new? If not, another reason for this error MIGHT-BE (caps for emphasis) that a previous owner has manually coded out J367 from J519 - I'm totally guessing, of course! If this is a possibility on this car - normally the way that J519 is told to start operating J367 via the blue, LIN wire is via a software switch on the BCM long-code string. Setting the correct Bit in long-code, activates a subroutine in the BCM firmware that controls J367. 

 

So again if this is a possibility -maybe it is worthwhile looking through the Bytes/Bit descriptors on long-code in the central electrics module for anything that is remotely like "battery monitor module". How comfortable are you with long-code using your OBD11 device?

 

Don 

 

 

Link to comment
Share on other sites

@dv52, appreciate the input, I'll have a look and revert.

 

I'm conflicted with some information but worth double checking anyway, I believe the LIN wiring should be fine because once I disconnected the module it changed the error from Fault to communication error, if the LIN line was broken it wouldn't know about the disconnection.

 

Had a quick look offline about the possibility of coding J367, couldnt see anything but will explore further, I can recall when I played around in the gateway menu one of the menu's brought up J367 so I somewhat believe that this might not have been disabled.

 

History of the car... life lesson for me and anyone interested... don't buy a car when you just immigrated, looking for something and the kids in the back seat shouting and screaming because they are excited to get out of the house. I have no history of the car, even the identification sticker in the trunk where the spare wheel is has been removed, I have no service history (good excuse to change the timing belt and do a full service - at least I now know it's good) but have no idea if things have been changed or settings modified. Again, fortunately there's a limit to the price of this life lesson and I'm gaining some exposure in fault finding.

 

Anyways, back to the problem, I'm comfortable to scratch around wherever, if you have any pointers please point out, I'm grateful of any guidance.

 

Cheers!

Link to comment
Share on other sites

@Booysenc Chaun: Hmm..........OK, life lessons are a good thing -notwithstanding that life lessons often come with a heavy price,  it's much better than not learning!!!

 

So, I'm not sure what "pointers" to  "point-out"? I guess the two most useful features with OBD11 (and the features that I wished that I knew when I first started using OBD11) is Freeze-frame and  History :

 

Freeze-frame: Whenever the self-monitoring system in this car senses an error of sufficient severity to be recorded in fault memory - a snapshot of the vehicle's sensor readings and conditions at the moment the Diagnostic Trouble Code (DTC) is also saved with the error details. This freeze-frame data often contains very useful information in the process of diagnostic analysis. However and for unknown reasons, the deities on the OBD11 mother-ship have decided that this is an opt-in feature. With VCDS, freeze-frame data is default enabled - a much better set-up IMO. So, I suggest that you enable Freeze frame - read THIS

 

History: I'm not sure if you are aware of this part of the OBD11 software - but the details of almost every OBD11 function that you use is recorded and saved in a file that lives against your account number!  To access your History records - read HERE

 

Making sense of the records in History is often difficult especially if the file is big. So, it's usually better to filter-out unwanted data and to digitize the information so that it can be read on a PC screen -this is done as follows:

  1. Fire-up OBD11 software - no need to connect to the dongle
  2. Select Garage tab in the Home screen (lower left-side)
  3. If you have registered multiple cars on you account - select the the correct vehicle
  4. On the car information screen - scroll-down and select History
  5. Follow the screen instructions below:
    OLdpB2w.png?1
  6. On the 2nd screen above -tick the required elements in the Filter and deselect ALL unwanted entries 
  7. After you receive the Email that you sent to yourself (last screenshot) - open/read/copy the file information on a PC.

 

18 hours ago, Booysenc said:

I'm conflicted with some information but worth double checking anyway, I believe the LIN wiring should be fine because once I disconnected the module it changed the error from Fault to communication error, if the LIN line was broken it wouldn't know about the disconnection.

 

Had a quick look offline about the possibility of coding J367, couldnt see anything but will explore further, I can recall when I played around in the gateway menu one of the menu's brought up J367 so I somewhat believe that this might not have been disabled.

 

Yes, your observations with the LIN wire test is "conflicting" - but perhaps it's also instructive? If as you say the test suggests that the LIN wire is OK - then the same result also suggests that the module itself is OK!  The only logical conclusion from these deductions is that the error is NOT a problem related to either the physical infrastructure related to J367, or the operation of  J367. This leaves ONLY the possibility of a coding issue with J519 - I think!

 

After you absorb the two OBD11 features in my opening words above - maybe use the History records to find-out when the J367 error first happened. If the DTC-date was after you purchased the vehicle - again look through the History entries around the DTC-date for any manual coding changes that were made to the central electrics module. If any records are found that even vaguely relate to J367 - revert the code change back to the "old value" as specified in the History record

 

Don 

 

Link to comment
Share on other sites

  • 2 weeks later...

Quick update, couldn't find any settings to enable or disable the J367 module, due to the error change to disconnected when unplugged I knew the wiring was OK, power was confirmed and I knew it was either a user problem not getting the setting or the module itself. Picked a brand new second hand part for 6euro (and some more for shipping) which was cheap enough for the risk. Quick install and everything works. 

 

Appreciate the assistance @dv52

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Current Donation Goals

    • Raised £170
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...