<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Tom,<div><br></div><div>For firmware v2.x builds, there are now just 4:</div><div><br></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><pre style="margin: 0px; padding: 0px; border: 0px; font-size: 12px; font-family: Consolas, 'Liberation Mono', Courier, monospace; color: rgb(51, 51, 51); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 16px; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div class="line" id="LC6" style="margin: 0px; padding: 0px 0px 0px 10px; border: 0px; ">V1_experimental.hex V1 Hardware Module, experimental firmware</div><div class="line" id="LC7" style="margin: 0px; padding: 0px 0px 0px 10px; border: 0px; ">V1_production.hex V1 Hardware Module, production firmware</div><div class="line" id="LC8" style="margin: 0px; padding: 0px 0px 0px 10px; border: 0px; ">V2_experimental.hex V2 Hardware Module, experimental firmware</div><div class="line" id="LC9" style="margin: 0px; padding: 0px 0px 0px 10px; border: 0px; ">V2_production.hex V2 Hardware Module, production firmware</div></pre></div></blockquote><div><br></div><div>A single firmware supports multiple vehicle types (selectable at run-time based on parameter #14 (or the fourth argument to the "MODULE" SMS command).</div><div><br></div><div>It may be worth pointing out the following on the update page:</div><div><br></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>For Tesla Roadster owners, once you upgrade firmware from v1 to v2, you will need to either:</div></div></blockquote><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div> (a) SMS "MODULE" command again to include the fourth parameter vehicle type "TR", or</div></div></blockquote><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div> (b) use the iOS App to set parameter #14 to "TR" (you can even do this in the App _before_ you upgrade).</div></div></blockquote><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>You will require this for the CAN bus stuff to work. We have updated the Tesla Roadster user guide to reflect this new parameter.</div></div></blockquote></div></blockquote><div><br></div><div>Regards, Mark.</div><div><br><div><div>On 17 Jan, 2013, at 11:29 AM, Tom Saxton wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>The idea of permanent links sounds great, but now I'm confused.<br><br>I just flashed my V1 Roadster module, and it comes up as version 1.5.1. Now<br>that I look more carefully, I see that all of the .hex files I grabbed from<br>my updated OVMS directory are dated 10/21/2012. For example,<br><br>vehicle/OVMS.X/dist/RT_V2_Experimental<br><br>Looking at the links in the tagged v2.2.2 folder, I just see four builds<br>(V1,V2)x(Experimental,Production). I expected to see builds for each<br>vehicle.<br><br>Or is V1 just for the Roadster and the V2 build dynamically figures out<br>which vehicle it's on?<br><br> Tom<br><br>on 1/16/13 5:39 PM, Mark Webb-Johnson wrote:<br><br><blockquote type="cite">I think I may have a solution for this (going forward).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">If we use the git 'tags' feature, to tag each released firmware build, github<br></blockquote><blockquote type="cite">will allow us to publish the tree at that time. For example, see:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><a href="https://github.com/markwj/Open-Vehicle-Monitoring-System/tree/v2.2.2/vehicle/f">https://github.com/markwj/Open-Vehicle-Monitoring-System/tree/v2.2.2/vehicle/f</a><br></blockquote><blockquote type="cite">irmware<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">And an example link to the v2.2.2 V2 production firmware is:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><a href="https://github.com/markwj/Open-Vehicle-Monitoring-System/raw/v2.2.2/vehicle/fi">https://github.com/markwj/Open-Vehicle-Monitoring-System/raw/v2.2.2/vehicle/fi</a><br></blockquote><blockquote type="cite">rmware/V2_production.hex<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">That link is quite clean and should be stable going forward. It will just take<br></blockquote><blockquote type="cite">some discipline to set things up correctly during a release:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Build all firmware<br></blockquote><blockquote type="cite">Copy the .hex files to the firmware folder<br></blockquote><blockquote type="cite">Update the change log<br></blockquote><blockquote type="cite">Commit<br></blockquote><blockquote type="cite">Tag the commit<br></blockquote><blockquote type="cite">push (--tags) to github<br></blockquote><blockquote type="cite">Announce the new version<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">What do people think? Sensible?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Regards, Mark.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On 15 Jan, 2013, at 8:38 AM, Mark Webb-Johnson wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I think this approach is ok, and given github's approach probably the best<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">way.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I really wish that github had a 'files' repository (like sourceforge) that we<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">could put fixed (not revision controlled) files. Release, not development,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">files. I tried to create symlinks (in the 'firmware' folder), but they don't<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">work (the symlink text file is just downloaded, not the thing it linked to),<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">and anyway that doesn't give us history.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I've got a git guru on staff here at work - I'll ask him for his advise.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Regards, Mark.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">On 15 Jan, 2013, at 5:49 AM, Tom Saxton wrote:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">That directory structure changes about as often as there are new official<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">releases, as you can tell by all of the orphan build directories. Linking<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">straight into the repository won't let me pick up new vehicles, and will<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">break when vehicles go from "experimental" to "production" status.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">The release notes aren't in the repository (AFAIK), so I have to enter those<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">links manually as well.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Given that I have to manually update the page, I figure it's more reliable<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">to ferret out the right versions for each vehicle and copy them to my site.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">This way, my page keeps working even if the repository changes, which means<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">less work maintaining the page between releases (which is currently zero<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">effort).<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Anyone who's really into getting the latest builds can just grab the files<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">from the repository. My page is to support those who don't care enough to<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">climb that learning curve.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> Tom<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">on 1/14/13 1:23 PM, Michael Balzer wrote:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Thanks, Tom!<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Hm... to optimize the rollout, have you tried to link directly to the<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">repository files?<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">The links in vehicle/firmware don't work, but using the github file<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">browser I can get for example...<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/master/vehicle">https://raw.github.com/markwj/Open-Vehicle-Monitoring-System/master/vehicle</a><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">/OV<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">MS.X/dist/V2_Experimental/production/OVMS.X.production.hex<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">I'm new to github, but that URL scheme looks like being designed as a<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">permanent link.<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Regards,<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Michael<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Am 14.01.2013 21:13, schrieb Tom Saxton:<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">The firmware update guide page now has version 2.2.2 builds up.<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="http://www.idleloop.com/tesla/ovms/">http://www.idleloop.com/tesla/ovms/</a><br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> Tom<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">OvmsDev mailing list<br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a><br></blockquote></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><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></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">OvmsDev mailing list<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a><br></blockquote></blockquote></blockquote><blockquote type="cite"><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><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><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite">OvmsDev mailing list<br></blockquote><blockquote type="cite"><a href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a><br></blockquote><blockquote type="cite"><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><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></div></blockquote></div><br></div></body></html>