We use cookies to try and give you a better experience in Freshdesk.
You can learn more about what kind of cookies we use, why, and how from our Privacy policy. If you hate cookies, or are just on a diet, you can disable them altogether too. Just note that the Freshdesk service is pretty big on some cookies (we love the choco-chip ones), and some portions of Freshdesk may not work properly if you disable cookies.
We’ll also assume you agree to the way we use cookies and are ok with it as described in our Privacy policy, unless you choose to disable them altogether through your browser.
Gimbal with Pixhawk
NOTE: Pixhawk supports multiple flight stacks: PX4 or Ardupilot. Please choose the right setting bellow.
The Gremsy’s Gimbal that can communicate with PX4/Ardupilot (Copter) by using Mavlink v2
NOTE: Support for this Gimbal is include in Copter 3.3 (or higher) for gimbals running
1. What’s New?
2. Connecting the gimbal to the Pixhawk
Connect cable from COM2 port on Hyper Quick release to Telem2 (Recommend for flight stack PX4) or Telem1(PX4 does not support) on Pixhawk.
Baurate on Pixhawk should be set at 115200bps, 8 Data bits, No Parity, 1 Stop Bit (8N1)
NOTE: The remaining 3 pins (VCC, RTS, CTS) of the cable should not be connected
3. Set-up through the Mission Planner (Mavlink protocol with default Flight Stack Ardupilot)
Through your GCS (i.e MP’s Full Param List or Tree) set the following parameters:
Using Telem 1
Using Telem2
Set up MNT parameter
4. Set-up through the QGroundControl (Mavlink protocol with default Flight Stack PX4)
4.1 Set up mavlink
4.2 Changing the baud rate
NOTE: JUST using the Telemetry 2
4.3 Gimbal (mount) Control Setup with Pixhawk (Flight Stack PX4)
PX4 contains a generic mount/gimbal control driver with different input and output methods. The input defines how you control the gimbal: Via RC or via Mavlink commands (for example in missions or surveys).
The output defines how the gimbal is connected: some support MAVLINK commands, others use PWM (described as AUX output in the following). Any input method can be selected to drive any output. Both have to be configured via parameters.
NOTE: PIXHAWK need to setup MNT_MODE_OUT: MAVLINK. MNT_MODE_IN is up to your methods. (via RC or MAVLINK commands)
0 Votes
1 Comments
mdk posted over 2 years ago
Why do these instructions show 3 possible settings for MNT_DEFL_MODE?
Set “MNT_DEFL_MODE” to “3” that is the RC targeting mode.
Set “MNT_DEFL_MODE” to “2” that is the Mavlink targeting mode (DO_MOUNT_CONTROL)
Set Set “MNT_DEFL_MODE” to “4” that is the GPS point mode (DO_SET_ROI
If I am flying mapping missions from QGroundControl what setting am I to use to point the camera?
0 Votes
Login or Sign up to post a comment