Al:
What happened with the engine alarm going off could have been caused by a number of things....a slipping belt, a temporary obstruction to the raw water intake (plastic bag that came out when you sailed back to the harbor), you said you "shut down and checked the water filter".......now here's a probable cause...happened to me....the wing nut screws on the raw water filter came loose (or were not tightened enough) and the raw water system was sucking in more 'air' than 'water'......a few turns on the wing nuts, engine alarm problem solved.

My point, there is no one problem/solution.....you will figure it out.

Rob Abbott
AZURA
C&C 32 - 84
Halifax, N.S.

On 2015-10-18 8:24 PM, Josh Muckley via CnC-List wrote:

There is a chance that the belt was slipping. When you stopped the engine, it may have given it a chance to "re-seat" the belt. Next time you started the engine it had enough friction to grab, once it overcame the starting torque it stayed going and the problem no longer presented itself. If it happens again, check the belt to see if it is slipping.

Josh Muckley
S/V Sea Hawk
1989 C&C 37+
Solomons, MD

On Oct 18, 2015 7:09 PM, "Al Serrato via CnC-List" <cnc-list@cnc-list.com <mailto:cnc-list@cnc-list.com>> wrote:

    I'm looking for advice on a situation that arose yesterday. I have
    a 34 with a 3GMD diesel with raw water cooling. I motored for
    about 45 minutes at 2000 rpm and then shut the engine down.
    Everything was running smoothly. The temp gauge showed the normal
    100 degrees and I could hear water from the exhaust. I sailed for
    about half hour but then lost the wind and turned the motor on.
    The high temp alarm stayed on and the gauge showed 140 degrees.  I
    shut it down and checked the water filter, which looked fine. I
    tried starting it a couple more times with the same result, so I
    sailed back to my harbor. When I went to start it, everything
    worked fine again, and I ran the motor for a good 30 minutes with
    no issues. The gauge stayed at 100 the whole time and no alarm.

    I initially thought it might have been the impeller (which is
    about 1.5 years old right now), but when the problem arose I
    didn't check for the sound of exhaust water. Since it was working
    back at the harbor, I don't think the impeller was bad. I'm
    starting to think that the sending unit malfunctioned and then
    reset itself somehow but that's never happened before.

    I'm not sure what temp triggers the high temp alarm and whether
    the same sending unit goes to both the alarm and the gauge.

    Am I missing something obvious?
    Were there other steps I should have taken to diagnose it? I was
    of course concerned to run the engine for long if it was overheating.
    What next steps should I take, since everything seems fine right now.

    Thanks in advance for any help.

    Al Serrato
    C & C 34
    Fidelity
    San Francisco Bay
    _______________________________________________

    Email address:
    CnC-List@cnc-list.com <mailto:CnC-List@cnc-list.com>
    To change your list preferences, including unsubscribing -- go to
    the bottom of page at:
    http://cnc-list.com/mailman/listinfo/cnc-list_cnc-list.com



_______________________________________________

Email address:
CnC-List@cnc-list.com
To change your list preferences, including unsubscribing -- go to the bottom of 
page at:
http://cnc-list.com/mailman/listinfo/cnc-list_cnc-list.com


_______________________________________________

Email address:
CnC-List@cnc-list.com
To change your list preferences, including unsubscribing -- go to the bottom of 
page at:
http://cnc-list.com/mailman/listinfo/cnc-list_cnc-list.com

Reply via email to