Pages: [1]
Author Topic: Wrong KKL Cable?  (Read 6430 times)
Murph
Jr. Member
**

Karma: +12/-0
Offline Offline

Posts: 39


« on: June 03, 2015, 04:23:24 PM »

Soo I think I may have an incompatible cable, or I am clearly missing something? I can't get my cable to show up in the NefMoto software.
Here's the one I bought and works fine in VCDS: http://www.ebay.com/itm/350766989906?_trksid=p2060353.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT

The cable automatically updates the drivers and if I attempt to update the device with the FTDI drivers from the website the n00b guide specifies, it just tells me they are already up to date... Soo, maybe its not the drivers that are the issue? But when I connect up to my OBD port, the NefMoto software doesnt recognize my cable as being plugged in.

Some help into troubleshooting this would be great. I already went through the process of restarting NefMoto, turning car off and on again, unplugging and plugging the cable back in, uninstalling and reinstalling drivers (which when I uninstall them manually it becomes an unrecognized device, I try to use the FTDI drivers, in which it gives me an error)..

I think I may have a cable that doesn't use an FTDI chip...  Huh
Logged

tjwasiak
Sr. Member
****

Karma: +26/-0
Offline Offline

Posts: 420


« Reply #1 on: June 03, 2015, 05:27:55 PM »

Soo I think I may have an incompatible cable, or I am clearly missing something? I can't get my cable to show up in the NefMoto software.
(...)
I think I may have a cable that doesn't use an FTDI chip...  Huh
Could you post your cable hardware ids?
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #2 on: June 03, 2015, 05:41:27 PM »

http://www.ebay.com/itm/281312477303?_trksid=p2059210.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
Murph
Jr. Member
**

Karma: +12/-0
Offline Offline

Posts: 39


« Reply #3 on: June 03, 2015, 06:02:26 PM »

Could you post your cable hardware ids?

USB\VID_1A86&PID_7523&REV_0254
USB\VID_1A86&PID_7523
Logged

nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12271


WWW
« Reply #4 on: June 03, 2015, 10:08:31 PM »

CH34x garbage
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
automan001
Full Member
***

Karma: +47/-0
Offline Offline

Posts: 153


« Reply #5 on: June 04, 2015, 01:28:56 AM »

You should not afraid non-ftdi chips like this. Yes, it's cheapest Chinese cable, somebody call it garbage, but if you know how to properly use it, you will realise it has almost same capabilities as FTDI. You just need to install CH340 drivers. I successfully use VAG-Com KKL 409.1 cable with CH340T chip inside for logging via me7log and for reading-writing eeprom via me7_95040 eeprom programmer and for flashing in boot mode. For flashing via OBD i use MPPS.
Try these drivers https://drive.google.com/file/d/0B0z1E_9eZCvMYk5UaUpiVGpXUXc/view?usp=sharing
Reuploaded from here https://translate.google.com/translate?sl=ru&tl=en&js=y&prev=_t&hl=ru&ie=UTF-8&u=http%3A%2F%2Ftehdocwiki.ru%2Ftehdoki%2Fview%2F249&edit-text=&act=url
« Last Edit: June 04, 2015, 01:36:49 AM by automan001 » Logged
Murph
Jr. Member
**

Karma: +12/-0
Offline Offline

Posts: 39


« Reply #6 on: June 04, 2015, 05:35:28 AM »

Yea, I've already ordered the cable that Dillenger linked. My current cable works great for everything except NefMoto flashing. I can use VCDS and have used the eeprom programmer to correct my mileage. I'll just have a spare laying around I guess.
Logged

Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.018 seconds with 17 queries. (Pretty URLs adds 0s, 0q)