As expected, many, mostly small issues emerged after 1.54 release. Over 30 commits have been made since. We just uploaded 1.55beta1 in the open beta track. The most important changes are:

  • A fix for getting DTCs for pre ZE50 cars
  • CCS charging for the ZE50!!
  • An Android compliant and much improved settings screen
  • Several KONNWEI optimizations
  • Many small fixes, including the pilot current for newer firmware in pre-ZE50 cars
  • Increased font size in graphs

As you can see, we’re not forgetting about the pre-ZE50 car drivers.

We’re very excited and would love to push this to the production track as soon as possible, so give it a spin.

After the release of 1.54 the team is already churning on a couple of things that will be released soon on the beta channel, such as

  • a completely overhauled settings screen “Android style”
  • fairly significant performance increase for the ELM dongles
  • DC charging information!

And of course a few minor issues tackled. Keep reporting issues on GitHub please, it’s the safest way to get our attention, and for you to get feedback.

It’s past midnight as I write this. After a few evenings virtual-team-testing and virtual-team-debugging mostly dormant ELM issues that sprang to life while working on ZE50 support, we now have a limited, though “official” production release with ZE50 support.

Please report issues to GitHub as usual, while our virtual team will sink away in virtual booze 😉

As a side project of CanZE “ZE50-ing”, team member Leopold Baillard took his CanSee dongle to get input from his ZOE, and fed it into Super Tux Cart, displayed on his garage wall with a laser based pico projector. I laughed so hard!

Please do forgive the dark, shaky and moiré patterned video as well as the wall crashes. Not easy to steer and use your phone at the same time filming. Oh, but that’s what the police says eh?

On the German forum a shared google spreadsheet is being community-maintained listing ECU software versions. Cool way to notice if something has changed. Since CanZE beta can also pick up on the versions in the ZE50, tabs for those models have been added. While the column titles are in German, I would urge everyone with a ZE50 and in the CanZE beta track to add to it. We even added a “query all to CSV file” button in the Firmware screen so it should be fairly easy.


Pushing ourselves alsong, we’re far from done but will release in the production channel soon, even if far from all fields working for the ZE50.

Unfortunately, things area bit bumpy wen using the already slow KONNWEI 902 dongle. As we need to keep the gateway open, we hardly see three functional requests per second coming through. We might be able to optimize that further in a later stage, but success is not a given there, and it’s irritating. So if you are an electronics tinkerer, building a cansee dongle is more advised than ever. If not, we’re also investigating if we can finally make a jump to a branded, better, cheap, more potent dongle, possibly even on BLE. This will take time of course.

For those of you on the beta channel, you must have noticed the insane update speed. Things have been progressing at such a rate, it was useless to add blog entries. All ECU’s have now been added and you can play around with the firmware and alldata screens. Many regular fields have already been “ZE50-ified”, but there are still a lot to do. And there are a bunch that are simply not there anymore, so we might have to downscale a few things in CanZE for the ZE50, yet upscale others. Stay tuned, and if you are on the beta and running a ZE50, do contact the team on github to share!

Thank you for your patience, and a very well deserved thank you to the new, relentlessly hard working new team members.

Late PS: if you are running a cansee dongle, you need to update it again. There was another bug found & fixed.

While working on the ZE50, we found a silly bug in the CanSee firmware. If…

  • you have a ZE50
  • you build a CanSee dongle
  • you want to be on the bleeding edge on the CanZE beta’s

… please update the firmware as soon as possible. You can find it here.

I am very happy and proud to announce that a small team of ZE50 owners with tons of technical talents coalesced the last week or so from all over Europe to take up where we left off what feels like ages ago on the ZE50. Leopold Baillard, Frederick Sommerfeld and Roberto Sonzogni caught up on the code in no time and started testing tons of fields on their ZE50’s. I can relate to the constant back and forth and sitting crammed with a laptop and cables in the cold, cold car.

We did some code cleanup and already added fields like the SOH. The pace is really high, and I just release our work in progress in the open beta. Feel free to punish it hard. Not much use yet in reporting “hey, this field doesn’t populate”, trust us, we know 😉 But fields that give weird values of course need to be addressed. As always, please use the issue tracker if you do.

Google has changed it’s storage model starting Android 10. Starting the next production release and also Beta1.53-3, we will be following their lead, which means log files, TPMS set files and the _Research.csv file will all be stored in Android > data > lu.fisch.canze > files now.

Note: We will not transfer old files to the new folder, so if you want to maintain your TPMS IDs, you need to do some copy-pasting yourself, or simply (re)type the IDs and hit Save.

The new storage model has a strange quirk that is relevant for the _Research.csv file only. On some, if not all phones, a file can be written through a copy, can be deleted, but not overwritten. Best practice at this moment is to maintain your file on your PC, and when needed on the device, delete the old file there, then paste the new version.