[Ovmsdev] Release Firmware

Mon Apr 15 14:11:43 HKT 2013

I'm the one who flashed Kevin's firmware. Could I have missed something? 

Sent from my iPhone

On 15 Apr 2013, at 07:03, Mark Webb-Johnson <mark at webb-johnson.net> wrote:

> 
> Kevin,
> 
> This is strange, and worrying...
> 
> I checked the logs for your car - it seems that your car has never reported odometer or trip != 0. Even with older firmware v2.2.2 it was always reporting 0 for both odometer and trip. I looked further back, and find the last record with a non-zero odometer reading seems to be  back in January (that was firmware v1.3.5, but the odometer reported was 0 even with that firmware a day later).
> 
> Seems to be that you and I are the only Tesla Roadsters on tmc server that are running v2.3.1 yet (not surprising, as only pre-released yesterday), but a bunch are running v2.2.6 (the previous release) and all those show odometer correctly. I don't think this is anything to do with new firmware - instead it seems to be specific to your car.
> 
> What is the actual odometer and trip reading in your car at the moment? Anything unusual about it (e.g. old vehicle firmware, etc)?
> 
> Can you try cycling through the VDS screens next time you go for a drive? Just keep pressing the right-arrow button on the VDS until you cycle back to the main battery screen.
> 
> Regards, Mark.
> 
> On 15 Apr, 2013, at 1:34 PM, Kevin Sharpe ZCW wrote:
> 
>> Hi Mark,
>> 
>> Thanks for the CAC explanation.
>> 
>> I can confirm I do not see ODO change from 0.0 (see attached screen shot). Indeed, I have never seen ODO change and had assumed it was only working on the very latest firmware.
>> 
>> I tried resetting the module using the app command and power cycling the hardware.
>> 
>> All the best
>> 
>> Kevin
>> 
>> 
>> 
>> On 15 Apr 2013, at 01:50, "Mark Webb-Johnson" <mark at webb-johnson.net> wrote:
>> 
>>> Kevin,
>>> 
>>> Thanks for the help testing.
>>> 
>>> CAC is retrieved (a) car is turned on, (b) car is turned off, (c) charge is started - so your experience is expected.
>>> 
>>> The odometer 0 miles is worrying. Is that still the case, or working now?
>>> 
>>> Regards, Mark.
>>> 
>>> On 15 Apr, 2013, at 3:50 AM, Kevin Sharpe ZCW wrote:
>>> 
>>>> Ignore my comment regarding CAC which I see now the car is on charge :-)
>>>> 
>>>> 		Kevin Sharpe | Founder & Patron
>>>> Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld
>>>> kevin.sharpe at zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld
>>>> 
>>>> Zero Carbon World is a UK Registered Charity #1141347
>>>> From: Kevin Sharpe <kevin.sharpe at zerocarbonworld.org>
>>>> Reply-To: OVMS Developers <ovmsdev at lists.teslaclub.hk>
>>>> Date: Sunday, 14 April 2013 18:32
>>>> To: "ovmsdev at lists.teslaclub.hk" <ovmsdev at lists.teslaclub.hk>
>>>> Subject: [Ovmsdev] FW: Release Firmware
>>>> 
>>>> Email sent again without the car photo (which exceeded the 1Mbyte file attachment limit)…
>>>> 
>>>> 
>>>> From: Kevin Sharpe <kevin.sharpe at zerocarbonworld.org>
>>>> Date: Sunday, 14 April 2013 18:28
>>>> To: OVMS Developers <ovmsdev at lists.teslaclub.hk>
>>>> Subject: Re: [Ovmsdev] Release Firmware
>>>> 
>>>> Just to add a little more to Nikki's report…
>>>> 
>>>> I've seen some odd behaviour with SOC… if you see the attached photo's you'll see STAT report SOC as 46% and then 50% even though the commands were sent within a minute of one another (approximately). You'll also see the app and car displayed 52% and 92m at the same time.
>>>> 
>>>> I also note that the ODO reports 0.0 mil and I see no CAC in response to a STAT command. Is this expected behaviour with this firmware?
>>>> 
>>>> Firmware version reported in the app is 2.3.1/TR/V2
>>>> 
>>>> All the best,
>>>> 		Kevin Sharpe | Founder & Patron
>>>> Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld
>>>> kevin.sharpe at zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld
>>>> 
>>>> Zero Carbon World is a UK Registered Charity #1141347
>>>> From: Nikki Gordon-Bloomfield <nikki at littlecollie.com>
>>>> Reply-To: OVMS Developers <ovmsdev at lists.teslaclub.hk>
>>>> Date: Sunday, 14 April 2013 17:24
>>>> To: OVMS Developers <ovmsdev at lists.teslaclub.hk>
>>>> Subject: Re: [Ovmsdev] Release Firmware
>>>> 
>>>> Just a head up:
>>>> 
>>>> I flashed my Twizy firmware and it immediately started working. 
>>>> 
>>>> I flashed Kevin's firmware on his Roadster, and it took about 10 minutes to start working. 
>>>> 
>>>> Not sure why -- but thought you'd all appreciate the report. :) 
>>>> 
>>>> I've got a 35 mile round-trip tonight to Bath, and about 120 miles of work-related travel this week in the Twizy, so plenty of time to test it! 
>>>> 
>>>> Nikki Gordon-Bloomfield
>>>> 
>>>> http://about.me/aminorjourney/bio
>>>> email: nikki at littleCollie.com
>>>> tel: +44 7901 553308
>>>> 
>>>> On 14 Apr 2013, at 17:04, Michael Balzer <dexter at expeedo.de> wrote:
>>>> 
>>>>> 
>>>>> I've had GPS streaming enabled during the last days, and neither GPS nor GSM connectivity are good at the moment. May be related, as streaming means more data communication. But still that should not lead to RAM corruption.
>>>>> 
>>>>> 
>>>>> Am 14.04.2013 17:54, schrieb Michael Balzer:
>>>>>> Mark,
>>>>>> 
>>>>>> I've got the last but one version in my car, just lacking the new VEHICLE commands.
>>>>>> 
>>>>>> I've got two open issues, the minor one being to raise the 12V auto acquisition time even more, as the faults have become better but it's not yet perfect. I'm trying 20 TAD now, as we don't need to be fast on that A/D conversion.
>>>>>> 
>>>>>> But a major issue might have turned up: I've just had the second RAM corruption within three days. Effect:
>>>>>> 
>>>>>> MP-0 c32,0,106,119,*-OVM-DebugCrash,2013-04-14 14:06:40,0,2.2.7/RT2.6.4/V2,0,0000,20
>>>>>> MP-0 c32,0,107,119,*-OVM-DebugCrash,2013-04-14 14:25:13,0,2.2.7/RT2.6.4/V2,80,0020,61
>>>>>> 
>>>>>> As there is no checkpoint 61, this means at least the debug variables have been overwritten, was the same with the first occurence (but other values).
>>>>>> 
>>>>>> As the module behaves weird afterwards I suppose more variables have been corrupted.
>>>>>> 
>>>>>> I've looked through the last changes several times, I'm pretty sure none could have introduced this kind of bug... if I'm the only one experiencing this, maybe I've got some hardware issue as well?
>>>>>> 
>>>>>> I'll continue checking the source for possible buffer overruns...
>>>>>> 
>>>>>> Regards,
> _______________________________________________
> 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/20130415/c7088554/attachment.htm>