[Ovmsdev] i-Miev/C-Zero/iOn

[Matt Beard]

The SOC was about 25%

Matt


On Tuesday, 24 September 2013, Thomas Bergo wrote:

> Was the SOC approximately 70% ?
>
> The Car takes a pause and stops charging for some time at 70%. I belive
> this is to level the charge state of the cells. After some time the
> charging will continue.
>
> Regards, Thomas
>
> tirsdag 24. september 2013 skrev Matt Beard følgende:
>
> More strange behaviour with my C-Zero.
>
> Trying to investigate charging current today I discovered that the car
> would not charge for longer than a couple of minutes with the OVMS
> connected (with Thomas' image loaded). It would start charging, then the
> current would drop to zero, but the charge light stayed on. After a while
> it stopped even trying to charge. Disconnecting the OVMS didn't fix it
> until I also turned the car on and off again (with the OVMS not connected).
> Did can noise cause problems again?
>
> Matt
>
>
> On Tuesday, September 24, 2013, Thomas Bergo wrote:
>
> The first models (2011) was delivered with a 16A cable. This was changed
> for the later models (2012 ->) to 10A cable do to firesafty.
> At home i use a 16A cable for charging, but the car only draw 13A.
>
> I'm not sure what is the correct info, EVSE limit or the charger limit.
> Any way the car will only draw 13A.
>
> The can message for current limit set by EVSE is not know for the i-Miev,
> so until this information is available we need to hardcode a value to be
> displayed in "STANDARD xxA" in the app.
>
> Regards, Thomas
>
>
> 2013/9/24 Håkon Markussen <hakon.markussen at gmail.com>
>
> Nice work Thomas,
>
> Your attached image reminds me that I should implement the car_time and
> car_parktime in the Think City module :-)
>
>
> Regards to max charge rate "STANDARD xxA":
> The variable car_chargelimit should contain the maximum available mains
> current, which is set by the EVSE.
> This is done in vehicle_thinkcity.c and I assume this can-message is
> available in a iMiEV and could replace the hardcoded "13A".
>
> The evse sends a pilot signal controlling the charger max rate, which can
> be adjusted by the user in steps depending on the evse type.
> The first evse's for iMiEV was delivered with two charging steps (maybe
> 10-16A) and got popular among Leaf-owners. Running up to 16A over the
> Schuko-connector is bad firesafety, so the later evse's were replaced with
> 13A. (I guess) limit max.
> This one is a nice one(mode 2, type 2 delivered with different charging
> connectors:
> http://salto.no/produkter/ladekabel-justerbar-13-a-type-2-shuko/
>
>
> When the max charge current is set by the evse, e.g. 13A the ac-charge
> current (which can be measured or viewed in a can-message) will never
> exceed this limit.
>
> Br.
>  Håkon
>
>
> 2013/9/24 Thomas Bergo <thomas.bergo at gmail.com>
>
> I don't remember to have seen any documentation. There is a common
> understanding in Norway that the car only can drain 13A.
> I have also measured hove much current the car use when charging.
>
> This setting is only for information in the app, as no information is send
> to the car from the car module. There is no way that the car module can
> impact on the charge current. The voltage and current (13A) is reported by
> the car and not limited by the OVMS.
>
>
> [image: Innebygd bilde 1]
>
> Regards, Thomas
>
>
> 2013/9/24 Matt Beard OVMS <smvo at mxf.org.uk>
>
> Do you have a source for this 13A maximum claim?  Mitsubishi claim that
> the on-board charger in the iMiev runs at 240V 15A in the USA.
>
> If you want to use the output rating of the charger you need to reduce the
> figure to 9A as the output is 330V.
>
> What does the Roadster version set - does it use the input current, or
> some version of the output current?
>
> I notice that the Volt/Ampera code sets 16A as the charge limit.
>
> Matt
>
>
>
> On 24 September 2013 19:58, Thomas Bergo <thomas.bergo at gmail.com> wrote:
>
> The charger is only
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20130924/03f78ad2/attachment.htm>