DIY eFoil Troubleshooting Guide: Fix Every Common Problem

1. Check the anti-spark switch. If you have a physical switch (Flipsky, Trampa), is it fully engaged? Some switches have a lock position. Try cycling it off and on. If it's an XT90-S connector, make sure it's fully seated — partial insertion only engages the pre-charge resistor.
2. Measure battery voltage at the connector. Disconnect the ESC side and measure directly at the battery output. If you read 0V or significantly below nominal (e.g., below 36V on a 12S), the BMS has locked out or a cell group has died.
3. Check the fuse. If your build has an inline fuse (it should), inspect or test it with a multimeter in continuity mode. Blown fuses are invisible from the outside on many automotive-style fuses.
4. Inspect all connectors in the power path. Corrosion, melted plastic, blackened contacts, or green deposits on bullet connectors all indicate a failed connection that may have opened the circuit entirely.
5. Bypass the switch temporarily. If you suspect the anti-spark switch has failed, carefully connect the battery directly to the ESC through an XT90-S (for anti-spark protection). If the ESC powers on, the switch is the problem.

1. Battery voltage too low. The ESC powers on using residual capacitor charge, detects undervoltage on the actual battery, and shuts down. Measure pack voltage — if it's below the ESC's configured cutoff start voltage, you need to charge the battery first.
2. BMS is tripping under load. Even the small load of the ESC powering on can trip a BMS that has a cell group near its low-voltage cutoff. Check individual cell group voltages through the balance connector.
3. Loose connection causing voltage drop. A high-resistance connection can supply enough current for initial capacitor charge but sag below cutoff under sustained draw. Wiggle connectors while watching ESC status lights.

1. Check receiver binding. Is the receiver LED showing bound status (usually solid)? If it's flashing, the receiver has lost its pairing with the transmitter. Re-bind according to your specific receiver's procedure.
2. Verify the transmitter is on and charged. Dead remote battery is embarrassing but accounts for a surprising number of "motor won't work" reports.
3. Run motor detection (VESC). Connect via USB/Bluetooth, open VESC Tool, go to Motor Settings → FOC → Motor Detection. If detection fails, you likely have a phase wire issue (open connection, short between phases, or water damage to motor windings).
4. Check PPM/UART signal. In VESC Tool, go to App Settings → PPM and watch the "Decoded" value while moving the throttle. If it doesn't change, the signal wire between receiver and ESC is the problem — check the cable, connector, and pin assignment.
5. Verify app configuration. In VESC Tool, make sure the correct app is selected (PPM for most remotes, UART for some smart remotes) and that it's configured on the right port. A factory-reset VESC has no app configured — you must set this up.

1. Motor detection was not run or failed. The VESC needs accurate motor parameters (flux linkage, resistance, inductance) to drive the motor correctly. Re-run motor detection with the prop off and the motor free to spin.
2. One phase wire is disconnected or has high resistance. With only two of three phases connected, the motor will cog and vibrate but not spin. Check all three phase wire connections at both the ESC and motor ends.
3. Hall sensor issue (if applicable). If using sensored mode, a failed Hall sensor causes the motor to stutter at low speed. Switch to sensorless mode in VESC Tool as a test — if the motor runs smoothly at higher RPM, the Hall sensor or its wiring is the problem.
4. Current limits set too low. If motor current is set below what's needed to overcome static friction and water resistance, the motor will try but fail to spin under load. Check VESC Tool motor current limits — most eFoil motors need at least 40-60A motor current to start reliably.

1. Check VESC fault log. This is step one, every time. Connect VESC Tool, open Terminal, type faults. The fault code tells you exactly what happened. Skip this step and you're guessing.
2. Loose phase wire connection. The #1 cause of intermittent cutouts. Vibration from riding loosens bullet connectors, especially if they weren't crimped tightly or if corrosion has started. With the board open, tug-test every phase connection firmly. If any connector moves at all, that's your problem.
3. BMS overcurrent protection. Many BMS units have a continuous discharge limit lower than peak motor draw. Aggressive acceleration can trip the BMS, which disconnects the battery for a few seconds before resetting. Check your BMS discharge rating versus your actual peak current draw. If they're close, the BMS is the limiter.
4. Battery voltage sag. Under heavy load, a battery with degraded cells or insufficient capacity sags below the ESC's cutoff voltage. The ESC cuts power to protect the cells, then voltage recovers when load is removed. Check voltage under load — not just resting voltage.
5. Water in the ESC compartment. Even a few drops on the wrong place can cause a momentary short that triggers a fault. Open the board after a session and look for moisture, water trails, or condensation on electronics.

1. Radio interference / signal loss. The receiver antenna position matters enormously. If the antenna is coiled up inside the board near the motor wires or ESC, EMI from the high-current switching can cause momentary signal dropouts. Route the antenna to a window in the board shell, away from power electronics.
2. PPM signal noise. In VESC Tool, check PPM input with the app wizard — look for jittery or noisy decoded values. Add a ferrite bead on the signal wire near the ESC if noise is present. Some builders route signal wires on the opposite side of the board from power wires.
3. Failsafe triggering. If the VESC's failsafe is configured to cut throttle on signal loss, even a momentary dropout triggers a brief power cut. Make sure failsafe is set to "current off" rather than "brake" to avoid sudden deceleration.
4. Transmitter low battery. As the remote battery drops, transmit power decreases and signal integrity degrades. Charge the remote before every session.

1. Check if water cooling is flowing. If you have a water-cooled ESC, verify the water intake isn't blocked (debris, prop wash not reaching intake). Run on land briefly and check if the cooling loop has flow by feeling the output hose.
2. Reduce motor current limits. If the ESC is air-cooled and overheating on long rides, reduce motor max current by 10-15% in VESC Tool. You'll lose some top speed and acceleration but the ESC will survive to ride again.
3. Add thermal padding to the enclosure. Contact between the ESC heatsink and an aluminum plate (or the board shell itself if it's aluminum) provides passive heat sinking. Thermal pads from laptop repair kits work well.
4. Check motor timing and detection values. Incorrect motor parameters make the ESC work harder to drive the motor, generating excess heat. Re-run motor detection and compare parameters to known-good values from other builders with the same motor on FOIL.zone.

1. Check prop pitch and diameter. An oversized or steep-pitch prop loads the motor beyond its efficiency sweet spot, turning excess energy into heat. Compare your prop specs to what others use with the same motor on FOIL.zone.
2. Water ingress into motor can. If water gets past the shaft seal and sits against the stator, it accelerates heating and corrosion. After a session, spin the motor by hand — grinding or resistance that wasn't there before suggests water or corrosion inside.
3. Bearing failure. A seized or rough bearing adds constant drag. Spin the motor shaft by hand — it should spin freely with a slight magnetic cogging. If it feels gritty, tight, or rough, the bearings need replacement.
4. Sustained high-current riding style. Continuous full-throttle riding generates the most heat. If thermal issues only appear during aggressive riding, consider a larger motor, better cooling, or adjusting riding style to include glide phases.

1. Check ramping settings in VESC Tool. Acceleration and deceleration ramp rates control how fast the motor responds to throttle changes. If ramp-up time is set too high (e.g., 5+ seconds), throttle feels sluggish. Reduce to 0.5-1.5 seconds for responsive riding, but don't go to zero — some ramping prevents jerky behavior.
2. PPM median filter too aggressive. In VESC Tool PPM settings, a high median filter value smooths out noise but adds latency. Try reducing the filter or adding hardware filtering (ferrite bead) instead.
3. Receiver to ESC communication delay. Some receivers add processing delay. If using UART-based remotes, check baud rate settings match between remote and VESC. PPM is simpler and lower latency for most setups.

1. PPM calibration is off. Open VESC Tool → App Settings → PPM Mapping. With the transmitter at minimum, note the decoded value. At maximum, note the decoded value. Set these as your PPM start and end values. If the range is narrow, you're only using a portion of the available throttle throw.
2. Current limits are the bottleneck. Check motor max current and battery max current in VESC Tool. If battery max current is set low (e.g., 30A on a setup that could deliver 80A), the motor will feel weak at full throttle. Increase in small steps, monitoring temperatures.
3. Battery voltage sag at load. A weak battery that sags heavily under load triggers the ESC's voltage cutoff ramping, which progressively limits power before the hard cutoff. This feels like "the board won't go faster." Check voltage under load, not resting.

1. Check charger LED status. Most eFoil chargers show red (charging) and green (full or error). If the charger shows green immediately on connection, it either thinks the pack is full (measure pack voltage) or it's not making connection (check charge port wiring).
2. Measure pack voltage at the charge port. If it's near full voltage, the pack may actually be charged. If it's near zero or very low, the BMS may have locked out to protect a deeply discharged cell group.
3. Check individual cell group voltages. Use the balance connector to measure each cell group. If one group is significantly lower than the others (e.g., 2.5V when others are 3.5V), that group has weak or dead cells. A BMS with hard undervoltage lockout won't allow charging until the problem cell is addressed.
4. Verify charger voltage matches pack configuration. A 12S charger won't charge a 14S pack, and vice versa. The charger's output voltage must match your pack's full charge voltage (50.4V for 12S, 58.8V for 14S).
5. Test with a different charger if available. Charger failure is less common than BMS issues but does happen, especially with budget chargers that see salt air exposure.

1. Check cell balance. Over many cycles, cells drift out of balance. An unbalanced pack's usable capacity is limited by the weakest group. If your BMS has passive balancing, let the pack sit on the charger for several extra hours after reaching "full" — passive balancing is slow.
2. Measure capacity with a cycle test. Charge fully, discharge at moderate current (not full riding power) while logging energy delivered. Compare to the pack's rated capacity. If you're below 80% of original, the cells are aging and the pack may need replacement or cell swaps.
3. Check for parasitic draw. If the board loses charge sitting unused, something is drawing current when it shouldn't be. Disconnect the battery, measure voltage, reconnect after 48 hours and measure again. If voltage dropped, trace the draw to the ESC, BMS, or receiver staying powered.
4. Consider environmental factors. Cold water significantly reduces lithium cell performance and capacity. If your range dropped when riding conditions changed (summer to winter, tropical to cold water), temperature is likely the primary factor.

You may not see water pooling inside the board. Look for these early indicators:

• Intermittent electrical behavior that changes with board orientation (water pooling on different components as the board tilts)
• White or green crystalline deposits on connectors, solder joints, or PCB surfaces — this is salt corrosion
• Fog or condensation on the inside of the hatch lid or any transparent windows
• Weight gain — weigh your board dry. If it gains 100g+ over sessions without adding hardware, water is accumulating somewhere
• Faint electrical smell when opening the hatch — ozone or burning indicates arcing on wet surfaces

1. Disconnect battery immediately. Do not power on the board. Do not "check if it still works." Disconnect the main battery connector as the very first action.
2. Rinse with fresh water. Counterintuitive, but fresh water displaces salt water. Gently rinse all affected electronics with distilled or clean fresh water. Salt crystals continue corroding as long as they're present.
3. Dry with compressed air. Blow out connectors, between PCB components, and inside cable glands. Air-dry in a warm (not hot), dry space for 24-48 hours. Silica gel packets in the compartment accelerate drying.
4. Inspect under magnification. Use a phone camera macro or loupe to inspect PCB traces, solder joints, and connector pins for corrosion, discoloration, or bridged connections. Pay special attention to fine-pitch IC legs.
5. Clean with 99% isopropyl alcohol. Use a soft brush (old toothbrush works) to scrub away any corrosion or deposits. Isopropyl displaces water and evaporates clean.
6. Reapply conformal coating on cleaned board areas after they're fully dry. This adds a moisture barrier for next time.
7. Find and fix the entry point. Water got in somewhere. Check: hatch seal (worn, misaligned, debris on seal face), cable glands (not tightened, wrong cable diameter), mast base penetration, charge port seal, and any drilled holes.

1. Check prop pitch and motor KV match. Low-KV motor + low-pitch prop = lots of torque but low top speed. High-KV motor + high-pitch prop = high speed but may not have enough torque to start. The motor/prop combination determines your speed ceiling. Compare to proven setups on FOIL.zone.
2. Verify ERPM limit in VESC Tool. If the ERPM limit is set too low, the VESC will cap the motor speed regardless of throttle input. Default is often 60,000 — check yours against your motor's pole count and desired RPM: ERPM = RPM × (pole pairs).
3. Check battery current limit. If your battery max current in VESC Tool is set conservatively (e.g., 30A when your pack can deliver 60A), you're artificially limiting power. Increase carefully while monitoring battery temperature.
4. Board and rider hydrodynamics. A heavy board, high-drag foil, or rider stance that creates extra drag will eat speed that electronics can't overcome. If all electrical parameters check out, the limitation is physical.

1. Prop damage. A chipped, nicked, or slightly deformed prop loses thrust efficiency dramatically. Even damage you can barely feel with your finger can cost 10-15% of thrust. Replace or refinish the prop.
2. Battery degradation. As cells age, internal resistance increases and the pack sags more under load. The ESC starts voltage-limiting earlier in the ride. Compare loaded voltage now vs. when the pack was new.
3. Fouling. Algae, barnacles, or marine growth on the foil, fuselage, or prop add drag. Clean all hydrodynamic surfaces. Even a thin biofilm slime layer measurably increases drag.
4. Motor bearing wear. Worn bearings add mechanical resistance. Compare the drag spinning the motor by hand to when it was new. If it feels noticeably harder to spin, bearings need replacement.
5. Settings changed. Did you update firmware, change VESC parameters, or swap any components recently? Export your VESC config and compare to a backup (you did keep a backup, right?).