ArduPilot / ardupilot

ArduPlane, ArduCopter, ArduRover, ArduSub source
http://ardupilot.org/
GNU General Public License v3.0
10.91k stars 17.41k forks source link

Gimbal tilt control doesn't work when using PPM input from RX #868

Closed tensafefrogs closed 10 years ago

tensafefrogs commented 10 years ago

I was just trying to set up gimbal tilt control via channel 6 on my TX but couldn't get it to work. I suspect that the issue was because I'm using PPM input from my RX to the APM (2.6).

APM versions: 3.1 and 3.1.2 (I tried upgrading just in case it was a recently fixed issue)

My setup is as follows:

As a workaround (and so I know the gimbal does work), I've connected my RX directly to the gimbal tilt control input, bypassing APM altogether. But if there is better ROI support in the future (or just for cleanliness) it would be nice to connect it all up through APM.

Let me know if you have any q's or need me to try some other config. I'll see if I can verify that it all works when not using PPM if I have some time this week to tinker with it.

jason4short commented 10 years ago

I use this all the time. Can you post your params? Also verify you are actually connected to A11 and A10. The labeling is sometimes skewed. There are two rows of pins, then A11... You can also connect a servo to test. Just use the power and ground from your servo rail and put the signal wire to A11. Don't power directly off of the aux pins. You can brown out the APM by drawing too much power with a servo.

tensafefrogs commented 10 years ago

Hmm, ok, lets go through it:

[1] Radio Calibration: screenshot 2014-03-03 01 00 34

[2] Gimbal setup screenshot 2014-03-03 01 02 19

[3] PIDs screenshot 2014-03-03 01 04 39

And I believe that's all it should take, right? Again, it works if I connect the gimbal directly to my RX and move the CH6 knob on my TX, and I can also see the gimbal move if I change the min/max values on the gimbal page of APM Planner, which suggests that that A11 output is correct, there just seems to be a problem between the RX PPM input and converting that to PWM output on the A11 pin.

Let me know if you see anything wrong here or have ideas to try out.

ofishel commented 10 years ago

Any updates on this? I running into the same issue with APM 2.5 with 3.1.5 firmware and a Tarot T-2D gimbal.

rmackay9 commented 10 years ago

I've updated the instructions for setting up the Tarot 2D gimbal just yesterday. It should all work. http://copter.ardupilot.com/wiki/common-tarot-gimbal/

The bit that was unclear was what to set the Servo Limits and Servo Angles to. There are instructions there now on what those mean.

ofishel commented 10 years ago

Will these steps work for an APM 2? I noticed the change from CH11 to CH9 for what looks like just Pixhawk. I tried to switch it anyway, but the gimbal didn't get any signal (solid blue light).

I switched it back to CH11 and tried to control the gimbal through my TX again without success. However, when I start the gimbal, it sets itself to 0 degrees. If the click the "Reverse" box in the Tilt options, the gimbal moves to -90 deg. It's clearly getting a signal from the APM, but it isn't picking up the readings from CH6 from my TX

ofishel commented 10 years ago

Update: For some reason, I was able to work via CH10 in the Windows Mission Control application. I also reversed the settings so that the pot at min settings puts the gimbal at 0 deg. So odd.

rmackay9 commented 10 years ago

I'm going to close this because I don't think the above was all just configuration issues. Please holler if I got it wrong.

jgeragi commented 9 years ago

I have exact same issue as tensafefrogs. Same setup as well. I notice that stabalize does not seem to be working on the roll axis servo as well? If I change the servo limits the servos move. I used to be able to pick up while disarmed and see servos moving to stabilize camera but this is not happening. I too am unable to control via CH 6 but I suspect it will work if I connect as tensafefrogs did, but what about stabilize??