#inav

My new mix, hope you’ll like it

My new mix to celebrate over 600 listening on SoundCloud, thanks everyone

Long-range FPV for Hobbyists: A Beginner's Guide

Long-range FPV opens a new side to flying but it also brings extra responsibility, safety checks and legal considerations, so start small and respect local aviation rules and airspace before attempting extended flights.

ExpressLRS, commonly abbreviated to ELRS, is the radio link most beginners should consider for long-range projects because it gives excellent range, low latency and is actively developed, so buy a compatible transmitter module and receiver and learn to flash firmware and set RF power legally and responsibly.

GPS rescue is the single most important safety feature to configure for long-range flights and it works best when integrated with a capable flight controller and OSD, so ensure your FC has a reliable GPS and compass, set a proper home point before take-off and configure rescue/RTH parameters in Betaflight or INAV for altitude, loiter and descent behaviour.

Efficient motors and prop selection determine endurance more than sheer power, so pick motors with an appropriate KV for your battery voltage, match them to a prop that produces good static thrust without excessive current, and use ESCs with low on-resistance and reliable firmware, because reducing current draw and weight is the fastest route to longer flight times.

Antenna placement on both the aircraft and ground station is critical for maintaining link quality, so keep receiver antennas clear of carbon fibre and the motor bell, orient antennas for proper polarisation and diversity where possible, and mount ground-station antennas high and unobstructed to reduce signal shadowing and multipath issues.

Set your failsafe in ELRS and the FC deliberately and test it before each flight, using conservative failsafe actions such as RTH or descend-and-land for long-range work while also ensuring RSSI and link-loss behaviours are visible on your OSD, and remember to read build guides and parts lists on my site WatDaFeck for practical examples and wiring diagrams.

Troubleshooting VTOL Hobby Builds: Transition, Firmware and Wiring Tips.

VTOL aircraft are rewarding but complex projects, and the transition phase between multirotor and fixed‑wing flight is where most problems show themselves, so it pays to approach troubleshooting methodically.

Start with transition programming and flight modes by testing on the bench before first flight, and always use a safety tether when attempting a maiden transition to avoid damage to people or property. Configure a smooth throttle and attitude ramp rather than an instant switch to reduce sudden load on motors and servos, and verify your chosen transition duration in your configurator before flight. Make small incremental changes and test each change in hover to check for unintended yaw or pitch drift during the initial part of the transition.

When using iNav or ArduPilot the diagnostic tools are different but both provide the essential telemetry and logging you need to understand control behaviour. Check iNav Blackbox logs to examine actuator outputs and attitude blending, and use ArduPilot logs in Mission Planner or QGroundControl to inspect servo outputs, PWM values and transition triggers. If you see oscillatory actuator commands during transition, soften the blending curve and add a little integrator damping, and if the aircraft fights the transition adjust mixer priorities or trim down multicopter PID gains temporarily for the transition window.

Tilt mechanisms are a frequent mechanical failure point, so inspect everything for slop and binding before flight and include mechanical stops or limit switches to prevent over‑travel. Use high‑quality metal‑gear servos or dedicated tilt motors with proper reduction gearing and ensure bearings and linkages are free from play while still allowing smooth travel. Fit return springs or dampers if the design can suffer hard landings and consider programmable failsafe positions so that a loss of signal puts tilt surfaces into a safe and predictable attitude.

Wiring errors are another common cause of bizarre behaviour, so follow a clear wiring checklist and keep power and signal paths sensible to reduce electrical noise and brown‑outs. Useful items to include in your pre‑flight wiring checklist are below.

Use a common ground between flight controller, ESCs and receivers while keeping power distribution neat and fused for each rail.

Fit capacitors across battery leads near the ESCs and use twisted signal pairs for long servo or telemetry leads to reduce EMI pickup.

Consider a separate BEC or UBEC for tilt servos if they draw significant current, and make sure the receiver sees a stable voltage during full tilt movement.

Practical bench tests are invaluable: run full transitions with the airframe strapped down and log every channel, then review the log to confirm that commanded servo positions match expected values and that the motor RPMs are being modulated in the correct sequence. If a servo refuses to reach a commanded angle, isolate it and test directly from a servo tester and the flight controller output to distinguish between mechanical, signal or power failure. For build logs, parts lists and a few video demos I often refer readers to my site at WatDaFeck which contains photos and notes from several VTOL projects.

Finally, keep a clear pre‑flight checklist that covers firmware mode selection, failsafe setup, power checks, and a short low‑altitude transition test with plenty of open space, and always be ready to flip back to multicopter mode quickly if the aircraft begins to diverge during the changeover. Small, safe test flights and careful log review will take you a long way toward a reliable VTOL build.