Actually it looks like evoscan is off by 500 rpm. The timing curve follows exactly as if it were 500 rpm lower. Check it out.

 

I'll log 1byte load and check back in with results. If that puts me in the 330-340 load column it would line up pretty accurately with what I'm getting for timing in my logs.👍

 

Man I asked you which load you are logging. So you were looking at the wrong load on the tracer. It will line up now.

 

I think it's something with the rpm because even at lower load it's off by 500 rpm. Maybe try 1 byte rpm.

 

Sorry, I must have overlooked that. I have been logging only kpa load since switching over to SD because that is what was suggested to me from an old friend, but he did not explain that I would also need to log load1byte.

 

I will try that also while logging load1byte today on my way home from work. I took the car to work today along with my laptop to get some logs. I'll update with results in a few hours.

 

https://www.evolutionm.net/forums/ec...ems-fixes.html

Looks like certain versions of evoscan have the wrong 2byte formulas.

 

I have not used 2 byte rpm on the car or have it set up. I'm logging "Engine RPM".

 

What baud rate are you running in evoscan?

 

I would data log and run the rpm up to 5k and hold it there watching your tach and keep it steady, then compare it to you logs. Just to verify the rpm is correct in evoscan

 

This is amazing feedback fellas.

 

Baud rate is 15625

 

Well I wish I could be reporting back with some results after logging 1byte load, but before I got the chance to do any logs I was left stranded in the car on my way back from work. Fortunately it was only about a mile away from home.
My crank pulley decided to extract itself from the car and sheared off one of the bolts in the process. Unbelievable.
Want to thank a few of you guys for all the input, and hopefully i can get the crank pulley issue sorted quickly so that I can get back with results.

 

Fuel?

 

Fuel is 93.…