Pages: [1]
Author Topic: Trouble connecting to ECU: KWP 1281?  (Read 6343 times)
NikkiTurbo
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 5


« on: May 30, 2015, 11:18:33 AM »

I am trying to connect to the ECU over the obdII port using this cable: http://www.ebay.com/itm/251088284958 from the "working FTDI cables list". My ECU is a 4b0 907 551L box in a 2000 audi a6. The cable installed the driver for it as soon as it was connected to my computer running windows 8.1 and was recognized by nefmoto as FT232r USB UART. I also already had the FTDI D2xx driver installed from a previous cable I had that would not work. When I tried running a slow init connection here is what I got:

Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init failed.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init failed.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init failed.
Disconnected
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init failed.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init failed.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init failed.
Disconnected
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
Failed to read KWP1281 connect info.
Connecting to address 0x01.
Slow init succeeded.
Failed to read KWP1281 connect info.
Connecting to address 0x11.
Slow init failed.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Failed to read KWP1281 connect info.
Connecting to address 0x01.
Slow init succeeded.
Failed to read KWP1281 connect info.
Connecting to address 0x11.
Slow init failed.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Failed to read KWP1281 connect info.
Connecting to address 0x01.
Slow init succeeded.
Failed to read KWP1281 connect info.
Connecting to address 0x11.
Slow init failed.
Disconnected
Switching to KWP2000 session.
Could not open FTDI device.
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
Failed to read KWP1281 connect info.
Connecting to address 0x01.
Slow init succeeded.
Failed to read KWP1281 connect info.
Connecting to address 0x11.
Slow init failed.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Failed to read KWP1281 connect info.
Connecting to address 0x01.
Slow init succeeded.
Failed to read KWP1281 connect info.
Connecting to address 0x11.
Slow init failed.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Failed to read KWP1281 connect info.
Connecting to address 0x01.
Slow init succeeded.
Failed to read KWP1281 connect info.
Connecting to address 0x11.
Slow init failed.
Disconnected
Switching to KWP2000 session.
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
Failed to read KWP1281 connect info.
Connecting to address 0x01.
Slow init succeeded.
Failed to read KWP1281 connect info.
Connecting to address 0x11.
Slow init failed.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Failed to read KWP1281 connect info.
Connecting to address 0x01.
Slow init succeeded.
Failed to read KWP1281 connect info.
Connecting to address 0x11.
Slow init failed.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Failed to read KWP1281 connect info.
Connecting to address 0x01.
Slow init succeeded.
Failed to read KWP1281 connect info.
Connecting to address 0x11.
Slow init failed.
Disconnected

it succeeds in connecting, but then cannot read the KWP1281 info. I searched around but was unable to find a deffinitive answer other than, "It should work". Ideas?
Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-167
Offline Offline

Posts: 12235


WWW
« Reply #1 on: May 30, 2015, 11:28:09 AM »

Try a lower baudrate, or unplugging the cluster.

Is the ECU stock?

Is the ignition on (motor not running)?

Is your battery fully charged?
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

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 experience.
NikkiTurbo
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 5


« Reply #2 on: May 30, 2015, 01:45:31 PM »

The ignition was on. 10400 was the lowest baud I tried. I will try 9600 and see. The battery is brand new and on a 12v charger. The car has no immobilizer so I didn't think that unplugging the cluster would help but I will check and see as well.

I just installed a new harness from a 2000 6 speed for the manual swap. Could that be messing it up?
Logged
NikkiTurbo
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 5


« Reply #3 on: May 30, 2015, 04:23:39 PM »

Just pulled my instrument cluster. More of the same.

Disconnected
Switching to KWP2000 session.
Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
Failed to read KWP1281 connect info.
Connecting to address 0x01.
Slow init succeeded.
Failed to read KWP1281 connect info.
Connecting to address 0x11.
Slow init failed.
Disconnected

I tried running it at 9600 baud and it would specify 10400 in the status bar.
Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-167
Offline Offline

Posts: 12235


WWW
« Reply #4 on: May 30, 2015, 05:44:10 PM »

I just installed a new harness from a 2000 6 speed for the manual swap. Could that be messing it up?

Could be. Might be worth trying it using a bench flasher. Do you have spare ECU to try?

Also, are you sure the ECU you are using is stock?
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

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 experience.
tjwasiak
Sr. Member
****

Karma: +26/-0
Offline Offline

Posts: 420


« Reply #5 on: May 30, 2015, 06:27:43 PM »

I would check if it possible to connect to ECU using VAG-COM/VCDS as it might be wiring issue.
Logged
NikkiTurbo
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 5


« Reply #6 on: May 31, 2015, 07:22:17 AM »

I don't have a spare ecu right now. I have two K boxes from 2000 manuals on the way so I can hopefully get the car going while I figure out whats wrong. I might try bench flashing just for shits and gigs though.

Also, I have no Vag-com/vcds cable because I thought I would try and save money.  Roll Eyes as if that ever happens.
Logged
NikkiTurbo
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 5


« Reply #7 on: July 05, 2015, 08:52:49 AM »

Been a while.

I got a K box and swapped into the car. It worked perfectly I was able to read the 1281 info and everything. Unfortunately, when I tried to read the files or checksums, I was met with an infinite lead bar. It would say it processing but would sit for hours and nothing would happen. I don't have the logs. As it was only able to read the 1281 info once. Ever since It has been exactly the same as before.

I'm starting to think this is a wiring issue, but I would rather not have to do all the wiring over. I'm going to set up a bench so I can see if its maybe a problem with my computer or cable.
Logged
Pages: [1]
  Print  
 
Jump to:  

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