<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, Michael,<div><br></div><div>I've implemented a fix for this in:</div><div><br></div><div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div>7831e4c #97 CAN overflow (lockups)</div></blockquote></div><div><br></div><div>It is the latest v2.1.1 bleeding edge code.</div><div><br></div><div>What I've done is take the code snippet out of vehicle_twizy.c and put it in vehicle.c, so that all vehicles benefit from it.</div><div><br></div><div>Michael: Please check. It seems ok, and I don't think will affect you.</div><div><br></div><div>Regards, Mark.</div><div><br><div><div>On 18 Dec, 2012, at 2:51 AM, Tom Saxton <<a href="mailto:tom@idleloop.com">tom@idleloop.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Rebooting the device fixed the problem.<br><br>I didn't get your email until after I had rebooted, but if it happens again<br>I'll try the reset command.<br><br> Tom<br><br>on 12/16/12 4:42 PM, Mark Webb-Johnson wrote:<br><br><blockquote type="cite">Tom,<br><br>I think this is definitely Michael's can-bus-lockup issue.<br><br>The problem seems to be that if the can bus overflows (or gets some other sort<br>of error?) then it sets a flag in the controller, and the controller won't<br>deliver any more messages until the flag is cleared. The bus still has<br>messages, but they don't get to the OVMS App. The OVMS code in the car will<br>keep reporting the old bus values - the only indication would be the stale<br>indicators would all go stale as there were no more messages seen by the code.<br><br>What Michael has done for the Twizy code (where he was seeing this often) is<br>to add a once-a-second check for the can bus error flag, and clear the<br>controller error condition if he sees it. He reported that solved his problem.<br><br>With the v2 code we are working on, I'm taking his can bus error clear code<br>and making it a standard for all cars. The roadster code will benefit from<br>this.<br><br>I think that if you reset the module (either sms RESET, or use the smartphone<br>module reset function), the error should clear (as a reset will re-iniitialse<br>the can bus controller. Can you try this? You'll know if it works if the SOC<br>immediately switches to the correct value.<br><br>Regards, Mark.<br><br>On 17 Dec, 2012, at 12:07 AM, Tom Saxton wrote:<br><br><blockquote type="cite">Opening the door didn't help.<br><br>I was wondering if I was getting data from another Roadster, so I checked<br>the Location view. It's showing the spot where the car was parked yesterday<br>afternoon, and in fact all of the data is consistent with that: SOC and<br>locked status. Since then, the car has been driven twice and charged, so<br>plenty of opportunity to get current CAN bus readings.<br><br>The other odd thing is that it shows it's been parked for 5 minutes every<br>time I update it.<br><br>The only thing unusual yesterday was that I realized I hadn't locked the car<br>a couple of minutes after we parked, so I used OVMS to lock the car, and<br>checked the Car view to confirm it was locked.<br><br>Could that have frozen things for some reason?<br><br>I'll try rebooting the car module before I drive it this morning.<br><br> Tom<br><br>on 12/16/12 6:29 AM, Mark Webb-Johnson wrote:<br><br><blockquote type="cite">Tom,<br><br>I just checked the server logs, and the car seems to be online.<br><br>2012-12-16 09:22:12.710176 -0500 info main: #65 C SAX217 msg handle S<br>73,M,-1,0,stopped,standard,135,105,32,254,100,29,7,14,0,1,200,1<br><br>It is reporting 73%.<br><br>Maybe some issue with the message reception on the can bus? Can you try<br>opening a door with the app running, and see if it registers?<br><br>[Michael, working on the Twizy, found an issue where the can bus buffers<br>could<br>overflow, causing no more can messages to be received - I haven't seen it on<br>the Roadster before, but it is possible this is what you are seeing]<br><br>Regards, Mark.<br><br>On 16 Dec, 2012, at 10:23 PM, Tom Saxton <<a href="mailto:tom@idleloop.com">tom@idleloop.com</a>> wrote:<br><br><blockquote type="cite">There's something odd going on with OVMS and my Roadster this morning. I'm<br>seeing data that claims to be live, but which is totally wrong.<br><br>I got home last night with a 50% charge and set the Roadster to charge at 2<br>am. When I checked it this morning at 6:20, OVMS said the car was at 73%,<br>live, parked for 5 minutes, and locked. When I checked the car, none of<br>those were true. The car's at 97%, has been parked 9.5 hours, and is<br>unlocked.<br><br>I've never seen OVMS be wrong and claim to be "live".<br><br> Tom<br><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></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><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>