Complete Speedybee F405 V4 Flight Controller Wiring Guide with Diagram

For optimal performance, route the 5V BEC output from the integrated power module to the flight controller’s dedicated pad–typically labeled 5V_IN or VBAT. Avoid powering servos or high-current peripherals from this rail; use a separate 5V regulator rated for at least 3A if additional devices are required. The board’s built-in current sensor (INA169) connects via CURR and VSENSE pads, but verify voltage scaling in Betaflight–default values often assume 50A/3.3V scaling before adjusting.

Motor outputs follow the M1–M4 sequence, matching standard quadcopter conventions. For reverse motor direction, swap any two signal wires or invert via CLI (resource MOTOR 1 NONE; resource MOTOR 2 A02). ESC telemetry (if supported) connects to TX1; ensure the UART is configured for “ESC Telemetry” in the ports tab. Bidirectional DShot requires a DMA-enabled output–check Betaflight’s resource mapping (resource list) to confirm availability on M1–M4.

USB port (PA11/PA12) shares interrupts with serial Rx (PA10); disconnect peripherals if debugging serial issues. For GPS, wire TX→RX and RX→TX (UART1 default), then set baud rate to 57600 in Betaflight. Barometer (MS5611) connects via I2C (SCL/SDA on PB6/PB7); pull-up resistors (4.7kΩ) are required if not present on the sensor. SD card logging utilizes SPI1 (PA5/PA6/PA7); verify the card’s formatting (FAT32, 512-byte allocation) to prevent write errors.

LED strip (if used) taps into PA8 (DMA-free) or any spare motor output. Avoid exceeding 500mA total draw; use a logic-level shifter if driving high-power LEDs. For FrSky receivers, connect SBUS to RX2 (PA3) and SmartPort to TX2 (PA2), then enable “Serial RX” and “Telemetry” in Betaflight. Crossfire/Tracer requires CRSF (UART3, PD2), with baud rate set to 420000.

Guide to Connecting Your Flight Controller Board V4

Start by powering the main circuit via the 5V BEC port if using a standalone power module. Connect the positive lead to the VCC pad and the ground to any GND pad–this ensures stable 5V input for the MCU before battery voltage fluctuates. Avoid powering through USB alone for prolonged configuration, as some peripherals may not initialize correctly.

Route ESC signals through the dedicated motor outputs labeled M1-M4, matching the flight stack’s motor rotation order (Betaflight defaults to CW on M1/M4). Use 20-22 AWG silicone wires for servo connections if integrating a gimbal or camera trigger; heavier gauge risks solder pad damage. For digital protocols like DShot, ensure signal wires are twisted with ground to minimize EMI.

Assign UART ports for telemetry and receiver input. UART1 (TX1/RX1) typically handles FrSky or ExpressLRS receivers, while UART3 often serves GPS modules–verify baud rates in firmware settings (e.g., 115200 for GPS). Connect SBUS or CRSF receivers to the designated RX pad, but never combine voltages: power the receiver from a 3.3V or 5V pad depending on model specifications.

For OSD or blackbox logging, use SPI2 (CLK, MISO, MOSI, CS pads) with a MAX7456 chip or flash memory module. Solder wires in a star topology from the pads to avoid signal interference–keep SPI traces shorter than 5cm where possible. Verify SPI mode in CLI (`set osd_spi_mode = 1`) if display corruption occurs. Capacitors (220-330µF) across the main power input pads dampen voltage spikes during throttle bursts.

Double-check polarity on all auxiliary connections (LED strips, buzzers) to prevent short circuits. LED strips typically draw 5V from a dedicated pad near the USB port, but confirm current limits (max 2A on most boards). For buzzer circuits, add a 1N4148 diode in reverse across leads if using a mechanical buzzer to suppress voltage spikes that could reset the flight stack.

Integrating the V4 Board into Your Quadcopter Control System

Begin by securing the autopilot module to the drone frame using silicone grommets to dampen vibrations. Position it centrally, aligning the arrow on the PCB with the forward direction of the aircraft. This ensures accurate sensor readings and prevents skewed telemetry.

Power distribution requires careful attention–connect the main battery lead to the designated pad labeled “VBAT” using a 12AWG silicone wire for currents up to 60A. For redundant power, solder a secondary 5V BEC to the “5V” pad, but only if your peripherals draw less than 2A combined; exceeding this risks thermal throttling.

Key connections for stable operation:

• ESCs: Link each motor output (S1-S4) to the corresponding signal pad. Use 22AWG silicone wires and twist pairs to minimize electromagnetic interference. Avoid daisy-chaining ground wires–run each back to a common ground point on the board.
• Radio receiver: For SBUS, solder the signal wire to the “RX3” pad. For CRSF, use “TX3/RX3” in full-duplex mode. Ensure the UART is enabled in firmware with a baud rate of 115200.
• GPS module: Attach the TX/RX wires to “TX1/RX1” and power via “5V”. Mount the module at least 5cm above other components to avoid magnetic interference.

Voltage sensing is critical for battery monitoring. Connect the balance lead of your LiPo to the “VBAT” and “CURR” pads using the included 30A shunt resistor. Calibrate the settings in Betaflight/INAV by entering the battery cell count and adjusting the voltage divider ratio to match your setup.

For telemetry, wire the “TX2/RX2” pads to an external transmitter like an ESP32 or Crossfire module. Configure the UART in the CLI with:

1. set serialrx_provider = CRSF
2. set telemetry_inverted = OFF
3. save

Avoid routing signal wires parallel to power cables longer than 3cm–this introduces noise. If unavoidable, shield the wires with aluminum foil grounded at one end. For LED strips, use the “LED” pad with a 300Ω resistor to prevent backfeeding.

After soldering, flash the latest firmware via DFU mode. Disconnect all peripherals first, then hold the boot button while plugging in USB. Use STM32CubeProgrammer or Betaflight Configurator to upload the binary. Verify gyro alignment by spinning the drone gently–the movement on your OSD should match the physical rotation.

Final checks include verifying failsafe triggers. Set the receiver to output a predefined position (e.g., 1500µs for neutral) on signal loss. Test by powering off the remote while armed–the drone should enter return-to-home or land mode within 1 second.

Step-by-Step Guide to Powering ESCs with the Flight Controller Board

Begin by verifying the BEC voltage output from your electronic speed controllers meet the board’s input requirements. Most modern ESCs deliver either 5V or 9V; the target module accepts 5V exclusively via its integrated regulator. Using a multimeter, confirm each ESC’s BEC outputs a stable 5V before proceeding to avoid overvoltage damage to sensitive components.

Locate the dedicated power pad cluster on the controller PCB, typically marked “5V,” “VBAT,” or “PWR.” These pads connect to the board’s internal power distribution network. Use 20-24 AWG silicone-insulated wire for these connections–thinner wires risk voltage drop under load, while thicker wires complicate soldering in confined spaces.

Prepare ESCs by trimming and tinning their BEC positive and ground wires. Avoid twisting wires together; instead, keep them parallel to prevent inductive noise from coupling into signal lines. For quadcopters, route ESC power wires radially outward from the center, maintaining equal lengths to balance current distribution and minimize weight imbalances.

• Solder the ESC’s 5V BEC positive wire to the controller’s “5V” pad.
• Attach the corresponding ground wire to the adjacent “GND” pad.
• Repeat for each ESC, ensuring no unintended shorts between pads.

After soldering, apply heat-shrink tubing or liquid electrical tape to insulate exposed joints. Avoid using standard tape–it can degrade under vibration or temperature cycles, leading to intermittent failures. For added reliability, secure wires with zip ties to nearby mounting posts or the frame’s structural elements to prevent strain on solder joints during flight.

Test each connection individually before final assembly. Power the system via a lab power supply set to 3.7V (simulating a single LiPo cell) and check for unexpected behavior: rapid beeping, LED flickering, or unusually high current draw. If any ESC fails to initialize, re-examine solder joints under magnification for cold joints or bridges.

Once all ESCs respond normally, verify voltage consistency across the board’s output rails. A deviation exceeding ±0.1V suggests improper grounding or a faulty connection. Use a low-ESR capacitor (100μF to 330μF) across the power input pads if voltage spikes occur during motor spin-up–this dampens transient loads from high-Kv motors.

Critical Troubleshooting Checks

1. Ensure the board’s firmware supports ESC telemetry if using protocols like DShot with bidirectional communication. Mismatched firmware can cause erratic motor behavior.
2. If encountering Brown-Out Detection (BOD) errors, add a secondary power source (e.g., 1S LiPo) to the “VBAT” pad for redundancy.
3. Inspect for overheating near the power regulator–excessive heat indicates incorrect load balancing or insufficient cooling.

Connecting GNSS and Magnetic Sensor Units to the Flight Controller Board

Use the dedicated UART port marked for satellite navigation modules–typically labeled “GPS” with RX/TX pins clearly identified. Most modern GNSS receivers like Ublox M10 or Matek M8Q require direct soldering to these pads, ensuring minimal signal interference. Match the TX output of the sensor to the RX input on the board and vice versa. If utilizing a combined module with a built-in magnetometer, connect the I2C lines to the corresponding SDA/SCL pads, usually situated near the microcontroller’s core.

For reliable positioning, mount the GNSS antenna facing upward with an unobstructed sky view, ideally on a carbon fiber or non-conductive mast to prevent RF noise from onboard electronics. Avoid placing magnetic sensor units near power distribution boards, ESCs, or high-current wires, as electromagnetic fields distort compass readings. A 10 cm separation from any motor or battery cable is the minimum recommendation.

Power the module via the 5V or 3.3V output on the controller, verifying voltage compatibility with the device datasheet. Some GNSS units tolerate 5V, while compass chips strictly require 3.3V–exceeding this risks permanent damage. Use twisted pair wiring for I2C connections to reduce susceptibility to external interference. If the module lacks built-in capacitors, add a 100nF ceramic capacitor near the power input for stable operation.

Enable the appropriate serial protocol in the firmware configuration: UART1 for Ublox binary (UBX), UART2 for NMEA parsing. Assign the correct baud rate–usually 38400 or 57600 for most receivers. For magnetometers, ensure the I2C bus is active and the correct device address is selected; common addresses include 0x0D (QMC5883L) or 0x1E (HMC5883L). Calibrate the compass after installation using ground station software, rotating the craft through all axes until interference-free readings are achieved.

Secure wiring with silicone-insulated strands for flexibility and heat resistance, especially if routing near hot components like regulators. Avoid solid-core wires in high-vibration environments. For redundancy, some pilots integrate a secondary GNSS module via an additional UART, requiring independent power and ground connections. Confirm signal stability by monitoring satellite count and HDOP values during bench tests–target at least 12 satellites with HDOP below 1.2 for precision navigation.

Post-installation, validate the setup by checking sensor status in the flight software. If the compass displays erratic values or fails to initialize, re-examine solder joints, I2C pull-up resistors, and ground plane integrity. For GNSS issues, verify the antenna connector’s SMA interface is fully engaged and the coaxial cable’s shielding is intact. Log data during test flights to analyze trajectory accuracy and heading consistency, adjusting PID values if necessary to compensate for residual magnetic interference.