Hi @Jose-Alfredo-Rosas-Cordova Yes, absolutely. That is one of the use-cases to have this along with GPS/Mag/RC. These cables are all related to those functions and can help you make whatever custom adapter you may need: https://docs.modalai.com/cable-datasheets/#mcbl-00061 https://docs.modalai.com/cable-datasheets/#mcbl-00064 https://docs.modalai.com/cable-datasheets/#mcbl-00070 Note, MCBL-00070 is brand new so we'll have the purchase link up soon. This guide also tells you some tips on how to modify these cables to your needs: https://docs.modalai.com/cable-userguides/ So, if we do not have exactly what you need, you can easily modify some others to get you there. Hope this helps! Thanks

Hi @aharvey , please see an email coming your way, thanks!

Thanks for the feedback! Document updated here: https://docs.modalai.com/calibrate-cameras/#stereo-calibration-video-tutorial

I apologize for the delay in responding. It seems like your suggestion seems to do what we want. Unfortunately it seems that I am unable to shut down the network interface on eth0. I get an error when I try to set the MAC address that the resource is busy. Are there any subroutines or other services that would keep the interface from being shut down?

No, it is not the latest. It's a few months of work on our end to update the SDK. We may try it later this year, but no formal plans to do so

@José-Quintanilla https://www.baeldung.com/ops/docker-mount-single-file-in-volume

Yes it is much easier to record in HD without taking a hit to framerate. You can use voxl-streamer to throttle the dimensions higher however, I wouldn't advise this for right now

@IChen, at the moment, we don't have prop guards. There does seem to be products available on the market that would work with the S500 frame. You could 3D print some if the ones out in the market are not up to your spec. I noticed you're looking for an indoor specific drone. Have you looked at the Seeker? That platform is more suitable specifically for indoors. FYI, we are developing a smaller drone platform called the Starling, smaller than the Seeker and designed for indoor navigation and development. Hope that helps

@ido-abergel I would start here: https://docs.modalai.com/voxl-tflite-server/#deep-learning-with-voxl-tflite-server

Yes, all of our "hi-res" image sensor modules support 4k and above

Yes, it should work, just try it.

This doesn't align with anything we have seen. Any chance there is vibration being introduced?

Thanks Chad... I'll dig into this; meanwhile, someone here suggested that perhaps we can fork the kernel, then just build the module and install that with modprobe (without actually updating the on-board kernel). Has that kind of thing ever been done with VOXL1? Ed

Hi @Daniel-Ryu Good news, we have a beta version that is ready for testing. Here are the details: use latest available VOXL2 system image python3 version of voxl-esc tools : https://gitlab.com/voxl-public/flight-core-px4/voxl-esc/-/tree/dev-python3 this version works on PC and VOXL2 (we are moving away from python2.7) if pip3 is not installed, https://pip.pypa.io/en/stable/installation/#get-pip-py if numpy, pyserial are not installed : pip3 install --upgrade numpy pyserial installation on voxl2: https://gitlab.com/voxl-public/flight-core-px4/voxl-esc/-/tree/dev-python3/tools#installation-instructions-for-voxl2 In summary, you will need to follow the steps below on voxl2. we will put it into a script soon. Please let me know if you run into any issues going through these steps #clone the voxl-esc repo cd /home/root git clone https://gitlab.com/voxl-public/flight-core-px4/voxl-esc.git -b dev-python3` #install voxl-esc-tools-bin version 1.1 into voxl-esc/tools directory #see instructions https://gitlab.com/voxl-public/flight-core-px4/voxl-esc/-/tree/dev-python3/tools#accessing-the-esc-tools-software #download and install slpi uart bridge package to VOXL2 cd /home/root wget http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-slpi-uart-bridge_1.0.0-202303021121_arm64.deb dpkg -i voxl-slpi-uart-bridge_1.0.0-202303021121_arm64.deb #stop and disable PX4 while using voxl-esc tools systemctl stop voxl-px4 && systemctl disable voxl-px4 #temporarily move libpx4.so and create symlink for slpi bridge to libpx4.so #this is required because currently the slpi application loader looks for libpx4.so (hardcoded) cd /usr/lib/rfsa/adsp mv libpx4.so libpx4.so.bak ln -s ./libslpi_uart_bridge_slpi.so ./libpx4.so #reboot VOXL2 reboot #test voxl-esc tools cd /home/root/voxl-esc/tools ./voxl-esc-scan.py #perform ESC testing / calibration #... #when done, restore original libpx4.so cd /usr/lib/rfsa/adsp rm libpx4.so cp libpx4.so.bak libpx4.so

This is not legal advice, but Wikipedia has a nice writeup on LGPL that may be relevant to your question https://en.wikipedia.org/wiki/GNU_Lesser_General_Public_License "Whether a work that uses an LGPL program is a derivative work or not is a legal issue. A standalone executable that dynamically links to a library through a .so, .dll, or similar medium is generally accepted as not being a derivative work as defined by the LGPL. It would fall under the definition of a "work that uses the Library". Paragraph 5 of the LGPL version 2.1 states: A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. Essentially, if it is a "work that uses the library", then it must be possible for the software to be linked with a newer version of the LGPL-covered program. The most commonly used method for doing so is to use "a suitable shared library mechanism for linking". Alternatively, a statically linked library is allowed if either source code or linkable object files are provided."

I was not implying that any other calibration needed to be done on the PX4 side. Sometimes you need to tune PX4 control gains, but it seems the default gains worked for you. Thank you for clarifying!