On a closed course

It was a pretty spirited drive out on the of the many twisty and windy roads I have here in the NW fairly close. I just went flat out (you cant really tell whats going on from the log 100%) over this stretch thats basically a loggin road that has been paved: off camber, multi apex corners, multi linked S's, elevation changes, elevation changes with corners happening simultaneously, etc.

Its also a two lane road and today it was kind of foggy. Enough why my drving sucks, but it was interesting where I was seeing knock and when I WASNT seeing knock. The fuel was straight 92 octane Shell, no boost leaks, ambient temps were in the high 30's low 40's, humidity about the same in percentage.

Log:

http://spreadsheets.google.com/ccc?k...-OYaLQPg&hl=en

I am trying to determine why the load was low as it was for the boost though, because the few short straights where I had time the boost gauge was reading the same amount or very close. I am assuming temp and humidity were playing their role in all of this but ... anyway, enjoy.

p.s. the reason behind it was I was testing the Cossie MIVEC map with my S1's to see if my S1 map isnt 100% where I thought it was.

 

JB, is that with evoscan 2.0? I notice g/rev, lbs/min and WHP

 

^^Obviously cant speak for JB but There in evoscan v2.0

 

Nahh thats v99...I added all of that as I was developing it a couple of months ago. Another thing I noticed when I reviewed this log is that I really seem to have a boost creep issue.

 

Maybe, like my car, your car is giving you a hard time for flashing it so much. I couldn't view it - no account, but 92 oct, if a poor quality can give some knock issues and perhaps the dense cool charge under pressure was enough to supress it under other occasions

 

Seriously? How many times have you flashed it?

 

Well here is the deal. I was hitting 27+psi on 92 with 3-4* and holding with 0-1 count and then I would get knock at 6-7psi with 10*? I also wasnt reporting 2byte load over 270 but at the same boost level earlier this year in the heat I was seeing well over 300 on race gas and only a little more timing (7-8*). I am going to switch back to my S1 map and then rerun the course and see what happens.

C6- to answer your question about EGR...I dont have any of the control parameters so I am of no help...sorry.

 

Take a look at the timing map I posted here: (https://www.evolutionm.net/forums/sh...5&postcount=33)

The Cosworths do NOT like much timing at all compared to other cams in the "midrange" of the map.

 

Very true story, especially on 91. My map is in that same thread JustDSM posted as well. I had to reduce my highway cruise 60-100 load range substantially as well, I was getting knock pretty bad with light throttle inputs on the freeway.

 

Just to be clear I am using S1 cams, but I am trying both of the MIVEC maps that I had developed for each specific cam. I have known that my S1 map seems to work better with Cosworths than my Cosworth map. Now it appears that the Cosworth map feels left out and works better with the S1's. I am trying to determine why that is, but on this particular logging session (at least until I got into traffic) I was getting knock when it shouldnt and wasnt knocking when it should have.

 

David (Tephra) generously shared the MUT address for 2 byte load as modified by Baro and temp last night so I went for a drive just to see how much of a difference there was between the raw value (what we have all been calling simply 2 byte load) and modified based on Barometer reading and temperature.

There were some minor issues so I have a kind of messed up log but I will give the highlights rather than post it (since it wouldnt be a bunch of help and confuse more than help likely).

If you looked at the previous log the load was 270ish for 25+psi which of course I thought was really strange. At first I thought maybe my MAP sensor was going away on me but when I took the time to log and watch the boost gauge it was reading the same.

Ambient conditions in BFE, WA this morning: Baro-105% at idle dropping to 101.5 at full pull. Underhood temps with the rain guard in, 38*F.

Sample point 1 (3rd gear)
RPM-5750
Boost-26.1
Raw load-274
Load/B/T-289

Sample point 2 (3rd gear)
RPM-6843
Boost-23.5
Raw load-249
Load/B/T-259

Sample point 3 (4th gear)
RPM-5750
Boost-25.1
Raw load-272
Load/B/T-286

Before there are a whole bunch of questions of how to do this I am going to answer it once. If you are currently logging 2 byte load and would rather see the corrected real value that the ECU is using (I assume on this and will undoubtedly need to be corrected) use the following values:

Instead of 27458/459 use 27464/27465

If you are using the MUT table the values would be instead of 6B42/6B43 use 6B48/6B49

These are for IX's specifically the type 15 rom, but as I recall the values are the same between 13-15 just addresses are different.

Thanks again David.

 

HMM this is very interesting. Now another question for you. Since nothing else is getting changed besides the value in ecuflash. Evoscan will still log this new load under the same 2 byte name?

 

That is correct. If you were to alter your 2byte load in this fashion it will automatically keep everything else in sync such as the WHP calc function if anyone happens to be using it.

 

JB, Any info on other rom ID with this? I have an 03 08 rom and it would be great to log the real load with that too. I can send you my 08 rom if needed

 

Dan,

I dont have one local to play with but I would think that the progression is the same as the IX. So if your 2 byte values are 35164/35165 add 6 to both of them and then log it.