openecu.org

For the time being, I've stopped posting information about new software releases here. Instead, current downloads and release notes for official releases can be found here:

http://www.tactrix.com/index.php?option=com_content&view=category&layout=blog&id=36&Itemid=58

... and betas here:

http://www.tactrix.com/index.php?option=com_content&view=category&layout=blog&id=44&Itemid=65

... and stand-alone Driver + J2534 DLL packages here:

http://www.tactrix.com/index.php?option=com_content&view=category&layout=blog&id=38&Itemid=61

excellent work colby!

calvin.

a HUGE thank you for all your hard work and for making this possible!

just a quick question:
upon startup of the ecuflash, on the right task pane there is a message about FT2DXX.DLL missing. Are the direct FTDI drivers needed or the VCP drivers will work fine?

thanks again

Good observation. The software supports both VCP / real com ports and the FT2DXX drivers/DLL. The DLL is not needed to use VCP. Eventually I would like to move everyone with OpenPorts to using those drivers, as they provide much better control than the standard serial port APIs. I don't want to do this yet until I can get other software that uses OpenPorts like the Tari software to support this driver as well. Otherwise, you would have to keep reconfiguring your drivers to use these different pieces of software. The new Mitsubishi cable needs and uses these drivers, but since there is no other software which works with that cable yet, there are no legacy support issues.

xswrex wrote:a HUGE thank you for all your hard work and for making this possible!

just a quick question:
upon startup of the ecuflash, on the right task pane there is a message about FT2DXX.DLL missing. Are the direct FTDI drivers needed or the VCP drivers will work fine?

thanks again

Colby, thanks for your hard work.

Connected to my MY06 2.5 Sti (UK model) and it read first time with no problems.

I will post the file when I get home.

Edward.

Glad to hear it!

Everyone: please give me feedback as to any problems you might have with connecting to your vehicle...

colby...

do the table offsets need to be for 160kb or 192kb files?
are there any tags to define this?

calvin.

[04:56:10.452] flashing tool "evo" loaded.

Sorry, I don't understand - does it work on Mitsubishi's ?
with 16V on PROG ECU pin of course.

suscribe

Wow, I picked the right day to come back onto this site and check out status.

I've been sidelined with a major project at work, and will probably be busy for another few weeks, and the car's been offline due to a leaky water pump.

Between this, the latest versions of ecuEdit and Enginuity, and the ecuExplorer source release, I've got a lot of project ideas.

/Andrew

Thanks a ton Colby, your work is amazing!

All offsets are the "real" offsets in the ECU, so in the case of the WRX, this would be equivalent to the 192k file. EcuFlash saves all ROMs in a compact (e.g. 160k for WRX) format. It will automatically read the 192k files though. I know this can be a bit confusing... I'm trying to make the program generic, and some ECUs have sparse address spaces. I wouldn't want to make a 4GB file just because and ECU had 64k at 0xFFFF0000 also. I may make an option to save the file as 192k for WRX instead. The software can already do that internally.

calvinc wrote:colby...

do the table offsets need to be for 160kb or 192kb files?
are there any tags to define this?

calvin.

YP wrote:[04:56:10.452] flashing tool "evo" loaded.

Sorry, I don't understand - does it work on Mitsubishi's ?
with 16V on PROG ECU pin of course.

That code is already done, but you need hardware which supports an electronically controlled PROG ECU pin. I will release another version in a couple of weeks when the hardware is available.

Colby

I don't know if this is the right place to post this but I've attached the file from my MY06 Impreza 2.5 STI (EURO) [AL340-2190] 6MT.

Found this in the file:
4a rA8DH200Z 46VEU Sti
Corp DENSO 2005
PF 23VH4T 80m Ver1.51r1

Woo hoo!

(dancing banana goes here)