-
Notifications
You must be signed in to change notification settings - Fork 6
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
Does this work on all TD5 ECUs? #6
Comments
Hi @happen-studio, There's no limitation on the year of manufacture but on the engine management system. Known limitations of this app:
As far as I remember, the Td5 ECU doesn't support OBD2 in any of its versions, whether they are a MY98 or MY2003 Defender or Discovery. Defenders are OBD2-compliant from the Td4 engine (2006). I haven't heard of a "simple" OBD2 interface capable of interacting with a Td5. This app is using K-line Communication defined by the ISO 14230 standard, also known as "Keyword Protocol 2000". It was in use on older German cars of the same epoch. Hope that helps! :) G'day! |
@Aloike is this a Lucas one? Thank you for all the info. |
Yes. Yours seems to be a MY2002 version. Td5 only came with Lucas ones, although there's a variation regarding their memory: ECUs with serial number starting with Your white tag seems to start with a cropped If you want to have a few more details about Lucas ECUs, here is an interesting link: https://blackbox-solutions.com/help/SM010.html 🤙 |
Hi @Aloike |
Knowledge is power, and it's meant to be shared 😉 Have a good day too, and keep rolling 🤙 |
Is there a limitation based on the year of manufacture?
As I can remember, all Defenders under 2004 don't support OBD2. Is this right?
Thanks
The text was updated successfully, but these errors were encountered: