Home › 2019 › February

Month: February 2019

By Posted on Posted in Builds 2 Comments

As you probably noticed, a lot of work is being done. We’re gearing up for a new release again.

  • Added total kWh and charge counts in the (experimental) Charging history screen. Very useful if you are checking out a used ZOE.
  • Several bug fixes and internal improvements.
  • Some appearance cleanup.
  • Deleted Dutch language.

Some other announcements and tidbits

  • The usage of CanZE is growing more than 33% per 6 months.
  • Because of the frankly staggering numbers we’re now focusing more than we used to on usability, consistency and stability.
  • Largest countries (by far) are Germany, the UK and France, together more than 50% of the installs.
  • As a result, German, English and French are the installed default languages on over 70% of the CanZE users phones (meaning Android languages, not CanZE languages)

We are planning on discontinuing all but English, German and French language support and are in an active process of finding committed, tool based language maintainers for those. So if you want to become such a language maintainer (the named ones or another one), please contact us through the CanZE Github page.

After this release, it might be quiet for a while: while we urge anyone with even mild tinkering skills to build the CanSee dongle and dump the commercial one, we realize that over 99% of the users actually use and will keep on using those. We’re in a process of research and change to massively improve the stability of the ELM based dongles and we’re pretty sure most users will be very pleased when it’s done. However, it will take considerable time.

By Posted on Posted in ZOE No Comments

Quite a while ago I did a strictly theoretical calculation on ZOE’s acceleration. You can find the post here. The end result was 8.9 seconds. I think in reality it is somewhere between 11 and 13; I should really do a test for fun but I don’t have a free runway available for that.

Anyway, I did the calculations again for the R110 under the exact assumptions, and in addition assumed that the maximum power level during acceleration was 88 kW. I have no idea if this comes close.

Car starts it’s accelerates exactly like the Q210/R240/R90 models: 5.0 m/s², but the R110 hits it’s (higher) power limit a bit later (2.36 seconds) and a bit faster (11.9 m/s). The remainder of the acceleration is at full power, reaching 100km/h (27.8 m/s) after a total of 7.6 seconds, roughly 14% (1.3 seconds) quicker. That 14% is probably pretty close to the real world difference.

By Posted on Posted in Builds 4 Comments

It’s only been an week, but we feel the need for some changes to be rolled out

  • Fixed negative numbers in Trip (Driving)
  • Much faster startup if you use the new, fast CanSee dongle
  • Fixed an issue that mostly produced wrong numbers in miles mode
  • Implemented a “news” bar on the main screen we can use to alert users
  • Moved Leak currents to Technical and made it more reliable
  • Fixed values not displaying in the experimental BCB screen

The trip function basically gives you a “Trip C”. Reset it by tapping it’s value area. It relies on trip B values supplied by the car so if you reset Trip B in the car, Trip C needs to be reset.

BCB and Leak Currents are helpful tools to assess charging problems. Note that HF Leak currents should not exceed 300 mA (preferably significantly lower), and that Ground resistance cannot exceed 150 or 200 ohms depending on model, and again, should preferably be significantly lower. On my home charger it is 11 ohms.

By Posted on Posted in Help No Comments

At this moment two rather serious discussions are going on in the issues section for CanZE to which I’d like to draw your attention and invite to participate.

First is the multi-language functionality. We, the current developers decided we are not willing and able to maintain the current language versions. Basically our stance is: own or remove. We maintain the app in English, but almost all strings are stored in separate, language sensitive XML files. I have maintained the Dutch version, but a quick check in the Dutch ZOE forum didn’t show any interest so we will ditch it in the next release. For the other languages (FR, DE, SL and ES), we need owners who are willing and able to maintain the language file, in XML and using GIT for version management. From our side, we can postpone anything but “crash” releases by say a week for language updates. Without a serious and committed owner for each language, we will remove it and keep doing so in the future. The app will default to English. To be honest, we see this as a one way street. Please comment if you want in the specific issue thread only.

Second is online data logging. We have written about our stance several times, but the truth is, it is a recurring issue in the comments, in some fora and also a few times in actual development. I have written my personal thoughts about it in the open issue here. This is not cast in stone, but it hints how far I am willing to go myself in terms of development effort and preference regarding architecture. Serious input is appreciated, also on the issue thread on github please.

Thanks for your input.