Tephra v7 and Load?
Mar 10, 2010, 02:41 PM
#1
Evolving Member
Thread Starter
Join Date: Aug 2009
Location: Herndon, VA
Posts: 128
Likes: 0
Received 0 Likes
on
0 Posts
Tephra v7 and Load?
So what's the deal with the Tephra rom and load? It appears to be configured to use the 1 Byte Load factor only (request 41).
What about the compensated loads? I've read that based on the Intake Air Temperature sensors reading, timing may be based on load with baro compensation, or load with baro and temp compensation.
The Tephra v7 thread states this;
Why is 2byte load no longer needed? According to the following, the new 1byte load is still RAW Load.
Isn't the ECU almost always using a temperature and/or baro compensated load?
What about the compensated loads? I've read that based on the Intake Air Temperature sensors reading, timing may be based on load with baro compensation, or load with baro and temp compensation.
The Tephra v7 thread states this;
Preconfigured MUT Requests
MUT00+MUT01 = 2byte airflow (ie MrFreds mod in g/s or lb/min)
MUT02+MUT03 = 2byte airflow (ie MAFHz)
MUT40 = 1byte gear
MUT41 = 1byte load
MUT42+MUT43 = 2byte SPEED/RPM ratio (to get your gear ratios correct - if you need to)
2byte load AND 2byte RPM are no longer included and IMHO not needed!
MUT00+MUT01 = 2byte airflow (ie MrFreds mod in g/s or lb/min)
MUT02+MUT03 = 2byte airflow (ie MAFHz)
MUT40 = 1byte gear
MUT41 = 1byte load
MUT42+MUT43 = 2byte SPEED/RPM ratio (to get your gear ratios correct - if you need to)
2byte load AND 2byte RPM are no longer included and IMHO not needed!
Isn't the ECU almost always using a temperature and/or baro compensated load?
Addresses
MUT Table
36200
There are 4 different 2-byte Load choices each with different correction factors.
2-byte LOAD_Raw (no temp compensation)
MUT00 = 8984
MUT01 = 8985
2-byte LOAD_Temp_Compensated
MUT00 = 8986
MUT01 = 8987
2-byte LOAD_Baro_Compensated
MUT00 = 8988
MUT01 = 8989
2-byte LOAD_Temp_and_Baro_Compensated
MUT00 = 898A
MUT01 = 898B
Load correction note: The ECU uses the following logic to find the lookup info it needs:
Fuel maps will either use Load_Raw OR LOAD_Temp_and_Baro_Compensated depending on an certain conditions
Ignition Maps will either use LOAD_Baro_Compensated OR LOAD_Temp_and_Baro_Compensated depending on the MAF IAT. (Thanks to Tephra for this info).
It is typically best to use the 2-byte LOAD_Temp_and_Baro_Compensated for tuning, while taking into account the lookup factors mentioned above for both Fuel and Ignition Timing. This will allow the tuner to accurately tune ignition timing while being able to compensate for the lookup logic for fueling. LOAD_Raw is typically 10-20 points higher than LOAD_Temp_and_Baro_Compensated at peak boost. You must take this into account when tuning using the 2-byte loads. With the advent of Tehpra's 1byte load(using a Tephra Mod ROM), you can use 1byte load(which is actually LOAD_Raw) to log LOAD_Raw. You can setup your 2byte load to be LOAD_Temp_and_Baro_Compensated, this will allow the tuner to see both compensated load and LOAD_Raw. Ultimatly, how you decide to set-up your 2-byte load and the methods you use to tune are up to you.
Other Addresses:
2-byte RPM
MUT02 = 8962
MUT03 = 8963
2-byte AirFlow
MUT04 = 89E2
MUT05 = 89E3
Retrieved from "http://evoecu.logic.net/wiki/96530006"
MUT Table
36200
There are 4 different 2-byte Load choices each with different correction factors.
2-byte LOAD_Raw (no temp compensation)
MUT00 = 8984
MUT01 = 8985
2-byte LOAD_Temp_Compensated
MUT00 = 8986
MUT01 = 8987
2-byte LOAD_Baro_Compensated
MUT00 = 8988
MUT01 = 8989
2-byte LOAD_Temp_and_Baro_Compensated
MUT00 = 898A
MUT01 = 898B
Load correction note: The ECU uses the following logic to find the lookup info it needs:
Fuel maps will either use Load_Raw OR LOAD_Temp_and_Baro_Compensated depending on an certain conditions
Ignition Maps will either use LOAD_Baro_Compensated OR LOAD_Temp_and_Baro_Compensated depending on the MAF IAT. (Thanks to Tephra for this info).
It is typically best to use the 2-byte LOAD_Temp_and_Baro_Compensated for tuning, while taking into account the lookup factors mentioned above for both Fuel and Ignition Timing. This will allow the tuner to accurately tune ignition timing while being able to compensate for the lookup logic for fueling. LOAD_Raw is typically 10-20 points higher than LOAD_Temp_and_Baro_Compensated at peak boost. You must take this into account when tuning using the 2-byte loads. With the advent of Tehpra's 1byte load(using a Tephra Mod ROM), you can use 1byte load(which is actually LOAD_Raw) to log LOAD_Raw. You can setup your 2byte load to be LOAD_Temp_and_Baro_Compensated, this will allow the tuner to see both compensated load and LOAD_Raw. Ultimatly, how you decide to set-up your 2-byte load and the methods you use to tune are up to you.
Other Addresses:
2-byte RPM
MUT02 = 8962
MUT03 = 8963
2-byte AirFlow
MUT04 = 89E2
MUT05 = 89E3
Retrieved from "http://evoecu.logic.net/wiki/96530006"
Last edited by Seijuro; Mar 10, 2010 at 04:10 PM.
Mar 10, 2010, 04:12 PM
#3
Evolving Member
Thread Starter
Join Date: Aug 2009
Location: Herndon, VA
Posts: 128
Likes: 0
Received 0 Likes
on
0 Posts
What's not necessary about it is what I don't understand.
EDIT: I guess to try and answer my own question, the Tephra v7 post is trying to say that 2byte RAW Load is not necessary because it's redundant.
But, I think in the real world, you still need your baro and temp compensated loads.
Is the same process of dividing down the load value in the ECU, and then multiplying it back out in the logger applied for these compensated loads somewhere as well and I'm just not seeing it?
Last edited by Seijuro; Mar 10, 2010 at 04:17 PM.
Mar 20, 2010, 11:53 AM
#5
Evolving Member
Join Date: Mar 2010
Location: Behind a laptop in FLA
Posts: 323
Likes: 0
Received 0 Likes
on
0 Posts
You can setup your 2byte load to be LOAD_Temp_and_Baro_Compensated, this will allow the tuner to see both compensated load and LOAD_Raw. Ultimatly, how you decide to set-up your 2-byte load and the methods you use to tune are up to you.
Thread
Thread Starter
Forum
Replies
Last Post
