I've crashed my quad (analog Chimera 5) from low altitude. Visually no issues. No cracks or loose contacts. Arming is fine, motors revolutions are normal. Roll, pitch and yaw generate also normal motor response and sound. The only problem is with throttle. When I raise throttle stick even for 1-2 notches, seems motors overreact and produce too much power. When I move throttle stick further to notch 3 on my Jumper 18, motors start to accelerate by themselves, even lowering throttle to minimum does not help to slow it down, it just keep going. I can stop motors only by disarm. I wonder how motor revolutions at arming can be normal, but so much overreacting at throttle stick move. I restored original configuration in betaflight but it did not help. Probably hard landing harmed FC or ESC (but why only for throttle response). Need advice to debug the issue. Below is the video how quad behaves now. Thanks in advance for the help.

P.S. I've put in on the bench without props after trying to fly. Same weird reaction to throttle with props on as well.

Crazy throttle response

hello!

I'm working on understanding the relationship between Throttle MID and Throttle Expo.....The TRYP simulator has an option to adjust rates and I'd like to dial it in to get as close to the feel of my Nazgul Evoque 5".   right now I have them set at throttle MID (.3) and Throttle Expo (.5).   this isn't quite there. I like more power under half throttle. a linear throttle curve doesn't quite do it. 

I'd like a little more torque / power below half throttle position and then a linear curve above that.....

am I making sense? 
 

can anyone help achieve that?

This is a little tip I picked up recently.  You stagger the motor wire joins so they don't flare out as much.  More for builders that reuse motors and need to adjust wire lengths.

Works a treat!   Here's an example with some trusty mamba 1105's that are going into my night flyer v2 project soon.

Attached Files

Thumbnail(s)
   

Hi all,

I'm new to the forum so apologies if I don't know how it all goes on here just yet. I am a beginner FPV pilot and have just build my second quad after my first one ended up in a crater lake (boy, was I sad).

I finished the build and everything looked great. It worked, the motors spin when tested in Betaflight and my Taranis X7 bound with the new Crossfire Nano RX on my drone. However, for some reason my receiver does not register any inputs on Betaflight. I scoured the internet (and this forum) for days trying to look for a solution. Double-checked the UART, went into Agent-X to check the output map, checked the soldering, etc. etc. I still consider myself very much a beginner even though this is my second quad. I am at a loss here, I have no idea what's wrong and I was hoping this forum could help me figure it out.

Below you can see the soldering joints from the Crossfire Nano RX to my SpeedyBee F405 V3. Sorry if the RX joints are a little unclear. I made the stupid mistake of ziptying and taping things in before checking whether the receiver worked in Betaflight.



This is my Agent-X output map:


And I have attached my CLI dump. I haven't set anything up for the drone as I first wanted to make sure the receiver was working.

I really want this to work and this forum is my last hope.
Thanks a lot in any case!

Cheers,
Sunny

Edit: I fixed it! It was probably a faulty UART (strange considering it was a completely new board). I switched it to another UART and now everything is working.

Attached Files

  CLI Dump.txt (Size: 28.27 KB / Downloads: 39)

Recently Bardwell did this with ELRS (I think).  Today out flying I had set my 5” down after flying (forgot to unplug), grabbed my 4” plugged it in didn’t even think about model selection.. both are on crossfire.  I moved over to the field.. armed took off and heard weird noises.  I thought a fellow fixed wing pilot was launching.. nope the 5” in the back of my truck launched. 
   I didn’t think this was possible… I believe I may have “bound” both RXs on the same model in my taranis

Hi all,

I am currently having some difficulties building my first Naked GoPro 9. I watched some videos online and got it all taken apart. Put it into a NamelessRC case with the BEC board. 

To power it, I am using the method shown here:  to draw power from a 4s LiPo balance lead. My multimeter is giving me a reading of 9.1V which I am plugging into the NamelessRC BEC board. Then nothing happens. The GoPro doesn't seem to be doing anything when I plug it in or when I press/hold the power button. One of the first times when I plugged it in, I saw a red light flash but nothing else after that. 

I am very new to this and am not sure where to go from here. I reopened the GoPro and double checked the ribbon cable connections. Any advice would be greatly appreciated.

Thanks!

Hello, as the title states I have no OSD on my Thinking P16. I am attempting to use it with the DJI Goggles 2. At this point I'm liking my Cetus X with the simplicity of analog more than this thing. I am new to FPV.

This is the one I have: https://www.getfpv.com/geprc-thinking-p1...ystem.html
Picture of the FC/Vista wiring is attached, as well as the dump from 4.1.7 that I believe should work.

I feel like I've tried everything:

• OSD is enabled
  
• Telemetry is enabled
  
• Auto/NTSC/PAL makes no difference
  
• Uploaded the default font again, tried different fonts
  
• The correct wires are wired from the Vista to TX1/RX1/nR2/etc on the FC, MSP is enabled on UART1 and SerialRx on UART2 (see attached photo for wiring & dump for Betaflight config)
  
• Re-reviewed the wiring diagram for my FC & confirmed all connections are going to the right place (https://geprc.com/wp-content/uploads/202...N-V1_4.pdf - this appears to be the one I have)
  
• Tried the instructions on two threads in this forum, which I believe don't apply because I have enough UARTs. Those folks must have a different FC where the LED pinout needs to be repurposed (https://intofpv.com/t-geprc-thinkingp16-...age-or-osd and https://intofpv.com/t-no-osd-on-dgi-goggles). Tried it anyway, didn't work (again not surprising since I have nothing soldered to the LED pinout on my FC).
  
• The receiver works with my DJI FPV Remote 2 (I had to set SBUS_BAUD_FAST=ON, it was OFF from the factory. I also tried setting to OFF to troubleshoot the OSD, no dice)
  
• Upgraded to Betaflight 4.2, configured UARTs and reconfirmed settings above (OSD on, UARTs configured, telemetry, tried NTSC/PAL, etc), no dice
  
• Upgraded to Betaflight 4.3, configured UARTs and reconfirmed settings above (OSD on, UARTs configured, telemetry, tried NTSC/PAL, etc), no dice
  
• Downgraded back to 4.1.7 (which I believe is the highest version my FC supports due to its gyro - see more here: https://geprc.com/downloads/thinking-p16/, I have the HD Version with MPU6000). I applied the board defaults, tried to configure the OSD from scratch, and I tried it with presets I loaded from a backup I made as soon as I got the quad. No dice.
  
• Checked all solder joints for continuity with a multimeter (some looked better than others from the factory, I resoldered one of them, but all checked out before & after)
  
• Checked for shorts with a multimeter
  
• Checked the RX, TX, and SBUS pinouts on the Vista against ground to see if the diodes were fried in the Vista. They are not.
  

Attached Files

Thumbnail(s)
   

  DUMP-BTFL_cli_Thinking_P16_20230115_092549.txt (Size: 26.82 KB / Downloads: 57)
  DIFF-BTFL_cli_Thinking_P16_20230115_092602.txt (Size: 1.54 KB / Downloads: 65)

Target
FCF411-FTE
Makefile
MATEKF411TE
Receiver is a FrSky ARCHER M+
Camera RunCam model Phoenix 2
Video TX Atlatl HV micro
Connections as per MATEKSYS F411-WTE product page:
Video to ST2
SmartPort to ST1
In INAV Ports SOFTSERIAL1 set to Telemetry SmartPort Auto
SOFTSERIAL2 set to Peripherals TBS SmartAudio 115200
Yaw left Pitch forward brings up OSD menu
'Features' lists VTX but no SA or TR and operations eg power, change screen value but not on Video Tx
CLI set vtx ops do not work eg set vtx_band=4 neither does programming as per Pawel Spychalski.
Everything else working

Can anybody help please

Hi, I am having some issues with my Mobeetle6 and would seriously appreciate some assistance.
New to the hobby and have tried everything I can think of.

In Horizon and Angle mode (line of sight), the Mobeetle6 starts its hover fine and stable. Upon giving it power (~70% or more) it begins to aggressively roll to the left. After bringing it back to "hover" it now continues to roll left, and I have to fight it, making it borderline unflyable. 

In Acro and Air mode with goggles, a similar thing occurs. When giving it power (~70% or more), it rolls to the left and shakes/trembles (and feels like it lacks power). After bringing it back to a hover the trembles dissipate. 
And, after a few (rough) punch-outs and bringing it back to a "stable" hover my artificial horizon is out of whack, sometimes even at around a ~45 degree angle.

Did I get a faulty gyro? (but some symptoms in Acro...?)

I have tried several presets/tunes (including the official Happymodel "updated" one from: " https://www.happymodel.cn/index.php/2022...le6-drone/ ")
I have tried wiping the FC once with new firmware.
I am running latest Betaflight 10.9.0-debug-1eaf329
Flashed baked in version of ELRS 3.x firmware to the SPI/FC. 
Props are healthy, motors seem fine from what I can tell.
Version came as ELRS v2.0 Betaflight 4.3

I have no idea what the next step is from here. 
Help would be very much appreciated.

Thank you!

Hey guys.
Complete newbie here coming from budget gps drones.

So I came into possession of a Redcat Carbon 210
For those who've never heard of it, it's basically a Tovsto/Walkera f210 that's set up as a RTF toy kit.
So the whole point is NOT to connect it to cleanflight/betaflight...lol

But there's an issue that when I arm the motors they spin up and freak out!

So I managed to get it connected to cleanflight and in the receiver tab all the (gimbal?) values are jumping around like crazy (sometimes some, sometimes all) and it's giving an i2c error 3
That's all I got...I can't even find an errors log or any information on i2c error codes or even an error codes list for cleanflight...
Not surprisingly... I'm baffled...

Any Ideas??