Hi @RykerBarthold That USB-C follows the pinout you can get from the device spec. We list the MPN of the connector here: https://docs.modalai.com/voxl2-mini-connectors/#summary I must caution that you need to plan on failure here. That connector will take a lot of heat to remove and you risk damaging a lot of the surrounding components. We will obviously not be able to offer any RMA or credit for boards that have been through this potential process.

@Abdullah01 There has been some progress but it is taking longer than expected. We are actively working on all of it.

@Chad-Sweet More on this from the manufacturer: MIPI Protocol The product we use is 2lane MIPI. The MIPI interface includes 1 pair of source-synchronized differencing clocks and 2 pairs of differencing data lines clock signals, which enter the high-speed mode at the beginning of each frame and exit the high-speed mode at the end of each frame. The interframe is in low power mode (both data and clock line are at 1.2V high level). MINI2-640, for example, uses a clock frequency of 400MHz. The data line sends the start packet of each frame at the beginning and the end packet of each frame at the end. The number of long packets between the start and end packets of each frame is the same as the height value of the array (such as a 640 * 512 module with 512 long packets), and each long packet data contains row valid data.

@Moderator I'm using a straight out of the box Starling.. with updated software..

there is some activity here that might be interesting

Hi @Moderator, @modaltb Any update on the configuration of tracking camera in HW Sensor ID- 3. Camera Server crashes whenever i connect tracking camera in HW sensor ID-3 (J7U) but in the camera server configuration, SDK 1.0 (C-06, C-14 , C-16, C-17 ) configurations shows that the tracking camera is connected to J7U. Can you please give me update on this?

@Moderator Are there downsides to running Ubuntu 20.04 or 22.04 within docker on VOXL2? Are there features of the VOXL2 that would not be accessible in that scenario?

@AP123 Cool, check out that unbricking guide, that should fix your issue.

@Eric-Katzfey only 420000 work for me for CRSF RAW

@Abdullah01 Hi, did you solve this?

@John-Nomikos-0 I found this info about DSP UARTs being available for use with external flight controllers starting in SDK 1.1. https://docs.modalai.com/voxl2-external-flight-controller/#dsp-uarts-via-apps-proc So I will try upgrading to SDK 1.1, connecting an external flight controller to DSP UART, and then connecting the gimbal to the UART on top of the 5G hat. I wonder if it will work if my external FCU is on Ardupilot and I'm using mavlink_router instead of voxl-mavlink-server

@AP123 You can SSH onto VOXL2 via. ssh root@VOXL2_IP_ADDRESS, password is oelinux123

@Darshit-Desai I have another post about starling drone radio transmitter? Can you answer that for me too? https://forum.modalai.com/post/12312

@Jyotish-Kumar Mythic discontinued this product a while ago. It is not available or supported

Hi @Enrico-Bandera , I've seen this to, and I believe my work around was to sort of remove the working output/or start from a clean git clone. There's some bitbake/poky cache something or other that causes this problem that I'm not clear yet how to fix... holler if you are still stuck.

https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-to-ros/-/blob/master/catkin_ws/src/src/interface_manager.cpp?ref_type=heads#L148 https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-to-ros/-/blob/master/catkin_ws/src/src/interfaces/ai_detection_interface.cpp?ref_type=heads