WARNING: From the image posted, your XDF is inappropriate for your BIN and you will corrupt your ECU firmware by editing values randomly.
Which gave me a .bin file to work with. I opened up the xdf first in TP then the bin file. TP then looks like this.
I say this because your fuel map is misaligned. You can tell by the abrupt changes in values -- an improperly aligned table looks like a TV with part of the image cut off the top, and sticking up from the bottom. That is exactly what I see in your image. Graphing the map by clicking the "graph" icon will show abrupt changes in the fuel map demonstrating this.
Another indicator is your TPS values (the X-coordinate in the top row of the table) are garbage. They go from 15 to 0 to 100 randomly. They SHOULD go from around 3-degrees to 89-degrees in a linear fashion.
Each ECU Ducati makes is slightly different, and has the maps stored at different "offsets".
I have found it is safer to pair a single XDF with a single Ducati ECU model number. A single bike may have multiple ECU models numbers. They are usually printed on two paper stickers on the ECU, with additional information on foil stickers beneath them.Furthermore, the XDF needs to be VALIDATED by someone who knows what they are doing.
However, sometimes even this varies due to Italian coding.
Creating XDF's is a bit of an art and is very time consuming. People such as me do it on a case-by-case basis.
Most others also (usually) PASSWORD-PROTECT their XDF file to prevent others from stealing their work. So (usually) you cannot correct the XDF yourself, and have to work from scratch.Bernd, Pauldaytona, and myself are exceptions.
We share our work openly. In fact, the SportClassic maps on GuzziDiag are the ones I developed in conjunction with Pauldaytona.
You'll see multiple tables on the left which you can play with if you are confident in the xdf mask. I only cared about two, the lambda 1/2 on/off settings.
If the maps are mis-located, the Lambda setting will also be mis-located. You are changing random numbers in the firmware.
To test out if it worked I just unplugged my Lambda sensor and went for a ride. The maintenance light didn't come on (was coming on intermittently with the Duc.EE installed). My bike runs like butter now at lower RPM. Donate to the GD author if you end up using his/her programs. That is all, be careful playing with the tables and good luck!
I strongly suspect your evaluation was "placebo effect". The narrowband sensor probably went into error-fault mode due to not receiving a signal.
Please send me your BIN and a picture of the top and bottom stickers on your ECU and I will try to tell you which XDF is appropriate, or perhaps create a new one if necessary.
An an aside, I need to compile a database of ECU firmwares if I am to assist in making XDFs for them.Upload a ZIP at this link containing: (1) your firmware BIN (2) a .TXT describing your bike/ECU (3) photos of the top and bottom of your ECU's PAPER stickers and (4) the LOG files GuzziDiag makeshttp://dbinbox.com/Impulsive_DucIf I have time, I will construct an appropriate XDF for any BINs placed there (that follow instructions!!) and host it in this folder:https://www.dropbox.com/sh/20hb4nqnxjqqbbw/AAAv6gjgypsWrCjm4yp-A2F9a