@jameskuesel Thanks! Merged

@Richa . thanks for the details, got it it. I will need to test the master / slave mode. Is your plan to have one IMX664 generate the sync signal (master) and the other(s) IMX664 being slaves? or all slaves? I should be able to give it a quick test this week. The change would involve setting several additional registers in the camera configuration, which would mean a change in the sensormodule driver for the camera. we can figure this out after i verify the functionality. Alex

Hi @Nate-The-great Please do not delay any of your efforts or programs in anticipation of a VOXL 3 platform. Our development roadmap is company confidential, but you can imagine we are working on many new and exciting things. One of the goals we have is to minimize disruptions should someone wish to "upgrade" platforms in the future. Similar to how we transitioned from VOXL to VOXL 2 by keeping mounting patterns the same, expansion compatibility (J13 -> J3), and plug-in board and sensor compatibility (M0048, M0030, M0084 & M0135 Camera adapters, etc), we would mimic that approach, but strive to make it even more seamless than before. Therefore, there is very little to no risk to your system if you start developing on VOXL 2 today. Hope that helped.

Hello @Kiran , the only TOF sensor that we currently sell is the following: https://www.modalai.com/products/m0178?variant=48528287793456 https://docs.modalai.com/M0178/ In terms of identifying unique features of individuals, you will have you decide whether this works for you. Here is a typical output of the this TOF sensor looking at a person. This is a depth image, but a point cloud output (for each frame) is also available. In order to build a map, you would need to use some mapper software (we provide a reference such as https://docs.modalai.com/voxl-mapper/). However you would need to be familiar with mapping algorithm(s) and learn how the software components work in order to get mapping to work well and tune it for your application. [image: 1744216152094-9b4bee44-2643-4aed-a20f-4ec2592af56b-image.png] Alex

@Eric-Katzfey Yes. This is regarding the Starling 2 Max GPS-denied Development Drone.

@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.

@Zachary-Lowell-0 Perfect, thanks! I'll try it when I get some time next week.

@blue OK thanks for the beta feedback. We will keep that in mind. I'm sure what we did was to mimic an existing OTS product at first, and that used a backplate. I'll get with our production team to ensure we have a backplate in future kits for this version. Thanks!

@Eric-Katzfey Thank you for the clarification!

@Aaky , Please check the following thread for more information: https://forum.modalai.com/topic/3459/masking-qvio/ My suggestion: download the test mask from here : https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/misc/mask_example_160x120.pgm . which has top half of image black (0), and bottom half white (255). values of 0 is where new features will be allowed to be detected You can use gimp, to modify the mask and before saving you can threshold it so that the values are all 0 and 255 (nothing in between, just in case). export from gimp as pgm (raw) do a test with the original mask example, make sure no features are picked up in the bottom image. This is the baseline test then try your new mask, you can also overlay the mask on top of the QVIO overlay, just like the other user did for checking. Also please note (from the other thread) to pay attention to the fact that QVIO mask path is relative to where qvio server starts. So if you start it as a service, it's working directory will be / but if you run it manually, the working directory will be your current directory in the terminal - the other thread explains that issue. Alex

@cfirth said in Update SDK docs on installing ROS2 on VOXL2: they Thanks for the comment @cfirth - this has been updated in the gitlab and is waiting to be merged for the document update!

since voxl-streamer can provide RTSP streaming from VOXL2, ffmpeg can be used on the host machine for recording outside of QGC. You can find some helpful information by searching ffpmeg save rtsp stream to a file . for example : https://medium.com/@tom.humph/saving-rtsp-camera-streams-with-ffmpeg-baab7e80d767

@tcg6000 It is possible, of course, for us to build without connectors, but it is expensive to do a custom build. There would be an MOQ of 200 units to get to similar pricing as found on our webpage.

@brinkap unfortunately, there is no CAN capability on VOXL 2. You would need to have an adapter PCB that supports CAN connects to one of the available interfaces, and then write a Linux driver that enumerates as can0

@Samer-Jaradat What kind of a drone do you have?