[Ovmsdev] OVMS Leaf Support

[Evergreen]

That's great news.

Regards,
Rob

On 16 Oct 2013, at 06:00, Mark Webb-Johnson <mark at webb-johnson.net> wrote:

> 
>> P.S. I'm trying to find a friendly Leaf owner in Hong Kong to co-operate with this. There are 200+ Leafs here, and no carwings coverage at all, but most are in government service and relatively few in private hands.
> 
> I think my fishing expedition on the forums may have come up with a bite. A Hong Kong Leaf owner who is willing to help.
> 
> I'll let you know how it pans out (over the next couple of days), but if I can get access to a local Leaf, getting the basic support working should be much faster.
> 
> Regards, Mark.
> 
> On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson <mark at webb-johnson.net> wrote:
> 
>> Barry,
>> 
>> Thanks for the history. I really think we can get what we need from the single car CAN bus.
>> 
>> I'll extract the relevant sections from the developers guide tonight, and post them here. The first step is to see which of those 'virtual car' pieces of information are available on the car CAN bus, and see if they match-up.
>> 
>> I really would like to see a dump (and dump) of the car CAN bus, as well as a trace from the leaf spy program. The captioned google docs spreadsheet for leaf can bus messages is quite confusing - it would be good to be able to compare that against what is actually seen on the bus.
>> 
>> Regards, Mark.
>> 
>> P.S. I'm trying to find a friendly Leaf owner in Hong Kong to co-operate with this. There are 200+ Leafs here, and no carwings coverage at all, but most are in government service and relatively few in private hands.
>> 
>> On 15 Oct, 2013, at 11:45 am, Barry Gershenfeld <gbarry42 at gmail.com> wrote:
>> 
>>> Early development assumed you had to get the EV info from the EV-CAN buss.  Somewhere during the development of Leaf Spy they kept finding desirable info on the car-CAN buss and so eventually determined that all if could be gotten from the car-CAN.  As a bonus, the ELM dongle no longer has to be modified to read the EV buss.
>>> 
>>> The original reporting efforts started with the "GID" meter, and the early work involved Gary G. building a data recorder as well as a program to analyze the logs.  I'm sure that's precisely what you have in mind as well.  There were downloadable logs--he invited others to install the analyzer and try to find meaningful messages therein.  But as it was early development, they were probably gotten from the EV-CAN.  I don't know if any more recent logs from the car CAN buss are posted.
>>> 
>>> As a matter of fact, I suspect Gary would be happy to have his analyzing program used.  It would be nice output the data into the same format that it uses.  Or at least write a converter.
>>> 
>>> I naturally have some interest, being a LEAF owner and PIC hacker.  I'll see if I can make head or tail of the developer's guide.
>>> 
>>>  * * *
>>> 
>>> On Mon, Oct 14, 2013 at 7:04 PM, Mark Webb-Johnson <mark at webb-johnson.net> wrote:
>>>> Developers guide is here:
>>>> 
>>>> https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OVMS_Development.pdf?raw=true
>>>> 
>>>> I would rather the actual development discussions take place here on this list. A lot of smart people here, with experience getting these vehicle modules working.
>>>> 
>>>> The biggest concern for me is whether we can get everything we need off one CAN bus...
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>> 
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk
>> 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.teslaclub.hk/pipermail/ovmsdev/attachments/20131016/0b28c04f/attachment-0001.html>