Pages: [1]
Author Topic: Cant seem to connect anything to 06A906032HN  (Read 6179 times)
robbyrr
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 16


« on: January 23, 2013, 01:38:48 PM »

Hi guys,

First post so dont kill me if i sound stupid Wink Still learning a lot,great site,some serious knowledge!..

I have a 06A906032HN ecu from an euro seat leon 1.8T (2002) and i cant get anything to connect to it.

I first tried eurodyne maestro,that didn't connect through obd. It was like the ecu didnt had any power.(but would sometimes connect through kwp2000 if i pressed read ecu right after i cycled the key on,but it again failed to connect right after that)

I thought maybe the cluster was interferring so i build a bech set up.

i have ecu:
pin 1 and 2:ground
pin 3 to a switch 12+  verified power(13,6v)
pin 21 to 2K resistor 12+(tried also without resistor) verifed power(13,6v)
pin 43 K line
pin 62 to 12+ verified power(13,6v)
 
and obd:
pin 4 and 5: ground
pin 7 K-line
pin 16 12+ verified power(13,6v)

and have a steady 13,6 powerfeed

So maestro gave the same results.

Then decided to try nefmoto,got an ebay ft232R and i get Validated FTDI device is in dumb mode.so figured the cable and drivers are ok?
But cant seem to connect.
This is the log:
Logger\ImportedLicenses.License.dat
23-jan-2013 09:14:40.153: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
23-jan-2013 09:15:14.454: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
23-jan-2013 09:15:14.678: LOG: Opened FTDI device.
23-jan-2013 09:15:14.687: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A20008JM Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
23-jan-2013 09:15:14.694: LOG: FTDI ChipID DLL is loaded, checking chip ID...
23-jan-2013 09:15:14.710: LOG: FTDI device chip ID: 0xFC92F7C1
23-jan-2013 09:15:14.786: USER: Validated FTDI device is in dumb mode.
23-jan-2013 09:15:14.822: LOG: Starting send receive thread.
23-jan-2013 09:15:14.893: LOG: Send receive thread now started.
23-jan-2013 09:15:14.903: USER: Disconnected
23-jan-2013 09:15:15.091: LOG: Setting communication timings to defaults.
23-jan-2013 09:15:15.102: LOG: Set timing parameters to defaults.
23-jan-2013 09:15:15.112: USER: Connecting...
23-jan-2013 09:15:15.142: LOG: Setting communication timings to defaults.
23-jan-2013 09:15:15.154: USER: Starting fast init connection.
23-jan-2013 09:15:15.162: USER: Connecting to address 0x01.
23-jan-2013 09:15:17.933: USER: Fast init sent, sending start communication request.
23-jan-2013 09:15:19.933: LOG: Message received no replies.
23-jan-2013 09:15:19.941: LOG: Failed to send message 1 times, message send failed.
23-jan-2013 09:15:19.952: USER: Start communication request did not receive any response.
23-jan-2013 09:15:19.959: USER: Disconnected
23-jan-2013 09:15:19.991: LOG: Setting communication timings to defaults.
23-jan-2013 09:15:20.002: USER: Connecting...
23-jan-2013 09:15:20.079: LOG: Setting communication timings to defaults.
23-jan-2013 09:15:20.088: USER: Starting fast init connection.
23-jan-2013 09:15:20.097: USER: Connecting to address 0x01.
23-jan-2013 09:15:22.841: USER: Fast init sent, sending start communication request.
23-jan-2013 09:15:24.839: LOG: Message received no replies.
23-jan-2013 09:15:24.849: LOG: Failed to send message 1 times, message send failed.
23-jan-2013 09:15:24.858: USER: Start communication request did not receive any response.
23-jan-2013 09:15:24.867: USER: Disconnected
23-jan-2013 09:15:24.906: LOG: Setting communication timings to defaults.
23-jan-2013 09:15:24.918: USER: Connecting...
23-jan-2013 09:15:24.948: LOG: Setting communication timings to defaults.
23-jan-2013 09:15:24.958: USER: Starting fast init connection.
23-jan-2013 09:15:24.968: USER: Connecting to address 0x01.
23-jan-2013 09:15:27.710: USER: Fast init sent, sending start communication request.
23-jan-2013 09:15:29.709: LOG: Message received no replies.
23-jan-2013 09:15:29.717: LOG: Failed to send message 1 times, message send failed.
23-jan-2013 09:15:29.726: USER: Start communication request did not receive any response.
23-jan-2013 09:15:29.734: USER: Disconnected
23-jan-2013 09:15:29.763: LOG: Setting communication timings to defaults.
23-jan-2013 09:15:29.776: LOG: Closing FTDI device.
23-jan-2013 09:15:29.792: LOG: Send receive thread now terminated.

Is there something i am missing? Any input would be great as im really lost..i really think it's something im not doing right.
Logged
aef
Hero Member
*****

Karma: +69/-46
Offline Offline

Posts: 1599


« Reply #1 on: January 24, 2013, 07:22:43 AM »

try only 4 at obd with ground, leave 5 alone...

and try with vagcom version 3.11
Logged
robbyrr
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 16


« Reply #2 on: January 24, 2013, 10:33:08 AM »

thanks for the reply!

The thing is,vagcom worked fine,version 514(i believe,hex-usb)but that was with a cable that doesnt supports nefmoto(not the right chip)so i bought a compatible one but no luck trying to connect to nefmoto.
I will try only 4 at obd and unplug 5,and report back.
Logged
robbyrr
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 16


« Reply #3 on: January 24, 2013, 11:42:03 AM »

nope,same results..unfortunately.

chip is good(FT232R USB UART)
Drivers of usb serial converter is ftdi 2.8.24.0
driver of usb serial com port is ftdi 2.8.24.0

maybe i have the wrong drivers?

sorry for my noobness..eager to learn though Smiley
Logged
prj
Hero Member
*****

Karma: +1072/-477
Offline Offline

Posts: 6025


« Reply #4 on: January 24, 2013, 12:30:20 PM »

You need to connect through slow init.
Fast init won't work through cluster usually.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
robbyrr
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 16


« Reply #5 on: January 24, 2013, 02:02:34 PM »

i tried both fast and slow and tried all baud rates,nothing helped..

but im trying to connect on a bench set up right now(first post),ecu is out the car right now.

i must be doing something wrong,but cant figure out what Huh
Logged
prj
Hero Member
*****

Karma: +1072/-477
Offline Offline

Posts: 6025


« Reply #6 on: January 24, 2013, 02:52:45 PM »

You are not getting any info back from the ECU.
If the ECU is on the bench then verify first that it will talk to vag com before trying anything else.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
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 0.001s, 0q)