A Yamaha that stumbles while starting, beeps without apparent reason or shows a fault that moves from one sensor to another between rides is worth a battery check before any part gets replaced. This applies to every four-stroke model the M-JET Diagnostic supports, from the 2002 FX140 up to the 2024 FX HO.
Why voltage comes first
The control unit and every sensor it reads work from the supply voltage. When that voltage is low or unstable, the control unit can log faults that have nothing to do with the part named in the entry. That is why sporadic codes spread over several unrelated sensors deserve suspicion of the electrical supply. Battery voltage has its own code as well, 19 on the newer control units and 25 on the older FX140, FX1000, FX1100 and GP1300R generation, and as always the numbers vary between generations and sources, so the app's description is what counts.
What to read
Battery voltage is one of the live values the app shows. Look at it twice.
- With the engine off, as a first impression of the battery. Charge it fully first, otherwise the reading tells you about the charger and not the battery.
- With the engine running and the ski on the water or on a proper water supply, at higher rpm. The reading should rise clearly above what it showed with the engine off, because that is the charging system doing its job.
If the voltage with the engine running barely moves, or sits lower than the resting value, the problem is on the charging side rather than the battery. If the app keeps updating while the starter turns, a reading that collapses during cranking points at the battery or at corroded cables. I wouldn't put a specific volt figure as a threshold here, because it depends on battery type and ski. Comparing the two readings and watching the trend tells you more.
The regulator and rectifier
The voltage regulator and rectifier corrodes on some skis. A single FX140 owner reported alarms and start problems with a corroded regulator, and for the VX1100 the problem is known. In both cases the live data would show a charging voltage that stays too low with the engine running. The scan can point at the symptom. It can't tell you the regulator is the culprit, because corroded connectors elsewhere in the harness can cause the same picture, and that part is a visual check.
Handling the codes
Write down every stored entry before you do anything else. Fix the supply, then clear the memory and ride again. Entries that don't return were probably consequences of the low voltage. Entries that come back with a healthy battery are real, and now you know where to look. The page on clearing the fault memory covers that sequence. Idle and throttle learning are also available in the app, and repeating the idle learning after the battery was changed is reasonable.
What it won't find
A corroded plug that interrupts a circuit without ever setting a code stays invisible to the scan. The same goes for a battery that shows good voltage at rest and gives up under load, unless you catch it in the cranking reading. When voltage looks fine at rest and while running and the faults persist, look at the connectors and ground points by eye and move on from the electrical side.
