Help! 23’ 195s Check Engine & Over Heat On / No apparent issue

[Jtmains]

Hey team, desperately needed some help. New to the Yamaha 195S (2023). Purchased used with 6 hrs. love the boat. Been on boats most of life and familiar with jet drive (own 97’ gtx - grandfather pass down) somewhat.

Had been out on the water most of the day and was heading back on Ohio river (gross I know but super close) running full throttle at 47/48 mph, smooth water for no more then 5 miles. Almost back and both check engine and overheat warning came on screen.
Immediately slowed down and placed in center position “neutral”. Opened engine cover, and everything felt and seemed normal. All 3 pissers were flowing continuously and same as always.
Tried moving forward, only got be limited, makes sense. Shut everything down.
Check everything you can quickly do on the water, absolutely 0 debris.
Started up after few minutes, came back on so limped to the ramp and was able to trailer. After I looked everywhere, even with the help of service manual, no luck.
Finally gave up took to dealership 1.5hrs away. They said, they see the code and tested with 0 issues.
Got it home, ran for 1 minute, no water and came on in 45 seconds.

What am I missing here?

 

[Btsnhos]

I assume you checked the impeller to see if you sucked anything up. You can remove the water coolant inlet cover on the port side forward of the nozzle and see if that is clogged.

 

[Jtmains]

@Btsnhos thanks for the response and insight. Yes I checked that also. Even removed thermostat to see if any debris possibly made it up into the motor.

I think at this point, come spring time it will be go or blow. I cannot find anything and I don’t feel it’s worth removing entire cooling system piece by piece.

 

[FSH 210 Sport]

Hey team, desperately needed some help. New to the Yamaha 195S (2023). Purchased used with 6 hrs. love the boat. Been on boats most of life and familiar with jet drive (own 97’ gtx - grandfather pass down) somewhat.

Had been out on the water most of the day and was heading back on Ohio river (gross I know but super close) running full throttle at 47/48 mph, smooth water for no more then 5 miles. Almost back and both check engine and overheat warning came on screen.
Immediately slowed down and placed in center position “neutral”. Opened engine cover, and everything felt and seemed normal. All 3 pissers were flowing continuously and same as always.
Tried moving forward, only got be limited, makes sense. Shut everything down.
Check everything you can quickly do on the water, absolutely 0 debris.
Started up after few minutes, came back on so limped to the ramp and was able to trailer. After I looked everywhere, even with the help of service manual, no luck.
Finally gave up took to dealership 1.5hrs away. They said, they see the code and tested with 0 issues.
Got it home, ran for 1 minute, no water and came on in 45 seconds.

What am I missing here?

What do you mean “ran for 1 minute no water came on in 45 seconds”? Did you run it on the trailer with no flush water going to the engine?

 

[zipper]

What do you mean “ran for 1 minute no water came on in 45 seconds”? Did you run it on the trailer with no flush water going to the engine?

I assumed low hose water pressure and no water emitted from pilot thruhulls. Butt I ASSUME.

 

[FSH 210 Sport]

Sounds to me like he sucked something up on the river and when he slowed down it cleared.

 

[Jtmains]

Sounds to me like he sucked something up on the river and when he slowed down it cleared.

What do you mean “ran for 1 minute no water came on in 45 seconds”? Did you run it on the trailer with no flush water going to the engine?

Yes exactly. More to get what remaining water could be lingering

 

[Jtmains]

I assumed low hose water pressure and no water emitted from pilot thruhulls. Butt I ASSUME.

Haha your assumption is correct

 

[Jtmains]

Sounds to me like he sucked something up on the river and when he slowed down it cleared.

Honestly what I was thinking. I’m confused because dealership says they see code on ecu, reset it and ran with 0 issues.

Bring it back home and throws the code again