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

@restore, it looks like PX4 does have a driver for this imu/compass.

https://github.com/modalai/px4-firmware/blob/voxl-dev/src/drivers/imu/invensense/icm20948/ICM20948.cpp

However, it is not clear whether you can read just compass data. Please take a look at this driver.

If you want to use it, you will need to enable building of the driver in the voxl2 board config: https://github.com/modalai/px4-firmware/blob/voxl-dev/boards/modalai/voxl2-slpi/default.px4board : enable DRIVERS_IMU_INVENSENSE_ICM20948=y .

Then, modify /usr/bin/voxl-px4-start to include:

qshell icm20948 start

We have not tested this driver, so we cannot really provide any guidance on using it for your application. However, with the above instructions, you should be able to compile it and run it.

Please make sure that the IMU data from this module does not conflict with the main flight IMU.

Alex

@Moderator Please tell me that without modifications Just Like Vijay Kumar has developed the SWARM of MESH with your Drones, I want to buy VOXL 2 Starling Drones in order to develop the Mesh Networking with 2 drones? How I can do it easily? Is it feasible ? or We can develop that with XBEE 3 ? Please help me in this regard ? If I need to change the driver setting How I can do that in order to implement the SWARM of the drones MESH Networking ?

@Eric-Katzfey
Understood. Thanks
My line of questioning in another topic I posted - " Attempt to reduce drift with the help of stereo camera " is similar. So, I'll close this and take your advice from that.

Thanks again

@Eric-Katzfey
Understood. Thank you.

@tom the full wipe SDK install sorted it out. Thanks

@riteshsharma do the SDK installation with ./install.sh -w option. This will wipe the entire file system including the /data partition which is usually untouched.

@Aaky, I see what you are asking.

What is needed is the python binding to the C function int pipe_server_get_num_clients(int ch) , which is defined here

pympa_create_pub already is set up to return the MPA channel number, so we would just need to use that channel number of checking the number of clients.

I can implement this, but it will need to wait a few days. That is a good feature to have. If you would like to try implementing it yourself, you can add the bindings to :

https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-tools/-/blob/pympa-experimental/tools/pympa.cpp (add call to pipe_server_get_num_clients) in a similar way how other functions are called. add the actual python wrapper to: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-tools/-/blob/pympa-experimental/tools/python/pympa.py then finally, when you call pympa_create_pub, save the pipe id and then pass it to check for clients.

Alex

@Chad-Sweet, @James-Strawson, @tom any updates?