Mobeetle6 shipped with firmware 4.3.1, but I successfully updated it to 4.4.2 using Betaflight 10.9.0.  This ensures that it is running ELRS 3.x.  I used the "auto detect" button in BF to identify the board, and it flashed 4.4.2 successfully.

Transmitter is TX16s with ELRS 3.0.1 built in.

(I have successfully bound this Tx to two AcroBee65 BLV4 drones with ELRS after upgrading their firmware to 3.0.0. via the wifi method.  I have also successfully bound to a Cinebot30.  So I believe I know how to bind.  I have read all of Oscar's instructions about flashing and binding.  Also, the Mobeetle6 pdf from HappyModel talks about ELRS 2.x, not 3.x., so I don't know whether their other instructions apply.)

This Mobeetle simply will not bind using either the BIND button or the CLI bind_rx in BF.  Also, it does not enter BIND mode with the 3 quick plug-ins, either.  I thought all ELRS receivers were supposed to do this.

Please advise.  Thanks in advance.

Shouldn't make any difference if it's ELRS 2 or 3. Have you tried asking on the ELRS discord? The people over there helped me sort out my issues last year. They are your best bet for help.

https://discord.gg/dS6ReFY

Almost all of us that use it, use a bind phrase. Guessing that doesn't work either?

Someone recently had an issue due to a high packet rate that is unsupported on the SPI version.

https://www.expresslrs.org/hardware/spi-...ers/?h=spi

Quote:SPI receivers DO NOT support D(D250, D500), F(F500, F1000) and Full Res(100Hz Full Res, 333Hz Full Res) Modes (Packet Rates) and thus will not bind or sync with a TX module in any of these modes.

If your radio is in a compatible mode, and if you didn't get a solution from discord then you might try flashing the hex file from Happymodel's website. They have a 4.3.1 custom target with ELRS 3.x.

https://www.happymodel.cn/index.php/2022...le6-drone/

(27-Jun-2023, 02:49 AM)Pathfinder075 Wrote: Shouldn't make any difference if it's ELRS 2 or 3.

Sorry man, but that is a significant point. There is no cross compatibility between major versions.

Yeah that was badly worded.

I was referring to him saying about the manual being for ELRS 2 and him using 3. What i meant was more along the lines of whether you choose to run ELRS 2 or 3 isn't largely relevant, but should have probably added as long as your radio runs the same major version. But since the OP stated his radio is running 3 and the quad is running 3, it should work.

I think the issue is the unsupported modes. If so it will be the third thread about this in the last couple of months. It would be nice if the ELRS configurator had an added tick box which said something like "I have quads with SPI ELRS" and then built a set of firmware without the unsupported modes and settings, almost like a legacy mode. or I suppose add something into the firmware, whereby if the quad won't bind, it would automatically try enabling a legacy mode that disabled all features not supported by version 2 / SPI.

   

OK, I finally got it to bind.  I went back to factory by using Betaflight to install the 4.3.1 firmware (yes, it's ELRS 3.x), and the CLI dump.

Then I had to change the packet rate in the Tx to 250.  That worked.

Now there is something weird going on with the flip over after crash (I think anyway).

With all switches OFF (arm, mode, and flip), I can arm it OK.  But as soon as I apply some throttle, it does the flip thing.  I have tried all combinations of mode switch and flip switch.  Same behavior.

Here is the mode tab attached.

Most likely, one or more of your props is on backwards.  Check them.  Or a motor is spinning the wrong way.

This tab in BF shows you which way the props spin.  Set up the props so that they push air downwards.  Look at the shape of the blade and imagine it spinning the way it shows in the Motors tab. 1 and 4 use the same direction prop and 2 and 3 use the same direction prop (2x CW and 2x CCW).



In the same tab, you can spin up your motors, so plug in a lipo and so do so, with the props on. But only spin them up a little bit, one at a time. Make sure the order is correct and the motors are spinning the correct way. If not, click on the Motor Direction tab and re-order them correctly. By a little bit I mean barely enough speed for them to spin, not anything more than a couple of % and never does this with bigger quads with the props on, but anything up to 2" with prop guards and less powerful motors is fine. Remember you want to work out which way it is spinning, not have it take off.

Thanks Path,

This Mobeetle6 as delivered from the vendor has the props mounted opposite of your tab diagram, but the motor direction is reversed.  I have confirmed that the props spin in the correct direction using your instruction above.  They blow air down.

My factory default ESC/Motor protocol is DSHOT300 and the bidirectional is ON.  I see your diagram shows PWM.  Is this for a different quad?

So, a second question.  What about the accelerometer?

rm

I was running BF in Virtual mode to get the motor diagram up. I didn't have a quad plugged in.

You could try resetting it. Place the quad on a glass or four blocks under the motors, so it is as level as possible and then recalibrate the accelerometer.

Also could we get a full dump and diff, wrapped in [ code ] [ / code ] blocks and some pictures of the drone. Thanks.

If it came from the manufacturer in a props out configuration like you said, and you kept it in that configuration, don’t forget to select the button that says “motor direction is reversed” on the motors tab in betaflight.

Otherwise, it will flip out on throttle.

DSHOT is the new digital control method that has excellent precision and speed. PWM is pulse width modulation where it just sends electrical pulses of varying lengths to act as instructions. It works, but it's old and limited. No reason to use it when DSHOT is available and supported.

I know this doesn't offer much in the way of help in figuring out what's wrong, but it's good to know what you're working with.

Just ignore the PWM bit from that screenshot. I tend to run Betaflight Config in Virtual mode a lot, so i can look things up without plugging an FC in, or in that case, taking a screenshot of the motor direction graphic. PWM is AFAIK for planes and boats. But in Virtual mode it just comes set to it as default (and has no relevance since simulating virtual motors would be pretty pointless).

Hey Lemon, thanks.  Yes, I did definitely turn the slider "reverse motor direction" to ON.  The props spin correctly, and they blow down.  That part is all fine.

What is problematic now is that when I arm, the props spin correctly, but as soon as I apply throttle, it bumps and tries to flip, then turns the props off.  When I dis-arm then re-arm, then apply throttle again, it repeats this crap.

***********************************

Does anybody have a CLI dump for this Mobeetle6 that actually works?  It must be compatible with elrs 3.x, which means firmware 4.3.1 or higher.

  Mobeetle6 ELRS 3 Dump.txt (Size: 27.28 KB / Downloads: 40)
Hey Path,

Here attached is my CLI dump, as a plain text file.  Note that I am running a non-standard stick map since I run my Tx mode 1.  This stick map works correctly in BF when I check my sticks in the receiver tab.

Now that you’ve updated to that special version of betaflight 4.3.1 that supports ELRS v3, you can actually load the stock dump back onto it (you didn’t change major versions of betaflight, so it’ll still work without an issue).

I’ll post a link to the stock dump that you can then paste into the cli tab, but first, we need to know which gyro your board has so that I know which dump file you need.

Please go to the cli tab in betaflight and type:
Status
And then hit enter. Copy/paste the result back here.