Regeneration is based on SOC increasing not on pack amps. Pack amps is read too infrequently to be used to determine the energy generated during regeneration (at best once every few seconds) and has a granularity of half an amp. It is the Leaf BMS unit that adjusts the SOC during driving and regen.patrickst wrote:Hey guys,
I have a problem I couldn't find anything about in the forum. I am doing research as a student with Leaf Spy Pro and have problems with understanding my data. I want to estimate the consumption of runs by the difference of GIDs left in the battery. I did some test runs and the consumption differs extremely (by the factor of 2.5) with trying to hold all nuisance factors constant (same route, driver, time etc.) I figured out that in the runs with an extremely high consumption the app is not recording the regeneration. The value is constant for about 20 minutes while driving, than starts recording again. Everything else is recording. Also the pack amps show me that there is regeneration from breaking.
The other runs are very constant and the variation quite low.
My question is, do you know what the problem could be? Possibly the device in the car? And why is the consumption so extremely high when not reading the regeneration?
Nexus 7 tablet
OBDII adapter via bluetooth in the vehicle
Leaf Spy Pro version 0.34.51
Thanks for an answer
There is no way for the app to show just Regen. All the app can do is report changes in SOC which at times are due to regen as you seem to be seeing. If the battery is changing temperature this could mask any Regen. Try plotting battery temperature and see what it shows. I assume you are not using climate control as that would also change the SOC and most likely prevent any regen from being recorded as SOC might always be decreasing.patrickst wrote:Thanks for the quick response.
My data is based on approx. 5 km long and very hilly runs on the same route. When I plot the excel file of Gids and regen over time, there should be a change in the value of regeneration. I don't mean at the same time, I mean the cumulated value and at the end of a run.
In some runs I record regen and the values fit quite well to the topography, and in some there is no change in regen over the whole time at all. The route stays the same. When the regen is recorded, the data is good enough for me and in each run very precise. But in the runs when regen is not recorded, constant value over time, the GIDs difference from start to end of the run increases enormously.
I do not know why regen in some of the runs is not changing at all. I hope I could explain my problem more precise.