- OvmsDev - Open Vehicles

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

OVMS v3 - Microcontroller
by Mark Webb-Johnson 11 Feb '16

11 Feb '16

Well, the new year is here and OVMS v3 is on the front burner now. As you know, I’ve been waiting for the MBED system to settle down and the news is … it hasn’t. Sure, they’ve finally released some open beta code, but only really 1 board supported. No more online compiler. Complicated tools. RTOS worse than the old MBED. And worse is a proprietary closed-source server platform for their Internet-of-things MBED O/S. Luckily, the one board they support is the NXP FRDM-K64F that I love. I’ve tried it, and it sucks. Maybe in a year’s time… I’ve been waiting and waiting for this. Can’t say how disappointed I am with the whole direction of the MBED project and closed development, closed, source approach. Anyway, OVMS v2 is end of life. We can’t get the SIM908 GSM modules any more. Even if we could, 2G really doesn’t have that much longer. There are a lot of M2M devices out there, but the frequency space is just too valuable. Over the next year or two, more and more 2G capable cell towers are going to be turned off. So, time to take the plunge and get on with it. I’m guessing an open source development environment, some free RTOS, and an adapted boot loader to allow us to flash from SC-CARD, USB, or something like that. From an overall system architecture point of view, I think we know what we want. A board with a fast micro controller, lots of ram and flash, several CAN buses, and easy development environment, easy firmware upload for the novice, SD card, USB, ethernet, wifi, bluetooth, and some digital I/O. Then, expansion slots to plug in 3G/4G connectivity and whatever else we want. We’ve now got lots of options on the wifi+bluetooth front. Within the next couple of months, the ESP32 is going to be out, and that looks really nice. Same story with 3G/4G modules. I don’t see this as an issue. So let’s discuss the micro controller. Let’s say we want at least 1MB flash, and at least 256KB RAM. At least. Now, we need multiple CAN ports. 2 at a minimum, but 3 or 4 would be much better. A lot of the newer cars split their stuff over multiple CAN buses, and having that support would be great. Remember that we want one system that can be used as a logger, development environment, and final production system. That puts us in ‘automotive’ territory, which is not a bad place to be. ST have some brutal micro controllers, like the STM32F769. M7 core. Up to 2MB flash, 512KB SRAM, and 3x CAN buses. All the older stuff is 2 CAN bus max, but availability of the new 3xCAN bus stuff is summer 2016. A couple supposedly available now, but I can’t find them. NXP have a nice automotive range in the MPC micro controllers (in particular MPC56 has lots of choice, and 10 year product life time), but a strange e200z0 core that I’ve never seen/used. Again, brutal on the flash and RAM, and up to 6 CAN buses. These are their SPC5 32bit automotive MCUs. They have a ‘free’ GCC based development environment. The NXP S32K looks good, but seems not available yet. My preference is the NXP range, but I am concerned about that e200z0 core. Really never heard of it. Anyone got any experience with this? The ST stuff also looks good, but availability is tight. Thoughts? Anybody have a good contact with NXP for some advice? Regards, Mark.

11 30

Open API
by Robert Sharpe 03 Feb '16

03 Feb '16

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 Your Plugged-in Partner Evergreen Consulting is the trading name of Sharpe Consultants Ltd

4 6

Re: [Ovmsdev] OVMS v3 - Microcontroller
by Bennett Leeds 01 Feb '16

01 Feb '16

Just a note that ATT is shutting down its 2G network, leaving only 3G and LTE: http://www.sine-wave.com/blog/2g-sunset-retiring-0 - Bennett On Mon, Feb 1, 2016 at 8:00 PM, <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. Re: OVMS v3 - Microcontroller (Mark Webb-Johnson) > 2. Re: OVMS v3 - Microcontroller (Mark Webb-Johnson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 2 Feb 2016 09:07:47 +0800 > From: Mark Webb-Johnson <mark(a)webb-johnson.net> > Subject: Re: [Ovmsdev] OVMS v3 - Microcontroller > To: OVMS Developers <ovmsdev(a)lists.teslaclub.hk> > Message-ID: <9C27858A-DFEF-4699-B7EC-6AEE34B28439(a)webb-johnson.net> > Content-Type: text/plain; charset="utf-8" > > Dominik, > > The idea is to make the cellular modem an (optional) plug-in board. This > is necessary for two reasons: > > a) Technology changes (2G->3G->4G). > b) Universal modems (such as quad band 2G that work everywhere in the > world) aren?t really possible in the 3G/4G space, so we need different > modems for different parts of the world. > > Happy to look at both 3G and 4G options as the time draws near. Quite > frankly, there are a huge number of options out there for this. I consider > this one of the easiest parts of the project. > > Regards, Mark. > > > On 2 Feb 2016, at 1:51 AM, Dominik Westner <ovms(a)nikwest.de> wrote: > > > > Generally I think 3G doesn?t make a lot of sense. A new platform should > be 4G capable. As far as I know 2G is more likely to stay longer than 3G. > > I know already some areas in Germany and Austria where you can find 4G > and maybe 2G, but no 3G. > > > > For example seeedstudio retargeted their Rephone 3G module to 4G after > some investigations about the future of 3G. > > ( > https://www.kickstarter.com/projects/seeed/rephone-kit-worlds-first-open-so… > < > https://www.kickstarter.com/projects/seeed/rephone-kit-worlds-first-open-so… > >) > > > > Just my 2 cents > > > > Dominik > > > >> On 01 Feb 2016, at 18:30, Arthur Hebert <ahebert(a)gmail.com <mailto: > ahebert(a)gmail.com>> wrote: > >> > >> The Particle Electron has recently caught my attention: > https://www.particle.io/cellular <https://www.particle.io/cellular>. > Actual performance and usability are unknown, since the first units don't > ship until later this month, but it has some attractive features: > >> low-cost M2M-oriented international SMS/data plans ($3/mo. for 20k > messages) > >> STM32F205 MCU with 1MB flash, 128k RAM and 2 CAN buses > >> free development IDE: https://www.particle.io/dev < > https://www.particle.io/dev> > >> also a free web-based dev environment at https://build.particle.io < > https://build.particle.io/> (I assume/hope this will support the Electron > cellular board when it comes out) > >> I know it doesn't come close to meeting the RAM requirements, but the > cellular plan is a pretty big draw IMO. Perhaps worth using this module in > conjunction with another board with a better MCU? > >> > >> -Arthur > >> > > > > _______________________________________________ > > OvmsDev mailing list > > OvmsDev(a)lists.teslaclub.hk > > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > >

1 0