I can not control Yaw of my quad copter via radio stick

Hi,
I can not control Yaw of my quad copter via radio.
I’ m using the controller Pixhawk with the firmware ware 3.3.3.

I have following tested

  • Stabilize Mode
  • Alt Hold Mode
  • Loiter Mode
  • RTL
  • Auto Mode together with Circle
    All modes are working in normal, simple and super simple.
    It is real fun.

But I cannot control yaw with my radio. If I use the yaw-stick during flight, the yaw of my copter doesn’t change. At Mission Planner Status h4in is shown that the yaw value is changing with the yaw-stick movement.

I am sure that I have made a wrong input.
After I could not solve the Problem, I have reset the firmware together with the parameter und changed

  • Extneded Parameter, the copter is a little bit over controlled, but no problem
  • Advanced Parameter, I have changed battery Volt and Current parameter
  • some radio parameter adaption
    That means not very much.

But the problem with the yaw control remains.

Perhaps someone had the same problem and got help.
Perhaps he will help me

Thank you for your help.

Hi,
I believe, you will need more information.

When you see the parameter below, may be you will not believe that I had no problem with the flight modes

  • Stabilize Mode
  • Alt Hold Mode
  • Loiter Mode
  • RTL
  • Auto Mode together with Circle. The only Problem is.
    I just can’t control the heading (yaw) of the Copter.

Here are parameters of the last 3 flights.

Analyses of flight 1)
Log File C:\Users\r\AppData\Local\Temp\tmp191C.tmp.log
Size (kb) 35496.9208984375
No of lines 438234
Duration 0:25:30
Vehicletype ArduCopter
Firmware Version V3.3.3
Firmware Hash acf2e10c
Hardware Type
Free Mem 0
Skipped Lines 0

Test: Autotune = NA -
Test: Balance/Twist = NA -
Test: Brownout = FAIL - Truncated Log? Ends while armed at altitude 14.59m
Test: Compass = GOOD - mag_field interference within limits (21.10%)

Test: Dupe Log Data = GOOD -
Test: Empty = GOOD -
Test: Event/Failsafe = FAIL - ERRs found: FLT_MODE CRASH
Test: GPS = FAIL - Min satellites: 0, Max HDop: 99.99
Test: IMU Mismatch = GOOD - (Mismatch: 0.12, WARN: 0.75, FAIL: 1.50)
Test: Parameters = GOOD -
Test: PM = NA -
Test: Pitch/Roll = NA -
Test: Thrust = NA -
Test: VCC = FAIL - VCC below minimum of 4.6v (4.089v)
Parameter of fligt 1)
File to big

Analyses of flight 2)
Log File C:\Users\r\AppData\Local\Temp\tmp90.tmp.log
Size (kb) 7208.974609375
No of lines 91089
Duration 0:08:15
Vehicletype ArduCopter
Firmware Version V3.3.3
Firmware Hash acf2e10c
Hardware Type
Free Mem 0
Skipped Lines 0

Test: Autotune = NA -
Test: Balance/Twist = NA -
Test: Brownout = GOOD -
Test: Compass = FAIL - Large change in mag_field (57.19%)
Max mag field length (628.19) > recommended (550.00)

Test: Dupe Log Data = GOOD -
Test: Empty = GOOD -
Test: Event/Failsafe = FAIL - ERR found: CRASH
Test: GPS = GOOD -
Test: IMU Mismatch = GOOD - (Mismatch: 0.27, WARN: 0.75, FAIL: 1.50)
Test: Parameters = GOOD -
Test: PM = NA -
Test: Pitch/Roll = NA -
Test: Thrust = NA -
Test: VCC = GOOD -
Parameter of fligt 2)
2016-09-16 16-51-16.bin (3.3 MB)

Analyses of flight 3)
Log File C:\Users\r\AppData\Local\Temp\tmp1129.tmp.log
Size (kb) 10389.2939453125
No of lines 131895
Duration 0:08:17
Vehicletype ArduCopter
Firmware Version V3.3.3
Firmware Hash acf2e10c
Hardware Type
Free Mem 0
Skipped Lines 0

Test: Autotune = NA -
Test: Balance/Twist = NA -
Test: Brownout = GOOD -
Test: Compass = FAIL - Large change in mag_field (58.21%)
Max mag field length (602.79) > recommended (550.00)

Test: Dupe Log Data = GOOD -
Test: Empty = GOOD -
Test: Event/Failsafe = FAIL - ERR found: FLT_MODE
Test: GPS = GOOD -
Test: IMU Mismatch = GOOD - (Mismatch: 0.15, WARN: 0.75, FAIL: 1.50)
Test: Parameters = GOOD -
Test: PM = NA -
Test: Pitch/Roll = NA -
Test: Thrust = NA -
Test: VCC = GOOD -

Parameter of fligt 3)
File to big with 4.5 MB

Hello,
Ich konnte mein Problem mit Hilfe des folgendes Diagramms lösen:

Das Diagramm zeigt alle Ausgänge an Motor 1 bis Motor 4
Dabei erkennt man, dass Motor 1 und 2 mit Minimalwerten (ca. 1800) angesteuert werden und
Motor 3 und 4 mit Maximalwerten (ca. 1300). Eigentlich müsste müsste der Copter bei solchen Werten schnell antiglockweise drehen. Tat der Copter aber nicht, er blieb relativ ruhig stehen, was man an ATT.DesYaw und ATT.Yaw sieht. Das hat mich auf die Idee gebracht, dass die Probs falsch montiert sind. Die hinteren Probs mussten ausgetauscht werden.
Seit dem läuft der Quadcopter correkt und Yaw kann über Die Fernsteuerung eingestellt werden.
Das Ganze war blöd von mir. Jetzt kann ich mit der Gimbala-Ansteuerung für die Kammerasteuerung weiter machen.
Ich wünsche eine gute Nacht