#Random RXLoss and RSSI drop

111 messages · Page 1 of 1 (latest)

vernal hound
#

I recently bought a Happymodel Crux35 and have had an issue where at complete random, I'll get RXLoss and my RSSI will drop to -130. I don't regain connection until I replug in the battery. I also get occasional Telemetry loss, but it comes back immediately. Radio is TX12 MKII with built-in ELRS. I've tried updating BF to no avail.

signal imp
#

What receiver?

vernal hound
#

Crazyf411 built in UART ELRS reciever

signal imp
#

Post a CLI dump and the output of status

vernal hound
#

I'm at work, I will in a few hours, thank you!

vernal hound
signal imp
vernal hound
#

Flashed 4.4.3, CPU load in BF sits at 31%. Is that better?

signal imp
#

Yes, you were at 60% before

vernal hound
#

Upon loading the old backup, my CPU load sits at 60% again

#

Is there anything that could be eating at it?

signal imp
#

Type tasks in the CLI twice, and post the output from the second time

vernal hound
signal imp
#

Reflash the receiver via Betaflight Passthrough

#

What ELRS version and regulatory domain are you using?

vernal hound
#

3.0.1, ISM

#

Should I update to 3.3.2?

signal imp
#

Yes

vernal hound
#

Whenever I put my FC into DFU mode to flash it, it doesn't show up as a COM port, instead as a USB device

vernal hound
#

I can't select it as a device in ELRS Configurator though

signal imp
#

DFU mode is only for updating Betaflight

vernal hound
#

BF Passthrough kept erroring out, so I updated both my receiver and transmitter to 3.3.2 through wifi. However, Betaflight isn't getting anything in the reciever tab, despite rx and tx being bound

#

my reciever serial rx is on

warm roostBOT
#

See the following image to save a log file from the configurator

vernal hound
signal imp
#

Try flashing via Passthrough again

vernal hound
signal imp
#

Show a clear photo of your FC

vernal hound
signal imp
# vernal hound

Disable Telemetry in Betaflight, unplug USB, hold down boot button, plug in USB, open Betaflight, click "exit DFU mode", close Betaflight, click flash in ELRS Configurator

vernal hound
#

no change, same timeout error

#

I may add that, in trying to fix this error before, this (BF not getting anything from the reciever) has happened before, but frankly it fixed itself after throwing myself at it enough and I don't know what I did ¯_(ツ)_/¯

#

Thank you for your help, though

vernal hound
#

Update, I reflashed BF 4.2.2 it's communicating with BF again

vernal hound
#

RXLOSS still happens.

signal imp
#

Have you reflashed the receiver?

vernal hound
#

yes

signal imp
#

Can you show the flashing log?

vernal hound
#

Betaflight.

vernal hound
vernal hound
signal imp
#

Please do

#

Try this: Flash via Betafight passthrough with "erase before flash" checked

#

It should fail, post the log

#

Then flash again without "erase before flash" checked

vernal hound
signal imp
#

No CLI available. Already in passthrough mode?, If this fails reboot FC and try again!

#

Unplug everything, plug in USB, and try again

#

ELRS Configurator can't talk to Betaflight

vernal hound
signal imp
vernal hound
#

Through wifi, yes

#

not through passthrough. It's never worked through passthrough

#

always get the same timing out-type error

signal imp
#

If you can't reflash via Passthrough that suggests a wiring problem between the FC and receiver

vernal hound
#

But it's an AIO?

signal imp
#

Yes, show the other side of the FC

#

Do you have any shorts in this area?

vernal hound
signal imp
#

Show a clear photo of the FC

vernal hound
#

Mhm, gimme a moment

signal imp
#

Is there solder on the u.fl?

vernal hound
signal imp
signal imp
#

I don't see anything obviously wrong. I'm leaning towards a hardware issue.

#

If you have a !ftdi adapter you can reflash using that

warm roostBOT
signal imp
#
vernal hound
#

What's the issue flashing over wifi?

signal imp
#

If the problem is a corrupted flash partition on the receiver, flashing via WiFi will not overwrite it

vernal hound
#

So next course of action is to get a FTDI dongle?

signal imp
#

You tried the recovery flash procedure?

#

Unplug USB, hold down the receiver boot button, plug in USB, and flash?

#

Failing that, I would try via FTDI. They're like $6

vernal hound
vernal hound
#

I'll give recovery flashing again as the button is hard to press and I may have not done it correctly

#

Booted it into recovery mode (solid green LED) and same error still, oh well.
Would there be any way to use a RPI pico or similar for an RFDI device, or do I have to bite the bullet and just buy something like the betafpv one

signal imp
#

Just get a FTDI adapter

#

they are cheap

vernal hound
#

Alright, ty!

vernal hound
#

I have a serial-to-usb adapter, which from what I can tell is no different to any FTDI device online. upon seeing the serial output after bridging +5v and E5, it's complete nonsense.

signal imp
#

Follow the instructions to flash via UART

#

Put the receiver into bootloader mode first

vernal hound
#

Consistently times out trying to flash, serial console doesn't show anything while in bootloader mode

signal imp
#

Show your wiring and the !log

warm roostBOT
#

See the following image to save a log file from the configurator

vernal hound
#

Red is RX, Brown is TX. I've also tried reversing them to no avail

signal imp
#

Use soldered connections

vernal hound
#

Still the same result.

#

not the greatest soldering job, but nothing is shorting out.

vernal hound
#

Is the consenous to buy a new board, or?

vernal hound
#

Betaflight is still recieving connection to the ELRS module despite the pads being bridged.

vernal hound
#

tried a different usb to serial adapter, no change still