Here’s a little video I made (no good conditions I know), but it should be enough to show how fast the custom based interface is compared to the ELM327.

Don’t forget: buying a ELM327 is cheaper and does not need to build anything at all and for 90% of the users this is enough.

We have exciting features in this weekly release. Most are a bit under the hood, but you will notice them anyway.

ELM327 stability has improved a bit and it is a little bit faster too. As I mentioned last week, we’re shaving and modifying there in tiny steps. It might be a tad more talkative when things go wrong.

Behaviour when CanZE goes out of focus has improved a lot we believe. In essence, CanZE is paused and communication with the ELM or other device is stopped.

A few timed graphs have been added on request, i.e. state of charge over time.

The driving screen now has a function where you can add the distance to destination, and CanZE will update you on the expected distance available in the battery on arrival. You can also choose to double the distance to destination when planning for a round trip. Just tap the “distance to destination” line to get a pop-up.

A feature that we really like is that the last values that were requested from the car are now retained so you can open all the screens even when not connected and they are showing real information.

Stay tuned and don’t forget to report issues, or requests on gitub.

Stay tuned

Behind the scenes a lot of things are happening, most of which are team members climbing up the steep Android development curve. Many have an IT background but have not done Android development or VCS through Git before. So, a lot of learning-by-copying, installing Android Studio, getting heads wrapped around git and github usage, and tiny little experiments. You won’t notice much about those, but regard it as planting seeds and waiting for them to grow and blossom.

We are still trying to improve ELM stability and speed. It is a complex part of the project and it is hard to anticipate on the many things that can (and do) go wrong. Don’t expect leaps there, but gradual improvement.

We received a lot of feedback about the firmware version screen, thank you all! We have simply implemented in the reference (per ECU, per car type) the highest firmware number we have seen reported in the wild. Please do continue to report to us if the application reports an ECU in your car that has a higher version than what we have seen, indicated by [your version] > [ref version] in the display. If you notice your versions being older, you might want to head to the dealer (no, we will not try to implement firmware uploading in the app). Upcoming Sunday’s release should have all these new version numbers implemented.

And then there is of course tons of little tweaks and fixes.

For the (upcoming) developers, information on how to get started is compiled in the WiKi on github.

Stay tuned!

Regarding version 2015.10.04 @ 14:50

  • display firmware versions installed in the car
  • “safe driving mode”, which does not allow to manipulate the app while driving
  • new type of graph (see X10 activity for an example)
  • different ELM enhancements