NefMoto

Hi Guys, 

Hoping somebody can help! I'm trying to read an used ecu thru the OBD port on a B5.

I'm getting a "unable to open comport" (error=0x01) message. I've tried ports 1, 2 & 3, not sure how else to aproach this....currently hooked up to the car!....Thanks.

Witch programmer / software you use ?

Argdubs tool for reading over OBD.

that is about as a cut and dry problem as you can get.
the most obvious question, which com port is for your cable?

I agree! lol.... I checked and it's on port 3 (Port_#0003.Hub_#0001) baud rate is 10400

My laptop only has two usb ports (1 & 3) I tried both and the same message, regardless.....I'm so close!!! just tried changing baud rate...same result.

usb does not equal com.
in device manager, under ports (com and lpt), thats where its listed.

Thanks for getting me on track Komp,

I know exactly what you're talking about, and it's been a long time since I had seen it. (I had originally looked at properties for the USB port I was connected to, to determine the com port as I hadn't seen com & lpt.). When I searched device manager, guess what? I was missing "com & lpt" off the tree.

I googled why and I was not alone! windows 7  is missing it. so I had to add it by doing a hardware add (which is also missing), then do a search for "hdwwiz" under the start menu, and the hardware wizard comes up.

I added the com & lpt to the device manager tree and now it shows. However com 5 & com 6 which now show, have a yellow exclamation on them, which I think means I have to transfer the USB communication to either com5 or 6 to identify the location.

So, my head is about to explode and my wife is hunting me down, therefore, I'm calling it a night and let you know how I make out tomorrow.....man, thanks for being patient.  :)

That's not going to work. If installing the driver didn't add COM ports you did something wrong or are using the wrong driver.

i was going to say he seems to be making it extra complicated. but what you said works too.  :P

I have to agree with both of you, which is why my head wanted to explode last night!

This is what i did today: I un-installed the ftdi driver and re-installed it, this time instead of it being usb converter a, it's just serial bus converter and it's working properly.

Unfortunately, my results are the same :'(

This is my command line if anyone can see something, please, fire away ;D

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Owner>Downloads\me7_95040 --OBD -r -p 3 95040.bin
Ver: 1.30
Com Port: 3
Baud Rate: 10400
Opening COM3 ... Unable to open comport. (error=0x01)
Closing COM3

C:\Users\Owner>

the phrase you can lead a horse to water but you cant make him drink comes to mind here.
again, how did you come to the conclusion that its port 3? because obviously, its not.

Please post a screenshot of your device manager.

Komp and nyet....here's a screen shot of both the device manager and the usb converter showing what I thought was the comport. (remember, I added com & lpt last night to the tree and I agree with you both of you that it shouldn't be as complicated to assign a comport as it is getting to be!).

I was able to read the ecu and pin throught the OBD with the regular vag tacho software cd i have, however, when I try to access the ecu with argdub's tool, I'm one step short, believe me, I appreciate the effort you guys are making, and I'm trying not to overlook something.
(http://)

You need to be using the VIRTUAL COMPORT DRIVERS (VCP). Download them, and manually install.

Also, remove the com5 and 6 that you added, its only going to cause problems down the line

And that is where the answer laid. Thanks dil, nyet and komp.

Long story short...I had downloaded the VPC from the FTDI site.  When I installed it, I chose USB converter in the Dev. Mgr Tree and that worked for the VAG TACHO sftware I got with the cable. However, for using argdubs tool, I needed to pick Unknown device and off that the UNIVERSAL SERIAL BUS CONTROLLER not CONVERTER. Once installed PORTS COM & LPT appeared on the DEV. MGR tree as COM 5. (Nyet, I did remove com&lpt as you suggested prior to).

So I tested at my desk (not connected to the car) and got an OK when opening COM 5 but communication fail, which I expected. I'll try to read the ECU and then try to read the new/used ECU so I can disable the IMMO on that one.....

Thank you again!

Excellent! Glad you got it sorted out.

Yeah, well, I may have spoken too soon....While it seems the comport is "ok" now, communication is still failing....I changed the port to 1 changed port settings such as baud rate, latency, BPS, USB transfer size...nothing, like I wasn't connected to the car....tried key off, key on, engine running...nada. here's a screen shot:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Owner>Downloads\me7_95040 --OBD -r -p 1 95040.bin
Ver: 1.30
Com Port: 1
Baud Rate: 10400
Opening COM1 ... OK
Initiating communication ... FAIL. (error=0x07)
Closing COM1

Anyway, thanks for the help.....not sure where to go from here. At least the last error message was cut and dry.

Hey NYET,

I found this discussion http://nefariousmotorsports.com/forum/index.php?topic=4491.15 and my jaw dropped...I downloaded the program from ftdi and did a scan with command prompt and it cannot find the device, which makes me think that ultimately I may not have the proper cable for using argdub's tool. What do you think?

Here's a screen shot:

FT:>SCAN
Scanning for devices...
No devices found!
FT:>

Yours is listed as FTDI in the device manager.

doesnt it have to be in boot mode to write to the 95040 over OBD?

Yes it has to be in boot mode to write, but his command string was to read.

I know... I've just kept on reading on the cable issues, and by now this probably should be categorized as such. Ok, so now I just needed to know what is up with the cable; I opened the cable and found an FTDI 245BL chip in it(lead free). (Probably why I couldn't even get the cable to scan with FTPROG.)

From FTDI; discontinued are the "B" series. So, an FT232r or FT245r can be used (the 232 is a USB UART IC and the 245 is a USB FIFO IC). It seems that most people are having success with the 232R.

I tried my XP laptop for chuckles and I couldn't even get the VCP to take with the 245B, the destination folder would appear empty. Then I tried to see if the driver would load from the supplied cd and it did! thought this was version 1.6, which started me thinking that this was very old. So I tried installing the driver again from my folder and same result: even thought the files are in the folder, once I browse the folder for installation, the folder is empty( no, it's not hidden). Because of this, argdub's tool is useless since I can't assign a comport to it.

So, today I'm going to purchase another cable from "gameadvance" in Ebay, listed as a compatible cable (he/she seems to know the issues with the cables) and try again.

Man, all I want to do is disable this damn Immobiliser in the new/used ecu and get this car on the road....tuning and mod's will come later but I need to get past this first!  ::)

Yep. Won't work. You need a 232 variant.

All right!, success.....Ok Boys, sit back and enjoy, this is how I've finally connected.

So, I got the new cable (ft232r), I'm thinking, no prob, easy from here on.....hahaha, think again. I connected the cable to my windows 7 laptop and wala! cable found! no need to install drivers as the updated driver from FTDI was already installed. I went to the car tried connecting with the vag 409.1 and test the connection...no device found, (or something to that effect, BTW the cd that came with the cable is awesome as far as directions are concerned)  same thing if I tried argdubs tool.

Now I'm depressed, what the heck? so, I thought I should try windows xp mode, but first maybe I should remove the driver in my machine and re-install it with the cd that came with the cable...sure enough, that was the key, the vag com 409.1 connected immediately! So even thought that FTDI says that the updated drivers are the ones to use, I have a feeling that the driver in the cd is different (I haven't completely checked it out).

So now I decided that for insurance, in order to work with argdubs tool, I should download xp mode...that was also a trick! for a great work around go to http://www.tomshardware.co.uk/windows-xp-mode-windows-7-win7,news-33258.html (http://www.tomshardware.co.uk/windows-xp-mode-windows-7-win7,news-33258.html) the problem that a lot of people are having is verifying their copy of windows. Without verification, you CAN'T download it. Long story short, I was using CHROME as a browser; I decided to try it with EXPLORER as the browser, and bang! verification went through, and XP mode downloaded perfectly (mind you, I'm on a 30 day trial, which I think I can convert to permanent...more on that later).

So, I downloaded the driver to my virtual (XP mode) machine, downloaded argdubs tool and went to work. When you connect with Xp mode, you want to make sure that the USB connection is enabled on the Tab on the desktop. I was finally able to connect with argdub's tool and read both ECU's, (the stock and the replacement). So now I have both SKC's and I can either ADAPT with the vag com 409.1 or disable the Immo on the replacement ECU. I'm leaning to the disabling of the Immo, however, since I used all the available power in my remaining brain cell, could somebody let me know what the actual steps in in backing up the info and disabling? do I now use the nefmoto software or can I use argdub's tool?....I think ddillinger was saying that doing it through OBD was tedious, but possible....I just happen to be over the big hump and haven't gone to deep in the actual process for disabling the Immo. I just don't want to wipe out a perfectly good ecu. Geez, I hope this helps somebody!

xr500t:

Please post the link to the seller/cable you used for others!

Argdub for read/writing the ECU eeprom (small) to disable immo.

Nefmoto is only for flashing ECU software (the large flash) to say, flash ECU software that does not require immo (different "box").

Absolutely, BTW, even before I bought the cable, I asked him if this was a232r and he replied promptly, which is why I bought.

Anyway, it's gameadvance on ebay.  http://www.ebay.com/usr/gameadvance (http://www.ebay.com/usr/gameadvance)

Thanks for the reply nyet, not sure how I missed it yesterday ??? anyway, this is where I show my inexperience with cmd....I'd like to back up the contents of my used ecu eeprom, but I don't know how to write the cmd line. Where does it save it to and or how do I retrieve it? Should I be using a redirect command to do this? ie:
>desktop\me7_95040 --OBD -r -p 3 95040.bin > C:\Users\Owners\Documents\Passat ECU

I think the way to write the cmd for the Immo off file is: >desktop\me7_95040 --bootmode -w -p 3 immodef95040  where I'm using ddilingers Immo off file. I also downloaded the Dd's immo off vlc file but I can't get that to open...

Thanks for all your input!

No. You can't redirect to a directory, even thats what you wanted to do, which it isn't. the file 95040.bin will be saved  in whatever directory you ran cmd from.


vlc file?

Thanks for all your input!
[/quote]

The videolan (vlc player) detects .bin as a media file and associates it with the program.

It's another Immo off file Dil put up....Anyway, not sure what you mean by "whatever directory you ran cmd from" since I have it pinned or can pull it up from my search box....so what you're saying is that I may have it saved already, just need to find it? I was trying to open the vlc file on its own, which may be why it's not opening (I do have the vlc player).

If I just do: >desktop\me7_95040 --bootmode -w -p 3 immodef95040 and make sure that immodef95040 is also on the desktop I should gold? :)

Download teamviewer, I'll school you quick to make this fooproof.

My email is in my sig.

cmd runs in a directory. the cmd prompt shows you the directory it is in, eg:

"C:\WINDOWS>"

"cd" changes directory.

Definitely getting schooled here 8) I'm attaching a shot of the command as it stands.

I'm so out of it I can't even paste the screen shot:(


(http://)

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>immo --OBD -r -p 3 95040.bin
Ver: 1.30
Com Port: 3
Baud Rate: 10400
Opening COM3 ... OK
Initiating communication ... OK
ECU ID response: 3B0907551BS
                 2.8L V6/5V      G
                 0001
Reading EEPROM .................................................................
. OK
File saved
Closing COM3

C:\Documents and Settings\Administrator>immo --OBD -w -p 3 95040.bin
Ver: 1.30
Error: EEPROM write via OBD port not supported. (error=0x01)

C:\Documents and Settings\Administrator>

dude, cmon :/


....


anyway, its better you cut and paste the contents of the command anyway, not post a screenshot, which nobody can quote from.

Sooner or later I'd get it :-[, but thanks for taking this dumb horse there ;D I was still having some issues getting programs to open by simply not understanding what I needed. I downloaded HxD editor which allowed me to open the saved file (part of the reason I couldn't understand part of this puzzle...thanks Dil for pointing me there.)

The other problem I have is that my cable is not liking W7, but playing nicely with XPmode, so I mirrored all the programs to XP. Anyway, I was looking for the saved file in W7, when it dawns on me I should look for it on XP (thank you NYET for knocking on my noggin!) I opened the file with the Hx Editor and it matched(obviously) what I had originally displayed to the screen.

I guess my final steps will be to name and save that stock file as a back up and then Immo off blocks 12 and 22 and write it in. Hopefully, it'll play nice and allow me to write over the OBD port.

You need to bootmode the ecu to write. Your cmd should be:

immo --bootmode -wp1 off.bin

where off is the name of your immo-off file.

Thanks man, I'll change 1 to 3 as that is my port on XP.

Unbelievable...she's just playing hard to get....all I want is some booty mode! lol! This is my result....even used a jumper cable between cars to make sure power supply was up.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>immo --bootmode -wp3 off.bin
Ver: 1.30
Com Port: 3
Baud Rate: 10400
Opening COM3 ... OK
Starting Boot_mode ... FAIL ... No response from ECU. (error=0x07)
Closing COM3

C:\Documents and Settings\Administrator>immo --bootmode -wp3 off.bin
Ver: 1.30
Com Port: 3
Baud Rate: 10400
Opening COM3 ... OK
Starting Boot_mode ... FAIL ... No response from ECU. (error=0x07)
Closing COM3

C:\Documents and Settings\Administrator>immo --OBD -p3 --screen
Ver: 1.30
Com Port: 3
Baud Rate: 10400
Opening COM3 ... OK
Initiating communication ... OK
ECU ID response: 3B0907551BS
                 2.8L V6/5V      G
                 0001
Reading EEPROM .................................................................
. OK
Printing to screen

Offset  0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F
   0   12 68 30 17 63 5A FF FF  FF FF FF FF FF FF FF A5
  10   05 01 01 00 65 77 00 00  00 00 69 C1 00 A5 4D FD
  20   05 01 01 00 65 77 00 00  00 00 69 C1 00 A5 4C FD
  30   04 01 27 0E 60 85 A8 61  DE 8F B4 00 01 00 B3 FB
  40   04 01 27 0E 60 85 A8 61  DE 8F B4 00 01 00 B2 FB
  50   07 02 54 02 AA 01 FA FF  33 04 2E 0E 07 00 7E FC
  60   00 00 A4 0D 54 0E 00 00  82 03 01 00 00 00 61 FE
  70   05 04 00 09 15 00 00 01  00 00 80 1D 00 00 34 FF
  80   05 04 00 09 15 00 00 01  00 00 80 1D 00 00 34 FF
  90   00 80 80 80 80 00 00 80  00 80 80 FF 00 00 78 FB
  A0   00 80 80 80 80 00 00 80  00 80 80 FF 00 00 78 FB
  B0   05 07 00 00 10 57 41 55  42 48 01 00 00 00 61 FE
  C0   05 07 00 00 10 57 41 55  42 48 01 00 00 00 61 FE
  D0   35 34 42 39 31 4E 30 36  36 35 37 34 41 01 12 FD
  E0   35 34 42 39 31 4E 30 36  36 35 37 34 41 01 12 FD
  F0   55 5A 37 5A 30 59 31 36  30 31 39 39 30 01 BD FC
 100   55 5A 37 5A 30 59 31 36  30 31 39 39 30 01 BD FC
 110   00 00 83 7E BC 0C 00 00  00 00 00 00 00 00 11 11
 120   FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF
 130   FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF
 140   FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF
 150   01 07 00 00 00 00 00 00  00 00 00 00 00 00 E3 FF
 160   00 00 00 00 00 00 00 00  00 00 00 00 00 00 EA FF
 170   00 00 00 22 7B 00 91 00  01 88 27 00 9D 20 4E FD
 180   6D 6D 02 88 40 02 0C 00  02 22 6C 00 15 20 71 FD
 190   00 00 00 88 6C 01 07 00  03 11 7E 02 16 20 21 FE
 1A0   00 00 01 44 EC 00 0D 24  01 44 57 00 05 20 C3 FD
 1B0   00 00 00 00 00 00 00 00  00 00 00 00 00 00 E5 FF
 1C0   00 00 00 00 00 00 00 00  00 00 00 00 00 00 E4 FF
 1D0   00 00 00 00 00 00 00 00  00 00 00 00 00 00 E3 FF
 1E0   01 02 00 00 00 00 00 00  00 00 00 00 00 00 DF FF
 1F0   01 02 00 00 00 00 00 00  00 00 00 00 00 00 DF FF

Closing COM3

C:\Documents and Settings\Administrator>immo --bootmode -wp3 off.bin
Ver: 1.30
Com Port: 3
Baud Rate: 10400
Opening COM3 ... OK
Starting Boot_mode ... FAIL ... No response from ECU. (error=0x07)
Closing COM3

C:\Documents and Settings\Administrator>immo --bootmode -wp3 off.bin
Ver: 1.30
Com Port: 3
Baud Rate: 10400
Opening COM3 ... OK
Starting Boot_mode ... FAIL ... No response from ECU. (error=0x07)
Closing COM3

C:\Documents and Settings\Administrator>

I guess I'm going to read the boot mode issues.

You need to open the ecu, ground pin 24 of the flash chip, then power on the ecu while keeping it grounded (for 10 seconds). After that, removing the ground while leaving the ecu powered will result in bootmode.

Is that what you're doing, or are you just hoping the ecu magically can enter bootmode on it's own :P

I thought I'd read that somewhere.....buut I thought I was Houdini....oh wait....he drowned!

Ok, I'll call it a night before my wife kills me and go at it again tommorow....thanks for the heads up!

Mine enters boot mode magically, the shoots sparks and disappears... Leaving only tracking info to NY.. Odd right?!

Ok, somewhat succesfull, but not quite there yet. I left off needing to boot the ECU, which I managed after a few tries. I got argdubs tool to write to the ECU, seemed to have gone well....but, my immo off file didn't seem to have flashed in, even thought the program told me it did. When I read the file back it came back as Immo on....So, where do I go from here? I only flashed it once as you can see.


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>immo --bootmode -wp3 off.bin
Ver: 1.30
Com Port: 3
Baud Rate: 10400
Opening COM3 ... OK
Starting Boot_mode ... FAIL ... No response from ECU. (error=0x07)
Closing COM3

C:\Documents and Settings\Administrator>immo --OBD -r -p 3 95040.bin
Ver: 1.30
Com Port: 3
Baud Rate: 10400
Opening COM3 ... OK
Initiating communication ... OK
ECU ID response: 3B0907551BS
                 2.8L V6/5V      G
                 0001
Reading EEPROM .................................................................
. OK
File saved
Closing COM3

C:\Documents and Settings\Administrator>immo --bootmode -wp3 off.bin
Ver: 1.30
Com Port: 3
Baud Rate: 10400
Opening COM3 ... OK
Starting Boot_mode ... FAIL ... No response from ECU. (error=0x07)
Closing COM3

C:\Documents and Settings\Administrator>immo --bootmode -wp3 off.bin
Ver: 1.30
Com Port: 3
Baud Rate: 10400
Opening COM3 ... OK
Starting Boot_mode ... uC identification response = 0xC5 (C167 derivatives) ...
OK
Sending Loader + MonitorCore ... MonitorCore successfully launched
Initializing registers ... ... OK
Sending EEPROM driver ... OK
Searching Chip_Select pin ... P4.7
Configuring SPI Interface ... OK
Checking EEPROM status ... 0x00F0 ... OK
Writing EEPROM ................................ OK
Verifying EEPROM write ... OK
Closing COM3

C:\Documents and Settings\Administrator>immo --OBD -p3 --screen
Ver: 1.30
Com Port: 3
Baud Rate: 10400
Opening COM3 ... OK
Initiating communication ... OK
ECU ID response: 3B0907551BS
                 2.8L V6/5V      G
                 0001
Reading EEPROM .................................................................
. OK
Printing to screen

Offset  0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F
   0   12 68 30 17 63 5A FF FF  FF FF FF FF FF FF FF A5
  10   05 01 01 00 65 77 00 00  00 00 69 C1 00 A5 4D FD
  20   05 01 01 00 65 77 00 00  00 00 69 C1 00 A5 4C FD
  30   04 01 27 0E 60 85 A8 61  DE 8F B4 00 01 00 B3 FB
  40   04 01 27 0E 60 85 A8 61  DE 8F B4 00 01 00 B2 FB
  50   07 02 4B 02 A4 01 02 00  23 04 EE 0D 07 00 D5 FD
  60   00 00 AF 0D 54 0E 00 00  82 03 01 00 00 00 56 FE
  70   05 04 00 09 15 00 00 01  00 00 80 1D 00 00 34 FF
  80   05 04 00 09 15 00 00 01  00 00 80 1D 00 00 34 FF
  90   00 80 80 80 80 00 00 80  00 80 80 FF 00 00 78 FB
  A0   00 80 80 80 80 00 00 80  00 80 80 FF 00 00 78 FB
  B0   05 07 00 00 10 57 41 55  42 48 01 00 00 00 61 FE
  C0   05 07 00 00 10 57 41 55  42 48 01 00 00 00 61 FE
  D0   35 34 42 39 31 4E 30 36  36 35 37 34 41 01 12 FD
  E0   35 34 42 39 31 4E 30 36  36 35 37 34 41 01 12 FD
  F0   55 5A 37 5A 30 59 31 36  30 31 39 39 30 01 BD FC
 100   55 5A 37 5A 30 59 31 36  30 31 39 39 30 01 BD FC
 110   00 00 36 D8 9C A5 00 00  00 00 00 00 00 00 11 11
 120   FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF
 130   FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF
 140   FF FF FF FF FF FF FF FF  FF FF FF FF FF FF FF FF
 150   01 07 00 00 00 00 00 00  00 00 00 00 00 00 E3 FF
 160   00 00 00 00 00 00 00 00  00 00 00 00 00 00 EA FF
 170   00 00 00 22 7B 00 91 00  01 88 27 00 9D 20 4E FD
 180   6D 6D 02 88 40 02 0C 00  02 22 6C 00 15 20 71 FD
 190   00 00 00 88 6C 01 07 00  03 11 7E 02 16 20 21 FE
 1A0   00 00 03 44 EC 00 0D 24  01 44 57 00 05 20 C1 FD
 1B0   00 00 00 22 2B 01 19 00  02 88 69 00 7F 00 0C FE
 1C0   00 00 00 00 00 00 00 00  00 00 00 00 00 00 E4 FF
 1D0   00 00 00 00 00 00 00 00  00 00 00 00 00 00 E3 FF
 1E0   01 02 00 00 00 00 00 00  00 00 00 00 00 00 DF FF
 1F0   01 02 00 00 00 00 00 00  00 00 00 00 00 00 DF FF

Closing COM3

C:\Documents and Settings\Administrator>

I had to specify the memtype, and CSpin to write mine, but somebody will chime in as to whether or not that applies to you.

Hey Jackson--just tried again with the same results, disappointing to say the least. Anyway, can you point me in the right direction on where I can read on memtype and CSpin? I did a search and am coming up empty.

ive never had the trouble with argdub tool as you are having.works first try everytime for me with 95040 ???  actually i have had problems with the 5P08C3  it would not communicate and i had problems with getting the ecus into bootmode.  i ended up having to desolder the eeprom and put it into a GQ-4X and manually read and modify for immo off.

Hey Corey, thanks for your reply. However, All the issues I've been having are and have been documented by others on this forum, both by the experienced and inexperienced. I just happened to have highlighted the problems as they happen as well well as the problem being resolved, with an explanation as how it was resolved. Most people are giving up, others just say problem fixed, with no procedure as to how they got there. This is why people get frustrated and you get a lot of noob questions, people just can't find stuff. I admit, I'm a noob, and I dove in the deep end but I don't have two left thumbs, unfortunately, there are people on all boards who can't change a tire, never mind trying this!

Anyway, I found a post where Argdub himself addresses the problem I'm having as an incorrect message (writing ok, when it's not), the guy he helps, figures out the problem, but does not outline how he got around to the fix....further perpetuating the pain! :P

If it helps anyone trying to get on to boot mode, I did it with the case open and grounding pin 24 right on the chip. The first time I got in to bmode, it was sheer luck, the 2nd time it was brutal, almost gave up. I ended turning the ignition switch on and then grounding pin 24 by tapping it a couple of times, then running the program reasonably quick.

Maybe I'm using the wrong version (1.30), I'm not sure I need specify memtype or chip select, as you can see the program identified those, possibly incorrect, but I don't know that, somebody does thought.  I'm putting up a profile picture of one of my projects (not an Audi) but not for the faint of heart....it's got a 16v hybrid conversion. So, can I work on cars? I think I can.

Read the entire stickied thread understanding/retrofitting immobilizer. I forget but I think it was version 1.40 I used which lets you specify the CSpin, and memtype.

Boot pin for full 10 seconds. Command string looked like this:

(http://s15.postimg.org/7ga7jxpu3/meatpopsiclethefinal.png)

and you really don't want to go poking around... TRUST ME!

Speaking of which, I got an ecu in for you today. Going to send it out Monday. STAY. OUT. OF. IT.

I'll cut one of the unused pins and make it a switchable bootpin for you :P

HOORAY!

Man, it's in my nature to open up stuff and poke!  ;D I'll give it a shot, I ended finding a couple of threads with similar arguments, so thanks for making it clear thought. I think that I'm also going to make sure my power supply is a little more steady. I've been charging the battery prior to doing the write, but I'm adding a battery charger to it.

Bro, I know.. All things must be poked, prodded, burnt or bricked for people like us to truly learn... But I think I've gone through 3 now... and hopefully this ones welded shut.. WHATEVER YOU DO! DON'T DRINK and do anything BUT you're wife..