Evo 9 with FPgreen, cossie cams, 353whp, 91 oct, 20.5psi at 7200rpm

Evo 9 with stock turbo, stock cams, 327whp, 91 oct, 21.5psi at 7200rpm

Evo 9 with stock turbo, stock cams, 307whp, 91 oct, 20psi at 7200rpm (Stock Turbo 2)

 

Everyone knows how rich a stock evo gets up top. One of the reasons for this is a huge jump in Injector Duty Cycle at 7000 rpm.

This graph pretty much shows it all. First overlay is a stock Evo 9 with the factory tune, second overlay is the same stock Evo 9, but now with my base map. You can see how the Injector Duty Cycle is cleaned up and lowered. Also spools much quicker and a little pick-up of peak load.

This evo gained approx 25wtq in the spool and peak torque area and approx 15whp at 7100rpm over the factory tune, with the same boost levels. As measured on a Mustang Dyno.

 

What are your AFRs at peak tq and peak hp?

 

For the Evo in post #32?

Factory tune it was approx 11.5 @ peak tq and 10.2 at 7200

with base map 11.2 @ peak tq and 11.0 at 7200

 

Bringing this back,

JB you were right theres something in the v2.0 2 byte airflow thats not reading correctly for me. I logged with v.99 and I am seeing low 2000 at redline

razorlab, are you using v2.0? If so can you post up the xml for the 2 byte if you changed it

 

No I am using v.99 or v.98, can't remember which one is on my laptop.

 

Just as a reference I had to change the location off V 2.0 it used 5 and 6 I believe for the 2byte airflow, and had to change to 2 and 3, under the new edit function. I had same prob as you, now it worlks fine. I also log around 1890 highest, this is spiking to around 30 psi on 100 octane. My load hits the 320 area, also 100.8 % IDC in same area.

 

^^I was going to change the request but 2 byte rpm is using 2 and 3. Although I dont use 2 byte rpm so I guess that wouldnt make a difference

 

I dont do 2 byte rpm and that seemed to be the only change from v.99, so i changed them and it worked, but i had same prob you did, 755 or whatever max, as well as high airflow at low rpm/spool folllowed by decrease high up. But its fine now.

 

It's request ID 4 and 5, not 5 and 6. Evoscan 2.0 is already setup to use 2byteload (request ID 0 and 1), 2byterpm (request ID 2 and 3), and 2byteairflow (request ID 4 and 5). If you followed the instructions that were posted for 2byteairflow on evom then yes, you would need to change the request ID to 2 and 3 on evoscan 2.0.

 

New round:

 

No FPGreen on 100octane?

 

Done a bunch but before I was doing the 2byte airflow.

Had a 100 oct one last week but it was cobb protuned so I couldn't log 2byte airflow.

 

Here is an interesting one:



Notice how the highest horsepower run has lower higher RPM load and airflow. Also interesting is how much load the Cams add in the midrange. Open air filter added to #3 added 16whp and 8wtq but had less airflow and load than #2 with stock intake.

All 3 are the same Evo 9. #2 and #3 where within 20 minutes of each other, #1 was 2 days before.

 

That is interesting. Adding the open air filter must be affecting the MAF if I'm reading this right because of the increase in IDC. (I'm assuming the AFR remained the same, but with lower MAF Hz and more fuel.) This is on the dyno, right?