PX4 / PX4-Autopilot

PX4 Autopilot Software
https://px4.io
BSD 3-Clause "New" or "Revised" License
8.26k stars 13.42k forks source link

Camera Trigger: Impossible to configure mavlink only trigger without PWM on PixRacer #11634

Open fredowski opened 5 years ago

fredowski commented 5 years ago

It is not possible to configure the camera trigger interface as mavlink message only without influencing and killing the PWM outputs. I tried this on PixRacer Hardware on a fixed wing plane with X-UAV Mini Talon airframe.

To Reproduce I setup the camera trigger via QGroundControl 3.5.0. The firmware is a custom version with minor changes (airframe plus a modified MAVLINK_MODE_MINIMAL message list) based on the 1.8.2 release (see https://github.com/fredowski/Firmware/commits/searchwing18 ). I guess that the modifications are not related to this problem but I mention the anyway. The camera trigger parameter setup is:

TRIG_MODE: 2 (This does not matter as long as the camera trigger is not disabled) TRIG_INTERFACE: 3 (MAVLINK Interface - no PIN modification expected) TRIG_PINS: 56 (default)

Expected behavior I expect the camera trigger to appear as mavlink only message on telemetry 2 port without modifying the PWM outputs on the PixRacer. So it should still be possible to use the PWM5 output for the motor.

Observed behavior The observed behavior is that once the camera trigger setup is activated, the motor starts as the motor of the plane is connected to PWM MAIN 5 (Servo Pin 5 on the PixRacer). Stupid as I am I had the propeller still attached...

Questions The setup process is a two step process where first the camera trigger is activated and only then the further parameters can be modified. I tried to modify the parameters via the QGC parameter list directly but without the TRIG_MODE parameter, the other parameters seem not to exist.

stale[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale[bot] commented 5 years ago

Closing as stale.

stale[bot] commented 4 years ago

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.