Jump to content
skoot

Nissan e-NV200 mit Leaf Spy

Recommended Posts

Hello,

I have a Nissan e-NV200 which works with Leaf Spy. But in ABRP I can't link it with Leaf Spy. I thing it should be work and it only needs to be unlocked in ABRP software.

Best regards
Klaus

Link to comment
Share on other sites

Thankfully an easy switch to make on our side! I've updated the e-NV200  to make it supported directly by LeafSpy, and I've also added a generic LeafSpy destination URL, relying on your selection on your Car Selection on the ABRP app.  This way it'll be easier in the future to add support!

Link to comment
Share on other sites

Can't get ABRP lifedata working with Nissan e-NV200 either...

Car: Nissan e-NV200, 24kWh, 2015

LeafSpy works fine. Updates SoC to match with the car own display.

ABRP running at the same Android tablet than LeafSpy. ABRP acting like there was no lifedata available. Went through all Nissa Leaf an e-NV200 car selections at ABRP. Same effect, ABRP cant find lifedata no matter which Nissan Leaf or e-NV200 model is selected in the car selection.   

Link to comment
Share on other sites

This is very likely due to an internal calibration we run on the LeafSpy data, since the SoC for the Leaf in the car's dash didn't match the SoC reported by LeafSpy we had users calibrate the min/max GIDs, and then compute the SoC from that.  If desired, I can change that behavior for the e-NV200, though.

Link to comment
Share on other sites

In my observation the LeafSpy reported SoC has always been within couple of percents the same than e-NV200 reported. However, I assume that this isn't always the case and the same peculiar relation between GIDs and SoC applies to e-NV200 than Leaf.

How about reading both (SoC and GIDs) to ABRP and using the one that gives more logical value, i.e. non-zero or non-inf.  Naturally there's a difficult decision in ABRP to make when both (LeafSpy SoC and GIDs based) values are logical, but different.

Link to comment
Share on other sites

Dear developers, i tried now leaf spy pro android version instead of ios. same behavior. i tried 3 different types of obd dongles.

2 smartphones, three dongles and 2 leafspy pro-versions later... i ask myself, is there anything i can try to make this work?

why do i see two soc and gid values in leafspy? can someone share his leafspy settings?

Link to comment
Share on other sites

Posted (edited)
On 4/8/2021 at 3:20 PM, electric_camper said:

Dear developers, i tried now leaf spy pro android version instead of ios. same behavior. i tried 3 different types of obd dongles.

2 smartphones, three dongles and 2 leafspy pro-versions later... i ask myself, is there anything i can try to make this work?

why do i see two soc and gid values in leafspy? can someone share his leafspy settings?

Hello,

I have the same problem: 2 different displays.
What is the solution? How did you do it?

Greetings from Alex from Germany

Edited by Alexissimo
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×
×
  • Create New...