[Ovmsdev] OvmsDev Digest, Vol 49, Issue 20

[Mark Webb-Johnson]

We are already on the EV can bus.

Perhaps someone can try hooking in either the 'wake up' or 'homelink' function call to issue these messages and see if it works?

Regards, Mark

> On 15 Feb 2016, at 5:11 PM, Thor <thor918 at gmail.com> wrote:
> 
> do consider making a solution that turns leaf heater on remotly:
> http://www.mynissanleaf.com/viewtopic.php?p=438109#p438109
> 
>> On 15 February 2016 at 05:00, <ovmsdev-request at lists.teslaclub.hk> wrote:
>> Send OvmsDev mailing list submissions to
>>         ovmsdev at lists.teslaclub.hk
>> 
>> To subscribe or unsubscribe via the World Wide Web, visit
>>         http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>> or, via email, send a message with subject or body 'help' to
>>         ovmsdev-request at lists.teslaclub.hk
>> 
>> You can reach the person managing the list at
>>         ovmsdev-owner at lists.teslaclub.hk
>> 
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of OvmsDev digest..."
>> 
>> 
>> Today's Topics:
>> 
>>    1. Nissan Leaf + Dev Environment (Tom Parker)
>> 
>> 
>> ----------------------------------------------------------------------
>> 
>> Message: 1
>> Date: Sun, 14 Feb 2016 21:42:40 +1300
>> From: Tom Parker <tom at carrott.org>
>> Subject: [Ovmsdev] Nissan Leaf + Dev Environment
>> To: OVMS Developers <ovmsdev at lists.teslaclub.hk>
>> Message-ID: <56C03E00.5010904 at carrott.org>
>> Content-Type: text/plain; charset=utf-8; format=flowed
>> 
>> Hi,
>> 
>> I just got an OVMS for my 2012 Japanese Domestic Manufacture Nissan
>> Leaf. I also ordered the Leaf OBDII cable:
>> https://www.fasttech.com/p/1779000 in my left hand drive car, this cable
>> points towards the driver rather than towards the front of the car, I
>> wonder if it's possible to rotate the socket in the car to make the
>> cable point the other way?
>> 
>> I didn't have any trouble setting up and communicating via the app or
>> SMS on New Zealand's 2degrees cell network.
>> 
>> I programmed the 2.6.5 firmware as recommended by the "Firmware
>> Easy-Install" link on https://www.openvehicles.com/ which turned out to
>> be a mistake. This I think this firmware expects the Car CAN bus but the
>> Leaf OBDII cable connects the EV CAN bus. For a while I thought I had
>> faulty hardware but the soldering looked good and when I took my
>> oscilloscope out to the car and found CAN data entering the PIC
>> microcontroller.
>> 
>> It turns out the 2.6.5 firmware is old and you need a later one to work
>> with the EV CAN bus on the Leaf cable. I'm not entirely sure how I
>> missed that, I just checked out the tag without looking at the other tags.
>> 
>> I installed
>> http://ww1.microchip.com/downloads/en/DeviceDoc/MPLABX-v3.20-linux-installer.tar
>> and
>> //bitbucket.org/simbuckone/simbuckbaseproject/downloads/mplabc18-v3.40-linux-full-installer.run
>> (and verified the md5sum matches
>> http://www.microchip.com/forums/m662617.aspx for whatever that is worth)
>> and have a working development environment and have built and programmed
>> master into my unit and everything seems to be working.
>> 
>> Thank you all for your work on this project, I'll post again about
>> improving the leaf support (I do embedded development in my spare time).
>> The cars intended for the Japanese market have CARWINGS, but the
>> telematics module doesn't work in New Zealand (incompatible cell network
>> apparently).
>> 
>> 
>> ------------------------------
>> 
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
>> 
>> 
>> End of OvmsDev Digest, Vol 49, Issue 20
>> ***************************************
> 
> _______________________________________________
> 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/20160215/04c17c4d/attachment.htm>