Another question.. did this work for you before or is this the first time trying to calibrate at half resolution? if you request the full resolution, do you get the non-zoomed image? i know it will be slow to display in voxl-portal, but you could still check.

If you enable EIS with default camera calibration (no intrinsics cal file). does EIS and zoom work as expected? note that your version of voxl-portal may not have the browser support for zooming, but the config file zoom should still work. If you want to use the latest voxl-portal for EIS, please use this branch : https://gitlab.com/voxl-public/voxl-sdk/services/voxl-portal/-/tree/eis-integration . however the initial zoom of the image coming from the camera server is not dependent on the version of voxl-portal.

Alex

@bendraper I just tried it and it is working now:

modalai@modalai:~/development/modalai/voxl-vision-hub (dev)$ voxl-docker -i voxl-cross launching image: voxl-cross with the following command: docker run --rm -it --net=host --privileged -w /home/modalai --volume=/dev/bus/usb:/dev/bus/usb -e LOCAL_USER_ID=0 -e LOCAL_USER_NAME=root -e LOCAL_GID=0 -v /home/modalai/development/modalai/voxl-vision-hub:/home/root:rw -w /home/root voxl-cross /bin/bash -l voxl-cross(4.4):~(dev)(1.9.21)$ ./clean.sh voxl-cross(4.4):~(dev)(1.9.21)$ ./install_build_deps.sh qrb5165 dev using qrb5165 dev debian repo Ign:1 http://voxl-packages.modalai.com ./dists/qrb5165/dev/binary-arm64/ InRelease Ign:2 http://voxl-packages.modalai.com ./dists/qrb5165/dev/binary-arm64/ Release Get:3 http://voxl-packages.modalai.com ./dists/qrb5165/dev/binary-arm64/ Packages [76.8 kB] Fetched 76.8 kB in 1s (122 kB/s) Reading package lists... Done INSTALLING: libmodal-json libmodal-pipe librc-math libmodal-cv voxl-mpa-tools voxl-mavlink Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: libmodal-cv:arm64 libmodal-json:arm64 libmodal-pipe:arm64 librc-math:arm64 voxl-mavlink:arm64 voxl-mpa-tools:arm64 0 upgraded, 6 newly installed, 0 to remove and 2 not upgraded. Need to get 5026 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://voxl-packages.modalai.com ./dists/qrb5165/dev/binary-arm64/ librc-math 1.4.6-202510091209 [180 kB] Get:2 http://voxl-packages.modalai.com ./dists/qrb5165/dev/binary-arm64/ libmodal-cv 0.6.0-202510141028 [3887 kB] Get:3 http://voxl-packages.modalai.com ./dists/qrb5165/dev/binary-arm64/ libmodal-json 0.4.8-202510091202 [52.5 kB] Get:4 http://voxl-packages.modalai.com ./dists/qrb5165/dev/binary-arm64/ libmodal-pipe 2.14.10-202601210836 [151 kB] Get:5 http://voxl-packages.modalai.com ./dists/qrb5165/dev/binary-arm64/ voxl-mavlink 0.1.6-202511141246 [650 kB] Get:6 http://voxl-packages.modalai.com ./dists/qrb5165/dev/binary-arm64/ voxl-mpa-tools 1.5.6-202601201423 [106 kB] Fetched 5026 kB in 1s (6805 kB/s) debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 79, <STDIN> line 6.) debconf: falling back to frontend: Readline Selecting previously unselected package librc-math:arm64. (Reading database ... 35164 files and directories currently installed.) Preparing to unpack .../0-librc-math_1.4.6-202510091209_arm64.deb ... Unpacking librc-math:arm64 (1.4.6-202510091209) ... Selecting previously unselected package libmodal-cv:arm64. Preparing to unpack .../1-libmodal-cv_0.6.0-202510141028_arm64.deb ... Unpacking libmodal-cv:arm64 (0.6.0-202510141028) ... Selecting previously unselected package libmodal-json:arm64. Preparing to unpack .../2-libmodal-json_0.4.8-202510091202_arm64.deb ... Unpacking libmodal-json:arm64 (0.4.8-202510091202) ... Selecting previously unselected package libmodal-pipe:arm64. Preparing to unpack .../3-libmodal-pipe_2.14.10-202601210836_arm64.deb ... Unpacking libmodal-pipe:arm64 (2.14.10-202601210836) ... Selecting previously unselected package voxl-mavlink:arm64. Preparing to unpack .../4-voxl-mavlink_0.1.6-202511141246_arm64.deb ... Unpacking voxl-mavlink:arm64 (0.1.6-202511141246) ... Selecting previously unselected package voxl-mpa-tools:arm64. Preparing to unpack .../5-voxl-mpa-tools_1.5.6-202601201423_arm64.deb ... Unpacking voxl-mpa-tools:arm64 (1.5.6-202601201423) ... Setting up voxl-mavlink:arm64 (0.1.6-202511141246) ... Setting up libmodal-json:arm64 (0.4.8-202510091202) ... Setting up librc-math:arm64 (1.4.6-202510091209) ... Setting up libmodal-pipe:arm64 (2.14.10-202601210836) ... Setting up libmodal-cv:arm64 (0.6.0-202510141028) ... Setting up voxl-mpa-tools:arm64 (1.5.6-202601201423) ... Processing triggers for libc-bin (2.39-0ubuntu8.5) ... Done installing dependencies voxl-cross(4.4):~(dev)(1.9.21)$ ./build.sh qrb5165 Found voxl-cross version: 4.4 -- --------------------------------------------------------- -- Using voxl-cross 64-bit toolchain for QRB5165 ubun1 18.04 -- C Compiler : /usr/bin/aarch64-linux-gnu-gcc-7 -- C++ Compiler: /usr/bin/aarch64-linux-gnu-g++-7 -- Sysroot : /opt/sysroots/qrb5165_1 -- C flags : -isystem=/usr/lib/gcc/aarch64-linux-gnu/7/include -isystem=/usr/local/include -isystem=/usr/lib/gcc/aarch64-linux-gnu/7/include-fixed -isystem=/usr/include/aarch64-linux-gnu -isystem=/usr/include -idirafter /usr/include -march=armv8.2-a -- CXX flags : -isystem=/usr/include/c++/7 -isystem=/usr/include/aarch64-linux-gnu/c++/7 -isystem=/usr/include/c++/7/backward -isystem=/usr/lib/gcc/aarch64-linux-gnu/7/include -isystem=/usr/local/include -isystem=/usr/lib/gcc/aarch64-linux-gnu/7/include-fixed -isystem=/usr/include/aarch64-linux-gnu -isystem=/usr/include -idirafter /usr/include -march=armv8.2-a -- Link Flags : -B/opt/sysroots/qrb5165_1/usr/lib/ -L/opt/sysroots/qrb5165_1/usr/lib/gcc/aarch64-linux-gnu/7 -L/opt/sysroots/qrb5165_1/usr/lib/aarch64-linux-gnu -L/opt/sysroots/qrb5165_1/usr/lib -L/opt/sysroots/qrb5165_1/lib/aarch64-linux-gnu -L/opt/sysroots/qrb5165_1/usr/lib/aarch64-linux-gnu -L/opt/sysroots/qrb5165_1/lib -L/usr/lib64 -L/usr/lib -- The C compiler identification is GNU 7.3.0 -- The CXX compiler identification is GNU 7.3.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/aarch64-linux-gnu-gcc-7 - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/aarch64-linux-gnu-g++-7 - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Configuring done (0.3s) -- Generating done (0.0s) -- Build files have been written to: /home/root/build [ 6%] Building C object utils/CMakeFiles/voxl-inspect-vfc.dir/voxl-inspect-vfc.c.o [ 6%] Building C object utils/CMakeFiles/voxl-calibrate-px4-horizon.dir/voxl-calibrate-px4-horizon.c.o [ 12%] Building C object src/CMakeFiles/voxl-vision-hub.dir/control_input.c.o [ 12%] Building C object src/CMakeFiles/voxl-vision-hub.dir/fixed_pose_input.c.o [ 18%] Building C object src/CMakeFiles/voxl-vision-hub.dir/geometry.c.o [ 18%] Building C object src/CMakeFiles/voxl-vision-hub.dir/autopilot_monitor.c.o [ 24%] Building C object src/CMakeFiles/voxl-vision-hub.dir/config_file.c.o [ 24%] Building C object src/CMakeFiles/voxl-vision-hub.dir/horizon_cal.c.o [ 30%] Building C object src/CMakeFiles/voxl-vision-hub.dir/main.c.o [ 36%] Building C object src/CMakeFiles/voxl-vision-hub.dir/mavlink_io.c.o [ 36%] Building C object src/CMakeFiles/voxl-vision-hub.dir/imu_manager.c.o [ 27%] Building C object src/CMakeFiles/voxl-vision-hub.dir/horizon_cal_file.c.o [ 39%] Building C object src/CMakeFiles/voxl-vision-hub.dir/mavlink_for_ros.c.o [ 42%] Building C object src/CMakeFiles/voxl-vision-hub.dir/offboard_backtrack.c.o [ 45%] Building C object src/CMakeFiles/voxl-vision-hub.dir/obs_pc_filter.c.o [ 48%] Building C object src/CMakeFiles/voxl-vision-hub.dir/misc.c.o [ 51%] Building C object src/CMakeFiles/voxl-vision-hub.dir/offboard_figure_eight.c.o [ 54%] Building C object src/CMakeFiles/voxl-vision-hub.dir/offboard_follow_tag.c.o [ 57%] Building C object src/CMakeFiles/voxl-vision-hub.dir/offboard_mode.c.o [ 60%] Linking C executable voxl-calibrate-px4-horizon [ 60%] Built target voxl-calibrate-px4-horizon [ 63%] Building C object src/CMakeFiles/voxl-vision-hub.dir/offboard_trajectory.c.o [ 66%] Linking C executable voxl-inspect-vfc [ 66%] Built target voxl-inspect-vfc [ 69%] Building C object src/CMakeFiles/voxl-vision-hub.dir/offboard_vfc.c.o [ 72%] Building C object src/CMakeFiles/voxl-vision-hub.dir/offboard_wps.c.o [ 75%] Building C object src/CMakeFiles/voxl-vision-hub.dir/pose_filter.c.o [ 78%] Building C object src/CMakeFiles/voxl-vision-hub.dir/state_manager.c.o [ 81%] Building C object src/CMakeFiles/voxl-vision-hub.dir/tag_manager.c.o [ 84%] Building CXX object src/CMakeFiles/voxl-vision-hub.dir/trajectory_monitor.cpp.o [ 87%] Building C object src/CMakeFiles/voxl-vision-hub.dir/transform_ringbuf.c.o [ 90%] Building C object src/CMakeFiles/voxl-vision-hub.dir/vio_manager.c.o [ 93%] Building C object src/CMakeFiles/voxl-vision-hub.dir/voa_manager.c.o [ 96%] Building C object src/CMakeFiles/voxl-vision-hub.dir/voxl_vfc_config.c.o [100%] Linking CXX executable voxl-vision-hub [100%] Built target voxl-vision-hub

Hi @jon ,

OK got it. Actually, we already do have a passthrough mode that can accept raw data coming from linux (via voxl io server) and forward it to the UART connection for voxl2_io board, for reference, code is here : https://github.com/modalai/px4-firmware/blob/voxl-dev/src/drivers/voxl2_io/voxl2_io.cpp#L270

Let me figure out (remember) how to use it, I will update you soon.

Alex

Hi @shawn_ricardo
Yes, any I2C port on an expansion board has 2.2K pullups to the voltage on Pin 1 of that connector.

The Linux Kernel user guide has info on which QUPS are enabled or not in which system image.
3356687b-6e2d-4443-9a15-6e9aa07566d1-image.png
and specifically this helps:
https://docs.modalai.com/voxl2-qups/
Note not all QUPs have actually been enabled in the system, but with the sets of ports we have enabled, we never had any customer claim of a shortage:

@zauberflote1 We are using our own custom airframe. Our SDKs are 1.6.0 beta and 1.4.5. However, I also just spoke with a colleague who owns a Starling 2, and he confirmed our findings.

@colombe-ai Can you please provide the SKU? (See: https://docs.modalai.com/sku/#inspect-sku). Was this drone flying before you updated? What version were you using before? If you go back to that version does everything work normally again?

@Samuel-Lehman

If you have the original adapter for Boson+ which allows you to connect it to a USB port, then you can use the FLIR SDK (we use Boson Plus SDK 4.0). Unfortunately, M0153 board does not have J3 connector populated, which would allow you to connect a serial-to-usb adapter to it.

We have several python scripts, which use the Boson SDK to help set up the Boson sensor without the GUI.

query basic sensor info:
https://storage.googleapis.com/modalai_public/temp/boson/boson_read.py

set up sensor for 8bit MIPI mode, 60fps (option to set 30fps):
https://storage.googleapis.com/modalai_public/temp/boson/boson_set_8bit.py

You can put both of these scripts next to the BosonSDK directory and run them. Please check the USB port name inside the scripts.

Once you get that configured, you can put M0153 back on boson. Regarding where to plug it in on Voxl2, please tell me what other cameras you plan to use with your Boson.

Alex

Hi @Tormod-Axelsson-Hagen
Our descriptions tell you all you might need to know to make your own power module:

2-6S tolerant (so VIN capable of up to ~25.2V+)

6A output at 5V

Current monitoring if you do not use our ESCs (our ESCs provide a current reading to keep PX4 and other autopilots happy and for accurate remaining battery %)

Connector format of your choosing but the Molex 4-pin MINI SPOX is the direct 1:1 for VOXL 2 https://www.digikey.com/en/products/detail/molex/0022057045/403343?s=N4IgTCBcDaIAxzGOBWA7HALCkBdAvkA

If you want to make this flexible for VOXL 2 Mini, make it capable of generating 3.8V and use the MOLEX MICRO ONE family of connectors https://www.digikey.com/en/products/detail/molex/2059720041/13235081?s=N4IgTCBcDa4AwFYCcB2Mc4BYCMIC6AvkA)

The rest is up to you based on your design intent and supply chain constraints and preferred vendors.
Hope this helped!

Hey @yunwool
I would recommend writing export ROS_DOMAIN_ID=1 in your ~/.bashrc and then restarting all terminals so the change takes effect. This should prevent other ROS 2 messages from appearing in your environment, since you’ll effectively be using your own domain.

Optionally, you may want to look into the ROS_LOCALHOST_ONLY variable as well, since I do believe if someone else sets their domain ID to 1, you would see their messages.

Hello,

This behavior sounds like turtle mode may be engaged. What are you using for a controller?

If it is a zorro blue the turtle mode switch is in the top left. As a general rule of thumb all switches should be away from you prior to arming. Controls have changed slightly since the guide on the docs page has been updated. I am working on updating them now. For now, please see the image on this forum post for current control mapping.

Hope this help,
Robbie

You can find the source code here: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-logger/-/blob/master/tools/voxl-replay.cpp

@zaimin78 We no longer sell that module. We do have some in stock though if you reach out at https://modalai.com/contact we should be able to get you a custom order.