hairyone / td5tester Goto Github PK

Looking at ODB2 cables, some have a PIC inside - such as the ELM327 and some cables marked up as things like "VAG K+CAN Commander"

Others just have the FTDI chip and a few other passive components

I'm guessing that the former two provides some abstraction between the car protocol and the PC - you talk to the PIC not the car - and so would not work with this project - whilst the latter, giving you direct control of the comms lines, should...?

"VAG K-CAN Commander" seems to be a specific bit of software, whilst ELM327 seems to be a defacto standard for ODBII comms - but neither are any use if what you need is direct control of the comms lines, which this project does?

(and I assume, since this project exists, that a standard ODBII connection would not get any data from a TD5...)

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

i assume the use of a CP2102 USB to TTL converter is not required if you have a KKL-USB cable with a FTDI chip. The FTDI chip with the suitable drivers makes the the USB act as a serial port. Hence this code will work ?

Hello @hairyone,

Is just to congratulate for this amazing project and to motivate you to not abandoned the project.
Don´t forget the "TODOs". ;)

Hello, unsure if you are still supporting this project but V2 crashes as soon as the apps opened but v1 seems to be ok! Is there much difference between the two?

Cheers for the brilliant app as well

Hi there, would it be possible to use this for abs data etc to use when off roading??

Hi! where to find the td5 tester.apk? because i was trying to import the project to Android Studio to be able to package it and make the .apk file, but it says that there are some missing files.?¿?¿?