Evo anti-lag ECU disassembly
I was referring to the ROM and not XML. I was asking if all the code to execute was on the ROM. If it is, and you edit the XML with an address and then open the ROM in ECUFLash, it will open the ROM and add the table if that address exists. Thus, if you change an address in the XML to reference another table and ECUFlash complains and won't open that table, I think it's safe to assume that address doesn't exist in the ROM, and thus doesn't exist in the ECU.
looking at the way the tables should look, the address change I listed I feel is incorrect. Someone more knowledgeable than me that is so inclined might want to look for it. 
JB, I didn't do it with your change and just copied over jcsbanks code and edited the settings to be what everbody else has, IE 2k-6k and 0 across the map.
I have some good news guys. If you recall, Oracle1 posted in the ALS thread during the first few months after it was created. He has since dropped off the map (no pun intended). He has been the only guy in this thread that has gotten some form of ALS working properly on a IX. I have gotten a hold of him and he tells me that he knows people with JDM IX's who run ALS editing those tables without any of the SAS hardware! He's currently editing my T13 ROM and I will post the results after testing it.
I have some good news guys. If you recall, Oracle1 posted in the ALS thread during the first few months after it was created. He has since dropped off the map (no pun intended). He has been the only guy in this thread that has gotten some form of ALS working properly on a IX. I have gotten a hold of him and he tells me that he knows people with JDM IX's who run ALS editing those tables without any of the SAS hardware! He's currently editing my T13 ROM and I will post the results after testing it.
I was referring to the ROM and not XML. I was asking if all the code to execute was on the ROM. If it is, and you edit the XML with an address and then open the ROM in ECUFLash, it will open the ROM and add the table if that address exists. Thus, if you change an address in the XML to reference another table and ECUFlash complains and won't open that table, I think it's safe to assume that address doesn't exist in the ROM, and thus doesn't exist in the ECU.
Computers are very stupid. And the way they understand data is pretty basic because of that. They basically don't: we have to tell them how to.
Furthermore, as is discussed above, and I will say here gain whether or not an address is in the ROM is irrelevant. It is whether or not it can be executed..
If it can't be executed, then there be code in the ROM to make your engine produce Gold and you wouldn't get any gold deposits out your exhaust
ECUFlash is not the same as the ECU in your car. It does not know how the ECU interprets/runs the code in the rom and thus any tests whereby you assume that because ECUFlash can read/use the rom that the ECU can are therefore null and void
.If I'm not able to get through after this then I give up
.
Last edited by codgi; Mar 15, 2008 at 04:53 PM.
As Jack of Trades correctly says if you tell ECUFlash to interpret an address it will stupidly look at that address and try to interpret it as you tell it to. Its doesn't know/care whether or not that address actually means something because it is not intelligent enough to know so. It assumes that the person who has changed the addresses actually knows what they are pointing to and how to adjust it.
Computers are very stupid. And the way they understand data is pretty basic because of that. They basically don't: we have to tell them how to.
Furthermore, as is discussed above, and I will say here gain whether or not an address is in the ROM is irrelevant. It is whether or not it can be executed..
If it can't be executed, then there be code in the ROM to make your engine produce Gold and you wouldn't get any gold deposits out your exhaust
ECUFlash is not the same as the ECU in your car. It does not know how the ECU interprets/runs the code in the rom and thus any tests whereby you assume that because ECUFlash can read/use the rom that the ECU can are therefore null and void.
If I'm not able to get through after this then I give up.
Computers are very stupid. And the way they understand data is pretty basic because of that. They basically don't: we have to tell them how to.
Furthermore, as is discussed above, and I will say here gain whether or not an address is in the ROM is irrelevant. It is whether or not it can be executed..
If it can't be executed, then there be code in the ROM to make your engine produce Gold and you wouldn't get any gold deposits out your exhaust
ECUFlash is not the same as the ECU in your car. It does not know how the ECU interprets/runs the code in the rom and thus any tests whereby you assume that because ECUFlash can read/use the rom that the ECU can are therefore null and void
.If I'm not able to get through after this then I give up
. Then I guess I'm wondering how people scour the ECU for memory addresses and know what does what?
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Its like a puzzle. You figure out one thing, and then you use that to help figure out other things. Its a painstaking process that requires some knowledge of computer programming and how engines work.
. You'd want to read up on "Reverse Engineering". Haven't read this particular book but it will help point you in the correct direction:http://www.amazon.com/Reverse-Engine...pd_sim_b_img_2
www.aktivematrix.com is pretty informative to.
The defs that JCSbanks listed definitely dont jive with the USDM rom. Not that I expected them too, but thats not going to work for us. I guess its time I learned to use IDA...I mean I managed to learn Emange how hard can it be?
Evolving Member
Joined: May 2007
Posts: 178
Likes: 0
From: Italy
Try this, not deep looked into, but seems right:
Code:
<table name="ALS minimum vehicle speed to trigger" category="ALS" address="1e12" type="1D" level="1" scaling="VehicleSpeed"/> <table name="ALS minimum coolant temperature to trigger" category="ALS" address="1e14" type="1D" level="1" scaling="Temp"/> <table name="ALS minimum RPM to trigger" category="ALS" address="1e16" type="1D" level="1" scaling="RPMStatLimit"/> <table name="ALS minimum load to trigger" category="ALS" address="1e18" type="1D" level="1" scaling="Load16"/> <table name="ALS minimum time to trigger" category="ALS" address="1e1a" type="1D" level="1" scaling="TimeSec"/> <table name="ALS trigger valid time" category="ALS" address="1e1c" type="1D" level="1" scaling="TimeSec"/> <table name="ALS Load below which active" category="ALS" address="1e1e" type="1D" level="1" scaling="Load16"/> <table name="ALS active time limit" category="ALS" address="1e20" type="1D" level="1" scaling="TimeSec"/> <table name="ALS Delay before air injection" category="ALS" address="1e22" type="1D" level="1" scaling="TimeSec"/> <table name="ALS Delay before fuel injection" category="ALS" address="1e24" type="1D" level="1" scaling="TimeSec"/> <table name="ALS Fuel injector time" category="ALS" address="1e26" type="1D" level="1" scaling="TimeSec"/> <table name="ALS Air injection time" category="ALS" address="4e3a" type="2D" level="1" scaling="TimeSecByte"> <table name="RPM" address="700e" type="X Axis" elements="9" scaling="RPM"/> </table>
Newbie
Joined: Nov 2007
Posts: 93
Likes: 0
From: france
Try this, not deep looked into, but seems right:
Code:
<table name="ALS minimum vehicle speed to trigger" category="ALS" address="1e12" type="1D" level="1" scaling="VehicleSpeed"/> <table name="ALS minimum coolant temperature to trigger" category="ALS" address="1e14" type="1D" level="1" scaling="Temp"/> <table name="ALS minimum RPM to trigger" category="ALS" address="1e16" type="1D" level="1" scaling="RPMStatLimit"/> <table name="ALS minimum load to trigger" category="ALS" address="1e18" type="1D" level="1" scaling="Load16"/> <table name="ALS minimum time to trigger" category="ALS" address="1e1a" type="1D" level="1" scaling="TimeSec"/> <table name="ALS trigger valid time" category="ALS" address="1e1c" type="1D" level="1" scaling="TimeSec"/> <table name="ALS Load below which active" category="ALS" address="1e1e" type="1D" level="1" scaling="Load16"/> <table name="ALS active time limit" category="ALS" address="1e20" type="1D" level="1" scaling="TimeSec"/> <table name="ALS Delay before air injection" category="ALS" address="1e22" type="1D" level="1" scaling="TimeSec"/> <table name="ALS Delay before fuel injection" category="ALS" address="1e24" type="1D" level="1" scaling="TimeSec"/> <table name="ALS Fuel injector time" category="ALS" address="1e26" type="1D" level="1" scaling="TimeSec"/> <table name="ALS Air injection time" category="ALS" address="4e3a" type="2D" level="1" scaling="TimeSecByte"> <table name="RPM" address="700e" type="X Axis" elements="9" scaling="RPM"/> </table>
thank
I find
time 0.0 is good
rmp
1750/2000/2500/3000/3500/4000/4500/5000/5500
is good or no?
Last edited by agron25; Mar 16, 2008 at 01:55 AM.
Evolving Member
Joined: May 2007
Posts: 178
Likes: 0
From: Italy
Code:
<table name="ALS Air injection time" category="ALS" address="4e3a" type="2D" level="1" scaling="TimeSecByte"> <table name="RPM" address="77ae" type="X Axis" elements="9" scaling="RPM"/> </table>