Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB - Tactrix EcuFlash Info for BRZ 86 FRS Rom flash update and logging

- Software Tuning (https://www.ft86club.com/forums/forumdisplay.php?f=88)

- - Tactrix EcuFlash Info for BRZ 86 FRS Rom flash update and logging (https://www.ft86club.com/forums/showthread.php?t=62332)

@Td-d, what's changes have you made? Also Can you check on idle stability ? Do you already have the x and y for logging?

Sent from my iPad using Tapatalk

Here's the link to notepad plus http://notepad-plus-plus.org/download/v6.6.9.html
My versions gonna get updated today, seem mine's quite outdated now at 6.1.3, May 28 2012 build LOL

Do we have logging addresses for B01D? I've acquired an OP2 and would love to use it for logging :)

Back on 98 as E85 locations were getting too hard and the economy wasn't great.

First 2 logs:
http://www.datazap.me/u/tech86/98-stage-1

3rd log split in 2 for size limit.
http://www.datazap.me/u/tech86/98-stage-1-0

Any comments?

Quote:

Originally Posted by tech86 (Post 1973128)

IAM dropped to O.9 , most likely due the -1 or greater knock events shown in the other logs around 2700 and 3000 rpm probably worth pulling 0.5 out of the advance map at those rpm/load points where your corrections is over 1 degree.

which 98 are you using BP seems worse than shell for knock on these cars.

fuel trims afr look ok.

Quote:

Originally Posted by steve99 (Post 1973475)

I do see a couple of those events but didn't think they were overly concerning. Are you talking about 0.5 from knock correction advance A? Not better to drop base timing B a bit?

LOL BP stands out that much ;) but yeah, was the closest servo at the time.

Yeah happy with the trims, still using stock A01G MAF scale so not sure I need to touch them just yet.

Quote:

Originally Posted by phrosty (Post 1972933)

Do we have logging addresses for B01D? I've acquired an OP2 and would love to use it for logging :)

If I haven't posted yet, I'll put them up for you shortly phrosty, no problem.

Quote:

Originally Posted by tech86 (Post 1974293)

I prefer to pull timing from Base_TIMING_B rarther than Knock Correction Max A as it does not effect what hapens when IAM drops.

However if you try Caltex or Shell fuel you probably wont need to remove that timing.

Good point. Still got a near full tank so I'll back it off for now and reload the current map with different fuel. P100 would sort it out no doubt, but I heard they were discontinuing it?

Quote:

Originally Posted by tech86 (Post 1974465)

Good point. Still got a near full tank so I'll back it off for now and reload the current map with different fuel. P100 would sort it out no doubt, but I heard they were discontinuing it?

The facebook guys @Wayno ect said they saw something of facebook about it , but nothing on their website www.unitedpetroleum.com.au, they seem to be still expanding E85 as well hopefully P100 and E85 will stay who knows ?

Quote:

Originally Posted by Td-d (Post 1974296)

If I haven't posted yet, I'll put them up for you shortly phrosty, no problem.

Where do they get posted to? I can't find them in github.

Normally in Steve's main Tactrix thread - I haven't set up a Github directory for it yet. Probably should.

Quote:

Originally Posted by Td-d (Post 1979045)

Normally in Steve's main Tactrix thread - I haven't set up a Github directory for it yet. Probably should.

Alright, I'll keep looking :)

I've tried to run the logcfg.exe for myself and it appears to be written for a very specific RomRaider configuration that I don't have. Otherwise I'd just create it myself. Going to have a look at the .xml files and see if I can just rewrite the program quickly.

I'll get to it this weekend Phrosty - I looked, hadn't posted up yet.

Logcfg won't work because it relies on the master logger.xml that RR logger uses, with its standard notation for the parameters (E_XXX - e.g. E_AF_Correction_1_4byteExt_E81). We need to generate a whole new set of parameters in this syntax to work for Romraider - I just haven't had the time...

Here the addresses dump for B01D:

Code:

RaM_Fuel_Type                                   FFF8DC2A 

RaM_LTFT                                        FFF8DB90 

Ram_AFR_Sensor_Heating_Limit_Result             FFF88478 

Ram_AF_Correction_3_32bit_ECU                   FFF8A900 

Ram_AF_Learning3_Percentage                     FFF8DC10 

Ram_AF_Learning_3                               FFF81640 

Ram_AF_Sensor_1_Current                         FFF8932C 

Ram_AF_Sensor_1_Resistance                      FFF89344 

Ram_Accelerator_Angle?                          FFF8B5B8 

Ram_Accelerator_Pedal_Angle                     FFF89230 

Ram_Accelerator_Pedal_Angle_0                   FFF8DC14 

Ram_Accelerator_Pedal_D                         FFF8DC00 

Ram_Accelerator_Pedal_E                         FFF8DC04 

Ram_Alternator_Duty                             FFF884A4 

Ram_Ambient_Air_Temperature                     FFF8DBF8 

Ram_Atmospheric_Pressure                        FFF8DBCC 

Ram_Atmospheric_Pressure_1                      FFF89B94 

Ram_Auxiliary_input_output_supported            FFF8DC2B 

Ram_Base_Pulse_Width                            FFF89744 

Ram_Base_Pulse_Width_times_100_0.84             FFF89CC0 

Ram_Battery_Voltage                             FFF87C6C 

Ram_Battery_Voltage_0                           FFF8DBD8 

Ram_Brake_Switch                                FFF89393 

Ram_CPC_Valve_Duty_Ratio                        FFF89CD0 

Ram_CPC_Valve_Duty_Ratio_0                      FFF8BD28 

Ram_Calculated_Base_Pulse_Width_                FFF8A058 

Ram_Catalyst_Temperature_Bank_1_Sensor_1        FFF8DBD4 

Ram_Clutch_Switch                               FFF893A7 

Ram_Commanded_Secondary_Air_Status              FFF8DC29 

Ram_CoolantTemperature                          FFF890A4 

Ram_Coolant_Temperature???                      FFF87C74 

Ram_Defogger_Switch                             FFF8939F 

Ram_Distance_Traveled_since_DTCs_cleared        FFF81CBA 

Ram_Distance_Traveled_with_MIL_On               FFF81CB8 

Ram_EVAP_Commanded_Purge                        FFF8DBC4 

Ram_EVAP_System_Vapor_Pressure_Absolute         FFF8DC0C 

Ram_Engine_Load_Absolute                        FFF8DBDC 

Ram_Engine_Load_Calculated                      FFF8DB84 

Ram_Engine_Oil_Temperature                      FFF8DC20 

Ram_Engine_Speed                                FFF89570 

Ram_Exhaust_VVT_Retard_Angle_Left_              FFF8C148 

Ram_Exhaust_VVT_Retard_Angle_Right_             FFF8C144 

Ram_Fuel_Air_Commanded                          FFF8DBE8 

Ram_Fuel_Injector_1_Pulse_Width                 FFF887D8 

Ram_Fuel_Injector_1_Pulse_Width_4byteExt_E60??? FFF887F0 

Ram_Fuel_Injector_2_Pulse_Width                 FFF887DC 

Ram_Fuel_Injector_Pulse_Width?                  FFF88810 

Ram_Fuel_Pressure_MPa                           FFF89378 

Ram_Fuel_Pump_Duty                              FFF8B1B4 

Ram_Fuel_Rail_Pressure_direct_inject            FFF8DBB8 

Ram_GDI_Flow_Rate                               FFF88844 

Ram_Gear                                        FFF895E5 

Ram_High_Low_Load_0_L_1_H                       FFF8A0F8 

Ram_Idle_Switch                                 FFF8B5C6 

Ram_Ignition_Total_Timing                       FFF8AE0C 

Ram_Intake_Air_Temperature                      FFF8DBA4 

Ram_Intake_Air_Temperature_0                    FFF87C64 

Ram_Intake_OCV_Current_Left                     FFF891B8 

Ram_Intake_OCV_Current_Right                    FFF891AC 

Ram_Intake_OCV_Duty_Left                        FFF8C20C 

Ram_Intake_OCV_Duty_Right                       FFF8C218 

Ram_Intake_Temp                                 FFF890B8 

Ram_Intake_VVT_Advance_Angle_Left               FFF8C100 

Ram_Intake_VVT_Advance_Angle_Right_             FFF8C0FC 

Ram_Map                                         FFF8DB94 

Ram_Map_Delta?                                  FFF8A234 

Ram_Mass_Airflow                                FFF89118 

Ram_Mass_Airflow_0                              FFF8DBA8 

Ram_Number_of_warm_ups_since_DTCs_cleared       FFF826CE 

Ram_O2_currrent                                 FFF8DBD0 

Ram_O2_volt                                     FFF8DBC0 

Ram_Per_Injector_Pulse_Width_Compensation_A     FFF8AB44 

Ram_Per_Injector_Pulse_Width_Compensation_B     FFF8AB4C 

Ram_Per_Injector_Pulse_Width_Compensation_C     FFF8AB54 

Ram_Per_Injector_Pulse_Width_Compensation_D     FFF8AB5C 

Ram_Per_Injector_Pulse_Width_Compensation_E     FFF8AB64 

Ram_Per_Injector_Pulse_Width_Compensation_F     FFF8AB6C 

Ram_Per_Injector_Pulse_Width_Compensation_G     FFF8AB74 

Ram_Per_Injector_Pulse_Width_Compensation_H     FFF8AB7C 

Ram_Rear_O2_Sensor                              FFF8DBB0 

Ram_Roughness_Monitor_Cylinder_1                FFF8CEDD 

Ram_Roughness_Monitor_Cylinder_2                FFF8CEDE 

Ram_Roughness_Monitor_Cylinder_3                FFF8CEDF 

Ram_Roughness_Monitor_Cylinder_4                FFF8CEE0 

Ram_Run_Time_Since_Engine_Start                 FFF84DB4 

Ram_SI_Drive_Mode_I3_S1_SSharp2_                FFF88999 

Ram_STFT                                        FFF8DB8C 

Ram_Throttle_Opening_Angle                      FFF8DBAC 

Ram_Throttle_Opening_Commanded                  FFF8DC08 

Ram_Throttle_Position_relative                  FFF8DBF0 

Ram_Time_Run_since_DTCs_Cleared                 FFF81CBE 

Ram_Time_Run_with_MIL_On                        FFF81CBC 

Ram_Timing_Advance                              FFF8DBA0 

Ram_Transient_Threshold_Testunk                 FFF89240 

Ram_Vehicle_Speed                               FFF8DB9C 

Ram_Vehicle_Speed_0                             FFF893D0 

Ram_coolant_temp                                FFF8DB88 

Ram_fuel_level                                  FFF8DBC8 

Ram_lambda                                      FFF8DBBC 

E_AF_Correction_1_4byteExt_E81                      FFF8A5EC 

E_AF_Learning_1_4byteExt_E48                        FFF8A774 

E_AF_Sensor_1_4byteExt_E91                          FFF89330 

E_CLOL_FuelingExt_E33                               FFF8DC26 

E_Closed_Loop_Fueling_Target_4byteExt_E121          FFF8A6D0 

E_Engine_Load_4ByteExt_E32                          FFF8914C 

E_Engine_Speed_Delta_E157                           FFF89408 

E_Feedback_Knock_Correction_4byteExt_E39            FFF8B0C4 

E_Final_Fueling_Base_4byteExt_E123                  FFF8A01C 

E_Fine_Learning_Knock_Correction_4byteExt_E41_      FFF8B160 

E_Fuel_Injector_1_Latency_4byteExt_E50              FFF8A05C 

E_Fuel_Injector_1_Pulse_Width_4byteExt_E60          FFF887C8 

E_IAM_4byteExt_E31                                  FFF816F0 

E_Idle_Speed_Map_SelectionExt_E49                   FFF8B748 

E_Ignition_Base_TimingExt_E53                       FFF8AE88 

E_Knock_Correction_Advance_4byteExt_E43             FFF8B0C0 

E_Knock_Correction_Advance_IAM_onlyExt_E40          FFF8B134 

E_Knock_Correction_Advance_Max_PrimaryExt_E118      FFF8B12C 

E_Manifold_Relative_Pressure_4byteExt_E113          FFF88F78 

E_Manifold_Relative_Sea_Level_Pressure_4byteExt_E52 FFF88F74 

E_Primary_Open_Loop_Map_Enrichment_4byteExt_E84     FFF8A988 

E_Requested_TorqueExt_E56                           FFF8B4A4 

E_Target_Throttle_Plate_PositionExt_E57             FFF8B58C 

E_Throttle_Plate_Opening_Angle_4byteExt_E38         FFF89030 

E_Tipin_ThrottleExt_E54                             FFF89038

Quote:

Originally Posted by Td-d (Post 1980246)

Here the addresses dump for B01D:

Right on :D

What data are you generating these from? I can infer some of the info from what others have posted, but is there a document that shows the data types and units of measure of each address?

Quote:

Originally Posted by phrosty (Post 1980929)

have a look at some of the logcfg.txt files and substitute in the ram addresses from your rom the scaling datatype should be same its generally just the ram address that changes. the names of ram address location may not be eaxactly the same sometimes it a bit of trial and error

unfortunatly no doco, if you find some post it up :D

Quote:

Originally Posted by phrosty (Post 1980929)

That's why we need to get these into standard notation sooner rather than later - your best bet is the logger.xml file from the Romraider Logger, combined with a look through the other logcfg.txt files users have put out there.

I have version 1.59 OTS maps for OFT with the latest rom file listed as B01C. That means that all files are B01C calID? Also has anyone tried to log a ECUTEK tune with OP2?

Quote:

Originally Posted by Toyota John (Post 2008903)

I have version 1.59 OTS maps for OFT with the latest rom file listed as B01C. That means that all files are B01C calID? Also has anyone tried to log a ECUTEK tune with OP2?

I have version 1.59 OTS maps for OFT with the latest rom file listed as B01C. That means that all files are B01C calID?

NO !!! it does not you have to check with hex editor. or check table integrity. see first post.

Also has anyone tried to log a ECUTEK tune with OP2?

It should work if you match the RAM addresses with the tune calid, have not done it though. I believe they just change seed keys to prevent reading/writing of rom but RAM addresses for log parameters are likely the same.

I am getting close to figuring out logging with the tactrix OP2 but I keep getting a logcfg.out file and red with flashing green lights. Any ideas?

Ha I got it. It was the Triggers. I remove the defrost trigger and it work. Steve99 also said he had a problem with the defrost trigger. Any one else have a trigger that works well I could use.

I couldn't get any triggers to work so I just plug mine in when I want to log and pull it out when I'm done (lol). Much easier with an obd2 extension cable.

Quote:

Originally Posted by vgi (Post 2019276)

i'm using the defrost trigger occasionally, the down side - it shuts off in about 20mins.
it's also kinda hard to get it working. I thought that the cfg file must be in asc order (which is how my file is done, that is numeric asc order - not string asc order, based on hex memory address which is a number) but then someone said it didn't work for him (although i donno if he sorted by string or number).

Can you post the order you used to get the triggers to work. I am not sure i follow the numeric order.

Quote:

Originally Posted by Toyota John (Post 2019332)

Can you post the order you used to get the triggers to work. I am not sure i follow the numeric order.

Again, I'm not sure if this will work all the time, maybe it just happened to work for me.

so let's say you have:
----------------------
paramname = Manifold_Relative_Pressure
paramid = 0xFFF88F78
isfloat = 1

paramname = Direct_Ijector_PW
paramid = 0xFFF887E8
isfloat = 1

paramname = Direct_Injector_PW_Ram
paramid = 0xFFF887F0
isfloat = 1

The memory addresses above in bold are numbers, so sorted numerically in asc order would be:
-----------------------
paramname = Direct_Ijector_PW
paramid = 0xFFF887E8
isfloat = 1

paramname = Direct_Injector_PW_Ram
paramid = 0xFFF887F0
isfloat = 1

paramname = Manifold_Relative_Pressure
paramid = 0xFFF88F78
isfloat = 1

Did you mix the triggers in with the rest or leave them at the bottom?

Quote:

Originally Posted by Toyota John (Post 2019827)

Did you mix the triggers in with the rest or leave them at the bottom?

pmed

Is there a parameter for engine oil temp on the B01C? Thanks.

Quote:

Originally Posted by D-VO (Post 2022019)

Is there a parameter for engine oil temp on the B01C? Thanks.

@Td-d is your only hope

Quote:

Originally Posted by D-VO (Post 2022019)

Is there a parameter for engine oil temp on the B01C? Thanks.

Ram_Engine_Oil_Temperature FFF8DC20

It's a float, in degrees C.

FYI, B01C and B01D appear to have identical addresses.

B01C and B01D will have most addresses identical - but not all. Any table that is specific to AT or MT will be different (since the At tables are not defined for the MT roms and vice versa). And yes, that's the correct address.

@phrosty and @D-VO if you have some working logcfg.txt files on your roms could you post vthem up and i can add them to the first post so guys dont have to re invent the wheel

thanks

Quote:

Originally Posted by steve99 (Post 2042188)

@phrosty and @D-VO if you have some working logcfg.txt files on your roms could you post vthem up and i can add them to the first post so guys dont have to re invent the wheel

thanks

Sure thing, here you go for B01D. I believe this should work 100% for B01C as well.

After having a good look around the maps and definitions on the A01G ROM I discovered an update. The DI maximum definition is:

Code:

<table type="2D" name="Direct Injection Quantity Maximum" category="Alpha - BRZ" storagetype="float" endian="big" sizey="12" userlevel="4">

      <scaling units="ml" expression="x/100" to_byte="x*100" format="0.00" fineincrement=".01" coarseincrement=".1" />

      <table type="Y Axis" name="Engine Speed" storagetype="float" endian="big">

        <scaling units="RPM" expression="x" to_byte="x" format="#" fineincrement="10" coarseincrement="100" />

I have also managed to do a complete ECUtek conversion def for those like me who use ECUtek most of the time ;) This has pressure in Bar, temps in C and tables (or most that I've used) in ratios rather than -/+ decimals. This is NOT an OFT definition!

ZA1JA01G ECUtek Conversion Definition

More ZA1JA01G ROM definition updates.

Just so you're aware, I use Celcius for temperatures. To convert into Fahrenheit you need to change to expression to the below:

Code:

expression="(x*1.8)+32" to_byte="(x-32)/1.8"

Updated A/F Learning Ranges - There is Range E!

Code:

<table type="2D" name="A/F Learning #1 Airflow Ranges" category="Fueling - AF Correction / Learning" storagetype="float" endian="little" sizey="4" userlevel="4">

      <scaling units="Mass Airflow (g/s)" expression="x" to_byte="x" format="0.00" fineincrement=".1" coarseincrement="1" />

      <table type="Static Y Axis" name="A/F Learning Store/Apply Ranges" sizey="4">

        <data> Max Range A / Min Range B </data>

        <data> Max Range B / Min Range C </data>

        <data> Max Range C / Min Range D </data>

 <data> Max Range D / Min Range E </data>

      </table>

      <description>These are the airflow ranges in which the different long-term fuel trims are calculated in closed loop and applied to the same airflow ranges for both closed loop and open loop.</description>

    </table>

Engine Load Limiters

Code:

<table name="Engine Load Limiter A" storageaddress="1047CC">

 <table type="Y Axis" storageaddress="1047A8" />

     </table>

<table name="Engine Load Limiter B" storageaddress="104804">

 <table type="Y Axis" storageaddress="1047E0" />

     </table>





<table type="2D" name="Engine Load Limiter A" category="Test" storagetype="uint16" endian="big" sizey="9" userlevel="3">

      <scaling units="Engine Speed (RPM)" expression="x*0.0000610351563" to_byte="x/0.0000610351563" format="0.00" fineincrement="0.1" coarseincrement="1" />

      <table type="Y Axis" name="Engine Load" storagetype="float" endian="little" logparam="P2">

        <scaling units="" expression="x" to_byte="x" format="#" fineincrement="100" coarseincrement="500" />

      </table>

      <description>Engine load limit against RPM.</description>

    </table>

<table type="2D" name="Engine Load Limiter B" category="Test" storagetype="uint16" endian="big" sizey="9" userlevel="3">

      <scaling units="Engine Speed (RPM)" expression="x*0.0000610351563" to_byte="x/0.0000610351563" format="0.00" fineincrement="0.1" coarseincrement="1" />

      <table type="Y Axis" name="Engine Load" storagetype="float" endian="little" logparam="P2">

        <scaling units="" expression="x" to_byte="x" format="#" fineincrement="100" coarseincrement="500" />

      </table>

      <description>Engine load limit against RPM.</description>

    </table>

CPC Duty Multiplier

Code:

<table name="CPC Duty Multiplier" storageaddress="C64C" />



<table type="2D" name="CPC Duty Multiplier" category="Test" storagetype="float" endian="little" sizey="1" userlevel="4">

      

 <scaling units="Hz" expression="1/(x*0.4)" to_byte="1/(x*0.4)" format="#" fineincrement=".1" coarseincrement="1" />

      

 <table type="Static Y Axis" name="Custom" sizey="1">

        

 <data>Frequency</data>

        

 </table>

      

 <description>The operating frequency of the solenoid valve. On turbo conversions where the CPC valve is replaced with a fast switching wastegate duty solenoid valve this will vary depending on the type used.</description>

 </table>

AVCS Hysteresis

Code:

<table name="AVCS Base/Normal/Safe Hysteresis" storageaddress="120BE8" />



<table type="2D" name="AVCS Base/Normal/Safe Hysteresis" category="Variable Valve Timing (AVCS)" storagetype="float" endian="little" sizey="2" userlevel="4">

      

 <scaling units="IAM" expression="x" to_byte="x" format="0.00" fineincrement=".1" coarseincrement="1" />

      

 <table type="Static Y Axis" name="Map Transition" sizey="2">

        

 <data>Safe Above</data>

 

 <data>Normal Above</data>

        

 </table>

      

 <description>These values specify which of the base, normal or dafe maps will be used. </description>

    

       </table>

Closed Loop Delay Parameters

Code:

<table name="CL to OL Transition with Delay (Injector Load Threshold)" storageaddress="10F2A8">

 <table type="Y Axis" storageaddress="10F268" />

     </table>

<table name="CL Delay Period A" storageaddress="10C3E0" />

<table name="CL Delay Period B" storageaddress="10C3DE" />

<table name="CL Maximum Vehicle Speed" storageaddress="10CBF0" />

<table name="CL Delay Maximum (Engine Load)" storageaddress="10CC2C" />



<table type="2D" name="CL to OL Transition with Delay (Injector Load Threshold)" category="Fueling - CL/OL Transition" storagetype="uint16" endian="big" sizey="16" userlevel="4">

 <scaling units="Injector Duration (ms)" expression="x*.000000061" to_byte="x/.000000061" format="0.0000" fineincrement="0.1" coarseincrement="1" />

       <table type="Y Axis" name="Engine Speed" storagetype="float" endian="little">

        <scaling units="RPM" expression="x" to_byte="x" format="#" fineincrement="100" coarseincrement="1000" />

       </table>

       <description>Injector load threshold, varying with RPM, above which fuelling will go open loop after a delay.</description>

     </table> 

<table type="2D" name="CL Delay Period A" category="Fueling - CL/OL Transition" storagetype="uint16" endian="big" sizey="2" userlevel="4">

      

 <scaling units="Delay" expression="x" to_byte="x" format="#" fineincrement=".1" coarseincrement="1" />

      

 <table type="Static Y Axis" name="Delay Period" sizey="2">

        

 <data>A1</data>

 <data>A2</data>

 

  

 </table>

 <description>Delay periods when changing from closed to open loop fuelling. Reduce these for quicker open loop operation.</description>

    

 </table>

<table type="2D" name="CL Delay Period B" category="Fueling - CL/OL Transition" storagetype="uint16" endian="big" sizey="3" userlevel="4">

      

 <scaling units="Delay" expression="x" to_byte="x" format="#" fineincrement=".1" coarseincrement="1" />

      

 <table type="Static Y Axis" name="Delay Period" sizey="3">

        

 <data>B1</data>

 <data>B2</data>

 

 <data>B3</data>

   

 </table>

 <description>Delay periods when changing from closed to open loop fuelling. Reduce these for quicker open loop operation.</description>

    

 </table>

<table type="2D" name="CL Maximum Vehicle Speed" category="Fueling - CL/OL Transition" storagetype="float" endian="little" sizey="2" userlevel="2">

      <scaling units="Vehicle Speed (MPH)" expression="x*.621" to_byte="x/.621" format="#" fineincrement="1" coarseincrement="5" />

      <table type="Static Y Axis" name="(Condition) - Result" sizey="2">

        <data>(Below) - Check Other CL Tables</data>

        <data>(Above) - Clear CL Delay</data>

      </table>

      <description>When vehicle speed is the same or greater than the second value, the closed loop delay value is set to zero which can result in switching from closed loop to open loop depending on the current enrichment value as determined by the 'Open Loop Fueling' map. When vehicle speed drops below the first value, other specific closed loop triggers are reviewed. If all these triggers are below their thresholds, then the closed loop delay is determined from the 'CL to OL Delay' table. In this case, depending on the delay value, the 'CL to OL Transition with Delay (Base Pulse Width)' and 'CL to OL Transition with Delay (Throttle)' are used to determine the open loop to close loop transition and vice versa.</description>

    </table>

<table type="2D" name="CL Delay Maximum (Engine Load)" category="Fueling - CL/OL Transition" storagetype="float" endian="little" sizey="2" userlevel="2">

      <scaling units="Engine Load (g/rev)" expression="x" to_byte="x" format="0.00" fineincrement=".01" coarseincrement=".1" />

      <table type="Static Y Axis" name="(Condition) - Result" sizey="2">

        <data>(Below) - Check Other CL Tables</data>

        <data> (Above) - Clear CL Delay if Load Counter Threshold Exceeded</data>

      </table>

      <description>When the engine load is the same or greater than the second value, a counter value is incremented. If engine load remains equal to greater than the second value, the counter will be continue to be incremented and if it exceeds the 'CL Delay Engine Load Counter Threshold' value, the primary closed loop delay value is set to zero which can result in switching from closed loop to open loop depending on the current enrichment value as determined by the 'Open Loop Fueling' map. When engine load drops below the first value, the engine load counter value is set to zero and other specific closed loop triggers are reviewed. If all these triggers are below their thresholds, then the closed loop delay is determined from the 'CL to OL Delay' table. In this case, assuming a non-zero delay value, the 'CL to OL Transition with Delay (Base Pulse Width)' and 'CL to OL Transition with Delay (Throttle)' are used to determine the open loop to close loop transition and vice versa.</description>

    </table>

New Idle Parameters

Code:

<table name="Idle Speed Target G" storageaddress="118C34">

 <table type="Y Axis" storageaddress="1180FC" />

     </table>

<table name="Idle Speed Target H" storageaddress="118C94">

 <table type="Y Axis" storageaddress="118C54" />

     </table>

<table name="Idle Speed Target I" storageaddress="118CF4">

 <table type="Y Axis" storageaddress="118CB4" />

     </table>

<table name="Idle Throttle Target for Airflow" storageaddress="13C6A8">

 <table type="Y Axis" storageaddress="13C620" />

     </table>

<table name="Failsafe Idle Throttle Target for Airflow" storageaddress="109C00">

 <table type="Y Axis" storageaddress="109BF8" />

     </table>

<table type="2D" name="Idle Speed Target G" category="Idle Control" storagetype="uint16" endian="big" sizey="16" userlevel="1" logparam="P8">

      <scaling units="Engine Speed (RPM)" expression="x*.1953125" to_byte="x/.1953125" format="#" fineincrement="50" coarseincrement="100" />

      <table type="Y Axis" name="Coolant Temperature" storagetype="float" endian="little" logparam="P2">

        <scaling units="Degrees C" expression="x" to_byte="x" format="#" fineincrement="1" coarseincrement="5" />

      </table>

      <description>Idle speed target at different coolant temperatures.</description>

    </table>

<table type="2D" name="Idle Speed Target H" category="Idle Control" storagetype="uint16" endian="big" sizey="16" userlevel="1" logparam="P8">

      <scaling units="Engine Speed (RPM)" expression="x*.1953125" to_byte="x/.1953125" format="#" fineincrement="50" coarseincrement="100" />

      <table type="Y Axis" name="Coolant Temperature" storagetype="float" endian="little" logparam="P2">

        <scaling units="Degrees C" expression="x" to_byte="x" format="#" fineincrement="1" coarseincrement="5" />

      </table>

      <description>Idle speed target at different coolant temperatures.</description>

    </table>

<table type="2D" name="Idle Speed Target I" category="Idle Control" storagetype="uint16" endian="big" sizey="16" userlevel="1" logparam="P8">

      <scaling units="Engine Speed (RPM)" expression="x*.1953125" to_byte="x/.1953125" format="#" fineincrement="50" coarseincrement="100" />

      <table type="Y Axis" name="Coolant Temperature" storagetype="float" endian="little" logparam="P2">

        <scaling units="Degrees C" expression="x" to_byte="x" format="#" fineincrement="1" coarseincrement="5" />

      </table>

      <description>Idle speed target at different coolant temperatures.</description>

    </table>

<table type="2D" name="Failsafe Idle Throttle Target for Airflow" category="Idle Control" storagetype="float" endian="little" sizey="2" userlevel="5">

     <scaling units="Throttle Angle (Degrees)" expression="x" to_byte="x" format="#" fineincrement="0.1" coarseincrement="1" />

       <table type="Y Axis" name="Mass Airflow" storagetype="float" endian="little">

        <scaling units="g/s" expression="x" to_byte="x" format="#" fineincrement="1" coarseincrement="5" />

       </table>

       <description>Help!</description>

     </table>

<table type="2D" name="Idle Throttle Target for Airflow" category="Idle Control" storagetype="float" endian="little" sizey="34" userlevel="5">

     <scaling units="Throttle Angle (Degrees)" expression="x" to_byte="x" format="#" fineincrement="0.1" coarseincrement="1" />

       <table type="Y Axis" name="Mass Airflow" storagetype="float" endian="little">

        <scaling units="g/s" expression="x" to_byte="x" format="#" fineincrement="1" coarseincrement="5" />

       </table>

       <description>Help!</description>

     </table>

@Td-d

Quote:

Originally Posted by Kodename47 (Post 2057827)

M
Updated A/F Learning Ranges - There is Range E!

Do you know what the bounds/thresholds for each load range are?

Quote:

Originally Posted by Wepeel (Post 2057855)

Do you know what the bounds/thresholds for each load range are?

In what way? The learning ranges are done by MAF g/s and set the areas for the LTFT.

Quote:

Originally Posted by Kodename47 (Post 2059122)

In what way? The learning ranges are done by MAF g/s and set the areas for the LTFT.

Whoops, meant to ask what flow ranges are ABCDE. i.e. A=0-10 g/s, B=10-20 g/s,...

And with the addition of E, is the E range higher than the previous D, or did they just increase resolution?