July 2018 - OvmsDev - Open Vehicles

Nissan Leaf Support Request
by Mark Webb-Johnson 12 Jul '18

12 Jul '18

A user has a raised a ticket: https://www.openvehicles.com/node/2053 <https://www.openvehicles.com/node/2053> I would like to be able to turn my A/C on and off remotely as discussed http://www.arachnon.de/wb/pages/en/nissan-leaf/ovms.php <http://www.arachnon.de/wb/pages/en/nissan-leaf/ovms.php> here. When I use their version of the OVMS app it just crashes repeatedly after I input my car's settings so I can't use it. However when I use the play market version of the app, there is no A/C button but it runs solidly and I can see my car's information (it works). Is there a way to turn the A/C on and off with this version of the app? Also, I'm assuming (perhaps incorrectly) that the latest hardware already has the features built in and no flashing is necessary. Bonus questions: In the app it seems there's an ability to unlock my car and to put it in valet mode but those features need a pin. Where does this pin come from and do the features really work? What is valet mode anyway? What is the 'Features' section of the app for? I see that I need to set my #15 CAN Write to 1 before I can expect the A/C control to work which I've done but is there any info on what the rest of it does? Server: 2.1.1-20121216 Car: 3.1.006 App: 3.12.4 (20180428 Update: The remote A/C worked with homelink 1 and 2 when I got home to charge. I don't have a model with navigation or car wings so I don't think I have the option mentioned about when to allow remote A/C with respect to SOC level. Is it possible that there's a way to set this option with the OVMS? Can a Nissan Leaf developer/expert help out with this? Regards, Mark

3 7

Missing submodule init in Development Guide.
by Jakob Löw 12 Jul '18

12 Jul '18

Hey, the development guide states: Git clone the OVMS v3 repository and init the build configuration: $ git clone https://github.com/openvehicles/Open-Vehicle-Monitoring-Sys tem-3.git $ cd Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3 $ cp support/sdkconfig.default.hw31 sdkconfig $ make menuconfig This does not initialize the mongoose submodule and thus does not work. Either a --recursive has to be added to the git clone or git submodule update --init has to be run. Unfortunately I do not have access to the Google Doc, so I can't change it. See this issue on github: https://github.com/openvehicles/Open-Vehicle- Monitoring-System-3/issues/140 - Jakob

2 1

GPS / NMEA integration
by Michael Balzer 11 Jul '18

11 Jul '18

I'm currently working on the NMEA module. The MUX channel is working, but I don't get a GPS fix. I've tried all GPS commands and now suspect my SIMCOM module having a hardware issue. I'm doing this: OVMS > level debug OVMS > power simcom on …wait for the MUX to be ready, then issue… OVMS > simcom muxtx 4 AT+CGPSNMEA=1 OVMS > simcom muxtx 4 AT+CGPS=1,1 …now the SIMCOM begins sending NMEA $GPGGA lines once per second looking like this: D (2937174) SIMCOM rx: f9 05 ff 35 24 47 50 47 47 41 2c 2c 2c 2c 2c 2c ...5*$GPGGA,,,,,,* D (2937174) SIMCOM rx: 30 2c 2c 2c 2c 2c 2c 2c 2c 2a 36 36 0d 0a 60 f9 *0,,,,,,,,*66*..`. Normally the modem should get a GPS fix within about 1-2 minutes and begin filling data in the $GPGGA record. But my modem won't, it just keeps sending empty fields. Can someone please try this with his/her module? To disable the GPS receiver, issue: OVMS > simcom muxtx 4 AT+CGPS=0 Thanks & regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

7 30

Re: [Ovmsdev] Leaf
by Dean MacGregor 10 Jul '18

10 Jul '18

I'm using the play store version 3.12.4 and I don't have the AC button. It's not that big of a deal except that I can't see whether or not the AC is on from the app. Also it seems like since the recent OTA update my app always says my doors are unlocked even when they are locked. On Thu, Jul 5, 2018 at 5:42 AM, ovmsdev-request(a)lists.openvehicles.com<ovmsdev-request(a)lists.openvehicles.com> wrote: Send OvmsDev mailing list submissions to ovmsdev(a)lists.openvehicles.com To subscribe or unsubscribe via the World Wide Web, visit http://lists.openvehicles.com/mailman/listinfo/ovmsdev or, via email, send a message with subject or body 'help' to ovmsdev-request(a)lists.openvehicles.com You can reach the person managing the list at ovmsdev-owner(a)lists.openvehicles.com When replying, please edit your Subject line so it is more specific than "Re: Contents of OvmsDev digest..." Today's Topics: 1. Re: Can buses stop after some time (Stein Arne Sordal) 2. Re: Can buses stop after some time (Tom Parker) 3. Re: Nissan Leaf Support Request (Tom Parker) 4. Re: MQTT and Ovms Server v3 (Jakob L?w) ---------------------------------------------------------------------- Message: 1 Date: Thu, 5 Jul 2018 08:34:17 +0200 From: Stein Arne Sordal <ovms(a)topphemmelig.no> To: OVMS Developers <ovmsdev(a)lists.openvehicles.com> Subject: Re: [Ovmsdev] Can buses stop after some time Message-ID: <B62B646E-7129-4A61-B928-467E83EC32B1(a)topphemmelig.no> Content-Type: text/plain; charset=utf-8 Did anyone figure out what happens here? Now the OVMS thinks my car is stolen since it?s moving (GPS) and CAN2 is dead. Reboot of module brings CAN2 back to life for a period of time. -Stein Arne Sordal- > On 11 May 2018, at 12:29, Stein Arne Sordal <ovms(a)topphemmelig.no> wrote: > > Hi Tom > > I have seen this with my Leaf. > I?ve been on vacation, so I haven?t got time to test a lot, but it looks like one of the can buses stops. Started testing again today. > > -Stein Arne Sordal- > > > >> On 11 May 2018, at 12:22, Tom Parker <tom(a)carrott.org> wrote: >> >> Hi all, >> >> I synced up with master about a week ago and since then I've seen both can busses stop working. I still see the 12v battery metric changing, but everything that comes from the car stops. Rebooting the module with "module reset" does not seem to fix it, while make app-flash monitor does fix it. I haven't tried make monitor on it's own. >> >> Is anyone else seeing behavior like this? >> >> Sorry for the vague bug report. I'll spend some time later this weekend to try to gather more information. >> _______________________________________________ >> OvmsDev mailing list >> OvmsDev(a)lists.openvehicles.com >> http://lists.openvehicles.com/mailman/listinfo/ovmsdev > > _______________________________________________ > OvmsDev mailing list > OvmsDev(a)lists.openvehicles.com > http://lists.openvehicles.com/mailman/listinfo/ovmsdev ------------------------------ Message: 2 Date: Thu, 5 Jul 2018 19:55:05 +1200 From: Tom Parker <tom(a)carrott.org> To: ovmsdev(a)lists.openvehicles.com Subject: Re: [Ovmsdev] Can buses stop after some time Message-ID: <8e2964d0-047e-7f27-9eaa-daf9cd14f6a0(a)carrott.org> Content-Type: text/plain; charset=utf-8; format=flowed I haven't had a chance to try to work out what is going on. I can say that the second can interface doesn't work for very long before stopping. This manifests most obviously on my Leaf as a stopped odometer in the OVMS app. If you look at the metrics in the console then everything that comes from the Car CAN bus (ie the second CAN bus) has frozen. The first CAN interface seems much more reliable, with SOC information from the EV bus being fairly reliably reported. I haven't done the modification to make my 3.0 unit's GPS work so I haven't experienced the stolen detection. On 05/07/18 18:34, Stein Arne Sordal wrote: > Did anyone figure out what happens here? > Now the OVMS thinks my car is stolen since it?s moving (GPS) and CAN2 is dead. > Reboot of module brings CAN2 back to life for a period of time. > > -Stein Arne Sordal- > > > >> On 11 May 2018, at 12:29, Stein Arne Sordal <ovms(a)topphemmelig.no> wrote: >> >> Hi Tom >> >> I have seen this with my Leaf. >> I?ve been on vacation, so I haven?t got time to test a lot, but it looks like one of the can buses stops. Started testing again today. >> >> -Stein Arne Sordal- >> >> >> >>> On 11 May 2018, at 12:22, Tom Parker <tom(a)carrott.org> wrote: >>> >>> Hi all, >>> >>> I synced up with master about a week ago and since then I've seen both can busses stop working. I still see the 12v battery metric changing, but everything that comes from the car stops. Rebooting the module with "module reset" does not seem to fix it, while make app-flash monitor does fix it. I haven't tried make monitor on it's own. >>> >>> Is anyone else seeing behavior like this? >>> >>> Sorry for the vague bug report. I'll spend some time later this weekend to try to gather more information. >>> _______________________________________________ >>> OvmsDev mailing list >>> OvmsDev(a)lists.openvehicles.com >>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev >> _______________________________________________ >> OvmsDev mailing list >> OvmsDev(a)lists.openvehicles.com >> http://lists.openvehicles.com/mailman/listinfo/ovmsdev > _______________________________________________ > OvmsDev mailing list > OvmsDev(a)lists.openvehicles.com > http://lists.openvehicles.com/mailman/listinfo/ovmsdev ------------------------------ Message: 3 Date: Thu, 5 Jul 2018 20:34:34 +1200 From: Tom Parker <tom(a)carrott.org> To: ovmsdev(a)lists.openvehicles.com Subject: Re: [Ovmsdev] Nissan Leaf Support Request Message-ID: <85109d8f-31ba-245e-40bf-50b0351f13fc(a)carrott.org> Content-Type: text/plain; charset="windows-1252"; Format="flowed" On 01/07/18 21:23, Mark Webb-Johnson wrote: > A user has a raised a ticket: > > https://www.openvehicles.com/node/2053 > I can't see this link > > I would like to be able to turn my A/C on and off remotely as > discussed > http://www.arachnon.de/wb/pages/en/nissan-leaf/ovms.php?here. When > I use their version of the OVMS app it just crashes repeatedly > after I input my car's settings so I can't use it. However when I > use the play market version of the app, there is no A/C button but > it runs solidly and I can see my car's information (it works). Is > there a way to turn the A/C on and off with this version of the > app? Also, I'm assuming (perhaps incorrectly) that the latest > hardware already has the features built in and no flashing is > necessary. > You want to use the play store version. I'm running 3.12.4 from the Play store and when connected to a Leaf, I see the AC button. > Bonus questions: > In the app it seems there's an ability to unlock my car and to put > it in valet mode but those features need a pin. Where does this > pin come from and do the features really work? What is valet mode > anyway? > Not all cars support lock and unlock or valet mode. We have some code that works for lock/unlock on the Leaf but it's not yet finished. There are no plans to support valet mode. > What is the 'Features' section of the app for? I see that I need > to set my #15 CAN Write to 1 before I can expect the A/C control > to work which I've done but is there any info on what the rest of > it does? > You don't need this for OVMS v3. > Server: 2.1.1-20121216 > Car: 3.1.006 > App: 3.12.4 (20180428 > Update: The remote A/C worked with homelink 1 and 2 when I got > home to charge. I don't have a model with navigation or car wings > so I don't think I have the option mentioned about when to allow > remote A/C with respect to SOC level. Is it possible that there's > a way to set this option with the OVMS? > We still support climate control with homelink 1 & 2 for old apps. This at least lets use separate your climate control button problem questions about how the AC works. Which model year Leaf do you have? Older than 2013 may require extra hardware to enable climate control when the car is asleep. 2013 through 2015 use a different remote climate control to that of 2016 & 2017. You have to set the module year configuration option to tell the OVMS which car you have. 2018 Leafs are not yet supported. We made a change to how the climate control is switched off recently and this is probably in the latest firmware (which you don't have on your OVMS). We don't have a way way to configure the remote climate control -- the OVMS simply sends the enable command to the car and the car does it's thing.

2 1

Server V3 topic prefix, stability and encryption
by Jakob Löw 04 Jul '18

04 Jul '18

Hey, I've seen some changes pushed to the repo regarding the v3 server. I did some development on that too and found it to be very unstable, often crashing after start (when transmitting all metrics) or when the NetUp was called before any interface was up. Both issues were connected to race conditions. I opened two pull requests to fix them [0], [1]. The first one also introduces a new configuration option to set a custom prefix for the MQTT topic. OVMS metric names seem to use a sort of namespacing using dots, like m.freeram or v.e.on. Replacing dots in metric names by slashes in MQTT topics, makes the OVMS follow MQTT namespacing rules (m/freeram and v/e/on). One thing currently missing with the Server V3 is encryption. Mongoose supports SSL so enabling it would be easy, but the problem is the certificate management. We could allow users to load certs onto the module, however this is something unexperienced users wouldnt do. Another option is to ship the OVMS with a list of common root certs, like many browsers do. The certs shipped with firefox are ~500KB and can be easily obtained e.g. from the debian repos [2]. This could then also be used by the server v2 to replace the outdated RC4 encryption. - Jakob [0] https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/pu ll/137 [1] https://github.com/openvehicles/mongoose/pull/1 [2] https://packages.debian.org/stretch/ca-certificates

2 2

Alerts (or, the lack thereof)
by Greg D. 03 Jul '18

03 Jul '18

Hi folks, A couple of postings on TMC from Roadster owners who have received a single alert, and never got any more. I've not had this problem, and wonder what guidance we can give them. https://teslamotorsclub.com/tmc/posts/2845522/ (starting with his "next question"...) I'm on version 3.1.006; the two recent posts are from versions .006 and .007, so this isn't a version issue. Is there something they need to configure? I don't know, for example, what app they are running, but presume the issue is upstream of that. Thanks, Greg

2 3

OVMS v3 v3.1.008 Over-the-Air firmware update
by Mark Webb-Johnson 03 Jul '18

03 Jul '18

https://www.openvehicles.com/node/2058 <https://www.openvehicles.com/node/2058> Today, we are pleased to release v3.1.008. Over 60 bug fixes and enhancements have gone into this release since the last public release (v3.1.006), and a summary of the major changes is here: Firmware: 3.1.008 3.1.008 OTA release - Vehicle theft alert if vehicle moved more than 500m when parked - New 'location radius' command to set location radius - Only issue 'location.enter' and 'location.leave' events if vehicle is ON - Fix issue with OTA updates in 3.1.007 3.1.007 OTA release - Logging: auto expire log archive New config: log [file.keepdays] = 30 0 = disable New command: log expire [days] Manual expire Note: auto expire is done within hour 0 of day - Web UI: simplified time zone region selection (vehicle config) - Web UI: locations editor - Prefer SPI RAM (on 3.1 hardware) for improved on-chip memory availability For full detail on all changes, check the GitHub revision history. Please note the firmware v3.1.007 was never fully released (beyond testing release levels) as it had an issue with OTA updates. If you are running v3.1.007 you will most likely have to manually update to v3.1.008, using these instructions (only for those running v3.1.007): 1. Firstly, go back to factory firmware: ota boot factory module reset 2. After reset, connect to wifi and do a manual ota update: ota flash http api.openvehicles.com/firmware/ota/v3.1/main/3.1.008.ovms3.bin module reset 3. After that is done, check the version with: ota status You should be running 3.1.008 from an ota partition. Alternatively, you can download 3.1.008 from http://api.openvehicles.com/firmware/ota/v3.1/main/3.1.008.ovms3.bin <http://api.openvehicles.com/firmware/ota/v3.1/main/3.1.008.ovms3.bin> directly and put as ovms3.bin on SD CARD to update from that. The v3 modules can be updated over the air (wifi), via SD CARD, or over USB - all without requiring special hardware programmers like the PICKIT used for v2. The simplest way to update the module firmware is to connect it as a client to your wifi network (or phone hotspot), and then use the web interface Config / Firmware / Flash-from-Web; that will show you the version you are running, as well as the latest version available for update. One click on 'Flash now' and the update will be downloaded and installed. Alternatively, you can download the firmware update to a file named ovms3.bin in the root directory of a FAT formatted SD CARD and insert the card into the module's slot - the new firmware will be updated automatically and the file renamed ovms3.done to signify completion. This firmware also includes the feature to check for and automatically update to newly available firmware, every night (so long as the vehicle is connected to WiFi). After updating to 3.1.005 or later, you can enable this for future firmware releases with 'config ota auto yes'. Thank you for your support of the project. Open Vehicles

1 0