Epifan,

Having converted over ECUflash xml defs for Subaru and Mitsubishi there are some Mitsubishi ROMS ECUflash will open and ECUedit wont even though i've converted from the same ECUflash defs.

Is there a solution for this or have i missed something??

Also ECUflash has support for EVO 5+6 ECU's with Tactrix OP 2.0. I noticed ECUedit doesn't.

Cheers

spanmanuk wrote:Having converted over ECUflash xml defs for Subaru and Mitsubishi there are some Mitsubishi ROMS ECUflash will open and ECUedit wont even though i've converted from the same ECUflash defs.

Please, contact to me by e-mail and point ECU ID that you try to open in EcuEdit. Also point to me which version of EcuFlash do you use.

spanmanuk wrote:Also ECUflash has support for EVO 5+6 ECU's with Tactrix OP 2.0. I noticed ECUedit doesn't.

I haven't Evo6 around me for testing...

I use latest ECUflash 1.42.2595

ROM ID's: 8997-09 and 8884-16 not able to open.

Is there any way to make ECUedit accept EVO VI definitions with just the ROMS or does it have to be done with EVO VI car?

Bump.......

Any new news on this yet?

I've just noticed...you said email...apologies

spanmanuk wrote:I use latest ECUflash 1.42.2595
ROM ID's: 8997-09 and 8884-16 not able to open.

I've no problems with converted defs from EcuFlash 1.42.2595 using latest ecuEdit. All maps are correct. If you have several descriptions of one ECU program ask you about what to choose. May be you choose wrong description..
Send to me screenshots of all ecuEdit messages and map problems.

spanmanuk wrote:Is there any way to make ECUedit accept EVO VI definitions with just the ROMS or does it have to be done with EVO VI car?

Yes. ecuEdit.xml must be edited

Code: Select all

<ecu_desc file_size="#20000" name="EVO5-6 16bit ECU" desc_size="#30000" type="evo16">
   <map_id offset="#21A" length="4" data_format="BCD"></map_id>
</ecu_desc>