no, i've yet to try anything that advanced being a bit "old school" but hope to explore in the future. I just tried the bike with the new fault on it, re-assembling after a night on the radiator and it's done the job. (so far)
my issue maybe because i attempted to reset my tps. the reset is here http://www.bikeboy.org/ducati4vthrottleb.html which seems like a massive ballache.
For any unfortunate fucker in my position am going to describe how I found the immo flag in my own firmware which has moved due to remapping. The default one is at offset "3a19e", thats the exact location of the stock immo flag. So find your favorite hex viewer and look that up at the stock location. Then search the value such as "1c 98 00 22 00 4f 00" in your own firmware. Then find the matching value. In normal ascii its ".O.{.......-.Z...... So there it is. I haven't been home to disable my own and see if that fixes my misfiring issue but we'll see.
hmm so it seems my normal map with immo disabled didnt work. odds are i found the wrong location. but the stock map won't start and run either it just keeps firing. spark is fine, fuel seems to be fine, but my plugs seem to being oiled up. i have iridium plugs arriving tomorrow
I haven't read up on how you overcome an accidental "TPS RESET" with aftermarket software on your ECU, or what the symptoms are if you try and run bike afterwards..
Doing a software TPS reset will have no effect on the ST4s ECU. That function isn't programmed into it. The TPS can only be set mechanical. It's a bit fiddly but not difficult.
no, you miss my point Derek - besides physically moving TPS body while reading off values, it's something you can also enable via aftermarket software, and it's imperative that you don't "tick" this on certain early (non-linear I believe) ECUs - it's all in that Brad Black link that mgrover included above. I was led to believe you did tick this M?
that's why we could do with info as per post #140 - e.g. - is reflash the only answer? I think chrisw will probably know the answer to this.
No I didn't miss your point Chris. I knew exactly what you were referring to and it has always been my understanding that doing a software reset on a non-linear ECU would have no effect. I've been using Brad Black's TPS procedure reset procedure since I bought an ST4s 15 years ago although I haven't looked at Brad's site for some time and see now the warnings in red at the start of his instructions and it appears that I'm wrong. Well you live and learn. I'm not sure how the TPS software reset is interpreted by a non-linear ECU. The linear ECUs have a preset value loaded in the map, say 4.2º. When the reset is initiated it sets the current position of the butterflies as 4.2º which is why it must be done on a closed throttle, the throttle stop having been set at the factory and should not be meddled. So where does a non-linear ECU get the preset value for the TPS closed throttle degrees, wrong value or otherwise? I don't know enough about ECU maps and how they are written to have any idea.
I don't know the exact software Brad is referring to, or what software O.P. used, but seems to be more to this in Brad's notes Chris? http://www.bikeboy.org/ducati4vthrottleb.html
Quote from Brad Black: I had an M900ie 2002 model with the non linear TPS and 59M ecu come in with a TPS output voltage that did not match the degrees it was showing at all. The TPS was rotated all the way in one direction (high mV from memory) and the diagnostic was showing 3.1 degrees throttle opening. I flashed the ecu with the OEM file, and then the relationship between TPS mV output and ECU read throttle opening in degrees become much as I would expect to see. I then carried out the non linear TPS reset procedure as laid out here (well, in the 2V report in that instance) and after that everything else (CO trimmer, air bleeds, etc) became as expected. Although Brad says that flashing the ECU with an OEM file fixed the problem he doesn't specifically say that doing a software TPS rest caused it! In fact he doesn't mention that at all with regard to that ECU. Perhaps the map was corrupted for another reason?
hmm a new weird symptom. the digital bit of the dash is super faded. edit: that seems of to resolved itself. realistically if its jumped a tooth and the valves have gone into the pistons, it wouldnt continue to fire would it.
and another update. managed to disable my immo on my normal map and iridium plugs in, fires strong but wont keep going. it was from here i got the working xdf off the 620 monster https://www.ducati.ms/threads/ecu-maps-repository.348730/page-21
