@Moderator Yep, I got routing through the VOXL2 working. The problem was actually in my host and the device I was pinging. I would have to setup static routing on both devices. But I ended up using a NAT on the VOXL2

Thank you for the help!

@riteshsharma , based on changelog (https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/master/CHANGELOG) you can use voxl-camera-server package version 1.8.10 -- dowload it from here http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/.

Upgrading your SDK would also work as Tom suggested.

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

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

@Moderator Thank you. This clarifies everything.

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

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

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

@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

@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 , 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.

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

@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

@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

Thank you @Eric-Katzfey , it worked, I tested each port individually and made sure the individual ports are working, and then integrated the two and is working fine.

Here is my solution if anyone needs.

I used Telem 1 port of the cube and the UART pins on the J5 connector of USB2 Type A Breakout (M0141) . The parameters I set for MAV 1 is here

214a9a31-6231-4a59-bb93-3048e5fc9c5b-image.png

33012de2-cc53-484e-99de-dc534345f369-image.png

After disabling the voxl-px4 services, Connect to VOXL wifi and check QGC, you'll get the FC data in which the cube is used as the flight controller.

The VOXL ESC, I haven't tested it yet, I'll test and get back if any problems.

Hi @Jonathan-Davis,

Our Starling v2 VOXL 2 board requires this flat build image (M0054-2 Starling QDL Image 1.7.4) which is available in our protected downloads as well as in the unbricking documentation here where you can proceed with the same step-by-step instructions. When finished, the qdl command should complete and the terminal should output "partition 1 is now bootable" indicating a successful QDL flash.

Hope this helps!

@Nathan-Sullivan-0 Great! Thanks for the update

Noting here that flashing the wrong kernel will brick the device (ie flashing the QRB on the QSM) make sure to select the correct option when upgrading the board.