Jaguar I-Pace Forum banner

Canbus and PID for the IPace

73K views 421 replies 24 participants last post by  Maxwell_400 
#1 ·
Since there is barely no information on the PID and ECU ID on the web for the Jaguar IPace CANbus, I have started some investigation.
I have found a little more than 30 ECU ID, and between 10 to 250 PID per ECU.
I will disclose my finding here : https://www.openvehicles.com/node/2423 since I have using the OVMS device for this.
The ECU ID and PID are available here : <GOOGLESHEETS gid="1830471105" id="1wNMtpPqMAejNeOZGsPCcgau8HODROzceFcUSfk2lVz8">https://docs.google.com/spreadsheets/d/1wNMtpPqMAejNeOZGsPCcgau8HODROzceFcUSfk2lVz8/edit#gid=1830471105</GOOGLESHEETS>
For the moment, I am in the investigation mode, I am scanning extensively the CANbus and collecting all data I can find on the bus.
I have not put any Label to the PID, except the odometer, because it was an obvious one . I found that the VIN is replicated almost in any ECU, and the PID in the Fxxx range contain a lot of Jaguar part number. I hope that will help identifying what the ECU is about.
Anyone who want to help on this is welcome.
 
#356 ·
ANBO said:
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?
 
#357 ·
Yesterday I grabed some data and I'm now testing the following formula:

Displayed_Soc = (Real_Soc_Average * 1.08) - 3.2

It goes to zero when Real Soc avg is equal to 2.6 and is equal to 100 with real soc avg is 96 (more or less). It maybe not perfect but it should be a good aproximation I think.
 
#359 ·
kermit68 said:
Maxwell_400 said:
Available power to the wheels drop rapidly when SOC falls below 20%. Make sure you are charged when you want to show off.

Figure_power.png
But maximum power shouldn't be 295 kw ? I see in the graph that it goes well above ...
This is what the battery can deliver, the motors are restricted to 147kW each. We can only hope for an SVR version which can unlock more power, the motors are rated for 195kW (355Volts x 550 Amps) each in 10 sec bursts.
 
#361 ·
kermit68 said:
ANBO said:
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.
 
#364 ·
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"?
 
#366 ·
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/
 
#367 ·
dernotte said:
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.
 
#368 ·
dernotte said:
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?
 
#370 ·
ANBO said:
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
 
#372 ·
There is a great chat in FB (Jaguar IPace discussion group) from someone at Jaguar Land Rover's global product marketing & planning team. His area of speciality is HMI (human machine interface) plus our Infotainment & Sound Systems.
He mentioned that SOTA update can not happen if the car is plugged in to charge, or if there is something plugged in the OBD2 port....
 
#373 ·
dernotte said:
There is a great chat in FB (Jaguar IPace discussion group) from someone at Jaguar Land Rover's global product marketing & planning team. My area of speciality is HMI (human machine interface) plus our Infotainment & Sound Systems.
He mentioned that SOTA update can not happen if the car is plugged in to charge, or if there is something plugged in the OBD2 port....
Considering the frequency and the effectiveness of JLR Sota I would say it's not a big problem ;).
We are waiting for big improvement in charging curve, still bugs in Touch Duo Pro and the situation with PiviPro is even worse. We are lucky if we get 3 updates/year so no big deal to unplug the Obd reader for 3 days / year. IMHO of course.
 
#374 ·
I am curious about your thoughts on this:
I own the German spec EV320. It has same torque, same motors and same battery but less horsepower.
I wonder if the EV400 and Ev320 only have different parameters regarding the driving pedal. I kinda doubt they made a completely new software.

Can we check the power on the wheels compared to % gas pedal?
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top