ApplagApp Forum

I mean risk of fire. The standard ECU management is full of safety routines to avoid fire, also in case of sensor or system failures. An example is the forced regeneration after a fixed amount of minutes or km, regardless of all the sensor values. This prevents the clogging of the filter that can pr...

Here's a screenshot Thanks! Did you voluntarily disable the soot mass measured field? Maybe you clicked on it without meaning to? After this feedback I think I have to change the commands sequence to avoid the error after the 0100 request. This should remove the error popup for the supported 29-bit...

My only advise is to do a full diagnostic check, if possibile in an official service to be sure of the results.
The app can only show you the parameters value, but it isn't for detailed diagnostic and most important, it doesn't read the ECU errors.

No feedback about this engine, I'm sorry.
Anyway you can try every existing group, maybe some of them is ok for your engine. Also using the free app, just to check that the communication is ok ans some parameter can be read.

Let me know the results

So did you test with a different adapter? Yes, but i have problem with automatically refresh, as I wrote I see you enabled the saving of the log file, can you share that file? I don't find it... The first time you enable the logging, the app asks you the permissions to save the file and the folder ...

The common behavior is that the app can read data with reasonable values or can't read the data showing nd. It's very rare to see a fixed value, while sometimes it happens to read too high or too low values due to a wrong calculation formula. I'm not an expert of chip tuning or DPF removal, but in t...

So did you test with a different adapter?

I see you enabled the saving of the log file, can you share that file?

I own the K903 that worked fine with my old car, but using the 11bit id protocol.
Never used with new beta 29bit id protocol, but it should work I think.

Another good adapter is the Carista one, but it's more expensive.

I use this ELM I own exactly the same adapter, at least the same external case, and it doesn't work with my car. It often refuses to manage a multi line can packets adding NO DATA in the second line. It's a very low quality adapter, it works only with OBD2 protocol with 2-bytes PIDs and single line...

Still not working, but using the 29bit ID (protocol 7 for ELM) your ECU replies always with CAN ERROR while using the 11bit ID (protocol 6 for ELM) the ECU replies sometime with a correct answer and sometime with the error of "serviceNotSupported". So the 29bit ID is wrong for sure, but I don't und...

Unfortunately I don't have experience with it and I never received a feedback from users.
Have you ever tried to use the existing groups? If you use a good adapter, I think some of them should let you read at least some parameter.

Jirkus did you tried also the other groups? in your log I see the ECU answering CAN ERROR to a standard pid request, this is strange, it means that the used protocol is completely wrong. Let me know what happens with other engine groups. But at start this shows Unable to communicate with engine ECU...

OBDlink LX improves the speed, but by the compatibility point of view, an ELM327 compliant device is enough. The problem is that the majority of the adapter in the market are not 100% compatible with the ELM standards. A good and reliable adapter is the Carista one, but in this beta testing, first w...

clodi wrote: ↑

Tue Oct 22, 2024 1:11 pm

Very good! another positive feedback makes me more confident.

misiakpb wrote: ↑

Tue Oct 22, 2024 7:43 pm

When new release will be published pls ?

I can work on the last fix tomorrow and in the evening, or Thursday morning in the worst case, I should publish the new release.
I want to give a quick check also to the Jirkus log.

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 ful...

App modified, but before to release I need some infos: Your log is strange because I see answers to the commands requesting the ECU data, the text you should see at the bottom of the screen, but I don't see anything in your picture. It seems that your ELM cuts the answers to the first row only inste...

This is the first request for DEWA engine and I don't have information about it.

Other 3.0 TDI engines are in the groups:
2 = CLAB
7 = CAPA, CCWA
11 = CDUD, CDUC
16 = CRTD
17 = CRCA, CGQB

Anyway you can try every group available and check what's the best.

I'm working on the 29bit init protocol with the help of the users, you can give a check here:
viewtopic.php?f=4&t=20036

Usually I add the oil ash in grams because it's more precise, but I can do it only if the parameter is available in the ECU.
When I find the value in liters only, I can only add it.
Anyway there is a fixed ratio of 400 between grams and liters, if you want to convert.

After checking your last logs, I've realized that some ECU uses the 29bit and 11bit init mixed together, so some PIDs require 11bit and some other 29bit init in the same ECU. I need to modify the app introducing another beta group according this news, but I'll probably also remove all the checks in ...