Hardware: Device: Starling 2 Max (MRB-D0012) Hardware platform: M0054 Machine variant: 1.2.1 SKU: MRB-D0012-4-V3-C28-T8-M36-X0 Software: System image: 1.8.06-M0054-14.1a-perf Kernel: #1 SMP PREEMPT Wed Oct 22 04:29:38 UTC 2025 4.19.125 VOXL Suite: 1.6.4~alpha2 I am new to drones, the ModalAI interface, and PX4. I encountered several issues while working through the VOXL Developer Bootcamp and would appreciate guidance on the following questions. Questions: In the ModalAI VOXL Portal, I repeatedly receive one of the following errors: "Preflight Fail: High Accelerometer Bias" or "Preflight Fail: Yaw Estimate Error". To address these errors, I have restarted the drone while it was stationary and level on a table, and also recalibrated the gyroscope, accelerometer, level horizon, and magnetometer. However, the errors continue to appear. What additional troubleshooting steps should I follow to resolve these preflight failures? While the drone is powered on and idle on a table, the reported CPU temperature rises to approximately 104°C. Pointing a desk fan at the drone reduces the temperature to approximately 80°C. Is this temperature expected during normal development? If not, what are the recommended practices for keeping the system cool while writing, compiling, or testing code? The log is shown below: Name MHz Temp Util Jul 20 2026 20:46:05 cpu0 979 104.7 99.0 Uptime: 0:15:36 cpu1 979 103.5 90.0 cpu2 979 102.4 91.4 Mem Use (MB) cpu3 979 104.3 89.5 6244.8/7671 cpu4 710 103.9 100.0 Mem Allocation cpu5 710 104.7 99.0 6.4 MB/s cpu6 710 103.5 100.0 cpu7 844 104.7 100.0 Governor: Cool Total 104.0 96.1 Pitmode: Active 10s avg 91.4 Auto Pitmode: ON ------------------------- CPU OVERLOAD WARN GPU 305 98.1 15.0 CPU OVERHEAT CRIT GPU 10s avg 18.6 MEM LEAK WARNING PID Top CPU Consumers CPU% Core Pri 1429 voxl-camera-server 184.3 4 80 2867 voxl-qvio-server 96.2 6 80 1931 px4 89.7 3 0 2219 voxl-mavlink-server 12.3 3 0 1266 voxl-cpu-monitor 5.3 3 0 1425 voxl-vision-hub 5.0 3 0 1714 voxl-imu-server 5.0 3 80 2889 voxl-portal 4.3 6 0 527 systemd-journald 3.4 7 0 1364 voxl-rangefinder-server 1.9 2 0 ----------------------------------------------- PID Top Memory Consumers Mem (MB) uptime 1931 px4 167.8 15:29 1429 voxl-camera-server 137.2 15:31 2867 voxl-qvio-server 12.9 14:22 2889 voxl-portal 10.4 14:04 2219 voxl-mavlink-server 7.6 15:27 2274 voxl-streamer 6.6 15:26 1364 voxl-rangefinder-server 5.9 15:31 1714 voxl-imu-server 5.7 15:30 1277 sensors.qti 5.3 15:31 1425 voxl-vision-hub 4.6 15:31 ----------------------------------------------- A red light on the top portion of the drone flashes continuously. I initially thought this indicated that the drone was not connected to the controller. However, the light continues flashing even after the Commando 8 controller is connected and the drone can be controlled successfully. What does this flashing red light indicate, and what steps should I take to diagnose or resolve it? A picture is attached below: [image: 1784659843277-7748e0e7-20c0-4d1a-b2f7-6f0d2fa0aca4-image.jpeg]

Hi, I have a voxl 2 starling drone and I am running the camera stream using hireses_front_small_encoded inside adb shell via voxl-camera-server -d 0. Its crashing after 5-7 minutes, not sure what it is wanted to send here for inquiry purposes. Hardware Here is the hardware specs: ──────────────────────────────────────────────────────────────────────────────── 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-D0012-4-V2-C28-T8-M0-X0 ──────────────────────────────────────────────────────────────────────────────── voxl-suite: 1.6.3 ──────────────────────────────────────────────────────────────────────────────── current IP: 192.168.30.103 (wlan0) ──────────────────────────────────────────────────────────────────────────────── Logs Here is the error breakdown: VERBOSE: finished sending request for frame 17621 for camera tracking_front VERBOSE: returning from SendOneCaptureRequest for frame 17622 for camera tracking_front VERBOSE: setting hal3 exposure for tracking_front 6175533 461 VERBOSE: Received result from HAl3 for frame number 17564 VERBOSE: added request for preview stream VERBOSE: Sending request for frame 17622 for camera tracking_front for 1 streams ERROR: Received Fatal error from camera: tracking_front ERROR: Sending request 17622, ErrorCode: -ENODEV ERROR: Received "Result" error from camera: tracking_front, frame number 17607 VERBOSE: Received result from HAl3 for frame number 17607 VERBOSE: Received 1 buffers from camera tracking_front, partial result:0 VERBOSE: Received output buffer 17607 from camera tracking_front WARNING: Thread: tracking_front result thread Received ESTOP VERBOSE: Buffer arrive before meta frame 17607 VERBOSE: Received result from HAl3 for frame number 17608 VERBOSE: Received 1 buffers from camera tracking_front, partial result:0 VERBOSE: Received output buffer 17608 from camera tracking_front VERBOSE: Buffer arrive before meta frame 17608 VERBOSE: VERBOSE: Exposure: 26132338 VERBOSE: Readout Time: 22874342 VERBOSE: Received result from HAl3 for frame number 16321 VERBOSE: Received 0 buffers from camera hires_down, partial result:2 VERBOSE: Received metadata for frame 16321 from camera hires_down VERBOSE: Timestamp: 1013675034124 VERBOSE: Gain: 1004 VERBOSE: Exposure: 33233328 VERBOSE: Readout Time: 22874342 VERBOSE: Received result from HAl3 for frame number 17564 VERBOSE: Received 0 buffers from camera tracking_down, partial result:2 VERBOSE: Received metadata for frame 17564 from camera tracking_down VERBOSE: Timestamp: 1013725406646 VERBOSE: Gain: 637 VERBOSE: Exposure: 6971563 VERBOSE: Readout Time: 16122531 VERBOSE: Received result from HAl3 for frame number 16353 VERBOSE: Received 1 buffers from camera hires_front, partial result:0 VERBOSE: Received output buffer 16353 from camera hires_front VERBOSE: Received result from HAl3 for frame number 16321 VERBOSE: Received 1 buffers from camera hires_down, partial result:0 VERBOSE: Received output buffer 16321 from camera hires_down VERBOSE: Received result from HAl3 for frame number 17564 VERBOSE: Received 1 buffers from camera tracking_down, partial result:0 VERBOSE: Received output buffer 17564 from camera tracking_down VERBOSE: Received result from HAl3 for frame number 16354 VERBOSE: Received 0 buffers from camera hires_front, partial result:2 VERBOSE: Received metadata for frame 16354 from camera hires_front VERBOSE: Timestamp: 1013707432602 VERBOSE: Gain: 497 VERBOSE: Exposure: 22541986 VERBOSE: Readout Time: 22874342 VERBOSE: Received result from HAl3 for frame number 16322 VERBOSE: Received 0 buffers from camera hires_down, partial result:2 VERBOSE: Received metadata for frame 16322 from camera hires_down VERBOSE: Timestamp: 1013703705218 VERBOSE: Gain: 1004 VERBOSE: Exposure: 33233328 VERBOSE: Readout Time: 22874342 VERBOSE: Received result from HAl3 for frame number 17565 VERBOSE: Received 0 buffers from camera tracking_down, partial result:2 VERBOSE: Received metadata for frame 17565 from camera tracking_down VERBOSE: Timestamp: 1013758701129 VERBOSE: Gain: 635 VERBOSE: Exposure: 6960569 VERBOSE: Readout Time: 16122531 VERBOSE: Received result from HAl3 for frame number 16354 VERBOSE: Received 1 buffers from camera hires_front, partial result:0 VERBOSE: Received output buffer 16354 from camera hires_front VERBOSE: Received result from HAl3 for frame number 17565 VERBOSE: Received 1 buffers from camera tracking_down, partial result:0 VERBOSE: Received output buffer 17565 from camera tracking_down VERBOSE: Received result from HAl3 for frame number 16322 VERBOSE: Received 1 buffers from camera hires_down, partial result:0 VERBOSE: Received output buffer 16322 from camera hires_down VERBOSE: Received result from HAl3 for frame number 16323 VERBOSE: Received 0 buffers from camera hires_down, partial result:2 VERBOSE: Received metadata for frame 16323 from camera hires_down VERBOSE: Timestamp: 1013737159124 VERBOSE: Gain: 1004 VERBOSE: Exposure: 33233328 VERBOSE: Readout Time: 22874342 VERBOSE: Received result from HAl3 for frame number 16323 VERBOSE: Received 1 buffers from camera hires_down, partial result:0 VERBOSE: Received output buffer 16323 from camera hires_down ------ voxl-camera-server: Camera server is now stopping DEBUG: Stopping Camera: tracking_front DEBUG: ------ Last frame encoded: -1 DEBUG: OMX_EventCmdComplete DEBUG: OMX_EventCmdComplete DEBUG: Encoder moved to Idle State DEBUG: Deleting buffers for tracking_front preview stream DEBUG: OMX_EventCmdComplete DEBUG: Deleting buffers for tracking_front small video stream DEBUG: Deleting buffers for tracking_front large video stream DEBUG: Deleting buffers for tracking_front snapshot stream DEBUG: Deleting buffers for tracking_front misp stream DEBUG: Done closing device for camera tracking_front DEBUG: Done calling stop for camera tracking_front Stats For Camera tracking_front: Received Frame Count: 17622 Request Error Count: 55 Buffer Error Count: 31 Result Error Count: 32 DEBUG: Deleting Camera: tracking_front DEBUG: Stopped Camera: tracking_front DEBUG: Stopping Camera: hires_front DEBUG: ------ Last frame encoded: 16348 DEBUG: OMX_EventCmdComplete DEBUG: OMX_EventCmdComplete Segmentation fault: Fault thread: VideoEncCallBac(tid: 10824) Segmentation fault voxl2:/data/px4/log$ voxl2:/data/px4/log$ ERBOSE: finished sending request for frame 17621 for camera tracking_front bash: ERBOSE:: command not found front:/data/px4/log$ VERBOSE: returning from SendOneCaptureRequest for frame 17622 for camera tracking_f bash: VERBOSE:: command not found voxl2:/data/px4/log$ VERBOSE: setting hal3 exposure

Sorry for being very specific.. but there are two types of telemetry you can get from DSHOT-capable ESCs. UART telemetry : the four ESCs send telemetry one at a time over a dedicated UART line, which can be fed into standard UART RX DSHOT telemetry is sent from each ESC over the PWM lines (all at the same time) and do not use UART. The FC hardware as to change the PWM outputs to inputs while receiving telemetry (requires tight timing) So, do you have a requirement to use one or another.. or which specific fields in the telemetry are you looking for? Alex

And the latest build of our fork with this fix is here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-px4_1.14.0-2.0.146-202607161052_arm64.deb

Hey @alex-kushleyev, good to know it holds up like that under load, and thanks again for the reply. Two things I'm trying to pin down on the Mini: Power. Can a USB port on the VOXL Mini actually supply around 2-2.5 W, and can it do that on one port while a small USB camera runs on the other? Or should I plan to power those externally? Extra camera slot. From the D0013-V2 CAD the imager board looks like 5 DF56 coax connectors with 4 used (EO + dual AR0144 + Boson+), and the Lepton is on the M0187 SPI adapter so it's off the CSI bus. Is that spare coax connector wired to a usable CSI lane, and would voxl-camera-server take a 5th sensor (an M0161) there without a custom config? Thanks, Eyal