Page 5 of 7

DLL error on my laptop - FIXED, FTD2XX.DLL error on desktop

PostPosted: Mon May 15, 2006 10:10 am
by S54fan
Tried installing ECU flash 1.26 on my laptop and got a DLL error. Windows 2000 Pro. See pic.

I installed this file into the WinNT/system directory along with MSVCR71.dll and now it works. Must be a Win 2K thing.

Also, on my desktop there is the error about the missing FTD2XX.DLL - does this no longer matter on 1.26? I know these are very basic questions, but I've been searching. I know the driver is included on 1.26 so I can I just ignore the error message

PostPosted: Mon May 15, 2006 10:30 am
by cboles
The driver portion of the installer should have put the FTD2XX.DLL in your winnt\system32 directory (from the ecuflash\drivers directory). If you do that the message should go away.

PostPosted: Mon May 15, 2006 10:42 am
by S54fan
:D sorted

I get the cable tomorrow - can't wait! : :D :P :)

small bug in 1.27

PostPosted: Mon May 15, 2006 9:42 pm
by Matz
I found a small bug in v1.27. If you open any maps / dialogs, and then Alt-Tab to another app and back, everything goes behind the main app's window.

PostPosted: Tue May 16, 2006 1:53 am
by New2Scoobs
Colby, V1.27 is a marked improvement over 1.26 in terms of displaying the data in the maps but there still appears to be an issue with the width of the "RPM" column. See below.

PostPosted: Wed Jun 14, 2006 11:32 am
by nv-wrx
I had that problem. Exiting ECUFlash and re-opening it seemed to fix it.

Colby, V1.27 is a marked improvement over 1.26 in terms of displaying the data in the maps but there still appears to be an issue with the width of the "RPM" column. See below.

PostPosted: Mon Jul 10, 2006 6:01 am
by JRSCCivic98
Colby, can you put the "flash method" back in ecuFlash as a menu choice please? XMLWrite doesn't put in the corrent flash methods and I'm getting tired of having to put them in. I personally liked it when it was a menu choice... dunno why you changed it. Is that possible or do you think it'll cause problems with some users?

PostPosted: Mon Jul 10, 2006 6:15 am
by cboles
I understand your pain - but it was never a menu choice, except when you are loading an unknown ROM, in which case it still is. The idea is for an existing ROM definition, you would never change this, so the question / choice only comes up when EcuFlash sees something new.

c

PostPosted: Mon Jul 10, 2006 7:49 am
by MalibuJack
cboles wrote:I understand your pain - but it was never a menu choice, except when you are loading an unknown ROM, in which case it still is. The idea is for an existing ROM definition, you would never change this, so the question / choice only comes up when EcuFlash sees something new.

c


I get a few questions here and there about using an incorrect definition, and how to get it back.. So its probably a good idea to have a feature that lets you redefine the rom to a new or different definition, after you do it once incorrectly, you have to know to find and delete the new inherited/generated definition to get it to a point where you can do it again...

PostPosted: Mon Jul 10, 2006 8:30 am
by cboles
It is actually on the todo list - to be able to edit the ROM info, so I can include that there.

PostPosted: Mon Jul 10, 2006 4:39 pm
by JRSCCivic98
cboles wrote:I understand your pain - but it was never a menu choice


Yes it was, back in the day when all ecuFlash was was a GUI for the DOS based command version. I liked it back then. :)

PostPosted: Thu Aug 03, 2006 9:21 am
by alwaysinboost
anyone have a time table on when the next version of ECUFlash will be out???

PostPosted: Thu Aug 03, 2006 1:44 pm
by Sanctifier
GTODesign wrote:E5/6 does have the second init connector but the E4 doesn't.
E5/6 uses a different MCu to E7/8 which may explain why you are having problems with your OBDII loggers.

GTO I'm afraid that neither the E6 GSR or E6 RS2 (my model) have the second re-flash socket.

I am trying to initialize my Evo 6 RS2 ECU with the Tactrix OpenPort 1.3M cable.

I read this in another thread. Not sure if it also applies to my problem...
cboles wrote:...The new Mitsubishi cable needs and uses these drivers, (sic~ FT2DXX drivers/DLL) but since
there is no other software which works with that cable yet, there are no legacy support issues.

Unlike the Evo 7-9 models, the Evo 6 RS2 has no additional socket alongside the
OBDII port under the dashboard.

I'm looking for an alternative connector or wire that can be used on the
1999-2000 Evo 6 RS2s (with Immobilizer) for initialization to reflash the ECU.

I know that the Evo 6 software is still a work-in-progress... but this seems
to be more of a hardware issue that will have to be addressed anyway.

At the moment any attempt to initialize results in this error message...
"H8/500 processors are not yet supported!"

Any help or advice appreciated.

PostPosted: Mon Aug 21, 2006 5:58 pm
by danl
Is it possible that a description of all the parameters we get to edit can be put in a list? Some of the things in the Evo rom’s have me confused such as all the open loop high load and open loop low load as well as load #1 and load #2.

Or perhaps such a file has been made and I just need pointed in the right direction? Otherwise seems to work well for me.

PostPosted: Tue Aug 22, 2006 4:42 am
by red^shark
Or perhaps such a file has been made and I just need pointed in the right direction?


I am assuming you started your learning by reading the Ecuflash tutorial?
http://forums.evolutionm.net/showthread ... h+tutorial


Red