2017.02.12 [Jeroen] Added total energy to ChargingTech #430
2017.02.12 [Bob] Spanish language file added, many thanks to the contributors
2017.02.11 [Jeroen] Improved code to get DTC's
2017.02.11 [Jeroen] Added TCU to the DTC reporting
2017.02.11 [Jeroen] Changed http interface to use RequestID instead of ResponseID
2017.02.09 [Jeroen] Added compressor RPM graph (0-4000) in climatech
2017.02.09 [Jeroen] Fixed Y axis on ChargingGraphs for model 90s
2017.02.06 [Jeroen] Fixed formatting problem in ChargingTech
2017.02.05 [Jeroen] Code fixup on getting strings from language packs
2017.02.05 [Jeroen] Added debug lines to all running screens
2017.02.05 [Jeroen] Lots of code and layout cleanup
2017.02.03 [Jeroen] Allow operation without BT adapter so runs on emulator
2017.02.02 [Jeroen] Fixed ELM test #427
2017.02.02 [Bob] Merged German with file received from Roland Klose <rkl.fritzbox@gmx.de>
2017.02.02 [Jeroen] Compressor power dissed, replaced with RPM.
2017.02.02 [Jeroen] Hotfix on master: log level #417
2017.02.02 [Jeroen] Added German (Thank you Stefan!)
2017.02.01 [Jeroen] Climatech, climate replaced power by a graph
2017.01.31 [Jeroen] Added Slovenian (Thank you Zdenko!)
2017.01.27 [Jeroen] Climatech, Power as extra field

With the release of version 1.21 CanZE (Android version) is now officially a multi-language application. We have included English as default, and locales for Dutch and French. German is on it’s way. The language files are roughly 350 lines of XML. If there are volunteers who would like to see other languages added we would be very grateful and of course will be happy to include them. You can grab the complete English file here which contains as you know them, including untranslatable ones, and any of the other files (Dutch, French) as a template on how to format your language file.

The best way to get the file to us is by dropping it as an attachment to a new issue on GitHub.

Hi

Version 1.20 has been dispatched by Google’s Playstore, but I got noticed that it crashes on some devices. If you want to help or get some details, please go here:

https://github.com/fesch/CanZE/issues/407

In order to fix it, we need to be able to reproduce it, so reporting every setting of your device may help us! We introduced localized strings with this version, and probably this is the reason for the crashes.

Edit: On first glance, it seems to be related to the SD card logging, Fields option switched on. If true, switching it off is your temporary workaround until we have fixed it, but we would appreciate if you could report on the issue tracker above if this matches what you are experiencing.

Edit: hotfix (1.21) is being deployed now.

Version 1.16 is being rolled out, so stay tuned while Google approves the build ๐Ÿ˜‰

Changelog

2016.10.11 [Jeroen] Refined length of prediction interval
2016.08.24 [Jeroen] Split ZOE into ZOE Q210 and ZOE R240 for battery prediction

All the hype has been over the new R90 an Q90 and there has been written so much about it, that we didn’t feel the need to add to that. Of course we would love to get our hands on a ZOE with a big battery, because we probably need to change at lot of graphs and most certainly the battery prediction model.

Speaking about the that, there is a release upcoming with major improvements in the prediction model. As a consequence, the car selection in the Settings screen will change to also distinguish between a Q210 and an R240, as the latter will top charging at 22 kW even when it is connected to a more potent charger. If you do own a R240, please do check the settings screen after the next release. Also, expect the Q90 and R90 to be included too pretty soon, which will use the exact same mathematical model, but with a bigger capacity. We have no idea if this is correct and time will tell.

Actually, we don’t even know if the ’90 models speak the same language on the CANbus, but we do expect that to be the case. Stay tuned. As always, once we’re ready to roll, we’ll publish an update note here, drop a new release in the play store and publish an APK file.

Most prominent change is the driving screen now showing braking torque, with the bar extending to the left, and an aiming point for maximal motor based braking. This is more of a feed-forward instead of the old feed back system with the red Friction Braking (avoid) bar now for you to peruse.

And of course there were a couple of strange bugs and spelling errors that we fixed.