Hello, I'm new to FPV. I'm only flying in simulation. It's time to collect a quad. I have a 2-inch device in mind. It says that it is designed for the newly produced Lumenier QAV PRO NANO.O3, but I am thinking of using caddx vista or naked vista. Do you think it is possible?
Thanks for comments..

Hi, got this on a old drone. And trying to find pinout for this. EByte E108 GN02D GPS module. It's 6 pinouts

Cheers.

Attached Files

Thumbnail(s)
   

Do you guys think that 1102 size 19000kV motors on a 65mm pusher is too much?  The dry weight will be heavy due to the walksnail vtx and hd pro camera.  Going to run it on 2S.  I see the dry weight in the 55 - 65 gram range.  Will run on 31mm 4 blade gemfans.  Hoping the extra torque of the HM 1102 motors will help with the higher inertia or am I dreaming about the amount of thrust I'm going to get?   

Hello, after a long time I would like to ask for help here.

I would like to set FC for 5 servos. And I have a problem that I can't solve. When I set BF for servo_tilt I get 2 servos. Everything is working fine at this point. Even if I remap the outputs, all outputs to motors and TX pads work correctly, but I only ever have two servos. Which is fine.
When I switch to channel_forwarding to get more than 2 servos, the outputs for both motors and TX pads stop working. In the servo tab, the bars move accordingly, but there is nothing on the outputs. In other words, the signal goes out from them, but the servos stand still and do nothing.
I tried to set up the mixer, servos and my own SMIX through the CLI and nothing affects the functionality. Some instructions according to youtube. I also used servo_lowpass. I did everything exactly as per the instructions and nothing works.
FC - SKYSTARSF405 - Betaflight / STM32F405 (S405) 4.4.3 Mar 23 2024
I also tried INAV, it works fine, but I only have 4 servers, because it doesn't support resource remapping in CLI. I'm at an impasse right now. 
How do I force BF? I think I'm doing something wrong. Or are the servos already out of the game in BF?
Thanks for the advice Gentlemen.

Does anyone know where I can find the manual on the Pavo 20?......I went to BetaFPV's web site but could not find it.

Thank you!

TxFlyer

So I recently bought and put some flights on a new TH3+ freestyle, and I already had one battery failure.  Doing some surgery on the battery (EMAX 650 PH2 plug) showed a burn through on the battery terminal pad.  As I have a mess of BT2 batteries for my Meteor75Pro I was thinking of replicating the TH3+f PH2 double plug with that capacitor into a BT2 one.

Has anyone done this already?  What is the purpose of the capacitor?  A visual inspection of the plugs and circuit board seems to have the batteries in series, with the capacitor in parallel to the two batteries - so is the capacitor a brownout prevention?

As I'm fairly recent flying drones, I'm still flying mostly LOS and there was a post somewhere in these forums that you can get flight battery voltage telemetry - is this done through Betaflight on the quad? or on the controller?(Radiomaster Pocket ELRS version).

Any help on these subjects is greatly appreciated.

CDC

.......thought I will share them.

I was browsing my own YouTube channel this morning. Just some old stuff I did.

I didn't even know I had this one.



I was making stabilized camera gimbals and helping iFlight. They sent me there prototype and I was testing it.


My earlier gimbal.



Shot with my Y6 multicopter. No FPV back in those days. 


I guess I did acro with my multi copters back in the days.

I had no idea my Taranis x9D plus only has 100mw output?… well that’s what I discovered online.. if It’s wrong please post.. Not that it makes a difference.. the only thing I fly on Frsky is my d8 whoops.. my bigger rigs now have crossfire and I have a ELRS module on the way.. so the 100mw is moot at this point…
It just never occurred to me to actually know what it’s output power was.. I guess I should have when I cranked my crossfire module to 1w or on dynamic range.. it didn’t take long before I would hear “Transmitter battery low”…
And from what I have read, you can’t change that “level” in the controller ..
I know at some point I will get a boxer, even with this microwave oven hanging from my neck.. it has no issues and nice gimbals ..

The first release candidate of ExpressLRS 3.4.0 was published an hour ago. Keep in mind that this isn't a final release so there are likely still bugs present, so only install release candidate versions if you are happy to be a beta tester and take the risk of having an unexpected failure. Full details are below.

For details about what was in the previous 3.3.2 release, see another thread HERE.

Relevant Links:

• GitHub Release Page for ELRS 3.4.0-RC1: https://github.com/ExpressLRS/ExpressLRS.../3.4.0-RC1
  
• Getting Started 3.x.x Documentation: https://www.expresslrs.org/3.0/quick-sta...ng-started
  
• Latest ExpressLRS Configurator: https://github.com/ExpressLRS/ExpressLRS...r/releases
  

Quote:The important stuff

• Arming must be on AUX1 for safety and feature reasons, having this fixed allows us to maintain small packet sizes and deliver better aux channel options
  
• Be sure to flash both the TX and RX.
  
• This is a release candidate. We have tested it using our release test plan, but there may still be bugs. Don't flash it to anything important. We appreciate the community testing.
  
• Lua script MUST be updated to elrsV3.lua and is backwards compatible with 2.x. Firmware get it here: Lua
  

Compatibility

This is a feature release version (meaning it contains new features, targets and bug-fixes) and is compatible with all V3.X versions.

Who should update from V3.3?

• Our 3 LBT users
  
• Anyone who is interested in the latest and greatest features listed below
  

Who should NOT update from V3.3?

Our STM32 users. This includes the Happymodel ES915 TX/RX, Happymodel PP, NamimnoRC V1 Flash/Voyager TX/RX, FM30, Ghost and FrSky R9 hardware.

New Features

More detail on the below features will be added with coming RCs and the final release.

Team Race

• #2176
  

"Match TX" output power

• #2242
  

Added US433 domains

• #2309
  

Sentinel tracker integration

• #2370
  

Move targets to separate repository

• #2400 This allows the dev team to add new targets as soon as they have been tested/passed, if they don't require firmware changes to support them
  

Added serial protocols on receivers

• #2408 Support Graupner HoTT telemetry sensors
  
• #2631 HoTT Telemetry: robustness measure
  

ESP32-S3 target support

• #2410 Support for ESP32-S3 targets
  
• #2463 Get thermal info from S3 if no LM75A
  
• #2472 Fix esp32s3 and backpack passthrough flashing settings
  
• #2494 Allow flashing of the backpack on S3 via USB
  

PWM extensions

• #2346 DShot output for PWM receivers
  
• #2425 Configurable I2C pins for PWM capable (ESP32) receivers
  
• #2535 PWM failsafe modes, like no-pulse, hold, and custom set position
  
• #2624 WebUI: prevent multiple I2C SCL/SDA selections
  

OLED/TFT menu updates

• #2322 Configurable OLED/TFT startup splash screen
  
• #2432 Added switch-mode and Gemini settings
  

UDP/WiFi Joystick support

• #2444 Adds a Joystick that sends data via UDP/WIFI
  

SPI VTx control

• #2515 VTX SPI output calibration routine and initial PWM value config
  
• #2583 Fixed VTX PWM array initialization for unified ESP32 targets
  

Better binding experience

• #2542 Allow all binding methods on RX
  
• #2523 Support CRSF bind command from betaflight
  

Support for non-EdgeTX handsets

• #2528 PPM handset support
  
• #2612 Fix TX module PPM input seeing spurious channels
  

Support for Semtech LR1121 dual-band radio

• #2540 Gemini Xrossband (GemX) - LR1121 Driver
  
• #2616 Adds LR1121 image calibration
  
• #2617 Fix LR1121 binding (adds 2.4GHz binding)
  
• #2618 Allow choosing the domain for LR1121 modules
  

Fix for LBT telemetry lost

• #2643 LBT - Change TX modules to use RX mode with timeout
  

Support for BMP280/BME280 I2C barometers on receivers

• #2480 Add BMP280/BME280 I2C barometer support
  

New Targets

With the separation of the targets from the main firmware repository we will list only those targets that are only supported from this release onwards.
Any new targets that have been added that can be supported by older firmware will just show up in Configurator.

Transmitters

• Add ESP8285 900MHz TX Target #2566
  

Maintenance

• Allow SPI VTx operation without an FC, for use with planes/cars etc that do not use a flight controller #2316
  
• Display a logo on OLED/TFT boot #2322
  

Fixes

• Fix backpack on Gemini 900 target #2323
  
• Disable MSP VTx after no comms on boot #2324
  
• Bring back full 16 Channel support #2365
  
• Work around hardware bug in ESP32-S3 SPI implementation for SPI connected VTx #2406
  
• Add float support to Lua #2415
  
• Fix Lua for SELECT types with only one value #2416
  
• Various web UI fixes and improvements #2422
  
• Hide lua backpack items if the backpack is disabled #2429
  
• SUMD not working at packet rates above 100Hz #2478
  
• Pin AsyncTCP to a specific version (The upstream released a broken version!) #2522
  
• Allow screen rotation for TFT screens #2520
  
• Disable processing MSP VTX commands if there is no SPI VTx #2525
  
• Pick SSID with strongest RSSI in mesh networks with multiple identical SSIDs #2536
  
• Allow setting the destination for CRSF MSP packets (fixes integration with rotorflight) #2550
  
• Fix error when radio chip failed to read #2567
  
• Update the wifi power levels #2568
  
• Only call servo function if theres a change #2571
  
• PWM testing/fixes #2588
  
• Increase SX1276 SyncPktIntervalDisconnected for 25Hz #2589
  
• Add file drag-and-drop to web UI update tab #2590
  
• Pass through handset channels if headtracking switch is off #2615
  
• Fix "Not set" UID badge in web UI #2619
  
• Fix antenna value for Diversity/Gemini receivers #2622
  

Known Issues

• Some STM32 hardware is currently not compatible with v3.4.
  

...at least for a tinkerer like me.

I was tinkering with my Skyzone Steadyview VRX's today and was a bit disappointed. I still cannot understand what Skyzone was trying to do and I cannot get enough "logical" explanation as to how Skyzone is doing things.

I can use RF Normal in the Steadyview VRX module and I can switch through Diversity, Mix 1, 2 and 3 without issue. I guess my expectation maybe a bit too high. I don't really have the major issue like some older Steadyview VRX had. I just have a lot of scatter snow. I did have the screen rolled and tear a bit with certain VTX's.

Then when I switch over to SteadyView X mode on the menu all hell breaks loose. The blue menu bar will change frequency from Race Band 8 of 5917 to 5865. So I looked at the VTX table and 5865 is band A channel 1. However if I change the VTX to band A channel 1 the goggle's VRX will still not give me the video image.

Then I was watching some YouTube video of reviews of the older Skyzone 04X (not pro) and using Steadyview. Ian (Mads Tech) said something about SteadyView X was really for the goggles using two VRX's. Then in Oscar Liang's webpage about upgrading the VRX to a Fusion V3.3 board he mentioned that after changing the board the user is supposed to change over to Steadyview X mode for the Fusion board to work. I bought the so called Fusion V3.3 board from Skyzone and changed it but that is really not working in Steadyview X mode. 

So I settled on RF normal and test different mixes. No change in image quality. It is tolerable but nothing to write home about. 

So back to the drawing board and connected my SpeedyBee VRX back to the goggles. What a heck of a lot of difference. I flew around my backyard and I know there are issues at certain areas. The analog video will get scattered a bit. Even my Walksnail video will hiccup a bit. I even get a flicker or two from Walksnail in those areas. However this SpeedyBee VRX is so good I was only getting a little snow flicker and nothing major.

So time to play. I use an omni and a patch antenna on the modules as default. So I figure maybe I can try different setup. So I just swapped antennas around. I went with two different omni and no patch. I did not use two patches although I was thinking about it. No matter what omnis I use with the SpeedyBee VRX the image quality did not falter. 

I was thoroughly impressed. 

Then the last flight was pretty late and I didn't noticed because I was so focused on tinkering. I could hardly see my transmitter buttons. Luckily the transmitter screen lit up and provided some light.

I put on the goggles and man it was like daylight. I could see my whole backyard like it a bright and sunny. I was flying a quad with the Caddx Ratel Pro. That camera is so good in low light I actually flew it once when it was pitch black in the backyard. Granted during that flight the video turned black and white but I could still see the trees to avoid them.

When I finished this last flight in the evening I thought to myself that the camera was really impressive and the SpeedyBee VRX was really impressive. That's why I like analog. I can tinker and swap things around to play.

Yes I know Walksnail has a 4K Moonlight kit. However I looked at the picture and the hardware looked so big and heavy.

Sorry no videos of low light flying because I was too busy messing with the VRX. Maybe next time.