search

ArduPilot / MissionPlanner

Mission Planner Ground Control Station for ArduPilot (c# .net)
http://ardupilot.org/planner/
GNU General Public License v3.0
1.7k stars 2.34k forks source link

Max. throttle is not acquired #1566

Open sgr-gpt opened 7 years ago

sgr-gpt commented 7 years ago

Issue details

Please describe the problem, or desired feature When I am pointing the stick of my radio controller in the top extreme position for max throttle, I am getting only about 20% of it.

Version

What version was the issue encountered with I am using APM 2.6 board with mission planner 1.3.48 with firmware version 3.2.1

Platform

[ ] All [ ] AntennaTracker [ ] Copter - THIS ONE** [ ] Plane [ ] Rover [ ] Sub

Airframe type

What type of airframe (flying wing, glider, hex, Y6, octa etc) 'X' Quadcopter

Hardware type

What autopilot hardware was used? (pixhawk, pixracer, PX4FMU etc) APM 2.6

Logs

Please provide a link to any relevant logs that show the issue Not really sure.

meee1 commented 7 years ago

can you confirm your transmitter end point and travels are set correctly?

sgr-gpt commented 7 years ago

the transmitter end points for throttle pin are 956 to 1901. and I don't well understand what you mean by 'travels'

magicrub commented 7 years ago

How do you know you're only getting 20%? This sounds like a configuration error.

sgr-gpt commented 7 years ago

i was not able to get the escs callibrated through the software it showed an error- 'Set param error. Please ensure your version is AC3.3+' However my board is not able to download firmwares post 3.2.1. So i did manual calibration in which 1microsec signal corresponded to min throttle and 2 corresponds to max throttle. testing with a logic analyser a signal of only 1.2-1.3 micro sec was being obtained at max throttle.

narew commented 7 years ago

In situation like this, first thing what I do is display value of ch3in (or another "channel in" which supports thrust) and ch1out, ch2out , ch3out ,ch4out in "Quick" Window on FlightData page in MissionPlanner. Then connect wireless or by usb cable (without propeller on motors :) ), move throttle stick and check where is the problem: with input (RC transmiter) or with output (in autopilot config).

You can also check: