OpenFlash Tablet v1.52b Maps now available in Database Format

[Vlady]

Originally Posted by shiv@vishnu

Here is your ecutek "stock" ROM compared to an actual stock ROM:



You can see some non-stock data where there should be FFs. This also changes the checksum data at the end of the ROM (not shown).

Until we come up with a way to flash non-stock and old ROMs to new stock ROM status, I've added your ecutek "Stock" rom to the database so it should work for you now.

soooo.....now v1.53 is released

v1.53b Changes:
-Replaced the stock A01G and A01D ROMs in the database with actual stock ROMs.
-Added a “stock” Ecutek ROM to the database.

If anyone else with one of the supported ROM types doesn't get tuned map file generation, please email me your original ROM so I can compare it to the counterpart in our map database. If they aren't 100% identical, tuned map files will not be generated. I will have to add your original ROM to the database.

Cheers
shiv

OK.. so forgive me here. What does this mean??lol

[Fizz]

Originally Posted by shiv@vishnu

Great. I'll add your ROM to the database later tonight and post up a new .dev file

It's possible that the A01G in the database isn't perfectly stock. Since you are sure yours is, I'll replace it with your file.

Hi Shiv, for the preloaded OFT's being shipped out this week, how "up-to-date" are the preloaded files in there? Would it come with the latest 1.53b release?

[Shiv@Openflash]

Originally Posted by Fizz

Hi Shiv, for the preloaded OFT's being shipped out this week, how "up-to-date" are the preloaded files in there? Would it come with the latest 1.53b release?

Yep. We will always load the newest release before shipping OFTs.

[Apoc]

1.53b works for me meow. Thanks Shiv

[steve99]

Originally Posted by shiv@vishnu

Great. I'll add your ROM to the database later tonight and post up a new .dev file

It's possible that the A01G in the database isn't perfectly stock. Since you are sure yours is, I'll replace it with your file.

Hi Shiv,

A01G works for me now thanks

[Ondreiko]

Originally Posted by shiv@vishnu

Great. I'll add your ROM to the database later tonight and post up a new .dev file

It's possible that the A01G in the database isn't perfectly stock. Since you are sure yours is, I'll replace it with your file.

Hi Shiv!

Just tried 1.53b to write, but "write" button is grey.
Will send you my original ROM shortly.
Please take a look what is wrong in my case.
Thank you in advance,

Andrey A00G.

[steve99]

Originally Posted by Vlady

OK.. so forgive me here. What does this mean??lol

Ecutek have written extra bits of data into the "stock" rom in areas that are just padding or spare space ie ""FF".

This may be for various reasons, but likely to be so that ecutek can identify the ROM as one of theirs for licensing/locking tune ect or that Ecutek has written to this ROM/vehicle at some stage.

Ecutek can also add extra features to their ROM's (RaceROM's (not this one as its a "stock" ROM), to do this they patch the original ROM's instruction code with extra code (program instructions) to perform extra functions such a map switching. this extra code need's to be inserted in "spare" or unused spade in the ROM usually this will be filled with "FF". The extra code data for alternate maps ect is usually inserted in this unused space. These ROM's are also locked/encrypted such that an ECUTEK licence is required to access/flash the ROM's I believe not even dealers can access/flash ecutek locked ROM's

Well that the way i think it works anyway.

[tonystewart]

Originally Posted by shiv@vishnu

Yep. We will always load the newest release before shipping OFTs.

That's great news for me!

[enwave]

Any more details as to what some of those trim/timing changes etc. are relative to 1.42b?

I'm interesting in knowing a little bit about what adjustments are made and why, for learning purposes! If you'd rather PM to keep it more private, that's okay too!


Sent from my iPhone using Tapatalk

[AdrianG]

Originally Posted by enwave

Any more details as to what some of those trim/timing changes etc. are relative to 1.42b?

I'm interesting in knowing a little bit about what adjustments are made and why, for learning purposes! If you'd rather PM to keep it more private, that's okay too!


Sent from my iPhone using Tapatalk

Easiest way is to datalog and compare the results:

Stage 1 1.42b

Stage 1 1.52b

Not the same stretch of road, but more or less the same conditions and the same tank of gas.

[Shiv@Openflash]

Originally Posted by Ondreiko

Hi Shiv!

Just tried 1.53b to write, but "write" button is grey.
Will send you my original ROM shortly.
Please take a look what is wrong in my case.
Thank you in advance,

Andrey A00G.

You should be good to go now with the v1.54 download. I updated the stock A00G file with your original ROM

Cheers,
Shiv

[moK]

Originally Posted by shiv@vishnu

What is your ROM type/CAL ID?

OpenFlash Manager reports my CAL ID as ZA1JA00C. However, plugging in the OFT into my car and going into Tuning -> ECU Info reports my 'Calibration Code' as ZA1JA01C, while going into Information from the main menu reports 'File in ECU' as a ZA1JA00C bin. I'll send you my stock file to take a look at.

[Shiv@Openflash]

Originally Posted by moK

OpenFlash Manager reports my CAL ID as ZA1JA00C. However, plugging in the OFT into my car and going into Tuning -> ECU Info reports my 'Calibration Code' as ZA1JA01C, while going into Information from the main menu reports 'File in ECU' as a ZA1JA00C bin. I'll send you my stock file to take a look at.

That's totally fine. Your original ROM is indeed an ZA1JA00C. However, when updating your ROM with the new v1.5 maps, your ROM will be updated to A01C.

[moK]

Originally Posted by shiv@vishnu

That's totally fine. Your original ROM is indeed an ZA1JA00C. However, when updating your ROM with the new v1.5 maps, your ROM will be updated to A01C.

Thanks for the super quick reply. In that case, any idea why Write would still be grayed out?