@Eric-Katzfey Sure, Thank you!

@groupo Exactly

@Aaky voxl-tflite-server is a wrapper for TensorFlow Lite. So, anything you can get to work in standard TensorFlow Lite you should be able to get working in voxl-tflite-server https://ai.google.dev/edge/litert

@restore you'll need to use PX4 logs for that

@Inhan-Kang Did you ever resolve this issue? We may have a similar one. Ruled out power issues already by running straight off a powerful 5V supply. It does not reboot though, just goes dark and stops responding over ADB or over the network (we are using Doodle).

@Aaky great to hear, from my experience when the board is booting directly to fastboot it is often a power issue

@Morten-Nissov , About the IMU dt, sorry, i got it backwards, the dt is 0.976ms, so that would be slightly above 1khz. So we are on the same page. Yes, reducing the FIFO size results in more SPI read transactions, which means that the CPU / Kernel has to do more work. There is a per transaction overhead that is much more significant than just getting more data per single transaction. Let's not bother with the PR because it is a 2-character change . I will get to it and test it soon. Alex

About 95C is when the temperature control loop will kick in and start reducing the maximum core frequencies (gradually). You can monitor the cpu usage and current core frequencies using voxl-inspect-cpu. Here are the maximum core frequencies for all cores: cpu0 1804.8 cpu1 1804.8 cpu2 1804.8 cpu3 1804.8 cpu4 2419.2 cpu5 2419.2 cpu6 2419.2 cpu7 2841.6 If you set the cpu governor mode to perf (voxl-set-cpu-mode perf), it will pin all the cores to max frequency and they will stay there unless they are being throttled due to temperature, which you can check using voxl-inspect-cpu.

@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?

@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