[Ovmsdev] Open API

Mon Feb 1 13:18:37 HKT 2016

Robert,

Interested, but really no idea what you are trying to do here.

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.

Too negative?

Or am I missing something?

Perhaps you can explain in more details what you are building?

Regards, Mark.

P.S. If a standard existed, OVMS would adhere to it. We only rolled our own because there was nothing out there already.

> On 1 Feb 2016, at 12:33 PM, Robert Sharpe <robert.sharpe at evergreen-consulting.co.uk> wrote:
> 
> Hi,
> 
> Just to let everyone know that I have created an Open Vehicle Protocol LinkedIn group <https://www.linkedin.com/groups/8469823> that everyone is welcome to join.
> 
> The OVP and group gives an opportunity to
> contribute to making OVMS compliant with an OVP
> develop and sell interfaces to manufactures to make them compliant with the minimum of effort
> contribute to making OVP happen
> Look forward to seeing some of you on the above group
> 
> Regards,
> Rob
> 
> 
> ---- On Mon, 18 Jan 2016 01:39:00 +0000 Mark Webb-Johnson<mark at webb-johnson.net> wrote ---- 
> Robert,
> 
> The links Michael provided below are the best from OVMS side.
> 
> 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).
> 
> Regards, Mark.
> 
>> On 18 Jan 2016, at 1:38 AM, Michael Balzer <dexter at expeedo.de <mailto:dexter at expeedo.de>> wrote:
>> 
>> Hi Robert,
>> 
>> you can connect to an OVMS server through the client protocol (TCP) or via HTTP.
>> 
>> See
>> - https://github.com/openvehicles/Open-Vehicle-Monitoring-System/blob/master/docs/OVMS_Protocol.pdf <https://github.com/openvehicles/Open-Vehicle-Monitoring-System/blob/master/docs/OVMS_Protocol.pdf>
>> and the perl clients for details and examples. The protocol supports telemetry, command execution, push notifications and more.
>> 
>> The HTTP API lacks documentation, it supports telemetry up to now and it's been described here:
>> - http://lists.teslaclub.hk/pipermail/ovmsdev/2013-February/000919.html <http://lists.teslaclub.hk/pipermail/ovmsdev/2013-February/000919.html>
>> - http://lists.teslaclub.hk/pipermail/ovmsdev/2013-March/000958.html <http://lists.teslaclub.hk/pipermail/ovmsdev/2013-March/000958.html>
>> 
>> ...and there's a simple JS client implementation over here:
>> - http://www.openvehicles.com/simpleclient.htm <http://www.openvehicles.com/simpleclient.htm>
>> 
>> To my knowledge there is no cooperation with any car manufacturer.
>> I would be surprised if car manufacturers actually show interest in supporting unified or open APIs.
>> 
>> Regards,
>> Michael
>> 
>> 
>> Am 17.01.2016 um 14:20 schrieb Robert Sharpe:
>> 40b9287899.2914718679153564571 at evergreen-consulting.co.uk" type="cite" class="">
>> Hi,
>> 
>> As always, after sending the email found some of what was required turned up.
>> 
>> But I am still looking for the OVMS server API specification.
>> 
>> For your information
>> General APIs - https://developer.ibm.com/apimanagement/2014/10/31/whats-driving-apis-automotive <https://developer.ibm.com/apimanagement/2014/10/31/whats-driving-apis-automotive>
>> Tesla - http://docs.timdorr.apiary.io/ <http://docs.timdorr.apiary.io/>
>> Nissan CarWings - www.npmjs.com/package/carwingsjs <http://www.npmjs.com/package/carwingsjs>
>> GM - https://developer.gm.com/documentation <https://developer.gm.com/documentation>
>> BMW i3 - https://shkspr.mobi/blog/2015/11/reverse-engineering-the-bmw-i3-api <https://shkspr.mobi/blog/2015/11/reverse-engineering-the-bmw-i3-api>
>> 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?
>> 
>> Look forward to hearing any plans.
>> Regards,
>> Robert Sharpe (Managing Director)
>> 07711 252971
>> 
>> <Mail Attachment.gif> <http://www.linkedin.com/in/arsharpe> <Mail Attachment.gif> <http://www.twitter.com/EgcTechnical> <Mail Attachment.gif> <https://www.facebook.com/EvergreenConsultingLtd> <Mail Attachment.gif> <http://www.evergreen-consulting.co.uk/staff/skype/rsharpe.html> <Mail Attachment.gif> <http://www.evergreen-consulting.co.uk/staff/calendars/rsharpe.html?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
>> <Mail Attachment.png>  <http://www.evergreen-consulting.co.uk/?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
>> Your Plugged-in Partner
>> 
>> Evergreen Consulting is the trading name of Sharpe Consultants Ltd
>> 
>> 
>> 
>> ---- On Sat, 16 Jan 2016 16:25:35 +0000 <robert.sharpe at evergreen-consulting.co.uk> <mailto:robert.sharpe at evergreen-consulting.co.uk> wrote ---- 
>> Hi,
>> 
>> I am working on an EV route planning and navigation system that will need real time remote access to vehicle data.
>> 
>> 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.
>> 
>> Can anyone tell me
>> the location of a OVMS API definition?
>> any other standard APIs (similar to Open Charge Point Protocol but for cars)
>> Thanks in advance.
>> Regards,
>> Robert Sharpe (Managing Director)
>> 07711 252971
>> 
>> <Mail Attachment.gif> <http://www.linkedin.com/in/arsharpe> <Mail Attachment.gif> <http://www.twitter.com/EgcTechnical> <Mail Attachment.gif> <https://www.facebook.com/EvergreenConsultingLtd> <Mail Attachment.gif> <http://www.evergreen-consulting.co.uk/staff/skype/rsharpe.html> <Mail Attachment.gif> <http://www.evergreen-consulting.co.uk/staff/calendars/rsharpe.html?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
>> <Mail Attachment.png>  <http://www.evergreen-consulting.co.uk/?utm_campaign=General&utm_source=EmailFooter&utm_medium=Email>
>> Your Plugged-in Partner
>> 
>> Evergreen Consulting is the trading name of Sharpe Consultants Ltd
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________ OvmsDev mailing list OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev> 
>> 
>> --  Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26 
>> <dexter.vcf>_______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at lists.teslaclub.hk>
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
> 
> _______________________________________________ 
> OvmsDev mailing list 
> OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at lists.teslaclub.hk> 
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev> 
> 
> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20160201/b14fb839/attachment.htm>