[dernotte]

You can use the terminal since the value can't be displayed in a standard widget like gauge, and it is probably not defined as a buildin metric either

 

[hughmama]

You can use the terminal since the value can't be displayed in a standard widget like gauge, and it is probably not defined as a buildin metric either

Excellent. I did try via the terminal but I might have to ask you to tell me exactly how to do that please. Do I need to enter
ATSH 7E4
1003
And the key etc then what is the call for the PID please? I tried both the PID by itself and 31014A7C
Sorry I did try to find this info online but couldn't immediately find it

 

[dernotte]

just "ATSH 7E4" to talk to 7E4, then "224A7C" and "224A7D" to read the 4A7C and 4A7D PID

 

[hughmama]

just "ATSH 7E4" to talk to 7E4, then "224A7C" and "224A7D" to read the 4A7C and 4A7D PID

This is what I got. No sign of the array of values unfortunately

 

[dernotte]

Probably a limitation of your OBD2 dongle. What version of ELM is it ?

 

[hughmama]

Probably a limitation of your OBD2 dongle. What version of ELM is it ?

Bafx OBD2 with elm327

 

[dernotte]

Is there any way you can find if it is a ELM327 V1.5, V2.1, V2.2 ... ?

 

[hughmama]

Is there any way you can find if it is a ELM327 V1.5, V2.1, V2.2 ... ?

Can't find it but it's from 2019 so maybe it's an older version. What adapter do you use? Happy to upgrade.

 

[dernotte]

Here is the one I have: https://www.ipaceforums.co.uk/threa...-app-now-shows-up-in-infotainment-android-auto.9244/?post_id=121090#post-121090

I know old versions have internal memory limitations and can’t handle large amount of data in a single response. The one I have can.

 

[dernotte]

here is what I can get with a V2.2 firmware version of the ELM327:

 

[hughmama]

A new OBD2 device and I get this:

 

[Maxwell_400]

On android there is an app called "ELM327 Identifier" that shows what your adapter supports, this is from my OBDLink LX:

 

[dernotte]

@hughmama , with those values, it shows that you don't have any problematic modules (or sub modules) when we look at the deviation at rest. They are all at 0. For the other deviation they show:

(10 12 11) (13 12 0E) (14 0F 12) (13 13 13) (10 11 0F) (14 10 0E)
(0F 13 11) (13 0F 0F) (0F 12 11) (14 17 11) (12 12 0F) (16 14 11)
(0F 10 10) (0E 10 13) (12 13 12) (10 11 10) (12 12 10) (11 0F 0E)
(0E 10 11) (11 11 10) (17 13 14) (12 0E OF) (13 0F 13) (0E 0E 0D)
(12 0F 11) (0E 0F 16) (0F 10 10) (13 11 13) (14 13 10) (10 11 11)
(0F 11 11) (10 13 11) (13 0F 10) (12 12 14) (13 13 13) (14 16 13)

Those values seems very good as well. The highest value is "16".

 

[hughmama]

@hughmama , with those values, it shows that you don't have any problematic modules (or sub modules) when we look at the deviation at rest. They are all at 0. For the other deviation they show:

(10 12 11) (13 12 0E) (14 0F 12) (13 13 13) (10 11 0F) (14 10 0E)
(0F 13 11) (13 0F 0F) (0F 12 11) (14 17 11) (12 12 0F) (16 14 11)
(0F 10 10) (0E 10 13) (12 13 12) (10 11 10) (12 12 10) (11 0F 0E)
(0E 10 11) (11 11 10) (17 13 14) (12 0E OF) (13 0F 13) (0E 0E 0D)
(12 0F 11) (0E 0F 16) (0F 10 10) (13 11 13) (14 13 10) (10 11 11)
(0F 11 11) (10 13 11) (13 0F 10) (12 12 14) (13 13 13) (14 16 13)

Those values seems very good as well. The highest value is "16".

Thanks so much for this. I ran another check at a lower SOC and got the same numbers. Very positive.

When I took the car to the dealer to explore the replacement of the faulty module this is what they noted in the report:

HV battery Module 29 fault- fault code logged and deviation noticed on 40 D2 application. Initially need to charge battery to 100% and rerun application to confirm no other modules are faulty. Price up for Module 29 replacement.

I though I might be able to make out what they meant by the deviation comment from this but alas. Maybe 40 D2 application just refers to the command and is not referring to specific cells.

 

[looney]

I wonder if anyone has an idea what these numbers mean and what is 'good' and what should be considered 'bad'?

For example, I get numbers - all converted to decimal - in the 0 ... 39 range for 224a7c, and 16 ... 34 for 224a7d. The 'hot spots' do not occur on the same cells for both measurements. This is with an indicated SoC of 94% after charging to 100% including cell balancing two days ago and driving home, at a battery temperature of 13°C.

I also wonder how the module voltage is measured / calculated. It is never the sum of the single cells as I would naively expect. Suggestions?
As I don't have an Autel scanner I cannot directly compare.

On the bright side, all these measurements work on my MY21 without any alterations. Thanks for the hard work to get there!

 

[dernotte]

I though I might be able to make out what they meant by the deviation comment from this but alas. Maybe 40 D2 application just refers to the command and is not referring to specific cells.

Yes, 40D2 is the ID of the CAN routine on the BECM module. That routine is a protected routine that allows you to get the SOH, voltage and temperature per module. The two type of deviation are stored in PID 4A7C and 4A7D, not from the routine 40D2. Maybe the routine forces the update of the deviation on 4A7C and 4A7D, but you don't get any deviation out of the CAN routine.

 

[dernotte]

I wonder if anyone has an idea what these numbers mean and what is 'good' and what should be considered 'bad'?

I don't know what is the theshold between good and bad value, but as you can see here

https://www.ipaceforums.co.uk/threads/how-to-find-defective-module-by-torque-pro.7926/page-5?post_id=126576#post-126576

I agregate those values from my car since last Aug. The only bad cell I have is cell #8 with a value of 180. All other values are ok.

 

[Ayepace]

New Autel update includes TCU functions.

 

[dernotte]

I will give a try tonight, but from this changelog, does not seems to include a lot of changes for the Ipace 2019...

 

[Ayepace]

2019 I-pace got some parts that didn't get into other JLR products until 2020s. Due to same TCU part numbers for for both, this may apply to both. However, there are several TCUs used based on vehicle market too.