OpenFlash Tablet: OTS v2.0 Beta (132 new maps, 12 new XMLs) Available for Download

[troek]

so far other than the 44 tables my rom dosnt have that that the state side one has, these are the tables that are changed between 1.5x stage 2 and 2.0 stage 2 uel 93 octane:
knock correction advnace max a
overrun fueling cut counter rpm threshold
misfire count map threshold a
misfire count map threshold b
various input rising load activation ECT Load tables
are any of these performance orientated?

[steve99]

Originally Posted by troek

so far other than the 44 tables my rom dosnt have that that the state side one has, these are the tables that are changed between 1.5x stage 2 and 2.0 stage 2 uel 93 octane:
knock correction advnace max a
overrun fueling cut counter rpm threshold
misfire count map threshold a
misfire count map threshold b
various input rising load activation ECT Load tables
are any of these performance orientated?

something weird going on there mate.

The 1.5 to 2 tune have big changes to MAF scaling and OL Fuel tables.
for sure.

[solidONE]

Originally Posted by JB86'd

Stock intake, unmodified, AFE dryflow filter. You on the 2.0 maps?

I'm using an afe r5 oiled filter element (supposed to flow more cfm than the dry one). maybe its time for me to wash and reoil it. You'r logs were reading up to 4.03v, mine on stg 1 v 2.0 tune is topping out at 4.01v.

[steve99]

Originally Posted by clintavo

Has anyone else noticed hesitation/ bogging at 1500 rpm when floored?

I realize this is a somewhat rare scenario, but I have run into it twice:
Loafing around a parking lot in 2nd gear, suddenly to get out of someone's way.
Starting from a stop uphill.

It is repeatable; floor it at 1500 rpm and it completely bogs. It never happened with 1.3 or 1.6

BTW the throttle calibration seems much smoother in this tune : )

Thanks Shiv!

Stock intake ??

also log whats going on include long Term fuel trims LTFT see if its are way off like over 10%

[troek]

Originally Posted by steve99

something weird going on there mate.

The 1.5 to 2 tune have big changes to MAF scaling and OL Fuel tables.
for sure.

Yeah thats what i was thinking as well. Might have to just wait till shiv gets around to the japanese rom, im at the bottom of the list being the only one over here lol

[steve99]

Originally Posted by troek

Yeah thats what i was thinking as well. Might have to just wait till shiv gets around to the japanese rom, im at the bottom of the list being the only one over here lol

Just compared a stock D00G to OFT modded D00C and their is a couple of weird tables and values that look a bit suspect in the DOOC rom actually, it late though and maybe my brain fading. Think I;m going to be lazy and let shiv do it.

[Td-d]

Originally Posted by troek

Yeah thats what i was thinking as well. Might have to just wait till shiv gets around to the japanese rom, im at the bottom of the list being the only one over here lol

Japanese rom is done, I've posted it already - I'm guessing Shiv just has to transfer the maps.

[troek]

Originally Posted by Td-d

Japanese rom is done, I've posted it already - I'm guessing Shiv just has to transfer the maps.

[Juanito08]

I keep getting a "post catalyst fuel trim too lean (bank 1) " code from this beta maps. And on top of that someone times when I crank the car to turn on it doesn't. The bash lights up but the car doesn't turn on like if the battery wasn't charged. Takes it like 2- tries to turn it on

[clintavo]

Originally Posted by steve99

Stock intake ??

also log whats going on include long Term fuel trims LTFT see if its are way off like over 10%

Modified stock snorkel. I'll post a log. Thanks

[JB86'd]

@steve99 @Shiv@Openflash

just took a new datalog and got the IAM to drop from 1. Seems that partial throttle mid-rpm fine knocking is what's bringing my IAM down mostly. There are quite a few FLKC events under 1.0..no actual Knock Correction, and LTFT does not go above or below +4 and -4.

Are those FLKC events something I should make an effort to edit out in the map or get a custom e-tune, or are they not a problem?

http://datazap.me/u/joshbustos86/frs...1-2-9-10-11-12

keep in mind I'm on CA 91 oct and it's about 80* F out.

[Kodename47]

Originally Posted by JB86'd

@steve99 @Shiv@Openflash

just took a new datalog and got the IAM to drop from 1. Seems that partial throttle mid-rpm fine knocking is what's bringing my IAM down mostly. There are quite a few FLKC events under 1.0..no actual Knock Correction, and LTFT does not go above or below +4 and -4.

Are those FLKC events something I should make an effort to edit out in the map or get a custom e-tune, or are they not a problem?

http://datazap.me/u/joshbustos86/frs...1-2-9-10-11-12

keep in mind I'm on CA 91 oct and it's about 80* F out.

FLKC is when loads are more stable and are easily tuned out. I would just make sure they are consistent. I've said multiple times to use VGI's utility to log these events to see how to adjust the map.

[steve99]

Originally Posted by JB86'd

@steve99 @Shiv@Openflash

just took a new datalog and got the IAM to drop from 1. Seems that partial throttle mid-rpm fine knocking is what's bringing my IAM down mostly. There are quite a few FLKC events under 1.0..no actual Knock Correction, and LTFT does not go above or below +4 and -4.

Are those FLKC events something I should make an effort to edit out in the map or get a custom e-tune, or are they not a problem?

http://datazap.me/u/joshbustos86/frs...1-2-9-10-11-12

keep in mind I'm on CA 91 oct and it's about 80* F out.

+1 on @Kodename47 comments.

log it a couple of times note the RPM and Engine Load where knock occurs consistently and the amount of negative correction of FLKC or Knock correction FBKC. (Don't worry about the positive FLKC as that is the ECU putting back timing it took away.)

have a read here

http://www.ft86club.com/forums/showthread.php?t=61820

pull timing from the appropriate cells in BASE_TIMING_B reflash = happy.
looks like about 0.7 or so needs to be pulled from 3000-3600 loads 0.6 to 1 but do a couple more logs.

Once you IAM get back to 1 you might need to pull a bit of timing at the upper RPM range as well.

[Kodename47]

Ignition timing adjustments can be done as below:

Originally Posted by Kodename47

The way I have used to easily see what's happening is as below, using VGI's Tool.
- Go to Log Stats screen
- Import Log
- On the set axis button, copy in your base timing table and verify (save for future if you want)
- Set X axis as engine load
- Set Y axis as RPM
- Set Data as FLKC
- Set a filter as FLKC < 0

I would then check the mode value and the count. You can repeat for FBKC too. Obviously if you log pull by pull then you won't need to do that, but if you're logging more than that, it can be useful to see other problem areas.