ApplagApp Forum

Hi

2 weeks ago suddenly application stops communicating with DCZA engine after almost 1 year of using it. Same phone, same bluetooth adapter. It is showing green icon for adapter connection, then green icon for car connection, green two round arrows (last icon) and after 2-3 seconds it is showing red last icon (arrows) and icon for car turns yellow. So I assume it is connected to the car but can`t read data from ECU. Any idea what happened? Seems that last application update done something with communication protocol? Torque is working OK so it is not adapter fault.

Did you already try to reinstall and pair the adapter again? Usually this procedure solves those strange behaviors.

If you're using a low cost adapter with cloned firmware, don't trust on it also if you see it works with other apps. There is a big difference between the "common" OBD apps and the full canbus scanners/readers. The first ones use a simple 2 bytes communication with single packets, the second ones use the full length messages with 7 bytes and multi lines packets. The cloned adapter use a cracked firmware that is borderline by the reliability point of view. If you have the opportunity to test another adapter, it can be a good way to confirm where is the issue, in the adapter or in the app.
In the meantime I give another check at the code, but I didn't change the connection protocol in the last revisions.

I found what is wrong. When I`m choosing DCZA (group 14) it is not working (also with different bluetooth adapter). Same when using read from ECU option. When I`m choosing group 4 (DCXA) everything is working fine. For sure I have DCZA engine in my car

Mmm interesting, can you post a screenshot? So I can read the ECU sw/hw versions. Thanks