CanZE with Arduino Due based interface

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.

4 Comments on “CanZE with Arduino Due based interface

  1. Does the speed with ELM327 depend on the dongle, or do you use a fixed speed for ELM327 anyway?
    (Some dongles allow faster readings than others)

    • Actually we use the default dongle speed. If you hold any information on how to read it out faster, it would be kind to share it with us, so we could use it too …

      • I will try to have a closer look. Not sure about what is default and how to set it if possible.

        For my OBDLink LX they advertise “delivering up to 4 times as many samples per second as the closest competitor” (probably very optimistic and only refer to competition when they designed it a while ago…)
        They indicated in their forum “Maximum Parameter ID (PID) rate: 124 PIDs/second for PC, 62 PIDs/second for Android” (they have a PC and an Android app).
        So here we should be able to get 62 PID/second (maybe even more since their PC app can?).

        In their Android app (“OBDLink”), there is a setting “Fast Polling” (on/off): “Set whether fast communication is attempted. Not compatible with all adapters”, so it may not be the default behaviour.
        They have also a “Dwell time” setting: “dwell time between each PID read from the vehicle”, which is set in the app by default to 5ms (can be set from 0ms to 250ms).

        But their app do not work with ZOE (works OK in my Toyota Auris HSD)…

        • Here is the (technical) problem: all those ICE commands are ODB2-ish. Question, answer, question, answer. So, it is pretty easy to push that to the max, as you know what to expect. Zoe (and most EV’s): not so, which is why that other program doesn’t work. Part of the information we have to get from operational data (non OBD2). It means we need to setup some sort of sniffing mode, enable it, wait for something to fly by, stop it before the tiny memory gets overwhelmed, repeat. It is VERY hard to get the timing right.

Leave a Reply

Your email address will not be published. Required fields are marked *