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

Mark Webb-Johnson mark at webb-johnson.net
Wed Sep 25 08:09:12 HKT 2013


We could use carbits, which is what we did with the roadster originally.

However, in general I think it best to try to determine the version based on CAN bus data. The current roadster logic is based on that (actually, it sets carbits based on what is sees on the bus).

Regards, Mark.

On 25 Sep, 2013, at 2:09 AM, Thomas Bergo <thomas.bergo at gmail.com> 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?
>>>> 
>>>> Regards, Thomas
>>>> 
>>>> 
>>>> 2013/9/23 Thomas Bergo <thomas.bergo at gmail.com>
>>>> I did a rebuild from clean to ensure that i running the exact same code.
>>>> My OVMS module is booting as expected, and only the green led is blinking OK (one blink]
>>>> 
>>>> Which version of the OVMS FW are you running? I have only tested with the 2.5.2 FW.
>>>> Are there any significant changes from 2.5.2 that can impact the code to constantly reboot?
>>>> 
>>>> 
>>>> 
>>>> 
>>>> Regards, Thomas
>>>> 
>>>> 
>>>> 2013/9/23 Matt Beard OVMS <smvo at mxf.org.uk>
>>>> OK - either this code is broken, or my OVMS is.
>>>> 
>>>> I flashed the code and set the unit up - no go, kept rebooting and the GPRS does not work.
>>>> 
>>>> Rebuild from clean. Reflashed, reloaded settings and still constant rebooting and GPRS does not work.
>>>> 
>>>> Matt
>>>> 
>>>> 
>>>> 
>>>> On 23 September 2013 10:24, Thomas Bergo <thomas.bergo at gmail.com> wrote:
>> _______________________________________________
>> 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/20130925/49bb6d7a/attachment.htm>


More information about the OvmsDev mailing list