PDA

View Full Version : EcuFlash basic startup question.



Davezj
05-09-2011, 09:08 PM
Hi All,
after some basic advice.
i have a 7202 ecu and openport 2.0 cable. so the hardware is correct.

i have used EcuFlash a few times, but i had to delete it from my PC and now it will not connect to my ECU.

i can't remember what directory paths i need to set for the hex file to be saved in and the xml and colour file.
also i think i had to make a VR4 folder someware as well. So basicly it is a start from scratch install.
i set this all up about a year ago, and not really used it since so i just don't remember.
also when reading ECU, do you use the 1996-2001 evo G2 format to connect (well the frirst one on the list). i think this the right one to use.
so any help will be greatly received.

if you can bullet point me in the right direction that would be great, also it would be usefull for and newbie flasher.

foxdie
05-09-2011, 09:53 PM
Hi Dave,

Firstly, make sure you're using EcuFlash version 1.43.3150, this appears to be the most stable, you must also install this AFTER installing EvoScan as EvoScan includes its own, older firmware drivers for the OpenPort 2.0 unit.

Once you've done that, keep your ROM files (hex and bin) in a safe place such as "My Documents -> My ROMS", that way if you're only backing up your My Documents folder, you've got a backup of the files that matters.

XML Definitions can be stored wherever you like providing you point EcuFlash to that folder in its settings, however for the sake of simplicity, place vr4base.xml and it's VR-4 related kin inside something like C:\Program Files\OpenECU\EcuFlash\rommetadata\vr4, so long as it's in the rommetadata folder and EcuFlash is set to use that path (C:\Program Files\OpenECU\EcuFlash\rommetadata), it will go through every folder to find definitions.

Colormaps should always be the default - C:\Program Files\OpenECU\EcuFlash\colormaps

When reading ROMs, select the Evo 5/6 MH7202F format, be careful not to choose MH7202FA though, only choose that if the first one won't read :)

Ps. You'll also need to enable developer mode in the settings to access / edit some of the ROM tables.


Hi All,
after some basic advice.
i have a 7202 ecu and openport 2.0 cable. so the hardware is correct.

i have used EcuFlash a few times, but i had to delete it from my PC and now it will not connect to my ECU.

i can't remember what directory paths i need to set for the hex file to be saved in and the xml and colour file.
also i think i had to make a VR4 folder someware as well. So basicly it is a start from scratch install.
i set this all up about a year ago, and not really used it since so i just don't remember.
also when reading ECU, do you use the 1996-2001 evo G2 format to connect (well the frirst one on the list). i think this the right one to use.
so any help will be greatly received.

if you can bullet point me in the right direction that would be great, also it would be usefull for and newbie flasher.

Davezj
05-09-2011, 10:11 PM
Cheers jason i will try it tomorrow, great bit of info there.

Davezj
06-09-2011, 06:52 PM
i have tried to connect to my ecu again, and it will not read it, i am ovviously doing something wrong but i don't know what.

here is the log of my verious attempt to connect

[18:33:09.341] J2534 API Version: 04.04
[18:33:09.341] J2534 DLL Version: 1.00.3147 Sep 3 2010 00:11:07
[18:33:09.341] Device Firmware Version: 1.11.3137
[18:33:09.341] Device Serial Number: TA$1NAzj
[18:33:35.484] sending init sequence 2
[18:33:37.512] interface close
[18:34:21.294] J2534 API Version: 04.04
[18:34:21.294] J2534 DLL Version: 1.00.3147 Sep 3 2010 00:11:07
[18:34:21.294] Device Firmware Version: 1.11.3137
[18:34:21.294] Device Serial Number: TA$1NAzj
[18:34:26.970] sending init sequence 2
[18:34:28.982] interface close
[18:34:42.281] J2534 API Version: 04.04
[18:34:42.281] J2534 DLL Version: 1.00.3147 Sep 3 2010 00:11:07
[18:34:42.281] Device Firmware Version: 1.11.3137
[18:34:42.281] Device Serial Number: TA$1NAzj
[18:34:46.017] sending init sequence 2
[18:34:48.029] interface close
[18:35:30.577] J2534 API Version: 04.04
[18:35:30.577] J2534 DLL Version: 1.00.3147 Sep 3 2010 00:11:07
[18:35:30.577] Device Firmware Version: 1.11.3137
[18:35:30.577] Device Serial Number: TA$1NAzj
[18:35:33.467] sending init sequence 2
[18:35:35.480] interface close
[18:38:11.838] J2534 API Version: 04.04
[18:38:11.838] J2534 DLL Version: 1.00.3147 Sep 3 2010 00:11:07
[18:38:11.838] Device Firmware Version: 1.11.3137
[18:38:11.838] Device Serial Number: TA$1NAzj
[18:38:11.838] interface close

i have used the cable to read my ecu before and it is a openport 2.0 rev E.
and the cable works fine on the same laptop with evoscan logging.

foxdie
06-09-2011, 07:09 PM
Hi Dave,

Not immediately sure why that's happening, just to double check, you had the reflashing cable connected at the same time too? No loose connections? Tried turning car ignition off and on again? Made sure OpenPort was connected to laptop BEFORE connecting to OBDII port?

I can't test mine to compare API / DLL / Firmware versions as I've left the bloody thing at work :)

I'll check it when I get into the office tomorrow morning and let you know.

Nutter_John
06-09-2011, 07:11 PM
likewise my one is in the office as well , you tried re-installing the Beta version to ensure the drivers are correct

also did ya have the white plug in ?

Davezj
06-09-2011, 07:34 PM
sorry guys i knew i was being a muppet!

i had forgotten you need the other coneector in place to allow the read of the ecu.
i was under the inpression that you only needed both connectors to write to ecu and only one to read, but that is not the case

MUPPET!!!

sorry agaian and thanks for your input.

foxdie
06-09-2011, 07:46 PM
We all have blonde moments ;)

Let us know how you get on mate.

Nutter_John
06-09-2011, 08:43 PM
Dave wins this months MUPPET award :D

Davezj
06-09-2011, 10:04 PM
this club should have a muppet of the month award loosely called the MOM award.
it is an honer to receive it and a muppet crown should appear over your login name with a link to the relative thread or post as proof of becoming a fully fledged Muppeteer.

Nutter_John
06-09-2011, 10:06 PM
Where I used to work we had the Noddy award which went to the person who made the most stupid mistake , you kept the award until some one made a far worse mistake , they would have to stick a toy noddy from a happy meal on there monitor for all to see

record was 3 awards in a row , after 4 years it was retired as no one could beat the previous cock ups :D