What is the max load are u seeing guys?
The load limit calculation is correct, but in working through it, it gets clipped to a byte at a crucial point which stops our table changes having any effect. I think I'll nobble it somewhere else instead
Mellon, for 96940011, try adding this to your xml and change the value from "2ba1" to "0x9".
<table name="Set to 9 to remove load limit" address="28140" type="1D" level="1" scaling="Hex16"/>
I hope this allows higher than 380 load, pls check for normal behaviour, and that it registers the correct fuelling and timing from your maps though as there could be other limits or overflows in there.
I would just put the earlier tables I mentioned back to stock, no longer necessary, this disables their effect anyway.
<table name="Set to 9 to remove load limit" address="28140" type="1D" level="1" scaling="Hex16"/>
I hope this allows higher than 380 load, pls check for normal behaviour, and that it registers the correct fuelling and timing from your maps though as there could be other limits or overflows in there.
I would just put the earlier tables I mentioned back to stock, no longer necessary, this disables their effect anyway.
Quick Question:
I also have an EVO 8 and am in the same place as Mellon. However, I have 94710015. I have not yet tested the 380 load limit since setting the earlier tables to "255". Shall I do that first, or should I just await Mellon's result and inquire about this same fix for that ROM?
I also have an EVO 8 and am in the same place as Mellon. However, I have 94710015. I have not yet tested the 380 load limit since setting the earlier tables to "255". Shall I do that first, or should I just await Mellon's result and inquire about this same fix for that ROM?
Account Disabled
iTrader: (38)
Joined: Aug 2005
Posts: 9,319
Likes: 1
From: Virginia Beach, Virginia
Mellon, for 96940011, try adding this to your xml and change the value from "2ba1" to "0x9".
<table name="Set to 9 to remove load limit" address="28140" type="1D" level="1" scaling="Hex16"/>
I hope this allows higher than 380 load, pls check for normal behaviour, and that it registers the correct fuelling and timing from your maps though as there could be other limits or overflows in there.
I would just put the earlier tables I mentioned back to stock, no longer necessary, this disables their effect anyway.
<table name="Set to 9 to remove load limit" address="28140" type="1D" level="1" scaling="Hex16"/>
I hope this allows higher than 380 load, pls check for normal behaviour, and that it registers the correct fuelling and timing from your maps though as there could be other limits or overflows in there.
I would just put the earlier tables I mentioned back to stock, no longer necessary, this disables their effect anyway.
Account Disabled
iTrader: (38)
Joined: Aug 2005
Posts: 9,319
Likes: 1
From: Virginia Beach, Virginia
success! idle/cruise/wot looks normal and feels fine to me. Thanks Jcsbanks!
Code:
4531.25 149.375 4593.75 158.75 4625 168.75 4718.75 180.625 4750 195.625 4843.75 217.1875 4906.25 239.375 5000 272.8125 5093.75 305.3125 5187.5 343.75 5343.75 344.375 5500 341.25 5625 356.875 5750 365 5906.25 370.625 6062.5 373.75 6218.75 381.5625 6375 383.4375 6531.25 386.25 6656.25 389.0625 6843.75 389.375 6937.5 392.5 7062.5 392.5 7218.75 391.25 7343.75 385.625 7437.5 383.75 7593.75 381.25 7750 377.5 7843.75 373.4375 7968.75 370
96260009:
<table name="Set to 9 to remove load limit" address="25d40" type="1D" level="1" scaling="Hex16"/>
90550001:
<table name="Set to 9 to remove load limit" address="22014" type="1D" level="1" scaling="Hex16"/>
<table name="Set to 9 to remove load limit" address="25d40" type="1D" level="1" scaling="Hex16"/>
90550001:
<table name="Set to 9 to remove load limit" address="22014" type="1D" level="1" scaling="Hex16"/>








