@restore I would recommend taking a look at the source here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-gphoto2-server It is built using the headers from voxl-libgphoto2: https://gitlab.com/voxl-public/voxl-sdk/third-party/voxl-libgphoto2

@Amin-Bassiri Can you open a new thread describing your issue? It'll make it so the rest of the team gets eyes on it

@Eric-Katzfey ok, thank you

@Jeremy-Frederick I'm guessing that the black 4 wire cable between the VOXL 2 and the APM may have some issues making an occasional problem for the i2c bus. Do you have another one of those cables to swap with?

@restore , thanks. One more thing, when you entrer the pwm_vs_rpm_curve_a1 and a2 params, you currently have only one significant digit, which may explain why your rpm response was not working well. You should enter at least 3-4 significant digits, so instead of a2=0.003, you should put 0.003xyz where xyz are the additional digits from the original calibration results.

@Taylor-Presley Hey Taylor, happy to try and help! On calibrating we try to keep the reprojection error as low as possible. You're getting an error of 1.42 which is almost triple what we'd like at worst. I'd recommend trying to recalibrate in different lighting conditions with as flat of a checkerboard as you can make. Even small imperfections here can lead to bad calibration. Hope this helps! Thomas

@restore After reading older posts, changing the Voxl start script to add the ist8308 magnetometer to the build instead of the ist8310 solved the issue. I can now see the compass through PX4-listener

@LucaVertiq , Here is the latest VOXL2 mini nightly SDK : https://storage.cloud.google.com/platform-nightlies/voxl2-mini/voxl2-mini_SDK_nightly_20240415.tar.gz I just tested by using SDK 1.1.1 as a base and booting using the kernel from the nightly: adb reboot bootloader fastboot boot qti-ubuntu-robotics-image-m0104-1-boot.img IMX214 works on all 4 ports. I think you have an option of using this approach or just installing the full nightly. I am not 100% that the latest kernel is fully compatible with everything in SDK 1.1.1, so that is a bit of a risk, so using nightly is a back up option if you wanted to try the SDK 1.1.1 and something did not work as expected with the latest kernel. If you install the full nightly, use M0054-1 board variant for the voxl2 mini. Also here are links for the imx214 sensormodule for slot 1 (regular and flip): https://storage.googleapis.com/modalai_public/temp/voxl2-misc-packages/com.qti.sensormodule.imx214_1.bin https://storage.googleapis.com/modalai_public/temp/voxl2-misc-packages/com.qti.sensormodule.imx214_flip_1.bin

@Eric-Katzfey We were able to resolve the issue. We went to /etc/modalai/voxl-px4.conf and changed the RC params to Spektrum.

@Eric-Katzfey Thanks Eric. I will try this out and let you know soon.

@Vinny yes thanks so much! I'll look into it.

@tom Ok, thank you for you help & time in troubleshooting this issue

@Aaky The Microhard board does not expose an apps processor UART but you could use a USB to UART adapter to connect to the Gimbal via one of the USB ports.

@Moderator Thank you. This clarifies everything.

@AndriiHlyvko , thank you for following up with your solution!

@Aaky Unfortunately, we have not done any integration between PX4 and SPI devices on the apps processor. I would get an oscilloscope and see what is happening on the bus.

@Eric-Katzfey This sounds like perfect plan. I would implement this and get back for any queries. Thank you Eric!