I am interested in the process for the 2018 390 Duke. Read this whole thread and subbin
I guess your duke is using a different ecu than mine, as above stated by satria_wr the ecu is EMP44. That time he was strugle to find the right checksum, hope he can find the right one now.I am interested in the process for the 2018 390 Duke. Read this whole thread and subbin
Yes, you are absolutely right. I did a wrong checksum correction for this M17.8.7 before. What i did with the tables was, fuel enrichment, advance ignition, rev limit increment, speed limit removal. The engine can start, but when I turn it off, it won't start again. Lucky for me it wasn't bricked, now i use winols for the checksum correction, it works fine. The demo version of winols also works flawlessly.All these are good but make sure you do the checksum correction or you will searching for new ecu.
Στάλθηκε από το ASUS_X00HD μου χρησιμοποιώντας Tapatalk
Thanks for the input. but there is not the original computer. It has a fueltech ft300 installed. All the maps must be assembled from 0. The motorcycle is equipped with a turbo, so I need to know the ignition values well. Fuel is tuned with a widebandI am sure you won't get any serious gains because all these ktm high rev engines have quite high stock ignition timing settings. On the contrary, extra fuel gives quite perceptible difference.
So I believe you must ad 7-8% fuel to the entire fuel map both closed and open loop and set the rev limit at 12500, not more in my opinion. If you find the ignition map don't add at high loads over 6000 rpm. Give just 5% 4000-6000 rpm (there is a slight loss of power at this rpm band) and use 100 Ron gasoline.
Sent from my ASUS_X00HD using Tapatalk
Hi brother. Maybe you can help me. I am with a project on my ktm duke 200. and I need to see the original ignition table. Only see the map, since I do not have the tools to read the ecu, nor the ecu in place since it is equipped with a programmable injection. Will you have a picture of this? or any file that you can read on the pc? Thank youCan you share the XDF file?
Hi Han_s, Awesome work man!. Can you please share the XDF file (even if it's incomplete), it will help me tremendously understanding the workings and structures of different maps in the duke, I have a KTM RC200 , which shares the same ECU M17.8.7 metal body, I have the files extracted from my ECU, maybe we can share the ECU bin files with each other and compare a few maps between a 200 and 250. I am working on Winols and trying on TunerPro.
Can you send me the bin ktm duke 200 250 390 file? Please [email protected].Bro,
sorry for the delay
i can only upload the XDF as i can't upload more than 98kb.
let me know your email and I will send you the original bin file along with my tuned bin file, for your reference.
I purchased xdf from oldskulltuning . Unfortunately, their xdf is encrypted so I can't tell you the exact location. You can get in touch with them to get an xdf for your bin
That can be circumvented. In order to identify the map and switches placement you change the value and save a copy of the bin file. Then you open both bins in free WinOls and use their map compare function to identify.