Topics created by restore

Thanks @Eric-Katzfey ! Here is the pinout for the dev board "UART" port that includes i2C_SCL and I2C_SDA.

0cda71eb-2c0f-4b1b-ba91-8b3862fc9763-image.png

The dev board pins 1-6 matching to J19 pins 1-6

We will give the COMPASS_DISBLMSK parameter a shot and see if that works.

@Alex-Kushleyev Thanks for the follow up and working towards the calibration map. For us the real time processing speed doesn't matter too much, but the image file size does as we need to send the unprocessed images over radio in real time. We were hoping to use voxl-record-raw -j -q 90 as this doesn't show the vertical artifact and results in reasonable file sizes.

@restore There are a few examples of code that listens for Mavlink messages in our SDK. For example, in voxl-mpa-tools, take a look at the source code for voxl-inspect-mavlink.c. https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-tools/-/blob/master/tools/voxl-inspect-mavlink.c?ref_type=heads

Probably would be a good idea to run voxl-inspect-mavlink on the mavlink_onboard and mavlink_to_gcs pipes to see which one has the desired Mavlink message in it. Then create your own application that listens for the Mavlink message on that pipe.

@Alex-Kushleyev thank you! It works now.

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

@Alex-Kushleyev yes you can reference the log

@restore , i don't think this module will work with VOXL2_IO because it seems the Seagull MAP2 interface expects direct connection to the I/O pins, which is not the case when using VOXL2_IO module.

Alex

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

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

@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

@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

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

@Alex-Kushleyev
Thanks for the help, as I was calibrating the ESCs I did notice those messages, which confused me as to why we weren't able to get that information in PX4. On Monday it suddenly just started working despite my changing nothing. Gotta love when things fix themselves

@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

Thank you - I was able to make it work for one camera with the following changes.

etc/modalai/voxl-camera-server.conf

changed "camera_id_second": to -1 to get just one camera, changed "en_preview": to false, Added:"en_small_video": true, "small_video_width": 1280, "small_video_height": 800, restart voxl-camera-server service

etc/modalai/voxl-streamer.conf

"input-pipe": "stereo_small_encoded"

etc/modalai/voxl-mavcam-manager.conf

"video_record_pipe_name": "stereo_small_encoded",

@Alex-Kushleyev Yes thank you, we will be going through all of the calibrations as our application is completely custom.