Evoscan Ceddy logging

[u2civic1]

I've currently using Evoscan with Ceddy's xml settings and I was wondering which items should I log when tuning, there alot of items I don't understand like 2byte Load IAT Baro Comp, AirFlow Calc gm/s lb/min, CPU loop time etc. Can anyone help me out and explain some of these things

 

[tallywacker]

http://tinyurl.com/ybygynu

 

[davidalindsey]

Let me google that for you

HAHA, I never seen that before.
You made it to easy

 

[jeff24680]

Let me google that for you

Baaaahhhaaha.


Priceless

 

[davidalindsey]

On a more serious note, If you are just starting out with EVOscan/Ceddy's mod and have not read or searched the forums then you have to read all of this thread:
First Flashed DSM ECU! (98/99 Flashing FAQ), I have it booked marked.
You also need to visit ceddy's website at Ceddy's Lair
Read, watch videos, re-read, ask question if you dont understand.

 

[u2civic1]

I understand how to tune using the fuel maps, and timing maps using 2byte load, knock sum, timing, injector duty but what I didn't understand is the extra setting ceddy put in to his evoscan settings like byte Load IAT Baro Comp, AirFlow Calc gm/s lb/min, CPU loop time is any of these things important or is it more for speed density or other stuff ceddy is working on.

 

[Ceddy]

I understand how to tune using the fuel maps, and timing maps using 2byte load, knock sum, timing, injector duty but what I didn't understand is the extra setting ceddy put in to his evoscan settings like byte Load IAT Baro Comp, AirFlow Calc gm/s lb/min, CPU loop time is any of these things important or is it more for speed density or other stuff ceddy is working on.

There are a lot of good how-tos on the evom/ecuflash forums.

2Byte Load
2Byte Load Baro Comp
2Byte Load IAT Comp
2Byte Load IAT&Baro Comp

Normal you will just use Load, but the ecu uses Compensated Loads for some things, this is because colder air is more dense, etc.

AirFlow Calc -> log airflow in lb/min or g/sec, useful for plotting turbo compressor maps. Or as rough horsepower estimate, lb/min x 10 = ~HP.

CPU Loop Time is the ecus time to run the complete code. Usually it does this about 100 times per second, so fuel maps, etc are updated about 100 times per second. It has no real use to common user.


I updated this page -> http://ceddy.us/?page_id=414
It tells under what conditions the Load and Compensated Loads are used for the Fuel and Ignition map look ups.