Skip to content

Instantly share code, notes, and snippets.

@GPlay97
Created December 21, 2018 15:15
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save GPlay97/a074a5d8362009b362c7969904422ddc to your computer and use it in GitHub Desktop.
Save GPlay97/a074a5d8362009b362c7969904422ddc to your computer and use it in GitHub Desktop.
EVNotify NO DATA issue
So - I need your help.
Most of the OBD2 dongle are working absolutely fine with EVNotify. Even with the newest v2 versions and new cars.
However, some Dongle can not be used with EVNotify, because they are not sending the required data.
What are they sending? Well - NO DATA. That is the response.
This response normally says, that no data was found, that matched the criteria - or the response from the car took to long.
But all other dongle are fine, only a few have these issues. With Torque they seem to work normally.
I think, there is some missing command or handling for these dongle on initialization process.
This is the initilization:
Each command is seperated and will be executed before monitoring will start.
['ATD', 'ATZ', 'ATE0', 'ATL0', 'ATS0', 'ATH1', ('AT0')*, 'ATSTFF', 'ATFE', 'ATSP6', 'ATCRA7EC']
* This command normally disables adaptive timing - to fully wait the maximum timeout (ATSTFF).
But this was now removed - because the NO DATA dongle don't know this command - they respond with '?'.
I have even tried to close the protocol with 'ATPC' command, every time NODATA receives. The dongle is responding then with 'OK'.
But still NO DATA.
What is missing? Can you help?
I appreciate every little help.
If you can found the issue, there is a little bounty waiting for you. 5€. Just a small amount, because EVNotify is free.
And I'm young and don't have much money ;) If you decline the bounty, it will be saved for upcoming server fees.
Thank you in advance
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment