Too busy to give as complete an answer as I would wish, but here are the salient points:
Smoke/Lambda issues- Smoke map was a CR170 not PD- common rail can run richer than PD for a given smoke limit and 16V better breathing. You can have as big a gap as you wish, values in between are interpolated.
If you want to run leaner, then reduce the figures.
At the same time, 1.3 lambda makes no sense when to spool a 1756- this is the whole reason why smoke limits are a map and not a single figure, or a flat lined map such as you have initially made. Richer lambda will increase pre-turbine exhaust enthalpy, thereby work that can be performed on the turbine, meaning target boost setpoint can be acheived quicker and then once spooled lambda can be leaned out again. Think more 1.1-1.15 lambda at lower IQ and RPM to initially spool. Worth noting on your log boost only meets specified ~3100rpm. Boost following the green line on the graph as shown would be less aggressive and yet still meet specified by ~2600rpm.
Boost log.jpg
N75 issues- are you changing the right values? Look at IQ in your log and compare to your N75 map. ~60mg? 33-21%? PID is doing a good job keeping you up above 40%. Why does your N75 map reduce as IQ reduces?
Nice to hear you've got Lambda limitation functioning- well done.
Bookmarks