[Ovmsdev] v2.2.2

[Michael Balzer]

My pleasure, really :-)

And I would've been stranded right away without your great support, Mark.

Thanks!
Michael


Am 17.01.2013 02:22, schrieb Mark Webb-Johnson:
>
> I've been running v2.2.2 in my car for a week now, and I've gotta say 
> that this seems to be the most stable OVMS firmware I've seen to date. 
> My car's connection to the server has been rock-solid (only one GPRS 
> re-connection due to poor cellular coverage), and zero module reboots. 
> An average of about 10KB of cellular data a day (an all-time low).
>
> I'd like to give a big public thanks to Michael Balzer for all his 
> hard work on this (and the v2 framework in general). His DebugCrash 
> diagnostics, and re-working of the sprintf calls to his own library 
> routines, seems to have nailed those strange random module reboots we 
> were seeing. Thanks, Michael - most appreciated.
>
> Rollout of this version has been slow. On the TMC server, today, there 
> are just 6 cars running v2.x code. I really would like to encourage 
> people to upgrade to this version, to let us get more data on it - 
> you'll hopefully also get the benefit of more stability, lower 
> cellular data usage, and a few bugs have been fixed since v1.5.1.
>
> Regards, Mark.
>
> On 13 Jan, 2013, at 4:29 PM, Mark Webb-Johnson wrote:
>
>>
>> I've released firmware v2.2.2 to the github repository. The change 
>> log is as follows:
>>
>>     2013-01-11 2.2.2 Firmware 2.2.2
>>      #94 v2 firmware re-work for multiple vehicle support
>>      #95 Valet Mode - Tesla Roadster - Trunk open is working off bonnet
>>      #96 Server: Support for historical data messages
>>      #97 CAN overflow (lockups)
>>      #99 Update vehicle/Car Module/VoltAmpera/voltampera_canbusnotes.txt
>>      #72 #72 Add GPS support for cars without it
>>      ### v2.x firmware, first release
>>          Internal GPS integration
>>          Basic support for Renault Twizy
>>          Volt/Ampera work-in-progress
>>          Framework sprintf rework
>>          First draft of OVMS Development document
>>          Twizy user guide v1.0.1
>>
>>
>> The .hex files have been built for all configurations. I (and others) 
>> have tested this in hardware v2 vehicles, but so far this is pretty 
>> much untested with v1 hardware (in particular for Tesla Roadster). I 
>> would appreciate it if you guys could test it and make sure it is ok 
>> for v1 hardware in Roadsters.
>>
>> Once you upgrade firmware to v2, you will need to either (a) SMS 
>> "MODULE" command again to include the fourth parameter vehicle type 
>> "TR", or (b) use the iOS App to set feature #14 to "TR". You will 
>> require this for the CAN bus stuff to work. I have updated the Tesla 
>> Roadster user guide to reflect this new parameter.
>>
>> Regards, Mark.
>>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk <mailto: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

-- 
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20130117/aef3d00c/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dexter.vcf
Type: text/x-vcard
Size: 206 bytes
Desc: not available
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20130117/aef3d00c/attachment-0002.vcf>