TephraMod V7
Nov 22, 2009 | 06:39 PM
#1096
I went to get ready to load up Live mapping MAF based ROM into my car yesterday but noticed the NLS rpm drop box wasn't accessible. Had anyone picked up on this and should i just download it again?
Also in the big maps the load column said LOAD (kpa), is that what its just labeled or is it really boost based load which should actually be for SD based and not maf.
Also in the big maps the load column said LOAD (kpa), is that what its just labeled or is it really boost based load which should actually be for SD based and not maf.
Nov 23, 2009 | 12:32 AM
#1098
Newbie
Joined: Jan 2009
Posts: 55
Likes: 0
From: Long Beach, CA
I notice the same thing. I think what is really missing are the mods to log boost via JDM MAP. I did not see the tables that set the required values for the sensor, only the scalings are on the xlm. The tables like the ones below are missing on the xlm but I do not know the address for this ROM. They are not in MRFred original thread. Where did you get them? I am not sure if the values required for JDM3Bar are already in the ROM or if they need to be modified to the correct values.
<table name="MAP Scaling" category="MAPSensor" address="????" type="2D" level="1" scaling="uint8">
<table name="MAP Output" address="????" type="Y Axis" elements="9" scaling="Volts16"/>
</table>
<table name="MAP Fault Trig: Mid VE Max #1" category="MAPSensor" address="????" type="1D" level="1" scaling="Volts16"/>
<table name="MAP Fault Trig: Mid VE Min #1" category="MAPSensor" address="????" type="1D" level="1" scaling="Volts16"/>
<table name="MAP Fault Trig High VE #1" category="MAPSensor" address="????" type="1D" level="1" scaling="Volts16"/>
<table name="MAP vs MAF Baro" category="MAPSensor" address="????" type="1D" level="1" scaling="uint16"/>
<table name="MAP Scaling" category="MAPSensor" address="????" type="2D" level="1" scaling="uint8">
<table name="MAP Output" address="????" type="Y Axis" elements="9" scaling="Volts16"/>
</table>
<table name="MAP Fault Trig: Mid VE Max #1" category="MAPSensor" address="????" type="1D" level="1" scaling="Volts16"/>
<table name="MAP Fault Trig: Mid VE Min #1" category="MAPSensor" address="????" type="1D" level="1" scaling="Volts16"/>
<table name="MAP Fault Trig High VE #1" category="MAPSensor" address="????" type="1D" level="1" scaling="Volts16"/>
<table name="MAP vs MAF Baro" category="MAPSensor" address="????" type="1D" level="1" scaling="uint16"/>
Nov 23, 2009 | 07:54 AM
#1099
Evolving Member
Joined: Dec 2005
Posts: 232
Likes: 0
From: South Africa
Ok, did some testing this weekend and found some interesting things
I ended up using 2 byte load + baro and that got me to less than 5% difference between actual (ecu) and logged. it would only log the next cell up if it was in the upper edge of the current cell (my load goes up in 10's)
way i tested it... picked a moderate boost level (22psi) and then did a log, saw the load column it was logging.... i.e. 160. then made the 2 columns 150, 155, 160, 165, 170... in those columns i made the timing 6, 5, 4, 3, 2 deg the whole way down the column. then did a run. looked at the timing in that row and saw if it matched the timing table... found iwas over 20% out on raw load.
baro and temp was out more than just baro
ALso found this out.. I know the 96530607 rom has an option for timing vs air temp and coolant temp but the 88590715 does not in the rom and have noticed that the equal to or below 24 deg C (75 deg F) it adds 1 deg of timing and equal to or above 32 deg C ( 89 deg F) it pulls 1 deg of timing.
Is there a patch for this on the 885 rom or not.
Thanks
I ended up using 2 byte load + baro and that got me to less than 5% difference between actual (ecu) and logged. it would only log the next cell up if it was in the upper edge of the current cell (my load goes up in 10's)
way i tested it... picked a moderate boost level (22psi) and then did a log, saw the load column it was logging.... i.e. 160. then made the 2 columns 150, 155, 160, 165, 170... in those columns i made the timing 6, 5, 4, 3, 2 deg the whole way down the column. then did a run. looked at the timing in that row and saw if it matched the timing table... found iwas over 20% out on raw load.
baro and temp was out more than just baro
ALso found this out.. I know the 96530607 rom has an option for timing vs air temp and coolant temp but the 88590715 does not in the rom and have noticed that the equal to or below 24 deg C (75 deg F) it adds 1 deg of timing and equal to or above 32 deg C ( 89 deg F) it pulls 1 deg of timing.
Is there a patch for this on the 885 rom or not.
Thanks
Nov 24, 2009 | 01:39 AM
#1100
Newbie
Joined: Oct 2009
Posts: 13
Likes: 0
From: Europe
V7 is perfect for me, rom 88580714, original rom 88840016... Very good job Tephra...
Donation sent.
A question, how could I log Mivec, as MUT40 and MUT41 are used for 1byte gear
1byte load..
I'm not using boost control in the ECU because I have an AVCR, thanks for your answer
Donation sent.
A question, how could I log Mivec, as MUT40 and MUT41 are used for 1byte gear
1byte load..
I'm not using boost control in the ECU because I have an AVCR, thanks for your answer
Nov 24, 2009 | 03:08 PM
#1104
guys for 96532706 (ie the Livemap version) the defs for the "Injector Cranking enrichment IPW Adder (Main)" are wrong. they need to be 0x58d0 and the axis is 0x69d8 and 9 elements.
i presume the other xmls will be wrong too.
i presume the other xmls will be wrong too.
Nov 24, 2009 | 06:38 PM
#1106
Now that I look at it, this does look strange. Thanks!
Last edited by D-VO; Nov 24, 2009 at 06:51 PM.
Nov 25, 2009 | 03:50 AM
#1107
Ok, did some testing this weekend and found some interesting things
I ended up using 2 byte load + baro and that got me to less than 5% difference between actual (ecu) and logged. it would only log the next cell up if it was in the upper edge of the current cell (my load goes up in 10's)
way i tested it... picked a moderate boost level (22psi) and then did a log, saw the load column it was logging.... i.e. 160. then made the 2 columns 150, 155, 160, 165, 170... in those columns i made the timing 6, 5, 4, 3, 2 deg the whole way down the column. then did a run. looked at the timing in that row and saw if it matched the timing table... found iwas over 20% out on raw load.
baro and temp was out more than just baro
ALso found this out.. I know the 96530607 rom has an option for timing vs air temp and coolant temp but the 88590715 does not in the rom and have noticed that the equal to or below 24 deg C (75 deg F) it adds 1 deg of timing and equal to or above 32 deg C ( 89 deg F) it pulls 1 deg of timing.
Is there a patch for this on the 885 rom or not.
Thanks
I ended up using 2 byte load + baro and that got me to less than 5% difference between actual (ecu) and logged. it would only log the next cell up if it was in the upper edge of the current cell (my load goes up in 10's)
way i tested it... picked a moderate boost level (22psi) and then did a log, saw the load column it was logging.... i.e. 160. then made the 2 columns 150, 155, 160, 165, 170... in those columns i made the timing 6, 5, 4, 3, 2 deg the whole way down the column. then did a run. looked at the timing in that row and saw if it matched the timing table... found iwas over 20% out on raw load.
baro and temp was out more than just baro
ALso found this out.. I know the 96530607 rom has an option for timing vs air temp and coolant temp but the 88590715 does not in the rom and have noticed that the equal to or below 24 deg C (75 deg F) it adds 1 deg of timing and equal to or above 32 deg C ( 89 deg F) it pulls 1 deg of timing.
Is there a patch for this on the 885 rom or not.
Thanks
Hmm....interesting sooo what you are saying is that the 2byte load + baro is the most accurate for you...? But remember this is in relation to the timing table...what about the fuel table and boost?
Nov 25, 2009 | 07:40 AM
#1108
Evolving Member
Joined: Dec 2005
Posts: 232
Likes: 0
From: South Africa
not sure i understand what you saying? my fueling is more of a scaling latency depentant, as far as i see it, it seems that the load i am logging the ecu is using the same load so all matches up, boost is load based boost control , not psi based.
remember i am at 5500ft above sea level
Mike
remember i am at 5500ft above sea level
Mike
Nov 25, 2009 | 07:42 AM
#1109
Just wanted to verify that mapswitching is working properly in v7 final. I am running 96531706, speed density is the isht! All other mods seem to work dandy, I think I've tested all of them.
Nov 25, 2009 | 07:52 AM
#1110
not sure i understand what you saying? my fueling is more of a scaling latency depentant, as far as i see it, it seems that the load i am logging the ecu is using the same load so all matches up, boost is load based boost control , not psi based.
remember i am at 5500ft above sea level
Mike
remember i am at 5500ft above sea level
Mike
I am on 96260009 and I am using 2 byte load with 8984 and 8985 as the mut 00 and mut 01 addresses. I believe that this is 2byte load raw...will try 2byte load baro and temp...
what loads are u using to put in your BDEL tables - the loads gained from 2byte load + baro?