#Meteor75 Pro - Can't connect to RadioMaster Pocket

83 messages · Page 1 of 1 (latest)

red marlin
#

I replaced my camera today on my Meteor75 Pro (2022 version) and it wouldn't connect to my RadioMaster Pocket after that. I used to fly it all the time and never had any issue configuring it.

I tried a bunch of different things today and it just wouldn't connect. I thought maybe it needs new firmware so I upgraded my Pocket to 3.5.3 and then tried to do the same for my Meteor75 Pro after that, thinking they needed to match versions. I have seen conflicting choices for which Target (Device category and Device) to use on various posts / videos and I think I may have flashed the wrong Target. Now I don't see my quad coming up in Wifi mode and ELRS Configurator keeps giving various errors after I following numerous post on the internet and in this discord.

Any help getting me straightened out would be much appreciated.

red marlin
#

Here is my log by the way:

** Searching flight controllers **

FC found from 'COM3'

Detected the following serial ports on this system:
COM3

======== PASSTHROUGH INIT ========
Trying to initialize COM3 @ 420000

Attempting to detect FC UART configuration...

** Serial RX config detected: 'serial 0 64 115200 57600 0 115200'

Enabling serial passthrough...
CMD: 'serialpassthrough 0 420000'

======== PASSTHROUGH DONE ========
======== RESET TO BOOTLOADER ========

  • Using full duplex (CRSF)

Cannot detect RX target, blindly flashing!

esptool.py v4.2.1
Serial port COM3
WARNING: Pre-connection option "no_reset" was selected. Connection may fail if the chip is not in bootloader or flasher stub mode.
Connecting...
.
.
.

worthy geode
#

target should be "BetaFPV 2.4GHz AIO RX" if you indeed have the elrs version of the aio

red marlin
#

That's what I've been trying to flash. I had seen a video on YouTube that people kept pointing to where he was using the diy target and tried that too. Is there anyway around the error above?

worthy geode
#

try this !aio procedure here:

lusty pikeBOT
#

AIO with Serial ELRS receiver recovery flash instructions:

  1. Disable Telemetry in Betaflight
  2. Unplug everything
    3a) if there are two boot buttons, hold down the receiver boot button, plug in USB, and click flash in ELRS Configurator
    3b) if there is only one boot button, hold it down, plug in USB, open Betaflight, click "Exit DFU mode", close Betaflight, click flash in ELRS Configurator
  3. Re-enable telemetry in Betaflight after successful flash

Note: If the recovery flash fails, try downgrading to Betaflight 4.4.3 temporarily.

https://cdn.discordapp.com/attachments/798006228450017290/1238518416181166100/betafpv5A1sAIO.jpg?ex=6640e528&is=663f93a8&hm=2bfe322bcb84c6e83fb65629013384f3708c4ef9ca45bb3c69cfee39716713a6&
https://cdn.discordapp.com/attachments/798006228450017290/1238518416583950467/exitDFU.jpg?ex=6640e529&is=663f93a9&hm=d810384bcf0daceaa83d9336dd62cda17595dcd263075a914773e6f1d0a80e5e&

red marlin
#

When I do steps 1,2, and 3b I don't get a choice for port (passthrough or uart) and it fails. After clicking Exit DFU it prompts me to connect to the port again. Whether I just close without connecting again or just close betaflight, the green light (boot mode) stays solid and the elrs configurator can't see the port.

red marlin
#

HEre is the ELRS log when I follow the instructions above:
Traceback (most recent call last):
File "runpy.py", line 196, in _run_module_as_main

File "runpy.py", line 86, in run_code
File "C:\Users\mikec\AppData\Roaming\ExpressLRS Configurator\firmwares\cloud\ExpressLRS\40555e141efb0c93ea8d075ec47a27592355f924\firmware\flasher.pyz_main
.py", line 3, in <module>

if __name__ == '__main__':

File "C:\Users\mikec\AppData\Roaming\ExpressLRS Configurator\firmwares\cloud\ExpressLRS\40555e141efb0c93ea8d075ec47a27592355f924\firmware\flasher.pyz_bootstrap_init_.py", line 253, in bootstrap

File "C:\Users\mikec\AppData\Roaming\ExpressLRS Configurator\firmwares\cloud\ExpressLRS\40555e141efb0c93ea8d075ec47a27592355f924\firmware\flasher.pyz_bootstrap_init_.py", line 38, in run

File "C:\Users\mikec.shiv\flasher.pyz_a4a57aab0c3eaded256af93c8e8a5802d28f2040d54a50392b9b4e4fec341e9e\site-packages\binary_configurator.py", line 437, in main

return binary_flash.upload(options, args)

File "C:\Users\mikec.shiv\flasher.pyz_a4a57aab0c3eaded256af93c8e8a5802d28f2040d54a50392b9b4e4fec341e9e\site-packages\binary_flash.py", line 168, in upload

return upload_esp8266_bf(args, options)

File "C:\Users\mikec.shiv\flasher.pyz_a4a57aab0c3eaded256af93c8e8a5802d28f2040d54a50392b9b4e4fec341e9e\site-packages\binary_flash.py", line 86, in upload_esp8266_bf

args.port = serials_find.get_serial_port()

File "C:\Users\mikec.shiv\flasher.pyz_a4a57aab0c3eaded256af93c8e8a5802d28f2040d54a50392b9b4e4fec341e9e\site-packages\serials_find.py", line 71, in get_serial_port
raise Exception('No valid serial port detected or port already open')
Exception: No valid serial port detected or port already open

** Searching flight controllers **
** No FC found, find all ports **

Detected the following serial ports on this system:

#

If I then unplug and replug without being in boot mode, I get the original error above.

#

I have even tried it just now with downgrading to Betaflight 4.4.3. I keep getting the same thing. Even after clicking exit dfu mode keeps the green light on.

#

OMG I think I might have solved it. ONE VERY IMPORTANT STEP!!! DO NOT USE THE WEB BASED Betaflight for this. Use the software download version.

red marlin
#

So now have both my Meteor75 Pro and my RadiioMaster Pocket on ELRS 3.5.3 and they both have the same binding phrase set. They still can't seem to talk. Any ideas?

clear surge
red marlin
#

Can you be more specific?

#

I'm not sure what you want me to look for

clear surge
#

Show a screenshot of the ELRS lua on the radio

red marlin
#

Is that what you were asking for?

red marlin
#

Kindly let me know what else you need

worthy geode
red marlin
#

ive done that a bunch of times (today even)

worthy geode
red marlin
#

@worthy geode the screenshot of my expresslrs on the radio is above

#

@worthy geode the tx and rx screenshots are coming shortly

worthy geode
#

I've read the thread

red marlin
#

HEre is the TX

#

And here is the RX Model and Options

#

@worthy geode ^^^

worthy geode
red marlin
#

@clear surge has asked for the lua screenshot from the radio

#

It works with other quads, just not this one

worthy geode
red marlin
#

I have them all setup the same way with same binding phrase

#

and this one used to work until I changed the camera

worthy geode
red marlin
#

the actual hardware?>

#

the camera with the meteor is plugged

worthy geode
red marlin
#

i didnt do any soldering

#

it was basically unscrew three screws, unplug the old camera, plug in the new one, and screw the three canopy screws back in

worthy geode
red marlin
#

the thin red one?

worthy geode
red marlin
#

yes, picture incoming

worthy geode
#

has this been in crashes?

red marlin
#

well that is what caused the camera to not work

worthy geode
red marlin
#

I guess hard enough to screw up the camera but I didn't think it was that bad

worthy geode
red marlin
#

ok ill take it to my local electroncs guy and see if he can do that and if not I guess I am going to have to get a new flightcontroller board?

#

that's what it is sounding like to me

worthy geode
#

I am going to have to get a new flightcontroller board?
sure.. your call

red marlin
#

alright, thanks for your help, I apprecaite it

red marlin
#

I took it to the electronics shop and had them reflow the solder joints as suggested and it still isn't communicating with the radio.

#

I'm going to order a new FC and see how it goes. Thanks again for help.

clear surge
red marlin
#

It is at the electronics shop and I told them I would just order a new FC and have them replace it when it arrives.

red marlin
#

@clear surge I managed to get photos of the flight controller just now.

worthy geode
# red marlin

is that button still functional or it's in the "pressed" position the whole time?

red marlin
#

Do you mean the boot button?

worthy geode
red marlin
#

I thought so but I wanted to double-check

#

Yeah it comes undone

#

I have seen that stick a couple times but if you push it it'll come unstuck

worthy geode
red marlin
#

It's not too sticky

#

When I was trying to flash the board before I know I pushed it a little too hard I think

worthy geode
#

this could be causing the FC or receiver to go into bootloader mode automatically resulting in that solid green LED

red marlin
#

But I don't think that's the source of the issue because the issue happened before that

#

I don't know that it's going in to bootloader mode automatically though

#

If a jiggle a handle it comes undone like it's supposed to

worthy geode
#

your call..