- OvmsDev - Open Vehicles

Size limit on scp
by Mark Webb-Johnson 26 Mar '18

26 Mar '18

@Steve Is there any particular reason for this: $ scp build/ovms3.bin mark@ev914.local:/sd/ovms3.new scp: size unacceptable: 1841760 Can we increase to allow firmware copies to SD? Regards, Mark.

2 3

Leaf Range Calculations
by Tom Parker 24 Mar '18

24 Mar '18

Hi all, I'm looking to rearrange the leaf range calculations in v3 to use Wh per Gid and km/kWh as inputs to the calculations in order to mirror leaf spy. The v2 code used a simpler mile per gid calculation which is basically the same but didn't separate the two constants. LeafSpy appears to have a temperature compensation as well which I haven't yet tried to reproduce. The constants are configurable but question is, what should the default values be? v2's range calculation was based on 84 miles using 281 gids, or 218/135 = 2.08 gids per km. If one gid is 80Wh, then that's 166Wh/km or 6.01km/kWh. 80Wh per Gid and 6.01km/kWh is in the right ballpark, although Nissan's dashboard trip meter says 7.1km/kWh on my car. Does anyone have a reference to a better way to calculate range, or an opinion on what the default values should be in this calculation?

1 0

v3 at fasttech.com
by Michael Balzer 24 Mar '18

24 Mar '18

The v3.1 modules are listed at www.fasttech.com now. Mark, please mail me the coupon code when you get it, users begin asking for it. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

5 9

New Zealand Cellular Frequencies
by Tom Parker 24 Mar '18

24 Mar '18

Hi, In New Zealand we have 3 3G cell phone networks: 2degrees & Vodafone use 900MHz with 2100MHz infill. Spark uses 850MHz with 2100MHz infill. The European v3 modem supports 900MHz & 2100MHz while the US modem supports 850MHz & 1900MHz. I can confirm the European OVMS v3 does not work at all well on Spark's network in Auckland. It works well on 2degrees and I'm assuming also on Vodafone (but I haven't tested). The US OVMS v3 might work on Spark, but I don't know how many places Spark have holes in their 850MHz network that are filled by 2100MHz (possibly no such hole exists). The US model will probably also on Vodafone's 900MHz 2G network (which they say they are keeping up until 2025), but I haven't tested either of these. If you're in New Zealand, you might be able to get away with the US modem on Spark 3G or on Vodafone 2G. Otherwise you'll have to wait for the EU modem to be in stock again.

1 0

First “Real” ride with v3.0 in a Twizy
by Julien “JaXX” Banchet 24 Mar '18

24 Mar '18

Hi, Feedback on my First real ride after having had it sit >12h without a crash on my desk. I did have to auto wifi.mode off (instead of ap/apclient), otherwise nor v2 or v3 server wouldn't connect (ppp up, underground parking). Sidenote, before off-ing wifi, using my iPhone, web server went mute at a moment on ap: W (133945) websocket: WebSocketHandler[0x3fff15e0]: job queue overflow W (133975) websocket: WebSocketHandler[0x3fff15e0]: job queue overflow W (134225) websocket: WebSocketHandler[0x3fff15e0]: job queue overflow W (134475) websocket: WebSocketHandler[0x3fff15e0]: job queue overflow W (134725) websocket: WebSocketHandler[0x3fff15e0]: job queue overflow Otherwise RAM hovered around 70kB free. https://pastebin.com/EHBSHp4X (It doesn’t “stream” that much, I initially thought of regular crashes but monotonic keeps counting, I’ll have to figure a way to log the console somehow during a drive Getting usable despite the lack of a passive GPS :-) I really though I cut v2 before taking off, but got notifications from Michael’s server Volts: !SD:35mV !C1:+50mV !C2:+40mV !C3:+45mV !C4:+40mV !C5:+45mV !C6:-25mV !C7:-25mV !C8:-25mV !C9:-25mV !C10:-25mV !C11:-25mV !C12:-25mV !C13:-25mV !C14:+25mV Temps: SD:1C OK Ouch, I really need to let the cells balance sometimes. Trip 8.8km 21.0kph 81Wpk/23% SOC+42949656.0%=79.7%=== 22% 68Wpk/5%+++ 37% 3.0kps 222Wpk/0%--- 40% 2.0kps -43Wpk/433% :-) First ride metrics or Battery was really ~ -42949740% full :-) JB./.

2 1

First connection to car
by Stephen Casner 24 Mar '18

24 Mar '18

I took my OVMS v3.0 off the desk and into the car for the first time this evening. The only real hitch was that I had a hard time inserting the plug of the diagnostic cable into the car's connector. It seemed to be hitting a stop halfway in, whereas the old cable for my v1 unit goes in easily. Perhaps just a stiff release lever. In the middle of fiddling with connections I had a stack overflow crash in the tiT task, but after getting everything connected and doing a reset the wifi and modem came up successfully. Since I had not used the modem or Hologram SIM yet, I stopped wifi and then verified that my car status was making its way to the server and from there to the iPhone app. No news here; others have done much more testing than this. -- Steve

3 5

wifi issues
by Mark Webb-Johnson 21 Mar '18

21 Mar '18

I’m seeing problems with our wifi driver. If I stop, start, change modes, etc, etc, after a while it just seems unwilling to connect to access points. Even ‘wifi scan’ seems to stop working. A ‘module reset’ resolves the problem. I think the issue may be our use of init/deinit to continually load and unload the driver (and the associated two tasks), in a similar way to the mdns issues we had. I suggest to change as follows: Use the power control not-off / off to init / deinit the driver. Whenever the wifi mode is set (client, ap, scan, etc), power it on automatically. But don’t stop it unless explicitly told to by the user (power wifi off). Even ‘wifi mode off’ won’t unload the driver. Then use the existing commands ‘mode, scan, client, apclient, ap, etc’ to start / stop the actual wifi. This will mean that we will take a memory hit when we first start the wifi, and even ‘wifi mode off’ won’t free that memory. You would need to do a ‘power wifi off’ to do that. But, the upside is that we won’t be continually loading and unloading the wifi driver (which seems to be causing the issues). I’ll try it tonight, as my home is one of the areas I’m having the most problems with wifi. If it looks like it might break things, I’ll put it in a branch. Any comments / suggestions are welcome. Regards, Mark.

3 3

MDNS crash
by Stephen Casner 21 Mar '18

21 Mar '18

The crash below occurred right upon startup. I have not done anything with the auto start mechanism yet; I just have a script that starts wifi in client mode. I did not dig into this, and after a reset it did not repeat. I have not done more tests. -- Steve I (39) ovms_main: Set default logging level for * to WARN W (744) esp32wifi: AutoInit: using module password as AP password Welcome to the Open Vehicle Monitoring System (OVMS) - Async Console OVMS > CORRUPT HEAP: Bad head at 0x3ffec1f0. Expected 0xabba1234 got 0x3ffec2c8 assertion "head != NULL" failed: file "/Users/casner/src/github/esp-idf/components/heap/./multi_heap_poisoning.c", line 201, function: multi_heap_free abort() was called at PC 0x400fb243 on core 1 0x400fb243: __assert_func at /Users/ivan/e/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib/libc/stdlib/../../../.././newlib/libc/stdlib/assert.c:63 (discriminator 8) Backtrace: 0x4008f5d4:0x3ffeb990 0x4008f777:0x3ffeb9b0 0x400fb243:0x3ffeb9d0 0x4008f235:0x3ffeba00 0x40082712:0x3ffeba20 0x40082ca1:0x3ffeba40 0x4000bec7:0x3ffeba60 0x400dbeb9:0x3ffeba80 0x401f2105:0x3ffebaa0 0x401f212b:0x3ffebac0 0x401f4c9c:0x3ffebb00 0x401167eb:0x3ffebb30 0x4011681d:0x3ffebb50 0x40116c3c:0x3ffebb70 0x400e88a9:0x3ffebbb0 0x400e8b45:0x3ffebbe0 0x400ed570:0x3ffebc70 0x400ed591:0x3ffebcc0 0x4008f5d4: invoke_abort at /Users/casner/src/github/esp-idf/components/esp32/./panic.c:648 0x4008f777: abort at /Users/casner/src/github/esp-idf/components/esp32/./panic.c:648 0x400fb243: __assert_func at /Users/ivan/e/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib/libc/stdlib/../../../.././newlib/libc/stdlib/assert.c:63 (discriminator 8) 0x4008f235: multi_heap_free at /Users/casner/src/github/esp-idf/components/heap/./multi_heap_poisoning.c:326 0x40082712: heap_caps_free at /Users/casner/src/github/esp-idf/components/heap/./heap_caps.c:388 0x40082ca1: _free_r at /Users/casner/src/github/esp-idf/components/newlib/./syscalls.c:42 0x400dbeb9: esp_timer_delete at /Users/casner/src/github/esp-idf/components/esp32/./esp_timer.c:162 0x401f2105: _mdns_stop_timer at /Users/casner/src/github/esp-idf/components/mdns/./mdns.c:4510 0x401f212b: _mdns_service_task_stop at /Users/casner/src/github/esp-idf/components/mdns/./mdns.c:4510 0x401f4c9c: mdns_free at /Users/casner/src/github/esp-idf/components/mdns/./mdns.c:4185 0x401167eb: OvmsMDNS::StopMDNS() at /Users/casner/src/github/ovms/vehicle/OVMS.V3/components/ovms_mdns/src/ovms_mdns.cpp:111 0x4011681d: OvmsMDNS::NetworkDown(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*) at /Users/casner/src/github/ovms/vehicle/OVMS.V3/components/ovms_mdns/src/ovms_mdns.cpp:64 0x40116c3c: void std::_Mem_fn_base<void (OvmsMDNS::*)(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*), true>::operator()<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*, void>(OvmsMDNS*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&, void*&&) const at /Users/casner/src/github/esp-idf/xtensa-esp32-elf/xtensa-esp32-elf/include/c++/5.2.0/functional:600 (inlined by) void std::_Bind<std::_Mem_fn<void (OvmsMDNS::*)(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*)> (OvmsMDNS*, std::_Placeholder<1>, std::_Placeholder<2>)>::__call<void, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&, void*&&, 0u, 1u, 2u>(std::tuple<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&, void*&&>&&, std::_Index_tuple<0u, 1u, 2u>) at /Users/casner/src/github/esp-idf/xtensa-esp32-elf/xtensa-esp32-elf/include/c++/5.2.0/functional:1074 (inlined by) void std::_Bind<std::_Mem_fn<void (OvmsMDNS::*)(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*)> (OvmsMDNS*, std::_Placeholder<1>, std::_Placeholder<2>)>::operator()<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*, void>(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&, void*&&) at /Users/casner/src/github/esp-idf/xtensa-esp32-elf/xtensa-esp32-elf/include/c++/5.2.0/functional:1133 (inlined by) std::_Function_handler<void (std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*), std::_Bind<std::_Mem_fn<void (OvmsMDNS::*)(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*)> (OvmsMDNS*, std::_Placeholder<1>, std::_Placeholder<2>)> >::_M_invoke(std::_Any_data const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&, void*&&) at /Users/casner/src/github/esp-idf/xtensa-esp32-elf/xtensa-esp32-elf/include/c++/5.2.0/functional:1871 0x400e88a9: std::function<void (std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*)>::operator()(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*) const at /Users/casner/src/github/esp-idf/xtensa-esp32-elf/xtensa-esp32-elf/include/c++/5.2.0/functional:2271 0x400e8b45: OvmsEvents::SignalEvent(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*) at /Users/casner/src/github/ovms/vehicle/OVMS.V3/main/./ovms_events.cpp:155 0x400ed570: OvmsNetManager::MongooseTask() at /Users/casner/src/github/ovms/vehicle/OVMS.V3/main/./ovms_netmanager.cpp:322 0x400ed591: MongooseRawTask(void*) at /Users/casner/src/github/ovms/vehicle/OVMS.V3/main/./ovms_netmanager.cpp:306 Entering gdb stub now. $T0b#e6GNU gdb (crosstool-NG crosstool-ng-1.22.0-80-g6c4433a) 7.10 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=x86_64-build_apple-darwin16.3.0 --target=xtensa-esp32-elf". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /Users/casner/src/github/ovms/vehicle/OVMS.V3/build/ovms3.elf...done. Remote debugging using /dev/cu.SLAB_USBtoUART 0x4008f5d4 in invoke_abort () at /Users/casner/src/github/esp-idf/components/esp32/./panic.c:139 139 *((int *) 0) = 0; (gdb) bt #0 0x4008f5d4 in invoke_abort () at /Users/casner/src/github/esp-idf/components/esp32/./panic.c:139 #1 0x4008f77a in abort () at /Users/casner/src/github/esp-idf/components/esp32/./panic.c:148 #2 0x400fb246 in __assert_func ( file=0x3ffb3730 "/Users/casner/src/github/esp-idf/components/heap/./multi_heap_poisoning.c", line=201, func=<optimized out>, failedexpr=0x3ffb3720 "head != NULL") at ../../../.././newlib/libc/stdlib/assert.c:63 #3 0x4008f238 in multi_heap_free (heap=0x3ffe4350, p=0x3ffec1fc) at /Users/casner/src/github/esp-idf/components/heap/./multi_heap_poisoning.c:201 #4 0x40082715 in heap_caps_free (ptr=0x3ffec1fc) at /Users/casner/src/github/esp-idf/components/heap/./heap_caps.c:262 #5 0x40082ca4 in _free_r (r=0x3ffebdd4, ptr=0x3ffec1fc) at /Users/casner/src/github/esp-idf/components/newlib/./syscalls.c:42 #6 0x4000beca in ?? () #7 0x400dbebc in esp_timer_delete (timer=0x3ffec1fc) at /Users/casner/src/github/esp-idf/components/esp32/./esp_timer.c:162 #8 0x401f2108 in _mdns_stop_timer () at /Users/casner/src/github/esp-idf/components/mdns/./mdns.c:4032 #9 0x401f212e in _mdns_service_task_stop () at /Users/casner/src/github/esp-idf/components/mdns/./mdns.c:4081 #10 0x401f4c9f in mdns_free () at /Users/casner/src/github/esp-idf/components/mdns/./mdns.c:4185 #11 0x401167ee in OvmsMDNS::StopMDNS (this=0x3ffb45c8 <MyMDNS>) at /Users/casner/src/github/ovms/vehicle/OVMS.V3/components/ovms_mdns/src/ovms_mdns.cpp:111 #12 0x40116820 in OvmsMDNS::NetworkDown (this=0x3ffb45c8 <MyMDNS>, event=..., data=0x0) at /Users/casner/src/github/ovms/vehicle/OVMS.V3/components/ovms_mdns/src/ovms_mdns.cpp:64 #13 0x40116c3f in std::_Mem_fn_base<void (OvmsMDNS::*)(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*), true>::operator()<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*, void>(OvmsMDNS*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&, void*&&) const (__object=<optimized out>, this=<optimized out>) at /Users/casner/src/github/esp-idf/xtensa-esp32-elf/xtensa-esp32-elf/include/c++/5.2.0/functional:600 #14 std::_Bind<std::_Mem_fn<void (OvmsMDNS::*)(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*)> (OvmsMDNS*, std::_Placeholder<1>, std::_Placeholder<2>)>::__call<void, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&, void*&&, 0u, 1u, 2u>(std::tuple<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&, void*&&>&&, std::_Index_tuple<0u, 1u, 2u>) ( __args=<unknown type in /Users/casner/src/github/ovms/vehicle/OVMS.V3/build/ovms3.elf, CU 0x2f4c41, DIE 0x3048f6>, this=<optimized out>) at /Users/casner/src/github/esp-idf/xtensa-esp32-elf/xtensa-esp32-elf/include/c++/5.2.0/functional:1074 #15 std::_Bind<std::_Mem_fn<void (OvmsMDNS::*)(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*)> (OvmsMDNS*, std::_Placeholder<1>, std::_Placeholder<2>)>::operator()<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*, void>(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&, void*&&) (this=<optimized out>) at /Users/casner/src/github/esp-idf/xtensa-esp32-elf/xtensa-esp32-elf/include/c++/5.2.0/functional:1133 #16 std::_Function_handler<void (std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*), std::_Bind<std::_Mem_fn<void (OvmsMDNS::*)(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*)> (OvmsMDNS*, std::_Placeholder<1>, std::_Placeholder<2>)> >::_M_invoke(std::_Any_data const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&&, void*&&) (__functor=..., __args#0=<optimized out>, __args#1=<optimized out>) at /Users/casner/src/github/esp-idf/xtensa-esp32-elf/xtensa-esp32-elf/include/c++/5.2.0/functional:1871 #17 0x400e88ac in std::function<void (std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*)>::operator()(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, void*) const ( this=0x3ffcaef0, __args#0=..., __args#1=0x0) at /Users/casner/src/github/esp-idf/xtensa-esp32-elf/xtensa-esp32-elf/include/c++/5.2.0/functional:2271 #18 0x400e8b48 in OvmsEvents::SignalEvent (this=0x3ffb4290 <MyEvents>, event=..., data=0x0) at /Users/casner/src/github/ovms/vehicle/OVMS.V3/main/./ovms_events.cpp:155 #19 0x400ed573 in OvmsNetManager::MongooseTask (this=0x3ffb4314 <MyNetManager>) ---Type <return> to continue, or q <return> to quit--- at /Users/casner/src/github/ovms/vehicle/OVMS.V3/main/./ovms_netmanager.cpp:322 #20 0x400ed594 in MongooseRawTask (pvParameters=0x3ffb4314 <MyNetManager>) at /Users/casner/src/github/ovms/vehicle/OVMS.V3/main/./ovms_netmanager.cpp:306 (gdb)

4 22

Memory owned by deceased tasks
by Stephen Casner 20 Mar '18

20 Mar '18

I removed my startup script that brought up wifi in client mode. I let auto init wifi run and bring up the associated services and did a "module tasks" command to populate the task map. Then I manually started wifi in client mode, which caused the running wifi and NetManTask to stop first, along with the servers, and then all come up again. At that point I ran "module memory" and saw that there were two deceased tasks still holding memory, a wifi task and a NetManTask. I then stopped wifi and started it in client mode a second time. The second deceased wifi did not hold onto any memory, but the second deceased NetManTask did: OVMS# mo m = Free 8-bit 32684/283144, 32-bit 27552/55828, SPIRAM 0/0 --Task-- Total DRAM D/IRAM IRAM SPIRAM +/- DRAM D/IRAM IRAM SPIRAM no task* 5276 0 0 0 +0 +0 +0 +0 main* 40076 0 0 0 +0 +0 +0 +0 NetManTask* 0 264 0 0 +0 +0 +0 +0 wifi* 0 1396 0 0 +0 +0 +0 +0 NetManTask* 0 264 0 0 +0 +0 +0 +0 esp_timer 55112 0 644 0 +0 +0 +0 +0 eventTask 0 7620 0 0 +0 +0 +0 +0 ipc0 10848 0 0 0 +0 +0 +0 +0 ipc1 12 0 0 0 +0 +0 +0 +0 Tmr Svc 0 27812 0 0 +0 +0 +0 +0 Housekeeping 17912 32628 0 0 +0 +0 +0 +0 tiT 136 1748 0 0 +0 +0 +0 +0 AsyncConsole 0 16384 27488 0 +0 +0 +0 +0 mdns 0 108 0 0 +0 +0 +0 +0 wifi 0 1596 0 0 +0 +0 +0 +0 NetManTask 0 2200 0 0 +0 +0 +0 +0 So, I don't know if the memory for the deceased wifi and NetManTask tasks is truly leaked or represents objects still in use elsewhere. -- Steve

1 0

OVMS 3.1 Production
by Mark Webb-Johnson 20 Mar '18

20 Mar '18

Both the 3.0 box in my car, and 3.1 on my desk, are running fine with the firmware I built and tagged this morning as 3.1.000. That version is now available on api.openvehicles.com <http://api.openvehicles.com/> as an OTA update. I’ve sent that to the factory, along with the QC instructions we have. It is not perfect, but it is good enough for a factory starting point. I’ve also sent the factory the production/qc/production_notes.txt for production/QC steps. Pressure is off a bit now. We have some time to work on documentation, stability and fine-tuning (which is what I will be concentrating on for the next few weeks). The OTA update system works well (I had a chance to play with Michael’s web based firmware update, and that went well), and should be usable for people to do OTA updates when they get the modules. Feature wise, a web server OTA using file upload would be good. I’m finding Access Point mode very useful to get into the box from an iPad and play with it. Still have to work out how to get the module to connect to my iPhone hotspot (which may be a better way of doing things). A single page QuickStart on the webserver would also be good to have; something people go to and enter password, vehicle type, vehicle ID, server, etc - all on one page. I started the user documentation, and there are quite a lot of steps to go through, on a bunch of different screens, to setup the box. To set user expectations, there is a knownissues.txt file where I would like to keep a TODO list of stuff people want, as well as a list of what we can’t do that v2 could. That currently contains: Open Vehicle Monitor System v3 - Known issues * Wifi APCLIENT mode is to be considered experimental. * SSH, TELNET, and WEBSERVER all register listeners for incoming calls. There is a possible security issue here as those calls may come over cellular networks (not just wifi). There is no firewalling of these calls. It seems that the correct approach to this is to validate the destination IP to make sure it is a wifi interface IP address; but this is not currently done. * Bluetooth is not currently supported. * Vehicle: Tesla Roadster limitations (vs 2.x): * Cooldown not currently supported. * Charge timer not currently supported. * Charge time predictor not currently supported. * VDS vehicle errors not currently supported. * Digital speedometer feature not currently supported. * CAC request not currently supported. * Vehicle: Kyburz not currently implemented in 3.x. * Vehicle: Mitdubishi iMiev not currently implemented in 3.x. * Vehicle: NissanLeaf: * Remote telemetry wake-up for pre-2016 vehicles not currently supported (as required hardware wakeup circuit). * Vehicle: Tazzari not currently implemented in 3.x. * Vehicle: Think City not currently implemented in 3.x. * Vehicle: Volt/Ampera not currently implemented in 3.x. * Vehicle: Renault Zoe not currently implemented in 3.x. * Advanced Charge control not currently implemented in 3.x. Note that scripting can go someway towards providing equivalent functionality. I’d appreciate it if people could update that as necessary with things they want or that v2 did. Thanks to everyone involved for getting to where we are. I’m expecting hardware to be coming out of the factory (and in my hands) early next week. Regards, Mark.

1 0