Mark, Nikolay,

I just checked in a new Twizy release (2.6). I had to introduce a second overlay section, as my variables now exceed the 256 byte section limit of the C18 linker. There seems to be another solution configuring the linker to assign fixed addresses and sizes to sections, but that doesn't seem to be necessary. There is no RAM loss from the section split. Nevertheless, this needs to be known to other vehicle implementors (Nikolay) as well: if your variables exceed 256 bytes, distribute them over two sections. The second overlay section is addressed using:

#pragma udata overlay vehicle_overlay_data2

Sections can be switched as needed, I'm currently assigning my battery vars to "data2".

This leads me to another issue: precompiled firmware images...

I would like to point users to www.openvehicles.com for all updates, but the "firmware" page links to another site with no Twizy images at all. ("User guide" btw also just links to the Tesla guide...)

I would also like to provide full featured firmware versions, including the battery monitoring. Mark, as RAM usage has proven to be non-critical, could you include the feature by default now? If you're still in doubt, maybe we could define "V2_Production" as "without battmon" and include it only in "V2_Experimental"?

Regards,
Michael

Am 13.01.2013 09:29, schrieb Mark Webb-Johnson:

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@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