Happymodel Mobula6 HDZERO

To Next Page

1. The Default Arm/Disarm switch for is AUX1(Channel 5),and you can also Mobula6 HDZERO

customize it with Betaflight Configurator.

3.The default channel map for Mobula6 HDZERO version is TAER1234. Please make sure your

transmitter is matched, otherwise it wouldn't be armed. Toggle the AUX1 Switch ,the Green LED

on the flight controller will getting to be solid, this indicates the motor was armed . And also you

can found“Armed" notice displayed on your FPV Goggles or the FPV Monitor. Please make sure

keep the Mobula6 HDZERO level before arming .Be careful and Happy flying !

The following settings are reserved from out of factory. Sometimes maybe you need it after you

updated firmware.Please set Receiver mode to be SPI RX Support from the Configuration tab of

the Betaflight Configurator, then select Frsky_D for Frsky D8 protocol or Frsky_X for Frsky D16

protocol .Don't enable Serial RX since the Superbee F4 Frsky Flight controller is integrated SPI

Receiver.

2.Turn on the Radio transmitter (Use TX16S as an example) and move to the MIXES interface, Set

CH5 channel to "SF" or other aux channel to ARM/DISARM the motor

Specifications

Brand Name: Happymodel

Model: Mobula6 HDZERO

Frame wheelbase: 65mm

Weight: 23.5 gram without battery

Size: 80mm*80mm*50mm

Receiver option:

SPI ELRS 2.4GHz

SPI FRSKY 2.4GHz

Compatible with 1S Lipo battery or Lihv battery

Battery Plug: PH2.0

Package includes

Qty

Item Name

Mobula6 65mm frame+Canopy

SPI Receiver Option1: SuperbeeF4 Lite FC built-in ExpressLRS SPI RX

SPI Receiver Option2: SuperbeeF4 Lite FC built-in Frsky SPI RX

EX0802 KV19000 Unibell brushless motor

Gemfan 1210 31mm propeller(4cw+4ccw)

HDZero Nano Lite Camera

HDZero Whoop Lite VTX

Spare Canopy

Propeller disassemble tool

Screw driver

Bind procedure video

https://bit.ly/39SvE0r

1). Connect Mobula6 HDZERO with computer by Plug USB. Running Betaflight configurator and

then move on Receiver tab then hit “Bind Receiver”. Or move to CLI command and then type "

bind_rx" code .The Red LED on the flight controller would get to be solid, it means the onboard

SPI Frsky receiver is in bind mode.

Notice: The HDZERO whoop lite vtx and nano lite camera can only working while battery was

connected. USB couldn't supply for the whoop lite vtx module and nano lite camera.

TX1 pad was used for Smartaudio

TX2 and RX2 were used for MSP

2).The default SPI Receiver provider is set to Frsky_D, that means you need to bind with your Frsky

D8 radio transmitter or other radio with Frsky D8 tx module. Turn on your radio and move to model

setup ,then hit B . The RED LED of the ﬂight controller would start to blinking , it means bind ind

successfully.

If you want to use other protocol , Please change Receiver provider to "FRSKY_X" for D16 radio,

and Change to "REDPINE" or "SFHSS" to match REDPINE TX module or Futaba Radio.

Frsky D8

Frsky D16

M4 C_

M4 B_

M4 A_

M3 A_

M3 B_

M3 C_

LIPO IN_ +

GND

M1 A_

M1 B_

M1 C_

M2 A_

M2 B_

M2 C_

T 1X

R 2X

+5V

GND

BUZ-

I 1R

LED strip_

GND

+5V

R 1X

T 2X

Vin

Vout

Superbee F4FR lite v1.0

LIPO IN_ +

Need help?

Do you have a question about the Happymodel Mobula6 HDZERO and is the answer not in the manual?

Summary

Mixer Type and ESC;Motor Protocol

Props Out

Instructions for correctly installing propellers on CW and CCW motors for optimal flight performance.

Flight Controller Firmware Update

Flip Over After Crash Procedure

This document describes the Happymodel Mobula6 HDZERO, a 1S 65mm HD whoop Frsky version, focusing on its setup, maintenance, and operational features.

Function Description

The Mobula6 HDZERO is a compact, lightweight drone designed for indoor and outdoor flight, featuring HD video transmission. It utilizes a quad-X mixer configuration with specific propeller rotation directions for optimal flight stability. The drone is equipped with ESCs (Electronic Speed Controllers) that support DSHOT300 protocol and include features like motor stop, bidirectional DShot, and ESC telemetry. The flight controller is configured with default PID settings for roll, pitch, and yaw, and includes options for adjusting damping, D gains, and feedforward. It also incorporates a VTX (Video Transmitter) for real-time video feedback, with configurable bands, channels, and power levels. The device supports firmware updates for both the ESCs and the flight controller, ensuring it can be kept up-to-date with the latest performance enhancements and bug fixes. A "Flip over after crash" function is available to help recover the drone if it lands upside down.

Usage Features

To begin using the Mobula6 HDZERO, users must first ensure the propellers are correctly installed: CW propellers on M2 and M3 motors, and CCW propellers on M1 and M4 motors. The motor direction is reversed, which is a key configuration detail.

For ESC setup and firmware flashing, users need to download the BLHeliSuite software. The flight controller is connected to a computer via USB. It's crucial to check the COM port serial number in Device Manager; if it's above 255, it needs to be adjusted to ensure proper connection with BLHeliSuite. Within BLHeliSuite, users select "SILABS BLHeli Bootloader (Cleanflight)" and the correct serial COM port to connect. Firmware updates for the ESCs can be performed here, with the target firmware being "S-H-50" and the recommended BLHeli_s revision being JazzMaveric (16.80 BLS) to support RPM Filter. The BLHeliSuite interface allows for reading and writing ESC setup, checking ESC details, and flashing firmware.

The VTX channels can be switched in two ways. First, by connecting the battery and USB, then accessing the Video Transmitter tab in the Betaflight configurator to select the band and channel and save. Second, by disarming the drone and moving the transmitter sticks (THR MID + YAW LEFT + PITCH UP) to enter the OSD Menu, navigating to Features, then VTX SA to set the VTX Band and channel.

For flight controller firmware updates, several steps are required. Users need to install the latest STM32 Virtual COM Port Driver and the STM BOOTLOAD Driver (STM Device in DFU MODE). Betaflight configurator is then opened, and the firmware target "CRAZYBEEF4FR" and the desired firmware version are selected. The drone can be put into DFU Mode either by soldering the boot pad and plugging in USB, or by loading Betaflight firmware and hitting "flash," which will automatically put it into DFU Mode. After this, Zadig tools are used to replace the drivers from STM32 Bootloader to WINUSB Driver. Finally, the flight controller is reconnected to the computer, and Betaflight Configurator is used to load and flash the firmware.

The "Flip over after crash" feature is activated by setting one channel of the radio transmitter in the Mode tab of Betaflight configurator. The default switch for this function is AUX4 (Channel 8). This allows users to recover the drone by flipping it over if it lands upside down, without needing to physically retrieve it.

Maintenance Features

Regular maintenance involves checking and updating firmware for both the ESCs and the flight controller. The BLHeliSuite provides an interface to flash new ESC firmware, ensuring the drone benefits from performance improvements and bug fixes. Similarly, the Betaflight configurator, in conjunction with specific drivers and tools like Zadig, facilitates updating the flight controller firmware. This proactive approach to firmware management helps maintain the drone's optimal performance and stability.

The ability to adjust PID settings in Betaflight configurator allows users to fine-tune the drone's flight characteristics to their preference or to compensate for wear and tear on components. The VTX settings, including power levels, can also be adjusted, which is useful for managing heat and optimizing video range depending on the flying environment.

The detailed instructions for connecting to BLHeliSuite and Betaflight, along with the driver installation steps, are crucial for troubleshooting and maintaining the drone's electronic components. The emphasis on checking COM port numbers and using specific drivers highlights the importance of proper software and driver management for the longevity and functionality of the device.