Author: admin

By Posted on Posted in Builds No Comments

Starting now, we might sometimes publish pre-release builds for people who want to be on the bleeding edge, but are unable to build from the source. I am still checking if these can be unsigned builds. Regard these pre-releases as unstable and unusable, but if you are not afraid of fiddling with APK files and not afraid to re-install older, more stable versions if things go haywire, you might want to grab these from github in the releases section. They will always be clearly marked with an orange “Pre-release” flag. Here is an example, where we added some interesting BCB stuff to the experimental section.

By Posted on Posted in Main No Comments

We’ve had quite a few remarks and questions about the modified firmware screen. Please note you now need to tap an ECU line to display it’s version information. We now display 4 fields that are all required to find the proper definitions of what these computers can and cannot do. Also, note that the reference numbers are gone. There are simply too many hardware permutations and we have no reliable source about what is the latest for what version of what hardware.

By Posted on Posted in Teaser 2 Comments

Today I finally got some data from the BCB. I am not crying victory yet, but here are a few teasers. Screen-shots were taken close to the end of a charging session on my home single phase 16 amps charge-point.

Harmonic leak currents look fine, with only the LF one (that is 50 Hz) a bit on the high side. Maybe the scaling is not good. We don’t know what acceptable values are.

On single phase, the voltages on the BCB screen look a bit weird, but I will be working on that.

Progress!!

By Posted on Posted in Geek talk 11 Comments

Chris sent me a very interesting dongle. It is called a Freematics ONE. The simplest way to describe it is it being an ELM327 CANbus interface, plus a fully programmable Arduino UNO, plus an SD-card interface, plus a Bluetooth interface, plus serial-over-USB (oh yeah, could do a fast, wired CanZE version) plus an accelerometer, plus (optionally) one of WiFi, GPRS+GSM or xBee modules. Pricepoint is not crazy expensive: a bare version would come in at 70 USD.

I am still figuring what to do with it, but it sure is a great datalogger. And assuming the ELM327 “look-alike” chip inside is reasonably compatible with the V1.5 dongles we use, the Arduino code is in large part available, as I made that for the WiFi gateway. Anyone got cool ideas?

By Posted on Posted in Geek talk 9 Comments

We received a CLIP clone today. CLIP is the tool that your Renault mechanic will use to diagnose any of the brand’s cars. The tool was very kindly financed by “kick-starter” style funding on the Dutch and UK forum. Thank you all for that! Reason I asked for it was that we really like to get to the data of the BCB (the charger inside the car) and we haven’t been able to figure out why. This post is a short update.

Let me first say, the hardware is a serious piece of kit. You have seen your dongles and my interface s and that´s child play compared to this. Two rather massive 4 layer PCB’s plus a connector PCB. Admitted, it seems the hardware can do ISO 9141-2 next to CAN, but the ZOE doesn’t use that. Anyway, it explains the price-point somewhat.

The good news is that it works. Somewhat. As ar as we understand Renault is pushing more and more functions to their central services and there is very little we can do with the tool without online connectivity, which we obviously do not have. Or maybe we do not understand it yet, which is a possibility.

Still, it’s able to run a diagnostic script on all computers of the ZOE and extract their DTCs, including a more extensive context. In theory, that should be enough to teach us how to get at least some data from the BCB. Stay tuned for updates.

By Posted on Posted in Builds 
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

By Posted on Posted in Geek talk 7 Comments

From day one we’ve had a love-hate relationship with the dongles. We love them being cheap, available, consumer-grade devices anyone can get on the cheaps and just use them. We hate the instability, how slow they are, the version issues and the complicated way to interact with them. They’re totally unusable to analyze what is going on on the CANbus.

When we started getting our feet wet and didn’t know anything about what was going on on the CANbus we started building our own hardware. Alex and Bob used AVR powered Arduino’s with an external CAN controller, I myself build a derivative of EVTV’s CanDue, based on a fast but not very popular ARM powered Arduino Due. Data was then pushed over serial (USB or Bluetooth) to a PC or tablet for further processing. This of course was totally not consumer rated, but it enabled us to really see what was going on in the car. There are some video’s on youtube of us struggling with that: the AVRs were lacking processing power, and the Due was more bulky and had to be hooked up to a PC using USB.

Fast forward two years and with the fast, small and WiFi enabled ESP8266 processor taking over the role of many AVRs in hobby projects, it was time for a new experiment. I connected a WeMos D1 Mini processor (bottom PCB) to a cheap external CAN controller board (top PCB) featuring an MCP2515, the bigger of the two chip and unfortunately a TJA1050. I had to either replace that chip with an SN65HVD230 or or modify the board a bit for 3.3 volt usage and choose the latter.

Be careful with the pin layout. The ESP8266 is VERY confusing: GPIO numbers, WeMos pin numbers, notation with D-prefixes and without. Most of that stuff is documented in the source code. Oh and I found a really tiny 12 -> 5V buck converter. It is minuscule, tucked away under the WeMos.

On the software side I started with the code for the http Bluetooth gateway, removed all code for Bluetooth and the dongle and added in code to use the CAN controller. This opened up a wealth of possibilities:

  • Fast WiFi interface, fast direct PCI connection to the CAN controller
  • Can auto-connect to the home WiFi network, or act as an access point;
  • Very small footprint (4 x 6 cm PCB);
  • No changes in CanZE and other tools needed as the http interface is exactly the same as for the gateway;
  • Processor easily keeps up with the bus speed;
  • Multi-frame handling (ISO-TP) completely offloaded to the ESP8266.

The device is more functional than an ELM327, completely programmable (watch this space for more functions beyond CanZE) and most of all FAST. You can see how fast here

By Posted on Posted in ZOE

Zoe’s error messages to the driver are not always crystal clear. This one usually points to a failure in the 12 volt system.

There are basically two reasons why the 12 volt system can be compromised (barring real faults somewhere in the electrical system):

  1. failure of the 12 volt lead acid battery
  2. unexpected drain of the 12 volt battery (leading very very quickly to 1.)

Let me start by saying the 12 volt system feeds anything and everything that is not traction or the air conditioning compressor. For the non-Nordic version, it also feeds a few rheostats for fast wind shield defrosting. It’s all pretty beefy but still it can drain fast. Remember that all 16 computers are powered from the 12 volt system. If this bus runs bad, literally nothing will work as expected, if at all really.

Renault has the lead-acid battery replacement in their schedule set for after 3 years. This does seem pretty short indeed, but given the above, I wouldn’t dismiss the dealers suggestion for replacement flat out. If you are in doubt, at least have it tested. Lead acid batteries are loosing a notoriously amount of capacity when it gets cold, and you don’t want to get stranded with a full traction battery, but a dead 12 volt system. And if it’s dead, the computers are dead, and there will be no way to bootstrap charging it without hooking it up to an external 12 volt battery charger. Been there, read on.

Unexpected drain is pretty hard to do. The auxiliary power shuts off when the car goes in sleep mode, so even leaving on some sort of accessory through the lighter plug should shut down.

There is one scenario however, which I am pretty sure happened to me. The charger plug was not seated properly, or at least the car thought so. You can actually detect this when the motor lock retries every 2-3 seconds. This retrying continues forever and while this is going on, the car is fully awake, all computers are on, the lock motor is being fired continuously and of course no charging is happening while there is a serious load on the 12 volt system. Now one could think the 12 volt system is being replenished by the traction battery, but it isn’t. The lead acid battery was drained down to 5 volt in a few hours at which point the car went completely dead. 5 volt is devastating to a lead acid battery if not quickly charged. Luckily, I found out and diagnosed this within a few hours of it happening.

I couldn’t bootstrap the car “in situ”, because as soon as I connected my small 12 volt car charger to the battery, the car woke up, started to initialize all it’s systems and while doing so overwhelmed the charger. I removed the mass cable from the battery and charged it for an hour. After that, the battery had enough juice to pull the car through it’s initialisation. I then was able to remove the charger cable, hooked it up again and charged the car normally. The error went away after one cycle.

By Posted on Posted in Geek talk No Comments

In the previous episodes of developers geek talk I explained a bit how the hardware you use is terrible for actual software development. Sitting in a cold car, often at night with a laptop is no fun, and the process is slow. The http gateway changed a lot in that respect. We can now test new features in CanZE without having to leave the desk. So code, upload to the phone and it will get to the car over WiFi through http and in the car itself it is still using a real ELM327 KONNWEI 902 dongle. More about an alternative approach in another episode of geek talk.

Another benefit is that CanZE can now be run in an Android Studio emulator. Here you see an emulated Nexus phone running CanZE on my Ubuntu laptop showing the latest Climate screen. I went outside while it was running an pushed my hand against the outside temperature sensor that is mounted under the right side mirror. We can now test different screen sizes and orientations too without actually owning such devices. All this has never been possible as the Android emulators do not support Bluetooth. Also, we can quickly test different language settings without messing up our own devices.

So now you know why the latest release of CanZE asked for network permissions: next to using Bluetooth to get raw data from the car, it can use WiFi or even the Internet over the cell network to get that data through a gateway.