- OvmsDev - Open Vehicles

Memory leak
by Michael Balzer 26 Apr '18

26 Apr '18

There seems to be a memory leak, after running the module over the past hours in my car, ssh couldn't allocate 4K for a new session and I had this status: OVMS > mo m Free 8-bit *14600*/281968, 32-bit 8052/24308, SPIRAM 4129588/4194252 --Task-- Total DRAM D/IRAM IRAM SPIRAM +/- DRAM D/IRAM IRAM SPIRAM no task* 5348 0 0 0 +5348 +0 +0 +0 main* 18084 0 0 0 +18084 +0 +0 +0 esp_timer 39268 0 644 23436 +39268 +0 +644 +23436 OVMS Events 53304 65064 0 10076 +53304 +65064 +0 +10076 ipc0 7776 0 0 0 +7776 +0 +0 +0 ipc1 12 0 0 0 +12 +0 +0 +0 tiT 232 908 0 6376 +232 +908 +0 +6376 OVMS SIMCOM 0 4512 0 0 +0 +4512 +0 +0 wifi 1464 64 0 3512 +1464 +64 +0 +3512 OVMS Console 0 20 0 0 +0 +20 +0 +0 OVMS NetMan 0 12688 0 68 +0 +12688 +0 +68 mo m 0 0 15488 12000 +0 +0 +15488 +12000 OVMS > mo t Number of Tasks = 20 Stack: Now Max Total Heap 32-bit SPIRAM 3FFAFB48 1 Blk esp_timer 388 644 4096 39268 644 23436 3FFBDE54 2 Blk eventTask 448 1328 4608 0 0 0 3FFBFC50 3 Blk OVMS Events 444 3932 6144 118368 0 10076 3FFC4974 4 Blk OVMS CanRx 432 544 1024 0 0 0 3FFC9090 5 Blk ipc0 396 444 1024 7776 0 0 3FFC9690 6 Blk ipc1 396 444 1024 12 0 0 3FFCB4B8 9 Rdy IDLE 356 484 1024 0 0 0 3FFCBA4C 10 Rdy IDLE 360 488 1024 0 0 0 3FFCC7E0 11 Blk Tmr Svc 396 1820 3072 0 0 0 3FFC98FC 16 Blk tiT 496 2272 3072 1136 0 6576 3FFD7540 17 Blk OVMS SIMCOM 460 3020 4096 4512 0 0 3FFD951C 18 Blk wifi 424 2168 4096 1528 0 3512 3FFDBCB4 19 Blk pmT 416 576 2560 0 0 0 3FFDDABC 20 Blk OVMS Vehicle 456 2008 3072 0 0 0 3FFDFE38 21 Blk OVMS COrx 452 580 3072 0 0 0 3FFE1C88 22 Blk OVMS COwrk 532 532 1536 0 0 0 3FFE3E78 23 Blk OVMS Console 548 1716 6144 20 0 0 3FFE9430 24 Blk OVMS NetMan 732 5980 7168 12692 0 68 3FFEA9C8 25 Blk mdns 404 1724 4096 0 0 0 3FFFCD14 36 Rdy mo t 704 1936 5120 72 0 0 Nothing special to see. +14k on the events task vs. a fresh boot, but nothing that can explain the loss of more than 40k. Odd, I'll watch this. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

3 24

Lessons learnt, production batch #2 and onwards
by Mark Webb-Johnson 24 Apr '18

24 Apr '18

Well, it has been an interesting few weeks as the first production batch of OVMS v3 came online. I don’t know about for others helping out with support tickets, but I’ve sure learned a lot - especially about what can go wrong for inexperienced users trying to setup a complex product. 14 support tickets were opened, along with another perhaps 6 calls for help via other means, and here are the most common problems encountered: Switched from Access Point mode to Client mode, and lost access. Can’t get into module via USB (drivers seem ok, but terminal emulators, and baud rates, are beyond most people’s understanding). Too hard for most to do a factory reset. Can’t see modem ICCID when powered off. Modem powered off by default, unless the little tick box is clicked. Server v2 off by default, unless the little tick box is clicked. Upper vs lower case on command execution. Unable to do firmware update in Access Point mode. Password confusion (wifi client vs module vs server vehicle vs server account vs access point vs OVMSinit vs etc etc). wifi vs modem switches and DNS settings. Modem SIM registration issues (can’t see, or don’t know how to see, status of simcom). Don’t understand how to check status. While some of these issues have been addressed, I am reluctant to release a new batch of modules to the world, especially this time with less technically capable users coming online. It is probably not ‘fun’ work, but I think we can make this much simpler for new users. We can lead them through the setup in the following stages: Require, as a pre-requisite, users to initially setup the module within range of a home wifi / cellular hotspot connection. Factory default, use Access Point mode, SSID OVMS password “OVMSinit”, and no module password. Have them connect to the module over wifi Access Point, and http://192.168.4.1/ <http://192.168.4.1/>. The web interface then shows them a list of WiFi access points in range, and asks them to choose one and enter the password for that access point (clearly labelled as SSID, and "<SSID> Password”). The module then reconfigures as Client + Access Point mode, and tries to connect to the client wifi, as well as keeping the access point connection open. If not ok, tell them and go back to #3 for them to try again. When ok, proceed to ask them to update the firmware. This will do a simple OTA download over HTTP, then reboot. When back up, in one screen ask them to enter all the details for their network, and configure appropriately: Use Wifi? WiFi Mode (AccessPoint+SpecificClient, or ScanningClient) OVMS Access Point SSID New OVMS Access Point password (as OVMSinit is insecure beyond initial setup) DNS (default: google, or custom) Module password (as default empty is insecure beyond initial setup) Use OVMS Server v2? Vehicle type Vehicle ID Vehicle Server password Vehicle server (openvehicles, dexter, or custom) Use modem? Modem APN, username and password (default: hologram) Test each of the above, and show them the results. Set auto appropriately, and disable quickstart then reboot. The point is to lead them through each of the steps, test each setting and show them the result. Technically, my only concern is the switch from AP to AP+client mode and whether the existing wifi connection will die or survive the channel switch. We also have to do a wifi scan, in Access Point mode, but I think we can do that by just temporarily turning off access point or doing it before the access point is brought up. Both these will depend on how ESP32 handles it. I’m happy to do a lot (if not all) of the above, but will definitely need help with the web side. But, first let’s agree on the proper list of questions to ask and flow to follow. Regards, Mark.

5 7

Getting started
by Craig Leres 23 Apr '18

23 Apr '18

Although experienced with J1850/Class 2, ovms is completely new to me. I have a friend with a V1 module in his roadster and it's great that the V3 module is finally out! I've figured out a fair amount on my own but it's probably time for me to start asking questions (and providing some feedback). I got my module up on the bench without too much trouble. The V2 and V3 server config was confusing to me since I knew almost nothing. I think I had read that V2 was legacy and V3 was where new development effort was happening so I thought that's what I wanted. But I didn't find much info on io.adafruit.com vs. ovms so I ended up configuring the V2 server for starters. My canbus car is a second generation CTS-V. Once I plugged that in I could see my car with the iphone app. But the app didn't show much (I completely understand that most work so far as been on plugin vehicles). Once I turned the car on the battery percentage starting showing how full my gas tank was. I'm still a bit confused about how GPS works. I was expecting it to use the GPS periodically but what I've found is if I don't turn on the GPS at startup, I never see location info even when I'm driving. And if I enable GPS at startup, it seems to always be on even when the car is not. Maybe this is because my car isn't supported and the module doesn't know when it's running? I also found that trying to press any of the homelink options crashes the iphone app. Initially I could not get ssh to work. This wasn't surprising since my FreeBSD desktop runs openssh 7.7p1 and I know there is a push to disable or even remove less secure and insecure crypto. But after joining the ovmsdev list the solution was revealed (create a Host block with "Ciphers aes128-cbc") so that is working for me now. I like the way ssh.keys work (mapping the remote username) but I use hard tokens with ssh it sure would be nice if you could configure more than one ssh key. When learning about how ssh works I was using the google doc (15Mar18) and it says when you login you start in non-secure mode. I find ssh always puts me in secure mode. The section about SD cards in the google doc is empty; I made assumptions and got a couple class 10 64G cards. I don't know if this is a good size or way to big to be useful. Today I brought up a mqtt server (mosquitto). In verbose mode I can see my v3 module posting things to it but I don't know what tools I can use with my server. I'd like to get a build environment up. The only info I could find was: https://github.com/openvehicles/Open-Vehicle-Monitoring-System/blob/master/… which is geared towards v2 (which I saw is pic based). What do I need to be able to build for v3? I normally work/play on FreeBSD but I have an ubuntu system handy for when I need it. I noticed lists.openvehicles.com uses http; if I try to force https I end up on a different website. Looks like apache is in use; I have a lot of experience with apache and lets encrypt ssl certs and would be happy to share the setup I use. I'm also wondering about https support for the ovms module itself. Is that on the roadmap? I know the esp32 can do it; I have done a *lot* with atmega arduino clones but have recently started using esp8266 and esp32 modules because I can network them (and with https). Craig

3 2

OT: A tool for exploring data graphically
by Stephen Casner 23 Apr '18

23 Apr '18

Another software project I've been working on recently (timesharing computer time with OVMS) is a little data graphing program named "graf" for use in X11 environments. It's one that I've used for work and personal data exploration over the past couple of decades, but recently I added several enhancements. It is quite lightweight, using only the base Xlib library and protocol, so it can display large datasets without choking. You folks may have your own favorite fancy graphing tools; this one has a somewhat different purpose than most. It is designed for data exploration more than presentation, using mouse functions to measure the distance between points or the slope of a line or calculate the least-squares regression line for a dataset or to zoom in on a section of the graph for a closer view. It takes a simple text file as input with an (x,y) pair of numbers on each line so it is easy to feed it with the output of a script, or it will accept multiple files as input to show each as a separate line on the graph. One unusual feature that was part of the recent enhancements is the ability to interpret Unix-style timestamps (based at 1970-01-01 00:00:00 GMT) as dates and times and to generate dynamic grid labels with varying temporal resolution depending upon what unit boundary the grid line represents. The motivation for varying the resolution is that to show a complete date and time down to microseconds takes too many characters to fit on each grid line. Each grid line label on the X axis shows the increment of time at the scale that allows the labels to fit, while at the left and right edges an additional label shows the remaining date and time information not included in the grid line labels. The format of the labels will vary to show a larger scale value on the even boundaries and as you zoom in the detail changes. Examples: 09/01 2014 03/01 06/01 09/01 2013 2014 22:30 23:00 23:30 04/26 00:30 01:00 2014-04-25 2014-04-26 45.000 50.000 55.000 23:56 05.000 10.000 15.000 20.000 25.000 2014-04-25 23:55: 2014-04-25 23:56: Although this varying format is not common, I think it is a pretty neat idea. In the actual graph window I use three levels of gray for the grid labels so the major boundaries are emphasized. And in local time, the DST transitions are handled properly (that was a challenge) by varying the grid spacing if needed. If you have an X11-Unix-ish environment and would like to try it out, the source is here (build it with ./configure then make): https://github.com/kernelsid/graf Or, I have MacOS and linux (CentOS) binaries here: http://casners.us/macos/graf http://casners.us/linxu/graf Try "graf -h" to see the usage text and Ctrl-H, ? or F1 in the window when running to pop up another window describing the mouse and keyboard functions. A three-button mouse or simulation thereof is needed to access the functions on the middle button. I've attached two data files that you could try along with a third that you could download since it is bigger than I want to put in email: 1) The first graph has a bunch of data lines for all the telemetry parameters collected from my Tesla Roadster log while driving on the track at Laguna Seca in the time trial event at ReFuel 2011. 2) The second dataset contains timestamps with fractional second resolution. This produces a graph of the difference between the internal-clock-based timestamps contained in the datastream generated by the little 8-pin PIC microcontroller that I used to extract the data from the two meters on our home solar PV system and NTP-derived timestamps in the computer that collects the datastream. The latter timestamps only have a resolution of one second, hence the +/-500ms noise. This is a good dataset for testing the linear regression function. 3) The third graph shows the output of the solar PV system on our home for a period of 7 days as measured in Amps as displayed on the meters connected to the left and right strings of panels in our system. This dataset demonstrates graf's speed since it contains 1.2 million datapoints, but that means the file is 49MB so rather than attaching it to this email I have it available for download from: http://casners.us/amps.graf If you want to run graf with these datasets, I suggest invoking it with "graf -Lmt" plus the dataset filename to select the X axis date display in local time and to show a small icon at each datapoint. I usually also include -t because I prefer just tickmarks rather than full grid lines most of the time. I also attached a screenshot of the first graph so you can at least see a static image if you don't want to try to run the program. -- Steve

1 1

T down
by Mark Webb-Johnson 22 Apr '18

22 Apr '18

1 0

Please update mongoose submodule
by Stephen Casner 20 Apr '18

20 Apr '18

I have changed the mongoose mg_send() function to return the number of bytes appended or zero if buffer allocation fails. The code in console_ssh now depends upon this to avoid corrupting the ssh packet stream if the system runs low on free memory. Thus, if you update the the latest OVMS master branch, please remember to "git submodule update" as well. -- Steve

1 0

Any activity/thoughts around a script to sign on to multi-prompting wifi networks?
by chip＠cangmag.com 20 Apr '18

20 Apr '18

If this is a naive question, please excuse my ignorance, but is their any activity/thoughts around implementing a script on the v3 module to allow for sign on to multi-prompting wifi networks--for example, a wifi network that prompts for a username and a password? Thanks. Chip C.

1 0

Initial OTA update
by Greg D. 20 Apr '18

20 Apr '18

5 16

Async events and config updates
by Michael Balzer 19 Apr '18

19 Apr '18

Frank Demes found an issue in the Twizy code that may affect other vehicles and commands as well, please check your code: I'm using the ConfigChanged() hook to process config changes, it's triggered by the "config.changed" and "config.mounted" events. In my command implementation I previously relied on this hook being called inline from MyConfig.SetParamValue…(), so my internal state would be updated immediately. Due to events now being processed asynchronously this is no longer valid. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

1 0

OVMS v3 v3.1.004 Over-the-Air firmware update
by Mark Webb-Johnson 17 Apr '18

17 Apr '18

FYI: Email sent to all purchasers of OVMS v3.1 modules Thank you for your support of the Open Vehicles project. OVMS kits have started arriving, and are being connected to cars. Approximately 1/3rd of the first batch of modules have already been installed and are connected to OVMS servers, with more coming online every day. The feedback you early users are providing is extremely helpful to the project, to smooth the way for future users, and is most appreciated. 1] Firmware Update Of those who have already installed their OVMS v3 modules, approximately half are still running the old factory firmware (now more than a month out of date). As this is early beta firmware, it is important that you keep the module up-to-date with the latest firmware (to take advantage of fixes and improvements as they are released, and avoid running into problems already fixed). Today, we are pleased to release v3.1.004: Firmware: 3.1.004/ota_0/main (build idf v3.1-dev-454-gdaef4b5c Apr 17 2018 08:35:59) OTA release providing minor improvements and fixes. - Tesla Model S: Add support for v.bat.soc, v.pos.speed and park/drive status metrics - Tesla Roadster: Fixes for charge/drive mode on v1.x and v2.x cars - SD CARD: Provide configurable sdcard parameters: sdcard [maxfreq.khz] = 16000 Maximum frequency (in kHz) of SD CARD bus sdcard [automount] = yes Automatically mount SD CARD on insertion - Boot: store & send crash debug info (*-OVM-DebugCrash records) - OTA: Support for configurable release tag and server URL ota [tag] = main ota [server] = api.openvehicles.com/firmware/ota <http://api.openvehicles.com/firmware/ota> - Wifi: Increase scan responsiveness (60 seconds -> 10, on first scan) - Factory reset by SD file "factoryreset.txt" or pushing SW2 for 10 seconds Note: SW2 method needs removing any SD card inserted. - Wifi: fallback to AP mode net "OVMS" password "OVMSinit" after factory reset - Miscellaneous bug fixes and enhancements 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. 2] FAQ Early production users have run into some common problems, which we summarise below in a mini-FAQ: The 'metric list m.net.mdm.iccid’ is not showing my modem, and my modem is not connecting. To minimise power consumption, OVMS v3 will by default keep all peripheral devices turned off unless you enable them. In the case of the modem, you can enable it at startup by the web interface ‘Autostart’ configuration clicking the “Start modem” option. You can also do this from the command line with ‘config auto modem yes’. I’ve messed things up, and need to reset the settings back to factory defaults. If you are running the latest v3.1.004 firmware, you can simply remove any SD CARD then press and hold the BOOT button for 10 seconds. Alternatively, make a file ‘factoryreset.txt’ on the root of the SD CARD and insert it. If you are running older firmware, you will need to connect a serial console (via USB) and use the ‘module factory reset’ command. Instructions are in the User Guide. It is not connecting. How do I find out what is going on? The following commands show useful status information: simcom status network status wifi status server v2 status What WiFi configuration is recommended? The most flexible seems to be “Scanning Client” mode. Enter SSIDs and passwords for all the WiFi networks you have access to (including your phone hotspot if you have it), and enable Scanning Client mode. The OVMS module will then connect to WiFi whenever it gets in range of any of those networks. That will then give the module cheap fast Internet (without cellular data charges), the ability to do OTA firmware updates over WiFi, and a simple way for any laptop/phone/tablet on the same WiFi network to connect to the module to configure/monitor. While Access Point mode is useful at times (especially for initial setup), it offers no Internet connectivity. Access Point + Client mode can only use one single SSID and is limited in that the channel for the SSID must be the same as the channel for the Access Point (only 1 radio in the module). In general, Scanning Client mode is much simpler and more useful for the majority of cases. 3] Help/Support links Unboxing Video: https://www.youtube.com/watch?v=HpyI1q4Y89I <https://www.youtube.com/watch?v=HpyI1q4Y89I> User Guide: https://docs.google.com/document/d/16JrXR7rybp-18DrEoeh1rg6GqQT_jVBvhaXh2oE… <https://docs.google.com/document/d/16JrXR7rybp-18DrEoeh1rg6GqQT_jVBvhaXh2oE…> User Forums: https://www.openvehicles.com/forum <https://www.openvehicles.com/forum> 4] Hologram To simplify getting started, a Hologram SIM has been included with the modem in every OVMS v3.1 kit. Hologram have also kindly provided a coupon code “OVMS” that can be used to get US$5 credit; this can be used for both existing as well as new Hologram customers. You can simply enter that coupon code at checkout (when purchasing data credits, etc). When activating your Hologram SIM, you’ll need to enter the ICCID written on the SIM itself. You can also get that electronically (without having to open up the package) from the web or terminal shells, so long as the modem is powered up, with the following command: OVMS# metric list m.net.mdm.iccid 5] Support Please remember that this first production batch is intended for experienced OVMS v2 users and v3 developers, and note: Firmware is not complete, and should be considered beta. Functionality is approximately equivalent to basic OVMS v2 firmware, but some advanced features (such as ACC, SMS control, etc) are not available yet. Firmware is far in advance of v2 in other aspects (such as built in web server, metrics, console, tcp/ip support, diagnostics, geofencing, scripting, etc). Firmware can be updated either Over The Air (OTA), by Micro SD card, or over USB interface. Vehicle support currently includes: Kia Soul EV, Nissan Leaf, Renault Twizy, and Tesla Roadster. If you do experience a problem, or need assistance, please start by talking to other OVMS v3.1 users/developers in your area. If you still can't solve the issue, then login to the www.openvehicles.com <http://www.openvehicles.com/> website and open a support ticket or forum topic. Software issues can be reported directly to the project GitHub issue tracker here: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues <https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues> Thank you for your support of the project. Open Vehicles

1 0