- OvmsDev - Open Vehicles

Re: [Ovmsdev] Simple TCP client
by Derek Caudwell 24 Aug '20

24 Aug '20

+1 for using mqtt. I use this approach also - using Home Assisstant on a private lan when at home and wifi connected. Mqtt broker between car and HA can run on NAS, Openwrt router or similar device. Main reason for doing so is to start/stop charging based on cell voltages and time of day with a smart switch.

1 0

Reverted fast OBD polling changes
by Michael Balzer 22 Aug '20

22 Aug '20

Everyone, if you did a pull during the last 2 hours, you may need to reset your local "master" manually to commit 967780ed2b6e8b60f460eef2eddca91c293055f2. I've decided to keep the fast polling changes by Soko which turned out to have a last bug in a separate branch, as I think we're close to a solution. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

1 0

Android Studio first-time setup
by Derek Caudwell 20 Aug '20

20 Aug '20

Ok, so with a bit of trial and error on Android Studio for Windows I have got to the point it will build the Apk successfully. In case it assists others here are the steps I took (not all may be necessary): Under Tools | SDK Manager select Android Pie API level 28 Also check under Tools | SDK Manager | SDK Tools that Android SDK Build - Tools and Android SDK Platform - Tools are selected. Under gradle scripts create a gradle.properties file with the following: android.useAndroidX=true android.enableJetifier=false This step removed the AndroidX build dependency requirement error. However, doing so then creates build dependency errors on pre-AndroidX libraries. Under Settings | Required Plugins select Android APK Support and Android Support. The normal Build process should then complete without any errors. regards Derek

1 0

Re: [Ovmsdev] Battery cell monitor on Android
by Derek Caudwell 19 Aug '20

19 Aug '20

Cheers Michael, I suspect it is as simple as selecting the right Android SDK, from the code I thought v28 was the one. If you could confirm that would be great, saves some trial and error downloading earlier versions.

3 2

Re: [Ovmsdev] Frequent Crashes
by Derek Caudwell 19 Aug '20

19 Aug '20

Hi Michael The crashes have been occurring when POLLSTATE is OFF, I cannot recall a crash whilst charging which is when the battery polls occur. But the Soko/Thomas changes may resolve some funny behaviour I have seen occasionally such as the vin returning more than 19 bytes and battery poll returning more bytes than the car has battery cells. It may also be linked to @Glynhudson DTC error. Cheers Derek

1 0

Battery cell monitor on Android
by Derek Caudwell 19 Aug '20

19 Aug '20

Hi Michael, Now that the battery cell polling is working reliably for my Gen2 Leaf I am interested in using the Battery/Temp Monitor Android feature you have for the Twizy. I have got stuck however trying to setup the Android build environment in Android Studio. I have installed the SDK for Pie v28, and included a gradle.properties file with android.useAndroidX=true to resolve the build error on AndroidX dependencies. I now seem to be coming up against build errors for older packages such as: error: package android.support.v7.app does not exist error: package android.support.v4.content does not exist A google on these types of errors suggests updating implementation and import statements to AndroidX equivalents, however I assume it is simply I am missing an option somewhere to have these packages downloaded and included in the build? Apologies if I am missing something simple here but I could not find a guide similar to that for building the open vehicle monitoring system environment. Thanks for the help. Cheers Derek

2 1

Re: [Ovmsdev] Frequent Crashes
by Derek Caudwell 19 Aug '20

19 Aug '20

With DukTape disabled and Mcp2515 overflow logging turned off the module has run and been stable for 5 days or so however I had it crash today with the following log entry. 2020-08-18 13:16:55 NZST I (12067) ovms-server-v3: Tx notify ovms/nismo/notify/data/debug.crash/1/0=*-OVM-DebugCrash,0,2592000,3.2.014-45-g390b4759-dirty/ota_0/edge (build idf v3.3.2-881-g22d636b7b-dirty Aug 13 2020 19:05:42),13,Crash,12,12,1,0,abort(),0,,0x4008e96b 0x4008ec05 0x400e6aec 0x40084122 ,6,Task watchdog,ticker.1,esp32wifi,0,IDLE1 It appears the issue remains (note this is with OVMS Events set to priority 19), however the likelihood of it causing the module to crash is reduced. Let me know if you have other suggestions to debug it, otherwise I will re-enable DukTape and see if anything changes. Cheers Derek

2 1

Re: [Ovmsdev] New pull requests pending
by Derek Caudwell 18 Aug '20

18 Aug '20

Hi Mark, Would it possible to have a 'Dev' branch in the main repository for those of us needing assistance to get a feature to the point it can be merged into the 'Master'? If that's not preferred and we use a branch on our own github clone, is it as simple as providing the link to the branch on this email list to invite others to collaborate/review? With the latter approach we may miss out on input from others not actively monitoring this forum I guess. Regards Derek

4 15

Re: [Ovmsdev] dirty mongoose submodule
by Derek Caudwell 17 Aug '20

17 Aug '20

Hi Michael, Thanks for the links I went through them along with trying to resolve the issue through the git command line, and it seems the only approach that reliably works is to add an ignore dirty or submodule statement to the appropriate git file - which to be effective needs to be committed and so will appear in the Pull request. I will continue to work around it. Kind regards Derek

1 0

Re: [Ovmsdev] Frequent Crashes
by Derek Caudwell 16 Aug '20

16 Aug '20

Hi Michael, I am still running with DukTape off and overflow logging on Mcp2515 line 489 commented out. The module has not crashed in over 4 days now, so seems to be stable, but I have a few more things to test eg using the weaker wifi connection in my garage. I will then uncomment line 489 in Mcp2515 and retest, and then turn Duktape back on with task priority 19 and let you know when I start seeing frequent crashes again. Regards

1 0