# Camera Interfacing & Triggering

**URL:** <https://discuss.px4.io/t/camera-interfacing-triggering/385>\
**Category:** Flight Testing & Log Analysis\
**Created:** [May 1, 2016, 3:28pm UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385 "2016-05-01T15:28:38Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![LorenzMeier](https://discuss.px4.io/user_avatar/discuss.px4.io/lorenzmeier/32/17_2.png) [@LorenzMeier](https://discuss.px4.io/u/LorenzMeier)\
**Post date:** [May 1, 2016, 3:28pm UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/1 "2016-05-01T15:28:38Z")

</div>

@Justin_Cooper This topic is best suited for a longer discussion on triggering, which is super interesting but unrelated to the release discussion.

---

<div class="post-metadata">

**Author:** ![Justin\_Cooper](https://discuss.px4.io/letter_avatar_proxy/v4/letter/j/e274bd/32.png) [@Justin\_Cooper](https://discuss.px4.io/u/Justin_Cooper)\
**Post date:** [May 1, 2016, 3:37pm UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/2 "2016-05-01T15:37:58Z")

</div>

@dogmaphobic

Pix4d had a mapping ground station app for DJI and they do not recommend shooting in manual mode when mapping.

---

<div class="post-metadata">

**Author:** ![dogmaphobic](https://discuss.px4.io/user_avatar/discuss.px4.io/dogmaphobic/32/221_2.png) [@dogmaphobic](https://discuss.px4.io/u/dogmaphobic)\
**Post date:** [May 1, 2016, 3:45pm UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/3 "2016-05-01T15:45:37Z")

</div>

As I said, I have never done mapping so I can’t speak for that. In what I do, it’s always manual as I don’t want the variations introduced by the camera. With that said, assuming we nail down the triggering system, what you now want is something new. A feedback system. Let me talk to @LorenzMeier and see how that could be integrated (both hardware and software).

---

<div class="post-metadata">

**Author:** ![Justin\_Cooper](https://discuss.px4.io/letter_avatar_proxy/v4/letter/j/e274bd/32.png) [@Justin\_Cooper](https://discuss.px4.io/u/Justin_Cooper)\
**Post date:** [May 1, 2016, 3:49pm UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/4 "2016-05-01T15:49:26Z")

</div>

Sounds good. Thank you.

---

<div class="post-metadata">

**Author:** ![Justin\_Cooper](https://discuss.px4.io/letter_avatar_proxy/v4/letter/j/e274bd/32.png) [@Justin\_Cooper](https://discuss.px4.io/u/Justin_Cooper)\
**Post date:** [May 1, 2016, 3:58pm UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/5 "2016-05-01T15:58:21Z")

</div>

FYI hardware wise @bchristal makes the feedback cables.

---

<div class="post-metadata">

**Author:** ![Justin\_Cooper](https://discuss.px4.io/letter_avatar_proxy/v4/letter/j/e274bd/32.png) [@Justin\_Cooper](https://discuss.px4.io/u/Justin_Cooper)\
**Post date:** [May 1, 2016, 4:25pm UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/6 "2016-05-01T16:25:49Z")

</div>

@LorenzMeier

I thought I would post this here since its camera related but is a 1.3 issue. We need a simple button in the camera tab to hit to test the camera is triggering otherwise we do not know if we have it setup correct until we throw it in the air.

---

<div class="post-metadata">

**Author:** ![dogmaphobic](https://discuss.px4.io/user_avatar/discuss.px4.io/dogmaphobic/32/221_2.png) [@dogmaphobic](https://discuss.px4.io/u/dogmaphobic)\
**Post date:** [May 1, 2016, 4:36pm UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/7 "2016-05-01T16:36:08Z")

</div>

That’s in my todo list 🙂

---

<div class="post-metadata">

**Author:** ![andrejpan](https://discuss.px4.io/user_avatar/discuss.px4.io/andrejpan/32/3611_2.png) [@andrejpan](https://discuss.px4.io/u/andrejpan)\
**Post date:** [September 15, 2016, 4:04pm UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/8 "2016-09-15T16:04:46Z")

</div>

Is anything new on this topic? I have a uEye UI-3241LE camera. I found how I could connect wires, but Pixracer is apparently lacking AUX output. Would mapping somehow solve this? Or could I attach some other chip which could work as AUX output?

---

<div class="post-metadata">

**Author:** ![Orico4](https://discuss.px4.io/letter_avatar_proxy/v4/letter/o/c68b51/32.png) [@Orico4](https://discuss.px4.io/u/Orico4)\
**Post date:** [September 15, 2016, 4:09pm UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/9 "2016-09-15T16:09:40Z")

</div>

I think Piercer’s 6 main output can be config to 4 wpm + 2 trigger? can that work for you?

---

<div class="post-metadata">

**Author:** ![andrejpan](https://discuss.px4.io/user_avatar/discuss.px4.io/andrejpan/32/3611_2.png) [@andrejpan](https://discuss.px4.io/u/andrejpan)\
**Post date:** [September 15, 2016, 4:14pm UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/10 "2016-09-15T16:14:44Z")

</div>

Yeas, how I can implement this?

---

<div class="post-metadata">

**Author:** ![Orico4](https://discuss.px4.io/letter_avatar_proxy/v4/letter/o/c68b51/32.png) [@Orico4](https://discuss.px4.io/u/Orico4)\
**Post date:** [September 15, 2016, 6:12pm UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/11 "2016-09-15T18:12:07Z")

</div>

I think that is straight forward using QGC.  
Connect pixracer to QGC and there is a ‘camera trigger’ tab, click on it, and select enable it on the right side of the screen.

Then it will show the output pin config map which you can set.

Something like this procedure.

---

<div class="post-metadata">

**Author:** ![andrejpan](https://discuss.px4.io/user_avatar/discuss.px4.io/andrejpan/32/3611_2.png) [@andrejpan](https://discuss.px4.io/u/andrejpan)\
**Post date:** [September 28, 2016, 4:15pm UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/12 "2016-09-28T16:15:23Z")

</div>

@Orico4 thanks for the help. I managed to make it work, but now I have different problem.

Setting up pins on Pixracer is not working correctly. Camera is triggered all the time, regardless what are the settings at QGC. Frequency of data is changing by it self, enabling and disabling GPIO pins also does not have any meaning.

Here is also a video when I tried to modify parameters: [https://sendvid.com/q80lolda](https://sendvid.com/q80lolda)

Any idea what I could do differently?

---

<div class="post-metadata">

**Author:** ![Thrane](https://discuss.px4.io/letter_avatar_proxy/v4/letter/t/0ea827/32.png) [@Thrane](https://discuss.px4.io/u/Thrane)\
**Post date:** [September 28, 2016, 9:21pm UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/13 "2016-09-28T21:21:27Z")

</div>

@andrejpan, could you please share how you got the Pixracer to trigger the camera at all? I have got a Pixfalcon, which has 8 main outputs and no Aux. The pin-options mentioned by Orico4 above all refers to “Aux”. From this discussion - [Camera trigger using Pixfalcon](http://discuss.px4.io/t/camera-trigger-using-pixfalcon/869) - I was under the impression that triggering a camera without aux-ports wasn´t possible.

---

<div class="post-metadata">

**Author:** ![Orico4](https://discuss.px4.io/letter_avatar_proxy/v4/letter/o/c68b51/32.png) [@Orico4](https://discuss.px4.io/u/Orico4)\
**Post date:** [September 29, 2016, 3:06am UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/14 "2016-09-29T03:06:26Z")

</div>

As to my knowledge Pixfalcon can not do this like pixracer, as they using different FMU architecture. The way i mentioned currently only works for pixracer or other FMU v4 FC.

---

<div class="post-metadata">

**Author:** ![Orico4](https://discuss.px4.io/letter_avatar_proxy/v4/letter/o/c68b51/32.png) [@Orico4](https://discuss.px4.io/u/Orico4)\
**Post date:** [September 29, 2016, 4:36am UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/15 "2016-09-29T04:36:31Z")

</div>

@andrejpan Sry but seems i can not help much on this right now, as i did not test this feature myself.  
i am not sure if it can work as expected, thought should work.

We are working on a better solution to this but will need some time.

---

<div class="post-metadata">

**Author:** ![Andreas\_Hoffmann](https://discuss.px4.io/user_avatar/discuss.px4.io/andreas_hoffmann/32/3467_2.png) [@Andreas\_Hoffmann](https://discuss.px4.io/u/Andreas_Hoffmann)\
**Post date:** [February 3, 2017, 1:12pm UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/16 "2017-02-03T13:12:19Z")

</div>

Sorry to taking this up again.

Is there a possibility to manually trigger the Camera Shutter via QGC?  
If not I’d like to raise a festure Request for this. I’m actually not aware if the Firmware would allow this and/or Mavlink/QGC can handle this?!

Anybody sone Info on this?

---

<div class="post-metadata">

**Author:** ![topometrics\_gr](https://discuss.px4.io/letter_avatar_proxy/v4/letter/t/9f8e36/32.png) [@topometrics\_gr](https://discuss.px4.io/u/topometrics_gr)\
**Post date:** [February 7, 2019, 11:07pm UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/17 "2019-02-07T23:07:40Z")

</div>

Hi,

I have a pixhawk 4 holybro and I set it up with firmware that I downloaded from qgroundcontrol but with missionplanner.

1. I set it up with mission planner as i coudn’t set up the bheli\_s escs with the qgroundcontrol .

2. I have a problem set up the shutter in mission planner for a mapir camera survey2.

Could you please help me as to how I can set up the camera fucntion

Thank you very much!

---

<div class="post-metadata">

**Author:** ![auturgy](https://discuss.px4.io/letter_avatar_proxy/v4/letter/a/e480ec/32.png) [@auturgy](https://discuss.px4.io/u/auturgy)\
**Post date:** [February 8, 2019, 7:37am UTC](https://discuss.px4.io/t/camera-interfacing-triggering/385/18 "2019-02-08T07:37:17Z")

</div>

[discuss.ardupilot.org](http://discuss.ardupilot.org) will be a better place to seek help for Missionplanner
