Please can someone help. I just recently purchased a tactrix open port 2.0 for the evo, I cannot get the damn thing to read my rom. I had the recall reflash done a couple of months ago. it reads the ecu fans turn on clicks, beeps, says it good when I close the window on the computer another window pops up and says unknown rom image.

 

It's because the ROM you are downloading from the ECU isn't on your computer. Save the file as something else and in any Hex program like HxD. Goto line 5002a it should look like this 55 59 00 06 which means it's ROM id 55590006 or simply a 2010 USDM Ralliart.

 

I'll try that. I tried to inherit the ROM and it did but it was a 2014 edm evo x.

 

If you send me that ROM image as an attachment to support at tactrix dot com, I'll take a look and recommend something close in number if we don't already have a definition.

-Mike
Tactrix

 

WTF!!!! I guess I'm computer stupid, when I open ecuflash and try to open a file there is nothing. When I open the files thru c/ program files /open ecu.... everything is there what am I missin

 

I'm not following what you're saying. Is it that you can't find anywhere on your computer the ROM image file you read from your ECU? Or that you know where it is, but when you try opening it in EcuFlash, you don't see it in the file selection dialog, even though you know you're looking in the right folder? If it's the later, then in the lower right of the EcuFlash file open dialog, switch the file filter from whatever it's on now (either raw ROM files (hex or bin) or SRF files) to the other format. Let me know if that makes sense.

-Mike
Tactrix

 

Mike,


Yes that makes sense. I can find the XML files in the computer but not in Ecuflash. All the files are XML files do I have to convert the files in order to view them in ecuflash?

 

Unless you're working on developing definitions, which is something that 99% of our users aren't doing, you don't view the XML files. XML files are used by EcuFlash to show where in your ROM image (.hex, .bin, or .srf file) the tables are. The XML describes the size, type, and location of the tables so that EcuFlash can display them to you correctly. You most likely are only concerned with reading your ROM image, saving a stock copy, editing it, saving it under a meaningful name to describe the modifications, and then using EcuFlash to write the modified ROM image back to your ECU.

You might want to check out this youtube series which does a great job of going over the basics of using EcuFlash.


It also happens to be done on an Evo X which is a bonus, through the concepts apply equally well to any Mitsubishi or Subaru you can tune with our hardware/software.

-Mike
Tactrix

 

when I open ecuflash and click on the folder icon it takes me to the evo folder but it is empty. Should there be xml files there when I open it.

 

No, when you click the open dialog, it's looking for .hex, .bin, or .srf files. EcuFlash is an editor for those three file types, which are associated with ROM images. EcuFlash is not an XML editor. It's like using Microsoft Word to browse for a word doc and wondering why it isn't showing you .dll files. Word no better understands non-Word documents than we understand non-ROM images. When you do a read of your ECU, you will save that file to a folder of your choice, and then when you want to open it later, EcuFlash will show it, or other ROM image files that you've acquired.

 

Thank you. I got it to work.
When I first downloaded my rom from my car it could not find the rom image so I did an inherent and it came up with a 2014 edm 5 spd my car is a 2008. Did I screw anything up by doing the inherit. I did have the reflash done by the dealership in Feb. and I had the cobb ap before I just switched over to tactrix. The cobb was unmarried and sold.

 

That's a pretty big year difference. Send me your original ROM and I can probably come up with something more appropriate. As I said before:

"If you send me that ROM image as an attachment to support at tactrix dot com, I'll take a look and recommend something close in number if we don't already have a definition."

 

My ROM id is coming up 52680028 in the hex editor. I did have my car reflashed per the dealer, in February.
Can I use 52680024

 

Yes, you can definitely use 52680024. We've had at least two customers in the same position as you. They went with the same substitution for 52680028. Generally speaking, you can usually interchange Mitsubishi ROMs if they have the same first four digits. That means you should be able to use any 5268XXXX. Since 52680024 is the most recent ROM with a full definition, that would be the most appropriate one to use.

-Mike
Tactrix

 

One more dumb question. Do I just use the 52680024 ROM and upload that to my ecu.