Imiev measured data

Post by **offgridQLD** » Thu, 10 Jul 2014, 03:06

Yesterday I made my 104km trip to the hinterland but I carried a lot of things on the roof racks (A big bundle of 4m long electrical conduit longer than the car

. It was about 4C outside when I made the trip at night with lights on and heated seat on. So it was my worst consumption ever. I arrived at my place in the hills with 12% SOC.

I recorded my consumption from the wall to recharge the battery from 12% SOC back to 100% 15.27kwh + 12% = 17.10kwh.

I then today I took a trip down the range to the beach and back again. 90km distance total with a mix of 100kph,80,70. I wasn't driving for economy. I even had a bit of fun zipping up the hills. I had 5 bars remaining when I got home

This trip the battery felt strong like it got a good charge this time.

I think the temperature when you charge your car plays a big part in how many kwh it can accept before stopping 100%. For example if you charge late at night until early morning when it could be 8-3C outside vs charging in the day time when its 20 - 25C.

Kurt

Kurt

Post by **Malm** » Thu, 10 Jul 2014, 04:38

Can you tell us how where the cells at 12% SoC. What was the difference between the lowest and the highest?

Post by **offgridQLD** » Thu, 10 Jul 2014, 04:49

I didn't log the trip but I viewed with Canion when I arived . At 12% SOC with 1kw load on the battery (car was in drive and trying to move forward) 3.675v high and 3.645 low 30mv differance.

Kurt

Post by **Malm** » Thu, 10 Jul 2014, 08:47

So, it could go to 0,0% SoC. And can charge more then 17 kWh. In excellent shape, has the same autonomy as new, I think.

Find the best way to keep the temperatures under 31 ºC, and it will continue many months like that.

Post by **g4qber** » Fri, 11 Jul 2014, 02:44

one thing that could be an issue with the OBDlink MX is its finding an interference free bluetooth channel.
today the Nexux 7 tablet kept going to 0 shortly after connecting at 400fps.
I re-paired the tablet and now it is more stable for now.

the batman dongle doesn't seem to have this issue.
perhaps it uses safe channels.
it doesn't even need a pairing button.

feels like the OBDLink is PC and batman is Mac.

ie. "fiddle around" vs "just works"

Post by **me68** » Fri, 11 Jul 2014, 20:35

g4qber wrote: one thing that could be an issue with the OBDlink MX is its finding an interference free bluetooth channel.
today the Nexux 7 tablet kept going to 0 shortly after connecting at 400fps.
I re-paired the tablet and now it is more stable for now.

the batman dongle doesn't seem to have this issue.
perhaps it uses safe channels.
it doesn't even need a pairing button.

feels like the OBDLink is PC and batman is Mac.

ie. "fiddle around" vs "just works"

Hello!

I do not agree. I also use a OBDlink MX with a Nexus 7 (2012) with latest android version, i use bluetooth also with my mobile & radio at the same time, but i do not have any communication errors/problems.

Measured more then 28.200km and 583hours operation with canion.

Martin

Post by **offgridQLD** » Tue, 15 Jul 2014, 01:15

2013 nexus 7 and obdlink mx I have about a 50/50 dropout rate. My typical logged trip is 1.5hrs long. It's common for it to drop out and loose the connection after 1hr driving...frustrating to look over after 80% of your logged trip to find it has stopped logging

last weekend it logged fine all the way up 1.5hrs but the next day it lost sink after 50 min on the way home.

The app is starting to get more polished with some nice features but I shy away from using it to log trips as it always drops out.

Perhaps everyone who has the same issue can start sending the error log to the developer as your usually asked you if you want to.

Kurt

Post by **offgridQLD** » Tue, 15 Jul 2014, 01:31

Regarding measuring kwh from the wall to 100% SOC mine inst consistent.

After Last weeks trip 105km
starting at 12% SOC back to 100% 15.27kwh + 12% = 17.10kwh.

This week
stating at 16.5% SOC consumed 14.3kwh back to 100% + 16.5% = 16.65kwh

Kurt

Post by **Malm** » Tue, 15 Jul 2014, 01:37

The same with me.

Sometimes I get the value of 16, other times 15,5 kWh. Temperatures could be responsible, or an inaccurate calculation of the SoC. I should take the value of the total voltage in the beginning, because that number will be correct. Two equal SoCs will be correct if the total voltage is the same for each other.

Post by **offgridQLD** » Tue, 15 Jul 2014, 02:25

yes I have voltage

12% started out at 322v

16.5% started out at 327v

Kurt

Post by **g4qber** » Tue, 15 Jul 2014, 06:34

Kurt are you able to spare another $AUD150 to get this dongle?

http://ahdesign.us/blog/stn1170-bluetoo ... i-adapter/

it might solve your problems.

Post by **Malm** » Tue, 15 Jul 2014, 08:56

offgridQLD wrote: yes I have voltage

12% started out at 322v

16.5% started out at 327v

Kurt

The voltages that we should expect. So, the only explanation that I see is the temperature. Let me say it again, your i-MiEV is very healthy. You charge at L2 16 A?

And if you charge at 16 A, can you tell me how much, as seen by canion, is the Wh reg when you charge a 5% bar. ANd can you tel me how much time it takes to get that 5%. My time is around 14 min. and charge around 550 wh.

Post by **offgridQLD** » Tue, 15 Jul 2014, 12:47

No Australian chargers for 2012 imiev are 2200w just under 10A at 240v.

g4qber,
I just don't want to take a gamble of $150 for a chance that it will fix the issue. Considering others say the mx is working perfect for them. It's a expensive chunk of plastic if it doesn't fix it. Though perhaps some one can do a comparison between the two who owns both or could borrow one and prove the mx is the culprit?

Kurt

Post by **Malm** » Tue, 15 Jul 2014, 13:36

Ok, but how much will be the kWh reg as seen by canion to fill a 5% bar charging at 10A?

Post by **g4qber** » Tue, 15 Jul 2014, 15:09

Hi kurt
I have used my own mx, acmotor's mx and batman dongles.

Both my mx and acmotor's mx had dropoff issues if BT Audio was on.
This is with nexus 7 gen 1 tablet.

Hmmm that reminds me. I should probably do a latest mx test with other BT devices turned off

Somehow martin has been lucky with his equipment

Martin which imiev do you have or is it a ion or c-zero?
Perhaps this could be the diffence. I hadn't thought of this until now.

I have 2011 imiev

Post by **offgridQLD** » Tue, 15 Jul 2014, 15:51

Malm,
I have your data for you.

I charged the car from 54% soc (8 BAR) UP TO 59% soc (9 BARS) This one 5% bar increase Took 622whr on canion regeneration and 22min 44 seconds. pack temperature started at 18c average and was just over 19c average at the end.

5% = 622whr x 20 = 100% so 100% = 12.44 kwh

Kurt

Post by **me68** » Tue, 15 Jul 2014, 21:26

g4qber wrote: Hi kurt
I have used my own mx, acmotor's mx and batman dongles.

Both my mx and acmotor's mx had dropoff issues if BT Audio was on.
This is with nexus 7 gen 1 tablet.

Hmmm that reminds me. I should probably do a latest mx test with other BT devices turned off

Somehow martin has been lucky with his equipment

Martin which imiev do you have or is it a ion or c-zero?
Perhaps this could be the diffence. I hadn't thought of this until now.

I have 2011 imiev

Hello!

We have a C-Zero with original radio connected to some Windows phones.

Somebody said that WLAN/WIFI=on could be an issue. On travelling you pass a lot of WLAN/WIFI-hotspots. The device have to handle some communication tasks therefore. This guy said turning off wlan on his android device, solved the BT drop outs with the dongle.

Martin

Post by **offgridQLD** » Tue, 15 Jul 2014, 21:35

Wifi off makes no difference.

Kurt

Post by **Malm** » Wed, 16 Jul 2014, 00:06

offgridQLD wrote: Malm,
I have your data for you.

I charged the car from 54% soc (8 BAR) UP TO 59% soc (9 BARS) This one 5% bar increase Took 622whr on canion regeneration and 22min 44 seconds. pack temperature started at 18c average and was just over 19c average at the end.

5% = 622whr x 20 = 100% so 100% = 12.44 kwh

Thank you.

Mine 5% = 550 whr x 20 100% = 11,00 kWh

Lets assume that at 10 A it would be 11,2 kWh

11,2/12,44 = 10% difference.

I believe your car do it like a new one. So my car as 10% less capacity then yours. Your car do the same miles as a new one, mine less 10%.

(yours have some degradation, but the car don't use that extra energy that it had at new, so it will do the same distance as it was new)

This is only valid when we know that both cars go to 0,0% SoC

Finally, thanks to you, Offgrid, I know how my i-MiEV behaves in relation with a new one. It acts like it has less 10% capacity.

Post by **offgridQLD** » Wed, 16 Jul 2014, 00:39

Perhaps we can get a few others to do the same test.

You need to start a few % say 52 - 53% soc. That way when the bar appears you are going to log at... 54% SOC you can reset cannon and get ready to note the whrs (take screen shot/photo) when it reaches 59% SOC.

AC motor?

I want to try it a few times to see how the consistency is.

Kurt

Post by **Malm** » Wed, 16 Jul 2014, 01:32

So, we now have our test.

The test is "how much do your i-MiEV wh reg, as seen by canion, from 54% to 59%, at 10A? and takes how many time to do that?

But we will only can compare i-MiEVs that go to 0,0% SoC without losing bars stopped.

First results:

OffgridQLC i-MiEV - 622 Wh

Malm i-MiEV - (approximately) 560 Wh

Post by **offgridQLD** » Wed, 16 Jul 2014, 01:37

54 -59%

First I need to see consistency by repeating it a few times.

Kurt

Post by **Malm** » Wed, 16 Jul 2014, 01:50

I think it will be always the same.

Post by **offgridQLD** » Wed, 16 Jul 2014, 15:43

I did read a reasonably in depth transport research report on EV's that had the Imiev listed as 16kwh battery (13kwh usable) (Page 19)

http://www.transport-research.info/Uplo ... _Tests.pdf

If this is accurate info then I have lost some capacity around 4%

Kurt

Post by **Malm** » Thu, 17 Jul 2014, 04:14

I doubt that it is correct. Only 13 kWh usable????????.