NefMoto > Technical > Communication Protocols > Simple diagnostic adaptor for KWP2000.
Pages: [1]
« previous next »
Author Topic: Simple diagnostic adaptor for KWP2000.  (Read 12305 times)
jasnm
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« on: January 18, 2017, 01:43:06 PM »
Having spent many hours decoding TP2.0 and KWP2000 I built simple diagnostic adaptor using a UDOO Neo to prove it works. Video https://youtu.be/FR6Yilzh6vE and more info on the blog http://jas-hacks.blogspot.co.uk/2017/01/imx6sx-prototype-vw-vag-vehicle.html.
Logged
royce5950
Sr. Member
****

Karma: +18/-44
Offline Offline

Posts: 376
« Reply #1 on: February 15, 2017, 12:29:22 PM »
When I open nefmoto to connect to my 01 jetta it transfers to kwp2000 session automatically and I'm using an ftdi based dongle (FT232RL) works great with vag-com VCDS Lite: full registered version as well.

Were you having troubles getting a cable to work for just diagnostics? I would imagine you were likely just either using the USB setting in your diagnostic program and you didn't have the right driver for your chip, and if you were using com port you likely didn't have your com port confgiured properly in device manager.

Regardless glad you got your interface working!!  Smiley
Logged
Purchase Tuned Files Ready To Be Flashed ⚡ For Audi / VW 1.8T & 2.0T Engines ➡️ TUNEDBYV3@GMAIL.COM ✨ Send Me An Email Now And Save BIG On A Performance Tuned File
jasnm
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« Reply #2 on: February 23, 2017, 11:32:44 AM »
Quote from: roycerollz5950 on February 15, 2017, 12:29:22 PM
When I open nefmoto to connect to my 01 jetta it transfers to kwp2000 session automatically and I'm using an ftdi based dongle (FT232RL) works great with vag-com VCDS Lite: full registered version as well.

Were you having troubles getting a cable to work for just diagnostics? I would imagine you were likely just either using the USB setting in your diagnostic program and you didn't have the right driver for your chip, and if you were using com port you likely didn't have your com port confgiured properly in device manager.

Regardless glad you got your interface working!!  Smiley

I'm not using ftdi as the interface is CAN so I wired up my own cable to the MCU.
Logged
prj
Hero Member
*****

Karma: +1072/-481
Offline Offline

Posts: 6037
« Reply #3 on: February 23, 2017, 02:38:54 PM »
Develop all that, and still not able to spell OBD II correctly.

Sorry, just had to say it Tongue
Logged
PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
jasnm
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 7
« Reply #4 on: February 24, 2017, 02:06:04 PM »
Quote from: prj on February 23, 2017, 02:38:54 PM
Develop all that, and still not able to spell OBD II correctly.

Sorry, just had to say it Tongue


 Grin
Logged
Pages: [1]
  Print  
« previous next »
 
Jump to:  

Navigation
Personal Tools
  • November 26, 2024, 11:05:44 PM
  • Welcome, Guest. Please login or register.
    Did you miss your activation email?

    Login with username, password and session length
Search
 
Advanced Search
About Disclaimer
All Rights Reserved 2010 Nefarious Motosports
Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.023 seconds with 17 queries. (Pretty URLs adds 0s, 0q)