#error-code

Recently, while tacking 90° in a light breeze, my Yanmar 30HP 2.6 outboard flashed an E3 error. The error pops up exactly when the prop pitch sensor registers a dead zone after the gear shift. I've checked the wiring harness, the sensor connector, and the ECU, all seem fine. But the error persists. Anyone else experienced this? What steps should I take? I'm not sure if it's a sensor fault, a calibration issue, or a software glitch.

• Model: Yanmar 30HP 2.6 outboard
• Error code: E3 (prop pitch sensor dead zone)
• Conditions: 90° tack, light breeze, 1st to 2nd gear shift
• Diagnostics done:
  • Visual inspection of wiring harness – no frays
  • Sensor connector – clean, no corrosion
  • ECU reset – error still present
  • Firmware version 1.2.3 – latest
• Symptoms: engine stalls briefly, then resumes, but error remains

Possible solutions I'm considering:

• Recalibrate the prop pitch sensor via the Yanmar diagnostic tool
• Replace the sensor module (model YAN-PS-01)
• Check for any updates to the ECU firmware that address E3
• Look into the mechanical linkage of the prop pitch mechanism

Any detailed steps, or has anyone found a quick fix? If this is a known bug, a link to a forum thread or a service bulletin would help. I'm not looking for a generic 'reset the boat' solution. I need a concrete fix.

Thanks, and let me know if you have data on this issue.

I've been encountering a persistent DOG-404 error on my 2023 Labrador X-Model 4.2. The issue surfaces every time the SmartFeeder 3000 initiates a feeding cycle. The feed log shows:

• Timestamp: 14:32:07
• Error code: DOG-404
• Firmware: v2.5.1
• GPIO pin: 12
• I2C bus: 1

The dog refuses to eat and the feeder lights up red. I’ve tried:

• Resetting the feeder (power cycle, 30‑second wait) • Updating firmware to 2.5.2 (still DOG-404) • Replacing the feed dispenser module (same error) • Checking the I2C cable for continuity (no fault)

The error seems to correlate with the dispenser’s motor drawing 0.8A instead of the spec’d 0.5A. Could this be a firmware bug or a defective motor? Any known patches or workarounds? Also, does anyone know if the X-Model 4.2 has a known compatibility issue with the 3000’s 2.5.x firmware? Any insights would help.

Thanks.