✅ Nissan Leaf

[vvdt]

Also another set of screenshots while charging L2.

Screenshot	Screenshot
IMG_5824.png (554.59 KiB) Viewed 1222 times	IMG_5823.png (569.51 KiB) Viewed 1222 times
IMG_5825.png (222.95 KiB) Viewed 1222 times	IMG_5827.png (226.73 KiB) Viewed 1222 times
IMG_5828.png (726.02 KiB) Viewed 1222 times

[jeff]

Also another set of screenshots while charging L2.

Screenshot	Screenshot
IMG_5824.png	IMG_5823.png
IMG_5825.png	IMG_5827.png
IMG_5828.png

Thank you @vvdt! Can you confirm that the power parameter is being displayed correctly in v1.18?

[jeff]

• Rear heater state kept loading

It looks like your car is responding with undocumented data. I've captured the current state of understanding that parameter here: https://github.com/ElectricSidecar/Niss ... /issues/14

• Eco mode kept loading
• E-pedal mode kept loading

I've added a decoding for the "pedal off" and "eco off" states in SHA: 8b2dcab.

• Charging power showed unsupported power

This should be fixed in v1.18.

What didn’t work or kept loading

• Estimated range was much lower than on the dash, 61 km in the UI while 108 km on the dash
• model year off by 1 year
• High voltage battery health slightly off compared to leafspy as mentioned above

These ones are still open.

[jeff]

@vvdt for the estimated range, I've filed https://github.com/ElectricSidecar/Niss ... /issues/16 to track the PID we're using. I suspect it might be the wrong one but we'll need to get more values mapped to readouts on the dash to try to understand what's going on.

To test the range pid, we'll need to get the raw value of that PID paired with readouts from your dashboard and try to correlate the values together to determine the scaling function. The testing flow for this is:

1. Connect your scanner.
2. Open the range parameter.
3. Take a screenshot of the data readout (or copy the hex value of the data readout by long-tapping). Take note of the range value on your dash when you do so.
4. Share the screenshot + the readout here.

We'll have to do this with a variety of different range values in order to pinpoint the scaling function.

[jeff]

I've fixed the VIN decoder to decode your VIN as a 2019 instead of a 2018. This will land in the next release of Sidecar.

[vvdt]

@jeff allright cool. I’ll do more testing soon I’ll get back to you.

Edit, sent you a new log export of scanning sessions from my trip yesterday running v1.19.0 build 217

[jeff]

@vvdt thank you! In order to tune the range parameter though we'll need two pieces of information:

1. The current range reported by your vehicle.
2. The exact Range parameter data value responded by your vehicle at the same time.

In this case the OBD logs aren't as needed because the logs don't make it easy to correlate parameter data values with the values you're seeing on your dashboard.

If we can get at least 3 pairs of the above information at very different range values, we should hopefully be able to tune the range parameter a bit more.

[vvdt]

I did some more testing today, specifically the range you mentioned.

Screenshot	Screenshot	Screenshot
IMG_6006.png (142.85 KiB) Viewed 280 times	IMG_6004.png (142.2 KiB) Viewed 280 times	IMG_6003.png (126.47 KiB) Viewed 280 times
IMG_6002.png (97.47 KiB) Viewed 280 times	IMG_6001.png (136.11 KiB) Viewed 280 times	IMG_5999.png (395.6 KiB) Viewed 280 times

[vvdt]

Ah I see now you can also tap on range remaining as well to see more details. Let me take some more screenshots tomorrow and pictures of the dash as well for reference.

We are going on a weekend trip tomorrow so I bet I might be able to do this for multiple ranges remaining.

[jeff]

oh I just noticed, does your range alternate between showing 0 and a non-zero value?