My meteor 85 won’t fly it turns on and shines a solid green light but it won’t fly, it shows the video feed but doesn’t all of the information it normally would.
Can anyone help?

Is it new? Have you flown it before? Connected to your controller in betaflight and could see stick inputs having an effect? Modes and arm switch set in the modes tab? No OSD sounds like wrong firmware perhaps?

(25-Aug-2023, 01:28 PM)FPVme Wrote: Is it new? Have you flown it before? Connected to your controller in betaflight and could see stick inputs having an effect? Modes and arm switch set in the modes tab? No OSD sounds like wrong firmware perhaps?

It is new I have flown it

it sounds like you got a flash error.

connect it to betaflight configurator, if you are connecting to betaflight and it asks for applying costum defaults. than all settings might be lost.
apply costum defaults and start to set it up again, there might be diff or dump for the meteor on the betafpv website.

I cannot seem to get the controller to show stick movements in BetaFPV configurator.

Cable setup for testing via a Mac:

Literadio 3 controller connected via USB to laptop.




Drone is connected via USB.

I have run the CLI script: BF4SX1280 4.3.1_M85_A_ELRS V2.2_ELRS_20230202.txt

I have flashed the drone


The problem:
1. does not arm
2. The controller movements do not show in BetaFPV Configurator.
3. The drone flashes blue lights.

Not sure if this is correct but I also changed these settings:

Ports


Controller:

It does not do anything if I change this to UART

final point:
Motor test works from BetaFPV Configurator

I think you’ve got a few different problems. Do you happen to know which version of the meteor 85 you bought?

On the receiver tab in betaflight, under receiver mode, you currently have msp selected. Change that to “SPI Rx”, and in the new drop down menu that appears below it (receiver provider), select “ExpressLRS”.

Make sure you hit save prior to navigating to a different tab.

Your other potential issue is an ELRS firmware mismatch. Someone else will have to confirm this, but I believe the literadio 3 only supports ELRS v2.x. Since you flashed betaflight 4.4.2, that would make the built in ELRS spi receiver run ELRS v3.x. You may need to flash an earlier version of betaflight (4.3.x) in order to make it compatible with your transmitter.

If you need clarification on any of that, feel free to ask. Once you get your transmitter and receiver talking, and betaflight registering stick movements on the receiver tab, you’ll need to set up the modes tab.

Edit- here’s something easier to follow/try- flash it to betaflight 4.3.1, and then run the cli text that you tried previously. That should set everything up properly, and the only things you may have to do after is set up your binding phrase on the quad and set up the modes tab.

Still not getting a response from the controller in BetaFlight.  The drone just flashes blue light with the green led permanent on.

The exact model of the Meteor 85 is: https://www.unmannedtechshop.co.uk/produ...pter-elrs/

thanks, I have flashed the drone to 4.3.2
 

Run the CLI script.

Controller setting is:


And the BetaFPV configurator is set as:



The exact model of the Meteor 85 is: https://www.unmannedtechshop.co.uk/produ...pter-elrs/

Okay, now you need to bind it.
Power on your transmitter and then hit the bind button (I think it’s on the bottom of the transmitter)
Then plug in a battery to the quad, unplug it, and replug it three times.
On the third time leave the battery plugged in. Leds should do something different now than they were before.

Now connect to betaflight again and see if you have movement on the receiver tab.

Edit- Do all of the above without the transmitter plugged into usb or connected to the configurator, and without the quad connected to usb or betaflight.

Important side note- anytime you have a battery plugged into your quad while it’s on the bench, make sure you have a fan pointed at it to keep the video transmitter from overheating.

If the above binding method doesn’t work, let us know and we’ll talk you through setting up a bind phrase on both transmitter and quad.

Just wanted to mention you should verify you using the correct diff that goes with your vtx. The diffs for that board are different depending on what vtx you are using. Since yours is a 2022 version, it should have a v1.1 vtx. Older versions use the diff for the v1.0 vtx. The vtx version is printed right on the vtx board. Here's more info:

https://support.betafpv.com/hc/en-us/art...eor85-2022-

Oh yeah... side note on elrs binding. Use a binding phrase FTW! Binding phrases are more dummy proof... if binding phrases match they bind, end of story (well sorta... elrs 3 won't bind with 2). No 3-power cycles and "...is it bound yet?" bs.

Hi, still not getting the controller to show in BetaFlight and still can't operate the drone.

I made a video of what I have done:



Not sure if this helps you guys to debug this? Am I doing something obviously wrong here?

there is a warning for the gyro, there no gyro signal

while you are successfull with binding, it doesnt arm cause of the gyro warning.

this does often happen by a wrong firmware. i would suggest to try the .hex file from the betafpv website posted by truglodite.
download the firmware on the betafpv website, open betaflight configurator - firmqare flasher and choose local file, the downloaded hexfile.
check if the fc does comunicate with the gyro befor applying any diff


if you doent get gyro signal thatway, it might be time for a replacement  provided by betafpv

(27-Aug-2023, 05:41 PM)hugnosed_bat Wrote: there is a warning for the gyro, there no gyro signal

while you are successfull with binding, it doesnt arm cause of the gyro warning.

this does often happen by a wrong firmware. i would suggest to try the .hex file from the betafpv website posted by truglodite.
download the firmware on the betafpv website, open betaflight configurator - firmqare flasher and choose local file, the downloaded hexfile.
check if the fc does comunicate with the gyro befor applying any diff


if you doent get gyro signal thatway, it might be time for a replacement  provided by betafpv

Thanks,

the Hex is for a different board, I have VTX 1.1 and the Hex was for Meteor 85 with M03 VTX V1.0.

Here is my board:

the hex file is the fiemware for the flightcontroller, ir doesnt matter which vtx you have. it just matters for the diff file, the vtxtable

i would suggest to try that firmare because of the gyro issue

Thanks will try that tomorrow.  I'll keep going with this, hopefully we can figure something out.

Just to clarify:
.. when the drone is not paired the drone flashes blue?
.. when its paired the drone stops the blue flashing?

How do I flash with the Hex file? using the betaflight or using the BetaFPVConfigurator software?

Sorry for all the questions...