<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;'>Hi Mark,<div><div><br></div><div>Thanks for your reply and questions, they have helped to steer the OVP project.</div><div><br></div><div>I have answered some of your general questions on the forum at</div><div><ul><li><a href="https://www.linkedin.com/groups/8469823/8469823-6099836756406923264" target="_blank">See more about the vision for the group</a></li><li><a href="https://www.linkedin.com/groups/8469823/8469823-6099832442359738371" target="_blank">How do you think OVP would be implemented?</a></li></ul></div><div>One example of how it could work is to consider how our own EV route planning app and OVMS might interact. As you might expect initially the vehicles supported will be those that are most common. If our route planner communicates to the cars via OVP, then someone with a rare car could make an software adapter to convert from OVP to say OVMS and use the route planner with OVMS. That would benefit both products.</div><div><div><br></div><div>As regards how OVMS could support OVP, there are a couple of options that come to mind</div><div><ul><li>someone develops an OVMS<->OVP adapter or</li><li>OVMS supports OVP in addition to its current API directly</li></ul></div><div><div><div>In reality OVMS is also driving a standard by a direct need. Hence, I was pleased that you joined the LinkedIn group. Between us and other visionary people I am sure we can develop a defacto standard that will eventually be widely used and benefit everyone.</div><div><br></div></div></div><div>I don't think lack of manufacturer involvement in the OVP standard will make things any thing more difficult than it is now. For example, currently</div><div><br></div><div> [third party app communicates with and used manufacturer's API] ----> [specific manufacture's server]</div><div><br></div><div>but using OVP</div><div><br></div><div> [third party app communicates with generic OVP server] ----> [OVP server which handles the communication with] --> [specific manufacture's server]</div><div><br></div><div>So how could this cause problems?</div><div><div><br></div></div></div><div>Thanks again for your input. Hopefully this has clarified things a little. Although I started OVP it is better if it grows as a community. It would therefore be great to hear your suggestions on the linkedin group and look forward to hearing your thoughts.</div><div><br></div><div><div><div id="1">Regards,</div><div id="1">Rob</div><div id="1"><br></div><div id="1">---- On Mon, 01 Feb 2016 05:18:37 +0000 <b>Mark Webb-Johnson <<a href="mailto:mark@openvehicles.com" target="_blank">mark@openvehicles.com</a>></b> wrote ---- <br></div><blockquote style="border-left: 1px solid #0000ff;padding-left: 6px; margin: 0 0 0 5px"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Robert,<div><br></div><div>Interested, but really no idea what you are trying to do here.</div><div><br></div><div>It would be wonderful if there was a standardised vehicle protocol, and all the manufacturers complied to that (both on the vehicle and App sides), but I just don’t see it happening. They seem to love their walled gardens, and hardly ever allow anyone in. Those who do sneak over the walls run the risk of being thrown out at any time. Hoping that they all contribute to a common park is great, but unlikely to happen.</div><div><br></div><div>Too negative?</div><div><br></div><div>Or am I missing something?</div><div><br></div><div>Perhaps you can explain in more details what you are building?</div><div><br></div><div>Regards, Mark.</div><div><br></div><div>P.S. If a standard existed, OVMS would adhere to it. We only rolled our own because there was nothing out there already.</div><div><br><div><blockquote type="cite"><div>On 1 Feb 2016, at 12:33 PM, Robert Sharpe <<a href="mailto:robert.sharpe@evergreen-consulting.co.uk" target="_blank">robert.sharpe@evergreen-consulting.co.uk</a>> wrote:</div><br><div><div><div style="font-size:10pt;font-family:verdana,arial,helvetica,sans-serif;"><div><div>Hi,</div><div><br></div><div>Just to let everyone know that I have created an <a href="https://www.linkedin.com/groups/8469823" target="_blank">Open Vehicle Protocol LinkedIn group</a> that everyone is welcome to join.</div><div><br></div><div>The OVP and group gives an opportunity to</div><div><ul><li>contribute to making OVMS compliant with an OVP</li><li>develop and sell interfaces to manufactures to make them compliant with the minimum of effort</li><li>contribute to making OVP happen</li></ul></div><div>Look forward to seeing some of you on the above group</div><div><br></div><div>Regards,</div><div>Rob</div><div><br></div><div><br></div><div>---- On Mon, 18 Jan 2016 01:39:00 +0000 <b>Mark Webb-Johnson<<a href="mailto:mark@webb-johnson.net" target="_blank">mark@webb-johnson.net</a>></b> wrote ---- <br></div><blockquote style="border-left: 1px solid #0000ff; padding-left: 6px; margin:0 0 0 5px"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Robert,<div><br></div><div>The links Michael provided below are the best from OVMS side.</div><div><br></div><div>Each vehicle manufacturer has their own standard, and most are closed (only opened by reverse engineering, and at the whim of the manufacturers who could shut it down whenever they like).</div><div><br></div><div>Regards, Mark.</div><div><br><div><blockquote type="cite"><div>On 18 Jan 2016, at 1:38 AM, Michael Balzer <<a href="mailto:dexter@expeedo.de" target="_blank">dexter@expeedo.de</a>> wrote:</div><br><div> <div text="#000000" bgcolor="#FFFFFF"> Hi Robert,<br> <br> you can connect to an OVMS server through the client protocol (TCP) or via HTTP.<br> <br> See<br> - <a href="https://github.com/openvehicles/Open-Vehicle-Monitoring-System/blob/master/docs/OVMS_Protocol.pdf" target="_blank">https://github.com/openvehicles/Open-Vehicle-Monitoring-System/blob/master/docs/OVMS_Protocol.pdf</a><br> and the perl clients for details and examples. The protocol supports telemetry, command execution, push notifications and more.<br> <br> The HTTP API lacks documentation, it supports telemetry up to now and it's been described here:<br> - <a href="http://lists.teslaclub.hk/pipermail/ovmsdev/2013-February/000919.html" target="_blank">http://lists.teslaclub.hk/pipermail/ovmsdev/2013-February/000919.html</a><br> - <a href="http://lists.teslaclub.hk/pipermail/ovmsdev/2013-March/000958.html" target="_blank">http://lists.teslaclub.hk/pipermail/ovmsdev/2013-March/000958.html</a><br> <br> ...and there's a simple JS client implementation over here:<br> - <a href="http://www.openvehicles.com/simpleclient.htm" target="_blank">http://www.openvehicles.com/simpleclient.htm</a><br> <br> To my knowledge there is no cooperation with any car manufacturer.<br> I would be surprised if car manufacturers actually show interest in supporting unified or open APIs.<br> <br> Regards,<br> Michael<br> <br> <br> <div>Am 17.01.2016 um 14:20 schrieb Robert Sharpe:<br> </div> <blockquote cite="mid:1524fbe93d2.11dcd<a ><a>40b9287899.2914718679153564571@evergreen-consulting.co.uk" type="cite" class="" >="" <div="" style="font-size:10pt;font-family:verdana,arial,helvetica,sans-serif;">Hi, <div><br> </div> <div>As always, after sending the email found some of what was required turned up.</div> <div><br> </div> <div>But I am still looking for the OVMS server API specification.</div> <div><br> </div> <div>For your information</div> <div> <ul> <li>General APIs - <a href="https://developer.ibm.com/apimanagement/2014/10/31/whats-driving-apis-automotive" target="_blank">https://developer.ibm.com/apimanagement/2014/10/31/whats-driving-apis-automotive</a></li> <li>Tesla - <a href="http://docs.timdorr.apiary.io/" target="_blank">http://docs.timdorr.apiary.io/</a></li> <li>Nissan CarWings - <a href="http://www.npmjs.com/package/carwingsjs" target="_blank">www.npmjs.com/package/carwingsjs</a></li> <li>GM - <a href="https://developer.gm.com/documentation" target="_blank">https://developer.gm.com/documentation</a></li> <li>BMW i3 - <a href="https://shkspr.mobi/blog/2015/11/reverse-engineering-the-bmw-i3-api" target="_blank">https://shkspr.mobi/blog/2015/11/reverse-engineering-the-bmw-i3-api</a></li> </ul> <div>Because we need to access multiple car types, my vision is to find/develop a unified open API. Is OVMS working with anyone along this line?</div> <div><br> </div> <div>Look forward to hearing any plans.</div> <div> <div style="font-family: verdana, arial, helvetica, sans-serif;"> <div style="font-family: verdana, arial, helvetica, sans-serif; background-color: rgb(255, 255, 255);"><p style="font-size: 13.63636302947998px;"><font face="Calibri, Verdana, Arial, sans-serif"><font size="3">Regards,<br> Robert Sharpe (Managing Director)<br> 07711 252971</font></font></p><p style="font-size: 13.63636302947998px;"><a href="http://www.linkedin.com/in/arsharpe" target="_blank"><span><Mail Attachment.gif></span></a> <a href="http://www.twitter.com/EgcTechnical" target="_blank"><span><Mail Attachment.gif></span></a> <a href="https://www.facebook.com/EvergreenConsultingLtd" target="_blank"><span><Mail Attachment.gif></span></a> <a href="http://www.evergreen-consulting.co.uk/staff/skype/rsharpe.html" target="_blank"><span><Mail Attachment.gif></span></a> <a href="http://www.evergreen-consulting.co.uk/staff/calendars/rsharpe.html?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email" target="_blank"><span><Mail Attachment.gif></span></a></p><p style="font-size: 13.63636302947998px;"><a href="http://www.evergreen-consulting.co.uk/?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email" target="_blank"><span><Mail Attachment.png></span> </a></p><p style="font-size: 13.63636302947998px;"><font size="5" face="Calibri, Verdana, Arial, sans-serif"><i>Your Plugged-in Partner</i></font></p><p style="font-size: 13.63636302947998px;"><font face="Calibri, Verdana, Arial, sans-serif"><font size="2">Evergreen Consulting is the trading name of Sharpe Consultants Ltd</font></font></p> </div> </div> <span style="top: 326px; left: 206px; cursor: e-resize;"></span><span style="top: 326px; left: 6px; cursor: w-resize;"></span><span style="top: 278px; left: 108px; cursor: n-resize;"></span><span style="top: 370px; left: 108px; cursor: s-resize;"></span></div> <br> <div> <div><br> ---- On Sat, 16 Jan 2016 16:25:35 +0000 <b><a href="mailto:robert.sharpe@evergreen-consulting.co.uk" target="_blank"><robert.sharpe@evergreen-consulting.co.uk></a></b> wrote ---- <br> </div> <blockquote style="border-left: 1px solid #0000ff; padding-left: 6px; margin:0 0 0 5px"> <div> <div style="font-size:10pt;font-family:verdana,arial,helvetica,sans-serif;">Hi, <div><br> </div> <div>I am working on an EV route planning and navigation system that will need real time remote access to vehicle data.</div> <div><br> </div> <div>The most powerful approach would be to access all the different supported vehicles through a standard cloud base open api. My initial Googling has not shown an existing API but I know OVMS has a server.</div> <div><br> </div> <div>Can anyone tell me</div> <div> <ul> <li>the location of a OVMS API definition?</li> <li>any other standard APIs (similar to Open Charge Point Protocol but for cars)</li> </ul> </div> <div>Thanks in advance.</div> <div> <div> <div style="font-family: verdana, arial, helvetica, sans-serif;"> <div style="font-family: verdana, arial, helvetica, sans-serif; background-color: rgb(255, 255, 255);"><p style="font-size: 13.63636302947998px;"><font face="Calibri, Verdana, Arial, sans-serif"><font size="3">Regards,<br> Robert Sharpe (Managing Director)<br> 07711 252971</font></font></p><p style="font-size: 13.63636302947998px;"><a href="http://www.linkedin.com/in/arsharpe" target="_blank"><span><Mail Attachment.gif></span></a> <a href="http://www.twitter.com/EgcTechnical" target="_blank"><span><Mail Attachment.gif></span></a> <a href="https://www.facebook.com/EvergreenConsultingLtd" target="_blank"><span><Mail Attachment.gif></span></a> <a href="http://www.evergreen-consulting.co.uk/staff/skype/rsharpe.html" target="_blank"><span><Mail Attachment.gif></span></a> <a href="http://www.evergreen-consulting.co.uk/staff/calendars/rsharpe.html?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email" target="_blank"><span><Mail Attachment.gif></span></a></p><p style="font-size: 13.63636302947998px;"><a href="http://www.evergreen-consulting.co.uk/?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email" target="_blank"><span><Mail Attachment.png></span> </a></p><p style="font-size: 13.63636302947998px;"><font size="5" face="Calibri, Verdana, Arial, sans-serif"><i>Your Plugged-in Partner</i></font></p><p style="font-size: 13.63636302947998px;"><font face="Calibri, Verdana, Arial, sans-serif"><font size="2">Evergreen Consulting is the trading name of Sharpe Consultants Ltd</font></font></p> </div> </div> <span style="top: 326px; left: 206px; cursor: e-resize;"></span><span style="top: 326px; left: 6px; cursor: w-resize;"></span><span style="top: 278px; left: 108px; cursor: n-resize;"></span><span style="top: 370px; left: 108px; cursor: s-resize;"></span></div> </div> </div> </div> </blockquote> <br> </div> <br> </div> </blockquote></div> <br> <fieldset></fieldset> <br> <pre wrap="">_______________________________________________ OvmsDev mailing list <a href="mailto:OvmsDev@lists.teslaclub.hk" target="_blank">OvmsDev@lists.teslaclub.hk</a> <a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" target="_blank">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a> </pre> </div></blockquote> <br> <pre cols="72">-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 </pre> </div> <span><dexter.vcf></span>_______________________________________________<br>OvmsDev mailing list<br><a href="mailto:OvmsDev@lists.teslaclub.hk" target="_blank">OvmsDev@lists.teslaclub.hk</a><br><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" target="_blank">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br></div></div></blockquote></div><br></div>_______________________________________________ <br>OvmsDev mailing list <br><a href="mailto:OvmsDev@lists.teslaclub.hk" target="_blank">OvmsDev@lists.teslaclub.hk</a> <br><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" target="_blank">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a> <br></div></div></blockquote><br></div><br></div></div>_______________________________________________<br>OvmsDev mailing list<br><a href="mailto:OvmsDev@lists.teslaclub.hk" target="_blank">OvmsDev@lists.teslaclub.hk</a><br><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" target="_blank">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a><br></blockquote></div></div><br></div>_______________________________________________ <br>OvmsDev mailing list <br><a href="mailto:OvmsDev@lists.teslaclub.hk" target="_blank">OvmsDev@lists.teslaclub.hk</a> <br><a href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev" target="_blank">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a> <br><br><br></div></body></html>