[Fuentessegura]

That sounds REALLY REALLY GOOD!!
Juan Carlos you did a great job!! Congratulations!

Before you reprogram any module again, one question. Do you mean the automatic hight adjustment of the steering wheel? This is a setting, that can be enabled via the car dash display. Or is the hight adjustment not working at all? Even if you move the up and down knob under the steering wheel?

And yes, your battery need some attention. But no need to change it again now. Try to charge it over night in the car. Take the car for a 100 km ride. Switch off the engine. Measure the voltage. Wait over night and measure it again. Just post your values here. Then I can tell you more about your battery status.

Cheers
Dirk

I update the information, after finishing configuring everything, I have checked the battery connections, and to my surprise, I realize that the Jaguar mechanic has left the screw on the positive terminal of the auxiliary battery loose, the connector is not It made good contact, so I deduce that the problems I described in the previous message are due to that. By not making good contact, the battery module would not be reading well and that is why the charging error occurred, and there were false contacts in the browser. and instrument panel.
What do you think about it? but it seems amazing that the official house has these types of errors.
thank you

 

[sandmaennle]

Thanks for the information about the steering column code. I didn't know that.

Strange issue with Battery not charging. Did you check for DTC from the generator?
It's really strange. You measure 14.5 V and the display will start flashing? That doesn't match. The generator provides all the power that's needed during driving. But if the generator has an intermittent fault, then your batteries have to provide the power you need while driving and you will get the message Battery not charging.
And you will find DTCs.

Cheers
Dirk

 

[Fuentessegura]

Thanks for the information about the steering column code. I didn't know that.

Strange issue with Battery not charging. Did you check for DTC from the generator?
It's really strange. You measure 14.5 V and the display will start flashing? That doesn't match. The generator provides all the power that's needed during driving. But if the generator has an intermittent fault, then your batteries have to provide the power you need while driving and you will get the message Battery not charging.
And you will find DTCs.

Cheers
Dirk

Apparently the positive battery connector did not make good contact and when checking the status of the auxiliary battery from SDD an error appeared for not correctly detecting the amperage.
This week the same error appeared again and I decided to change the auxiliary battery. 2 days later I got the following error on the instrument panel "battery charging failure" and when you turn off the car it stays dead and the modules are deconfigured again. When connecting SDD and reading errors I get the following error

“B1402-96 GWM”

In the recommended actions of SDD, check the wiring of the double battery control module. Apparently everything is correct, but I will disconnect the cables from the two batteries and clean the terminals in case there is something that does not allow a correct connection.
I will continue to tell you and apologize but I did not have time to continue with the tests until now.
If this doesn't work, the other option is to change the main battery.

 

[sandmaennle]

The exact decription of this DTC is:

Cheers
Dirk

 

[Fuentessegura]

The exact decription of this DTC is:

View attachment 202176

Cheers
Dirk

Contactor 1 is located under the battery, right? Is there a way to check that it works correctly? Do you think it could be a wiring problem? visually everything looks good

 

[xf_phil]

Yes, under the small battery. It should be normally be closed but I believe there is a FET in parallel with it which is used as a diode ( with the ability to measure current ) to allow current to pass from the battery to the car even when open so there is no power glitch when switching between batteries. I'm not sure if it's a large relay ( 350A ) that can be unplugged from the DBJB which would be nice for testing. I suppose if you apply voltage + ground to the correct pins you should be able to hear it click.

Has the car had water in the boot at some point?

Was it the battery terminal on the main battery with a bad connection?
( Check the negative is on properly, at both ends of the cable too. )

When you put the terminals on, they should be pushed on far enough that the post is slightly raised above the terminal clamp or at least level ( never recessed, as they won't clamp properly despite being tightened to the correct torque and will work loose )

 

[Fuentessegura]

Yes, under the small battery. It should be normally be closed but I believe there is a FET in parallel with it which is used as a diode ( with the ability to measure current ) to allow current to pass from the battery to the car even when open so there is no power glitch when switching between batteries. I'm not sure if it's a large relay ( 350A ) that can be unplugged from the DBJB which would be nice for testing. I suppose if you apply voltage + ground to the correct pins you should be able to hear it click.

Has the car had water in the boot at some point?

Was it the battery terminal on the main battery with a bad connection?
( Check the negative is on properly, at both ends of the cable too. )

When you put the terminals on, they should be pushed on far enough that the post is slightly raised above the terminal clamp or at least level ( never recessed, as they won't clamp properly despite being tightened to the correct torque and will work loose )

I have opened the auxiliary battery module and apparently everything is fine! And the internal fuses it has are all 4 good. I will continue checking wiring but apparently everything is fine. the 350A relay also seems fine on both ends.

 

[xf_phil]

Did you try erasing the fault code?
Can you see by mileage if it was set when you had a loose cable?

 

[Fuentessegura]

Did you try erasing the fault code?
Can you see by mileage if it was set when you had a loose cable?

The error occurred 2km before I got home and this is how it appeared when I connected the SDD. but all the cables were connected. Could it be that they did not configure the auxiliary battery change configuration from SDD correctly?

I have already connected everything and reconfigured the modules. With the car started the main battery shows 14.25 V, and the auxiliary battery shows 13.77V. The error has appeared intermittently. But I don't know what could be the reason. How could I configure the BMS? accessing service functions and main battery change? thank you

 

[Fuentessegura]

after configuring all the modules. I read DTC errors and no errors appear. I access service functions and "checking auxiliary battery charging system" After completing the check, the following message appears (the battery is new)

The dual battery system test has failed.

- Waiting time exceeded; low tension Recharge the batteries and run the application again. If the problem persists, check the cables that connect the battery and the alternator, and the respective fuses Special application

- You can also use the power system service mode diagnosis to diagnose the malfunction

 

[xf_phil]

The error occurred 2km before I got home and this is how it appeared when I connected the SDD. but all the cables were connected. Could it be that they did not configure the auxiliary battery change configuration from SDD correctly?

I have already connected everything and reconfigured the modules. With the car started the main battery shows 14.25 V, and the auxiliary battery shows 13.77V. The error has appeared intermittently. But I don't know what could be the reason. How could I configure the BMS? accessing service functions and main battery change? thank you

You should be able to tell if they informed the BMS system of the battery change, by viewing the live data ( datalogger in SDD ) for the GWM, there is "Vehicle Battery - Time in service - Battery 2" ( it may be named slightly different in SDD, that's what I see via Autel AP-200 ), the value is in days ( not including any days with the batteries disconnected )

If that looks reasonable, then I suggest looking at the "Vehicle Battery state of charge - Estimated - Battery 2", and "Dual Battery module charging set point" values ( do that last one with the engine running, and check it again with a volt meter so you can compare the set point with the actual voltage at the same point in time )

If the "Vehicle Battery state of charge - Estimated - Battery 2" is < 80% the I'd suspect 13.66V is on the low side, but comparison with the "set point" is probably more definitive.

I believe the battery replacement procedure gives you options for which batteries you have replaced.

after configuring all the modules. I read DTC errors and no errors appear. I access service functions and "checking auxiliary battery charging system" After completing the check, the following message appears (the battery is new)

The dual battery system test has failed.

- Waiting time exceeded; low tension Recharge the batteries and run the application again. If the problem persists, check the cables that connect the battery and the alternator, and the respective fuses Special application

- You can also use the power system service mode diagnosis to diagnose the malfunction

You are disconnecting your power supply from the car before starting it as requested for the test? ( required at any time you start the car )

Was your new battery fully charged before fitting?
Is it AGM type?

Running that other diagnostic they recommend sounds like a good idea if you can.

 

[xf_phil]

There's a description of how to run power supply service mode diagnostic in https://static.nhtsa.gov/odi/tsbs/2016/SB-10096953-1020.pdf

 

[Fuentessegura]

You should be able to tell if they informed the BMS system of the battery change, by viewing the live data ( datalogger in SDD ) for the GWM, there is "Vehicle Battery - Time in service - Battery 2" ( it may be named slightly different in SDD, that's what I see via Autel AP-200 ), the value is in days ( not including any days with the batteries disconnected )

If that looks reasonable, then I suggest looking at the "Vehicle Battery state of charge - Estimated - Battery 2", and "Dual Battery module charging set point" values ( do that last one with the engine running, and check it again with a volt meter so you can compare the set point with the actual voltage at the same point in time )

If the "Vehicle Battery state of charge - Estimated - Battery 2" is < 80% the I'd suspect 13.66V is on the low side, but comparison with the "set point" is probably more definitive.

I believe the battery replacement procedure gives you options for which batteries you have replaced.


You are disconnecting your power supply from the car before starting it as requested for the test? ( required at any time you start the car )

Was your new battery fully charged before fitting?
Is it AGM type?

Running that other diagnostic they recommend sounds like a good idea if you can.

I'm sorry it took me a while to respond. I did tests and erased all the errors. I have driven the car for 20km and no errors appear when passing the sdd. But I am worried that when I enter service functions and check the following battery options, the following errors appear.

checking the charge of the auxiliary battery: the response time has been exceeded (when starting the test with the car started, the battery indicates 13.74V and as the test progresses it reaches 15.7V and remains at that fixed value until The test time ends and I get the previous message as an error)

double battery system check: result ok

Internal check of the quiescent current control module: the test could not be passed.

What do you think could be happening? Could it be the dual battery module that is bad?

 

[Fuentessegura]

.

 

[xf_phil]

No problem, most folk have work days / bad weather etc so can't necessarily run the tests they'd like for a few days at a time.

I'm glad to hear you're not getting any fault codes in SDD now.
Assuming you're measuring that aux battery voltage with a meter ( rather than just relying on any figure displayed in SDD ) since it's varying between 13.74 and 15.7V , it sounds like the charging functionality of the dual battery module is ok. ( Though you could still compare a voltage meter reading with the "Dual Battery module charging set point" ( read from the datalogger in SDD ) with the engine running )

It would be interesting to know what "response time" SDD is referring too, but I don't suppose there is a way to find out, maybe check the session file in SDD as suggested in
https://www.jaginfo.org/posts/2996284/ ( or post it so we can have a look ), but I don't know if there will be any useful info in it or not.

From what I've read there is no quiescent current control module on facelift cars, the relay for it ( which shuts down the entertainment systems is solder inside of BCMB ), and the GWM provides the rest of the functionality.

So maybe the GWM is failing, they do seem to have a lot of issues. Also it takes the measurements of the FET in the dual battery junction box to check that contactor 1 is ok.

Perhaps the emulated eeprom in BCMB has got corrupted, you could use a BDM programmer ( xprog 5.84 or later seems to be the commonly used one, as 5.55 has problems reading the dfash ) to dump the pflash and eeprom ( if eeprom fails to dump, then you have corrupted emulated eeprom ), if eeeprom dump fails, dump the dflash, eeeprom can usually be reconstructed from dflash dump. Check out https://www.jaginfo.org/posts/2948062/ for details of where to solder etc, but do not use that virgin_eep.txt as it's for BCM, not BCMB. This could explain why you keep having to reconfigure modules whenever you disconnect the battery too. If you have to reprogram modules every time you disconnect the battery ( smart key lost messages etc ) despite waiting with key out of range before disconnecting the battery, then there's a very high likelyhood that either BCM, BCMB, or the KVM has corrupted emulation for it's emulated eeprom.

On the other hand we can't rule out the Dual battery module ( the one with the cooling fins ), as it controls the contactors in the dual battery junction box.

If you have no fault codes, and no dash warnings, and the charging voltages on both batteries match their set points, then maybe it's a bug in SDD or something only very slightly out of spec that you don't really need to worry about.

 

[Fuentessegura]

No problem, most folk have work days / bad weather etc so can't necessarily run the tests they'd like for a few days at a time.

I'm glad to hear you're not getting any fault codes in SDD now.
Assuming you're measuring that aux battery voltage with a meter ( rather than just relying on any figure displayed in SDD ) since it's varying between 13.74 and 15.7V , it sounds like the charging functionality of the dual battery module is ok. ( Though you could still compare a voltage meter reading with the "Dual Battery module charging set point" ( read from the datalogger in SDD ) with the engine running )

It would be interesting to know what "response time" SDD is referring too, but I don't suppose there is a way to find out, maybe check the session file in SDD as suggested in
https://www.jaginfo.org/posts/2996284/ ( or post it so we can have a look ), but I don't know if there will be any useful info in it or not.

From what I've read there is no quiescent current control module on facelift cars, the relay for it ( which shuts down the entertainment systems is solder inside of BCMB ), and the GWM provides the rest of the functionality.

So maybe the GWM is failing, they do seem to have a lot of issues. Also it takes the measurements of the FET in the dual battery junction box to check that contactor 1 is ok.

Perhaps the emulated eeprom in BCMB has got corrupted, you could use a BDM programmer ( xprog 5.84 or later seems to be the commonly used one, as 5.55 has problems reading the dfash ) to dump the pflash and eeprom ( if eeprom fails to dump, then you have corrupted emulated eeprom ), if eeeprom dump fails, dump the dflash, eeeprom can usually be reconstructed from dflash dump. Check out https://www.jaginfo.org/posts/2948062/ for details of where to solder etc, but do not use that virgin_eep.txt as it's for BCM, not BCMB. This could explain why you keep having to reconfigure modules whenever you disconnect the battery too. If you have to reprogram modules every time you disconnect the battery ( smart key lost messages etc ) despite waiting with key out of range before disconnecting the battery, then there's a very high likelyhood that either BCM, BCMB, or the KVM has corrupted emulation for it's emulated eeprom.

On the other hand we can't rule out the Dual battery module ( the one with the cooling fins ), as it controls the contactors in the dual battery junction box.

If you have no fault codes, and no dash warnings, and the charging voltages on both batteries match their set points, then maybe it's a bug in SDD or something only very slightly out of spec that you don't really need to worry about.

After this explanation I think the problem may come from the BCM. Months ago I disconnected the complete bcm because I saw a sulfated cable (the one for the windshield wipers) and I dismantled the board to clean the connectors.
I have to say that I have had the problem of having to program the modules if I disconnect the battery for two years, which was the first time it happened to me.

After reading the post you sent me, I think that the eeprom of my BCM is corrupted, because my windshield wipers are not working. I don't know how to flash the eeprom again and everything you told me about, is there a step-by-step tutorial on how to do it? I have never used Xprog. I have worked with soldering on plates, so I don't think the task could be complicated for me.

As for the problem that appeared to me regarding battery charging, I don't know if it could also appear due to this corruption, although I think it may be the dual battery charging module, the one with the shark fins. By the way, in my version of sdd v159, every time I read the car modules, a message appears at the top of the screen telling me that no program updates have been made and that some functions will be disabled. Is this normal? because I hit update and after 10 minutes I get a message "no updates available", but the same message continues to appear in the upper window.

thanks for everything.

 

[xf_phil]

Is it the wipers or the washer spray that doesn't work?
( usually, it's the washers that don't work due to corrupt eeeprom, but the wipers work )

What part number is your BCM? ( instructions can vary a bit depending on revision )

I have heard of folk having charging problems due to BCM, so probably best to fix that first.

I'm pretty sure I read SDD only works for a month after install without update. Also the current version is 1.64 so you might need to upgrade to the new version before you can apply other updates.

 

[Fuentessegura]

Is it the wipers or the washer spray that doesn't work?
( usually, it's the washers that don't work due to corrupt eeeprom, but the wipers work )

What part number is your BCM? ( instructions can vary a bit depending on revision )

I have heard of folk having charging problems due to BCM, so probably best to fix that first.

I'm pretty sure I read SDD only works for a month after install without update. Also the current version is 1.64 so you might need to upgrade to the new version before you can apply other updates.

Sorry, the windshield wipers do work, what doesn't work is the washer spray. My BCM number is DX23-14b476-AG.

With the message that appears on my SDD, will I be able to update the modules now if the error occurs again? or do I need to update compulsorily. I don't know how to get version 164.
Thanks again

 

[xf_phil]

Yes that's classic corrupted emulation for the eeprom in the BCM ( footwell one ) if the washers stopped working on battery disconnect ( or fully discharged battery ).

As you have a matching BCM version, I'd suggest following the instructions at https://www.jaginfo.org/posts/2948062/ but best to go with the newer xprog version (5.84 is the one there is confirmed success for, but newer probably works too, in my option it's worth avoiding 5.55 as there are no virigin dump files available for BCMB ( in the boot) if you end up needed to repair that too if it's the source of your quiescent current control issues ) as 5.55 is know to have problems reading dflash, do your best to get a dflash dump before you erase just in case. But as you've already reprogrammed it multiple times the chance of being able to reconstruct the eeprom from the dflash dump is lower, but I can give it a go if you want to post the dump file. As you're already up to speed on programming it though, you probably may as well go with the virgin_eep.txt from that thread.

A little tip, most flash programming tools require you to create a new project / file before you can read flash from the device into it.
Dumping pflash is a good way to check you have connected properly ( and a useful backup I suppose too )

I don't think you can use your current SDD install to update the modules, you'd either have to get an up to date version ( or maybe reinstall the one you have ). I think I've seen posts from Dirk @sandmaennle with a pdf explaining the install process on modern versions of windows.