Jump to content

Nissan e-NV200 mit Leaf Spy


Recommended Posts

  • 3 months later...

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 post
Share on other sites
  • 2 weeks later...
  • 1 month later...

I tried now 4 OBD Dongles.... but no change. Is there anyone with a working combination of  E-NV200 using Livedata with Leafspy and ABRP? 

Is there any alternative getting live-data into ABRP?

Why cant ABRP read OBD-Data directly from the dongle without using LeafSpy?

Link to post
Share on other sites
  • 3 weeks later...

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 post
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 post
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 post
Share on other sites
  • 2 months later...

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 post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...