- OvmsDev - Open Vehicles

Vehicle support for VW MEB platform
by ovmsdev 24 Apr '22

24 Apr '22

Hi all, I'm new to OVMS, just ordered my kit. Sinc e I own an VW ID.4, I'd like to add support for the VW MEB platform, which includes the Skoda Enyaq, Volkswagen ID.x, Audi Q4 etron, Cupra Born. Anyone else interesting in helping out? I have found some resources that will help us get started: VW ID3 support for the evDash: https://github.com/nickn17/evDash/blob/master/src/CarVWID3.cpp ID.3 support for the UDS Decoder tool: https://www.goingelectric.de/forum/viewtopic.php?p=1758362&sid=f3168951a5a6… https://github.com/TUMFTM/uds-decoder/blob/master/python_can_recorder/ids.t… Quickest way would be to create an EBC description for it... but I guess for full feature support we'll need an additional vehicle to the source code. Which of the existing vehicles would be best suited as a starting point: vweup? This uses two CAN connectors though. Kind regards, Wessel

3 2

Re: [Ovmsdev] MG5 - I'd like to help
by Martin Klefas-Stennett 05 Apr '22

05 Apr '22

I just got an MG5 LR and while any actual development work is completely beyond me, I’m happy to help with collecting data and such if that’s useful? I noticed in the Docs that it mentions the MG5 Specifically as “not yet supported in this build” though, so perhaps you’re all past the stage where someone unskilled could be useful? Thanks in advance. Regards, Martin Klefas-Stennett. ________________________________ From: Martin Klefas-Stennett Sent: 13 February 2022 22:22 To: ovmsdev(a)lists.openvehicles.com <ovmsdev(a)lists.openvehicles.com> Subject: MG5 - I'd like to help I just got an MG5 LR and while any actual development work is completely beyond me, I’m happy to help with collecting data and such if that’s useful? I noticed in the Docs that it mentions the MG5 Specifically as “not yet supported in this build” though, so perhaps you’re all past the stage where someone unskilled could be useful? Thanks in advance.

1 0

Update zlib to version 1.2.12
by Michael Balzer 02 Apr '22

02 Apr '22

Everyone, I've just updated our zlib clone (https://github.com/openvehicles/zlib) to version 1.2.12, fixing a serious security issue (out of bounds access by extracting malicious ZIP data). To follow you need to do… git submodule update --recursive …after your next pull/fetch. From https://www.zlib.net/: > > Version 1.2.12 has these key improvements over 1.2.11: > > * Fix a deflate bug when using theZ_FIXEDstrategy that can result in > out-of-bound accesses. > * Fix a deflate bug when the window is full indeflate_stored(). > * Speed up CRC-32 computations by a factor of 1.5 to 3. > * Use the hardware CRC-32 instruction on ARMv8 processors. > * Speed upcrc32_combine()with powers of/x/tables. > * Addcrc32_combine_gen()andcrc32_combine_op()for fast combines. > > /Due to the bug fixes, any installations of 1.2.11 should be replaced > with 1.2.12./ I suggest also checking your other projects for inclusions of zlib. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

1 0

3.3.002 to EAP
by Mark Webb-Johnson 20 Mar '22

20 Mar '22

I have today built 3.3.002 (based one latest edge): Released 3.3.002 to v3.1/eap (and v3.2/eap via symlink) Released 3.3.002 to v3.3/eap Released 3.3.002 to v3.3/main Regards, Mark.

2 2

Newly installed 4G modem getting DeniedRegistration
by Stephen Casner 15 Mar '22

15 Mar '22

On Saturday I installed a new 4G modem in Timothy Rodgers' OVMS (he is "Timothy" on TMC). When I did mine, it came right up on AT&T, but Timothy's is repeatedly failing. Both his and my OVMS are running 3.3.002. Both of us are using the Hologram SIM. At first, it looked like I might need to set the new IMEI at Hologram somehow because the old IMEI for the 3G modem still showed. Later, though, the IMEI changed to the new one, but the connection still did not come up. I suggested that Timothy contact Hologram support, which he did. The reply from the support agent is below. It says there have been many momentary connects and disconnects with zero bytes transferred. Has anything like this been seen elsewhere? Are there other tests we should do? -- Steve ---------- Forwarded message ---------- From: Rudy R (Hologram) <support(a)teamhologram.zendesk.com> Sent: Monday, March 14, 2022 6:41 AM To: Timothy Rodgers <timothy(a)cal.berkeley.edu> Subject: [Hologram] Re: My OVMS (On Vehicle Monitoring System) has been wo... ##- Please type your reply above this line -## Your request (147988) has been updated. To add additional comments, reply to this email. <https://secure.gravatar.com/avatar/2a79f7d3cba57758d4d2dbbb139c7bc9?size=40…> Rudy R (Hologram) Mar 14, 2022, 8:40 CDT Hi Timothy, Thanks so much for contacting Hologram support! My name is Rudy and I'd be happy to help with your request. After reviewing your Hologram admin dashboard I found an indication your device has at some points connected to the AT&T cellular network, however no data is passing after a connection is made with the network. A device with many zero-byte sessions in quick succession indicates excessive and unnecessary reconnects. This may be caused by improper connection logic by the device firmware or the cellular module's current configuration. For example, a device constantly trying to connect despite successfully opening data sessions will result in multiple zero-byte sessions over time. You may also find this Help Center <http://support.hologram.io/> article called, <https://support.hologram.io/hc/en-us/articles/360040668834-What-is-a-Sessio…> "What is a Session without Data and what causes it." useful in diagnosing the problem. If the article's recommendations do not help resolve the issue, to further help diagnose the connectivity issues with the connecting network, can you please run these modem diagnostics <https://support.hologram.io/hc/en-us/articles/360035697393-Modem-SIM-annota…> and send back the results? If you prefer, you can also run this script <https://support.hologram.io/hc/en-us/articles/4417363338647> for the diagnostics to automatically execute. The diagnostics will help our engineering team pinpoint possible causes and in most cases we can at least get you on the right path! Looking forward to your response! Rudy Hologram Support | support(a)hologram.io <mailto:support@hologram.io> For more information check out our awesome Help Center <https://support.hologram.io/hc/en-us> <https://secure.gravatar.com/avatar/983069bffb928389d285266979d0d8a5?size=40…> Timothy Rodgers Mar 12, 2022, 23:29 CST My OVMS (On Vehicle Monitoring System) has been working fine with my long standing Hologram account. Because of the ending of 2G and the addition of 5G it was recommended to put a new card in the device. An engineer who is a friend did this for the identical device in his car and it worked fine. When my new card was installed in my device and connected in my car, it worked when connected my home network but not with cell when away from home. When I typed in 'cell status' as a message on my device the reply was State: NetWait, Mux: Status up, and PPP:not running and GPS: not running. The PPP and GPS ran fine on my friends car. He was not sure why mine didn't work or what to do next and suggested I contact Hologram. I would appreciate your help. Thank you. My org ID 3616 ------------------ Submitted from: https://www.hologram.io/ This email is a service from Hologram. [660GYP-L5VDZ]

1 0

OVMS App Charge Status
by Michael Iimura 14 Mar '22

14 Mar '22

With my new RAV4 EV port, every time there is a charge status change, the OVMS App pops up a notification that Charging Stopped. Even when a charging session is starting, the notification says Stopped. What do I need to set so that the notification indicates the correct state change? Also the Vehicle status pane on the web server Status page always says "Not Charging", even when the ms_v_charge_state is "charging" and ms_v_charge_inprogress is TRUE. Also, where do I send my stock image so it can be included in the app? Thanks, - Mike

2 1

Build / release infrasructure
by Mark Webb-Johnson 07 Mar '22

07 Mar '22

My directory structure for firmware releases on api.openvehicles.com <http://api.openvehicles.com/>: /firmware/ota v3.0 main v3.1 edge pre -> eap eap main v3.2 -> v3.1 v3.3 edge -> ……/firmware/ota/v3.1/edge pre -> ……/firmware/ota/v3.1/pre eap main I build v3.1/edge automatically each night. cd $IDF_PATH git config pull.rebase false git pull git submodule init git submodule update cd $OVMS_TREE git config pull.rebase false git fetch --tags git pull git submodule init git submodule update cd $OVMS_PATH make defconfig make size >$INFO_PATH echo >>$INFO_PATH git log --graph --decorate --pretty=oneline --abbrev-commit --all -n 10 >>$INFO_PATH cp build/ovms3.bin $REL_PATH/${REV_NEW}.ovms3.bin cp build/ovms3.elf $REL_PATH/${REV_NEW}.ovms3.elf echo $REV_NEW >${REL_PATH}/ovms3.new echo `/usr/bin/date -u` "Automated build ($HOSTNAME)" >>${REL_PATH}/ovms3.new echo >>${REL_PATH}/ovms3.new cat $INFO_PATH >>${REL_PATH}/ovms3.new rm -f ${REL_PATH}/ovms3.bin ln -s ${REL_PATH}/${REV_NEW}.ovms3.bin ${REL_PATH}/ovms3.bin rm -f ${REL_PATH}/ovms3.elf ln -s ${REL_PATH}/${REV_NEW}.ovms3.elf ${REL_PATH}/ovms3.elf mv ${REL_PATH}/ovms3.new ${REL_PATH}/ovms3.ver The v3.1/pre, */eap, and */main are all manually released when ready. My directory structure for plugin releases on api.openvehicles.com <http://api.openvehicles.com/>: /plugins plugins.json plugins.rev abrp auxbatmon chgind chgthrottle edimax foglight helloworld pwrmon regenmon repidscan retools I build plugins automatically each night. See support/buildplugins.pl That is what I do today. At some point, we will build the v3.3 tree separately (rather than symlink to v3.1), to take advantage of a ESP32 rev3 specific sdkconfig. Regards, Mark.

1 0

Repeated WDT crashes after upgrade to 3.3 with 4G
by Stephen Casner 07 Mar '22

07 Mar '22

I installed version 3.3.001-285 from edge on my OVMS v3.1 unit before replacing the 3G modem with a 4G modem. Upon rebooting with the unit still on the bench I noticed that the unit was crashing every three minutes with a watchdog timeout: I (112275) gsm-mux: Start MUX I (112285) gsm-mux: Channel #0 is open I (112295) gsm-mux: Channel #1 is open I (112305) gsm-mux: Channel #2 is open I (112315) gsm-mux: Channel #3 is open I (112325) gsm-mux: Channel #4 is open I (113265) cellular: State: Enter NetWait state I (122265) housekeeping: System considered stable (RAM: 8b=81540-82392 32b=12344 SPI=3454300-3456824) I (122505) webserver: HTTP GET / I (122535) webserver: HTTP GET /apple-touch-icon.png I (122555) webserver: HTTP GET /status I (123265) ovms-server-v2: Send MP-0 h1,0,*-OVM-DebugCrash,0,2592000,3.3.001-285-g601f2a70/ota_1/edge (build idf v3.3.4-848-g1ff5e24b1 Feb 20 2022 00:04:30),2,Crash,12,12,2,0,abort(),0,,0x4008ddca 0x4008e065 0x400e9608 0x40084176 ,6,Task watchdog,ticker.1,esp32wifi,0,IDLE0,OVMS WIFI BLE BT cores=2 rev=ESP32/1; MODEM SIM7600 I (123295) cellular: Network Registration status: RegisteredRoaming I (123295) cellular: Network Provider is: AT&T Hologram I (123595) ovms-server-v2: Incoming Msg: MP-0 h1 I (124265) cellular: State: Enter NetStart state I (129845) webserver: HTTP POST /status I (129845) webserver: HandleLogin: 'admin' logged in, sid c3bb26091e718ad I (129875) webserver: HTTP GET /status I (130035) webserver: HTTP GET /menu W (178175) websocket: WebSocketHandler[0x3f8b19f0]: job queue overflow detected OVMS> E (185265) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time: E (185265) task_wdt: - IDLE0 (CPU 0) E (185265) task_wdt: Tasks currently running: E (185265) task_wdt: CPU 0: Tmr Svc E (185265) task_wdt: CPU 1: IDLE1 E (185265) task_wdt: Aborting. abort() was called at PC 0x400e9608 on core 0 ELF file SHA256: 2d4b51699f53abce Backtrace: 0x4008ddca:0x3ffb0aa0 0x4008e065:0x3ffb0ac0 0x400e9608:0x3ffb0ae0 0x40084176:0x3ffb0b00 Rebooting... I was hoping that when I put the module back into the car with all the right inputs on its data cable that this problem would not continue, but sad to say the crashes remain the same. I have not heard about this issue for others who have upgraded to 3.3 and 4G. Any suggestions? Here are a couple of examples of the boot status: auge1> ssh ovms Welcome to the Open Vehicle Monitoring System (OVMS) - SSH Console Firmware: 3.3.001-285-g601f2a70/ota_1/edge Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1; MODEM SIM7600 OVMS# boot Last boot was 152 second(s) ago Time at boot: 2022-03-02 14:29:11 PST This is reset #1 since last power cycle Detected boot reason: EarlyCrash (12/12) Reset reason: Task watchdog (6) Crash counters: 1 total, 1 early Last crash: abort() was called on core 0 Backtrace: 0x4008ddca 0x4008e065 0x400e9608 0x40084176 Event: ticker.1@esp32wifi 0 secs WDT tasks: IDLE0 Version: 3.3.001-285-g601f2a70/ota_1/edge (build idf v3.3.4-848-g1ff5e24b1 Feb 20 2022 00:04:30) Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1; MODEM SIM7600 OVMS# packet_write_wait: Connection to 192.168.1.74 port 22: Broken pipe auge2> ssh ovms Welcome to the Open Vehicle Monitoring System (OVMS) - SSH Console Firmware: 3.3.001-285-g601f2a70/ota_1/edge Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1 OVMS# boot Last boot was 76 second(s) ago Time at boot: 2022-03-02 14:32:18 PST This is reset #2 since last power cycle Detected boot reason: Crash (12/12) Reset reason: Task watchdog (6) Crash counters: 2 total, 0 early Last crash: abort() was called on core 0 Backtrace: 0x4008ddca 0x4008e065 0x400e9608 0x40084176 Event: ticker.1@esp32wifi 0 secs WDT tasks: IDLE0 Version: 3.3.001-285-g601f2a70/ota_1/edge (build idf v3.3.4-848-g1ff5e24b1 Feb 20 2022 00:04:30) Hardware: OVMS WIFI BLE BT cores=2 rev=ESP32/1 OVMS# OVMS# packet_write_wait: Connection to 192.168.1.74 port 22: Broken pipe -- Steve

5 27

4G Modem Module *requires* 3.3 firmware
by Mark Webb-Johnson 26 Feb '22

26 Feb '22

Just a reminder note to people upgrading existing v3.1 and v3.2 OVMS to 4G: You will need to install the v3.3 firmware (currently version 3.3.001) to support the new 4G modem option. That version is pre-installed on all new v3.3 kits, but not yet released to 'main' release level for everyone. The solution is to set the release level to 'edge', and you will see the v3.3 firmware available for install. You can set back to 'main' after install.

2 3

OVMS v3.3 hardware
by Mark Webb-Johnson 23 Feb '22

23 Feb '22

For the 4G modem options we need to go through FCC, CE, and ROHS certification. Minimising/eliminating the changes to the main board simplifies this (and brings down the exorbitant costs) but if there is anything urgent / necessary, now is the time to do it. The goal here is to maintain 100% compatibility with existing OVMS main boards, to keep this is a simple and relatively cheap upgrade of the modem board. So far, I have come up with this minimal list: Main board v3.3: Improve soldering of micro USB port. Bigger solder pads, and more solder to secure it better. Modem board v1.3: Add support for SIM7600 module. Modem board v1.3: Fix support for DTR sleep/awake support. Is there anything else required for this update? Regards, Mark.

4 37