RomRaider

I have a 2006 Subaru legacy 2.5i and I put uel’s on it. Recently I’ve been getting a p0137 as a nuisance code, I don’t have any exhausts leaks. I disabled the code in rr and it still returns. Is there something I’m doing wrong? It also has a one of those 90 degree spacers/defoulers to “get rid of CELs” but would that cause the sensor is not reading enough exhaust gas. The sensor is new

disabling the code should do the trick, but it might be there's another table to set the conditions for low/high voltage on the sensor. if you have them available the rear o2 fuel trims should be zeroed out then try with the codes off and sensor unplugged.

I have a rare ecu, E2VL001B, the only ecu defs i could find for it were on github and was based off the defs of different ecu but same model subaru. sadly it only has the definitions for the basic options, none of the alpha ones. I tried to get into ida to solve this myself but i couldn't figure it out

maybe try switching to E2VG221B :
https://romraider.com/forum/viewtopic.php?f=8&t=11230&p=105764#p105764

Not really sure how to go about this because that forum only talked about going from e2vg221b to my ecu id. i tried to see if romraider would read my rom with ev2g221b defs and it couldn't. would i have to reprogram the ecu back to e2vg221b? how does this all work with ecuflash?

so when early cars left the factory they had E2VG211B on them, which would have been updated by subaru to E2VG221B, then E2VG231B and finally E2VL001B. Probably due to recalls for something or other or an attempt to help with any warranty claims. You'd have to compare the files thoroughly to see the specific differences, which isn't gonna be much of an option if you dont have complete defs for each.

What I'm suggesting is take any changes you've made to your tune and place them into a stock E2VG221B rom, save that rom and flash it to your ECU (all the blocks will be overwritten instead of the usual 1 or 2 blocks for little changes to the map). Then see if that helps with your fault codes issue.

I loaded the E2VG221B stock rom into romraider with the E2VG221B defs that have addresses and codes for everything, even alpha tables, but it still doesn't show any of the alpha files in romraider. im at the highest user level too

EDIT: E2VG221B actually also doesn't an alpha codes or addresses

I have a 2006 outback 2.5i auto NA/T I've been working on defining the ECU. It has the E2VL001B ecu in it. I have pretty many tables working, CEL checks, and some basic logger deffs.

I also have working basic tables and CEL checks. The issue is is that no one has gone through ida to get the alpha defs, which one is the rear o2 sensor scaling, and I have figured out that certain CELs even when checked off will trigger a CEL if the sensor isn’t zeroed out in scaling and unplugged so it consistently reads 0 volts as normal. If you have the ability to pull the addresses for alpha tables then you will be an answered prayer

I'm not sure what "alpha" tables and deffs are but this project I've been working on does not have cats or rear O2 and no check engine lights.
I disabled pretty much everything for secondary O2
(P0038) REAR O2 SENSOR HIGH INPUT
(P0138) REAR O2 SENSOR HIGH VOLTAGE
(P0139) REAR O2 SENSOR SLOW RESPONSE
(P0037) REAR O2 SENSOR LOW INPUT
(P0137) REAR O2 SENSOR LOW VOLTAGE
(P0140) REAR O2 SENSOR NO ACTIVITY
(P0420) CAT EFFICIENCY BELOW THRESHOLD
(P2097) POST CATALYST TOO RICH B1
(P2096) POST CATALYST TOO LEAN B1

I’ve also disabled all these and still get a code even with it unplugged. Alpha tables are advanced tuning tables that most definitions for ecu’s don’t have addresses for because must people who dont have turbo Subaru’s don’t need so no one has bothered trying to get them for n/a ecu’s. Why the rear o2 sensor scaling is an alpha table and the front isn’t is beyond me. I wish the overrun fuel cut delay table wasn’t alpha either because I want a bit more pop in my exhaust. If you want to view all the available alpha tables load your rom into ecuflash and scroll down until you see a bunch of groups titled ALPHA and then stuff like brz, idle control, AF 3, overrun fueling, etc. you won’t have tables for these but they’ll still appear

Interesting, I haven't had to adjust any of the alpha tables for the E2VG221D or the E2VL001B that I put a turbo on and tuned. All I did on those was disabled them.

If you post up your ecu .BIN file I can look at it and see if something is off.

If your using the "E2vl001b def" file from Cbast that one didn't work for me either. The O2 addresses are off in that deff so it doesn't actually turn off that code. I made it a project to use Ghidra to find what I needed from scratch.

Here is the current rom on my car, i linked the defs too because i dont think any of my changes show up on your def for e2vl001b

I checked the deffs you attached and compared them to mine, they are the same at least for the rear O2 codes. I opened up your ecu file in Ghidra and compared it to the ecu file I've been working on and they are the same as well. I did notice that the rear O2 codes were still active and some front 02 codes are deactivated in ecu flash. If you want to try this attached file you can its just your file and I turned the codes off. If it doesn't work them maybe for some reason yours needs zeroed out. I can put it on the list of things I'm looking for, it might take some time.

EDIT:

I dug into it a little more, and I found that the starting code for your CEL is different than mine. Yours is "0008e438 00 35" mine is "0008e438 03 35" for P0335. It messes every thing up when running the CEL tool in Ghidra. I changed it to match mine and it then maps out you CEL codes correctly. My understanding is that needs to be "03 35" in any ecu, I have absolutely no idea how something like that would get changed but possibly that is messing up things?

I also attached a copy of my base ecu file from my car with O2 codes turned off, if you want to load it up.