Hi @Gary-Holmgren. This is likely because you're running the build script from an x86 system (docker requires that you build on the same architecture as the base image, in this case arm64). You can solve that by cloning the repo onto the voxl and running build.sh from there. Note: make sure your voxl has a wifi connection before running ./build.sh.

@Eric-Katzfey Thank you for your quick update. I was able to confirm that it is functioning properly. Really appreciate your support. Wishing you a wonderful New Year!

@tom Thanks!

@Shivam-Sehgal , does it look like the board is rebooting after 10 seconds of running with cameras enabled? also, what if you ssh into the board, does the SSH connection stay alive when the cameras are connecting? Also, how are you powering the drone for this test - battery or power supply? Alex

@Shivam-Sehgal , it seems you are using VOXL SDK that is more than one year old, please upgrade to the latest 1.3.5. If you are not able to upgrade, then please try the following: reduce the width/ height of hires camera large video stream to 3840x2160, if that does not help, reduce the FPS of hires camera to 25Hz disable snapshot if you are not using that feature try starting voxl-camera-server manually and assign upper cores 2-7 to the process, which helps with stability stop camera server running in the background (if applicable) : systemctl stop voxl-camera-server run camera server and assign cpu affinity using taskset : taskset -c 2-7 /usr/bin/voxl-camera-server Alex

@griffin Unless you have your network setup to manually cycle IP addresses every so often then your PC's IP address should stay the same. They're usually logged by mac address

@Jeremy-Frederick Okay, well then you will need to add support for such an external Mavlink enabled peripheral into voxl-mavlink-server. We don't currently support that.

@Alex-Kushleyev Thanks, everything looks alright now that I've removed the other cameras from the config file

@svempati Are you trying to access the mavlink data from VOXL 2 itself or from an offboard computer / ground station?

@Shivam-Sehgal Re-calibrating cameras if the calibration files are lost requires a precise calibration board which many customers don't have, which is why we back them up in our database before shipping the drones. These calibration files (extrinsic and intrinsic) are specific to each drone. gyro, accel, and other sensors can be easily re-calibrated on the bench by the user without any extra peripherals.

@Gary-Holmgren Thanks for the update!

@FIREBIRD VOXL2: https://www.modalai.com/products/voxl-2?variant=39914779836467 https://docs.modalai.com/voxl2-datasheets/ M0130 add-on board (1 USB 3.0 + 2 USB 2.0s): https://www.modalai.com/collections/voxl-2-add-ons/products/m0130-3?variant=48186331693360 https://docs.modalai.com/lte-io-breakout-usb-hub-datasheet/

@Gary-Holmgren Copying over response from another thread: https://forum.modalai.com/post/20119

@mkriesel, For global shutter camera like AR0144, the center of exposure will happen at the time that you suggested: int64_t center_of_exposure_ns = start_of_exposure_ns + exposure_time_ns / 2; For rolling shutter cameras, this is not true because different lines are exposed at different times. In this case, the center of exposure, which means the center of exposure of the middle line ( ) will be: int64_t center_of_exposure_ns = start_of_exposure_ns + (exposure_time_ns + readout_time_ns)/2; This means that you will need to know the readout_time (which is time it takes for the full image to be transferred from the camera). It is not currently exposed in camera server or the camera metadata. Take a look at this resource, it should help understand the rolling shutter case if you need : https://www.1stvision.com/cameras/IDS/IDS-manuals/en/basics-shutter-mode.html , specifically: [image: 1734062749454-shutter_global.png] [image: 1734062647078-shutter_rolling.png] Alex

@soraminds VOXL 2 is a Linux computer so you can just run Apache or any other standard web server. But be aware that voxl-portal is also a running web server so you would have to stop it or, even better, run your server on a different port.

We have added support of the following barometers to voxl-dev branch of px4-firmware repo and you should be able to pick up the change tomorrow in the latest nightly build: bmp280 bmp388 ms5611 http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/ (look for voxl-px4 and check build date). the new barometers can be enabled connected to J19 (px4 i2c port 1, so -b 1) and modifying voxl-px4-start script: qshell bmp280 start -X -b 1 qshell bmp388 start -X -b 1 qshell ms5611 start -X -b 1 You should disable the onboard barometer icp101xx, otherwise there may be a conflict where two barometers are publishing under the same instance (at least when viewed with px4-listener). We will investigate this issue. Alex

@Viktor-Gal If you've already removed the board then sending in just the board as an RMA is fine

@tom thank you. I've been looking through the code. I'd like to test masking areas of non-interest in my tracking cameras. From the voxl-open-vins-server.conf file and from common.h image_data struct it seems like this feature exists, but I cannot find where I can put the masks, or define where they are. Do you know if this is implemented already? Maybe I'm looking in the wrong place?