Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AndrOBD is not reading some DTC's #246

Open
DevEnthusiast99 opened this issue Nov 2, 2023 · 4 comments
Open

AndrOBD is not reading some DTC's #246

DevEnthusiast99 opened this issue Nov 2, 2023 · 4 comments
Labels
wait for details Waiting for details of issue contributor(s)

Comments

@DevEnthusiast99
Copy link

Describe the bug

On Toyota Sai 2011, Nissan Note 2012 vehicles, App is not finding DTCs even though there are multiple MIL lights are ON in the dashboard.

To Reproduce

Steps to reproduce the behavior:

  1. Try on the above mentioned models or any models

Expected behavior

When I tried the same cars with Carscanner app, everything works and I was able to clear the DTCs

AndrOBD Debug log files

Not available

Important details on your environment:

  • Android OS version: 15
  • AndrOBD version: 2.6.6
  • OBD adapter type: ELM327
  • Connected vehicle make, type, year, engine size: Toyota Sai 2011, Nissan Note 2012

Additional context

Picture from the Dashboard of Toyota Sai 2011 below:

Issue_img

@DevEnthusiast99 DevEnthusiast99 changed the title AndrOBD is not reading some specific DTC's AndrOBD is not reading some DTC's Nov 2, 2023
@fr3ts0n
Copy link
Owner

fr3ts0n commented Nov 2, 2023

Please could you provide a log file to allow analyzing this issue?
Pls see https://github.com/fr3ts0n/AndrOBD/wiki/Reporting-improvements---issues#reporting-improvements how to do ....

Thx

@DevEnthusiast99
Copy link
Author

Sure. I will try to provide a log file. I will definitely follow the given instruction. Thx.

@DevEnthusiast99
Copy link
Author

Hi again,
I haven't been lucky about getting the Logs as asked.

  1. I set the Log level to ALL but I found only empty file in the Logs directory unfortunately.
  2. I also tried things like disabling ATZ command, and Enabling Reset on NRC.

Since I could not get access to the same SAI described in my original issue. I tested on 2008 Toyota RAV4 but I got "Protocol not supported error" every time I try OBD data and OBD fault codes in the app.

Any input on this issue can help a lot :)

By the way, is the current code supporting cars before 2008? Because I've haven't been successful with cars older than 2008 due to the same "Protocol not supported error"

396070455_661872962681051_1836810776229021107_n

@fr3ts0n
Copy link
Owner

fr3ts0n commented Nov 3, 2023

A 2008 RAV4 should definitely support OBD data and DFC services.
It is really impossible to analyze anything protocol related without any log output ...

Have you checked the app file permissions to be allowed to write log files?

  • App info - Permissions

@fr3ts0n fr3ts0n added the wait for details Waiting for details of issue contributor(s) label Jan 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wait for details Waiting for details of issue contributor(s)
Projects
None yet
Development

No branches or pull requests

2 participants