Carson— I'm trying to do the same: create a Kicad symbol for VOXL 2 as a module (ie, no internal details, just interfaces). Have you had any luck in locating something? Best, —John

@joshuagaus Sorry, but SBUS is not supported. That option will be hidden in future SDK releases to prevent confusion.

@Myles-Levine Nevermind, I got it working through the voxl interface instead of Qgroundcontrol. Thank you.

@Eric-Katzfey And this is also handy: https://www.sparkfun.com/breadboard-to-jst-ghr-04v-cable-4-pin-x-1-25mm-pitch.html

@jon For MONOTONIC the apps side uses the slpi version so that they are in sync. Your application should use apps MONOTONIC. PX4 will convert it using timesync.

@Moderator Thanks for the quick response! Which helper would you recommend for outdoor flight configuration with GPS? I see there are several available for different variations. An added detail: we need good relative altitude measurements at low altitudes for our custom precision landing solution.

@jimbow77 those drones are for aeronautical research. we recommend installing a dronetag or similar

@ggangmi What was the flight mode on takeoff and what did it unexpectedly change to? There should be logs in /data/px4/log. They may be incomplete or maybe even corrupted if the drone lost power in the crash but there should be something there. The logging starts when the drone is armed.

@Sarika-Sharma , Since you are testing different configurations, i would suggest to reduce the number of cameras first to find working cases and see if you may have a bad camera or a bad flex cable. So, try both tracking camera one at a time, then hires camera by itself, then two tracking cameras, then two tracking + hires, etc.. Alex

@Jetson-Nano , We have not tried QVIO with Boson, it may work (but we can't really support that). The boson output is usually a bit fuzzy, so i am not sure how the feature detection will work, but it may be ok. Disabling FFC will definitely resolve the gaps in the frame feed, but disabling the FFC will also affect the Boson image quality, which may degrade over time. If you wanted to use any USB (thermal) camera with VIO, you would just have to use voxl-uvc-server to publish the images to mpa, so that voxl-qvio-server can subscribe to them. The only issue is that the uvc interface does not provide accurate timestamp of the camera, but it may be ok just to use the time of arrival of the frame. QVIO does estimate the time offset between the IMU and camera, so as long as the timestamp is consistently captured, it should be ok.. Alex

Hi @Richa We have not provided our pinouts for this and have no plans to. For our Micro Coax direct CMOS based sensors, you need to use our products end-to-end to guarantee functionality. Hope this helps clarify.

@Colby-Howell You can save camera data onboard using voxl-logger, but it will take up a lot of storage very quickly and the voxl2 has < 64gb so be careful with that. If you're not trying to save raw frames and are okay with compression & artifacts you can stream it to a ground computer with voxl-streamer and save it there For connecting to the drone the easiest (especially cause you don't have a ground radio) is wifi, you can just connect your drone to a somewhat powerful router, set a static IP and ssh in. For autonomous navigation, the best way in my opinion is to talk to voxl-px4 through the uxrce-dds bridge (implemented on the voxl2 as voxl-microdds-agent) https://docs.px4.io/main/en/middleware/uxrce_dds

@Piyush-Singh , The voxl-portal does not handle well streaming large images (including in multi-view, where the images are actually appearing small). The voxl-portal back-end uses software JPEG encoding, so one of your streams (hires_large) is 4208x3120, which takes LOT of cpu processing to encode to jpeg. You can see that the voxl-portal process uses 260% cpu (2.6 full cores), which is a lot. There is no practical need for streaming small and large uncompressed images to voxl-portal, so you can just enable small video stream, which is much smaller. Also, if you select an individual camera stream, you can enable advanced camera controls (click on the small check box in lower left) and then you can adjust the JPEG encode quality from default 70 to something much lower in order to use less cpu. This setting will be applied to all cameras and you can go back to multi view after that. Note that the jpeg encode quality only affects voxl-portal view, not h264/h265 encoding. Please try. Alex

I'm losing video feed flying just behind a wall not far from me. What can I do to prevent video signal loss? Increase transmit watts or is there a frequency better suited to penetrate thick concrete walls?

@Alex-Kushleyev Could you please share the pinouts of the serial console port. I am not able to find it anywhere.

Hi @Peter-Lingås-0, I have been working on voxl-tflite-server for the last few weeks and was actually testing this. I find that both YOLOV8 and YOLOV11 work well with GPU delegate. The comment you are referring to is removed as of version 0.51 of voxl-tflite-server.