Thanks Aaron for chiming in!

I haven't touched or read anything about changing the dwell settings, yet. I'm running Spoolin Up COP.

I changed the plugs today and realized I was already at .020" gap. So the new set was set at .019" and the stutter is gone. I could have probably done .020".

I guess I put all my eggs in 1 basket for tuning the timing. I used this as a guide for timing: https://www.evolutionm.net/forums/6874325-post94.html
I should have researched more and used what is called for in a lot of the guides (start low and add timing until MBT). It was just such a nice chart to get some numbers from. I did take it out of context as he says that every Evo is different.

 

Yeah when Bryan posted that a few years ago it was with the curve. When we talk peak we almost always mean near redline. You can see it in his curve to an extent what he is talking about.

Here is a log to show kind of what to expect, albeit this is rather over the top example-

https://www.evolutionm.net/forums/ec...ne-800whp.html

 

That makes more sense. After reading his post again I see he's referencing peak timing closer to redline. I assumed it meant across the RPM range.

Do you also believe VIII can take about 4* more up top on a 8 or 9 turbo?

I don't know how I missed your thread on how to tune 800 whp. That helps a lot!!! Thanks

 

I was almost unclear in that last post as well.

There is Peak Timing which is the max it is, not to be confused with timing at peak which really refers to peak torque but often gets shorthanded down to peak.

I dont believe it can take anymore timing. Maybe if it was stock cams or something or the turbo was falling off REALLY bad, but turbo to turbo I see them routinely stop making power at 18-19* just like the IX.

 

That's a good point about peak. I asked this question awhile back, but didn't get a clear answer. Should we have the lowest timing at peak load or peak torque? I'm assuming peak load. My peak torque is sometimes 1000 RPM's later than my peak load. From your logs it looks like the lowest timing is before peak load. I know experience has a lot to do with tuning. I guess it's not quite as simple as I was hoping for.

 

Peak load usually lowest timing. Maybe it depends on tq control.

Tq usually follows the peak load by some margin, virtual dyno tends to round peak tq into a hump where the real dyno will peak a little more sharply

Between vd and stms mustang I saw some tq difference but hp was spot on. I made more torque on the dyno. Then again that was vd almost a year a go

 

I kept timing low for traction control as Dubstar said, in that thread I talk about it a little. This moved my peak torque 1500 rpm higher than it could have been but it also keeps the bearings and headgasket happy.

 

rats & 10isace, Can you guys teach me this detail above. I have reread this thread a few times, and wonder if my cruise knock and troubleshooting sometimes shows me modifying cells in the wrong column. That had me thinking my load was off. However I don't know where or how to check, and don't understand the comment above.

I use Load MUT 2byte Mod. I think its because of the reading that I did this was the most accurate, but I could be wrong. This goes back a bit for me.

Here is my evoscan choices for load.


Considering the above and that I want to confirm I am using load columns in my tables appropriate what should I be doing to confirm everything is set correctly.

 

They are talking about Load 1Byte, the row above what you have selected. In your log posted above you are using Load 1Byte. Change that eval. and in the ECU you need to change "2byte to 1byte Load Factor" under the "Miscellaneous Tephra Mods" column to 1.5

edit: I didn't realize you were not the OP

 

Yup, I got that part, but was wondering in general what I should be using, or how to confirm that my load scaling between ecuflash and evoscan need to be reviewed/corrected to eliminate any possible error there that is confusing my other tuning troubleshooting.

 

Fireroasted, did you read this page https://www.evolutionm.net/forums/ec...-vs-log-3.html?

Log load with
2 byte load MUT 00 = 6B42
MUT 01 = 6B43
2 byte RPM MUT 02 = 6B1E
MUT 03 = 6b1F

These are the addresses for Rom 8859

See if there is a discrepancy with the load readings.

 

Yeah, I read that a bunch of times, and the one that spins out of that one.
https://www.evolutionm.net/forums/ec...ng-values.html

I see the similar comments about using 1 byte and adjusting the scaling to 1.5. Since I don't use 1 byte, I never paid much attention. So I think I just don't understand some basics and why I keep getting lost in these threads about 1 and 2 byte stuff. I wanna get it, but if this question needs it own newb post just tell me, I won't be offended.

This is my MUT table, so the first values are as you noted for 2 byte load. So what two items am I logging to compare logged load values for a discrepancy? Sorry if this is really fundamental stuff I should already know. Just filling in some knowledge gaps I guess.

 

No problem. I've been helped so many times on this forum that it's nice to give back.

I didn't realize you weren't using 1byte load. You can use 1 byte and 2 byte load to see if there is a discrepancy. I see in your evoscan that it shows 1.2 for your 1 byte load. Change that to 1.5 and change it on your rom to 1.5. Then log both 1 byte and 2 byte load. 2 byte is taking info from 2 different addresses and with a formula creating a load #. 1 byte is getting it from one address.

From your logs/tracer it looks like you're reading 1 column to high. Eg. You're reading 240 and you should be in 230 load. I'd have to look closer later tonight. I'm headed to the gym.

 

OK thanks. I will log that tomorrow. Tonight I couldn't get time,as I also have the upgrade you have in your sig. The Britax special. I owe several responses to other threads folks are helping me on my cruise knock.

I am embarrassed to ask but where in my rom or how do I modify the 1byte value like I do in EvoScan? the 1.2 to 1.5. it must be so obvious I am missing it.

 

2 byte to 1 byte conversion factor. It's actually a hardwired 2 byte formula that is divided by the factor you set then logged and multiplied by the factor in your evoscan. It's not technically a one byte load. That's why they need to be the same number