skoot 0 Posted July 5, 2020 Share Posted July 5, 2020 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 Quote Link to post Share on other sites
Katya-ABRP 56 Posted November 2, 2020 Share Posted November 2, 2020 Hi @skoot, Sorry about the much delayed response! We simply haven't been aware that LeafSpy would be a possible connection for the e-NV200, we'll have it added as soon as possible 😉 /Katya Quote Link to post Share on other sites
Jason-ABRP 180 Posted November 2, 2020 Share Posted November 2, 2020 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! Quote Link to post Share on other sites
electric_camper 0 Posted November 10, 2020 Share Posted November 10, 2020 Hi, my odb-dongle connects with LeafSpy and ABRP. But the SOC stays allways at 100%. All other data is synced every 5 seconds. What can I do? I am not yet using the premium version, but i will when this works. The SOC value in LeafSpy is correct. Quote Link to post Share on other sites
Jason-ABRP 180 Posted November 10, 2020 Share Posted November 10, 2020 Ah, I missed a spot where the Leaf was called out specifically, so SoC calculation was skipped if you had a non-Leaf. I've pushed a fix, so you should see the correct values now. Quote Link to post Share on other sites
electric_camper 0 Posted November 11, 2020 Share Posted November 11, 2020 Hi, yes, i see a value now!  To be exact: i see two values. Its jumping from 32% to 23% (back and forth). LeafSpy is showing 38%. The graph while driving showed a zic-zac. Quote Link to post Share on other sites
electric_camper 0 Posted November 13, 2020 Share Posted November 13, 2020 Quote Link to post Share on other sites
electric_camper 0 Posted November 16, 2020 Share Posted November 16, 2020 I dont know if the following information helps to solve the problem: - my car is also an e-vn200 (40kwh) - the gids in leafspy are also showing two values, changing every 2-3 seconds - the first of the two SOC-values in ABRP matches the SOC shown in the car Is there anything i can do? Quote Link to post Share on other sites
electric_camper 0 Posted December 1, 2020 Share Posted December 1, 2020 Should i try another OBD? Currently its a Lelink 2 BLE OBD-II... some kind of input would be wonderful   Quote Link to post Share on other sites
BarryH 29 Posted December 1, 2020 Share Posted December 1, 2020 Do you see the jumping up/down in leafspy as well? Or does Leafspy give a stable value (that of course slowly drops)? Quote Link to post Share on other sites
electric_camper 0 Posted December 1, 2020 Share Posted December 1, 2020 Yes, in LeafSpy also. Quote Link to post Share on other sites
BarryH 29 Posted December 2, 2020 Share Posted December 2, 2020 @electric_camperIn that case it does make sense to try another dongle. ABRP gets the data from Leafspy. So let's first make sure Leafspy gives a stable and plausible result and then look at the result in ABRP. Â Quote Link to post Share on other sites
electric_camper 0 Posted January 16 Share Posted January 16 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? Quote Link to post Share on other sites
Snowy Owl 0 Posted February 3 Share Posted February 3 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.  Quote Link to post Share on other sites
Jason-ABRP 180 Posted February 3 Share Posted February 3 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. Quote Link to post Share on other sites
Snowy Owl 0 Posted February 7 Share Posted February 7 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. Quote Link to post Share on other sites
electric_camper 0 Posted April 8 Share Posted April 8 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? Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.