OK, thanks to the wonders of technology, and some very clever and helpful people, I've done my first log.

Just a couple of questions:

In ECMSpy, I can load the log then go to Maps, EGO and see how the readings came though then do some math and change my map. I can also convert the bin, put it into MLV and get it to do some calculations for me.

Is there any advantage in one over the other?

Finally, on a DDFI3 bike, as I've only got a NB sensor, I'm only reading the rear cylinder. If I change the map, for the rear, does it compensate automatically for the front or do I have to add a certain percentage to the front map, based on my rear map calculations (If that makes sense).

I've tried to digest the Tuning guide, but not everything is sinking in and I'm wondering if I've missed something.

Thanks in advance for any info.

_________________
2009 XB12Scg

The ECMSpy log file analysis is a simplification of the MLV process, which is good in many ways cos you really need to know a bit more about what you are doing on MLV otherwise you will end up with meaningless maps.

Yes, you only have a sensor in the rear pipe and it is a narrowband sensor, so the mixture in the front is calculated based on assumptions related to the rear fuelling. If you are not going to use a front narrowband lambda sensor (which your ECM will support) or dual widebands (which your ECM will log), then I would follow the advice in the tuning guide, which IIRC says factor the front map by the same amount as the rear.

As an aside, I will shortly have access to a DDFI3 bike so will be playing with the enhanced logging capabilities in the coming months.

_________________
08 Specialized Langster

Thanks for the info Pash.


Looking forward to seeing your findings.....

_________________
2009 XB12Scg

Yes: EcmSpy averaging of EGO correction works. MLV filters are not set up for DDFI and results are beginning to overshoot after a few iterations. You will start tuning your ass off then and never get good results. MLV also seems to take into account the O2 voltage, guessing AFR from it, which adds another error to the calculation. Setting a new map value isn't simply calculating (EGO Corr. * map value), which is how MLV does it, therefore EcmSpy outputs just the average EGO correction and not a new map value.

_________________
"It is often said that before you die your life passes before your eyes. It is in fact true. It's called living."
Terry Pratchett

Thanks for the info Gunter. That helps.

I'd like to stay within one piece of software if possible to remove the chance of errors in conversions/configuration etc.

You mentioned "Setting a new map value isn't simply calculating (EGO Corr. * map value), which is how MLV does it, therefore EcmSpy outputs just the average EGO correction and not a new map value.", so, is there a way these figures can be used to modify the fueling without much of an issue? Or should they only be used for reference?

_________________
2009 XB12Scg