Hi Team,

After upgrading to SDK 1.6.x we noticed that the ov_overlay for voxl-open-vins-server is not present anymore.
Is there any plan to bring it back since this is quite helpful for debugging OpenVINS in different environments and with different camera setups.

Thank you for you help!

Best,
Joel

@Alex-Kushleyev
Thank you very much for your reply!

We bought the USB C adapter from Flir and followed your guide to enable MIPI. Now it works and I can get the video from the Boson over MIPI.

Thanks for your help!

@Alex-Kushleyev

I just noticed with the updated documentation that the J4 connector on the M0201 board is not the USB connector but J3, which is the USB one, is not soldered on. Our Boson+ 640 is purchased separately and is therefore not configured properly.

Is this J3 port the one which has to be used to enable MIPI output on the camera? If so, is it possible to solder the connector on or are also other components on the M0201 board required?

Also is the functionality of the J3 connector on the M0201 the same as Flir's adapter board: https://www.apliter.com/en/product/usb-vpc-kit-para-flir-boson/

Thank you for your help!

Hi @Alex-Kushleyev

I'm currently encountering the same issue. When connecting a Boson+ 640 to the VOXL 2, no image is received. The same configuration worked with the Hadron, where I'm able to get the thermal image.

I assume the Boson is not sending images over the MIPI interface. As you described in the docs (https://docs.modalai.com/M0153/ ), this has to be enabled first with the Flir Boson application. The only versions I could find online are v3.0 and v4.6 which both not connect to the Boson and just freeze when connecting. Is this the same problem why in the guide only version 4.2 is recommended?
I'm connecting the camera with a JST-GH to USB adapter to my laptop.

Is there anything I can try to get thermal images over MIPI from the Boson+?

Thank you for your help!

@tom Thank you for your answer!

Unfortunately the overlay does not appear, even when the drone is armed. We are using Starling 2 drones with SDK 1.6.2.
Also in the voxl-open-vins-server.conf we can't find a setting for something related to the overlay.

Do you have any ideas what we can try to see the ov_overlay again?

Thank you in advance!

Hi Team,

After upgrading to SDK 1.6.x we noticed that the ov_overlay for voxl-open-vins-server is not present anymore.
Is there any plan to bring it back since this is quite helpful for debugging OpenVINS in different environments and with different camera setups.

Thank you for you help!

Best,
Joel

Hi @tom,

Unfortunately, I don’t have a QGC file with the parameters. Do you know where the original parameters come from when the Starling 2 drone is shipped? Are they the ones from the voxl-px4-params repository?

Thank you in advance!

Hi,

I ran the voxl-configure-mpa command on our Starling 2 drone (SDK 1.5.0). Unfortunately, I didn’t realize that this command also resets some of the PX4 parameter configuration files, and since then the drone seems noticeably more unstable in flight.

When we got the drone, I pulled the /data and /etc/modalai folders to my local machine since I thought these will contain the important configuration.
From the command output, I can see that it also overwrote the following files (among others) in the /usr/share/modalai/px4params/v.14/ folder:

• platforms/VOXL_2_defaults.params
• platforms/D0014_Starling_2.params
• other_helpers/starling_2_indoor_position.params

My questions are:

1. Is there a way to restore or recover the previous parameter files that were on the drone before running voxl-configure-mpa?
2. I found the GitLab repository with parameter files, but it seems to only contain the new defaults (the ones that replaced my old configs). Where did the original parameters that shipped with the drone come from?

Thanks a lot for your help!