#Mobula6 won't arm anymore

1 messages · Page 1 of 1 (latest)

ebon halo
#

I have a Mobula6 with Flight Controller 4.5.0 BTFL running on it. It is bound to a Radiomaster Zorro running ELRS 3.3.0 CE_LBT and in Betaflight Configurator I can see all the inputs in the "Receiver" tab. ARM is assigned to the switch which is on AUX 4 and in the "Modes" tab when I switch it it is clearly within the slider range and the ARM "header" is getting red. In the "Motors" tab I can test every single motor successfully. When I disconnect the drone from the Betaflight Configurator and attach the battery the Zorro says that the connection was recovered but still... using the ARM switch doesn't do anything from here. What could go wrong here?

#

These are the outputs of “version”, “status” and “diff all”:

#

version

Betaflight / STM32F411 (S411) 4.5.0 Jun 25 2024 / 06:06:01 (c155f5830) MSP API: 1.46

config rev: 932b5c6

board: manufacturer_id: HAMO, board_name: CRAZYBEEF4SX1280

#

status

MCU F411 Clock=108MHz (PLLP-HSE), Vref=3.30V, Core temp=53degC
Stack size: 2048, Stack address: 0x2001fff0
Configuration: CONFIGURED, size: 3779, max available: 16384
Devices detected: SPI:1, I2C:0
Gyros detected: gyro 1 locked dma
GYRO=ICM42688P, ACC=ICM42688P
OSD: MSP (53 x 20)
BUILD KEY: 76bf8c4fa405f97ad412d0e517be475a (4.5.0)
System Uptime: 110 seconds, Current Time: 2024-07-08T10:39:04.175+00:00
CPU:65%, cycle time: 126, GYRO rate: 7936, RX rate: 249, System rate: 9
Voltage: 413 * 0.01V (1S battery - OK)
I2C Errors: 0
GPS: NOT ENABLED
Arming disable flags: LOAD CLI MSP

#

diff all

version

Betaflight / STM32F411 (S411) 4.5.0 Jun 25 2024 / 06:06:01 (c155f5830) MSP API: 1.46

config rev: 932b5c6

start the command batch

batch start

reset configuration to default settings

defaults nosave

board_name CRAZYBEEF4SX1280
manufacturer_id HAMO
mcu_id 001c003e3233510c39363337
signature

feature

feature TELEMETRY
feature LED_STRIP
feature OSD

aux

aux 0 0 3 1300 2100 0 0
aux 1 1 2 1300 1700 0 0
aux 2 2 2 900 1300 0 0
aux 3 35 0 1800 2100 0 0

master

set acc_calibration = 18,-32,10,1
set yaw_motors_reversed = ON
set osd_disarmed_pos = 2389
set expresslrs_uid = 0,0,224,245,74,48
set expresslrs_rate_index = 1

profile 0

profile 1

profile 2

profile 3

restore original profile selection

profile 0

rateprofile 0

rateprofile 0

set rates_type = QUICK
set roll_rc_rate = 108
set pitch_rc_rate = 106
set yaw_rc_rate = 100
set roll_srate = 100
set pitch_srate = 95
set yaw_srate = 70

rateprofile 1

rateprofile 2

rateprofile 3

restore original rateprofile selection

rateprofile 0

save configuration

save

#

(Do the “#” from the output make the text go bold?)

raven spire
#

Arming disable flags: LOAD CLI MSP
LOAD means the CPU load is very high

sturdy mortar
#

You said Arm is asigned to Aux 4 but with ELRS Arm needs to be asigned to Aux 1.

#

May be not the main reason of your problem but may leads to other problems.

ebon halo
raven spire
#

post that support id so we can check the full configuration of the flight controller

ebon halo
ebon halo
raven spire
#

what about a GPS?

#

this configuration still shows you have arming on aux4

#

feature -LED_STRIP
set pid_process_denom = 2
save

#

if you're not using digital fpv systems, reflash the flight controller without OSD(HD) in the cloud build options

Also remove everything else you're not ever going to use on this drone to make the firmware footprint smaller and lighter for the F411 mcu

#

e.g. GPS, Acro Trainer, LEDSTRIP, PINIO

ebon halo
raven spire
ebon halo
raven spire
raven spire
#

so again, reflash your flight controller without the build options you're not ever gonna need to make the firmware footprint smaller and lighter for the f411 fc you have

make sure to save a backup of the current configuration (via presets tab or via diff all command)
after reapplying your backup, after the reflash, type these commands on the CLI

feature -LED_STRIP
set pid_process_denom = 2
save
then after reconnecting, save another backup

ebon halo
ebon halo
ebon halo
ebon halo
# raven spire so again, reflash your flight controller without the build options you're not ev...

So here is what happened: I did flash betaflight 4.5.0 after removing GPS, Acro Trainer, LEDSTRIP and OSD HD. I loaded the config backup and entered your three cli lines. I bound the Zorro and set ARM to AUX 1. I connected the battery armed and IT WORKED! When I wanted to fly I noticed that the rotation direction was wrong. I flipped the reverse switch in configurator, saved but ever since then the OSD on my goggles say “CPU overload” and the arming is not working anymore. Even in configurator it always says “load” in the “arm disabled flags”.

raven spire
#

"motors are reversed"?

ebon halo
# raven spire "motors are reversed"?

Yes but I got it wrong again. Now I set each motor individually to push the air down, great. But my problem stays the same with “CPU overload”

raven spire
ebon halo
raven spire
ebon halo