Time pulled without apparent reason...
Time pulled without apparent reason...
I'm trying to understand why my ECU is pulling time with (apparently) no reason.
Car is an IX EDM 88840016, runs with 100 RON (95 US???).
The timing map of the log is this:

(note: actual is a little smoother, but basically the same).
With this map, copied on all 3 timings map, I logged this:

As you see the ECU set 0°/1° at 3500 RPM with a load between 260 and 280, but my timing map is not like this!
There is no knock, all maps are the same (high octane), so no time should be pulled. Why do I get 0° and a 4° degrees step just after?
Car is an IX EDM 88840016, runs with 100 RON (95 US???).
The timing map of the log is this:

(note: actual is a little smoother, but basically the same).
With this map, copied on all 3 timings map, I logged this:

As you see the ECU set 0°/1° at 3500 RPM with a load between 260 and 280, but my timing map is not like this!
There is no knock, all maps are the same (high octane), so no time should be pulled. Why do I get 0° and a 4° degrees step just after?
I'm sure too that other factors affect time, but I'm trying to find what... For example, ACD in gravel mode seems to pull more timing (I get -4° instead of 0°), like reported here.
IAT wasn't very hot, in this season we get 5-6°C and I was not driving for hours. And from previous log it did not knock in that range...
I don't think that 88840016 high octane map (#1 or #3) definition is wrong, they seems very coherent.
IAT wasn't very hot, in this season we get 5-6°C and I was not driving for hours. And from previous log it did not knock in that range...
I don't think that 88840016 high octane map (#1 or #3) definition is wrong, they seems very coherent.
Trending Topics
Account Disabled
iTrader: (38)
Joined: Aug 2005
Posts: 9,319
Likes: 1
From: Virginia Beach, Virginia
I guess it's possible it's going into the low octane maps for some reason, if you're okay with the risk you could try matching the high to low octane in the affected area and see if you can keep it from pulling there. Obviously you would need to keep an eye on knock.
also, was the engine fully warmed up when you did the pull?
also, was the engine fully warmed up when you did the pull?
I guess it's possible it's going into the low octane maps for some reason, if you're okay with the risk you could try matching the high to low octane in the affected area and see if you can keep it from pulling there. Obviously you would need to keep an eye on knock.
also, was the engine fully warmed up when you did the pull?
also, was the engine fully warmed up when you did the pull?
I could try to "cheat" the low octane maps since I usually use 100 RON. But which are the reasons for low octane map?
1) knock > 3 to start interpolation
2) ... ?
Account Disabled
iTrader: (38)
Joined: Aug 2005
Posts: 9,319
Likes: 1
From: Virginia Beach, Virginia
I'm not exactly sure where it starts but you're likely close, then again even a 1 count will get 1* pulled sometimes.
with locked low/high octane maps it's still going to pull timing, it just won't be as aggressive about it.
do you have a CEL?
with locked low/high octane maps it's still going to pull timing, it just won't be as aggressive about it.
do you have a CEL?
I believe it was confirmed that very significant MIVEC advance will pull 1 degree, because I experience this a lot in my 30 cell MIVEC map.
Try for the hell of it lowering MIVEC to 20 and re-log
Try for the hell of it lowering MIVEC to 20 and re-log
I don't think this is your problem, but just for an FYI. Intake temps and coolant temps will pull certain amounts of timing without the presence of knock. I don't think it was verified on the EVO ECU yet, but the DSM ECU did this. I forgot if there was a lower limit on the values, but I do remember that there was an upper limit. And there were a few limits, meaning that if the temps were at temp x and above, then 1 degree was pulled, temp y and above, then 2 degrees were pulled.



