@NikosMav There are two IMUs on a VOXL2. One is accessible from the applications processor and is used by VIO and voxl-calibrate-imu. The other is accessible by the SLPI DSP and that is where PX4 runs. Are you using a ModalAI drone or a custom drone? What SDK release are you on? Which parameters are you talking about, PX4 parameters? If you adb into the drone and issue px4-listener sensor_accel or px4-listener sensor_gyro do you see values?

@voxltester As I tried to explain before, don't wait for voxl-mavlink-server to connect to your application. You need to have it initiate the connection to voxl-mavlink-server.

@voxltester You cannot use a port number that is already in use by another application. So pick a different one.

Hi @isagmz
That is indeed a cap. It is a 4.7uF 25V 0603 in support of the 5V input rail when sourced by J5.

We have so much margin on the 5V power rail, I would not worry about one cap missing. My best advice is to clean up that area to make sure there is no FOD or ripped up pads that can cause a short on that 5V rail from the broken cap, and just keep developing.
Let us know if you have any other issues.
Thanks!

@RoyAzriel I would just grab the most recent one.

@RoyAzriel Instructions are here: https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release

@RoyAzriel Can you just try a fresh SDK install and see if that helps?

@RoyAzriel I'm guessing that there is a version mismatch somewhere. Can you install a recent SDK from scratch and see if everything comes up fine? And when you say "dev crone" do you mean that this is a custom drone and not one of our products?

@RoyAzriel Does it come up fine after a power cycle?

@daniellee This log shows a normal flight happening in altitude hold mode. RC inputs are coming in and motors are spinning. Was there some issue with the flight this log was captured from?