Help with PnP Ecu Into 1G GTO

[Twofastoocatch]

Hey guys,
I've searched around and can't seem to find any info on my scenario, so here goes:
I've been working on a '91 GTO TT, and saved my pennies, and a few months ago I bought my PnP flash ECU. Over the winter I've completed a wiring tuck, poly motor mounts, FMIC, Xfer case brace, and at the end of last year I did the complete 120k, oil pump, t belt, water pump, idlers, ISC, the works. The car ran pretty good on the stock ECU. Fast foreward to now, and after finally finishing up the exhaust and wideband setup, I'm trying to get this car back on the road. I've encountered a few problems that I cant seem to find an answer to, so without to much more of an essay, here goes:

I seem to have extra wires on my harness. The terminal that is used to provide +12v power the flash ECU (pin 77) already has a wire in it, a white wire, no tracers. Its a factory connector, with a quality crimp on a quality connector, so I assume its supposed to be there...? For the sake of the flash ECU, I unplugged it, and ran the +12v wire there anyways, and insulated it from contacting anything else.

The second extra wire is in my Diagnostic connector. All the instructions for installing the ECU showed that when you plug the other end of the red +12v wire, it would just plug into the open space. Again, I already have a wire there. This on is yellow with a red tracer.

The final thing that just doesn't want to work is ECUflash. I just unplugged and insulated that yellow wire at the DDL connector and I can now log with evoscan, but ecuflash refuses to work. I'm getting error " error loading FTD2XX.DLL " Can anyone help me? I've re installed both ecuflash and evoscan multiple times, in multiple different locations, manually installed drivers (I think, I'm not exactly a computer guru...), I've also tried both versions of ecuflash I could find, and still nothing. Thanks in advance.

Kyle

[FluffyCow]

HVe to install drivers with the taxtrix hooked up.

Also double and triple chexk your wiring. I had mine screwed up and it coulsnt do anything

[Twofastoocatch]

So just to make clear, my best bet is to remove ecuflash again, plug in the tactrix cable, and then install ecuflash again? The only thing there is, when I plug in the tactrix cable, windows auto installs them from wherever it gets them. Do I stop it from auto installing? Sorry to be asking noob questions, but after the amount of time I've put into this in the past week, the less guess work I can pull out of this, the better.

[sergechronos]

I installed Evoscan and ECUFlash before plugging the Tactrix in, otherwise I was getting an error that it couldn't find any drivers.

For what I can find regarding the OBDI connector: Pin6 (which you should put the yellow wire into) *could* be occupied with a yellow/red wire if it was an ATX for the computer for it.
Pin 2 (for the red wire) shouldn't have anything in it.

Regarding pin 77 on the ECU, not sure what yours may have there. My pin 77 was empty but was between 2 white wires. Not to belittle you at all, but are you sure you counted correctly? Should be the 5th wire/slot from the end.

Start with the basics, if you could get pictures that would probably help.

[Twofastoocatch]

No offense taken. I checked quite a few times, as I did make an error the first time I put the pin in. Then I had to get the pin out. After another 45 minutes of fighting I decided to be distinctly more careful and ensure I didn't make the same mistake twice. It definitely resides in the 5th spot from the end now. Like you said, there was no issues with the red wire on the DDL side of the wire. That was open, plugged in, worked awesome.

Reguarding the pin/ecu wiring, I know it's atleast somewhat correct, as everything I have tried works well... AC/engine/cat over temp/ everything works with that white wire out, and Evoscan works very well. The car is on jackstands, but I did manage to make a log of coolant temp vs engine RPM, and everything seemed normal there.

I'll have to get back to you later this week with pictures, I'm out of town with work for a few days now. But I can tell you that pin 77 on my harness does have a white wire on either side of it. I didn't pay enough attention to check for tracer colors/stripes on them though.

ECUflash.... All of the times I've tried it, I have had the cable unplugged. It seems to me its worth a shot re installing it with the cable plugged in, I'm just not sure at what point I should plug it in? Or does it matter? Should I just not let windows install the drivers for it, and then manually install them?

Another side note, but I'm assuming when you guys mention manually installing the drivers, you mean that I go into the folder where ecuflash keeps the openport 2.0 files and run the only application file in there? Or am I way off track?

[sergechronos]

Hmm..Then you have yourself a pickle. I will snap a couple pictures if I can get my camera to cooperate later for a reference. You may have to trace that white wire back and figure out what it runs to.

As far as the ECUflash/Evoscan issue: You could uninstall them, then reinstall somewhere other than your Program Files directory. If you run windows Vista or 7, that user account control can cause issues if you don't have it all disabled. Haven't installed Evoscan or ECUFlash on my Vista computer as it's a desktop, but they are installed and working on my Windows 7. You can give it a shot with the cable plugged in, shouldn't make much of a difference.

[Twofastoocatch]

My laptop is a windows 7 OS. I think I may have sourced a XP based laptop to give it a shot with later this week. I'll give that a shot and see what happens there. I had read before installing ecuflash that there were issues with allowing windows to put it in the standard directory, so to be completely honest I never did allow it to install in the C\programfiles area. I made an ecuflash folder in my documents, and figured I'd try and skip the part where windows makes another copy of the program somewhere else. I'll post up back here if I get anything figured out. There's only this and a few other things keeping her off the road now.

[Twofastoocatch]

After another hour of messing with this, I still can't do anything. The problem I'm having I think boils down to ecuflash having an error loading "FTD2XX.DLL" I've manually copied it into the system32 folder, I've tried installing, and running ecuflash as an admin, installing ecuflash as an admin, I've tried installing the program in my documents, as well as allowing windows to put it in program files. I've deleted, uninstalled, and re installed ecuflash, and all the drivers and everything pertaining to it. I've also tried installing and running ecuflash with the windows XP SP2, and 3 compatibility. No matter what I do, I open ecuflash and it says error loading FTD2XX.DLL. It has to be an install error?, because just opening the program I get that error message. It will allow me to edit the chrome rom I downloaded, but it still says there's an error.

I googled the problem and all the results are from 2008. I've tried as far as I can tell, everything. Is there somewhere I can download an older version of ecuflash? Is that something worth the risk?

[sergechronos]

Is the driver installation prompt coming up during install? Alternatively you could try download the driver thing from ECUFlash
Download Drivers + J2534 DLL

[Twofastoocatch]

After installing the drivers in the link, it made it worse. It then added a j2534 error. After rolling back the drivers, I went back to just the FTD2XXL.DLL error. This is the log I get, if it helps any?
[14:02:23.888] EcuFlash Version 1.44.3719
[14:02:23.888] OS Version Windows 7
[14:02:23.888] Qt Version 4.8.0
[14:02:23.888] 63 memory models read.
[14:02:23.903] scanning for metadata models in C:/Users/Jarvis/Desktop/ECU Programs/EcuFlash/rommetadata
[14:02:24.044] 611 ROM metadata models scanned.
[14:02:24.044] checksum module "subarudbw" loaded.
[14:02:24.044] checksum module "mitsucan" loaded.
[14:02:24.044] checksum module "mitsuh8" loaded.
[14:02:24.044] patch module "Subaru CAN Enhanced RAM Parameter Logging" loaded.
[14:02:24.044] patch module "Mitsu CAN RAM Parameter Logging" loaded.
[14:02:24.044] flashing tool "wrx02" loaded.
[14:02:24.044] flashing tool "wrx04" loaded.
[14:02:24.044] flashing tool "sti04" loaded.
[14:02:24.044] flashing tool "sti05" loaded.
[14:02:24.044] flashing tool "mitsukernel" loaded.
[14:02:24.044] flashing tool "mitsukernelocp" loaded.
[14:02:24.044] flashing tool "mitsubootloader" loaded.
[14:02:24.044] flashing tool "shbootmode" loaded.
[14:02:24.044] flashing tool "shaudmode" loaded.
[14:02:24.059] flashing tool "subarucan" loaded.
[14:02:24.059] flashing tool "subarucand" loaded.
[14:02:24.059] flashing tool "mitsucan" loaded.
[14:02:24.059] error loading FTD2XX.DLL
[14:02:24.075] J2534 API Version: 04.04
[14:02:24.075] J2534 DLL Version: 1.00.3719 Dec 28 2012 2348
[14:02:24.075] Device Firmware Version: 1.12.3688
[14:02:24.075] Device Serial Number: TAMtxQSP
[14:02:24.075] interface close
[14:02:24.106] J2534 API Version: 04.04
[14:02:24.106] J2534 DLL Version: 1.00.3719 Dec 28 2012 2348
[14:02:24.106] Device Firmware Version: 1.12.3688
[14:02:24.106] Device Serial Number: TAMtxQSP
[14:02:24.106] interface close
[14:02:24.137] J2534 API Version: 04.04
[14:02:24.137] J2534 DLL Version: 1.00.3719 Dec 28 2012 2348
[14:02:24.137] Device Firmware Version: 1.12.3688
[14:02:24.137] Device Serial Number: TAMtxQSP
[14:02:24.137] interface close