@Alex-Kushleyev thank you for confirming that the Flir Hadron will work on J8. Would I be able to get it working using the documentation here: https://docs.modalai.com/voxl2-hadron/

For the kernel, I have never looked at it. I see that there is documentation on kernel building etc. I will go through that and see if I can get things to work; otherwise I will reach out

Now that you mention that M0173 and M0181 both need kernel variant 1, and M0155 need kernel variant 0, I am thinking of ditching M0155 board, and just sticking with M0173 board for configuration 1 and M0181 for configuration 2.

Thanks.

@Alex-Kushleyev first of all, I really appreciate the support ModalAI - and specifically you guys, provide. It really means a lot for a team that is moving fast.

There are two independent configurations we are targeting with VOXL 2:

• dual camera configuration with M0155 on J7 (with IMX412) and M0155 on J6 (with some tracking camera), OR
• Flir Hadron configuration with M0181 on J7 (or J8 if it is easily doable).

At this stage, we are not planning on any additional camera with the Flir Hadron configuration.

I hope this clarifies our use case a bit.

Thanks.

@Alex-Kushleyev I am trying to package the M0180 hadron board with VOXL 2. Just to confirm that the M0180 board is properly plugged in the VOXL2 as shown:

If yes, can the M0180 board be trimmed (horns snapped off?) as shown in red for better packaging?

Thank you in advance for your reply.

Hi @Alex-Kushleyev ,

Any update on the EIS feature merge?

Thanks.

@wilkinsaf Hi,

Is there a CAD model for the M0181 and M0159 boards?

Thanks.

@Eric-Katzfey I would love to contribute!

I tried setting up voxl-cross. The pre-build version of voxl-cross is v2.7 on the downloads page. But I see that the voxl-cross in the repository has reached even v4. So I wanted to build voxl-cross myself. Unfortunately, the instructions say to download these files from the modalai downloads:

ubun1.0_1.8.04-M0054-14.1a-perf-20250421-rootfs.tar.tar
ubun2.0_2.0.0-perf-20250421-rootfs.tar.tar

And I can't seem to find these files. Without that, I am unable to compile. Any suggestions on how to compile the latest voxl-cross? Or should I just use v2.7?

Thanks.

Re: External MAVLink Connection using VOXL 2 through ttyHS1

Hi,

I am in need of integrating a mavlink gimbal and a parachute with the voxl2 autopilot. Mavlink is becoming a common protocol to communicate with a number of external peripherals like gimbal, parachute, engines etc. As such, there is a growing need to have voxl-mavlink-server be able to start a bi-directional mavlink stream on app UARTs like that on the USB3/UART Add on board (/dev/ttyHS1).

Is this something on the roadmap? Or any work arounds at the moment?

Thanks.

@Alex-Kushleyev thank you so much. I can wait till the changes are merged and available to update directly on the voxl2.

Yes, I am using the IMX412 camera.

I can start off with whatever you have got for now and hope for a good video feed on my drone without any gimbal. As new changes come along, I will update.

I have never setup a build environment for voxl repos. I am used to building PX4 etc. with some of my custom changes. I would love to learn how to setup the build environment for the voxl repos. So if you can point me in the right direction, that would be great! I see in the docs, under "voxl SDK > custom voxl applications", there are some instructions.

Thank you!

@Alex-Kushleyev said in EIS merge:

You will need to build the voxl-camera-server and voxl-portal packages from the appropriate branches. Hopefully you can do that by yourself. If not, i can post the test debs.

Hi @Alex-Kushleyev I want to use the EIS features. Would you be able to help me guide in the right direction of how to setup a build environment and build from the voxl-camera-server eis branch? Thank you.

@Alex-Kushleyev That was it! I first tried with a lower baud rate of 250K on PX4 and I started getting the battery info. Then as you recommended, I uploaded new parameters to the ESC. I used:

python3 voxl-esc-upload-params.py --params-file ../voxl-esc-params/D0014_starling_1504_3000kv_ms_props/D0014_starling_1504_3000kv_ms_props.xml

because I will be using it on a drone of similar size and performance. Then with 2M baud rate in PX4, I was able to make it work!

Thank you.