Disable ALL circuit tests in the ECU
Apr 25, 2011, 07:50 PM
#34
You can set the byte at address 101C to 0 in 96530006 and it will disable all the checks in FCA and FDA periphery bits.
There is an extensive number of these master control bytes that can kill HUGE chunks of code very easily. In 96530006 these byte are located from 101c to 1091.
I WOULD NOT go randomly changing these to 0 though as you can kill some very important items with some of these. They are not limited to "1" or "0" either, some have numbers that will completely change the configuration of the ECU code ran byt changing from like a "4" to "5".
I'm looking to do exactly what you are talking about, but I'm interested in more then just killing the performance checks, I want to kill the code that it would even check so I have a much better idea of EXACTLY what is going on at all times.
Unfortunately, there is some very extensive code in some of the emissions stuff that doesn't look like it will be very straight forward.
There is an extensive number of these master control bytes that can kill HUGE chunks of code very easily. In 96530006 these byte are located from 101c to 1091.
I WOULD NOT go randomly changing these to 0 though as you can kill some very important items with some of these. They are not limited to "1" or "0" either, some have numbers that will completely change the configuration of the ECU code ran byt changing from like a "4" to "5".
I'm looking to do exactly what you are talking about, but I'm interested in more then just killing the performance checks, I want to kill the code that it would even check so I have a much better idea of EXACTLY what is going on at all times.
Unfortunately, there is some very extensive code in some of the emissions stuff that doesn't look like it will be very straight forward.
Last edited by 03whitegsr; Apr 25, 2011 at 07:56 PM.
Apr 26, 2011, 09:26 PM
#36
Yeah, the code you are looking at is the performance check stuff just to verify the system is working correctly. Useful for eliminating CELs but only half way there as far as reducing code.
Some of these control bytes will not only stop the performance checks, but can stop the code dealing with the item of interest all together.
For example, you can disable all the EGR performance checks, disable the EGR solenoid (skipping EGR duty cycle and activation subs), and disable any EGR corrections (EGR enabled ignition advance) using 103C and 103D along with FAA Bit.12.
If you don't use all three of these, segments of code can still run that can potentially set other control bit arrays that can feed much deeper into the code. I have not verified that these are the ONLY changes that need to be done to fully disable all EGR items though. There are a couple bit arrays that I still haven't fully tracked down to be sure all EGR code is killed. I'm also using 96530006 which is pretty light on emissions code, there could be A LOT more in some of the other ROMs.
EGR is pretty minimal in code, the purge/EVAP on the other hand is MASSIVE and so far, I've identified at least a few potential control bytes that are related.
Some of these control bytes will not only stop the performance checks, but can stop the code dealing with the item of interest all together.
For example, you can disable all the EGR performance checks, disable the EGR solenoid (skipping EGR duty cycle and activation subs), and disable any EGR corrections (EGR enabled ignition advance) using 103C and 103D along with FAA Bit.12.
If you don't use all three of these, segments of code can still run that can potentially set other control bit arrays that can feed much deeper into the code. I have not verified that these are the ONLY changes that need to be done to fully disable all EGR items though. There are a couple bit arrays that I still haven't fully tracked down to be sure all EGR code is killed. I'm also using 96530006 which is pretty light on emissions code, there could be A LOT more in some of the other ROMs.
EGR is pretty minimal in code, the purge/EVAP on the other hand is MASSIVE and so far, I've identified at least a few potential control bytes that are related.
May 17, 2011, 10:40 PM
#42
From what I can see, there is only like 3 control bytes for idle in 96530006 and they are all disabled from the factory. I don't see any simple way to kill the ISCV stuff. You could try and NOP sections out, but there are a couple other functions mixed in through the main idle sub and the number of variables is extensive so trying to track the impact would be very time consuming.
I just took a quick glance so I could be wrong, but nothing jumped out at me at all as a way to kill it.
I just took a quick glance so I could be wrong, but nothing jumped out at me at all as a way to kill it.
Thread
Thread Starter
Forum
Replies
Last Post
AIK
09+ Ralliart Engine/Turbo/Drivetrain
14
Jan 1, 2011 12:48 PM
