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

[Shiv@Openflash]

Originally Posted by Luckrider

I was just wondering if the intake/exhaust advance was to account for the header.

I'm on my 3rd tank of e85 and with my log with the longest time before flashing (probably 300 miles) had the highest ltft down to .74%

http://www.datazap.me/u/luckrider/e8...og=0&data=1-11

Edit: There is a 3rd gear pull from 1500rpm at ~1500s on that log.

A section of your previous log (which had more driving/learning time):


Notice how your LTFT under load dropped to -7.03% to account for the lower ethanol content in your fuel. Expect to see the same behavior with the new map (or after every new flash) after some more driving/learning time. Right after your flash, LTFTs will be 0.0%. As you drive more, they will start to move in the direction you need them to move in order to achieved the desired AFR under load

[Luckrider]

Originally Posted by shiv@vishnu

A section of your previous log (which had more driving/learning time):


Notice how your LTFT under load dropped to -7.03% to account for the lower ethanol content in your fuel. Expect to see the same behavior with the new map (or after every new flash) after some more driving/learning time. Right after your flash, LTFTs will be 0.0%. As you drive more, they will start to move in the direction you need them to move in order to achieved the desired AFR under load

So the -% in LTFTs helps lean out the car a tad to accommodate for the higher dino content of the fuel? I am not upset at all that my station is pumping low E since it is terribly cold here. My car starts right up without messing with the IPW. Vra vra vree VROOM! is all that it takes every single time.

[Shiv@Openflash]

Originally Posted by Luckrider

So the -% in LTFTs helps lean out the car a tad to accommodate for the higher dino content of the fuel?

Exactly

I am not upset at all that my station is pumping low E since it is terribly cold here. My car starts right up without messing with the IPW. Vra vra vree VROOM! is all that it takes every single time.

I agree. Having a lower E content is great for the reason you mentioned. Plus, it's overkill to run E85 on an NA FA20. It will get all the cooling/octane it needs to make max power at somewhere around E60.

[FrsDuke]

Originally Posted by RSH

Just the opposite for me. I have an EL and axleback and it sounds much quieter to me.

I am loving it though, throttle response is incredibly smooth and seems very uniform throughout the range. Much, much better than any previous release IMHO.

When I went from stock to 1.34 I noticed a marked decrease in drone and overall volume. Love it. I'm stock aside from a track pipe. Hope my drone doesn't come back when I can finally run 1.5 haha

[steve99]

Originally Posted by shiv@vishnu

OFT v1.51 maps will support the following Australian Market ROMs by tomorrow afternoon:

ZA1JA00G - 2012 EU Manual High FD
ZA1JA01G - 2012 EU Manual High FD
ZA1JA01I - 2012 EU Auto

Cheers,
shiv

Hi Shiv,

Erased tune files from OFT (except stock rom)
Loaded 1.52B dev database synced ok on OFM
I am on ZA1JA01G rom type (AU BRZ Sept 2013)
go to car but "write" greyed out
I currently have 1.42B stage 1 flashed to car do I need to flash back to stock before using 1.52B dev tunes ??
or something not correct in dev file for A01G roms ?

Thanks

[Shiv@Openflash]

Originally Posted by steve99

Hi Shiv,

Erased tune files from OFT (except stock rom)
Loaded 1.52B dev database synced ok on OFM
I am on ZA1JA01G rom type (AU BRZ Sept 2014)
go to car but "write" greyed out
I currently have 1.42B stage 1 flashed to car do I need to flash back to stock before using 1.52B dev tunes ??
or something not correct in dev file for A01G roms ?

Thanks

Email me (shiv@vishnutuning.com) your original ROM. It's probably different from the original A01G rom that is in the database. Which is why it's not recognizing your ROM type. Have you had your ECU flashed before by another other tuning device?

-shiv

[steve99]

Originally Posted by shiv@vishnu

Email me (shiv@vishnutuning.com) your original ROM. It's probably different from the original A01G rom that is in the database. Which is why it's not recognizing your ROM type. Have you had your ECU flashed before by another other tuning device?

-shiv

Hi Shiv will email my ROM to you
I have not used any other tuning device other than OFT
Thanks for reply

[Shiv@Openflash]

Originally Posted by steve99

Hi Shiv will email my ROM to you
I have not used any other tuning device other than OFT
Thanks for reply

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.

[Apoc]

@shiv My CAL ID shows as ZA1JA01C but isn't letting me use the dev tunes. I think my original rom is just a ecutek stock rom.

[Shiv@Openflash]

Originally Posted by Apoc

@shiv My CAL ID shows as ZA1JA01C but isn't letting me use the dev tunes. I think my original rom is just a ecutek stock rom.

That's the problem. It's not actually a stock ROM. Email it to me please.

[Apoc]

Originally Posted by shiv@vishnu

That's the problem. It's not actually a stock ROM. Email it to me please.

just sent

[Cross]

Hey Shiv I have a question and possible suggestion.

Where can we check which dev version our OFT has from the OFT itself?

I ask this because earlier I loaded the 1.50 and you updated twice today (Thank you for the hard work) and there was apparently an update at version 1.51 that could effect me so I wanted to be sure I had the latest updates.

The Device does say which flash was recently flashed but not the version of the flash. It also showed an asterisk next to the E85 UEL as thats what I was using. I went ahead and flashed it again just to be sure since I deleted and then loaded the 1.52 Beta Dev.

I wasn't sure if I just overlooked it or if this was something we could have in the future to help avoid confusion for those using this new format of .Dev Beta releases.

Also I will keep testing it but to me it did feel even smoother down low but it seems to have lost some up top... I will be doing some logging over this week to see the differences between the 1.5x and 1.42 I was running before it with my Cranking tables.
My cold start issues are back obviously since I cannot make the changes I did before with the help of others here on the boards.

[Malt]

Originally Posted by Cross

Hey Shiv I have a question and possible suggestion.

Where can we check which dev version our OFT has from the OFT itself?

I ask this because earlier I loaded the 1.50 and you updated twice today (Thank you for the hard work) and there was apparently an update at version 1.51 that could effect me so I wanted to be sure I had the latest updates.

The Device does say which flash was recently flashed but not the version of the flash. It also showed an asterisk next to the E85 UEL as thats what I was using. I went ahead and flashed it again just to be sure since I deleted and then loaded the 1.52 Beta Dev.

I wasn't sure if I just overlooked it or if this was something we could have in the future to help avoid confusion for those using this new format of .Dev Beta releases.

Also I will keep testing it but to me it did feel even smoother down low but it seems to have lost some up top... I will be doing some logging over this week to see the differences between the 1.5x and 1.42 I was running before it with my Cranking tables.
My cold start issues are back obviously since I cannot make the changes I did before with the help of others here on the boards.

Just to avoid any confusion, I've noticed that OFT just remembers what slot you flashed, not which map. If you flash slot 5 and then delete the maps on the OFT and put then in a different order it might confuse you as to which map you currently have on your ecu.

I found this out after I swapped back to a gas map but moved the e85 map I was using to a different slot.

[Shiv@Openflash]

Originally Posted by Apoc

@shiv My CAL ID shows as ZA1JA01C but isn't letting me use the dev tunes. I think my original rom is just a ecutek stock rom.

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