<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Mark, Nikolay,<br>
<br>
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:<br>
<br>
#pragma udata overlay vehicle_overlay_data2<br>
<br>
Sections can be switched as needed, I'm currently assigning my
battery vars to "data2".<br>
<br>
This leads me to another issue: precompiled firmware images...<br>
<br>
I would like to point users to <a class="moz-txt-link-abbreviated" href="http://www.openvehicles.com">www.openvehicles.com</a> 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...)<br>
<br>
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"?<br>
<br>
Regards,<br>
Michael<br>
<br>
<br>
<div class="moz-cite-prefix">Am 13.01.2013 09:29, schrieb Mark
Webb-Johnson:<br>
</div>
<blockquote
cite="mid:9B4D7EA2-209F-4235-AE8C-48A9D7065F79@webb-johnson.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div><br>
</div>
<div>I've released firmware v2.2.2 to the github repository. The
change log is as follows:</div>
<div><br>
</div>
<div>
<blockquote style="margin: 0 0 0 40px; border: none; padding:
0px;">
<div>
<div><font face="Andale Mono">2013-01-11 2.2.2
Firmware 2.2.2</font></div>
<div><font face="Andale Mono"> #94 v2
firmware re-work for multiple vehicle support</font></div>
<div><font face="Andale Mono"> #95
Valet Mode - Tesla Roadster - Trunk open is working off
bonnet</font></div>
<div><font face="Andale Mono"> #96
Server: Support for historical data messages</font></div>
<div><font face="Andale Mono"> #97 CAN
overflow (lockups)</font></div>
<div><font face="Andale Mono"> #99
Update vehicle/Car
Module/VoltAmpera/voltampera_canbusnotes.txt</font></div>
<div><font face="Andale Mono"> #72 #72
Add GPS support for cars without it</font></div>
<div><font face="Andale Mono"> ###
v2.x firmware, first release</font></div>
<div><font face="Andale Mono">
Internal GPS integration</font></div>
<div><font face="Andale Mono">
Basic support for Renault Twizy</font></div>
<div><font face="Andale Mono">
Volt/Ampera work-in-progress</font></div>
<div><font face="Andale Mono">
Framework sprintf rework</font></div>
<div><font face="Andale Mono">
First draft of OVMS Development document</font></div>
<div><font face="Andale Mono">
Twizy user guide v1.0.1</font></div>
</div>
</blockquote>
</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Regards, Mark.</div>
<div><br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Michael Balzer * Paradestr. 8 * D-42107 Wuppertal
Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
</pre>
</body>
</html>