<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\0027Andale Mono\0027";
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:357581893;
mso-list-template-ids:-2122675902;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1103919393;
mso-list-template-ids:-2140471780;}
@list l2
{mso-list-id:1241788471;
mso-list-template-ids:-1096235072;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=DE-CH link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Re Homelink<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The Homelink in Europe is disabled, because the frequency in Europe is not the same like in the US (FCC regulation?).<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=DE style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Von:</span></b><span lang=DE style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> ovmsdev-bounces@lists.teslaclub.hk [mailto:ovmsdev-bounces@lists.teslaclub.hk] <b>Im Auftrag von </b>Mark Webb-Johnson<br><b>Gesendet:</b> Samstag, 12. Mai 2012 13:22<br><b>An:</b> OVMS Developers<br><b>Betreff:</b> [Ovmsdev] Car firmware: 1.2.5<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I've committed to github car firmware v1.2.5.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Changes since v1.2.2 include:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>Support multiple vehicle configurations - TeslaRoadster and VoltAmpera<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>New LED indication scheme, and net driver tidy-ups<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>Auto-support Tesla Roadster v1.5 cars<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>Issue #38 - Prevent user from locking car if car is ON<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1'>Issue #39 - Alert (SMS/PUSH) if trunk is opened while in valet mode<o:p></o:p></li></ul></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Please don't get too excited - this doesn't support Volt/Ampera yet - we're just laying the ground work for that support, as some European developers are about to start work on it.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I don't think this release will make it to end-users in its current form. I'm still working on some features to go in, including:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2'>Drive logging<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2'>Charge logging<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2'>Timed (delayed) charging mode commands<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2'>Timed charging status feedback<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2'>Complete-charging-by charging mode<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2'>Cooldown<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2'>Moving digital speedo out of experimental and make it available in production units<o:p></o:p></li></ol></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Items [1], [2] and [3] are relatively easy and what I'm working on now.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Item [4] is tricky because we haven't found the status update message on the bus yet. Still looking. Item [5] needs the algorithm and lookup table. Item [6] is easy to do, but needs the thresholds defined (what battery temperature to cooldown from, what battery temperature to stop cooldown at, and what current/voltage to use for cooldown).<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Item [7] seems reasonable now, given the number of cars now using the digital speedo feature and the complete lack of issues seen with it.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I notice there was some discussion on the TMC forum about homelink control. That would be pretty easy to do, but we don't have homelink modules here in Hong Kong, and I don't have the can bus codes. They are probably easy to find on ID#102. If someone with a usb-can and a homelink adaptor wants to get the codes, I'm very willing to put them in. It certainly is a cool feature.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>So, I'm not sure what will make it into what release, when.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>This v1.2.5 release is definitely developers-only, and intended to check stability of the modem driver revisions and usability of the new LED feedback scheme. It is fully backwards-compatible with v1.2.2, and you can upgrade/downgrade firmware as you need.<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>It is in my car now, and seems to be ok. I would be grateful if developers with some time could try it out and let me have feedback on overall stability and usability of the new LED indication scheme.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I've got a little youtube video demonstrating this:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><blockquote style='margin-left:30.0pt;margin-right:0cm'><div><p class=MsoNormal><a href="http://www.youtube.com/watch?v=MdsB8qK6beY">http://www.youtube.com/watch?v=MdsB8qK6beY</a><o:p></o:p></p></div></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>The new LED indication scheme is as follows:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><ol start=1 type=1><li class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l2 level1 lfo3'>When first powered on, the red led stays on, and the green led blinks the version of firmware in the module (e.g.; 1, 2, 5). After that, it enters normal mode.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt;mso-list:l2 level1 lfo3'>In normal mode, the green led is used to indicate the state, and the red led is used to indicate the last error.<o:p></o:p></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l2 level1 lfo3'>If the modem needs to be reset, both red and green leds are turned on for the couple of seconds it takes to reset the modem.<o:p></o:p></li></ol></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The following states are defined:<o:p></o:p></p></div><blockquote style='margin-left:30.0pt;margin-right:0cm;border-width:initial;border-color:initial'><p class=MsoNormal><span style='font-family:"'Andale Mono'","serif"'>// LED MODES<br>#define NET_LED_WAKEUP 10 // Attempting to wake up the modem<br>#define NET_LED_INITSIM1 9 // Checking SIM card insertion status<br>#define NET_LED_INITSIM2 8 // Checking SIM card PIN status<br>#define NET_LED_INITSIM3 7 // Initialising modem<br>#define NET_LED_COPS 6 // COPS initialisation<br>#define NET_LED_NETINIT 5 // GPRS NET initialisation<br>#define NET_LED_NETAPNOK 4 // GPRS APN is OK, final init<br>#define NET_LED_NETCALL 3 // GPRS Network call<br>#define NET_LED_READY 2 // READY state<br>#define NET_LED_READYGPRS 1 // READY GPRS state</span><o:p></o:p></p></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The normal behavior is it will start at 10 green blinks and count down to 2 (GSM only) or 1 (GPRS). If GPRS lock is lost, but GSM is still up, the green will blink 1.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The followed error codes are defined:<o:p></o:p></p></div><blockquote style='margin-left:30.0pt;margin-right:0cm;border-width:initial;border-color:initial'><p class=MsoNormal><span style='font-family:"'Andale Mono'","serif"'>// LED ERRORS<br>#define NET_LED_ERRLOSTSIG 1 // Lost signal<br>#define NET_LED_ERRMODEM 2 // Problem communicating with modem<br>#define NET_LED_ERRSIM1 3 // SIM is not inserted/detected<br>#define NET_LED_ERRSIM2 4 // PIN lock on the SIM<br>#define NET_LED_ERRCOPS 6 // COPS GSM lock could not be obtained<br>#define NET_LED_ERRGPRSRETRY 7 // Error (maybe temp) during GPRS init<br>#define NET_LED_ERRGPRSFAIL 8 // GPRS NET INIT failed</span><o:p></o:p></p></blockquote><div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The error code is cleared (red led turned off) once everything is ok.<o:p></o:p></p></div></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regards, Mark.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>