@Vinny I was able to get it in fastboot mode and flash it so things seem to be working now, switching to off and hitting the button solved it. Thanks for all the help!

@cy208183395 Can you test this with SITL? Does it work fine there but not on VOXL 2?

@modaltb I also want to check the stock availability of new TOF sensor over here. Is this TOF camera available for shipping currently? I cant see that on website so wanted to check with you.

@Jetson-Nano You can run the SDK install script with the -f flag to do a factory flash (this will wipe any calibration files you have onboard so pull them off first is necessary) cd voxl2_SDK_1.3.3 ./install.sh -f

@Jetson-Nano Image of the board I'm using, [image: 1723733906698-20240815_200819_hdr_-1-1.jpg]

@Alex-Kushleyev, Cool, Thanks a lot!

@swickliff , I do see SOF received at t=203.337935 and t=203.371313, however there are errors reported right after. It looks like there is actually a issue in data transmission over the high-speed camera interface. Since the same camera unit appears to be working when plugged into a different camera port (per your report), it seems there is some damaged that occurred on the original camera connector or components around the connector. Please inspect the connector and surrounding components again. Alex

@ayrric We currently use a mix of 4 and 5mm spacers (we have used threaded on older model drones, current ones utilize unthreaded). 4mm are used on certain boards that connect to the underside of the Voxl, such as on the Starling 2 and Starling 2 Max. 5mm are used on most B2B connections on the top side of a Voxl. This has been used on Sentinels and all Starling variants for the Wi-Fi or Modem boards. I personally am not overly familiar with the components to answer this with certainty, but can say that we do not use any additional heat sinking on Starling model drones. Drones such as a sentinel with an add-on board will have a small fan pre-installed, but that is standard with the base model and on the other side of the board. We do have a small heat sink included with the ToF assembly on Starling 2 and Starling 2 Maxes. If you are referring to the Starling 2 Image Sensor Adapter, then it can be done in a variety of ways. Our current production process involves connecting the coax to both the image sensors the adapter board before installed to the Voxl 2. In some instances, we do use a bit of foam to secure some of them in place to prevent accidental release. (However, this is primarily a concern with the ToF flex cable, and not the mechanically held in place coax connectors.) We do also use a little bit of ESD safe tape (Kapton) to hold down some of the thin errant coax wires to prevent them from being pinched in the process of connecting the two boards. These coax connectors are fairly robust once installed but only rated for (as far as I am aware) roughly 30 connection cycles. So regardless of how or when you choose to install them, take caution in having to do it repeatedly. As long as you provide careful and even pressure when installing them it should be okay. Hopefully that answered your questions well enough!

@modaltb Thank you for the update

@ksl Not currently as its all internal work. Will throw out an update when we have something to share

@ayrric yes, it is available https://www.modalai.com/products/m0062-2

@Jetson-Nano , thanks for confirming. Yes, that is a sign of incorrect IMU to camera transform (tracking camera extrinsics).

Hi @Nathan-Sullivan-0 I did reach out, but for the benefit of the other forum users, I did a little digging into the modes of the Sony ILX-LR1. I'm wondering if there is a nuance between the camera being enabled as UVC device, but then if you are in still frame mode, sending it (very high resolution) JPEG/RAW/HEIF formats. [image: 1722380710567-d4c38f19-0671-4139-813d-d24f9419fed8-image.png] Maybe someone from SW can confirm, but UVC devices may only expect data in MPEG or other video formats. So, I wonder if the fact that your devices enumerate at first, but then the moment you try to use them in still image mode, things go wrong. This may be a data formatting issue. Another thing to note: can you make sure these images come across USB at controlled ways at different times. You are trying to push a LOT of data into this one port, even those stills are at 15MB minimum. Not sure what frame rate you are using, but you may be saturating the USB link. Have you done a bandwidth analysis? Our MCBL-00022-2 is not qualified for 10Gbps speeds, and for 5Gbps rates, we only qualified it for prototype use. Sustained very high throughput rates may require you to source a proper shielded USB3 to USB-C cable. We try to make that disclaimer clear on our Tech Docs page: [image: 1722381169057-bc9b090d-9bca-4090-b5e4-1a0166dc2298-image.png] And the last point I want to highlight is the USB-C port on the Sony camera may be orientation dependent when not using it in USB-C modes. We are only USB-3 modes on our Hub, and I'm not sure what cable you are using to convert our USB-3 to the USB-C, but we have found that a lot of USB-C to "less-than-USB-C" cables (i.e.: USBC-to-USB3, USBC-to-USB2) actually have orientation specific insertions at the USB-C side if done cheaply. We have some in our own HQ that work like that (I'm trying to find them all and trash them ) Look forward to your email response. Thanks!

@cy208183395 You have to follow all steps. The serial cable must be used.

@Cai-Bill Can you send a flight log of flying in manual mode and then trying to switch into position mode?

@Eric-Katzfey All right. We look forward to the update.

@cy208183395 VOXL doesn't need to be connected to a network in order to upgrade an SDK via the install.sh script, you can follow the steps here: https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release