OpenFlash Tablet v1.55b: BIN files added!

[1Cor10:23]

Hey @shiv@vishnu I know the new OFT tunes include the DI seal TSB fix that came with A01C, wondering if the additional factory changes in B01C (idle drop) is also being added to the OTS maps.

Thanks!

[akyp]

Did a longer log tonight: http://www.datazap.me/u/akyp/20140313?log=0&data=1-10

IAM dropped to 0.98 in the middle. Does it suggest a bit of knock? Too bad I neglected to turn on KC channel (which should be a default, really).

Stage 1 v1.55b with 98 RON fuel.

[steve99]

Originally Posted by akyp

Did a longer log tonight: http://www.datazap.me/u/akyp/20140313?log=0&data=1-10

IAM dropped to 0.98 in the middle. Does it suggest a bit of knock? Too bad I neglected to turn on KC channel (which should be a default, really).

Stage 1 v1.55b with 98 RON fuel.

Yes the IAM dropping indicates knock, but IAM only dropping to 0.97 indicates it was not to bad.

Their is generally a delay between when the knock occurs and when the IAM drops.

If you log "Knock Correction" then you will be able to see where the knock is occurring.

[Shiv@Openflash]

Originally Posted by akyp

Did a longer log tonight: http://www.datazap.me/u/akyp/20140313?log=0&data=1-10

IAM dropped to 0.98 in the middle. Does it suggest a bit of knock? Too bad I neglected to turn on KC channel (which should be a default, really).

Stage 1 v1.55b with 98 RON fuel.

Totally fine. It's totally normal to see IAM move slightly during a 28min log. The fact that it only dropped to .98 and went back to 1.0 is great.

Shiv

[Shiv@Openflash]

Originally Posted by 1Cor10:23

Hey @shiv@vishnu I know the new OFT tunes include the DI seal TSB fix that came with A01C, wondering if the additional factory changes in B01C (idle drop) is also being added to the OTS maps.

Thanks!

Hi,
Haven't gotten around to basing all OTS maps on the B01C rom. Simply because we incorporate an idle drop fix of our own in our A01C based OTS maps. It's something we will do in time though. But I'd like to enable LC and FFS before we make that change so customers aren't sacrificing functionality.

[Shiv@Openflash]

Originally Posted by Yobiwan

JDL UEL header
Perrin resonated CBE
KN filter

+ OFT OTS 1.55b stage 2 + 98RON pump gas

I did dyno after flashing. so it's not post learned

1. all stock vs
[IMG]
Flickr에서 Yobi-Wan님의 사진 2014. 3. 11. 오후 3 27 44[/IMG]


2. stage 1 ( without JDL UEL header, and It's post learned ) vs

there was FLKC at 7300 RPM . I think that cause torque depression at 7300rpm

http://www.datazap.me/u/yobiwan/oft-...-19&zoom=0-314

[IMG]
Flickr에서 Yobi-Wan님의 사진 2014. 3. 11. 오후 3 27 31[/IMG]


3. and I ordered OFT . I received tracking no. but not shipped yet.

Thank you!
OFTs are getting prepped for shipping as I type. Busy day....

[maxjedi]

Originally Posted by shiv@vishnu

Yes, but I wouldn't bother using Tuner Pro at this point. Rom Raider is more defined and supports more ROM types.

Can you make a mini guide on using romraider ? I have version 0.5.7 RC2 with RR_ZA1J700G.xml downloaded from your website and installed in romraider's definition manager. When I try to open "Stg1 700G.bin" it says "Checksum No.1 invalid" and then "ERROR - Data Mismatch, Table: Checksum Fix 2, Table editing has been disabled, Definition file or ROM image may be corrupt". I press OK, it shows the tables in read only mode. Saving the ROM with a different name and opening it again fixes "Checksum No.1" but not "Data Mismatch", still can't edit anything.

[Shiv@Openflash]

Originally Posted by maxjedi

Can you make a mini guide on using romraider ? I have version 0.5.7 RC2 with RR_ZA1J700G.xml downloaded from your website and installed in romraider's definition manager. When I try to open "Stg1 700G.bin" it says "Checksum No.1 invalid" and then "ERROR - Data Mismatch, Table: Checksum Fix 2, Table editing has been disabled, Definition file or ROM image may be corrupt". I press OK, it shows the tables in read only mode. Saving the ROM with a different name and opening it again fixes "Checksum No.1" but not "Data Mismatch", still can't edit anything.

You can ignore the checksum errors. The files aren't corrected for checksum since that is done by OpenFlash Manager when they are loaded into the OFT. After you make any desired changes, just save as a different name (as you should anyway). And you will be good to go.

[maxjedi]

Perhaps my english isn't good enough. The problem is I cannot make any changes (because "Table editing has been disabled"), and saving with different filename doesnt fix that.

[Shiv@Openflash]

Originally Posted by maxjedi

Perhaps my english isn't good enough. The problem is I cannot make any changes (because "Table editing has been disabled"), and saving with different filename doesnt fix that.

Oh.. just go to View menu and change User Level to 4 or greater. You will be able to edit and save the file.

[maxjedi]

Thanks, now it works. But why does it still show an error after saving ? I tried 700C and it opens without errors. Is it possible that something is wrong with G roms definitions ?

[Shiv@Openflash]

Originally Posted by maxjedi

Thanks, now it works. But why does it still show an error after saving ? I tried 700C and it opens without errors. Is it possible that something is wrong with G roms definitions ?

We didn't develop the Rom Raider application so I can't answer that. All I can say is ignore any and all checksum error messages since checksum correction is handled by OF Manager. Some files in your OTS map folder may already be corrected for checksum just by chance. So don't be surprised if some files give you the error while others don't. Nothing is wrong with G series ROMs (or any other ROMs AFAIK). Plenty of people using them

[troek]

Originally Posted by maxjedi

Thanks, now it works. But why does it still show an error after saving ? I tried 700C and it opens without errors. Is it possible that something is wrong with G roms definitions ?

make sure your using the correct ecu definition files.

[Captain Insano]

Just ran a log today on 1.55b stg1 with 93 octane fuel.
http://www.datazap.me/u/captain-insa...=0&data=1-8-12


How's it look? I did notice at one point IAM went down to .88, but then the rest of the time I logged it was back at 1 and later I watched the data viewer real time and it stayed at 1 anytime I was watching.