Hi John, Thank you for the information it was very helpful for analysis. It seems as though the firmware crash happens on stream timeouts and causes the firmware to crash. Here is a potential workaround with the installer, I kept all the claude output in case that helps with any analysis on your end: https://drive.google.com/drive/folders/1sbwS3RZ4wgmC2raH7SnDKZz3OYSOavSg?usp=sharing If you could try running that and using the device normally, hopefully that stops it from crashing. We also do have routing on that expansion board for the RESET pin but for some reason the firmware does not respect it. If you keep seeing the issue that might be the next place to look, but NXP has marked this chip as EOL and won't support any fixes there, so our best hope is to workaround whatever is happening. Let us know how that goes and any other findings. Thanks! Luke

Hello. Can a Starling 2 drone autonomously fly while flying over the pipe inside a sewer? The drone must fly autonomously in a dark place to inspect cracks or internal conditions while flying along the water pipe. I'm not sure if this feature can run on Starling, so I'm asking for help!

Hello again, This is the voxl-configure-mpa I've got after running voxl-configure-sku... voxl2:/$ voxl-configure-mpa ------------------------------------------------------------------ Welcome to voxl-configure-mpa! VOXL is currently thinks it is in the following hardware: family code: MRB-D0006 (sentinel) compute board: 4 (voxl2) hw version: 2 cam config: 11 modem config: 7 (VOXL 2 5G Quectel (M0067/M0090-3-01)) tx config: 9 (ghost) extras config: 0 (none) SKU: MRB-D0006-4-V2-C11-T9-M7-X0 If this doesn't look right, quit and run voxl-configure-sku to set it correctly. Then run voxl-configure-mpa again. Continue? y/n: n Ok, exiting This seems to apply correctly, but QGroundControl still shows no control stick responses. px4-shell ghst_rc status doesn't seem to indicate that the process is running, and I've rebooted the Sentinel after using the voxl-configure-mpa command.. voxl2:/$ px4-qshell ghst_rc status INFO [qshell] Send cmd: 'ghst_rc status' INFO [qshell] qshell return value timestamp: 395926563, local time: 395930281 voxl2:/$ px4-qshell ghst_rc status INFO [qshell] Send cmd: 'ghst_rc status' INFO [qshell] qshell return value timestamp: 398284392, local time: 398286173 voxl2:/$ px4-qshell ghst_rc status INFO [qshell] Send cmd: 'ghst_rc status' INFO [qshell] qshell return value timestamp: 399164515, local time: 399166110 voxl2:/$ px4-qshell ghst_rc status INFO [qshell] Send cmd: 'ghst_rc status' INFO [qshell] qshell return value timestamp: 399840897, local time: 399844011 voxl2:/$ px4-qshell ghst_rc status INFO [qshell] Send cmd: 'ghst_rc status' INFO [qshell] qshell return value timestamp: 412583664, local time: 412586186 voxl2:/$ px4-qshell ghst_rc status INFO [qshell] Send cmd: 'ghst_rc status' INFO [qshell] qshell return value timestamp: 418824570, local time: 418825970 voxl2:/$ px4-qshell ghst_rc status INFO [qshell] Send cmd: 'ghst_rc status' INFO [qshell] qshell return value timestamp: 422361921, local time: 422364518

Hey @arvind_g3aero So, it does look like you were able to get this working with the dev release of voxl-camera-server which is great to hear. The natural progression of a software package is through dev-> staging -> release. So, this version of voxl-camera-server will be released in a future SDK. There will most likely not be a backport onto the 1.6.2 SDK

Hi ModalAI team, We are planning a 7-port USB 2.0 hub for VOXL 2, connected through J3, using the Microchip USB2517. We wanted to use this to connect more sensors and USB cameras to the VOXL 2 board. I’m following the USB expansion guidance in the VOXL 2 Expansion Design Guide and wanted to ask: Do you have a reference schematic for a USB 2.0 hub connected to J3 that you could share? The guide mentions that ModalAI may review customer expansion-board designs. Once I have my schematic ready, would you be willing to review it before I proceed to PCB layout? Thank you in advance!