Same here, mine died after about 40hrs of operation. I suspect is thermal damage

Yes, the beta release is fine. It was beta only for some features that are not used on our development drones. Otherwise it was a stable release.

@Omri-Eival The Zorro Blue User Manual should answer most of your questions, with a shell script to copy all of the latest data to a handset in the provided zip file. While you are there, if your firmware is out of date it may be worth going through the update process.

@Jetson-Nano Given the crash and hardware issues I'd recommend sending this board in for an RMA

@ModalAI-Team Help me out here . I want to purchase some new components, but with out having a clear idea on the architecture I won't be able to do it. Please guide me here.

Hello, I would like to follow up on this topic. We are currently evaluating the feasibility of using Starling 2 for indoor autonomous flight applications in Japan. Understanding the recommended Wi-Fi configuration for operation in Japan will help us continue our evaluation. If anyone from the ModalAI team could provide guidance, we would greatly appreciate it. Thank you very much.

MCBL-00084-180 (26-pin Micro-Coax Cable): Operating temperature 0°C to +70°C; Storage temperature 0°C to +70°C. MSU-M0161 (EO Camera): Operating temperature 0°C to +70°C; Storage temperature 0°C to +70°C. (The Sony IMX412 image sensor guarantees image performance from −10°C to +60°C.) VOXL 2 / MDK-M0154-1-00 (Flight Computer): Operating temperature 0°C to +70°C; Storage temperature 0°C to +70°C. MDK-M0155-1-00 (Image Sensor Micro-Coax Adapter): Operating temperature 0°C to +70°C; Storage temperature 0°C to +70°C. MDK-M0062-3-00 (VOXL2 Ethernet & USB Hub Adapter): Operating temperature 0°C to +70°C; Storage temperature 0°C to +70°C.

Hello @jameskuesel , Sorry for the confusion about the lens change. Please see the details below. The original lens in the IMX412 modules (M0107 and M0161) had manufacturing issues where the internal components of the lenses were loose and vibrating in flight, causing shaky video. Due to quality / vibration issues of the original lens (part number M10000580) shipping with IMX412 (M0107 and M0161) modules, the default lens was changed to M10001028 (late 2025). However the new lens does have much narrower FOV. When purchasing the standalone camera, you have a choice of lens: M0161 with old lens (wide) : MDK-M0161-1-07 (3.1mm EFFL, M10000580 lens) M0161 with new lens (narrow) : MDK-M0161-1-08 (3.24 EFFL, M10001028 lens) It seems that there maybe some discrepancy in the manufacturer stated EFFL for the new lens (3.24 vs original 3.1) because the actual FOV change is more significant than the change in the effective focal length would result in. We are looking into this. Starling 2 and Starling 2 Max drones are currently shipping with the new lens (narrow FOV). We do currently have stock of the old (wide) lenses that should have no issues (according to the manufacturer), however we cannot provide any guarantees for this lens due to past history of issues. If you would like to update your drone / camera with the original wide lens, please contact us and we will make it available for you to purchase (lens part number M10000580). Alex

Yes, use the normal RC port. But cannot use an SBUS receiver with that port.

Great to hear @mikhail-mayers . I tested the module you sent back and it baffles me... must be some internal silicon damage to the IC since it had all in-spec inputs, and no faults on any outputs, but it was just not turning on... so, it is now one of my Mechanical Samples Glad we could get that resolved for you and thanks for your patience.

Hello @Alex-Kushleyev , This is exactly what we needed ... thank you for turning the combined flip + GNSS-fix driver around so fast! Confirming our plan against your docs: We're on the encoded (ISP) path ... large_encoded for the pilot's low-latency FPV feed, not MISP ... so the ISP should pull the reversed bayer from the flip sensormodule and debayer correctly (no R/B swap). We'll run the version-agnostic combo: the flip sensormodule + en_rotate = true, plus maxRAWSizes=20 in camxoverridesettings.txt. Bit rate: going with 2088 Mbps. Our GNSS is a Septentrio mosaic dual-antenna running moving-baseline heading, so GPS L1 integrity is critical for us ... your analysis showing 2088 sitting ~10 MHz off L1 center with only a 1–2 dB drop is exactly the margin we need. We'll keep our FPV mode clear of the three forced-2200 modes (staying 1080p ≤120 fps). We'll validate by logging the Septentrio C/N0 and satellite count with the camera streaming vs. off, in representative daylight (noting your point that under-exposed frames worsen the interference). One quick check: for our single hires IMX412 on the M0173, is the default i2c 0x34 the right choice, or is there a scenario where we'd want the 0x20 variant? I'll report back the before/after GNSS numbers once we've tested ... happy to share the data if it's useful. Thanks again, John

the hexagon sdk has been unlocked. It is under the miscellaneous folder: https://modalai.filecloudonline.com

Yes, your understanding is correct. To see the PX4 IMU values use standard PX4 commands. For example, on voxl2 you can use the PX4 listener commands: voxl2:/$ px4-listener sensor_accel TOPIC: sensor_accel sensor_accel timestamp: 30123125 (0.006725 seconds ago) timestamp_sample: 30122829 (296 us before timestamp) device_id: 2490378 (Type: 0x26, SPI:1 (0x00)) x: -0.05360 y: 0.01754 z: -9.68999 temperature: 34.62560 error_count: 0 clip_counter: [0, 0, 0] samples: 20 voxl2:/$ px4-listener sensor_gyro TOPIC: sensor_gyro sensor_gyro timestamp: 37716660 (0.003955 seconds ago) timestamp_sample: 37716405 (255 us before timestamp) device_id: 2490378 (Type: 0x26, SPI:1 (0x00)) x: -0.00409 y: 0.00796 z: -0.01429 temperature: 34.32669 error_count: 0 clip_counter: [0, 0, 0] samples: 20

Yes, thank you Vinny.