-
Notifications
You must be signed in to change notification settings - Fork 4.7k
MavLink (PX4 sitl) triggering camera #734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Which messages you are interested in handling? Currently we only handle actuator messages, i.e., how vehicle moves around. |
Since the HITL messages is implemented, and it's reasonable to use AUX channels for the gimbal the only new message i would like to implement is the CAMERA_TRIGGER message. The PX4 tutorial for camera trigger states that if |
I've made this work but I'm no longer sure that using the After i get a response from the MavLink guys, support in PX4 is the next step. |
Let us know how this goes. We haven't used these features yet... It would be great if you can submit a PR with your change! |
On related note, I just added Gimbal APIs in AirSim: https://github.com/Microsoft/AirSim/blob/master/docs/image_apis.md#camera-orientation-gimble |
We're doing an application that requires the possibility of planning a mission from QGC with camera caputre. It seems like AirSim currently doesn't do anything with the corresponding MavLink message, would it be of interest to have such features up-streamed?
If my limited understanding of the codebase is correct it should be implemented in the
handleMessage
method of a subclass ofMavLinkNodeImpl
. WouldMavLinkVehicle
or a new class similar toMavLinkVideoServerImpl
make the most sense?The text was updated successfully, but these errors were encountered: