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

Thomas Bergo thomas.bergo at gmail.com
Wed Sep 25 05:43:29 HKT 2013 

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 able to deliver 3 KW to the battery, so the car
>>>> will maximum use 13A from the grid. I therefor hardcoded the charging  to
>>>> "STANDARD 13A"
>>>>
>>>> Regards, Thomas
>>>>
>>>>
>>>> 2013/9/24 Matt Beard OVMS <smvo at mxf.org.uk>
>>>>
>>>>> I think my hardware may have a dodgy connection as it is working again!
>>>>>
>>>>> I am using the hex file Thomas sent (one that failed yesterday!)
>>>>>
>>>>> I noticed that the charge level is reported wrongly. I am using a 16A
>>>>> charger (and the car does charge at > 13A) yet the C-Zero code is reporting
>>>>> the charge type as "STANDARD 13A" and the charge current is showing as 12A.
>>>>>
>>>>> Matt
>>>>>
>>>>>
>>>>>
>>>>> On 24 September 2013 19:22, Thomas Bergo <thomas.bergo at gmail.com>wrote:
>>>>>
>>>>>> I read some rumors that some cars imported from Denmark to Norway had
>>>>>> a smaller battery pack.
>>>>>> Have to look some more to find where i read about this.
>>>>>>
>>>>>> Regards, Thomas
>>>>>>
>>>>>>
>>>>>> 2013/9/24 Matt Beard <matt at beard.tv>
>>>>>>
>>>>>>>  You can tell how many cells from the 6en messages, but I heard that
>>>>>>> the range is the same, but the unused capacity is less so the batteries
>>>>>>> don't last as well.
>>>>>>>
>>>>>>> This needs to be confirmed.
>>>>>>>
>>>>>>> Matt
>>>>>>>
>>>>>>>
>>>>>>> On Tuesday, September 24, 2013, Thomas Bergo wrote:
>>>>>>>
>>>>>>>> There is delivered some Citroen C-Zero with a smaller battery pack
>>>>>>>> (13 KWh VS 16 KWh.) The ideal range for the 13 KWh battery I believe is 80
>>>>>>>> miles and for the 16 KWh battery the ideal range is 150km (93 miles).
>>>>>>>>
>>>>>>>> To calculate the ideal range correctly for both battery size we
>>>>>>>> need a way to distinguish between them.
>>>>>>>>
>>>>>>>> Do you think that there will be any issues by using the Feature 14,
>>>>>>>> Car bits, to indicate which battery pack the car has?
>>>>>>>>
>>>>>>>> Regards, Thomas
>>>>>>>>
>>>>>>>>
>>>>>>>> 2013/9/24 Matt Beard <matt at beard.tv>
>>>>>>>>
>>>>>>>> I'm using a Global SIM.
>>>>>>>>
>>>>>>>> I may try the diag port if I can find something that reads RS-232
>>>>>>>> in this day and age! I must try and get a USB adapter.
>>>>>>>>
>>>>>>>> Matt
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tuesday, 24 September 2013, Nikki Gordon-Bloomfield wrote:
>>>>>>>>
>>>>>>>> Great. In addition, you might want to try and attach something to
>>>>>>>> the diagnostics port. You should be able to read through the port any AT
>>>>>>>> commands, to make sure it's working correctly.
>>>>>>>>
>>>>>>>> I believe there's a list somewhere of the messages you'll get from
>>>>>>>> the diagnostic port for that chip.. 901 is it?  (I can't remember, but it's
>>>>>>>> what we used to diagnose the SIM card was at fault.)
>>>>>>>>
>>>>>>>> Nikki.
>>>>>>>>
>>>>>>>> P.S. What SIM are you using? Global? O2?
>>>>>>>>
>>>>>>>>
>>>>>>>> On 24 Sep 2013, at 09:16, Matt Beard <matt at beard.tv> wrote:
>>>>>>>>
>>>>>>>> Actually, running it with stock firmware as OBDII in our ICE is
>>>>>>>> next on my list of checks.
>>>>>>>>
>>>>>>>> Matt
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tuesday, September 24, 2013, Nikki Gordon-Bloomfield wrote:
>>>>>>>>
>>>>>>>> The other suggestion I would have is to plug the ODBII module into
>>>>>>>> another car -- or power it from a bench supply using the method detailed in
>>>>>>>> the development guide?
>>>>>>>>
>>>>>>>> Nikki.
>>>>>>>>
>>>>>>>> On 24 Sep 2013, at 08:08, Mark Webb-Johnson <mark at webb-johnson.net>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Matt,
>>>>>>>>
>>>>>>>> I have modules with me for replacement, if necessary.
>>>>>>>>
>>>>>>>> I am concerned about your comments regarding soldering. All the v2
>>>>>>>> modules are supposed to be machine soldered, and we have had almost zero
>>>>>>>> returns of broken modules.I would be grateful if you could let me know the
>>>>>>>> serial number of your module, the approximate date you received it, and if
>>>>>>>> possible a picture of the soldering issues.
>>>>>>>>
>>>>>>>> I too am perplexed why the module would work SMS but not GPRS.
>>>>>>>> Perhaps you can try setting the vehicle type to 'XX', which would eliminate
>>>>>>>> any can bus/message issues, and see if the problem still occurs.
>>>>>>>>
>>>>>>>> Please eMail me, off list, as mark (at) openvehicles (dot) com, and
>>>>>>>> I'll work through this with you.
>>>>>>>>
>>>>>>>> Regards, Mark.
>>>>>>>>
>>>>>>>> On 24 Sep, 2013, at 5:13 AM, Matt Beard OVMS <smvo at mxf.org.uk>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Thanks Thomas,
>>>>>>>>
>>>>>>>> That has confirmed for me that my hardware has died.
>>>>>>>>
>>>>>>>> Looking at the circuit board the soldering on the GSM modem is
>>>>>>>> shocking, but I don't understand how it can work for SMS, but crash with
>>>>>>>> GPRS. Looks like I will be spending most of my effort in the coming days
>>>>>>>> trying to get the hardware replaced!
>>>>>>>>
>>>>>>>> I have confirmed that the unit functions perfectly (though is
>>>>>>>> pretty useless) with the GPRS switch set to disabled. If it is booted with
>>>>>>>> the switch enabled it dies as soon as I set the GPRS parameters, then
>>>>>>>> enters an endless reboot loop.
>>>>>>>>
>>>>>>>> Matt
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 23 September 2013 21:18, Thomas Bergo <thomas.bergo at gmail.com>wrote:
>>>>>>>>
>>>>>>>> Attached is the hex file, this is the exact same that is running om
>>>>>>>> my module now.
>>>>>>>>
>>>>>>>> Regards, Thomas
>>>>>>>>
>>>>>>>>
>>>>>>>> 2013/9/23 Matt Beard <matt at beard.tv>
>>>>>>>>
>>>>>>>> Thomas,
>>>>>>>>
>>>>>>>> That would be really useful. I am worried that the module may have
>>>>>>>> failed.
>>>>>>>>
>>>>>>>> I did not keep a copy of the last working hex file (lesson
>>>>>>>> learned!) but did save the sources. Rebuilt from previous sources and
>>>>>>>> loaded. It still fails.
>>>>>>>>
>>>>>>>> Matt
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Monday, September 23, 2013, Thomas Bergo wrote:
>>>>>>>>
>>>>>>>>  Matt:
>>>>>>>>
>>>>>>>> I can send you the hex file i'm running in my OVMS module, so you
>>>>>>>> can try if that woking in your module?
>>>>>>>>
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> OvmsDev mailing list
>>>>>>> OvmsDev at lists.teslaclub.hk
>>>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> OvmsDev mailing list
>>>>>> OvmsDev at lists.teslaclub.hk
>>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at lists.teslaclub.hk
>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> OvmsDev mailing list
>>>> OvmsDev at lists.teslaclub.hk
>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>>
>>>>
>>>
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>>
>>>
>>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>>
>>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20130924/0b9015f6/attachment.htm>

More information about the OvmsDev mailing list