disable nearly all OBD tests
#1
disable nearly all OBD tests
Turns out that there is a 1D table that overrides the periphery settings in P2 FCA and P3 FDA and sets all these bits equal to zero. This would disable nearly all of the OBD-II tests, however, I'm not sure if it will kill off all associated CELs. Would be interesting to try on a car with none of the OBD CEL kill tricks.
<table name="Disable/Allow P2_FCA, P3_FDA Bits" category="Periphery" address="101C" type="1D" level="2" scaling="uint8"/>
<table name="Disable/Allow P2_FCA, P3_FDA Bits" category="Periphery" address="101C" type="1D" level="2" scaling="uint8"/>
#2
Evolving Member
iTrader: (2)
Join Date: Jan 2008
Location: bucks county p.a
Posts: 310
Likes: 0
Received 0 Likes
on
0 Posts
I dont have any mods to my rom and have a CEL for the rear o2 being out and replaced with a wideband. will this work with rom 94170008? Also is there any bad effects that will come along with it?
#3
Evolved Member
hey i have a bunch of cels and i only disabled the rear o2 and the things to aid with cold start up. but i still have a few more cels would you like for me to still try?
#4
Evolving Member
iTrader: (2)
Join Date: Jan 2008
Location: bucks county p.a
Posts: 310
Likes: 0
Received 0 Likes
on
0 Posts
ok i tried the patch and it worked for all but the p0141 o2 sensor heater, which i havent done the resistor mod yet so i was thinking that was gonna happen. Thankks for all the hard work once again.
#6
mrfred: I mentioned 101c over here (and as usual, acamus was there long before us) when I was working my way through the periphery ROM-to-RAM copying routine; there's a whole bunch of items just past 0x1000 that control a variety of periphery bits.
Trending Topics
#8
Evolved Member
iTrader: (2)
I never bothered running through any tests of it, since the code seemed pretty clear, albeit somewhat odd; it seemed really weird to have multiple places to enable/disable those, especially the individual FCA toggles from 101D-1025. I think this is one of those places where it would be a lot more obvious if we had the original C source sitting in front of us with comments (and a window with Google Translate running in it ).
(At this point, I can't actually test much of anything either, which is why I've been so quiet lately; the recent cold weather caused some damage to the Evo that I haven't wanted to investigate both because of the cold and because I'm afraid of what I'll find. I have this sinking suspicion that I may have our 1g up and running with an IX ECU before I have the Evo running properly again...)
(At this point, I can't actually test much of anything either, which is why I've been so quiet lately; the recent cold weather caused some damage to the Evo that I haven't wanted to investigate both because of the cold and because I'm afraid of what I'll find. I have this sinking suspicion that I may have our 1g up and running with an IX ECU before I have the Evo running properly again...)
#9
Evolving Member
Join Date: Apr 2008
Location: Reading, PA
Posts: 265
Likes: 0
Received 0 Likes
on
0 Posts
Anyone who tried this patch, do you still have normal MUT and OBD2 communications?
Setting Periphery2 bit 0 = 0, looks like it will lock out 15625 and 10400 baud selection under certain conditions.
Unless I am looking at things wrong.
Edit :
Periphery2 bit 0 = 0, looks like it could mess with the Front O2 Sensor Switch Point, also.
Maybe some else could look at Periphery2 bit 0?
Setting Periphery2 bit 0 = 0, looks like it will lock out 15625 and 10400 baud selection under certain conditions.
Unless I am looking at things wrong.
Edit :
Periphery2 bit 0 = 0, looks like it could mess with the Front O2 Sensor Switch Point, also.
Maybe some else could look at Periphery2 bit 0?
Last edited by Ceddy; Dec 18, 2009 at 09:16 PM.
#10
Account Disabled
iTrader: (3)
Join Date: Jun 2009
Location: central pa
Posts: 312
Likes: 0
Received 0 Likes
on
0 Posts
Looks good Mrfred, I assume the xml works for all the popular rom ID's? When I finally get my CEL throwing evo ecu'd DSM up and running next weekend I'll give this a shot. Also I assume I would change the table to all 0's?
#11
I never bothered running through any tests of it, since the code seemed pretty clear, albeit somewhat odd; it seemed really weird to have multiple places to enable/disable those, especially the individual FCA toggles from 101D-1025. I think this is one of those places where it would be a lot more obvious if we had the original C source sitting in front of us with comments (and a window with Google Translate running in it ).
(At this point, I can't actually test much of anything either, which is why I've been so quiet lately; the recent cold weather caused some damage to the Evo that I haven't wanted to investigate both because of the cold and because I'm afraid of what I'll find. I have this sinking suspicion that I may have our 1g up and running with an IX ECU before I have the Evo running properly again...)
(At this point, I can't actually test much of anything either, which is why I've been so quiet lately; the recent cold weather caused some damage to the Evo that I haven't wanted to investigate both because of the cold and because I'm afraid of what I'll find. I have this sinking suspicion that I may have our 1g up and running with an IX ECU before I have the Evo running properly again...)
Sounds like you think you froze the coolant and cracked the block. Bummer if that's true.
Yes, it should work for all ROMs. No need to change any bits in FCA or FDA. This bit overrides anything in those periphery bit locations.
Last edited by mrfred; Dec 19, 2009 at 06:41 AM.
#12
EvoM Community Team
iTrader: (15)
Just for reference, trying to get the un-blocked OBD tests:
P0069: ??
P0111: IAT sensor input range
P0554: Power steering pressure sensor
P1530: AC pressure or ignition timing or cam sensor
P0830: ??
P0090: ??
MrFred, does this just block the OBDII tests or does it also have the other effects of changing the peripheries (ie, the cruise timing change for the EVAP bits)?
This is a nice quick solution, but unfortunately it doesn't allow for some tests that we might actually want (I know, hard to believe ). I'm definitely going to use it instead of peripheries if it does not change the actual function of the ECU and only prevents DTC.
P0069: ??
P0111: IAT sensor input range
P0554: Power steering pressure sensor
P1530: AC pressure or ignition timing or cam sensor
P0830: ??
P0090: ??
MrFred, does this just block the OBDII tests or does it also have the other effects of changing the peripheries (ie, the cruise timing change for the EVAP bits)?
This is a nice quick solution, but unfortunately it doesn't allow for some tests that we might actually want (I know, hard to believe ). I'm definitely going to use it instead of peripheries if it does not change the actual function of the ECU and only prevents DTC.
#13
Just for reference, trying to get the un-blocked OBD tests:
P0069: ??
P0111: IAT sensor input range
P0554: Power steering pressure sensor
P1530: AC pressure or ignition timing or cam sensor
P0830: ??
P0090: ??
MrFred, does this just block the OBDII tests or does it also have the other effects of changing the peripheries (ie, the cruise timing change for the EVAP bits)?
This is a nice quick solution, but unfortunately it doesn't allow for some tests that we might actually want (I know, hard to believe ). I'm definitely going to use it instead of peripheries if it does not change the actual function of the ECU and only prevents DTC.
P0069: ??
P0111: IAT sensor input range
P0554: Power steering pressure sensor
P1530: AC pressure or ignition timing or cam sensor
P0830: ??
P0090: ??
MrFred, does this just block the OBDII tests or does it also have the other effects of changing the peripheries (ie, the cruise timing change for the EVAP bits)?
This is a nice quick solution, but unfortunately it doesn't allow for some tests that we might actually want (I know, hard to believe ). I'm definitely going to use it instead of peripheries if it does not change the actual function of the ECU and only prevents DTC.
#14
Evolving Member
iTrader: (2)
Join Date: Jan 2008
Location: bucks county p.a
Posts: 310
Likes: 0
Received 0 Likes
on
0 Posts
Anyone who tried this patch, do you still have normal MUT and OBD2 communications?
Setting Periphery2 bit 0 = 0, looks like it will lock out 15625 and 10400 baud selection under certain conditions.
Unless I am looking at things wrong.
Edit :
Periphery2 bit 0 = 0, looks like it could mess with the Front O2 Sensor Switch Point, also.
Maybe some else could look at Periphery2 bit 0?
Setting Periphery2 bit 0 = 0, looks like it will lock out 15625 and 10400 baud selection under certain conditions.
Unless I am looking at things wrong.
Edit :
Periphery2 bit 0 = 0, looks like it could mess with the Front O2 Sensor Switch Point, also.
Maybe some else could look at Periphery2 bit 0?