Surely, I will change it.

Thanks, the problem is... time. Glad to help for EDM, when needed

 

Now that I think about it, its interesting that these tables exist in the EDM ROM. I thought that there was no EGR system on EDM Evos. Makes me wonder if the tables and code are in-place, but deactivated.

 

Tables are referenced, I should walk thru the code to see if the subroutine is called or not.

I was thinking to log EGR duty in evoscan, maybe this WE. I *think* these tables are used, since modifying the Hi Oct timing one the ECU add timing during cruise (tried a couple of months ago)...

 

Any chance anyone out there has the "BE" tables defined for 96530006?

 

One thing that is really confusing about these tables is the fact that we *know* it adds timing for the slower burn rate of the EG. Makes sense... but why do the correlations between the advance and duty cycle tables seem to suggest that the higher the EGR duty cycle, the lower the advance (other than the zeroed portions)?

I know they may not directly correlate, and you have to factor in the base timing tables they are working off of as well... but it does add a bit of confusion to the mix.

 

I am going to make a post later tonight with logs, but to add even more confusion to this is that we thought the EGR shut off when the car went to open loop.

I verified that it does in fact continue to add timing in open loop out of boost for sure, and I havent verified under boost again.

 

wouldn't having it open under boost just cause intake charge to vent out the exhuast and prevent any exhaust from actually being sent into the cylinder?

 

Maybe the Map is also used as vacuum advance with the valve shut. Something is advancing timing in a cruise- off boost condition. And it maches the values of HOtiming + timing in the EGR advance 2 table.

 

Yes. If you pull the vac line off the EGR during a boost leak test you can verify this.

 

I guess in looking at what I posted I didnt say what I meant.

The EGR closes in open loop (like you said it would be a boost leak if it didnt).

However I have the open loop tables all zero'd 100% and the car continued to add timing in even though we had thought it was solely used by the EGR. At least in vacuum this is not the case as it would have to be closed (as established) but the "dynamic advance" continues to function.

I was testing the lean misfire limit of E85.

Apparently 47* of timing at 68% load with 17.5 AFR is enough to do it. Drop the timing a few degrees and it didnt do it. Conversely, richen it 17:1 and it was okay as well.

I have 40* of timing in my timing map and then 7* cranked in on the EGR map. I had assumed it wouldnt be adding anything in since I had gone to 100% open loop to make the 1600s work a little easier but as I datalogged there was the extra 7* at cruise.

aaron

 

Did anyone find other EGR related maps for 97140008 yet?

It seems if I change EGR duty cycle values of those two found maps, I also have to change the EGR related ignition advance values at those changed EGR duty cycle values?

I would like to minimize EGR activity at 70~80 load and higher rpms so that I may get less intake manifold pollution while I can pass simple emission test at idle without remapping.

Thank you for the findings, and I hope someone can help finding other EGR related maps. Thanks!!!

 

But this configuration bit could do it ->

--------------------------------------------
Bit position definitions (FAA) (15-0, L-R)
--------------------------------------------
56DA = 0101011011011010
0: Unknown
1: Rear O2
2: PEDR Pin14
3: Immobilizer
4: PJR4
5: Unknown
6: Front O2
7: Knock Sensor
8: Unknown
9: Unknown
10: Unknown
11: Unknown
12: EGR Solenoid <----------------------------------------------
13: Unknown
14: Unknown
15: Unknown
00000FAA .data.w h'56DA
00000FAC .data.w h'56DA
00000FAE .data.w h'56DA
00000FB0 .data.w h'56DA
00000FB2 .data.w h'56DA
00000FB4 .data.w h'56DA
00000FB6 .data.w h'56DA
00000FB8 .data.w h'56D2

00022DB4 mov.w @(h'76,pc), r13 ;h'80
00022DB6 mov.l @(h'C8,pc), r0 ; MUT_D1_RAM_Periphery_0
00022DB8 mov.w @r0, r0
00022DBA shlr8 r0
00022DBC tst #8, r0
00022DBE bf 22E20 ; exit without using EGRDuty vs RPM lookup
00022DC0 mov.l @(h'C4,pc), r1 ; EGR_Duty_Table; (empty)

 

Fostytou - you mentioned EGR duty and its relationship to the timing. You have to consider that 100% duty does not mean 100% flow. At low load the solenoid is opened very little because there is alot more vacuum available to open the valve. As load increases and vacuum decreases the solenoid must be opened more to compensate for this. The amount of timing required can be found quite easily on an eddy current style dyno if you have access to an NOx probe.

 

Sorry to bring up an old thread that's not a real issue. I just had some xml code lying around that needed addresses for this so I tried to hunt down some addresses.

Can somebody skilled in dissassembly verify these addresses if they have a free miunte?

Visually, the tables match what is in this thread, but I pretty much just hunted around until I found something that looked right.

94170015

High Octane EGR Enabled Advance = 3e6d
load = 66f4
RPM = 66c2

Low Octane EGR Enabled Advance = 3ce5
load = 66f4
RPM = 66c2

Base EGR Duty Cycle = 46c9
Load = 6a4a
RPM = 6aca

Secondary EGR Duty Cycle = 4743
Load = 6a4a
RPM = 6aca

Normalization for Coolant Temp = 47b8
engine temp=67a2

EGR Duty (alternate) = 47c6
RPM= 635a