JeffRad54
Well-known member
- Joined
- Jul 23, 2019
- Messages
- 197
- Fluid Motion Model
- C-28
- Hull Identification Number
- FMLT2740K819
- Non-Fluid Motion Model
- None now
- Vessel Name
- MARGAUX
My chart plotter (Garmin 7612 xsv) Range (mpg x gallons remaining) has been acting strange the last month.
For example, with 140 gallons getting 5 mpg, the chart plotter may show 550 miles, or 170, or 22, or 0, or anything in between.
I'm not sure where the chart plotter gets it's info, but the Yamaha Engine Display (YED) shows the mpg and gph, which seems to be accurate based on prior observations. Also, the YED fuel level (bars) is close to what the chart plotter displays.
i.e., the YED shows 9 bars and the chart plotter shows 140 gallons with 150 gallons capacity. It's not exact, but it is reasonable.
The variance happens during a trip. I can start showing xxx miles (incorrect) and then it will go up or down.
If I stop to anchor, it invariably shows 0.0 when I start up again.
Oh, I doubt it is a software update issue. The chart plotter software was updated long before this problem arose recently.
Do I call Garmin, or Yamaha?
Anyone else had this problem?
Thanks,
Jeff
For example, with 140 gallons getting 5 mpg, the chart plotter may show 550 miles, or 170, or 22, or 0, or anything in between.
I'm not sure where the chart plotter gets it's info, but the Yamaha Engine Display (YED) shows the mpg and gph, which seems to be accurate based on prior observations. Also, the YED fuel level (bars) is close to what the chart plotter displays.
i.e., the YED shows 9 bars and the chart plotter shows 140 gallons with 150 gallons capacity. It's not exact, but it is reasonable.
The variance happens during a trip. I can start showing xxx miles (incorrect) and then it will go up or down.
If I stop to anchor, it invariably shows 0.0 when I start up again.
Oh, I doubt it is a software update issue. The chart plotter software was updated long before this problem arose recently.
Do I call Garmin, or Yamaha?
Anyone else had this problem?
Thanks,
Jeff