-= Ultimate Emanage Tuning Thread =-

[Fred 62]

just if it can help,
frequency logged with PLX-R500 with frequency input !


MAF frequency when i ran 15G and 360cc injectors and stock ECU and 91.1 pistons, stock heads :




for low RPM & closed loop



MAPS when i run 15G and 360cc injectors and stock ECU and 92.5 pistons and head porting and news 1mm oversized intake and exhaust valves :

the engine is in startup period and i go to a max of 4000RPM

MAF frequency for 92.5pistons and 1mm oversize valves and head porting




difference between 91.1 pistons and 92.5 pistons for MAF frequency with the same range





@+
fred

[Fred 62]

Originally Posted by BlackStealth

EManage Ultimate - 3SI Wiki.

thank's blackstealth for the support !

@+
fred

[rossfashow]

on my datalog the ignition timing is just flat line. i double checked the wiring and still flat line what is this cause?

[BlackStealth]

Originally Posted by rossfashow

on my datalog the ignition timing is just flat line. i double checked the wiring and still flat line what is this cause?

If you double click the graph table (ignition) you can adjust the set limits. Anything above v1.14 will show timing incorrectly and goes into large negative numbers.

[rossfashow]

Originally Posted by BlackStealth

If you double click the graph table (ignition) you can adjust the set limits. Anything above v1.14 will show timing incorrectly and goes into large negative numbers.

can you please explain. what you mean that it will show timing incorrectly.

from my understanding and what i see in my data logs is that ignition timing is just 0. a flat line throughout the entire datalog. It will datalog the ignition adjustment map but I dont even know if I am adjusting timing.

[BlackStealth]

You have to use v1.14 to see ignition timing correctly. Any version after that shows timing incorrectly on our engine types.

This timing bug will show an incorrect values like -114 degrees, which will appear as a flat line in your log because the default limits are outside it's defined ranged.

[rossfashow]

Originally Posted by BlackStealth

You have to use v1.14 to see ignition timing correctly. Any version after that shows timing incorrectly on our engine types.

This timing bug will show an incorrect values like -114 degrees, which will appear as a flat line in your log because the default limits are outside it's defined ranged.

will downgrading from 2.16 throw my tune off? will i have to retune?

[BlackStealth]

No, but you should verify everything still looks correct, ie. 6G72 engine type selected, etc.

p.s. When you downgrade to v1.14, use your current software to connect to your emanage with and select the v1.14 firmware from a different folder.

[badass3000]

What would you lose by downgrading to v1.14?

[jba3]

Originally Posted by badass3000

What would you lose by downgrading to v1.14?

Bump for an answering; I'm looking into the emanage ultimate for DR500/evo550inj/fmic/speed density setup.