Reply
 
Thread Tools Search this Thread
 
Old 06 July 2011, 14:20   #1
Member
 
Country: UK - England
Town: South Devon
Length: no boat
Join Date: Jun 2010
Posts: 28
2007 Yamaha 60hp Speedo issue

Hi all as above really, speed doesnt come up on the tacho so mucks up the other details as well such as MPG and trip distance obviously. Nothing came up the other day to start with then i got some numbers which obvisouly were wrong (22mph up the river - hmmm) 6knts showing on GPS. Not sure what i can check - where is it measured from. I know the speed sensor inside but not really sure how speed is measured or where to start.

Many thanks

Si
__________________

__________________
ribandlandy is offline   Reply With Quote
Old 06 July 2011, 17:59   #2
Member
 
Country: USA
Town: Oakland CA
Length: 3m +
Join Date: Feb 2005
Posts: 6,653
Take a look at the back of the gauge and see if there's a vinyl tube connected to it.

If so, you've got a blocked pitot tube. On the leading edge of the lower unit, there is a tiny hole (you can run a thumbnail along and it should snag at the hole.) As you move forward, water gets forced into the hole and it pressurizes the air, and that pressure is converted to a speed at the gauge. Unfortunately sand, kelp, and bits of shell all love to try and hide in the hole. Clear it out with a paper clip, small drill bit, or similar, and you should be good.

If it's an electronic sensor, well, I don't know. Not sure how the networked Yam's determine speed.

jky
__________________
jyasaki is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off





Copyright 2002- Social Knowledge, LLC All Rights Reserved.

All times are GMT -5. The time now is 13:17.


Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.