Hello All, I spent hours enjoying my time with Mobula6 and once day when I get an Idea to update my firmware on TX16s it's stop working. Now I can only hear beeping sound whenever I connect battery to it. I spent lot of hours trying to find a way to fix it but no results. You're my last hope.

I'm attaching video file with my problem and current settings from betaflight.

Video link: MOBULA6

It must be something to do with the Model setup on the TX16s. Did you try creating a new Model?

I can’t see your video to see what the problem is.

(14-Apr-2022, 03:22 PM)kafie1980 Wrote: It must be something to do with the Model setup on the TX16s. Did you try creating a new Model?

I can’t see your video to see what the problem is.

I just add link to my video. Can you see it now?

I did create new model few times in TX16 but it didn't help. Not sure what else I can change there.

Is your TX16S actually bound to the Mobula6 and are you seeing the bars in the Receiver tab of Betaflight Configurator moving when you wiggle the sticks?

(14-Apr-2022, 07:03 PM)SnowLeopardFPV Wrote: Is your TX16S actually bound to the Mobula6 and are you seeing the bars in the Receiver tab of Betaflight Configurator moving when you wiggle the sticks?

It's not bound. I did try it many times with Internal RF: FrSky D D8. Dron is also not responding when I'm pressing bind button on motherboard, it's just keep beeping. I have no idea what's wrong but I don't think it's broken.

Try binding it through betaflight.

Open betaflight, connect to drone, go to the “cli” tab.
Type in: bind_rx_spi
And hit enter. It should say something along the lines of, “binding…”
And put your transmitter in binding mode. Also, make sure your tx is a few feet away from the drone.

If bind_rx_spi doesn’t work, try bind_rx

Edit- also, it’s been a while since I updated the firmware on my Tx16s, I don’t remember if I had to start all over and create switches and whatnot, or if I just transferred that back over with my model settings.

(14-Apr-2022, 09:20 PM)Lemonyleprosy Wrote: Try binding it through betaflight.

Open betaflight, connect to drone, go to the “cli” tab.
Type in: bind_rx_spi
And hit enter. It should say something along the lines of, “binding…”
And put your transmitter in binding mode. Also, make sure your tx is a few feet away from the drone.

If bind_rx_spi doesn’t work, try bind_rx

Edit- also, it’s been a while since I updated the firmware on my Tx16s, I don’t remember if I had to start all over and create switches and whatnot, or if I just transferred that back over with my model settings.

I did try that too many times. On Betaflight I got confirmation it's binding but I'm not able to bind with receiver from any distance.

I am also wondering if the onboard SPI RX on the Mobula6 AIO board is defective.

Did you do any firmware updates on the Mobula6? The SPI RX on the AIO board depends on code in the Betaflight firmware.

What firmware did u install on ur tx16?… did u by chance do aback up or take note of what firmware was on it prior to the update?
Did u update “open tx”? Or the protocol firmware? I’m GUESSING it was d-8 / Frsky?

I just got a mobula6 and I wasn't able to bind it on D8 it did however bind on D16, if you were bound on D8 before check in betaflight to see is you configuration is still set to frsky_d. If it is, then, maybe try changing it to frsky_x and change your radio's internal setting to frysky_x also, then try binding in D16 and see if that works

My Mobula 6 is flying very well I did have to add some expo as it was a bit bouncy, however I'm having video saturation problems, the video feed is purple and green ish. Has anyone ever had a similar video issue and if so what was the fix. I tried different channels and two different goggles but the video is the same.