Topics created by JP Drone

@Eric-Katzfey Thank you for your work!
It successfully resolved the issue. The unexpected characters no longer appear on the OSD.
I appreciate your support and quick response.

@JP-Drone said in Support Photo/Video Capture via RC Switch:

MAV_CMD_IMAGE_START_CAPTURE

How are you handling the mavlink camera protocol exchange within voxl-px4? I know that there is the ability to forward commands to the GCS if using mission commands (but not manually flipping an RC switch).

Alternatively when using a joystick you can map a button to image capture: https://docs.px4.io/v1.15/en/camera/mavlink_v2_camera.html#manual-controllers

Currently the mavcam manager fully implements the camera protocol to send the ack for the incoming mavlink commands. It also handles the capture and video stream status (satisfies the mavlink camera protocol).

My only issue with implementing this is that the upstream voxl-px4 will not be camera protocol compliant and thus we are bypassing the entire protocol just to get camera image capture from the autopilot instead of the GCS (which also implements the same camera protocol). If you have a way to implement the protocol (even a stripped down version of it) please send a link so I can look at the code.

@JP-Drone ,

Please try to upgrade to latest voxl-portal version from here : http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64//

I just tested on iphone displaying individual and multi view, it works. What camera feed are you selecting (name)?

The non "encoded" feeds are compressed to mjpeg format which should play on majority of browsers.

I will check regarding the video recording feature in voxl-portal.

Alex

@Eric-Katzfey
Thank you for your quick update.
I was able to confirm that it is functioning properly.
Really appreciate your support. Wishing you a wonderful New Year!

@Jeremy-Frederick, can you specify which ESC you are asking about?

The PWM pins on the ModalAI ESCs (which have the pwm signals on a connector or test pads) are bi-directional, and yes they could be used as PWM output. However, a firmware change is required and enabling PX4 to send out PWM signals is another change

We were considering enabling this feature but it is not yet implemented. Can you please provide more information about your requirements?

what type of PWM signal are you trying to send ? min/max range, update frequency, (is it one shot, or just preriodic) how often are you planning to update the value of this PWM signal? how many PWM signals do you need? what is the source for the control of PWM signal in your application (RC or something else?). The reason why I am asking, the ESC would need to receive a serial data packet from voxl_esc driver in px4, so somehow that pwm output information would need to enter the voxl_esc driver.

Alex

@JP-Drone VOXL Flight doesn't handle cameras any differently than VOXL so that is a bit surprising to me that it would work on one but not the other as they are they same hardware and software

solved.
I found rotate_tracking option of voxl-configure-cameras command.

this usually means one of the following:

camera configuration does not match what is installed. the configuration needs to match what is installed, not what you want to use a connector is not properly seated a connector is backwards

@Eric-Katzfey Yes, it works.
I am not sure if changing the settings on the GCS side will affect the connection to other copter.
But now it seems fine.
Thanks.

@JP-Drone In my case, I was using the rb5 so the correct service was voxl-px4-imu-server, which was already running. The qvio, vison-px4 takes imu from imu_px4 not imu0. This is specific for the rb5.

@Matt-Turi Thank you for your quick response.
After updating to v0.0.5, it worked!

If you've made specific changes to specific config file you'll need to back them up manually either to a host pc or the data partition, otherwise the data partition will be saved which contains the camera calibration files and the factory settings for the config files which can be restored on a new system with voxl-configure-mpa --factory-reset