Is there a place someone can point me to for information about what periphery bits to disable for EGR, EVAP, and FPR (maybe...some report minor starting issues)? What is all the rest of the periphery mapping for this ROM (at least what is known to this point)?

I have read a couple (and then a few more...) threads about this...info for this ROM is sketchy at best, at least for periphery bits. I suspect some of the information in the 96940011 ROM patch thread is outdated as well.

An example of this pertaining to EGR/EVAP/FPR specifically would be FAA bit 11 being set to 0 disables an idle function that will cause 3k rpm idles until warmed up...my stock ROM image has this set to 0 as standard and idles fine. Maybe I just am not understading some other facets here?

The reason I am interested in getting rid of the EGR/EVAP/FPR is clean up the engine compartment (death to clutter!) and by getting rid of the EVAP equipment, this frees up the space in the rear fender to mount the ACD pump where the rest-of-world cars have it mounted (more on that in it's own thread later...).

I am really trying to catch up, but I think I need a little help. Free for your educational nudges.

 

FAA bit11 disables the EGR ignition advance adder table. Advance only occurs at low load and rpm. (enter "1")

FCA bit9 disables the EGR OBD test. Has nothing to do with engine performance. (enter "0")

FEA bit7 disables the fuel pressure OBD test. Again, this should have nothing to do with engine performance. (enter "0")

also check here... http://evoecu.logic.net/wiki/Periphery_Configuration

 

So the periphery mapping is the same for all the ROMs? So I want to enable the EGR ign. adv. adder table? Why is it disabled in original form?

edit: after reading the description of FAA bit 11 in the Wiki, it lists it as EGR ign. adv. disable. Putting a 1 in that bit disables the ign. adv. See, even crusty old guys like me can learn

So is the 02 heater patch that is published for other ROMS good for this one as well? I think the patch I found is good for 96940011, but I've read so much in the last couple of days, I am getting fuzzed up.

 

OBTW: free beer for Fast Freddie!

 

Set FCA to 0x0001, then do the force OBD2 pass and all the problems related to any of the nonsensical EGR/EVAP, P0300, fuel pressure solenoid, etc. will be gone.

 

Free to Mr. Bradley.

In what I have been reading, the only consequence to getting rid of the FP solenoid is some minor hard starting in cold weather?

 

Is FAA BIT 11 the one that disables retarded timing for cat lite off?

 

It will change the hex version (I deal in Hex generally) from 0x56xx to 0x54xx, so whatever one that is.

 

Well I tried the change FCA to 0X0001 and then pulled the connectors on a couple of solenoids...no CELs. Hurrah! I'll start decluttering when my EGR block-off plate shows up this week.

What I did notice is going to be a pain in the state of Missouri with their new centrally located OBD-II testing database. The system keeps track of your pass/fails and supported/non-supporteds from one inspection to the other, compares them, and then puts up a red flag if any major deviations are present...in addition to normal functional testing. Sneaky, sneaky! Dern staties must be reading our threads.

I went in to Scan-Tech before and made note that heated cat, A/C refrigerant, and air injection were not supported before changing FCA (P2) to 0x0001. After changing, everything was shown as supported...Grrrrr! This is even with going in to the OBD-II pass/Fail patch and setting the offending items to unsupported in the bit level menus.

Any ideas? Do I just need to go in to each Periphery and set the offending codes and processes for Evap, EGR, and FPR to 0 (or 1 for disable routines) individually? Anyone else notice this?

 

Anyone? I'm sure it's somethnig I did/did not do, but I'm just not seeing it.

 

I will look into it later tonight. I hadnt noticed it doing anything like that when I have switched them over...interesting.

 

Did you ever get a chance to look in to this??...not that I'm going to be home much this month to play with it. Dern job!

 

https://www.evolutionm.net/forums/ec...us-mrfred.html

 

fostytou:

That is the patch I applied. The results of setting FCA to 0x0001 vs. the patch's efficacy with this ROM ID are in post #9. It seems setting FCA to 0x0001 overrides the patch for either reasons of user error or a quirk with this ROM...and that is over my head, at the moment. Hence my iquiry for assistnce.

Or is there something in that thread addressing this problem I have overlooked?