Ducati Monster Forum

     With the not so recent demise of DucatiDiag(DD) and having bought a new bike that needed ECU work i though i was out of luck. But alas GuzziDiag(GD) came to the rescue. It uses the same OBD II cable and drivers that DD does. I'm not going to get into making sure you cable is correct, that was done here (http://www.ducatimonsterforum.org/index.php?topic=62060.0). GD only works with IAW5 and IAW15 ECUs do a quick google search to determine what your bike is running. Try searching here first. (http://jpdiag.freeiz.com/modelselect.php)

Link to GD page with everything needed. (http://www.von-der-salierburg.de/download/GuzziDiag/)

      Now after downloading and unzipping GD you can run it. GD being a tool for Guzzis were are just going to have pick a guzzi bike with the same ECU as our bikes. I picked the Breva 1100 being that my S2R1000 has a IAW 5 ECU


That is really the only explanation needed. The software is pretty straightforward. I've only tested the TPS reset function and it seemed to work. Also of note is that there is JP Diag that is DD without all the legal trouble. Download JP diag here. (http://jpl250rs.perso.sfr.fr/) I haven't had a chance/need to download it. But it is the same as the old DD from the looks of the screen shots. Now on the fun part...

The real reason to use GD is the IAW5x/IAW15x ECU writers and readers. They can read and write .bin files which are basically registry tables where the ecu looks up specific running parameters. To make sense of the .bin file you need to use TunerPro(TP). TP uses an .xdf file to translate the .bin file into something that is actually useful. The .xdf files are ECU/Bike specific(to the best of my knowledge). These are the xdf files available from GD page.


TP also has an .xdf for IAW 15x bikes at the bottom of this page. (http://www.tunerpro.net/downloadBinDefs.htm)


I wanted to disable the lambda sensor on my bike. So I downloaded and ran the IAW 5x reader. It takes around 15 minutes.


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. *NOTE* As mentioned in this thread, I was using the wrong XDF with my bin files so take the following images with a grain of salt. Basic steps still apply. Match your BIN and XDF ( Stock ECU and DP ECU XDFs may not be not the same!), I was using the S2R 1K DP xdf which is differn't from the stock S2R 1000 Map.


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.


I'm playing with my already edited .bin file so both the set boxes are already unchecked (lambda off). Now you would make the changes you wanted and "save as" the .bin file so you have a backup of your original settings. Also GD writes a little ECU.bin .txt file that relays information about the bin to the IAW 5x writer. I just copied the one GD made and changed the file name to match my edited ecu and I also edited one part of the contents so i could distinguish the two in GD.


No just open up the new .bin in the IAW 5x writer. You can see where i edited the text file here (Tester: DUC wo Lambda).


Then click write and that's pretty much all there is to it.


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!

Thanks for the writeup John! Were you able to disable the immobilizer?

I have a 5.9M ecu (woe is me) and it'll let the tps be reset and otherwise but not use the read/write program.

Not yet. I'll have to dig around in the bin file to find the table. If i could get my hands on a .bin with one already disabled it should be pretty easy to compare the two. I need to do this actually, i want to swap out my gauges.

I managed to download the .bin file for my 695. Any ideas about where to find a .xdf file? I tried the S2R800 XDF, most of the maps make sense, but it reports two Lambda sensors. I think the 695 has only one.

My S2R1k also only has one lambda but you need you to turn both off.

I think Lambda 1 actually controls the immobilizer. I did a compare between two bin files from an immo disabled to stock, and this was the only difference. On the 695, this is at offset 0x4D144.

Disable it and lets us know if your bike starts with the gauges unplugged.

Hey guys is there anyone successfully use this program on a 996 s4r ?

Is there an easier way? I struggled to get the gauge connector off, but was unable. Will try again this weekend with the headlight off. BTW, the 695 DP map makes the bike so much smoother!

WARNING: From the image posted, your XDF is inappropriate for your BIN and you will corrupt your ECU firmware by editing values randomly.

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.


If the maps are mis-located, the Lambda setting will also be mis-located. You are changing random numbers in the firmware.


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 makes
http://dbinbox.com/Impulsive_Duc (http://dbinbox.com/Impulsive_Duc)

If 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 (https://www.dropbox.com/sh/20hb4nqnxjqqbbw/AAAv6gjgypsWrCjm4yp-A2F9a)

Dude, thank you for the valuable information and offer with the XDF! I suspect you are saving many of us from bricking our ECUs.

Hey guys!
Im the austian guy and want to "play" with my sparepart ECU.
Does anyone have a .bin file from a Ducati Performance ECU from a M1000 or S2R1000?
This can be done with the reader from guzzidialog.
Thanks a lot,
Klaus

Klaus, can you be a little bit more specific about your map?
"BIN begging" is usually frowned upon.
You typically share a copy of your stock bin before asking others for theirs.

---

It has come to my attention certain motorcycle shops are approaching me as individuals here on the forum.
They are then taking advantage the help I (and others) provide in order to charge people, and are proceeding to claim the work as their own.
Additionally, they do not share the source of the information.

• I received permission from GuzziDiag and Pauldaytona to adapt their XDFs, with the understanding their attribution is credited and it is not sold. (CC: BY NC)
  I additionally add (CC: SA) to anything I make.
• Meaning if it comes through me: (1) you cannot sell it, or anything derived from it, (2) you have to share anything derived from it in return, and (3) you have to include attribution of everyone before you.
• (The source firmwares fall under "automotive repair" and I do not retain any ownership rights. DERIVATIVE WORKS, however, do -- meaning if you edit in our XDFs)

Just so it is clear: don't be a dick.
If I catch another business profiting off of the community's hard work I will cease providing support altogether.

No one screw this up before Guzzidiag hopefully supports 5.9M ecus.

It's not that big a deal, a MPPS cable costs the same and does the same job. (~$20, plus MPPS does more "things").
The issue at hand is this is a homebrew project, and Bernd puts in a lot of effort to make it more friendly for end-Riders.

Using MPPS is a bit of a pain.
And although I whine to Bernd about it, GuzziDiag is more for Guzzis than Ducatis. ;)

Please click the "Donate" button in GuzziDiag, if it comes up in the wrong language, please use this link for US/English:
(https://www.paypalobjects.com/webstatic/mktg/merchant/pages/donations/donate_hand.png)
Click to donate to GuzziDiag author so he continues to support his work!  [thumbsup] (https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=XWSP8EDEVQGPW&country=US)

Hello impulsive_duc!
I'm not a shop owner and and I work not for a bike shop.
I work for a chemical fab.
I own my Duc since February this year and very happy with it.
I have problems since I modified my duc: No O2 Sensor, No catalyzer, oper air box, Mufflers with dB Eater,
modiefied ECU by Daniele Moto, Power Commander 3;
My duc runs a instable idle when the engine is hot. Sometimes the idle hang up at 3000 RPM.
I bought the ECU used from a German Ducati Forum Member.
I also have a second stock ECU from a S2R1000.
With this ECU I want to exclude a damaged Daniele Moto ECU.
I hope my english is understandable  ;)
Bye,
Klaus

Klaus, your English is fine. :)
But you never said what bike you have. (Year, Model, Type?)  ???

Please do the above, and send me for:
(a) Your current (M1000 or S2R1000) Danielle Moto (aka Rexxer) ECU-- explain anything specific about your Rexxer flash
(b) Your "spare" S2R1000 ECU (Stock? DP?)
(c) Your PowerCommander PC3 .DJM map

^^ I made my own utility to permanently add PC3 maps into ECU firmware ^^
After you use the PC3 to dyno it/make it run OK, you can merge the maps and remove it.

If you give me the PC3 map I will see if I can "add it" to the firmware.
You will then be able to see what the TOTAL fueling looks like as a 3D graph in the XDF.
(Assuming a previous XDF works.)
This I will do as a one-time favor.

You should probably learn to make the XDF yourself.
I will only check to see if one of the pre-existing ones work, and will let you know.
I will not make a new XDF, it is too much work.

I will not disable the immobilizer for you.
I suspect your "spare" ECU is a stock one and therefore is Red-Keyed, and will not start your bike.
I would need to make an XDF to do that, and it is too much work.

Finally, I cannot help you write the ECU if it is a 59M.
GuzziDiag does not support 59M's (yet).
Send a donation to Bernd and politely ask, and maybe he'll be inclined to work on it faster.

However, I can still check the BIN to make sure it is OK.
(Assuming a previous XDF works.)

Hey impulsive_duc !

Thank you for supporting me. On Saturday I do a great ride in the alps. But I already have the Problems with a instable idel on my
S2R1000 from 2006  :)
So Yesterday I took my sparepart ECU from a S2R1000 with disabled immo.
I took out the catalyzer control in the bin with TP and wrote it back to the ECU.
And it works  [thumbsup] without a yellow lamp.
After TPS reset and setting the idle withe the adjusting screws it runs with a cold engine.
Today I will test it during a ride.
I will post my experience an will send you my bins.
Thanks a lot!

Bye,
Klaus

Klaus, thanks for the updated files. I've sorted out the XDFs and e-mailed you.

I am posting here for two reasons:

First, I'm plugging the Wiki I set up to handle user-made contributions to XDFs.
Please contribute your user-made XDFs or make corrections here:
use the "(MM 5AMHW610) Ducati SportClassic Biposto / S4RS / M695 / S2R1000" article as a template.


Second, I found something really silly on Ducati's part... take a look at one of my XDF's titles at this point:
The microcode is almost 100% identical between them. I believe the term for this scenario is "Parts bin bike"?

I'm looking on the Wiki and I see  the S2R800 XDF listed as under the 5am. However when I go into the hosted file server, there is no s2r800 under the 5am XDF folder. Am I missing something?

Good thread

Thank you very much for your offer, impulsive_duc :) I just uploaded my *.bin file and a photo taken from my ECU of my 1198. I've already tried the *.xdf files from the GuzziDiag page, but there are always implausible values in some tables. However, some tables seem to be correct, at least the values make sense. So somehow we need to create a new *.xdf file combining different *.xdf files from other ECU models which partly fit. But how can we assure that table values, which seem to be plausible, really reference to the appropriate registers of the ECU? In addition, none of the *.xdf files shows my lambda sensor being enabled, but actually it is. All in all, it seems to be kinda risky, because some tables describe very similar values.

Thanks for any help :)

I took a look. Seems like an EU spec stock 2009 1198 ECU (28641761A).
"V1.27 5AM 1198 328641831D" (http://www.von-der-salierburg.de/download/GuzziDiag/xdf/5AM_Ducati_1198_328641831D_V1.27.zip) from the GuzziDiag page loads the values correctly.
Pauldaytona developed that XDF, so contact him for further assistance.

I only took a brief look because Pauldaytona's XDF seemed OK. However, on closer inspection the three "Lambda" flags in his XDF are defined incorrectly and never would have worked. They point to a blank region of the firmware. He needs to fix that. I found where they are, but won't post it for a very specific reason:

• Why would you try to disable lambda in the stock ECU? Why not just flash the DP Termi Slipon firmware instead? That doesn't use lambda to begin with.

The firmware you likely want is "DP ECU firmware for 2009-2010 1198 Termi Slipons" (96520109B). However, that is significantly different from the firmware you are running!!!
If I were in your shoes, I'd try using "DP ECU firmware for 2009-2010 1198S Termi Slipons" (28641911A) first. That is very, very similar to your stock firmware. (~98% similar)

Be careful the version you pick has the same DTC (on/off) as your bike. You didn't give me any information about your bike, I am guessing from the firmware.
If anything goes wrong, restore from the backup.

Thank you for checking out my firmware file :)

So first of all, I don't intend disabling my lambda sensor, because I don't see an advantage in doing that. I've always assumed that the lambda sensor is an important part for adjusting the fuel-air mixture. So I don't understand how a bike can run flawlessly or even better with disabled lambdas than with enabled ones. Maybe you can lift this little secret for me  ;D

And the main reason why I came here is because I removed the cats from my stock exhausts and also mechanically disabled the stupid exhaust valve to get a better sound on by bike. But then in many forums I've heard that I need a new ECU mapping, because my bike might be run too leanly due to this modification.

Your idea of using a Termi Slipon firmware sounds nice, but I'm not sure if it fits best to my current hardware-exhaust configuration, because I'm not using termis but only modified stock exhausts. So do you think there's almost no difference between Termi Slipons compared to my current modified exhaust system? And where do I get the Termi Slipon firmware from?

Another point is that I'm not sure if the downloaded firmware file I got by using the GuzziReader is complete and bug-free. I didn't get any errors but it took about 15 minutes to download it and now I'm not sure if that went well. So if I flash the ECU with the termi firmware I won't be able to go back to the stock state, assuming that my backup is not consistent, you know.. :)

I haven't done any modifications to the software of the ECU so far, because I don't have that much experience with ECU controlled bikes.

Do you need some specific information about my bike? It's just a Ducati 1198 from 2009 with the modifications I mentioned above.

Cheers & Thanks
BCocq

//Edit
Meanwhile I reopened the stock cans and also removed the mufflers, so the cans are completely emtpy except for the damping wool inside.

Your PM has magically summoned me. But I thought I answered your question already?
Your backup seems perfectly intact to me.
Lambda sensors tweak fueling, but to the wrong ends. They cause bikes to run excessively lean. It is better for engine-health to remove them and convert to an "open-loop" map, but please consult your local municipality if it is permitted for street use.

Even the DP map is inaopriate for DP bikes. :(
I datalogged a DP map for a SC Mono and found fueling needed to be cut by about 30% across the board, except at WoT. Way too rich.
However, I recommend the DP map by default because of one thing: any values between "stock" and "DP" is guaranteed safe.
I even wrote a utility that uses a little (%) slider allowing me to create a new firmware by selecting much Stock (%) and how much DP (%) "character" I want.
However, that is left as an exercise for the reader.

Running lean is far more dangerous than running rich. Given your current modifications, my original recommendations remain valid.
But they are only that -- recommendations. Any changes fall on you to take responsibility for.
I am unsure what models/years had DTC enabled, but try the map and check the ECU errors. If it complains about "no DTC", try another map.
Per the advice of the venerable and knowledgeable chrisw, if you have the base 2009 1198 model, you ABSOLUTELY want the firmware labeled "96520109B".
If you want to retrofit DTC and DQS, that is also an option. Details in thread:
http://ducatiforum.co.uk/forum/threads/which-dp-ecu-for-2009-1198-base-model.28262/ (http://ducatiforum.co.uk/forum/threads/which-dp-ecu-for-2009-1198-base-model.28262/)

You can obtain the BIN if someone has uploaded it at the Open-Source Firmware Repository. The link is on the Wiki ( http://motoxdf.wikia.com (http://motoxdf.wikia.com) ) along with XDFs.
If you correct your stock ECU's XDF so the lambdas show up properly, please consider submitting the corrected XDF to the Wiki.
There are far too many ECU's for me to ever hope to make all the XDF myself.

PS: There is a new, better, more proper guide to TunerPro use at the WildGuzzi forum.
I strongly suggest using that guide instead.
I likely cannot continue reading three forums for updates, so ongoing individual help may be limited.
There are bigger fish to fry, so to speak -- but I will respond if able.

http://wildguzzi.com/forum/index.php?topic=73938.0 (http://wildguzzi.com/forum/index.php?topic=73938.0)

Oh, I knew there was something wrong with these lambda sensors  [bang]. So am I right, that if I disable the lambdas the ECU will use the statically defined fuel maps without being manipulated by the lambdas during the drive? That would mean I could disable the lambdas in my stock firmware file, if I didn't find some appropriate termi slip-on firmware, right?


I searched for the firmware file on the ftp-server http://www.irok.org/ftp/Ducati%20Tuning/ (http://www.irok.org/ftp/Ducati%20Tuning/) but I couldn't find one which is labeled like you mentioned above. Here is what I found

2237B37SNPZ_1098s_slipon_DP.bin
2237B37SNPZ_1098s_slipon_DP.bin.txt
28641571C_Superbike 848 Stock US.bin
28641571C_Superbike 848 Stock US.bin.txt
3213B13PT64_2009 Ducati 1198 Stock (Base model).bin
3213B13PT64_2009 Ducati 1198 Stock (Base model).bin.txt
321818PU017_2010_848_Evo_OEM_IAW5AMHW610.bin
321818PU017_2010_848_Evo_OEM_IAW5AMHW610.bin.txt
3220B20MA14_2011 Ducati 1198 Stock (DTC DQS).bin
3220B20MA14_2011 Ducati 1198 Stock (DTC DQS).bin.txt
32A0BA0SCA2_96520611B_2013_SF_848_DP_Slip_Ons.bin
32A0BA0SCA2_96520611B_2013_SF_848_DP_Slip_Ons.bin.txt
32A0BA0SCB2_SF_848_DP_70mm.bin
32A0BA0SCB2_SF_848_DP_70mm.bin.txt
96520311B_2011 Ducati 1198 DP Termi (DTC DQS).bin
96520311B_2011 Ducati 1198 DP Termi (DTC DQS).bin.txt

So maybe I missed it somewhere or you could send it to me somehow if you knew other repositories :)


I edited the xdf file "5AM_Ducati_1198_328641831D_V1.27.xdf" by Pauldaytona and first corrected the null-pointer reference of the lambda sensor 1 and 2. So now it points to the correct offset area, specially for my bike's ECU. Additionally, I added some tables, such as the "Dash Welcome Text" and the Fan 1 & 2 Temp. I will upload it as soon as possible  :)


Couldn't I easily disable DTC and DQS in the newly flashed firmware file instead, if there was an error? Would that work? I think my bike doesn't have any of these functions.

Thanks  :)

I'd recommend just using the SlipOn firmware as-is when you can find it. They will be "good enough" and you are not mucking with Lambda settings. Then consider changes later once you get a datalogger or if you have lots of backfiring.

May I ask how you know where the Lambdas are even located? Typically that involves a LOT of work.
Thank you very much for considering top help others by fixing the XDF on the Wiki. I'm sure Pauldaytona would say thanks too.

I've gone ahead and created the article template for you to modify for "5AM_Ducati_1198_328641831D_V1.27.xdf".
Just take off the note about it being the "GuzziDiag reference copy" when you modify it.

http://motoxdf.wikia.com/wiki/%28MM_5AMHW610%29_Ducati_1198_Stock_%28M/n_28641--%29 (http://motoxdf.wikia.com/wiki/%28MM_5AMHW610%29_Ducati_1198_Stock_%28M/n_28641--%29)

No, that is the only open-source repository. I know someone with that ECU but I can't bug him.
I do this as a job, and my hobby stops at the front door.
I use an entirely different set of tools for work which are infinitely more expensive. (Literally. [roll])

Yes, you could disable DQS and DTC, but then you would have a "bastardized" custom firmware that may cause grief for others later. As odd as it sounds, "keep it stock, don't mess with it" applies. Unless you have a wideband O2 datalogger, or there is something very specific you want to go in and change (like the Dash text), it is best to leave the "default" DP maps well enough alone. They had an entire team of engineers develop it. It's only a matter of picking which matches your setup most closely.

You can wait for a professionally dynoed map when it becomes available. There are enough corrupt, bad, and "seat of the pants" adjusted maps as-is. Anything with my special "Bin descriptor" txt file should be a reference, unmolested map. Anything else I can't vouch for.

Well, I kept watching for similar patterns I found in other firmware files where the lambdas seemed to be referenced correctly.


I changed the relevant parts of the xdf file entry in your wiki. I'm not sure if my changes make sense for others because the locations for the different components may surely differ from bike to bike. At least for me it might be correct. Further, there are still some tables which are probably useless, even for me.

[thumbsup] [thumbsup] [thumbsup]

You are the first person to actually contribute an XDF edit to the wiki in its three months of operation. Congratulations!

And yep, that is exactly how you find where something is. Just be a little careful, sometimes it doesn't line up just right. There are some models where the Lambda signature "says" there should be a Lambda, but there really isn't. Just be extra cautious when adapting XDFs across models.

Temperature tables tend to be 16x something, RPM are 32x something, TPS are 20x something. The "guess" of what the table is can come from those dimensions. (16x32? Must be some kind of Temperature-RPM graph. etc)

The normal download is 15 minutes for a 5am ecu. Guzzidiag does calculate the checksum of the downloaded file, at up and download, so when the reader or writer say it's ok it should ok.

Also the writer does not erase all memory, the part that lets the ecu communicate with guzzidiag isn't touched. So even if you have an error while writing, the ecu won't brick. In the time Guzzidiag exists, no single ecu was rendered unusable.

Some people have so little computer knowledge, that they can't find the downloaded file on the computer.

with a 5.9M ecu how can it do TPS reset ???

Should it do tps reset, what tps is in the bike? Could ducatidiag do tps reset? There is now IAW diag, because so many questions from other italian bike owners to support other ecu that need different connection code or other functions.

http://www.von-der-salierburg.de/download/GuzziDiag/IAWDiag_V0.46.zip (http://www.von-der-salierburg.de/download/GuzziDiag/IAWDiag_V0.46.zip)

Try if it works with IAWdiag.

But if you have a linear tps(tps1c) you can use it, if you have a logarithmic tps, pf09, pf3c never use tps reset, you will never get your hardware settings back.

 

I actually spoke with bradblack about this, and discussed a method by which you can recover a proper setting.

In fact, I accidentally did this to a bike.  [roll] And only an expert shop foreman at Nichols Sportbike knew how to correct it!
The way to fix an "accidentally-reset nonlinear TPS" is documented here:

http://www.ducati.ms/forums/42-monster/406882-non-linear-tps-readings-vary-between-ecus-2.html#post4124577 (http://www.ducati.ms/forums/42-monster/406882-non-linear-tps-readings-vary-between-ecus-2.html#post4124577)

I have the other fringe cases written up (nonlinear TPS reset if ECU reading is OK, ECU reset if TPS is OK), but did not post them as the above instructions cover the "worse-case scenario". If you wish me to post them, I can do so.

Thanks for your explanation :)

Today I tried to change something harmless in my ECU software and wanted to write it back to the ECU. So I used the Guzzi Writer and noticed the error message "Error CAN 38.0" on the display while it was uploading. The upload seemed to work well, but what about that error message?

//Update
Another guy told me that the CAN Error should be a normal reaction of the ECU because the Guzzi Writer erases a lot of fuel tables first before writing back the newer ones. He also noticed a yellow triangle on the bike's dashboard during the flash progress which indicates this error.

Thanks for all the input Impulse_Duc . I've updated the first post with a warning about XDFs and BINs and fixed the broken images. Also if some has the S2R 1K DP bin and wants to upload it that would save me around $250   ;) .

Also for more code minded people, the FTDI drivers have the header file included so if you wanted to write something yourself it shouldn't be that hard.

B.Cocq, that is a odd error. Only the newer ducs(696 on) have CAN networks to the best of knowledge.

Hi JohnEE, and to add, if you HAVE one of those bikes and willing to help, we can send you the technology to easily make that happen...

:) Chris

Wenn you up or download a map, the ecu goes into programming mode, and does not communicatie over the can  bus with the dash. All 59m/5am have can bus between dash and ecu. Because the dash doesn't see the ecu communicating it gives a can error.

First of all great work and spirit to this thread.  Thanks to all the people's efforts that make this happen, my donation is on the way.

I am looking to replace the dash on my 07 S2R1000/DP bike with a motoscope pro.  I have a guy who has made the wiring harness for the unit, and now I just need to disable the immobilizer.  It looks like the xdf file you posted for the S2R/DP shows the two bits that need to be flipped.  My plan once my cables arrive is to confirm they work, read the ECU with IAW5xReader, use the xdf with TunerPro to make the change, and write the ECU with IAW5xWriter.

There are a couple of other differences which I don't get in the xdf,

one is the 0x4D2DC value which changed from 25000 to 15000
second is the 0x390A value which doesn't exist in the original
third is the 0x7339 values

Do I need to worry about these or they are just additional fields that you discovered that can now be changed in TunerPro.  If so, should I look at tweaking these?

Thanks again.

Rule one: only change things where you have a clue what they do and what is going to happen. Don't change to much different things in the same map at once.  I'm not shure what three values you are talking about but just leave it as it is.   

So cables arrived, and while I wait for the roads to be cleared of gravel, I'm going to backup and investigate the map that my bike has.

I was wondering if anyone can offer any assistance locating where the immobilizer settings are in the S2R1000 xdf?

Thanks.

I might be able to help. Emphasis on the might...You'll need to send me your Bike's map. I should be able to figure it out.

As a followup, not all Ducati ECU use CANbus. Most Monsters use analog pulsed signaling to the dash. Most Superbikes use CANbus signaling to the dash.

You can tell if your bike uses CANbus by looking at the wiring diagram. If ECU pins Body20 and Body29 are used, it uses CANbus. All 59M/5AM hwardware may support CANbus, but not all firmware use it. All in all that error is a minor one and can be ignored, as PaulDaytona points out. It just means "ECU is unplugged/not responding", which is normal when it is in programming mode.

PS: jthunder please consider uploading your DP ECU stock, unmodified map to the FTP. Other people would really benefit from it!

Regarding the S2R 1000 DP, I have it but it is on the "work" side of my firewall. I was the one who added the immobilizer flags in the S2R DP XDF. There is a reason I put 2 flags and labeled "possible" and "likely" on there!!!  [roll] I'd love to hear how JohnEE solved the problem.

I haven't looked at the two S2R xdfs recently and couldn't remember which xdf already had it flagged....no need for passive aggressive colors just trying to help. And help myself as I need the DP map.

Hello everyone,
I've been having serious trouble with a M620 Dark. I see that some people in this forum do actually know what they are talking about, so any ideas welcome. The story is long and it has been posted on jp's site, so I won't reproduce it here. In short: friend forgets bike for 7 years, then decides to "revamp" and ride it. The red key has been lost and the immo's locked, we send it off to be fixed, some time later comes back. Bike starts, idles, works kind of o.k. after 4-4.500 but in between it's just horrible. New spark plugs are fouled after 5 minutes, the mixture appears to be impossibly rich. I've downloaded jpdiag - thanks jp250rs - some faults are present and cannot be erased. I've reset the TPS and played with the CO with no success. Then I turned to guzzidiag and downloaded the .bin file from the ECU to edit with Tunepro, as I'm somehow convinced that the map is screwed. Unfortunately I can't find the corresponding .xdf file. On "www.irok.org (http://) (http://)" I find 2 files for an M620 (a .bin and an .xdf) that seem relevent, however only some of the ECU data appear
Help!

...and now that we've met better, does anyone think he (she) could help!! I really am in dire straits here

Before I messed with the ECU, I would visit Brad Black's site: bikeboy.org and make sure the basics of the bike are right. Belts, valve check / adjust, TPS, throttle body sync, sparkplugs, etc. Then Google your bike for problems and start fixing any problem that fits your situation. Until you know that the basics on your bike are right, you could easily end up chasing your tail.

Hi jduke, I guess I didn't make clear that everything - absolutely everything - has been checked and double-checked again and again. From valves to belts, everything's new or good as new. Unfortunately it has to be the map - or something else in the ECU. If someone could check the .bin or provide an .xdf file, that would be a step in the process

Might be having problems with the ECU not the map. They can and do go bad from time to time.
Might be worth sending to Bobby / Houston Superbike and have him look at it and see if it's going bad and if not, have him load a stock map, if he has one, to see if that fixes things. Maybe when you sent it off they loaded a DP map and your setup (intake / exhaust) isn't able to take advantage of the extra fuel and is running rich.
Good luck!

JohnEE... please refrain from insults. I use colors to highlight important sentences in my replies, or to call attention to particular facts, if people are skimming the post. It was not "passive aggressive" and I take offense to that. Please read any of my other posts or writeups elsewhere online and you will see I do the same there.

I do this as a hobby freely. As does PaulDaytona. Bring rude to someone who volunteers their time then asking for their help is a surefire way to not get it.

I recently had someone walk up to me in-person and disparage me for "modifying free software you didn't write". I politely took out my tablet and showed them the e-mail conversation with Beard where I asked (and received) permission to modify and redistribute the TunerPro definition files. And the other developers who I've been helping.

Please be respectful of the developers and what they do. It takes a lot out of their time and they don't have to do this.

hi guys,

 I am going to try to flash my 5am ecu in S4R Testastreata because I modified full exhaust and air filter. I would like to use the "Guzi 5am writer" the problem is that I do not have any DP map in .bin file. I have only .hex file and this is not supported by the guzi writer. Will be glad if you can advice me where I can get the .bin file. Anyway I am now working on emergency plan, it means I opened the hex in Tunerpro and the .bin in Tuneecu in paralel  and I am changing F1,F2,I1,I2 manualy between those maps. only think I dont know is for example fuel delta for right cylinder and some others corrections. so the emergency question is. will it works? can I write back original s4r testasstreta map modified with F1,F2,I1,I2 from S4rs DP ecu?

thanks

so will anser myself  ;D as i today try it, it works....

 [thumbsup]

I have found two maps one is DP and second DP slip on.I see that the slip on map is even more rich on fue so I will try it as a firs and then I will try the lean one. I will test it in couple of days on road hopefully. now the temperetaru is about 5 degrees only so need to wait for better weather.

2008 S2R1000 here.

Finally got around to picking up the cables needed. Purchased some off of Amazon that should have been right (KKL type) but no joy, wrong chips in the OBDII. Come to find out that LonElec sells what you need and guaranteed to be the right chipset in the OBDII cable. ~$30 shipped from London, took a week to get to VA.

Started by clearing the maint code that's been on for the 20k miles since I stopped going to the dealers, then proceeded to download a backup of my stock map.

(https://scontent.forf1-1.fna.fbcdn.net/v/t1.0-9/20915169_10108780494839888_9144594281705935981_n.jpg?oh=e3dce8202c498538f1b738a44cc9994b&oe=5A2A1B85)

(https://scontent.forf1-1.fna.fbcdn.net/v/t1.0-0/p526x296/20883028_10108780536441518_3471810623271008443_n.jpg?oh=2ddedd2000fe82d7d9979fffe8c77774&oe=5A1C0EBF)

Next up, compare the stock map to the DP map in TuneECU.

(https://scontent.forf1-1.fna.fbcdn.net/v/t1.0-0/p526x296/20800068_10108780625138768_6731254368546494279_n.jpg?oh=b76f988a89737e4ed84ac69ff60ab877&oe=5A3396F6)

Then it's time to write the DP map!

(https://scontent.forf1-1.fna.fbcdn.net/v/t1.0-9/20841016_10108780722338978_2749747456514406734_n.jpg?oh=81255019b7bfe8109361484fce49dd90&oe=59EC8562)

Success!

(https://scontent.forf1-1.fna.fbcdn.net/v/t1.0-9/20840714_10108780723072508_4718768636273861141_n.jpg?oh=97e5ca07c6fbaa12f40fe1ab3fd71a49&oe=5A250AB7)

All in all, I'm happy with the results for the $30 price tag of the cables. Don't think the DP tune is worth $250 for someone to flash it or the $500-$600 for a DP ECU.

Would someone be able to tell me if it IS okay to use the DP S2R XDF map on a stock S2R 1000 ECU bin?

Despite the original yelling in this thread, I've now seen multiple people online who seem to be quite happy with their use of the DP XDF for their S2R 1000 bin file, and I'm unable to find a stock one anywhere.

All I want is to disable the lambda, but I'm stuck, not being confident that I can do this with the available DP S2R XDF, or corrupt my ECU as is earlier stated in this thread.

I'm not even completely against purchasing a DP ECU upgrade if it means disabling the blasted lambda. They're not as expensive as they used to be.

Any help would be massively appreciated.

Just to note that I found a working XDF for a stock S2R1000 in https://motoxdf.fandom.com/wiki/%28MM_5AMHW610%29_Ducati_SportClassic_Biposto_/_S4RS_/_M695_/_S2R1000?fbclid=IwAR2emwF9QtBbY-rvGygTZt9tmpWCnc9cM7ScR2P06aARJb2p110H0kuxjfg

I disabled both Lambda and also, as it claimed to have been found in the XDF and confirmed, the immobilizer..
Uploaded the file back to the bike, and it seems to fire up fine.. I'll see how the lambda erase works out.
My intermittent check engine light for the O2 sensor will have to wait on me riding. Because it's 3am, I fired it up very very briefly to test the immobilizer. All looks good, though I'm not sure how to test for that one.

One oddity though.. A clicking after I reset my TPS. My TPS was displaying the odd number of 2.6. Resetting set it to 3.2 (Isn't it meant to sit at 4.8?), and had it make a load of clicking sounds through the cam.
I reset it again, and it settled down, though still says that same 3.2.

Anyway. I feel that was somewhat successful, and slightly stressful.