- OvmsDev - Open Vehicles

US Stock
by Mark Webb-Johnson 26 Apr '20

26 Apr '20

I’m pleased to say that I’ve come to an agreement with Carl Medlock (at Medlock Tesla Service in Seattle, USA) to stock OVMS US kits (primarily for Tesla Roadster owners in USA). Carl was a long-term Tesla employee, and for the past 10 years has run a garage with his sons looking after Tesla Roadsters in the USA. https://medlockandsons.com/ <https://medlockandsons.com/> Carl’s team will be able to handle local distribution of OVMS in the USA, as well as installation for those users in the Seattle area that need it. He should have his first stock later this week. Regards, Mark

1 0

3.2.011 BUG for MIEV based cars
by Michael Eric Menk 26 Apr '20

26 Apr '20

Charge-status disappeared on update to 3.2.011 . The SOC is read, but it do not know that the car is charging. As you can see from the screenshot, OVMS sees the inncomming charge into the battery, but the state is "Not charging" -- Michael Eric Menk

2 12

make apt-flash destination location?
by Eddy Vromen 22 Apr '20

22 Apr '20

Hi All, Quick question: I am experimenting with some code changes and i am using the sdcard method to get a new .bin file on the device. It will automatically alternate between the 2 OTA image loactions which is great. I would like to make this process a little less labor intensive: When i use "make apt-flash", where does the code get flashed? With this method, how can i pick between the 2 OTA image locations? Thanks, Eddy

2 3

Modem unable to power cycle successfully
by Mark Webb-Johnson 15 Apr '20

15 Apr '20

I’ve seen cases where the modem will not come up correctly, even following a power cycle. But, a reset of the OVMS module (ESP32) solves the problem. This really makes no sense, unless something is getting corrupted inside the UART / EGPIO driver itself. The modem module status is not changed during an ESP32 reset - only the software side of it running in the ESP32. Thomas Heder has reported some success with using uart_flush to flush the UART ring buffer when power cycling the modem. Flushing the buffer would not seem to affect this, as we use ‘AT’ to look for an OK response during power up check anyway; but perhaps something is corrupt in the ring buffer itself, so using uart_flush clears that problem. Note that uart_flush is an alias for uart_flush_input, and the source code does seem to show a complete reset of the ring buffer pointers with interrupts disabled (not just a simple emptying). Anyway, the approach does not seem to do any harm, so I have added it to the latest code and let’s see if it improves the situation. https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/354 <https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/issues/354> Regards, Mark.

1 0

Ready for 3.2.011?
by Mark Webb-Johnson 13 Apr '20

13 Apr '20

It is time for a 3.2.011 OTA release. Things seem stable for me now, and it would be good to get these releases out every month or so. Is there anything else that needs to be in this? If so, please commit and/or pull request. I would like to get this release out to EAP over the weekend. Regards, Mark.

5 15

Crash random time
by Tamás Kovács 13 Apr '20

13 Apr '20

Car Peugeot iOn used TRIO vehicle type. Last crash: abort() was called on core 0 Backtrace: 0x4008b03f 0x4008b2d5 0x400e709c 0x40083d96 Version: 3.2.011-172-g51b71688/ota_1/eap (build idf v3.3-beta3-776-g3d198cd50 Apr 11 2020 11:57:14) Crash at 2020.04.11 18:59 and 20:59, 04.12 09:06 Created a log file the first 2 time only info level, but last with debug level. And another on OVMS SHELL is see many dropped ticker event before crash, but not show in log file.

3 4

Deadlock on module reset
by Michael Balzer 13 Apr '20

13 Apr '20

Chris informed me my commit bfcb1be97bb8fbfda9913f9094ba71ef9c94c7e8 introduced a deadlock in the module shutdown. My tests showed it doesn't always occur. A first simple analysis of the locks set during shutdown shows there is a race between networking tasks reacting to the "system.shuttingdown" event and the events task processing the next ticker event. It seems the subsystems which registered for processing events try to deregister while still allowing to process the next event delivered, leading to the deadlock. I think fixing this needs a thorough rework of the shutdown deregistration processes. As the event mutex was meant to fix a potential race condition, I've reverted the change for now. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

1 0

Flash memory and developement setup
by Eddy Vromen 11 Apr '20

11 Apr '20

HI All, I have a question about the flash memory of the ESP32. I read that the ESP32 uses 16Mb of external flash memory and in the schematics on page 27 there is a flash memory chip. However, in the latest v3.2 schematics there is no external flash chip. Am I correct to assume that the 16Mb of memory is on the module now? How does this impact the e-fuse settings? Another question that came up while setting up a development environment: The version of esp-idf thats used by the OVSM project uses the Mingw32 environment. Based on my limited exposure to using this environment, its very slow compared to compiling esp-idf code under e.g. platformio under VSCode. How are the core developers dealing with this slowness? Is it at all possible, if i could force platformio to use the correct the idf-esp libraries, to compile the OVMS code in a more recent environment that uses cmake and ninja? Thanks, Eddy

4 4

can log crash
by Tamás Kovács 11 Apr '20

11 Apr '20

Hi! i want to create some log file with ovms and savvycan, but ovms all time crashed very often. i start the logging with the following command: can log start tcpserver transmit gvret-b :23 424 I now want only the 424 pid, i connect the savvycan with ip address (not direct to the ovms, with the ap both the ovms and laptop connected). I used the 3.2.011-169-g4b2f3c64/ota_0/eap fw updated automatically with ota from dexters-web eap.

2 2

Trying to compile my first code.
by Eddy Vromen 06 Apr '20

06 Apr '20

HI All, Just jumped on the OVSM bandwagon! Ordered myself a board and downloaded everything i could download. I am now in the process of trying to compile the code. Followed the OVMS v3 Developer Guide to a T. Still, pretty far down the list it throws an error. I would be great full if someone could point me to a solution for this. The full log is attached. CXX build/main/ovms_events.o CXX build/main/ovms_http.o CXX build/main/ovms_console.o CXX build/main/ovms_boot.o C:/msys32/home/Eddy/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/ovms_boot.cpp: In constructor 'Boot::Boot()': C:/msys32/home/Eddy/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/ovms_boot.cpp:248:46: error: 'xt_set_error_handler_callback' was not declared in this scope xt_set_error_handler_callback(ErrorCallback); ^ make[1]: *** [/c/Users/Eddy/Desktop/esp-idf/make/component_wrapper.mk:290: ovms_boot.o] Error 1 make: *** [C:\Users\Eddy\Desktop\esp-idf/make/project.mk:552: component-main-build] Error 2 Eddy@DESKTOP-TIO8A3R MINGW32 ~/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3 Thanks, Eddy

1 1