February 2016 - OvmsDev - Open Vehicles

OVMS logo
by Mark Webb-Johnson 06 Jun '17

06 Jun '17

We need to change the OVMS logo, to better reflect the vehicle independence. The existing logo is too much Tesla. Felix has kindly prepared a couple of options for us, attached below. My preference is for the one with the car outline (even though it retains a hint of Tesla), as it emphasizes the vehicle comms aspect. This is quite urgent, as the Teslive people are pushing for artwork. What do you guys/gals think? Regards, Mark

8 14

OVMS v3
by Mastro Gippo 19 May '17

19 May '17

Hi all, I'd like to resurrect an old conversation. As we know, the current PIC is quickly running out of resources and maybe it's time to switch to a better platform. Two CAN buses are now desirable too. A microSD slot and direct USB connectivity wouldn't hurt either. I will probably have to design a similar hardware for myself, so I'd like to contribute to the OVMS by sharing the HW platform if you want; no strings attached of course, if you decide that there's no need for the upgrade, I'll keep on working on my project by myself! :) That said, I'd like to throw a few ideas to the table. - MCU: I'd like to use an STM32 micro. They seem to be emerging as the standard choice for diy ARM projects, and this offers a few interesting opportunities: -Programming it in c/c++ with the manufacturer CMSIS standard libraries (boring) -Programming it with the mbed.org SDK. Unfortunately no dev boards are available with dual CAN bus, but it will be easy to move to the correct micro of the same series once most of the software is ironed out on a dev board like the https://mbed.org/platforms/ST-Nucleo-F302R8/ -Programming it with an RTOS. NuttX would be my choice, as it's the one used in the Ardupilot Pixhawk platform, and I'd like to learn it. This would mean a steeper starting curve, but a lot of flexibility later as a lot of stuff is handled on the OS level (network stacks, SD card & filesystems, multitasking...). FreeRTOS is a nice option too. I'd like to use the STM32F405RG as it's the most similar to the one found on the Pixhawk, but of course I'm biased because of that, and that micro is quite overkill for the task. We can of course use a lower specced part and lose some RTOS fuctionality as long as it has 2 CAN buses. - MODEM: I have no experience in this field; is the SIM908 still a good choice or does anyone think that we should try new platforms? I like this, but I don't know if the price puts it out of budget: http://www.telit.com/telit/Pulsar/en_US.Store.display.1001./ge864-gps On the bright side, it can be programmed in python, so we can offload some of the work to the modem. This *could* allow us to free some space on the PIC, and keep that platform without changing MCU.. - Enclosure: I think that, even with the new MCU, we can still fit the old enclosure. Is that ok, or should we think about a more automotive-friendly one? Maybe waterproof for the twizy? And that's it. I think that the core SW developers should voice their opinion, as there is a lot of work to be done on that front. A huge problem will be keeping backwards compatibility to add features for the v2 users, so we should discuss about this too. Regards MG

18 70

Re: [Ovmsdev] OvmsDev Digest, Vol 49, Issue 25
by Thor 25 Feb '16

25 Feb '16

nice! Sorry can't help with the developing, since it's not my field of programming. But have you considered setting up a donation for leaf development? there has been a demand for leaf-alternative a long time, and the devs here that worked on it have left. One of the devs Jermey has no leaf no more, so no pushing for the leaf. It's very important that the leaf development now pushes forward to get somewhere and not halt before we get there. How will your code be with the new hardware that is comming? Anyways. I did a poll last year on how many that where interested in changing to a opensource alternative for carwings/nissan connect. and like 30-40 said yes. I estimate that atleast 60 leafs are interested in norway. ps: I think the number for opensource alternative might be even higher now after the Nissan disaster: http://www.troyhunt.com/2016/02/controlling-vehicle-features-of-nissan.html… I tested the security hole yesterday, and it was wide open. today it's partialy closed. look at the response time before nissan acted on it. it's a disaster. On 21 February 2016 at 05:00, <ovmsdev-request(a)lists.teslaclub.hk> wrote: > Send OvmsDev mailing list submissions to > ovmsdev(a)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(a)lists.teslaclub.hk > > You can reach the person managing the list at > ovmsdev-owner(a)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 Remote Climate Control (Tom Parker) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 21 Feb 2016 12:16:35 +1300 > From: Tom Parker <tom(a)carrott.org> > Subject: [Ovmsdev] Nissan Leaf Remote Climate Control > To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > Message-ID: <56C8F3D3.2090406(a)carrott.org> > Content-Type: text/plain; charset=utf-8; format=flowed > > I got remote climate control on & off working, but only during charge. > I've abused the alert and homelink commands for now: > > > https://carrott.org/git/Open-Vehicle-Monitoring-System.git/commitdiff/84a65… > > I can't promise I won't force-push into this branch until it's ready for > merging, so if you are from the future you may need to look at the > branch > > https://carrott.org/git/Open-Vehicle-Monitoring-System.git/shortlog/refs/he… > > > Tested on my 2012 Gen 1 JDM Leaf with Carwings (Apparently the TCU and > hence Carwings doesn't work in New Zealand due to incompatible cell > network). > > Next is to investigate the wakeup logic line between the TCU and VCU. > I've got > http://docslide.us/documents/nissan-leaf-2011-2012-ev-control-system.html > which > describes two EV System Activation Request Signal connections (on page > 88), both on the VCU E63 connector. Pin 96 is from the charger (on page > 84) and pin 84 is from the TCU (on page 85). > > I'm guessing I can observe how the charger wakes up the VCU and add some > GPIO output hardware to the OVMS do the same thing to on the TCU line. > > Remote charging will probably work the same way, but I can't test it > since the only way I can currently get the car to pay attention to these > messages is for it to be charging already. > > > ------------------------------ > > _______________________________________________ > OvmsDev mailing list > OvmsDev(a)lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > > End of OvmsDev Digest, Vol 49, Issue 25 > *************************************** >

2 1

Something new
by Mark Webb-Johnson 24 Feb '16

24 Feb '16

Something is different...

3 3

OVMS v2 stock / OVMS v3
by Mark Webb-Johnson 22 Feb '16

22 Feb '16

At the current rate, the batch we have of OVMS v2 modules will run out sometime in the next two months. Given the imminent shutdown of AT&T’s 2G network in USA, global re-allocation of 2G frequency bands, and the difficulties we are having obtaining the discontinued SIM908, it is decision time. Option #1: Re-order a large batch now, enough to last us into the new year, but with the risk that I’ll be personally stuck with them. Option #2: Just let the v2 modules run out, and move on with the plans for v3. Development on v2 is stagnating. Partly because the platform already does what we need it to do, and partly because we’re hitting the limits (no external connectivity other than GPRS, single CAN bus, no storage, limited RAM, flash, etc). The v3 plans have been on hold for some time, pending MBED OS release (first beta due this month) and the imminent release of hybrid processors such as that used in the UDOO Neo (due in September). We know what we want, but it is just too hard to pick a long-term platform when everything is on the cusp of changing. I really want a v3 module. Something with lots of RAM and Flash, wifi, bluetooth and cellular connectivity, multiple CAN bus support, and a rich development platform. Something we can all use as a platform for reverse engineering as well as end-user connectivity. I’ll do everything I can to make this a reality. Just not today. Too much is changing and we need to wait for things to stabilise. So, my gut feeling is to choose option #2. 2G GPRS is slowing dying, and building more on that platform just seems to be the wrong decision. This may leave us with several months of no platform stock, but I would rather people waited than spend $100 on something that is going to be obsolete/outdated. Kind of like buying an iPhone in August ;-) I don’t want to be stuck with the stock, and I don’t want people to buy a v2, only to have v3 come out a week later. Even if we started now, which we can’t, an optimistic schedule for the first end-user v3 units would be early 2016. So, tough decisions, but I really think option #2 is best. Bottom line is if you need v2 modules, order them now. If you are likely to need a large quantity for any upcoming projects, let me know. The SIM908 modules will be unavailable within the next month or so, and changing to another module is a PITA I don’t want to deal with (especially given the tight RAM and FLASH we have now). Regards, Mark.

14 37

Nissan Leaf Remote Climate Control
by Tom Parker 20 Feb '16

20 Feb '16

I got remote climate control on & off working, but only during charge. I've abused the alert and homelink commands for now: https://carrott.org/git/Open-Vehicle-Monitoring-System.git/commitdiff/84a65… I can't promise I won't force-push into this branch until it's ready for merging, so if you are from the future you may need to look at the branch https://carrott.org/git/Open-Vehicle-Monitoring-System.git/shortlog/refs/he… Tested on my 2012 Gen 1 JDM Leaf with Carwings (Apparently the TCU and hence Carwings doesn't work in New Zealand due to incompatible cell network). Next is to investigate the wakeup logic line between the TCU and VCU. I've got http://docslide.us/documents/nissan-leaf-2011-2012-ev-control-system.html which describes two EV System Activation Request Signal connections (on page 88), both on the VCU E63 connector. Pin 96 is from the charger (on page 84) and pin 84 is from the TCU (on page 85). I'm guessing I can observe how the charger wakes up the VCU and add some GPIO output hardware to the OVMS do the same thing to on the TCU line. Remote charging will probably work the same way, but I can't test it since the only way I can currently get the car to pay attention to these messages is for it to be charging already.

1 0

Re: [Ovmsdev] OvmsDev Digest, Vol 49, Issue 20
by Tom Parker 16 Feb '16

16 Feb '16

Remote climate control is my goal, i'm expecting to have to hook a GPIO to the wake up request wire on the VCM.On 15/02/2016 10:11 PM, Thor <thor918(a)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(a)lists.teslaclub.hk> wrote: >> >> Send OvmsDev mailing list submissions to >> ovmsdev(a)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(a)lists.teslaclub.hk >> >> You can reach the person managing the list at >> ovmsdev-owner(a)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(a)carrott.org> >> Subject: [Ovmsdev] Nissan Leaf + Dev Environment >> To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> >> Message-ID: <56C03E00.5010904(a)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-installe… >> 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(a)lists.teslaclub.hk >> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >> >> >> End of OvmsDev Digest, Vol 49, Issue 20 >> *************************************** > >

1 0

Nissan Leaf + Dev Environment
by Tom Parker 15 Feb '16

15 Feb '16

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-installe… 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).

2 1

Re: [Ovmsdev] OvmsDev Digest, Vol 49, Issue 20
by Thor 15 Feb '16

15 Feb '16

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(a)lists.teslaclub.hk> wrote: > Send OvmsDev mailing list submissions to > ovmsdev(a)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(a)lists.teslaclub.hk > > You can reach the person managing the list at > ovmsdev-owner(a)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(a)carrott.org> > Subject: [Ovmsdev] Nissan Leaf + Dev Environment > To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > Message-ID: <56C03E00.5010904(a)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-installe… > and > // > bitbucket.org/simbuckone/simbuckbaseproject/downloads/mplabc18-v3.40-linux-… > (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(a)lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > > End of OvmsDev Digest, Vol 49, Issue 20 > *************************************** >

2 1

OVMS user in NZ
by Stu 14 Feb '16

14 Feb '16

Hi Tom, I'm also in NZ with a gen 1 japanese import leaf, if you want another tester feel free to give me a shout. I'm happy to help out the cause but little skill in this area, I'm a IT Sys Admin so techie but just not in embedded systems. Stu On 15 February 2016 at 17:00, <ovmsdev-request(a)lists.teslaclub.hk> wrote: > Send OvmsDev mailing list submissions to > ovmsdev(a)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(a)lists.teslaclub.hk > > You can reach the person managing the list at > ovmsdev-owner(a)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(a)carrott.org> > Subject: [Ovmsdev] Nissan Leaf + Dev Environment > To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > Message-ID: <56C03E00.5010904(a)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-installe… > and > // > bitbucket.org/simbuckone/simbuckbaseproject/downloads/mplabc18-v3.40-linux-… > (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(a)lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > > End of OvmsDev Digest, Vol 49, Issue 20 > *************************************** >

1 0