<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Jack, Tom,<div><br></div><div>Yep, Jack is right. It is feature #14. 0x0e. I seem to have get hexed.</div><div><br></div><div>P.S. Tom's problem has been narrowed down to a faulty PIC board. The soldering seems ok, so probably the CAN bus driver chip. The module doesn't work in a 2.x roadster either. We're sending him a new board (I'm going to QC one tonight)..</div><div><br><div><div>On 7 Mar 2012, at 3:34 PM, Jack West wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div bgcolor="#FFFFFF"><div>Tom,</div><div><br></div><div>Carbits is actually feature 14 and would need set to be set to 1 for a 2008 Roadster.</div><div><br></div><div>Feature 15 set to 1 is to enable writing to the CAN bus. Set to 0 is 'listen' only.</div><div>You only need to do this once.</div><div><br></div><div>So</div><div>SMS </div><div>FEATURE 15 1 (allows you to do all the fun stuff)</div><div>FEATURE 14 1 (because you have a 2008)</div><div><br></div><div>That should do it (once you get the unit working). If you are using the new iPhone app you can do it from the Cars/I/Control tab.</div><div><br></div><div>I don't think Feature 12 is anything yet.</div><div><br></div><div>Jack</div><div><br></div><div><br></div><div><br>On Mar 6, 2012, at 3:45 PM, Mark Webb-Johnson <<a href="mailto:mark@webb-johnson.net">mark@webb-johnson.net</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Tom,<div><br></div><div>Scott451's original (ground breaking) post is at:</div><div><br></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><a href="http://www.teslamotorsclub.com/showthread.php/4388-iPhone-app/page2?p=49456&viewfull=1#post49456">http://www.teslamotorsclub.com/showthread.php/4388-iPhone-app/page2?p=49456&viewfull=1#post49456</a></div></blockquote><div><br></div><div>He talks there about the 2008 roadster, and confirms 1MHz bus speed.</div><div><br></div><div>Your confirmation of the wales gps location and 0 SOC means the module is definitely not getting any can bus messages.</div><div><br></div><div>It is either a faulty board, or some other incompatibility.</div><div><br></div><div>Can you ask Cathy (she is your hardware support, right?) to check the continuity on connections on the MCP2551P and pins #23 and #24 on the PIC CPU?</div><div><br></div><div>Do you know anyone close by with a 2.x roadster that you could plug the module in, to rule out 1.5 vs 2.x incompatibility?</div><div><br></div><div>Regards, Mark. </div><div><br><div><div>On 7 Mar 2012, at 1:35 AM, Tom Saxton wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>I did the "FEATURE 12 1" SMS command, but got no response. Are those<br>commands documented somewhere, or is it a "read the code" deal? (It is cool<br>to be able to read the code.)<br><br>I get the same "not charging" status with the charge port door open.<br><br>When I do a GPS command, I get back a link to 52.042460,-3.944089 which I<br>assume is the default position in Wales.<br><br>So, it seems the OVMS module isn't getting any of these CAN messages. Is<br>there a way to tell if the board is getting any messages at all?<br><br>With Cathy's help, I checked continuity and all four pins going to the MCU<br>board. They all check out, as do the four twin wires to the other connector.<br><br>When plugged in, after the start up sequence, I get a solid green LED on<br>each board and a blinking blue LED on the modem board.<br><br>Finally, I'm sure my diag port is functional as it has been working with my<br>Tattler (although the Tattler is going through some brain surgery right now<br>so I can't confirm that it's working today).<br><br>BTW, I notice the generated GPS link takes you to a static map that can't be<br>scaled or panned. This makes it impossible to tell where the pin is if you<br>don't recognize any features in the static map.<br><br>I like using a simpler link that gets you a fully functional map:<br><br> <a href="http://maps.google.com/maps?q=52.042460,-3.944089">http://maps.google.com/maps?q=52.042460,-3.944089</a><br><br>Also, I'm also not a big fan of the Tesla logo for the pin, but I have an<br>unusual history with the company that may be coloring my attitude on that.<br><br> Tom<br><br>on 3/5/12 5:38 PM, Mark Webb-Johnson wrote:<br><br><blockquote type="cite">Tom,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Good to have you aboard.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We haven't been able to test the module on 1.5 cars (which is why we're only<br></blockquote><blockquote type="cite">shipping to end-users with 2.x cars). The problem we've had is that all the<br></blockquote><blockquote type="cite">developers involved have 2.x cars.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">That said, the module _should_ work in a 1.5 car. Scott451 did the original<br></blockquote><blockquote type="cite">bus decodes on a 1.5 car, and while there are some differences, he did<br></blockquote><blockquote type="cite">document the messages (but we haven't been able to verify this as we have with<br></blockquote><blockquote type="cite">the 2.x cars).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">First, some trivia:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Our current master document on CAN bus messages is at:<br></blockquote><blockquote type="cite"><a href="https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/vehicle/C">https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/vehicle/C</a><br></blockquote><blockquote type="cite">ar%20Module/canbus_notes.txt<br></blockquote><blockquote type="cite">and that includes all of Scott451's published work, plus our own additions.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The SOC message is on the CAN bus - message ID#100, B1=0x80. There is<br></blockquote><blockquote type="cite">supposedly no difference between the 1.5 and 2.x models for this message.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">To get the charging messages correctly, you will need to set the CARBITS<br></blockquote><blockquote type="cite">feature to a 2008 model roadster. An SMS command:<br></blockquote><blockquote type="cite">FEATURE 15 1<br></blockquote><blockquote type="cite">should enable bit#1 of the carbits, and permanently record this as a 2008<br></blockquote><blockquote type="cite">roadster.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The "Not charging" just means the charge port door is closed (or bit#2 of B2<br></blockquote><blockquote type="cite">on id#100 B1=0x96 is zero). The SOC and Ideal range being zero is similar zero<br></blockquote><blockquote type="cite">(default) values.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">So, either none of these messages are getting from the CAN bus to the module,<br></blockquote><blockquote type="cite">or the messages are completely different on a 1.5 car. I suspect the former.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Can you try:<br></blockquote><blockquote type="cite">a) A "GPS" SMS command - do you get a location in Wales (default), or the true<br></blockquote><blockquote type="cite">location?<br></blockquote><blockquote type="cite">b) Open the charge port door, and repeat the "STAT" command - do you get a<br></blockquote><blockquote type="cite">charging reply?<br></blockquote><blockquote type="cite">and let us know the result?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The problem could also just be a faulty module (we had some factory soldering<br></blockquote><blockquote type="cite">issues with early modules), so please verify the soldering looks good, and<br></blockquote><blockquote type="cite">trace continuity test, particularly on the CAN bus side? Or, a loose<br></blockquote><blockquote type="cite">connection on the CAN bus cables (two pins CAN-L and CAN-H), so can you check<br></blockquote><blockquote type="cite">that with a continuity tester? If you have the opportunity, you could try it<br></blockquote><blockquote type="cite">in a 2.x roadster.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">There is a wiring schematic at:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><a href="https://github.com/markwj/Open-Vehicle-Monitoring-System/raw/master/vehicle/Ca">https://github.com/markwj/Open-Vehicle-Monitoring-System/raw/master/vehicle/Ca</a><br></blockquote><blockquote type="cite">r%20Module/OVMS_V5a.png<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">My guess for this problem is a loose/broken cable on the CAN bus side -<br></blockquote><blockquote type="cite">somewhere between the DIAG connector and the telco-style jacks connecting to<br></blockquote><blockquote type="cite">the PIC motherboard.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">It would be really helpful if you could help us test this and iron out any<br></blockquote><blockquote type="cite">wrinkles for the 1.5 cars. We've had some enquiries from 1.5 end-users, but<br></blockquote><blockquote type="cite">have told them to hold-off for the moment until we can verify things work in a<br></blockquote><blockquote type="cite">1.5 car.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Regards, Mark.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On 6 Mar 2012, at 8:39 AM, Tom Saxton wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">I just got the OVMS board plugged into our v1.5 Roadster. I haven't jumped<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">through the hoops to get a data plan on my SIM card yet, so I'm just using<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">SMS.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I registered my phone and changed my password. Those commands worked as<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">expected. I then did a STAT and got back:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> Not charging<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> Ideal Range: 0 Km<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> SOC 0%<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">It's true that it's not charging, but the car is actually at 96% and 185<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">ideal miles.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">What should I do next?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> Tom<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">OvmsDev mailing list<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><br><br></div></blockquote></div><br></div></div></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>OvmsDev mailing list</span><br><span><a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a></span><br><span><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a></span><br></div></blockquote></div></blockquote></div><br></div></body></html>