Does anyone know if you can use the AS3X Receiver USB Interface to update a Frsky rx in place of the Frsky STK tool? I have one lying around and I'm just curious if it'd work. I understand dsmx is a different protocol, but is the process of sending information the same? The devices look very similar and I know people have used USB to TTL adapters to update Frsky rx's. Thanks in advance!

Hello!
Got Betafpv Pavo20 drone with this FC: https://betafpv.com/products/f4-2-3s-20a-aio-fc-v1
is it possible somehow connect analog VTX and get OSD on video?

Got Eachine tx805 and AKK ultimate mini VTX
Camera: caddx ratel 2

Currently connected:
VTX with camera: 5v out, gnd, video
VTX with FC: 9v in, GND,  SmartAudio to FC T1

in betaflight configured this way:
https://disk.yandex.ru/i/mxwRKnewFGuc8A

Is it possible to get OSD on analog on this hardware? If yes, then what im doing wrong? If not is there any way to buy some external modules for an controller osd?

[url=https://fixfly.ru/zproduct/6646][/url]

Hello guys, i plan on building a quad which has only one hard mounting point for the antenna. I want to use the OG Air Unit which has 2 antennas and wondered if it is possible to combine the two into one. Like it is on the O3 Air Unit. Is that possible? 
Thanks for your advice.

Didn't see too many reviews on the Atlas 4 frame, but it looked like an interesting option. A not too heavy 4" LR frame with O3 mounting (advertised as no props in view) and budget priced. The front arms do look a little short compared to other deadcat frames, will have to see if that affects how it flies. The camera is pushed forward of the front motors though and has the CNC frame for protection.



Motors:
Seen some builds using 1404 motors all the way up to 2004 on this frame. As this will be more for cruising, I think I can rule out 1804/2004 and 1404 sounds a little underpowered for carrying the O3. Having a set of P1604 on a 3.5" build, I liked them quite a bit - smooth and good low-end response which should be perfect for a 4" cruiser setup.

AIO:
I am using the NeutronRC AT32 AIO v1.2 board with the 35A ESCs, mainly as this I what I had on hand. I previously tried the v1.0 of this board also with the P1604s, but had terrible yaw twiching. Not sure if it was a gyro issue or an ESC issue, as this board does not run BlHeli or Bluejay, instead it uses AM32. This board is very beefy and needs a good amount of heat for soldering on the motors, and it certainly has some quirks, but for less than $40, I decided to give it a second try, but not sure if that was a wise choice. 
I recently replaced a dead AIO on a 3.5" 1504.5 motor build with the same v1.2 board, the first flight on 4S was fine, but the second flight with 3S, the yaw twiching was really bad... so I don't know... will have to see if it happens here as well or can be corrected with some firmware upgrades.

O3:
I only have a single O3 air unit, and never really fly it much. I use the older V2 goggles and found I can only get smooth FPV feed if I use 120fps mode. 60fps looks very choppy and has latency issues. Also flying  in low light or in backlight conditions, shadow areas are really hard to make out. But still the onboard 4k is attractive and if props are out of view, maybe it is a viable single camera solution for cruising.

I had it installed on a budget LR4 clone frame with 1505 motors, and actually it flew very nicely. The frame was not made for O3, so TPU prints to mount the camera/air unit. It didn't really need to be swapped out... but maybe that frame would be a better match for the WS Pro camera. I decided to get one last flight in with this drone before pulling out the O3 and this was the result.



A crash on pavement. Not too rough, but rough enough. The frame is actually a folding frame, which is probably a good thing. The arms simply folded in, there is no visible damage to the motors or arms.



You can see how much wider the front arms are compared to the Atlas. The body is much shorter though, so it was a tight fit getting the O3 in.

Hello all! I'm trying to get an xm+ running on Betafpv Meteor 75 Pro. Betafpv said I have to run a 1.x version on the XM+ but I have a 2.x version on my Taranis x9d plus radio. Is there any way I can work this out without have to downgrade my TX and all other rx's? Sorry if I'm not wording this correctly. Hopefully y'all get the list of what I'm saying. Thanks!

Hello, I am thinking to try INAV 7.1 on my 7" drone. More than one person that I know tried to do the same but went back to BF due to technical issues that weren't able to solve and in some cases the drone was unflyable on stock settings, one of them even lost his quad due to a flyaway during PID tuning... I have noticed that compared to BF the INAV documentation appears to be much less detailed; I am not a programmer so I am not a user that will easily figure out how something works by reading only the code on github without a proper documentation and my drone is not equipped with a magnetometer. I am overthinking it? What do you suggest?

Hello, I can't get the xm+ to work on the meteor 75 pro. I updated xm+ to latest firmware, my Taranis x9d plus is running latest ACCST firmware, I set spi and sbus in rx tab in Betaflight, changed uart1 to serial rx and frsky. When I try to bind, the xm+ just has a solid red and green light. Then when I stop binding and unplug battery and plug it back in I just get a flashing red light on xm+. I watched the video on Betafpv's website and did everything exactly like he did, but it's not working. I could get the xm+ to bind to my taranis before I installed the latest firmware. But, even though it would bind before the update it wouldn't control the fc in betaflight. Any help would be appreciated. Thanks.

Also, it's almost impossible to get any solder to attach to the sbus pad on the fc no matter what temp I use. It's harder than any negative pad on a 5 inch quad I've ever seen. Thoughts?

Hello all,

I am trying to make a extremely small fixed wing plane with a rudder and elevators, no ailerons. I can not get my servos to work, I have used beta flight and inav and have read every tutorial online about it. both programs see the receivers and move servo 1 and 2 in the program but there is no output. Does anyone have any tips on where to begin?

Greetings to everyone. I just started FPV.
More precisely, I have been in the simulation for 6 months. Now it is time for me to fly outside.
I'm thinking of 2.5 inches as a starting point. What would you suggest?
Could Lumenier QAV-PRO 2.5 be expensive to start with?
Or do you have a better suggestion? I will fly for real estate in 1 year. Thank you in advance

I bought a pavo pico elrs with dji 03. I am a noob in the hobby and I am not very familiar with all the functions in express lrs or betaflight so I buy bnf's. As soon as I got it together I assumed I could bind it with a rapid 3 time connection to battery which seemed to work. Zorro receiver would lose and pick up telemetry with battery connection. But nothing worked. Plugged into betaflight and no movement showing from sticks when binded. I then did some research and found I am supposed to update the elrs rx to match my receiver. I tried that though express lrs application and got an error for not enough space. I did a reportition and now it has a solid green light and no wifi can be discovered. Any help would be much appreciated! I believe the rx is a betafpv f4 aio.