Hi Christopher We currently support two forms of recording, both at the pilot internal to the VRX onboard storage on goggles to the SD Card We do have on our list to implement recording at the UAS itself, but that will need to be in a future software update.

@Alex-Kushleyev Thank you. We will do, but for future reference: @Alex-Kushleyev said in Burnt board components: what type of vehicle was the ESC a part of? Singer Vision FPV 3.5" @Alex-Kushleyev said in Burnt board components: what was the behavior of the motor that was not functioning properly? Not operating a full power with intermittent operation @Alex-Kushleyev said in Burnt board components: did the whole ESC stop working or only one channel, which was originally struggling? Only one channel @Alex-Kushleyev said in Burnt board components: did you notice the burned component when the ESC arrived or did it burn after arrival? We didn't noticed or inspected it. @Alex-Kushleyev said in Burnt board components: was the black paint already on the ESC when you received it? We didn't notice or checked

@Mustafa_Cayci You can get the Starling 2 Max with a ToF sensor for depth mapping indoors (The sensors don't really work outdoors). https://www.modalai.com/products/starling-2-max?variant=49129974923568

@wilkinsaf You can disable compass with SYS_HAS_MAG = 0 and EKF2_MAG_TYPE = 5. But if you enable it and it isn't healthy you won't be able to arm. Power compensation may work, it depends on your particular drone model and use case.

@chinlee5 Which drone do you have? Which versions of software are you using? Are those messages appearing on QGC? Also, do not try to arm the drone or fly the drone while attached to a power supply. Only use a battery for that. If you take the drone outside with a full view to the sky so that GPS can acquire satellites do the messages go away?

With M0195, C34 is the camera configuration that you would need. See https://docs.modalai.com/M0195/#support-camera-configs

@tom Thank you!

@qubotics-admin First you need to determine the version of PX4 running. With ssh or adb you can run the following at the command line: px4-ver all. You will see PX4 version and Vendor version. So, for example, for px4 version 1.14.0 and vendor version 8.134.3 then you would checkout the tag v1.14.0-8.134.3-dev from the repo to see that commit.

@jbhines929 Please fill out the RMA form to get the process started. If it is due to manufactures defect it is covered under warranty and no diagnosis fee will be charged.

@Moderator thank you so much, I will go through that now.

@Cliff-Wong the drone is on SDK 1.5.0, I switched to open vins, and the vio portal reflected the movement, but when i toggled my controller from manual mode to position mode, the drone crashed for the first fight, on the second and third trial the drone kept landing, when i tried the fourth time, the drone finally maintained the height and hovered. Why do I have that unpredictable behavior ? I have attached images of my controller to show the toggling i meant. Kindly advice. Thanks. [image: 1771003494197-whatsapp-image-2026-02-13-at-10.53.46-am.jpeg] [image: 1771003494284-whatsapp-image-2026-02-13-at-10.53.46-am-1.jpeg]

@Moderator said in Blue Zorro specs?: COTS Radiomaster Zorro Oh interesting that its 1w 915mhz! ok that's so cool. But 2k right?

@clange It is technically possible as Stinger is supported by the same VOXL SDK as all of our products. It would likely be a lot of software development to make it happen though

@taiwohazeez , Once thing i noticed is that you don't have en_misp set to 1 for the tracking_front camera. I don't think this is the reason for the failure, but it should be set to 1. Meanwhile, please try to identify which camera is causing the issue by disabling cameras and testing camera server ( you can set enabled flag to 0, so that this camera is not started. Also, when you installed SDK 1.6.2, did you run voxl-configure-cameras and which option did you select for the camera configuration? Alex

@taiwohazeez , It is possible, as the output suggests that the motion blur is causing the issue. You can override the auto exposure algorithm and reduce the exposure down to 5ms or so to help with this. There are two ways of doing this: using voxl-portal : open the regular camera view for your tracking camera, click a small check box in the bottom left corner to enable the advanced control panel. This will allow you to set the exposure and gain, you can try to set the gain to the max (should be 1600 (16x) for AR0144) and then play around with exposure to have the lowest exposure that still makes the checker board clear. After you are done changing the manual exposure, you can run the calibrator and switch the voxl-portal to the calibrator output. please note that until you touch the sliders for exposure and gain, they will not correspond to the current values that are being used by auto-exposure algorithm. from command line you can send a command to camera server: voxl-send-command tracking_front set_exp_gain 5.0 1600 (this would set exposure to 5.0ms and gain to 1600 ISO (16x)) Please note that the manual exposure settings / mode will persist until you reboot the camera server. Alex

@Moderator Thank you for the link. But he says he needs to get on a call with the technical team. It's a year already and I still don't know much about the drones (which may be from my end, I don't know), but he wants to handle this himself this time around and get all necessary information on a single call sometime early in January 2026. Kindly let me know if this is possible, and how to go about it. Thanks

@tom This is the output voxl2:/$ voxl-version ──────────────────────────────────────────────────────────────────────────────── system-image: 1.8.06-M0054-14.1a-perf kernel: #1 SMP PREEMPT Wed Oct 22 04:13:18 UTC 2025 4.19.125 ──────────────────────────────────────────────────────────────────────────────── hw platform: M0054 mach.var: 1.0.1 SKU: MRB-D0014-4-V1-C27-T9-M0-X0 ──────────────────────────────────────────────────────────────────────────────── voxl-suite: 1.6.2 ──────────────────────────────────────────────────────────────────────────────── Packages: Repo: http://voxl-packages.modalai.com/ ./dists/qrb5165/sdk-1.6/binary-arm64/ Last Updated: 2025-12-25 03:58:02 List: libfc-sensor 1.0.8 libmodal-cv 0.6.0 libmodal-exposure 0.1.4 libmodal-flow 1.0.3 libmodal-journal 0.2.7 libmodal-json 0.4.8 libmodal-pipe 2.14.8 libqrb5165-io 0.5.0 libvoxl-cci-direct 0.3.3 libvoxl-codec 0.0.1 libvoxl-cutils 0.1.6 modalai-slpi 1.2.2 mv-voxl 0.1-r0 qrb5165-bind 0.1-r0 qrb5165-dfs-server 0.2.0 qrb5165-imu-server 1.2.3 qrb5165-mini-tof-server 0.2.2 qrb5165-rangefinder-server 0.1.6 qrb5165-slpi-test-sig 01-r0 qrb5165-system-tweaks 0.3.11 qrb5165-tflite 2.17.2 voxl-bind-spektrum 0.1.1 voxl-camera-calibration 0.6.1 voxl-camera-server 2.2.17 voxl-ceres-solver 2:2.0.0-2 voxl-configurator 1.0.10 voxl-cpu-monitor 0.7.4 voxl-docker-support 1.3.1 voxl-elrs 0.4.14 voxl-esc 1.5.7 voxl-feature-tracker 0.5.2 voxl-flow-server 0.3.6 voxl-gphoto2-server 0.0.10 voxl-io-server 0.0.6 voxl-jpeg-turbo 2.1.3-7 voxl-lepton-server 1.3.3 voxl-lepton-tracker 0.0.4 voxl-libgeographic 1.0.0 voxl-libgphoto2 0.0.4 voxl-libuvc 1.0.7 voxl-logger 0.6.0 voxl-mavcam-manager 0.6.0 voxl-mavlink 0.1.6 voxl-mavlink-server 1.4.12 voxl-microdds-agent 3.0.0-0 voxl-modem 1.2.2 voxl-mongoose 7.19.0 voxl-mpa-to-ros 0.3.9 voxl-mpa-to-ros2 0.0.7 voxl-mpa-tools 1.5.5 voxl-open-vins-server 0.5.7 voxl-opencv 4.5.5-3 voxl-osd 0.2.1 voxl-portal 0.8.4 voxl-px4 1.14.0-2.0.124 voxl-px4-params 0.8.11 voxl-qvio-server 1.2.2 voxl-remote-id 0.0.9 voxl-reset-slpi 0.0.1 voxl-ros2-foxy 0.0.1 voxl-state-estimator 0.0.5 voxl-streamer 0.8.0 voxl-suite 1.6.2 voxl-tag-detector 0.0.5 voxl-tflite-server 0.5.0 voxl-utils 1.4.9 voxl-uvc-server 0.1.7 voxl-vision-hub 1.9.19 voxl-vtx 1.7.6 voxl-wavemux 0.0.3 voxl2-io 0.0.3 voxl2-security-hardening-utls 1.0-r0 voxl2-system-image 1.8.06-r0 voxl2-wlan 1.0-r0 ──────────────────────────────────────────────────────────────────────────────── voxl2:/$

@taiwohazeez Can you post a video of it trying to fly?

@Zachary-Lowell-0 Hi, let me explain what i meant by hovering mode. There is a 3-way toggle switch beside the kill switch in the transmitter (toggling down switches to position mode, toggling up switches to the autonomous mode, while toggling to the middle maintains the drone flight positioning. I have another drone that when the button is switched to the middle, it maintains the drone position (thats what i meant by hover mode). My other starling 2 drones maintains their positions when the switch is toggled to the middle position, but this particular starling 2 drone doesnt.