- OvmsDev - Open Vehicles

Re: [Ovmsdev] Nissan LEAF: HVAC Metrics
by Jaunius Kapkan 16 Feb '20

16 Feb '20

Thanks Mark, that explains it! Most likeley that is what happens. Will have to check the CAN messages and make something similar. Regards, Jaunius Kapkan [Sent from cellphone] > On 2020-02-14, at 11:15, Mark Webb-Johnson <mark(a)webb-johnson.net> wrote: >

2 2

New plugin: PwrMon: Trip Power Chart
by Tamás Kovács 15 Feb '20

15 Feb '20

I installed this plugin with the optional code to store the history, I set the sd card for history file, everything work fine until crash, After the the history file is empty. I use the plugin in a Peugeot iOn (mi vehicle type). This is plugin problem or the problem in the car code?

2 1

3.2.010-153-g5562cd4a/ota_1/eap crash
by Tamás Kovács 15 Feb '20

15 Feb '20

I installed this fw (3.2.010-153-g5562cd4a/ota_1/eap) at 2020.02.12 06:00. I have 4 crash at this time and always get the following backtrace: Last crash: abort() was called on core 0 Backtrace: 0x4008ae97 0x4008b12d 0x400e7164 0x40083d92 I use ovms.dexters-web.de/firmware/ota for update server and eap now. My car Is a Peugeot iOn (mi vehicle type) and my car vehicle id is: NNB635

2 1

Re: [Ovmsdev] [cesanta/mongoose] LWIP SO_REUSEADDR & ESP32 logging (#894) (fwd)
by Stephen Casner 13 Feb '20

13 Feb '20

What happened? Did Mark's commit 58942ce96c5e3e14edb53c804ffcdd4127e226e7 finally wake up cesanta? Are we going to resubmit all of our changes as separate pull requests? One person does that, or each author? And to the extent that they may be interdependent, so we need for them to be accepted in order? -- Steve ---------- Forwarded message ---------- Date: Wed, 12 Feb 2020 01:35:43 -0800 From: Sergey Lyubka <notifications(a)github.com> Reply-To: cesanta/mongoose <reply+ABG5G6FIED7L3BL25LSLI4F4KD4W7EVBNHHBDAFYO4(a)reply.github.com> To: cesanta/mongoose <mongoose(a)noreply.github.com> Cc: Stephen Casner <casner(a)acm.org>, Mention <mention(a)noreply.github.com> Subject: Re: [cesanta/mongoose] LWIP SO_REUSEADDR & ESP32 logging (#894) This PR contains several unrelated pieces - please split, one PR per single functionality piece. The PR should be against the `dev` branch, and one PR must have only one commit. -- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: https://github.com/cesanta/mongoose/pull/894#issuecomment-585116086

3 2

Great video describing OVMS from Andrew Till
by Mark Webb-Johnson 12 Feb '20

12 Feb '20

Here is a great video describing OVMS from Andrew Till: https://www.youtube.com/watch?v=Z9Fsbvd1Kfg <https://www.youtube.com/watch?v=Z9Fsbvd1Kfg> Regards, Mark.

1 0

Reverse connections (module -> developer)
by Mark Webb-Johnson 09 Feb '20

09 Feb '20

Seeking opinions (in particular Stephen, our ssh guru). As I (and others) are doing more work remotely (OVMS modules in cars, and trying to connect in remotely to diagnose, test, or develop), I am seeing the same issue come up often. If the car is on your own home WiFi, it is simple and easy. But if the car is elsewhere, on someone else’s WiFi, then connecting _to_ the car becomes hard. Firewalls, port forwarding, and all that mess. Security also becomes an issue (once ports are opened and forwarded). The core requirements seem to be: A way to get a proper shell. The ovms v2 protocol shell is ok, but quite painful to work with (especially as logs are not shown and there is no command expansion). A way to get CAN dumps out of the car. Can save to sd card, but can’t copy in/out. Both of these are simple TCP connections. The second issue (CAN dumps) is resolvable if the developer has a public address. Open the firewall, ’nc -l’ a port, and ‘can log start tcpclient …’ on the module. But a little kludgy, and doesn’t support SavvyCAN (which can only connect _to_ the module, not receive a connection _from_ the module). I can see three possible approaches to this: Extension of OVMS v2 protocol We could extend the OVMS v2 protocol to support a PIPE mode. Have it allow connections and data to be transferred over the v2 protocol link using simple messages. Then, the pipe could be used to tunnel SSH and CAN log connections. The same could be done with v3 over MQTT (the transport is different, but the console / port forwarding bits inside the ovms module are the same). The advantage here is that the OVMS v2 server becomes a man-in-the-middle broker. Both the car module and the developer connect to the OVMS v2 server to exchange data. No incoming connections, so everything can be dynamic. The disadvantage is security is fairly weak on that protocol. Very dated RC4 encryption and poor authentication. Leverage SSH SSH has a port forwarding facility built in, that wolfssh seems to support. It is also possible to do a reverse ssh client. The advantage here is security (very strong encryption and authentication). The disadvantage is complexity and the fact that the developer end needs to poke a hole in their firewall (and possibly do NAT port forwarding, etc) to allow the incoming connections from the car. STUNNEL / WireGuard / Mosh / VPN / etc Perhaps someone else knows of something suitable? The issues here are that the LWIP stack is not the easiest to work with. My initial preference is #1 or #2, but open to discussion… Regards, Mark. P.S. To save you time, the reverse SSH (using normal Unix like systems) works like this: Say developer at IP address A wants to connect to module at IP address B. On the module: $ ssh -R 19999:localhost:22 <user-A>@<A> (And go through authentication for B to ssh to A) Then, on the developer’s workstation: $ ssh -p 19999 <user-B>@localhost

6 9

An interesting little script
by Mark Webb-Johnson 09 Feb '20

09 Feb '20

An interesting little script to show the power/danger of javascript on the box. Regards, Mark

1 0

Re: [Ovmsdev] VW e-Up project
by Jaunius Kapkan 05 Feb '20

05 Feb '20

Great news! My relative just bought the 2014 e-up. So I might be able to help with testing at some point. Regards, Jaunius Kapkan [Sent from cellphone] > On 2020-02-05, at 11:49, Chris van der Meijden <chris(a)arachnon.de> wrote: >

1 0

OVMS v3 v3.2.010 Release to Early Access Program
by Mark Webb-Johnson 03 Feb '20

03 Feb '20

@Michael: Please release on your EU server when you have time… Today, we are pleased to release v3.2.010 to Early Access Program. A summary of the major changes is here: 2020-02-03 MWJ 3.2.010 OTA release - EGPIO: address multiple ports by input & output command - SmartED: issue #293 fixed change savestatus from store to sd Add ecoscore system to drive report and web interface like defunct smart web app. (added by frantek) - New command: "vfs df" -- show disk usage - Scripting API: added VFS.Load() & VFS.Save() - Scripting API: renamed HTTP.request() to HTTP.Request() for consistency - Scripting API: added OvmsMetrics.GetValues() - Web UI: editor extended by embedded Javascript evaluation - Webserver: /api/execute: support for Javascript evaluation - Scripting API: added OvmsConfig.GetValues() & OvmsConfig.SetValues() - Config: added dedicated "usr" param for plugin configurations - Scripting API: HTTP.request() added - SmartED: add BMS diagnose report New commands: xse rptdata get a Battery Status Report xse bmsdiag get Battery Diagnose Report - #225 Fix charge duration display in iOS App - #228 AutoFlashSD cleanup ovms3.done before rename - #293 Event queue overflow on startup - #299 Fix Tesla Roadster vehicle type for 2012 cars - #328 Tesla Roadster: Vehicle AWAKE metric not correct For full detail on all changes, check the GitHub revision history. 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'. You can choose the release level by setting 'config ota tag edge | eap | main', as one of: edge: Bleeding edge developer nightly-builds eap: Early Access Program (full releases, but with little public testing) main: Publicly tested full releases (the most stable) Thank you to all the open source developers who have contributed to this, and previous, releases, and thank you for your support of the project.

2 1

Cannot reset simcom stuck in PoweringOn state without removing module power
by Craig Leres 02 Feb '20

02 Feb '20

Maybe this has been discussed and I missed it but occasionally I'll get a module with the modem/simcom stuck in the PoweringOn state. Rebooting does not fix this. I thought I saw that you could reset the simcom with: power simcom off [wait a minute] power simcom on but that doesn't work. I turned up some logging: log monitor log level verbose simcom and I see this happen about every 30 seconds: I (2204129) simcom: State timeout, transition to 2 I (2204129) simcom: State: Enter PoweringOn state I (2204129) simcom: Power Cycle I thought this level of logging would let me see the results of command like: simcom muxtx 3 at+csq (signal quality) but I don't see anything after sending it. Is there a way to hardware reset the simcom? (Is there any reason this doesn't happen when the ovms module reboots?) Craig

4 23