-
Notifications
You must be signed in to change notification settings - Fork 114
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
Attempting to read non-standard PID #247
Comments
I don't any specific knowledge of that system, but I can offer some suggestions that might help you get started. The example sketch ESP32_CustomHeader.ino shows how to create a query using a custom PID and extracting the desired data from the raw response. It's hard to know exactly how your query should be structured from that info, but I bet a bit of experimentation would get you there. Perhaps try combining some variants of the "data" and set word values provided with service 61 and go from there. The 00, 0C, 25, 25 values might indicate a specific controller in the system. You'd address those with a custom header as in the same example above - with the "ATSH" command before your query. I'd try running a few test queries and look at the data (if any) that gets returned and see if I could make anything of that. |
Hello,
First of all, congratulations to the author - great job with this library. I was able to connect my esp32 project to the car without any major problems. I can read many standard PIDs such as engine speed, engine temperature, etc.
I am wondering how I could read several parameters that are specific to my car: 2003 MG ZR 160, communication via k-line (ISO 9141& ISO 14230).
For example: oil temperature, which in my case is not available under the standard PID 5C.
I managed to get some information about communication with my ECU to read such parameters, the question is how can I convert this structure to be able to read it using e.g. processPID()?
Some data:
Can someone help me with this case?
The text was updated successfully, but these errors were encountered: