Disable high Rev cold start

[cruizin01]

@troek helped me with updated definitions which worked perfect.

Ill be switching back to 1x definitions since i just picked up a vortech and will be using oft300 map.

Sent from HTC M8 while in burnout mode

[Foobar]

Originally Posted by acj47

According to this thread, I should have the tables "MAF Correction After Start (In Gear)" and "MAF Correction After Start (Neutral)" in the "Mass Airflow / Engine Load" folder of the .bin file.

I am using OFT v2.06 A01C bin file (Stg 2 E85) and these tables are not present. There's a lot of talk about what to do/not to do to add these using definition files from romraider, github, etc...

Can Shiv or someone else confirm what is needed to get these two tables in the v2.06 A01C bin file? Thanks!

The 2.x files are based on the B01 definition, I believe. So you're going to need to grab the appropriate XML blocks for MAF After Start (In Gear) as well as the (Neutral) one, paste them into your definition file, then apply the definition and reopen the ROM in RomRaider. Should show up then.

[acj47]

Originally Posted by Foobar

The 2.x files are based on the B01 definition, I believe. So you're going to need to grab the appropriate XML blocks for MAF After Start (In Gear) as well as the (Neutral) one, paste them into your definition file, then apply the definition and reopen the ROM in RomRaider. Should show up then.

I just checked, and it appears the B01 does not have the (Neutral) or (In Gear) information either.

[Foobar]

Originally Posted by acj47

I just checked, and it appears the B01 does not have the (Neutral) or (In Gear) information either.

Grab the definitions from TD-D's github and paste the relevant blocks into the OFT 2.x ones.

[acj47]

Originally Posted by steve99

Oft guys just be carefull using defs off github as the oft roms can have the calid changed and hence need thecmatching defs from the openflash site. eg an oft 700C rom is exactly the same cas a 900C or an A01C just with calid changed. the oft guys alter the defs to match if you get github defs and your oft rom has been calid changed its not going to work and the tables will be all screwed up.

it will work if the rom yo have is the native rom the series was created wiith ie the latest rom in series

So if I am using OFT v2.06 map and my calid is A01C, which file do I need to reference?

Thank you.

[Foobar]

Originally Posted by acj47

So if I am using OFT v2.06 map and my calid is A01C, which file do I need to reference?

Thank you.

The B01C definition should have the appropriate mappings.

Specifically, you'll need

		<table name="MAF Correction After Start (Neutral)" storageaddress="11C868">
		  <table type="X Axis" storageaddress="11C81C" />
		  <table type="Y Axis" storageaddress="11C848" />
		</table>
		<table name="MAF Correction After Start (In Gear)" storageaddress="11C964">
			<table type="X Axis" storageaddress="11C918" />
			<table type="Y Axis" storageaddress="11C944" />
		</table>

and

    <table type="3D" name="MAF Correction After Start (In Gear)" category="Mass Airflow / Engine Load" storagetype="uint16" endian="big" sizex="11" sizey="8" userlevel="4">
      <scaling units="g/s" expression="x*0.004577637" to_byte="x/0.004577637" format="0.0" fineincrement="0.1" coarseincrement="1" />
      <table type="X Axis" name="Coolant Temperature" storagetype="float" >
        <scaling units="DegreesF" expression="(x*1.8)+32" to_byte="(x-32)/1.8" format="0.0" fineincrement="1" coarseincrement="10" />      
        </table>
      <table type="Y Axis" name="Idle Mode" storagetype="float" >
        <scaling units="Mode Counter" expression="x" to_byte="x" format="0" fineincrement="1" coarseincrement="5" />
      </table>
    </table>
    <table type="3D" name="MAF Correction After Start (Neutral)" category="Mass Airflow / Engine Load" storagetype="uint16" endian="big" sizex="11" sizey="8" userlevel="4">
      <scaling units="g/s" expression="x*0.004577637" to_byte="x/0.004577637" format="0.0" fineincrement="0.1" coarseincrement="1" />
      <table type="X Axis" name="Coolant Temperature" storagetype="float" >
        <scaling units="DegreesF" expression="(x*1.8)+32" to_byte="(x-32)/1.8" format="0.0" fineincrement="1" coarseincrement="10" />      
        </table>
      <table type="Y Axis" name="Idle Mode" storagetype="float" >
        <scaling units="Mode Counter" expression="x" to_byte="x" format="0" fineincrement="1" coarseincrement="5" />
      </table>
    </table>

I think that's all you're missing.

[acj47]

Originally Posted by Foobar

The B01C definition should have the appropriate mappings.

Specifically, you'll need

		<table name="MAF Correction After Start (Neutral)" storageaddress="11C868">
		  <table type="X Axis" storageaddress="11C81C" />
		  <table type="Y Axis" storageaddress="11C848" />
		</table>
		<table name="MAF Correction After Start (In Gear)" storageaddress="11C964">
			<table type="X Axis" storageaddress="11C918" />
			<table type="Y Axis" storageaddress="11C944" />
		</table>

and

    <table type="3D" name="MAF Correction After Start (In Gear)" category="Mass Airflow / Engine Load" storagetype="uint16" endian="big" sizex="11" sizey="8" userlevel="4">
      <scaling units="g/s" expression="x*0.004577637" to_byte="x/0.004577637" format="0.0" fineincrement="0.1" coarseincrement="1" />
      <table type="X Axis" name="Coolant Temperature" storagetype="float" >
        <scaling units="DegreesF" expression="(x*1.8)+32" to_byte="(x-32)/1.8" format="0.0" fineincrement="1" coarseincrement="10" />      
        </table>
      <table type="Y Axis" name="Idle Mode" storagetype="float" >
        <scaling units="Mode Counter" expression="x" to_byte="x" format="0" fineincrement="1" coarseincrement="5" />
      </table>
    </table>
    <table type="3D" name="MAF Correction After Start (Neutral)" category="Mass Airflow / Engine Load" storagetype="uint16" endian="big" sizex="11" sizey="8" userlevel="4">
      <scaling units="g/s" expression="x*0.004577637" to_byte="x/0.004577637" format="0.0" fineincrement="0.1" coarseincrement="1" />
      <table type="X Axis" name="Coolant Temperature" storagetype="float" >
        <scaling units="DegreesF" expression="(x*1.8)+32" to_byte="(x-32)/1.8" format="0.0" fineincrement="1" coarseincrement="10" />      
        </table>
      <table type="Y Axis" name="Idle Mode" storagetype="float" >
        <scaling units="Mode Counter" expression="x" to_byte="x" format="0" fineincrement="1" coarseincrement="5" />
      </table>
    </table>

I think that's all you're missing.

Thanks - just figured that out. My problem was this tidbit of information: Why is my Tune Calibration ID different from my stock ROM or in OFT/OFM...OFT tunes are generally based on the latest ROM revision for your ROM type...For USA/Canada type = C eg ZA1JB01C...2.0X tunes based on B01 revision

So once I added the two parts of code from the B01 file https://raw.githubusercontent.com/TD...R_ZA1JB01C.xml I then opened up in RomRaider and: success!

Thanks to all who helped!

[Foobar]

Originally Posted by acj47

success!

Right on! I've been using the quiet cold start through cold weather (right at freezing) and haven't had any issues. I know the primary purpose of the original start parameters are to make the cats more efficient, so I'm feeling a bit guilty about that, but then again, I've already eliminated one of the cats, so I'm already in the hole I guess.

[acj47]

Originally Posted by Foobar

Right on! I've been using the quiet cold start through cold weather (right at freezing) and haven't had any issues. I know the primary purpose of the original start parameters are to make the cats more efficient, so I'm feeling a bit guilty about that, but then again, I've already eliminated one of the cats, so I'm already in the hole I guess.

Exactly - I don't want to be the pesky neighbor with the loud exhaust, especially early in the morning. I changed the Ignition Timing Post Start values to 0 (0.04) yesterday, but the car still started up at ~2100 RPM and threw the CEL P050B (Cold Start Ignition Timing Performance). I'm hopeful that editing the MAF Correction AFter Start (In Gear) & (Neutral) tables will eliminate throwing the CEL and bring down the idle RPM to my Idle Speed Target values.

This forum rocks

[Foobar]

Originally Posted by acj47

Exactly - I don't want to be the pesky neighbor with the loud exhaust, especially early in the morning. I changed the Ignition Timing Post Start values to 0 (0.04) yesterday, but the car still started up at ~2100 RPM and threw the CEL P050B (Cold Start Ignition Timing Performance). I'm hopeful that editing the MAF Correction AFter Start (In Gear) & (Neutral) tables will eliminate throwing the CEL and bring down the idle RPM to my Idle Speed Target values.

This forum rocks

My ignition timing post start is set to -8.05 through the entire row, MAF Correction After Start is set to 8, 7, 5, 5, 5, 4, 4, 4, 4 on all rows for both in gear and neutral, and for good measure, I disabled the DTC for P050B - not sure if I needed to do that one.

[AdrianG]

Last weekend I started my car in -15C a couple times, zero issues.

- AdrianG

[acj47]

Originally Posted by Foobar

I disabled the DTC for P050B - not sure if I needed to do that one.

I left it enabled to see if it pops up again. I'll let you know what I find out.

[steve99]

Originally Posted by acj47

I left it enabled to see if it pops up again. I'll let you know what I find out.

I modded a tune or a guy in usa and he threw up same cel P050B , its definitly due to change to ingintion timing post start was using -4 instead of -15.

just disable the code.

we never throw that code on G roms, must be something dierent in usa roms.

you need to alter the maf correction at statup or the car will still idle high and not follow the idle maping settings at startup

[phrosty]

I've been using a cold start tune for a while and haven't had any codes, but I modified mine to be slightly less aggressive down low since I live in a place with freezing temps.