Logo

BF60 Low rpms

mnys71tbn

New member
Hello forum. I'm hoping to get some insight into my BF60 outboard.

The motor doesn't want to go higher than 2000 rpms. Even at wide open. Runs okay at idle and does fine at low rpms. The throttle has no effect anywhere from 1/2 to full. Alarm goes off when pushed for too long. 1 second on, 1 second off. To stop the alarm I have to shut down the engine and turn it back on. Its almost like its in some kind of safety mode that won't allow the engine to rev any higher.

I will be checking the tach just to be sure that it isn't stuck or malfunctioning in anyway but I doubt that this is the issue. There aren't any indicator lights on this boat (low oil, temperature, check engine) so I'm not getting help from those. Just the alarm.

Any ideas on where to start looking? Thanks.
 
I don't think that you'll find the tachometer would cause this.

This does sound like it is going into engine protection mode and de-powering itself.

You don't mention the green oil indicator lamp. Is it illuminated while this is happening? It should be lit anytime the engine is running.
 
I don't think that you'll find the tachometer would cause this.

This does sound like it is going into engine protection mode and de-powering itself.

You don't mention the green oil indicator lamp. Is it illuminated while this is happening? It should be lit anytime the engine is running.
I do not have any indicator lights on this boat. We bought it used two seasons ago and it didn’t come with any. I was going to check the tach just to rule out if it was sticking or not.
 
Well....I'm no expert on this but it sure sounds to me as if it's going into protection mode due to low oil pressure. But it might also be an over temp fault. You need to try to eliminate the possibilities.

One thing you can do is touch the engine in the thermostat housing area. If you can't hold your hand there for a few seconds it could be overheating.
A better method would be to use an infrared temp gun and look for temperature below 200°f
Does the engine have a good tell-tale (pee) stream?


Has the oil level.been checked?
Have the oil and filter been regularly serviced?

Sometimes these faults are caused by faulty sensors feeding bad information to the ECU. You may need to check for fault codes to get a direction to go in for troubleshooting.

You might try unplugging sensors, one at a time, to see if the condition will change. However, to protect the processor, you should only disconnect and then reconnect while the key switch is in the OFF position.

There is another guy here...Goneagain4.... currently troubleshooting a similar issue on a 2017 BF60. You may want to take a look at his post and maybe compare notes.
 
The oil level is fine. Both it and the filter were changed at the end of last season. Engine is not hot. Pee stream water is present and is cold to the touch so I don't think that it is overheating. I will check the sensors and for water in the oil.
 
I have to revise my statement about checking for fault codes.

It occurs to me that, if you don't have a dash MIL (malfunction indicator lamp) ....otherwise known as as a "check engine light"....then you won't be able to retrieve "flash codes" without hooking up an indicator lamp.
Depending on the year model though, it might be possible that connecting to a Dr.H tool would work to do that.

It may also be possible to retrieve the codes by connecting a multimeter with a sweep type display (old school) or graphing capability to the circuit. That, just as would wiring in a lamp, will at least require that you have the correct wiring diagram that comes with the shop manual.
Available here:


That is the genuine Honda manual site.

If you decide that you need/want one, please don't get "took" and buy a knock off like Seloc, Haynes, Clymer or others out there to save a few bucks. Those are notorious for being next to or worse than useless giving misleading and incorrect information at times. No "savings" there.
 
Glad you figured it out. Honda O2 sensors do seem to cause a lot of issues.

Any tips about how you went about finding that O2 was the problem?

Thanks for posting the solution.
 
Back
Top