<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Tom,<div><br></div><div>Here are the server logs (nothing very confidential in the 'S' and 'D' messages [I've removed odometer, etc, after temperatures], so hope ok to post here):</div><div><br></div><div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><font face="Andale Mono">2013-08-17 00:56:14.477118 -0400 info main: #69 C SAX217 rx msg S 71,M,-1,0,stopped,standard,132,139,40,226,100,27,7,21,0,0,0,-1,151.91,17,-1,0,0,0,0,0<br>2013-08-17 00:56:14.480328 -0400 info main: #69 C SAX217 rx msg D 128,32,3,38,68,30,...<br>2013-08-17 01:06:09.329374 -0400 info main: #69 C SAX217 rx msg S 68,M,-1,0,stopped,standard,126,140,40,226,100,27,7,21,0,0,0,-1,151.91,17,-1,0,0,0,0,0<br>2013-08-17 01:06:09.333821 -0400 info main: #69 C SAX217 rx msg D 128,32,3,41,75,30,...<br>2013-08-17 01:09:57.185946 -0400 info main: #69 C SAX217 rx msg S 68,M,-1,0,stopped,standard,126,140,12,0,100,27,7,21,0,0,0,-1,151.91,17,-1,0,0,0,0,0<br>2013-08-17 01:09:57.189470 -0400 info main: #69 C SAX217 rx msg D 100,0,3,35,60,30,...<br>2013-08-17 01:10:01.765659 -0400 info main: #69 C SAX217 rx msg S 68,M,-1,0,prepare,standard,126,140,12,0,100,0,7,13,0,0,0,-1,151.91,17,-1,0,0,0,0,0<br>2013-08-17 01:10:13.107763 -0400 info main: #69 C SAX217 rx msg S 68,M,1,0,stopped,standard,126,140,12,0,100,0,2,14,0,0,0,-1,151.91,17,-1,0,0,0,0,0<br>2013-08-17 01:10:17.925488 -0400 info main: #69 C SAX217 rx msg S 68,M,1,0,stopped,standard,126,140,12,0,100,0,2,14,0,0,0,-1,151.91,17,-1,0,0,0,0,0<br>2013-08-17 01:10:17.928642 -0400 info main: #69 C SAX217 rx msg D 108,0,3,35,60,30,...<br>2013-08-17 01:10:42.844896 -0400 info main: #69 C SAX217 rx msg S 68,M,1,0,stopped,standard,126,140,12,0,100,0,2,14,0,0,0,-1,151.91,17,-1,0,0,0,0,0<br>2013-08-17 01:10:42.849100 -0400 info main: #69 C SAX217 rx msg D 108,0,3,34,59,30,...<br>2013-08-17 01:12:31.604588 -0400 info main: #24 C SAX217 rx msg S 64,M,239,16,charging,range,151,168,16,1,100,0,5,1,3,0,0,-1,151.91,367,-1,0,0,1,27,42<br>2013-08-17 01:12:35.524060 -0400 info main: #24 C SAX217 rx msg D 124,0,3,36,57,30,...<br>2013-08-17 01:12:44.965847 -0400 info main: #24 C SAX217 rx msg D 124,0,3,36,57,30,...<br>2013-08-17 01:16:31.640460 -0400 info main: #24 C SAX217 rx msg S 68,M,1,0,stopped,standard,127,141,12,5,100,0,3,21,0,0,0,-1,151.91,381,-1,0,0,0,27,38<br>2013-08-17 01:20:24.337827 -0400 info main: #24 C SAX217 rx msg S 68,M,1,0,stopped,standard,127,141,12,5,100,0,3,21,0,0,0,-1,151.91,381,-1,0,0,0,27,38<br>2013-08-17 01:20:24.345774 -0400 info main: #24 C SAX217 rx msg D 108,0,3,34,59,28,...<br>2013-08-17 01:20:50.817512 -0400 info main: #24 C SAX217 rx msg D 108,0,3,34,59,28,...<br>2013-08-17 01:21:31.476733 -0400 info main: #24 C SAX217 rx msg D 100,0,3,33,59,28,...<br>2013-08-17 01:21:31.479403 -0400 info main: #24 C SAX217 rx msg S 68,M,-1,127,stopped,standard,127,141,12,-1,100,0,3,21,0,0,0,-1,151.91,381,-1,0,0,0,27,38<br>2013-08-17 01:28:00.151699 -0400 info main: #24 C SAX217 rx msg S 67,M,-1,127,stopped,standard,125,139,12,-1,100,0,3,21,0,0,0,-1,151.91,381,-1,0,0,0,27,38<br>2013-08-17 01:28:00.156752 -0400 info main: #24 C SAX217 rx msg D 100,0,3,33,59,28,...<br>2013-08-17 01:28:40.931885 -0400 info main: #24 C SAX217 rx msg D 100,0,3,33,59,28,...</font></blockquote></div><div><br></div><div>Time zone is EDT.</div><div><br></div><div>The "S" message fields are:</div><div><div><ul class="MailOutline"><li>SOC</li><li>Units ("M" for miles, "K" for kilometres)</li><li>Line voltage</li><li>Charge current (amps)</li><li>Charge state (charging, topoff, done, prepare, heating, stopped)</li><li>Charge mode (standard, storage, range, performance)</li><li>Ideal range</li><li>Estimated range</li><li>Charge limit (amps)</li><li>Charge duration (minutes)</li><li>Charger B4 byte (tba)Charge KWH consumed</li><li>Charge sub-state</li><li>Charge state (as a number)</li><li>Charge mode (as a number)</li><li>Charge Timer mode (0=onplugin, 1=timer)</li><li>Charge Timer start time</li><li>Charge timer stale (-1=none, 0=stale, >0 ok)</li><li>Vehicle CAC100 value</li><li>ACC: Mins remaining until car will be full</li><li>ACC: Mins remaining until car reaches charge limit</li><li>ACC: Configured range limit</li><li>ACC: Configured SOC limit</li><li>Cooldown: Car is cooling down (0=no, 1=yes)</li><li>Cooldown: Lower limit for battery temperature</li><li>Cooldown: Time limit (minutes) for cooldown</li></ul></div></div><div><br></div><div>The "D" message fields are:</div><div><div><ul class="MailOutline"><li>Door state #1</li><li>Door state #2</li><li>Lock/Unlock state 4 = car is locked</li><li>Temperature of the PEM (celcius)</li><li>Temperature of the Motor (celcius)</li><li>Temperature of the Battery (celcius)</li></ul></div><div><br></div></div><div>From what I can see, earlier (01:06:09) you had current limit at 40A, but at 01:09:57 it was reported as having dropped to 12A. The cool down charge started at 01:12:31 (switching to range mode and 16A) and stopped at 01:16:31 (switching back to standard mode and 12A). The cool down only ran for 4 mins, to bring battery temperature down from 30Celcius to 28Celcius. I guess it hit 27Celcius (your requested limit temperature) quite quickly, then went up 1 more degree after the stop.</div><div><br></div><div>The strange thing is why the drop in current limit from 40A at 01:06:09 to 12A at 01:09:57. It seems that at 40A the car was driving, but at 12A the car was parked with the charge port open.</div><div><br></div><div>Do you have the roadster set to save a charge limit of 12A at that location? From what I can see with the 2.x cars, the charge limit based on location is set immediately the charge port is opened (which is why my ACC stuff delays a few seconds before setting what it wants).</div><div><br></div><div>Regards, Mark.</div><div><br></div><div>P.S. Thanks for jumping on and helping test this. I've done quite a few cool downs in my 2.5 car, but it is good to see it work in a 1.5.</div><div>P.P.S. If you look closely, you'll see your hard work on charge time prediction show up. An estimate of 367 minutes from SOC 64% to full range mode, at 16A, changing to 381 minutes in standard mode at 12A. Nice.</div><div><br><div><div>On 17 Aug, 2013, at 1:35 PM, Tom Saxton <<a href="mailto:tom@idleloop.com">tom@idleloop.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I tried the cooldown feature with the right firmware installed this time.<br><br>It worked as expected, charging in Range mode at 240V/16A.<br><br>After the cooldown, it restored the charge mode to Standard, as expected,<br>but the OVMS app reported that the charge current was restored to 12A<br>instead of 40A as it was when I started cooldown.<br><br> Tom<br><br>on 8/16/13 3:17 PM, Tom Saxton wrote:<br><br><blockquote type="cite">Nevermin. The build worked, the download didn't.<br><br>Now I have the correct software on the module, which reports "2.5.1/TR/V1".<br><br>I may get another chance to try cooldown tonight.<br><br> Tom<br><br>on 8/16/13 1:42 PM, Tom Saxton wrote:<br><br><blockquote type="cite">Mark,<br><br>Wow, great stuff. Can't wait to have this all working!<br><br>I built and installed the latest version and tried to do a cooldown, but<br>couldn't get it to work.<br><br>I arrived home with the batteries at 98F (37C), flashed the OVMS device, and<br>sent a cooldown command. Nothing.<br><br>I set feature #13 to 255 and sent cooldown again. Nothing.<br><br>I took a look at the code, set param 15 to "27,45", sent cooldown again.<br>Nothing.<br><br>I look at the code some more, so that the car had to be "on" for cooldown to<br>work, so I went out and opened the driver's door to wake the car up. Battery<br>pack still at 98F. Sent cooldown again. Nothing.<br><br>I do have feature 15 (CAN Write) set to 1. The OVMS app lists the firmware<br>version as "2.3.3/TR/V1".<br><br>As I wanted to cool the batteries and then do a change, I manually kicked<br>off a 12A Range mode charge.<br><br>What should I try next time the batteries are hot?<br><br> Tom<br><br><br>on 8/15/13 6:55 AM, Mark Webb-Johnson wrote:<br><br><blockquote type="cite">Wow, let's not do that again.<br><br>I just spent the past two weeks trying to debug a problem where my car<br>module<br>kept rebooting. The debug crash log showed it seemed to be identical to a<br>normal power-on start. Seems like the module rebooted itself a dozen times a<br>day. After trying everything - more than a dozen firmware changes painfully<br>loaded into the car module, I finally found the problem: the module was<br>rebooting, it was just incorrectly reporting a reboot every time the<br>cellular<br>signal recovered. Good grief.<br><br>Anyway, back on track again now.<br><br>Today, I've pushed to github my backlog of 36 commits, totalling 1.5MB! This<br>makes the first 'alpha' release of v2.5 code. A summary of the (extensive)<br>changes:<br><br>Tesla Roadster Experimental Speedo<br><br>No longer experimental. Now on bit#0 of permanent feature #13. Old feature<br>#0<br>no longer used.<br><br>Drive and Charge logging<br><br>Server as well as vehicle changes made to support this. Setting bit#1 of<br>permanent feature #13 will turn on logging of drives. Setting bit#2 of<br>permanent feature #13 will turn on logging of charges. If enabled, at the<br>end<br>of each drive/charge the logging system will attempt to upload a *-Log-Drive<br>or *-Log-Charge record with details on the drive/charge. It can store up to<br>6<br>such records without server connectivity. The records themselves can be<br>downloaded as historical data using either the HTTP or OVMS protocol APIs.<br>To<br>implement this, a new 'h' style of historical data submission has been<br>supported by the server - this allows for acknowledgement of successful data<br>reception by the server, as well as a time offset for cases where the data<br>cannot be immediately transmitted.<br><br>Cooldown<br><br>Core support has been added for 'cool down' charges, and implemented in the<br>Tesla Roadster module. Cooldowns can be initiated by the 'COOLDOWN' SMS<br>message, or by server command #25.<br><br>Tesla Roadster event notification<br><br>A few changes have been made to the Tesla Roadster module to try to make it<br>notify the server of major events immediately (such as charge mode changes,<br>charge limit changes, etc).<br><br>Server support for Authentication failures<br><br>The server code has been extended to send a PUSH notification in the event a<br>vehicle authentication fails. The server will also send another PUSH<br>notification if the vehicle subsequently authenticates successfully.<br><br>Distance utility function<br><br>Courtesy of Tom, a distance utility function to calculate the distance<br>between<br>two GPS locations and tell if they are closer than a pre-set limit.<br><br>NET fixes<br><br>Added a few more checkpoints and sanity checks for NET layer data, to try to<br>avoid crashes and overflows.<br><br>Debug Crash Reason reporting<br><br>Bug fix to avoid duplicate reports of debug crashes every time the server<br>connection is made. As a side-effect, normal first-time boot-ups will no<br>longer be reported (by design).<br><br>Stub ACC implementation<br><br>I've done a lot of work on ACC in my own branch, but not committed to head,<br>yet. I need some more time to do further testing before I'm ready to<br>release.<br>For the moment, there is a minimal implementation the does the ACC location<br>mapping, and is capable of seeing if the car is within range of an ACC<br>location. You can also configure the ACC locations and parameters. More on<br>this will come with v2.5.2.<br><br>Documentation<br><br>I've updated the Tesla Roadster user guide, as well as OVMS Protocol guide,<br>for the above.<br><br>I haven't built binary firmware for this yet, as it is so new and raw. It is<br>running in my car, and now seems stable, but needs more testing before<br>prime-time release. If you want to try it, you'll need to build from source.<br>Then, set feature #13 to 255 (to enable all opt-in features) and you should<br>get a digital speedo (Tesla Roadster v2.x cars only) as well as logging to<br>the<br>server of both drives and charges.<br><br>I'm over the hump now, and hopefully v2.5.2 can come within the next week.<br><br>Regards, Mark.<br><br>On 5 Aug, 2013, at 12:38 PM, Mark Webb-Johnson <<a href="mailto:mark@webb-johnson.net">mark@webb-johnson.net</a>><br>wrote:<br><br><blockquote type="cite"><br>Just a short note on progress.<br><br>I managed to get a lot done over the weekend. Working with Tom on some misc<br>functions for ACC, and all looks good so far. Basic ACC location management<br>is done, and I've worked out a way of using base64 to encode the ACC<br>structures into our limited 32byte parameters. Seems to work quite well -<br>very lightweight (we already have base64 for the comms protocol), and very<br>expandable.<br><br>I'm now just trying to pull everything together to get cooldown working.<br>Once<br>that is working, I'll commit (even in that unfinished form). Logging (drive<br>and charge) is already done, and part of this. Flash space is getting<br>concerning (approaching 95% now, for experimental with all vehicles), so<br>we'll have to address that once ACC is out.<br><br>I'm getting a rather large backlog of other requests now (put aside due to<br>ACC work, trip to USA for TESLIVE, and horrendous day job hours). Once the<br>basic ACC is committed, I'll be able to spend some time to try to work<br>through that. Apologies for the delays (to anyone waiting for me).<br><br>Regards, Mark.<br><br>_______________________________________________<br>OvmsDev mailing list<br><a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a><br>http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br></blockquote><br>_______________________________________________<br>OvmsDev mailing list<br><a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a><br>http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br></blockquote><br><br>_______________________________________________<br>OvmsDev mailing list<br><a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a><br>http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br><br></blockquote><br><br>_______________________________________________<br>OvmsDev mailing list<br><a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a><br>http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br><br></blockquote><br><br>_______________________________________________<br>OvmsDev mailing list<br><a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a><br>http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br></blockquote></div><br></div></body></html>