NefMoto > Technical > Flashing and Chipping > Problem with cable
Pages: [1]
« previous next »
Author Topic: Problem with cable  (Read 9026 times)
tnel20
Full Member
***

Karma: +4/-0
Offline Offline

Posts: 139
« on: August 16, 2011, 09:19:51 AM »
after a fresh install of windows 7 i installed the flashing tool and driver for the cable and was able to read out my flash and erase dtc's. I was also able to flash jude's stage 3- tune/base file. No i am no longer able to connect to the ecu . I'm getting a echo failure from the fdic ship on my cable. so i tried multiple times to get it to work and said screw it and reinstalled a fresh copyu of windows 7 32bit version. installed the driver and tried it. Still getting the same fault. Any clue whats up?
Logged
tnel20
Full Member
***

Karma: +4/-0
Offline Offline

Posts: 139
« Reply #1 on: August 16, 2011, 09:23:05 AM »
This is the cable im using
http://www.autonostics.com/product.php?productid=1&cat=3&page=1

USB Dual K lines compatible with Ross-tech VAG-COM version 409.1
With the USB connector there is no need to have the old RS232 Comm port on your laptop.
This is the KKL version which is great for the new cars (2002 and above)

Specifications

Connects to PC via USB

2 K-Line & L-Line (KKL Interface)

Compatible to K/L and single K line mode

Because of it is 2 K-Line, it can also communicate with devices on 2nd K-Line on very new cars like latest Audi models

Powered from car battery over OBD2 connector

Comfortable cable length of 2.00 meters

Note

Terminal K = Bus of communication
Terminal L = Ignition for waking up car computing system (ECU: Engine Control Unit)
There exists 3 different protocols with same OBD2 connector incl. ISO/KWP, VPW, PMW
 ISO9141 protocol also supported
Logged
infinkc
Full Member
***

Karma: +6/-1
Offline Offline

Posts: 94
« Reply #2 on: August 16, 2011, 09:58:16 AM »
have you tried to use the rosstech vcds lite to see if the cable is even working correctly?
Logged
f up your ecu, i can help http://nefariousmotorsports.com/forum/index.php/topic,892.0title,.html
phila_dot
Hero Member
*****

Karma: +173/-11
Offline Offline

Posts: 1709
« Reply #3 on: August 16, 2011, 10:02:13 AM »
It may not be the cable, but the ECU. Have you tried another ECU?
Logged
tnel20
Full Member
***

Karma: +4/-0
Offline Offline

Posts: 139
« Reply #4 on: August 16, 2011, 10:09:51 AM »
no i havent tried another ecu yet. as i said i did a fresh install and only have the flashing software on here right now. that would really suck if it was my ecu after flashing it.
I'll see if our shop scan tool can read it properly
Logged
tnel20
Full Member
***

Karma: +4/-0
Offline Offline

Posts: 139
« Reply #5 on: August 16, 2011, 10:22:41 AM »
the log

15/Aug/2011 09:15:55.040: LOG: Opening NefMoto VW Audi ME7 ECU Flasher BETA 1.8.0.0
15/Aug/2011 09:15:55.774: LOG: Opened NefMoto VW Audi ME7 ECU Flasher BETA 1.8.0.0
15/Aug/2011 09:16:05.750: LOG: Closing NefMoto VW Audi ME7 ECU Flasher BETA 1.8.0.0
16/Aug/2011 06:25:18.447: LOG: Opening NefMoto VW Audi ME7 ECU Flasher BETA 1.8.0.0
16/Aug/2011 06:25:20.884: LOG: Opened NefMoto VW Audi ME7 ECU Flasher BETA 1.8.0.0
16/Aug/2011 06:25:36.508: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
16/Aug/2011 06:25:36.573: LOG: Opened FTDI device.
16/Aug/2011 06:25:36.574: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM ID: 0x4036001 Device Flags: 0x0
16/Aug/2011 06:25:36.575: LOG: FTDI ChipID DLL is loaded, checking chip ID...
16/Aug/2011 06:25:36.577: LOG: Unable to read FTDI device chip ID
16/Aug/2011 06:25:37.612: USER: Failed to read test echo from FTDI device.
16/Aug/2011 06:38:04.678: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
16/Aug/2011 06:38:04.679: LOG: Closing FTDI device.
16/Aug/2011 06:38:04.690: LOG: Could not open FTDI device
16/Aug/2011 06:38:04.690: USER: Could not open FTDI device.
16/Aug/2011 06:38:07.534: LOG: Closing NefMoto VW Audi ME7 ECU Flasher BETA 1.8.0.0
16/Aug/2011 06:39:40.063: LOG: Opening NefMoto VW Audi ME7 ECU Flasher BETA 1.8.0.0
16/Aug/2011 06:39:40.360: LOG: Opened NefMoto VW Audi ME7 ECU Flasher BETA 1.8.0.0
16/Aug/2011 06:39:44.063: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
16/Aug/2011 06:39:44.116: LOG: Opened FTDI device.
16/Aug/2011 06:39:44.117: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM ID: 0x4036001 Device Flags: 0x0
16/Aug/2011 06:39:44.117: LOG: FTDI ChipID DLL is loaded, checking chip ID...
16/Aug/2011 06:39:44.118: LOG: Unable to read FTDI device chip ID
16/Aug/2011 06:39:45.151: USER: Failed to read test echo from FTDI device.
16/Aug/2011 06:39:56.201: LOG: Closing NefMoto VW Audi ME7 ECU Flasher BETA 1.8.0.0
16/Aug/2011 06:40:26.158: LOG: Opening NefMoto VW Audi ME7 ECU Flasher BETA 1.8.0.0
16/Aug/2011 06:40:26.423: LOG: Opened NefMoto VW Audi ME7 ECU Flasher BETA 1.8.0.0
16/Aug/2011 06:40:29.371: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
16/Aug/2011 06:40:29.427: LOG: Opened FTDI device.
16/Aug/2011 06:40:29.428: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM ID: 0x4036001 Device Flags: 0x0
16/Aug/2011 06:40:29.428: LOG: FTDI ChipID DLL is loaded, checking chip ID...
16/Aug/2011 06:40:29.429: LOG: Unable to read FTDI device chip ID
16/Aug/2011 06:40:30.459: USER: Failed to read test echo from FTDI device.
16/Aug/2011 07:39:52.029: LOG: Closing NefMoto VW Audi ME7 ECU Flasher BETA 1.8.0.0
16/Aug/2011 10:19:31.832: LOG: Opening NefMoto VW Audi ME7 ECU Flasher BETA 1.8.0.0
16/Aug/2011 10:19:31.957: LOG: Opened NefMoto VW Audi ME7 ECU Flasher BETA 1.8.0.0
Logged
tnel20
Full Member
***

Karma: +4/-0
Offline Offline

Posts: 139
« Reply #6 on: August 16, 2011, 01:49:39 PM »
well the ecu is still readable with the audi scan tool. i guess i dont really know what to do then. I dont have another car to scan here at work right now. is there another way to check the cable.
Logged
infinkc
Full Member
***

Karma: +6/-1
Offline Offline

Posts: 94
« Reply #7 on: August 16, 2011, 01:58:36 PM »
Quote from: tnel20 on August 16, 2011, 01:49:39 PM
well the ecu is still readable with the audi scan tool. i guess i dont really know what to do then. I dont have another car to scan here at work right now. is there another way to check the cable.

like i mentioned use the vcds lite version, will allow you to try and read the codes and connect to the ecu.
Logged
f up your ecu, i can help http://nefariousmotorsports.com/forum/index.php/topic,892.0title,.html
tnel20
Full Member
***

Karma: +4/-0
Offline Offline

Posts: 139
« Reply #8 on: August 16, 2011, 02:32:07 PM »
before i reformatted again i had ecux and vcds lite on the comp i couldnt get vcds or ecux to make a connection but the flashing software would connect everytime. I'll d/l it again and try it out
Logged
tnel20
Full Member
***

Karma: +4/-0
Offline Offline

Posts: 139
« Reply #9 on: August 16, 2011, 04:04:44 PM »
this is what i get with vagcom lite
but i cannot connect to any control modules
Logged
tnel20
Full Member
***

Karma: +4/-0
Offline Offline

Posts: 139
« Reply #10 on: August 17, 2011, 06:01:33 PM »
update : used a guys laptop at work and loaded the flashing software on it and driver file and was able to connect first try. Flashed with the fixed file matt did for me . So im guessing its something with my laptop but i have no clue what it might be since it worked on here before. Any clue as to what im doing wrong. His comp has win 7 64 and i have win7 32bit.
Logged
Pages: [1]
  Print  
« previous next »
 
Jump to:  

Navigation
Personal Tools
  • November 27, 2024, 04:38:29 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.02 seconds with 17 queries. (Pretty URLs adds 0s, 0q)