Mobula7 failsafe from 30 feet away

[odd geyser]

Hey everyone,

This is my new mobula7 that I'm having issues with an occasional failsafe from short distance. I'll do my best to list the appropriate information below.

Betaflight version 4.3.1
ELRS v.2.5.1
quad is a mobula 7 which uses the x12 AIO board with SPI ELRS using the cube antenna
controller is a zorro with built in ELRS on 50hz max 250mw with dynamic turned on

Any help is appreciated

[foggy carbon]

do you have set VTX Admin in the Lua Script to a Band/Channel?

at what Power Level do you have the VTX set to?

[odd geyser]

Band is set to off
Channel 1
Vtx is set to 25mw here.
I had it turned up to 400 previously and was having these fail-safes so I turned it down in case temp is to blame but this failsafe occurred at 25mw.

[foggy carbon]

could you post an OpenTx/EdgeTx SD Log please with the failsafes

[odd geyser]

I think I just got my radio set up to log that so I will report back.

[crystal nebula]

My mobula 6 does the same if i have my packet rate any lower than 250hz.

[foggy carbon]

that's what I was wondering as well.. why 50Hz?

[crystal nebula]

At least it had a "soft" landing on the bouncy bouncy

[odd geyser]

Good to know. I'll give that a try

[odd geyser]

I just copied that model from a bigger quad where I cared about range. Also in my mind I'm so new a little latency wouldn't matter. I'll bump that up to 250 and give it a go

[foggy carbon]

whoop and range don't mix as much..

[odd geyser]

So I did some more testing today. Raised my packet rate to 250hz. I experienced more frequent failsafes after doing so although many of them were micro failsafes where I recovered control before even hitting ground. I took some logs but I made a mistake in that I set it up to log on my arm switch which meant everytime I failsafed, I would disarm upon hitting the ground and the log would stop. I don't feel like that's ideal for my situation so I can try to set it up on a different switch so my logs don't end immediately upon failsafing. I've attached a log that ends with a failsafe disarm. I can take better logs tomorrow probably.

[foggy carbon]

based off this log, your link isn't the cause of the failsafe... your LQ is 100%, which means your receiver is still getting all of the packets that the tx module is sending.
RSSI dBm is also still high to warrant a failsafe..
BUT your tx power do boost up to 250mW, but it could be that's because you're losing Telemetry (TQLY went to 0 on that last frame) though this shouldn't be a cause for the fc to issue a failsafe.

Recheck your radio setup/config making sure adc filter is OFF etc.

[odd geyser]

Looks like adc filter was on so I turned it off. Will fix my logs and do some more flying tomorrow.

[crystal nebula]

Maybe cpu overload? Just a thought

If all fails you could buy a uart receiver and use that instead.

[odd geyser]

Here's a better log. 3 failsafes during this flight.

[foggy carbon]

your average LQ is 99%, i.e. majority of the packets from your radio got to your receiver.
your 1RSS (RSSI dBm) never have gone to -130, which means the link DID NOT dropped the entirety of the flight.

so essentially your Failsafes aren't caused by RX LOSS, per your EdgeTX logs

[stoic axle]

Is this then related to betaflight setup?

[odd geyser]

For what it's worth, I switched to 150hz packet rate and I turned off dynamic power in favor of fixed 100mw and I've gone through at least 8 batteries without a failsafe. Had three fail-safes on one battery before making that change.

Based on the logs, It seemed like my flight controller was struggling with telemetry and then really freaked out when my controller boosted power from 10mw to 250. I don't know. It might still happen but it's good enough right now.

[stoic axle]

Hmmm

Very odd, and interesting

thanks for keeping me in the loop

[chilly fern]

@odd geyser have you considered switching to ELRS3?

Seen that behave a lot better on mobulas.