ERROR WITH ECUFLASH123

[daddyhaw]

AFTER INSTALLING ECUFLASH 123 AND TRYING TO RUN THE APP I GET THE FOLLWOING MESSAGE
"The procedure entry point setvbug could not be located in the dynamic link library MSVCR71.dll"

Any ideas?

[cboles]

I made a mistake in the installer, and I have fixed it and updated the downloads on the site. You will still need to do one thing manually to make things work. Go to

C:\Program Files\OpenECU\EcuFlash

and delete the two .dll files before reinstalling with the new version. Things should be OK after that.

Colby

[daddyhaw]

Colby,

That allows the program to open now thanks.
Question, Will it read my JDM Sti TWIN SCROLL? Ah581-5122

I tried with the earlier verision (before realizing u had responded) .
and it did not work.

It kept saying "dens002_bootloader_cmd_start"

[cboles]

What year is that model?

[daddyhaw]

its a 2003 JDM sti TWIN SCROLL
AH581-5122

[Spiider]

I have the exact same ecu. It is probably one of the most "fully tuned" ecu's on here now thanks to my good friend "west minist", who has spent loads of time with me on the phone and email trying different revisions and reviewing my logging.

Look in the JDM STi Twin Scroll section further down the page and you shall find the answers you are looking for.

[cboles]

Do you have the green test mode connector plugged in?

Colby,

That allows the program to open now thanks.
Question, Will it read my JDM Sti TWIN SCROLL? Ah581-5122

I tried with the earlier verision (before realizing u had responded) .
and it did not work.

It kept saying "dens002_bootloader_cmd_start"

[/img]

[swifty]

I was initially having problems downloading the rom off my car, it turned out I just wasn't quick enough between pressing the ok button and getting the ignition turned on. I found a thread on here somewhere that told me to leave ignition off, connect everything up and select the 'read from ecu' option and get the dialogue box. Click ok and turn the ignition on immediately, a delay can make it fail. That worked for me.

[daddyhaw]

click OK the turn ignition ON?

After getting dialogue box, I turn ignition ON then click OK.
I will ltry this sequenceand let you know

[daddyhaw]

tried that and still not able to read.
here are screen shots of what happened

[Spiider]

Physical car:
key is off
white test block jumpered
green test mode connectors connected together

Physical PC:
tactrix cable drivers installed
tactrix cable connected to usb on PC and obd2 port on car

Software PC:
open ecuflash software
select correct port for tactrix cable
select correct model of car (2002-2003 wrx for you)
select rom to burn
start flash process
confirm following dialog box by clicking ok
reach over and turn key forward until dash lights up

*you should not have fans cycling etc. even though green connectors are connected, if fans start cycling like green connectors test mode normally does, then start again from the top and don't read past anything too quickly, if it wasn't important I wouldn't have written it.

This works every single time on my car. Same ecu.

[JRSCCivic98]

You don't need to jumper the white (flash block) to "read" the ecu rom. Just FYI.

[cboles]

Similarly, there is really no harm in leaving the flash jumper connected, unless you think that you will go through all of the steps in EcuFlash to flash your ECU accidentally. I leave those connectors in my car all of the time. It is only the test mode connector you must connect / disconnect.

You don't need to jumper the white (flash block) to "read" the ecu rom. Just FYI.

[daddyhaw]

I have done everything as Spiider said(EXCEPT white test block jumpered), and i have the problem. The fans are cycling and they should not be based on what spiider is saying.

So I will try to jumper the white test block.


Aso the options in ecuflash 1.24 are 2001-2003 WRX & 2004-2005 WRX
So I am choosing the 2001-2003 WRX

BTW ECUFLASH does give me this message
ECU ID is 2E 04 49 60 05
ssm2_cmd_0x81
then it says "an error occurred. See the log for details"

Spiider thanks for taking the time to wriet out everything

[Spiider]

No problem, I can understand the frustration of a beginner.
Once you get it working you'll wonder why it was a problem in the first place.

I highly recommend connecting the white test block jumper, I am the same as Colby in that regard.

I'm flashing my ah581 so much lately that I permanently jumpered the white block and put 12" spade extensions on each of the green connectors so that I can connect them remotely.

I don't recognise the error message you are getting, but one clue is that the fans are cycling. What happenes to me is that I click the software twice to start the burn, and then turn the key forward about 1 second later and it "catches" every time. What will happen is that the fans will not cycle like they normally would in test mode.

Then the read or write takes only a couple seconds, its very fast to reflash, reading takes a bit longer.


You should maybe try to use the older version just before the map editing was added. I use 1.00.63 without fail.