End of Injection Timing Open Discussion

[Terminal_Crazy]

NOTE:
========
Kur4o: Appolgies, I could have pm'd you but if you're like me, I don't seem to get notifications of mail.

I'd like to bring to everyone's attention that I've seen the freaky injection PW issue again.
I used to reflash with EEHack 4.70.
On several occasions I've flashed with Kur4o's version 4.92 (December) and earlier versions.
I reflashed recently and have seen the differing PW issue again. Reflashed with 4.7 and it's gone away.
The car ran fine so I think it's a logging or reporting issue rather than a PCM issue and the log shows the issue when viewed in either version.

On suspiscion of this issue I've rechecked my EOIT timing test and the issue is showing up on that log.

On the two attached images you can see the differences on the IPW

I feel this invalidates my test. Has anyone reproduced or seen this?

I've replaced the PCM and reflashed with EEHack 4.70 without issue.

Mitch

[Stroked 388]

I have had some time to mess with eiot in eehack. Before I was getting the big cam problems strong fuel smell showing lean when you can tell it wasn't ect. So adjusting my eoit down 5* at a time I noticed my AFR going more rich so i kept repeating the steps till I seen no change in the AFR. now it shows it is rich and removing fuel witch the wideband conferms that it is rich. I ended up at 146 on the eoit. Less fuel smell and better response. Now my ve table is not that great it's red all over in the cells in the analyzer. Very happy with the outcome so far just need more tuning

[spfautsch]

Thanks for reporting your results! Assuming you were going by the eehack slider values in degrees, 146 would be a value of 0x1a in the table?

I'm curious to see what develops as you start to remap your VE table.

[Stroked 388]

Thanks for reporting your results! Assuming you were going by the eehack slider values in degrees, 146 would be a value of 0x1a in the table?

I'm curious to see what develops as you start to remap your VE table.

Yes that should be correct but I will check on that number and post it. Yes the ve tables should be fun lol

[Mr.owl]

I'm currently working on my tune trying to basically do the same thing you just did and god am i lost. I'm running a 60123 from lunati worked out my eoit needs to be right around that same 146 area but i know nothing about hex like at all. I'm using eextrav0[1].001[mod_v0005_03_02]v6_1.xdf or so it says. What in the world do i enter? Any help?

[Stroked 388]

I'm no good with hex. I don't think u have to change anything in hex if you changed the eoit you should be good to go. Have you tried ve turning after you set the eiot ? What is your AFR running now ?

[JimCT_9C1]

I believe the EOIT table in the xdf shows degrees after TDC of the prior compression stroke.
If you right click on the table header you can see the hex which is in terms of 90 degree pulses before TDC of the upcoming compression stroke.

For my stock B-body the hex value is $50, and the displayed value is 270.
The hex converts to 450 degrees (5*90 + 0*5.625) before TDC of the upcoming compression stroke.
This is equivalent to 270 degrees (720-450) after TDC of the the prior compression stroke.

Hope this helps, and others please correct me if I've missed something.

Jim

[Mr.owl]

I'm no good with hex. I don't think u have to change anything in hex if you changed the eoit you should be good to go. Have you tried ve turning after you set the eiot ? What is your AFR running now ?

For some reason it would only take if i entered in hex value so mine shows 60 stock I'm at 66 now and in calc view i see 146 now instead of 180 that i had at 60. My afris pretty much useless as a reference currently because i didn't log my last run to see how much it was pulling but seemed to hang around my target 14.3 at idle (e10) and 15.6 cruise but again no way of knowing whst it was doing there. I'll be flashing my base ve table on and taking it from 157 to 146 this weekend