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...)
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...)