A bunch of load calculation related maps
Apr 27, 2014, 06:05 AM
#31
i think the stock value (converted from baro -> raw -> load) is like 29... which means if you left alone you would never permit the code to detect increases or decreases of TPS.
I've set mine to 200... so that its disabled ABOVE 200 load...
I've set mine to 200... so that its disabled ABOVE 200 load...
Apr 28, 2014, 05:31 AM
#32
Evolving Member
iTrader: (1)
Join Date: Mar 2010
Location: PA
Posts: 304
Likes: 0
Received 0 Likes
on
0 Posts
so lately i have been focusing on driveability of my car, and i have to say its sucking a lot, but i think ive made some nice improvments..
one thing i noticed is that by increasing the "Load multiplier end when TPS decreased by % (hysteresis)" to stop 5% of load being dropped when you at WOT and the TPS drops by 0.4% (really annoying)... i feel like this made a big impact to regular driving... for me at least... problably a stock motor with normal cams (or less aggresive cam profile) it would be ok..
anyways i made a patch so that you can leave that value at 1, but use a load threshold instead:
53040010:
Quite simply it changes the "is the throttle being increased or released" routine so instead of using a Baro check (which would never get tripped because its WAY out of range) it uses a Load check...
#1 changes Baro to Load lookup
#2 changes the comparison order (ie instead of Load < value it does Load > value
#3 just remaps the Baro value into Load...
I haven't tested it yet, but it loads up in IDA fine, ill give it a go tomorrow...
See attached image for why I did this - this was using 2 as the value (or 0.8%) and it still pulled out load... bottom graph Red line indicates when the ECU thinks TPS has decreased or increased... bit crap :S
one thing i noticed is that by increasing the "Load multiplier end when TPS decreased by % (hysteresis)" to stop 5% of load being dropped when you at WOT and the TPS drops by 0.4% (really annoying)... i feel like this made a big impact to regular driving... for me at least... problably a stock motor with normal cams (or less aggresive cam profile) it would be ok..
anyways i made a patch so that you can leave that value at 1, but use a load threshold instead:
53040010:
Code:
<table name="TPS Liftoff Baro to Load patch #1 (0xC6DC -> 0xC766)" category="Misc" address="17f6a" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Baro to Load patch #2 (0x0056 -> 0x0650)" category="Misc" address="17f6c" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Max Load patch" category="Misc" address="546a4" type="1D" scaling="Load"/>
#1 changes Baro to Load lookup
#2 changes the comparison order (ie instead of Load < value it does Load > value
#3 just remaps the Baro value into Load...
I haven't tested it yet, but it loads up in IDA fine, ill give it a go tomorrow...
See attached image for why I did this - this was using 2 as the value (or 0.8%) and it still pulled out load... bottom graph Red line indicates when the ECU thinks TPS has decreased or increased... bit crap :S
Thank you!
(this is with 1 and 1 in the tps increase/decrease fields)
Apr 28, 2014, 06:51 AM
#34
So what we need to know is if the patched data remains the same or changes also but here are the addresses as requested and we'll have to wait for tephra to confirm patched data.
Patch #1 Stock value changed from C6DC -> C6F8
Patch #2 Stock value matches.
Max Load patch data matches as "29"
Code:
<table name="TPS Liftoff Baro to Load patch #1 (0xC6F8 -> 0xC784)" category="Misc" address="1878a" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Baro to Load patch #2 (0x0056 -> 0x0650)" category="Misc" address="1878c" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Max Load patch" category="Misc" address="546ce" type="1D" scaling="Load"/>
Last edited by itzwolf; Apr 28, 2014 at 11:56 AM. Reason: Updated Load address in Patch #1 description. Thanks rpacheco
Apr 28, 2014, 07:22 AM
#35
59580004:
Again stock value changed so confirmation needs done before attempting these patches.
Patch #1 Stock value changed from C6DC -> C734
Patch #2 Stock value matches.
Max Load patch data matches as "29"
Again stock value changed so confirmation needs done before attempting these patches.
Patch #1 Stock value changed from C6DC -> C734
Patch #2 Stock value matches.
Max Load patch data matches as "29"
Code:
<table name="TPS Liftoff Baro to Load patch #1 (0xC734 -> 0xC7C0)" category="Misc" address="1a866" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Baro to Load patch #2 (0x0056 -> 0x0650)" category="Misc" address="1a868" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Max Load patch" category="Misc" address="546d8" type="1D" scaling="Load"/>
Last edited by itzwolf; Apr 29, 2014 at 07:31 AM.
Apr 28, 2014, 08:13 AM
#36
Evolving Member
iTrader: (1)
Join Date: Mar 2010
Location: PA
Posts: 304
Likes: 0
Received 0 Likes
on
0 Posts
Well this isn't an exact one for one as the data in the ROM changed for Patch #1.
So what we need to know is if the patched data remains the same or changes also but here are the addresses as requested and we'll have to wait for tephra to confirm patched data.
Patch #1 Stock value changed from C6DC -> C6F8
Patch #2 Stock value matches.
Max Load patch data matches as "29"
So what we need to know is if the patched data remains the same or changes also but here are the addresses as requested and we'll have to wait for tephra to confirm patched data.
Patch #1 Stock value changed from C6DC -> C6F8
Patch #2 Stock value matches.
Max Load patch data matches as "29"
Code:
<table name="TPS Liftoff Baro to Load patch #1 (0xC6F8 -> 0xC766)" category="Misc" address="1878a" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Baro to Load patch #2 (0x0056 -> 0x0650)" category="Misc" address="1878c" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Max Load patch" category="Misc" address="546ce" type="1D" scaling="Load"/>
Apr 28, 2014, 11:33 AM
#38
Newbie
Join Date: Oct 2011
Location: Brazil
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
Well this isn't an exact one for one as the data in the ROM changed for Patch #1.
So what we need to know is if the patched data remains the same or changes also but here are the addresses as requested and we'll have to wait for tephra to confirm patched data.
Patch #1 Stock value changed from C6DC -> C6F8
Patch #2 Stock value matches.
Max Load patch data matches as "29"
So what we need to know is if the patched data remains the same or changes also but here are the addresses as requested and we'll have to wait for tephra to confirm patched data.
Patch #1 Stock value changed from C6DC -> C6F8
Patch #2 Stock value matches.
Max Load patch data matches as "29"
Code:
<table name="TPS Liftoff Baro to Load patch #1 (0xC6F8 -> 0xC766)" category="Misc" address="1878a" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Baro to Load patch #2 (0x0056 -> 0x0650)" category="Misc" address="1878c" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Max Load patch" category="Misc" address="546ce" type="1D" scaling="Load"/>
BE CAREFUL GUYS! It's not just a question of finding the right table addresses. Patch #1 requires you to find the correct address for load. This should be the correct xml for 55570005 (and please have someone validate it):
Code:
<table name="TPS Liftoff Baro to Load patch #1 (0xC6F8 -> 0xC784)" category="Misc" address="1878a" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Baro to Load patch #2 (0x0056 -> 0x0650)" category="Misc" address="1878c" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Max Load patch" category="Misc" address="546ce" type="1D" scaling="Load"/>
Apr 28, 2014, 11:44 AM
#39
Newbie
Join Date: Oct 2011
Location: Brazil
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
59580004:
Again stock value changed so confirmation needs done before attempting these patches.
Patch #1 Stock value changed from C6DC -> C734
Patch #2 Stock value matches.
Max Load patch data matches as "29"
Again stock value changed so confirmation needs done before attempting these patches.
Patch #1 Stock value changed from C6DC -> C734
Patch #2 Stock value matches.
Max Load patch data matches as "29"
Code:
<table name="TPS Liftoff Baro to Load patch #1 (0xC734 -> 0xC766)" category="Misc" address="18866" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Baro to Load patch #2 (0x0056 -> 0x0650)" category="Misc" address="18868" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Max Load patch" category="Misc" address="546d8" type="1D" scaling="Load"/>
Same here. One has to find the correct address for the load lookup in Patch #1. Address 0xC766 relates to the load address in Tephra's rom.
Apr 28, 2014, 11:54 AM
#40
BE CAREFUL GUYS! It's not just a question of finding the right table addresses. Patch #1 requires you to find the correct address for load. This should be the correct xml for 55570005 (and please have someone validate it):
Code:
<table name="TPS Liftoff Baro to Load patch #1 (0xC6F8 -> 0xC784)" category="Misc" address="1878a" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Baro to Load patch #2 (0x0056 -> 0x0650)" category="Misc" address="1878c" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Max Load patch" category="Misc" address="546ce" type="1D" scaling="Load"/>
Thank you for finding the 55570005 load address, happen to have the address for the 59580004 ROM? Is it C7C0?
Last edited by itzwolf; Apr 28, 2014 at 12:01 PM.
Apr 28, 2014, 12:05 PM
#42
Should be the following:
Code:
<table name="TPS Liftoff Baro to Load patch #1 (0xC728 -> 0xC7B4)" category="Misc" address="1a72e" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Baro to Load patch #2 (0x0056 -> 0x0650)" category="Misc" address="1a730" type="1D" scaling="Hex16"/> <table name="TPS Liftoff Max Load patch" category="Misc" address="546ce" type="1D" scaling="Load"/>
Last edited by itzwolf; Apr 28, 2014 at 12:12 PM.
Apr 28, 2014, 12:13 PM
#44
Newbie
Join Date: Oct 2011
Location: Brazil
Posts: 18
Likes: 0
Received 0 Likes
on
0 Posts
I don't have the disassembly for that rom but C7C0 seems correct. I just checked the evoscan xml for that rom at goldenevo.com, and the load address is 0x80887C0, so it seems you got it right.