Canbus and PID for the IPace

[ANBO]

BTW also found that SOC (%) val{*7E4(BECM) Battery State of Charge Minimum}/(86.2/90.2) aligns perfectly with the SOC of the car and Wattcat, where the latter two our rounding down to a full integer.

I tested your formula and for middle to high values of Soc actually it works. But I think the lower the Soc the bigger it will be the error. Basically you're multiplying Soc min by 1,04 (90.2/86.2) so for example the formula will never go to zero as Soc min will always be greater than zero.
I tried to use a linear formula for the conversion (96.6 = 100% and 2.5 = 0%) but I can't align the numbers. I'm pretty sure about
96.6% being the max for real Soc min while 2.5% it's just a guess but even playing a little bit with that I can't match the displayed Soc of my car.
Any suggestion?

Yes, I noticed the error but had not gotten to the right number yet. Also I am playing with the low number. Driving 1,600km of the grand tour of Switzerland at the moment, so have some time to get close.

This is what I am currently using:
(val{*7E4(BECM) Battery State of Charge Average}-2.72)*((3.6*108*4*58)/84.7)/1000

Yesterday I had 3,22 a the low cut off, which was a little too pessimistic. 2,72 is a little too optimistic.

Still using 84.7 a usable energy. Maybe indeed need to switch to 86.2 as well, but could not find anything official on it. Manual still says 84.7.

[dernotte]

I am sure that the displayed value must be hidden somewhere... It is "just" a matter of time to find it.

[ANBO]

Right. The formulas start deviating quite badly.

[ANBO]

For ABRP it is suggested to need:
"utc": time stamp
"soc": discussed above
"soh": avg 22491a
"speed": 22dd09
"car_model": abrp_cfg.car_model,
"lat": from phone
"lon": from phone
"alt": from phone
"ext_temp": 229924
"is_charging":
"batt_temp": avg: 224907
"voltage": 22490f
"current": 22490c
"power": same as SOC discussion

Guess power and soc we can settle on something before we find the actual PID, but any thought on "is_charging"?

[dernotte]

Lat : 754/a0a6 (byte(0-3)), signed divided by 0x20000
Lon: 754/a0a6 (byte(4-7)), signed divided by 0x20000
Soc: 7e4/4910
is_charging: negative value on 7e4/490c

[dernotte]

I have finalized the first version (V0.0.1) for the support of the Jaguar IPace on the OVMS box. I have submitted the code yesterday, so it should be available in the latest version of the firmware, by now. If you want to have access a couple of PID without programming (soc, soh, battery temp, ...)
https://www.openvehicles.com/

[ANBO]

I have finalized the first version (V0.0.1) for the support of the Jaguar IPace on the OVMS box. I have submitted the code yesterday, so it should be available in the latest version of the firmware, by now. If you want to have access a couple of PID without programming (soc, soh, battery temp, ...)
https://www.openvehicles.com/

Great. Don't have the OVMS box, so was checking for access through Torque Pro.

[ANBO]

Lat : 754/a0a6 (byte(0-3)), signed divided by 0x20000
Lon: 754/a0a6 (byte(4-7)), signed divided by 0x20000
Soc: 7e4/4910
is_charging: negative value on 7e4/490c

Unfortunately I cannot get data via Torque Pro on Lat/Lon. Checking with the programmer, but no response yet. Would indeed be good to get straight from OBD, as the reception on the phone is not always there.

Although negative on 7e4/490c is technically charging, is that what ABRP are looking for on "is_charging"?

7e4/4910 never gets to 100%, right?

[kermit68]

For ABRP it is suggested to need:
"power": same as SOC discussion

I have a linear regression from 6% to 100% and the best fit for me is:

Displayed_Soc = 1,07 * Real_Soc_Average - 2.7

[kermit68]

Unfortunately I cannot get data via Torque Pro on Lat/Lon. Checking with the programmer, but no response yet. Would indeed be good to get straight from OBD, as the reception on the phone is not always there.

Also when giving directions to ABRP pleapole always remeber to specify to which MY are applicable. Up to now I found that on MY21:
- max regen and max avaialble power are on the same PIDs as MY19/20 but with different formula
- GPS lat and long are not accessible as the whole TCU is not acessible via OBD up to now