Has anyone had this happen?

HeR3tic: Good point about the shared exhaust issue. Could have fouled a plug but if that were the case then why would shutting the engine down, cycling the ignition three times, re-starting the engine result in no further engine light, engine miss, black smoke or rough running condition?

The fuel tank was half full of fuel and I am running the single under the tank K&N filter. What really puzzles me is that the ECM is not retaining any codes....:confused: I would think that if the problem were electrical (ECM) it would code (turn on the engine light) and stay coded until cleared manually...would it not? When the ECM is reset in this manner (manually with the key), does this action also cancel any codes that should have shown to cause the engine light in the first place? Has anyone had their machine turn the engine light on and not set a code...Thanks SB...
 
Last edited:
TuneBoy

I have re-read some of the instructions for troubleshooting with TuneBoy and discovered that there is a "refresh" function in tuneboy which will re-post a list of any codes set by the ECU that have been previously cleared. Will keep you posted on results...maybe this will shed some light on this deal....SB.:)
 
Cycling the ignition 3 times will not clear codes in the ECU. A certain number of warm up and cool down cycles will clear a check engine light. However all of the faults are stored in the ECU until they are cleared by you with Tuneboy or with the Triumph tool. I think that is required for all OBDII equipped vehicles for emission inspection purposes. The codes should also show freeze frame info as to what the sensors were reading at the time of the fault. Tomo probably could explain/confirm this further.
 
I Understand the Theory

Pigger: The fact that this bike will reset the engine light with three cycles of the ignition key is part of the mystery for me. It will do exactly that and to compound the mistery it ran perfectly after cycling the key and turning the engine light off...Also, I have left the light on and it will reset itself after running 50 miles or so at highway speed...Give me a clue here:confused:.
Not only that but it will not give me any codes when I hook it up to the TuneBoy. That is what is making me wonder what the hell is going on with this bike...:confused:
Since the engine light is no longer on (at this time)...(this is not the first time I have reset it by cycling the key as per my initial description of events)..I am going to try "recovering" the codes as per the instructions from the TuneBoy manual.
My frustration with this is that I can't fix what does not set a code...:eek:..I hope to have some time Saturday to see what I can recover from the ECU with TuneBoy....Maybe TOMO wants to wade in on this one...SB
 
Last edited:
Pigger: Thanks for the help. Yes, I did open TuneBoy Diagnostics. :) No Codes. :mad: Thats why I went back into the manual and found the recovery process outlined there for past codes using TuneBoy. I am hoping TuneBoy will recover any erased codes. :D I know that cycling the ignition is not supposed to work with regard to resetting the engine light or the ECU but you will have to believe me when I say it does...it fixed the rough running engine problem and turned the engine light off immediately with no delay...:confused:.. SB.
PS. I may have to call you this weekend to chat on this subject...
 
Round Three...ding..ding..

Much to my displeasure I have discovered the reason I am getting no codes from Tune Diagnostics....It isn't working. :sick:

Pigger and I have less hair now than we did last week about this time, but have settled on a solution. Pigger suggested I Email TuneBoy tech support and explain the issue to include the fact that Tune Edit is working perfectly....go figure...:D

Pigger has been great and spent a fair amount of time on the phone with me getting the Tune Edit portion to work in the past few weeks. I want to thank Pigger for his time and efforts knowing that he didn't have too...it was great...Thanks Brian. :bch:

Wayne has been very helpful and we are now in the process of uninstalling TuneBoy V3.4.11 (my old version) and installing V3.5.0. Wayne and I will know tonight if this works or not as he has given me specific instructions to follow in trying to open the program for the first time. Apparently Wayne felt that trying to fix problems with my computer and V3.4.11 were not worth the time...better to update and go on from there.

GEEEZ....all I wanted to do was find out what if any codes were being sent.....I'll Keep you posted.....I think this computer is out to get me.....anyone know a hitman....SB
 
The most likely culprit in all of this is probably a connector in the wiring harness. All it takes is one poor contact and things can go south fast. A point of high resistance will make the ECM "see" things incorrectly. And to make matters worse, there is a probability that no codes were thrown because the connection wasn't completely broken.

The ECM in the Rocket isn't all that sophisticated. Many autos have specified ranges for values and will actively compare them to other inputs to make sure things make sense, and will set a manufacturer specific code for a sensor being out of range if it sees a high or low voltage when it shouldn't. Cars have gone so far as to skip all of this and use CAN systems which don't rely on voltages, rather digital info. If there is any kind of connection at all, this info will make it through. It would take a severed wire to stop it.

So, really, it could be any electrical connection to any engine management device, including sensors, control units, coils, stepper motors and so on. My advice would be to stop by your local auto parts store and pick up some contact cleaner and di-electric grease and lift your gas tank and go through your connectors one by one, first cleaning them and then sealing them with a little di- electric grease. It very well could be that heat from your motor cased the connection in question to improve, or possibly your battery being freshly charged from your ride may have enabled electricity to get through the poor connection sufficiently.

Since your problem is intermittent I would tend to rule out device failure or fuel contamination, this sounds more electrical in nature to me.
 
Back
Top