Cool. Thanks for the update/clarification.

Being new to "tuning", I would definitely appreciate a finished (non-beta) product to get started.

 

razorlab is one of the beta testers. The beta testers need to try it on as many cars as possible, so he's been trying it out on customer cars. He also tunes the cars a bit while he's at it.

 

Here's the issue to everyone who is asking for the software .. you may be able to download the ROM .. but you may not be able to view anything usable ..

I have encountered a few variants of the SM5268 now .. and while the ROM ID is the same .. the map locations are different .. so you'll see a bunch of weird numbers instead of the maps ..

I know it's painful .. if Mychailo hadn't roped me in for the testing .. I would be one of you guys .. the pain of finding all the maps is not funny at all ..

Just a little longer

I need Razorlab or USDM users who have weird maps to send it to me so I can generate the variant XMLs ..

 

Two more X's in a couple days, I'll let you know.

 

^ That all went over my head... You're saying if you released the software I wouldn't be able to read MY maps?

 

Possibly, yes.

 

What's going on is that say you have the USDM version and your ROM ID is SM5268 so you load the SM5268 XML into ECUFlash. When you open the ROM, you may be lucky and be able to see all the MAPs. If you happen to have a different variant of the SM5268, all the MAPs will look like a bunch of weird out of place numbers.

I'm seeing the same thing happening with the JDM versions too. It's hard to say but it maybe the difference between ROMs that got the factory reflash or not (different revisions).

 

Sorry for all the pain. I'm very impressed with how much effort you are putting into this. It really is a great service to the community. Most of the people here are so new to ECUFlash that they cannot appreciate how much time/effort you are putting into this.

You haven't seen any sort of variant ID tag in these SM5268 ROMs?

 

So far all the IDs I've already listed .. its within these IDs that are having the issues .. Only ID I haven't seen now is USDM SST ROM ..

The ROM will be identified as one of the XML rom ids .. but the maps are scrambled when you open them ..

I suspect these are factory flash updates .. same ID .. but re written software locations ..

 

This is the part I don't get....how is it you can read a map but if it possiably got a factory update then you can read the maps....

I know I have both factroy updates, so does that mean I couln't read my maps with the current state of ECUFlash? Or what is the cause of this? I'm confused how you can read one ECU but not another.

 

The ECU (Rom file) we can read just fine, but depending on the actual ID of the file, some of the actual maps (example: Fuel/boost maps) are at different addresses in the Rom file than another rom ID.

EcuFlash uses a definition file to make the maps look like something a human can understand. The definitions point to a certain hex address within the Rom file to show the actual map. If the actual hex address is different in a ROM ID then it will look like gibberish.

make sense?

 

Here's what the maps look like with different revisions. The top is how it's suppose to look like, the bottom is all out of wack due to a different revision.

 

Makes sense now. Looks normal on the timing map till the bottom half. Weird. None the less great work. Find any pattern with these ROM's not reading right? Got multiple XML's going to fix those? Like say you're reading the top one correct then you read one like the bottom got an XML to fix it already? And I'm guessing a new XML would make the first map go bad too. So will there be multiple XML's for certain owners, or can you make one XML to fix the issue?

 

Yes EcuFlash will eventually have XML files for all the different ID's, much like it is now with the 8's and 9's.

 

i had same result when trying open EDM rom with USDM xml