What is wrong with my ECUflash/EvoScan?

[HLxDrummer]

Alright.. I used to run Chrome V1 and Evoscan 2.6 no problems. V2 came out so I installed that along with Evoscan 2.9 no problems.

Got a CEL after installing injectors so I had to switch back to Evoscan 2.6 to scan them. I also deleted the .dll file that Forest said to delete in the Evoscan folder. Worked fine.

These programs then started acting up on me for some reason so I uninstalled everything and started from scratch. Got the new ECUflash (was previously using the previous I downloaded when V1 was out), and Evoscan 2.9. ECUflash installed new firmware on my Openport 2.0. The new ECUflash also didn't have a folder for 3000GT so I just made one to put the Chrome file in.

Now when I go to flash using ECUflash, it acts like everything is fine but then says interface close and doesn't flash. Not sure what the issue is there..

I tried using Evoscan 2.9 to disable injectors and it just says read error J2534 - 16. I think it says connection successful, though.

Not sure where to go from here. Can I download the older ECUflash? Can I downgrade the firmware on Openport? Should I do any of those things? I feel like everything on my car/laptop just gave up on me suddenly lol The laptop is an old Dell running XP, by the way.

[Greg E]

Probably a driver issue causing your ECUFlash connection errors.

As for EVOScan 2.9, it just flat out sucks... I should have tested it more thoroughly before releasing my file for it. I am considering stepping back to evoscan 2.7 for the next version of chrome or even just finding a new logging program all together.

[HLxDrummer]

Alright thanks for the suggestion I will look into driver issues.

As far as logging, I'm guessing it isn't possible to use 2.6/2.7 with V2 because your files are different, correct?

Thank you!

[Greg E]

I can make a 2.7 file. Maybe ill do that tonight.

[TwIzTeD_3kGt]

I have no problems at all with 2.9 other than it can't read codes properly (for which I have multiple other methods). I'm using an old Dell Inspiron 1200 on XP.

You said you made a folder for the 3000gt.xml (or whichever file)? Maybe that's your issue? The instructions didn't say to do that. Maybe an address issue because of the folder you made? I thought of doing the same since all the other cars had a folder, but stuck with the instructions and I have no problems.

[Greg E]

I have no problems at all with 2.9 other than it can't read codes properly (for which I have multiple other methods). I'm using an old Dell Inspiron 1200 on XP.

You said you made a folder for the 3000gt.xml (or whichever file)? Maybe that's your issue? The instructions didn't say to do that. Maybe an address issue because of the folder you made? I thought of doing the same since all the other cars had a folder, but stuck with the instructions and I have no problems.

If that folder was an issue, ECUFlash wouldn't even be able to open the 23682006.bin file. Very very highly doubt that's the issue.

[TwIzTeD_3kGt]

If that folder was an issue, ECUFlash wouldn't even be able to open the 23682006.bin file. Very very highly doubt that's the issue.

Probably not, just the only thing I see different between his and mine.

[HLxDrummer]

2.6 used to work fine for logging (that's all I used it for). I didn't get around to tuning V2 yet and I couldn't really figure out how to use 2.9 so never did logging with it. I THINK I used it to disable injectors (but I could have done that after I downgraded to 2.6).

And the instructions I found said to PUT it in the 3000GT folder (as if it should be there already). When I had V1 the folder was already there. Not sure what to think about that. Figured since ECUflash opened the tune that it worked.. How did you do yours?

[Greg E]

2.6 used to work fine for logging (that's all I used it for). I didn't get around to tuning V2 yet and I couldn't really figure out how to use 2.9 so never did logging with it. I THINK I used it to disable injectors (but I could have done that after I downgraded to 2.6).

2.6 worked perfectly for logging and reading codes except you could only do 4 injectors instead of 6. It didn't even disable the correct injector anyway... Never played with 2.7 or 2.8.

The 2.6 file I release for chrome V1 isn't compatible for Chrome V2.

[TwIzTeD_3kGt]

2.6 used to work fine for logging (that's all I used it for). I didn't get around to tuning V2 yet and I couldn't really figure out how to use 2.9 so never did logging with it. I THINK I used it to disable injectors (but I could have done that after I downgraded to 2.6).

And the instructions I found said to PUT it in the 3000GT folder (as if it should be there already). When I had V1 the folder was already there. Not sure what to think about that. Figured since ECUflash opened the tune that it worked.. How did you do yours?

Whatever I read just said to put it in the directory that has all the car's folders in it. Didn't specify to make a folder for it.