In a pinch, bike is running bad.

[DwarF]

my 1050 is running real bad. Last week, it died at stoplights a couple times. This morning it was having some rough idle issues while I let it warm up, and the check engine light came on.

I am in a tough spot where every day this week is really packed and I can't afford to not have a vehicle. The service shop is closed today (Monday).

I need some suggestions of things I can check to at least help make it though a few days. I might be able to take it in tomorrow, but I'm not hopeful.

Symptoms:
Idles below 1000 and dies frequently, even after driving for 20+ minutes. (neutral)
It has a hard time taking off, even under mild throttle. It wants to lock and die. (1st gear)
When running in 2nd or above, it runs smoothly.

[Gnome]

I would be inclined to check coils / leads / plugs, make sure all connections are good and that you haven't got any splits etc in the leads.

While your there, check your fuel lines are clear and not kinked, and if possible check your fuel pump and fuel pressure regulator (had the reg go on the 14 with simular symptoms to yours)

failing that - get it to a shop so they can run a diagnostic on it.

.GNOME.

[ This message was edited by: Gnome on 2006-04-03 09:28 ]

[DwarF]

I will check the rest, but how did you check your pump and regulator?

[gobits]

Sounds like a Fuel Injection problem. I would do a diagnostic run on the FI system.

[DwarF]

I am also going to check out the battery when I get home to my voltmeter. Has anyone had similar issues with a low battery perhaps, bad ground maybe? The bike kicked over strong on start, so I think the battery idea might not be right, but if I had a lose ground, perhaps?

Can you hook up a car battery charger to a bike battery? They are the same 12 volts. I would use the trickle charge option.

[Gnome]

On 2006-04-03 11:04, DwarF wrote:
I will check the rest, but how did you check your pump and regulator?

Not sure if the set up is the same as the 1400 - looks it - the regulator is 'clipped' to the pump, on mine one side of the clip had come away so the regulator wasn't doing it's job. It was just like riding an old 'carbed' bike with sh*t in the jets, any low revs and the bike wouldn't run and miss fire etc, give it heaps and it would 'sort of' run.
Removed the pump assembly, checked all the fittings / re-attached the reg and everything was okay again.

Might be a bit too much if your going to take it to the dealer anyway. Let us know the outcome ehh

.GNOME.

[crashmasterd]

Also, if it has ever been washed or ridden in the rain I would definitely check down around the spark plugs for water. This is a known problem, and could cause much the same symptoms you have mentioned. Particularly look at the left hand spark plug hole (Cylinder number 1).

Of course, #1 is the hardest to get to. :hammer:

[kuhlka]

Sounds like the problem I had a while back with a loose ground cable to the battery. Might try an ECU reflash at the dealer, or if you've got a tuneboy, just load the latest map/software for your setup.

[Captain_Rat]

I doubt it's the spark plugs. I had that issue (with water corroding mine). It did not start stong (in fact it stopped starting), but Dwarf's is. But if you're going to pull the tank you might as well change 'em anyway.

Capt.

[vinnyf]

My opinion, FWIW, is to find out if the problem is something endemic to the entire system (e.g, FI or ECM), or if the problem is localized to one cylinder (e.g., bad coil or spark plug). One cylinder going out will give you exactly those symptoms - running very poor, slow idle, etc. If it's a "system" problem, check for broken hoses or vacuum lines - air leaks into the system will screw up the running pretty badly too. And these bikes seem particularly sensitive to - or vulnerable to, if you like - moisture getting into the connections. Have you THOROUGHLY (too thoroughly?) washed your bike recently? If you have access to a standard automotive scanner - OBDII - you can plug it into the system connector and see if it tells you anything useful. But we tend to panic when these things go bad - take two steps back and try to narrow the field to what it was doing, what you were doing, and then the normal troubleshooting we've been doing for far too many years. And be sure to let us all know what you find, so we can come up with better answers for the next problem! :hammer:

[ This message was edited by: vinnyf on 2006-04-03 21:09 ]